Repository navigation
0.1.13 — the report says what it reached, and A7 says what clears it
No verdict, exit code, or JSON field changes in this release. What changes is text: one new line in every text report, two longer report sentences, and the acc skill stopping to ask after the first check. If you snapshot text reports in CI, re-record them once; JSON snapshots change only in the A7 finding's detail and coverageGaps strings named below.
Report output
- Every text report from
acc checkandacc reportcarries ascope:line directly under theconfig:line. It has one of these shapes:- root advertises verbs:
scope: the root only — the root advertises 3 verbs (open state tail) and none of them was probed; a batch handed back with --recorded-surfaces covers them - a batch was supplied:
scope: the root, probed by the kit, plus 2 recorded paths from /abs/path/batch.json; nothing below the root was run by the kit, where the path is the batch file's absolute path - no verb set could be read from the root:
scope: the root only — no verb set could be asserted at the root, so how many paths sit below it is not known; a batch handed back with --recorded-surfaces covers them acc reportover a JSON written by an older kit:scope: the root only — the advertised-verb comparison was not recorded by acc <version>, so how many paths sit below the root is not known, where the kit fills in the version that wrote the JSON
- root advertises verbs:
- The A7
unverifieddetail, in the text report and in the finding's JSONdetailfield, is now:both spellings exited non-zero without naming the offending value, so neither refusal can be attributed to the value rather than to the missing verb; a refusal that names the value clears this even where the verb is also missing, so if this root checks placement before values, check the value before the placement. - The remedy line for a modelled declaration whose target did not enumerate is now:
Remedy: nothing you can write in this file changes this — it becomes checkable when the target enumerates at the root, or when you record its rejections below the root and hand them back with --recorded-surfaces. Text report only. - One A7 coverage gap gained a missing word. It was
only the first flag whose set help advertises is probed so a target declaring several sets is checked on one of themand is nowonly the first flag whose set the help advertises is probed so a target declaring several sets is checked on one of them, in the text report and the finding's JSONcoverageGaps.
The acc skill
- The skill stops after step 4, the first check and its two adoptions, and reports before covering subcommands (step 5) or restructuring to one registry (step 6). If the request that invoked the skill already said to continue past the first check, the agent continues; otherwise it asks.
- Step 5 now says that
acc probe-planneeds--pathsor--declaration, an existing requirement, and that a hand-written path list or a modelled declaration at that step is scaffolding to replace in step 6, not to commit.
Guides
Documentation only; nothing here changes what the kit reports for a declaration or batch that passed before.
- Surfaces guide: the invocation named by
selfDescriptionmust also be a declared row, and a declaration normally declares the root aspath: []; both were already how the declaration comparison behaved. - One-registry guide: the root's own verbs such as
helpgo undeclared by a walk over the command table, as its flags do, and once one table feeds both the declaration and the path list,0 disagreementssays only that no flag was added outside the table. - A7 rule page: on a verb-first tool, when a flag is misplaced and its value is outside the set, name the value in the refusal.
0.1.13 (2026-09-07)
Features
- check: the text report says what the run reached, and A7 says what clears it (6f5c6a0)
- check: the verdict says what the run did not reach, and A7 says what would clear it (3270aa0)