Files

Tom Boucher ffd5370464 fix(#2903 ): use the command form that actually works in reader-facing docs (#3047 )

* fix(#2903): use the command form that actually works in reader-facing docs

Docs told readers to type the colon form, which no runtime registers -- 18 of
19 runtimes use slash-hyphen and the 19th uses shell-var -- so anyone copying an
example got an unrecognized command. Swept 178 occurrences across 53 files,
locale mirrors included so they do not re-diverge from English.

The colon form is a source-authoring token, not a user-facing one: install-time
converters key on it to produce the hyphen form runtimes actually register. So
the sweep is scoped, and three things are deliberately left alone:

- ADRs, which are a historical record; editing their prose falsifies what was
  written at the time.
- The legacy release-notes archive, pending a maintainer decision on whether it
  follows the same historical carve-out. Excluding it keeps a later reversal
  additive rather than a revert.
- Source artifacts under commands, workflows and agents, where the colon form is
  load-bearing. Rewriting those would break the installed-skill guarantee across
  every runtime -- the single largest hazard here.

The plugin namespace form is a real, separate token and survives untouched.

Adds a lint enforcing exactly that boundary, since the correct form genuinely
differs by directory and nothing previously caught the drift.

Also fixes a hardcoded colon form in the capability-matrix generator. The sweep
alone would have left the generated matrix disagreeing with the template that
produces it, so the fix is at the source and the output regenerated.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

* fix(#2903): stop the sweep misquoting source frontmatter

Adversarial review caught three lines where the sweep rewrote a citation of the
literal YAML name: key from a source command file. That key genuinely is the
colon form -- this change's own carve-out logic says source-authoring tokens keep
it -- so the docs ended up misquoting the real files. One of the three is an
acceptance-checklist assertion, which the sweep turned into a false statement.

Restored the three citations to match their sources verbatim, surgically: where a
line carried both a name: citation and a real reader-facing slash command, only
the citation reverted and the command stayed corrected.

The guard needed the same distinction, or it would have flagged the restoration
and reddened the build: a gsd:<cmd> token preceded by name: is a citation of a
source token and is now permitted. The exemption is deliberately narrow -- a bare
gsd:<cmd> anywhere else still fails -- with a test pinning that narrowness.

Also makes the detection case-insensitive. Review found /GSD:next slipped through
silently; no such casing exists in the tree today, so this closes a latent gap
rather than fixing a live one.

Swept the whole tree for further corrupted citations: none beyond the three.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

* fix(#2903): retire the stale-next invariant and sweep next like every other command

Maintainer decision on a genuine conflict between two contracts.

Invariant #3054 banned the literal /gsd-next from user-facing docs because it
named a retired workflow-advance command. But commands/gsd/next.md is a live
command -- the state-aware smart-entry launcher -- and this issue requires docs
to use the hyphen form every runtime actually registers. Both could not hold for
this one command, so docs had been sidestepping the ban by keeping the colon
form, which is exactly the defect this issue exists to remove.

FEATURES.md already recorded the reassignment: the hyphen form "is not the
retired workflow-advance command; it is reserved for the state-aware smart-entry
launcher. Workflow advancement remains under /gsd-progress --next." With that
reassignment the invariant's premise is obsolete and the guard now contradicts
the documented command form, so it is retired with a comment recording why
rather than deleted silently.

next is now swept like every other command, and the earlier exemption added to
the new guard is removed so nothing is special-cased.

Four citations of the literal name: frontmatter key stay in colon form, because
the source file really does carry name: gsd:next and a doc quoting it must
reproduce it verbatim. Two of those lines were reworded to say which side is the
frontmatter key and which is the slash command, since they previously conflated
the two.

Verified the retired scan would now genuinely fail against this tree -- the
conflict was real and resolved, not dodged.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

* chore(#2903): backfill changeset pr number

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5 <noreply@anthropic.com>

2026-08-04 13:23:44 -04:00

4.7 KiB

Raw Blame History

Review and Verification Capabilities

This reference describes the Capability Registry declarations used by GSD review and verification features in GSD 1.5 and later. It covers the first migrated review/verification capabilities from ADR-857 Phase 6: code review, security enforcement, and Nyquist validation.

For the system design, see ADR-857: Capability system.

Terms

Capability: A feature bundle declared in capabilities/<id>/capability.json. A capability owns skills, agents, config keys, and loop hooks.

Loop Extension Point: A named point in the Discuss -> Plan -> Execute -> Verify -> Ship loop where capabilities can register hooks.

Step hook: A hook that runs a capability skill as an ordered step.

Contribution hook: A hook that injects guidance into a core workflow prompt.

Gate hook: A hook that evaluates a predicate and can block when blocking is true.

Capability Ownership

Capability	Skills	Agents	Config keys
`code-review`	`code-review`	`gsd-code-reviewer`, `gsd-code-fixer`	`workflow.code_review`, `workflow.code_review_depth`
`security`	`secure-phase`	`gsd-security-auditor`	`workflow.security_enforcement`, `workflow.security_asvs_level`, `workflow.security_block_on`
`nyquist`	`validate-phase`	`gsd-nyquist-auditor`	`workflow.nyquist_validation`

These keys are Capability-owned config keys. They remain valid for .planning/config.json, but they are not central schema keys; validation and defaults come from the generated Capability Registry. Workflows must not branch directly on the boolean activation keys. Workflows resolve activation by calling gsd-tools loop render-hooks <point>.

Hook Map

Point	Capability	Kind	Behavior
`plan:pre`	`security`	`contribution`	Adds threat-model guidance to planner context when security enforcement is active.
`execute:post`	`code-review`	`step`	Runs post-execution code review when code review is active.
`verify:post`	`security`	`step`	Runs security verification and produces `SECURITY.md` when security enforcement is active.
`verify:post`	`nyquist`	`step`	Runs validation coverage audit and produces `VALIDATION.md` when Nyquist validation is active.
`ship:pre`	`security`	`gate`	Blocks shipping unless `SECURITY.md` reports `threats_open: 0`.

Activation Rules

Workflows use the active hook list from the registry:

EXECUTE_POST_HOOKS_JSON=$(gsd_run loop render-hooks execute:post --raw)
VERIFY_POST_HOOKS_JSON=$(gsd_run loop render-hooks verify:post --raw)

The resolver evaluates each hook's when key against the project config and the capability config default. If the key is absent and the capability declaration default is true, the hook is configured on.

A hook is active only when both conditions are true:

The Capability is enabled by the resolved Capability State: installed by .gsd-profile and surfaced by .gsd-surface.json.
The hook is configured on by its when key.

Use the diagnostic state view to inspect the same answer the workflows consume:

gsd-tools capability state --config-dir ~/.claude --raw

In that output, configured reflects config/default resolution, while active reflects final participation after install and surface state. Disabling a migrated Capability at the runtime surface removes its active hooks even when the project config default is true.

Direct command workflows self-gate the same way:

/gsd-code-review resolves the active execute:post hook whose ref.skill == "code-review".
/gsd-secure-phase resolves the active verify:post hook whose ref.skill == "secure-phase".
/gsd-validate-phase resolves the active verify:post hook whose ref.skill == "validate-phase".

Authoring Notes

When adding a review or verification capability:

Declare owned skills, agents, config keys, and hooks in capabilities/<id>/capability.json.
Use unprefixed skill stems in ref.skill; workflows add the gsd- prefix when invoking skills.
Declare produces and consumes arrays for every step and contribution hook.
Use onError: "halt" for verification work that must stop advancement when it fails.
Use a blocking gate for ship-time predicates that must prevent release.
Regenerate gsd-core/bin/lib/capability-registry.cjs with npm run gen:capability-registry.
Add tests that prove disabled hooks are absent from loop render-hooks output and that workflows do not branch directly on the capability's activation config key.

Do not add third-party code loading through a capability declaration. ADR-857 reserves that trust boundary for a separate design.

4.7 KiB Raw Blame History