chore(agent-hub): tighten verifier re-run scope, drop stale NORTHSTAR read - #104
Merged
Conversation
… read Synced from agent-hub-init kit (usage audit 2026-09-02): verifier now audits the implementer's evidence note by default instead of independently re-running npm test/npm ci from scratch. Re-run is reserved for suspicious notes, outward-facing/release nodes (this repo already shipped one real production bug via v1.2.0 -> v1.2.1), or project-declared exceptions. Also fixed manifest.yaml reads: NORTHSTAR.md (unused by the recipe) -> doctrine/MEMORY.md (actually used in step 4, was undeclared). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Synced from
agent-hub-initkit (usage audit 2026-09-02).What
haven/workers/verifier/manifest.yaml:reads:drops unusedNORTHSTAR.md, addsdoctrine/MEMORY.md(actually needed by recipe step 4, was undeclared).haven/workers/verifier/recipes/verify_seal.md: adds a "Re-run scope" section — verifier now audits the implementer's evidence note by default instead of independently re-runningnpm test/npm cifrom scratch on every node.Why
Usage audit across 3 production hubs (this one included) found verifiers re-running the full test suite from a fresh
npm ci(isolated worktree) for every node, roughly doubling the token cost of every change with no change to the SEAL/REOPEN verdict.EvidenceOnlymeans "don't substitute reasoning for evidence," not "always regenerate the evidence yourself." This PR pins that boundary explicitly.Re-run is still expected for: suspicious/truncated notes, outward-facing or
/release-gate nodes (this repo already shipped one real production bug via v1.2.0 → v1.2.1 — release nodes are exactly where the independent-confirmation cost is worth paying), or anythingdoctrine/domains/PROJECT.mdexplicitly flags.Bookkeeping-only change under
agent-hub/— no application code touched.🤖 Generated with Claude Code