Skip to content

release(v8.4.1): activate the doc-verifier spawn in /audit + /refactor - #90

Merged
aimsise merged 1 commit into
mainfrom
release/v8.4.1
Jun 10, 2026
Merged

release(v8.4.1): activate the doc-verifier spawn in /audit + /refactor#90
aimsise merged 1 commit into
mainfrom
release/v8.4.1

Conversation

@aimsise

@aimsise aimsise commented Jun 10, 2026

Copy link
Copy Markdown
Owner

TL;DR

v8.4.0 shipped agents/doc-verifier.md (the EC-SELFDOC doc/interface-truthfulness verifier) but no skill spawned it — EC-SELFDOC fired only via the inline ac-evaluator duty. v8.4.1 wires the actual spawn so the cross-agent handoff runs at review time.

What changed

  • /audit Step 2 and /refactor Phase 3 Step 6 now invoke simple-workflow:doc-verifier in parallel with their other read-only reviewers, gated on constraints.selfdoc_verification being active AND a documentation / advertised-interface surface being touched (a README / *.md / --help / man-page, or a Gate 9 R3 DESCRIPTION-MATCHES-BEHAVIOR / R4 DOC/INTERFACE TRUTHFULNESS AC).
  • doc-verifier RUNs the unit's advertised examples / boundary claims against the real build under the .simple-workflow/scratch/ carve-out; a non-reproducing example or advertised≠enforced boundary is a Critical that feeds the /audit Step 3 aggregation and the /refactor Step 7 loop-exit tally; an unrunnable build is a fail-open PASS-WITH-CAVEATS.
  • agents/doc-verifier.md gains a ## When spawned (input contract) section; both review skills' reviewer tables + Binding-rules name doc-verifier.

Scope rationale

doc-verifier is wired into the two review skills only. /impl Step 15 already grades EC-SELFDOC inline via the ac-evaluator duty (avoids hot-path duplication); /create-ticket is authoring-side. This follows CLAUDE.md ## Modifications sibling-symmetry (both review orchestrators get it).

Migration

Non-breaking, no new kill switch — constraints.selfdoc_verification: off now also skips the spawn. With the switch off, or no documentation / advertised-interface surface touched, the review flow is byte-for-byte pre-v8.4.1.

Verification

  • tests/test-skill-contracts.sh 824/824 (+ CT-EV-SELFDOC-6), tests/test-path-consistency.sh 144/144 (doc-verifier already registered), full run-all.sh ALL SUITES PASSED.
  • plugin.json 8.4.1 == newest CHANGELOG [8.4.1] (CT-MODE-14), real ISO date (CT-MODE-13); ac-evaluatorac-evaluator-hi byte-identical (CT-EV-MODEL-1).

See CHANGELOG.md [8.4.1].

🤖 Generated with Claude Code

v8.4.0 shipped agents/doc-verifier.md (the EC-SELFDOC doc/interface-truthfulness
verifier) but no skill spawned it — EC-SELFDOC fired only via the inline
ac-evaluator duty. This wires the actual spawn so the cross-agent handoff runs at
review time:

- /audit Step 2 and /refactor Phase 3 Step 6 now invoke simple-workflow:doc-verifier
  in parallel with their other read-only reviewers, gated on
  constraints.selfdoc_verification being active AND a documentation /
  advertised-interface surface being touched (README / *.md / --help / man-page, or a
  Gate 9 R3/R4 AC). A non-reproducing example or advertised-vs-enforced boundary
  mismatch is a Critical that feeds the audit aggregation / refactor loop-exit tally;
  an unrunnable build is a fail-open PASS-WITH-CAVEATS.
- agents/doc-verifier.md gains a ## When spawned (input contract) section.
- constraints.selfdoc_verification: off now also skips the spawn (no new kill switch).

doc-verifier is wired into the two review skills only — /impl Step 15 already grades
EC-SELFDOC inline via the ac-evaluator duty, and /create-ticket is authoring-side.
Additive + kill-switched; with the switch off or no doc surface touched the review
flow is byte-for-byte pre-v8.4.1. Guarded by CT-EV-SELFDOC-6; skill-contracts 824/824,
path-consistency 144/144, full sweep green; ac-evaluator <-> ac-evaluator-hi
byte-identical.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@aimsise
aimsise merged commit 7d6a632 into main Jun 10, 2026
2 checks passed
@aimsise
aimsise deleted the release/v8.4.1 branch June 10, 2026 00:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant