36375513b9
* feat(#3840): generate docs/FEATURES.md from per-feature fragments docs/FEATURES.md was hand-maintained, and every feature PR wrote into two shared mutable cells: the '### N.' heading whose integer was hand-allocated at authoring time, and the hand-maintained table of contents. Concurrent PRs all picked the same next integer, and two PRs adding differently numbered features still collided on the TOC. #3831 was renumbered 165 -> 166 -> 167 -> 168 across successive rebases, each collision also costing a full matrix verification run because the sha-keyed pass marker dies with the rebase. Mechanism: one fragment per feature at docs/features/<slug>.md carrying id/title/group (and an optional order) in frontmatter, consolidated by scripts/gen-features.cjs --write|--check into a marker-delimited region of docs/FEATURES.md that holds BOTH the TOC and every section body. Group headings and their order are derived too - a group sorts by its lowest-ordered member - so there is no shared registry to edit either; optional per-group prose lives in docs/features/_groups/<slug>.md. A contributor adds exactly one new file. Wired into regen:derived and lint:generated-sync alongside the eight existing generators, matching gen-adr-index.cjs's CLI shape and typed-REASON reporting. Migration froze all 168 existing numbers verbatim: identical section set, identical order, identical bodies. Two defects found in the tree are fixed inline rather than carried forward - the '## Related' block had been spliced into the middle of the document, orphaning §142's Reference line, and four inbound anchors were already broken on next (FEATURES.md#runtime-identity in two files, and #143-spec-phase-edge-completeness-probe off by one). Since the repo has no link checker, --check now validates every inbound FEATURES.md#anchor by resolved target, so that class cannot ship silently again; locale FEATURES.md files resolve elsewhere and stay out of scope. Refs #3840 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * fix(#3840): carry upstream §69 delta into its fragment and harden the generator Review found section 69 missing '[--strict]' and REQ-STATE-05/06 versus origin/next. Root cause was a stale base, not extraction loss: those lines landed in394bf384b(#3844) AFTER this branch forked at63abcface, and 'git diff63abcfaceorigin/next -- docs/FEATURES.md' is exactly that hunk. Merging origin/next auto-applied the hunk into the GENERATED region, which --check immediately reported as stale; the delta is now carried in docs/features/statemd-consistency-gates.md and regenerated from there. --write is now fail-closed. It previously rendered the region even with violations outstanding, warning only on stderr and exiting 0, so a '--write && git commit' chain could commit a FEATURES.md carrying two colliding sections. It now refuses and exits 1; --force is the explicit override and says so in the report. The test that pinned the old behavior now pins the refusal, plus the --force override and its scoping. Marker forgery is rejected at two layers. A fragment body containing '<!-- FEATURES:START' or '<!-- FEATURES:END' is a typed body_forges_region_marker violation (fragments and group notes alike), and spliceIntoFeatures anchors the end boundary with lastIndexOf instead of indexOf, so a marker that reaches the document by any other route can only make the generated region grow, never shrink. Matching is on marker PREFIXES, so a decorated variant comment cannot slip past. Symlinked corpus entries are refused with a typed dirent_not_regular_file rather than read. A fork PR could otherwise commit docs/features/evil.md as a symlink to any readable path and have the generator inline those bytes into the committed docs/FEATURES.md on the next regen. Equivalence re-verified with a method that cannot cancel out. The first check extracted both operands with the same body-normalising helper, so anything that helper dropped was dropped on both sides. The replacement runs two independent passes: a global content-line multiset diff with no per-section logic at all (0 gained, 19 lost, all 19 the stale hand-written mini-TOC links this change deliberately deletes), and a per-section byte-exact body diff carrying a coverage assertion that fails loudly per file when the extractor accounts for fewer lines than the file contains. That assertion caught two blind spots in the checker itself. 168/168 sections present, order identical, one intended body difference (§142 regains the Reference line orphaned by the misplaced '## Related' block). Refs #3840 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * chore(#3840): backfill changeset PR number Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> --------- Co-authored-by: sim <sim@local> Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
2.2 KiB
2.2 KiB
id, title, group
| id | title | group |
|---|---|---|
| 122 | Skill Surface Consolidation | v1.40.0 Features |
Purpose: Cut the eager skill-listing overhead by folding 31 micro-skills into 4 new grouped parents and 6 existing parents that absorb sub-operations as flags. Zero functional loss — every removed micro-skill's behavior survives via a flag on a consolidated parent. After consolidation, commands/gsd/*.md ships 60 sub-skills (plus 6 namespace meta-skills, see #123).
Requirements:
- REQ-CONSOLIDATE-01: Four new grouped skills replace clusters of micro-skills:
/gsd-capture— folds add-todo (default), note (--note), add-backlog (--backlog), plant-seed (--seed), check-todos (--list)/gsd-phase— folds add-phase (default), insert-phase (--insert), remove-phase (--remove), edit-phase (--edit)/gsd-config— folds settings-advanced (--advanced), settings-integrations (--integrations), set-profile (--profile)/gsd-workspace— folds new-workspace (--new), list-workspaces (--list), remove-workspace (--remove)
- REQ-CONSOLIDATE-02: Six existing parents absorb wrap-up / sub-operations as flags:
/gsd-update --sync,/gsd-update --reapply,/gsd-sketch --wrap-up,/gsd-spike --wrap-up,/gsd-map-codebase --fast,/gsd-map-codebase --query,/gsd-code-review --fix,/gsd-progress --do,/gsd-progress --next. - REQ-CONSOLIDATE-03:
/gsd-nextis not the retired workflow-advance command; it is reserved for the state-aware smart-entry launcher. Workflow advancement remains under/gsd-progress --next. - REQ-CONSOLIDATE-04: Deleted micro-skill slash forms (the bare
gsd-add-todo,gsd-add-backlog,gsd-plant-seed,gsd-check-todos,gsd-add-phase,gsd-insert-phase,gsd-remove-phase,gsd-edit-phase,gsd-new-workspace,gsd-list-workspaces,gsd-remove-workspace,gsd-settings-advanced,gsd-settings-integrations,gsd-set-profile,gsd-sketch-wrap-up,gsd-spike-wrap-up,gsd-reapply-patches,gsd-code-review-fix, …) MUST resolve to "Unknown command" — no shadow stubs. - REQ-CONSOLIDATE-05:
autonomous.mdinvokes/gsd-code-review --fix(was previously calling the deletedgsd-code-review-fix).
Reference issue: #2790