Skip to content

v5.0.0 - Zero-Base Redesign Mainline

Choose a tag to compare

@github-actions github-actions released this 09 Jul 01:29
· 551 commits to main since this release
c100dbb

What's Changed

v5.0.0 promotes the zero-base redesign to mainline — plan-time pre-approval, a runtime-floor secret-read allowlist, and a reproducible release pipeline

Before / After

Before After
Confirmations for secret reads / egress interrupted autonomous runs mid-implementation Plan-time pre-approval: expected confirmations are approved together when the plan is fixed, so /harness-work and /breezing run to completion
secret-read was the only runtime-floor category without a pre-authorization mechanism HARNESS_RUNTIME_FLOOR_SECRET_ALLOW env + per-project runtimefloor.secretAllow allowlist (fail-safe: invalid config denies everything)
v4-series internal layout (skills structure, hook wiring, generated artifacts) Zero-base redesign is now the mainline; cursor/codex delivery hooks are generated artifacts (harness gen)
Committed binaries could silently drift from source Reproducible builds (pinned toolchain, -trimpath -buildvcs=false) enforced by a binary/source drift gate

Breaking Changes

  • Zero-base redesign supersedes the v4-series layout: skills structure, hook wiring, and generated-artifact layout are fully reworked; cursor/codex delivery hooks are now generated, gitignored artifacts. Run /reload-plugins after updating from v4.16.x.

Added

  • Plan-time pre-approval flow: /harness-plan generates a pre-confirmation section per work scope (secret reads / egress / destructive operations) so runs are approved once and complete uninterrupted
  • Runtime-floor secret-read allowlist: declared paths no longer stop the run; no blanket opt-out, project-external absolute paths are ignored
  • Failure Codifier (Phase 100): read-only extraction of recurring failure patterns from orchestration/judgment ledgers with a structurally enforced human-approval gate (no auto-promotion to SSOT)
  • Harness worktree residue doctor check: harness doctor flags stale or untracked harness worktrees as advisory warnings

Changed

  • Review contract: the self-review ban now targets "the same context that produced the diff" instead of a model family; fresh-context cursor advisory pre-review is allowed while the primary verdict stays with the brain reviewer

Fixed

  • /harness-release delegates GitHub Release publishing to the release workflow (Claude Code runtime hard floor denies direct publish commands)
  • Reviewer cyber-safeguard false triggers mitigated via fresh-context isolation and a bounded findings-return contract

Full details (Japanese): CHANGELOG.md


🤖 Generated with Claude Code