Files
gstack/scripts/question-registry.ts
Garry Tanandcapy-ai[bot] 14d7414af3 v1.93.33.0 wave(review): #3705 #3744 #3745 #3764 #3765 #3795 (#3852)
* fix(ship): base merges, adjacent base edits, test-only and audit-requested fixes no longer force a second review loop (GST-407, GST-384, GST-391)

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* ship driver: trim two phrases for headroom with #3662

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* ship driver: keep the Next steps heading phrase the handoff check reads; trim elsewhere

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* test: regenerate ship goldens

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* fix: pre-landing review fixes

comparePath returns same only when every hunk sits where the base change puts it (patch-ids ignore positions) and treats a file-mode change as changed; the scoped-review packet says when a fence is truncated; --docs-result must be the posted audit's result; the --context-reviewed record goes beside the packet, outside the worktree. Negative controls for each.

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* fix: pass-2 review fixes

A test edit routes as tests= only when it adds lines with no gate tag; a removed or changed line or an unreadable test diff goes through the full loop. Diffs skip textconv. A hunkless patch (binary, empty, mode-only) is same when its patch-id matches. Without --reviewed-base test files route as before. finish's packet path and attempt's state directory have fallbacks.

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* fix: Step 11 review fixes; a version-only stamp_files edit after review is release metadata (GBRA-251)

gateEditedPaths reads removed lines only inside hunks; carry refuses when a path listing fails; docs freshness stops on a failed listing; attempt counts an unreadable state file. releasePaths includes stamp_files paths whose edit is a version swap under stamp_patterns.

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* fix: no test edit skips review; guard packet writes; exclusive attempt state

A test-only edit with no gate tag gets the scoped fix-check of its test hunks instead of a lanes-only rerun. Packet write failures print a STOP or RECEIPT_CARRY_REFUSED. attempt's allowance uses an exclusive create.

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* fix: attempt prints gstack's install command; carry checks the product diff outside context paths

The attempt STOP no longer echoes the audit child's fix text. A scoped-review carry now requires the product patch-id without the context paths to match at both heads.

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* fix: oversized packets take the full loop; exact --docs-requested match; name-only test globs only in test dirs

A scoped-review packet section over 200 lines sends that path to the full loop instead of a truncated packet. The docs-result path match is exact. test_*.py, *Test.java and similar count as test code only under a test directory.

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* docs(unattended): carry's scoped-review refusal and what it keeps

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* docs: carry's scoped-review route in ship-policy, review-policy and troubleshooting (docs-a-1)

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* test(windows): curate ship-rereview-triggers out of the Windows lane like ship-release (run 41193336209)

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* fix(review-log): record a notes-only /ship pass clean; name the cause and repair when a pass's tree moved (GST-430)

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* fix(receipt): carry and write handle PRs with thousands of files; tree receipt fails closed on a failed diff (GST-448)

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* fix(ship): preflight routes RECEIPT_CARRY_SCOPED_REVIEW to the scoped review; carry --dry-run writes no packet (GST-442)

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* docs(ship): Step 1.4 and Step 16 route the scoped-review refusal and the --docs-requested fix; trims keep the cap (GST-442, GST-444)

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* fix: /ship review pass 1: notes-only floor, scoped carry order, named temp and diff refusals

- A notes-only pass is recorded clean only when every finding is fixed, or noted or deferred below the
  blocking floor (never CRITICAL or blocking), by its logger-stamped action, and the findings account
  for the claimed issue and critical counts (GST-430).
- The preflight scoped carry route commits and pushes the base-merge fix before writing the packet (GST-442).
- patchId refuses by name on an unwritable TMPDIR; the tree receipt names why its diff failed (GST-448).
- Step 16 stage 3 spells out --docs-requested with its --docs-result (GST-444).

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* test: pin the Step 16 --docs-requested route with its --docs-result

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* fix: a claimed clean review row with a logger-stamped open gate finding reads UNVERIFIED (red-team, pass 1)

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* fix: Step 11 findings: gate rows from --findings are stamped, one open rule, stale patch-id dirs swept

- deriveFromFindings stamps gate rows with the session kind before deriving status, so a findings file cannot
  dispose of a gate finding the unattended logger forces open (outside-voice#1).
- reviewFreshness reads a claimed row's findings with isOpenByAction, the rule the notes-only rewrite uses;
  noted and deferred clear a finding only when it is marked blocking: false and is not CRITICAL.
- patchId sweeps gstack-patch-id-* directories over an hour old that a killed carry left in TMPDIR.

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* fix: Step 11 round 2: stamped-open gates win over status and disposition; resolved gate, skipped and below-floor actions stay CURRENT

- isOpenFinding treats action 'open' (the logger's forced-open stamp) as open before a row's status or disposition.
- reviewFreshness flags a claimed clean row only for an 'open' action or a CRITICAL or blocking deferral or note, so
  interactive kept and restored gates, skipped advisories and INFORMATIONAL deferrals read CURRENT as before.

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* fix: carry dry run offers the scoped route last; patch-id diff under the git dir; changelog matches the review-log floor

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* fix: a claimed clean review row with any unresolved non-gate CRITICAL finding reads UNVERIFIED (pass 2 red-team)

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* docs: carry dry-run scoped route, patch-id directory, tree-receipt refusal (docs-d-1 audit)

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* fix(ship): Step 3 names merge conflicts in its STOP sentence again (ship-workflow-clarity pin)

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* fix(tree-receipt): keep the gated-to-current diff at the file helper timeout (60 s); pregate literals check

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* test(carry): large-diff fixture sets core.longpaths so Git for Windows can add its long receipt paths (windows-free-shard 1, run 41210080055)

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* fix(review): a stale local base branch yields to its origin twin in gate-diff and diff-scope (GST-462)

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* fix(ship): Step 11 saves the targeted record and the receipt writes carry it; Step 9 clears it (GST-464)

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* changelog: GST-464 and GST-462

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* fix(review): pass 1: ahead and diverged labels, diff-scope needs shared history; preflight refreshes origin/<base> and stops on a diff far beyond the PR (GST-462, HARN-15)

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* fix: pass-2 review fixes for base twin, prSized stop and targeted record

Resolve the tracking twin by refs/remotes/<remote>/<ref> and only for a bare
branch name, keep a local base that is ahead or diverged, quote the prSized
stop's base and name the fork case, and have every Step 9 entry create,
exclude and clear .gstack/tmp/targeted.json.

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* fix: origin's tracking base wins whenever related; prSized lower bound

The fix-check found that keeping a local base ahead of origin left unpushed
base commits out of the gate scan while review-plan listed them. The tracking
branch now wins whenever it shares history with HEAD, an explicit origin/main
reads refs/remotes/origin/main, the preflight also stops when the diff lists
fewer files than the PR, and the Step 9 exclude line survives a missing
.git/info and an exclude file without a final newline.

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* changelog: the tracking-ref claim holds while the tracking branch exists

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* test: repin the two ship section briefs under no-loss replay GST-464

GST-464 brief-identity check: every reviewer brief lib/review-brief.ts cuts
from ship/sections/review-army.md and adversarial.md stays byte-identical to
the bodies the L and GST-257 replays admitted; only lead instructions outside
the cut spans changed. The check is a test CI runs.

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* ship: keep Step 9's PASS_HEAD sentence whole; repin review-army under GST-464

The targeted-record line follows the PASS_HEAD/RANGE_BASE sentence instead of
splitting it (test/review-fix-range.test.ts pins that sentence). The brief-body
check still holds: every reviewer brief is byte-identical.

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* fix: restore bin/gstack-ship-receipt after the main merge

The merge commit b10e2db wrote a truncated copy of the file. This is the
three-way merge of both sides with the refused() union: main's codes plus
RECEIPT_CARRY_SCOPED_REVIEW.

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* review-collect: narrow the consumer scan and give it one 300 s deadline (GST-544)

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* review-collect: keep the consumer scan deadline under the 180 s plan timeout (review fix)

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* review-collect: plain paths under --literal-pathspecs; whole-millisecond timeout override (review fix)

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* review-collect: whole-tree grep for non-UTF-8 names, no argument spread, name spawn errors (review fix)

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* review-collect: cap the consumer grep output at 256 MB across calls; per-scan deadline wording (review fix, cycle 4)

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* review-collect: read a missing spawn status as null (Bun 1.4.2 returns undefined on ENOENT)

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* test: review-collect whole-tree helper reads a null status as -1 (typecheck:test ratchet)

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* review-bots: /review and /ship triage every configured review bot, not only Greptile (#3122)

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* fix: pre-landing review fixes (gh before 2.48 pages without --slurp; driver routes Step 10; tests for guards, review-bot fence, REMOTE_SLUG owner)

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* fix: drop the review-bot fence test that could not fail (the tool-fence WARN degrade is unreachable: placeholder spans are skipped first)

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* fix: Step 11 review fixes (record by comment id so a filename never reaches a shell; lookup failures are errors; tojson pages; longest bot prefix wins)

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* fix: pass-2 review fixes (record refuses * paths, colliding ids and a missing fetch dir; parent requires id and dir; botOwning doc)

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* review: classify the PR type and always check repo conventions (#356)

The checklist now opens with a PR-type line (application, CI/infra,
scripts/tooling, docs-only or mixed). Application and mixed diffs run
every category; other types always run five categories, including the
new Repo Conventions & Platform Fit, and report the rest as not
applicable in one line instead of skipping silently.

No-loss replay: GSTA-224 H1 preregistered no-loss run (run id
gsta224-h1-20261031, Opus 5.5, 81 calls, $9.53) against main's checklist
with a no-gstack arm; every preregistered bar passed. The
review/checklist.md pin in test/review-packets-removed.test.ts moves to
a32963ef with replay 'GSTA-224 H1'.

Refs GSTA-224

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* review-bots: allowlist the record placeholders and match Step 10's id rule in tests

The record fence uses <comment-id>, <fix|fp|already-fixed> and <category>,
each with an enum or numeric grammar; <greptile-dir> becomes <bot-dir>.
review/greptile-triage.md also lists every REVIEW_BOTS skip reason.

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* docs: review-bot triage covers every configured bot (#3122)

README, CONTRIBUTING, the contributor reference and standalone-binaries
name gstack-review-bots and the review-bot fence; TODOS drops the #3122
item; the changelog fragment covers record-by-id and lookup errors.

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* test: the PR-type test also pins the compose, Terraform and README/CHANGELOG phrases

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* test: follow the review-bot rename in the remote free tier's three reds

The cross-skill consistency judge describes review-bot-history.md and its
record helper; the tracker-guard exemption for the removed raw Greptile
fetch in review/greptile-triage.md is dropped (the fetch now lives in
gstack-review-bots, whose bodies still reach context only through
gstack-issue-guard); the Step 10 PR-check test expects 'Review bots: not
run'. HARNESS_VERSION stays 6: skill-fixture.ts and llm-judge.ts are
recorded non-behavioral for every other case.

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* test: keep the cross-skill judge's rubric to one renamed bullet

Name review-bot-history.md beside the older greptile-history.md so the
calibration corpus still matches, and keep the REMOTE_SLUG bullet. One
live 3-sample panel at this tree: consistent 3/3, scores 4/4/4.

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* changelog: H1 fragment passes prose lint

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* changelog: name the H1 fragment after its branch; TODOS drops #356

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* docs: /review's PR type step in docs/skills.md (#356)

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* ship-policy: review_exclude_paths key and loadPolicyAt (GST-508)

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* review: apply the base policy's review_exclude_paths and the reviewer diff ceiling (GST-508)

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* receipt: bind review_exclude in write, carry and the queue (GST-508)

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* docs, tests and changelog for review_exclude_paths (GST-508)

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* fix: pre-landing review fixes (binary by bytes, links kept, untracked files out of the selection)

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* fix: keep binary files at code paths under review_exclude_paths

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* docs: name the reasons that keep a binary file under review_exclude_paths

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* fix: keep every review_exclude_paths candidate when the gate scan is unknown; docs example names its version

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* test: keep the NUL fixture clear of the sync-spawn tripwire

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* changelog: split the ceiling sentence

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* fix: keep a live binary file whose bytes cannot be read; tests render outside voices from a clean checkout and read the ship fixture text

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* test(review-exclude): explicit +x for the census script; skip the chmod-000 read case on Windows and root

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* refactor: move loadPolicyAt to lib/ship-policy-at.ts so lib/ship-policy.ts stays under the 800-line module cap

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* fix: refuse a base that contains HEAD; skip a self-pointing origin/HEAD (GST-774)

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* chore: regenerate gstack-doctor-components.sh for BASE_CONTAINS_HEAD

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* fix: land resumes a merged merge-only PR instead of refusing BASE_CONTAINS_HEAD (GST-774 review)

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* docs: changelog fragment for GST-774

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* docs: troubleshooting names diff-scope base_contains_head and the self-pointing no_base case (GST-774 docs audit)

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* test: repin the reviewer briefs to GST-508's no-loss-tested bytes

ship/sections/review-army.md, ship/sections/adversarial.md and lib/review-depth.ts now pin
the bytes the GST-508 preregistered no-loss replay ran at ef2760f (handoffs/GSTA-202/noloss-results.md
in the GStack Minder drive): Arm V 33/41 vs R 33/41, delta 4, exact sign flip, p_NI 0.0279 (pass).
The merge of main 83ae96e leaves these three files byte-identical to ef2760f, and an Arm P unit
(3593) renders byte-identical briefs at ef2760f and at the merge.

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* fix: GST-774 review round 1 — merged resume depth, aliased and detached PR checkouts, develop/trunk defaults

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* ship: Step 20 says a metrics row, keeping DRIVER.md at 12 KB after the main merge

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* test: ship-parts resend case leaves room for the first phase-3 part after the Step 9 targeted-record sentence

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* fix: /ship delivers review/checklist.md in two parts so checklist v1 fits the 24576-byte part cap (#3670)

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* changelog: drop the GST-407 and GST-430 fragments, already released on main (stacked history)

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* wave review-53cfb5bfe011: lib/ship-policy.ts back to 800 lines (module-size ratchet after merging #3744 and #3795)

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* wave review-53cfb5bfe011: /ship pass 1 fixes

- lib/ship-receipt-depth.ts: a merged resume (land after a true merge) no longer recomputes the review_exclude digest over the emptied range, so it lands instead of RECEIPT_INVALID (failing-first land test with review_exclude_paths active).
- bin/gstack-review-dispatch render: a standalone targeted render under an active review_exclude_paths refuses and points at the pass manifest voices stage, instead of writing a brief with no selection that leaves verify dirty (failing-first test).
- test/default-base.test.ts: #3795 expectations follow main R51 depth (light for an 80-line code diff; runtime_lines=80 still proves the real base).
- test/review-dispatch.test.ts: the GST-897 fingerprint test renders from the clean checkout, like its neighbor, because CI rebuilds the tracked lib/diagram-render/dist/diagram-render.html and the reviewer diff ceiling refused the ROOT render.

* wave review-53cfb5bfe011: /ship pass 2 fixes

- lib/review-exclude.ts: binaryContent reads each blob's first 8,000 bytes (git cat-file blob, 8 KB buffer) instead of one --batch read capped at 256 MB, so head mode (receipt, carry, queue) and the plan agree past 256 MB of blobs; an unreadable blob is kept, as in live mode. Failing-first test with two 270 MB blobs.
- lib/review-bots.ts: a file-level bot review comment (subject_type file, no line position) is triaged instead of read as outdated. Failing-first test.
- test/ship-queue-land.test.ts: the merged-resume exclusion test runs its gate scan under the fixture state root, not the real home (CI free-suite 6 home containment).

* fix: merge follow-ups for main 3d99c22: origin/* stays qualified in diff-scope's twin step, retro skeleton back under its cap, combined no-loss pin GST-508+R51+GST-911

* fix(review): receipt write gate-scans whenever the base declares review_exclude_paths; collectLive never re-qualifies origin/<base> (#3852 /ship red-team#1, outside-voice#1)

* test: the docs-only receipt digest test keeps its gate scan out of the real home (free-suite shard 5 FREE_SUBSHARD_REJECTED)

* fix(merge fc292e22f): tentative REVIEW_EXCLUDE_KEY_VERSION, classify targeted.json, render main's new outside-voice test from a clean checkout

- lib/ship-policy.ts: REVIEW_EXCLUDE_KEY_VERSION 1.93.0.0 -> 1.94.0.0, the next-minor tentative form stamp_paths moves (docs/ship-policy.md, #3512); 1.93.0.0 is a released heading that never names the key.
- test/gstack-clean-producers.test.ts (new from main): KEPT gains targeted.json, the wave's --review-targeted input.
- test/review-dispatch.test.ts: main's wrong-tree test rendered the outside voice from ROOT; a CI build that dirties ROOT pushes that diff past the wave's REVIEW_DIFF_MAX_BYTES ceiling, so render refused and verify saw no brief (exit 3). It now runs in cleanCheckout like the wave's other outside-voice tests.

* test(merge 68410828f): GST-967's brief-body pin carries the wave's GST-508 placeholders

The merged sectionTexts differ from main's by exactly the wave's GST-508 exclude-pathspec lines (merged minus main equals wave minus fc292e22f); the 1,440-case plan grid still hashes to main's MAIN_PLANS. Checks: GStack Minder drive handoffs/GSTA-202/merge-6841-checks.md.

* fix(merge e85005482): targeted classes since the read accept an empty range; the wave's receipt tests pass main's targeted record

- lib/ship-receipt-depth.ts targetedClassesSince (main, GST-986) reads the range from the commit the targeted reader read to HEAD through headInputs, which since #3795 runs gstack-diff-scope's BASE_CONTAINS_HEAD check. When the reader read HEAD itself the range is empty, diff-scope reported base_contains_head, and every write with --review-targeted was refused (the product patch matched). It now passes merged=true (--merged), which skips only that check; an ancestor check already guards the range.
- test/review-exclude.test.ts and test/review-targeted.test.ts: since #3887 write refuses a money head with no targeted record and requires the record's head, so the wave's two writes that must succeed pass one, as main's own tests do (targetedAtHead in test/ship-receipt-depth.test.ts).

* test(merge e85005482): drop the wave's duplicate targeted.json KEPT entry

Main (#3887) classified .gstack/tmp/targeted.json in KEPT too; the auto-merge kept both keys, which typecheck:test rejects (TS1117). Main's entry stays.

* test(merge e85005482): ship size ledger entry for the merged tree (-232 B)

Main's ship size ledger plus the wave's entries summed to 345,334 B; the merged tree measures 345,102 B because DRIVER.md takes main's shorter Step 19 line. Recorded with scripts/size-ledger.ts record ship.

---------

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
2026-11-03 01:40:07 +00:00

680 lines
25 KiB
TypeScript

/**
* Question Registry — typed schema for AskUserQuestion invocations across gstack.
*
* Purpose
* -------
* Every AskUserQuestion invocation is tagged with a stable question_id that maps
* to an entry in this registry. The registry is the substrate /plan-tune builds on:
* - Logging (question-log.jsonl) tags events with a registered id
* - Per-question preferences (question-preferences.json) are keyed by registered id
* - One-way door safety is declared here, not inferred from prose summaries
* - The psychographic signal map (scripts/psychographic-signals.ts) maps id → dimension delta
*
* Not every AskUserQuestion in gstack needs a registry entry right away. Skills
* often craft questions dynamically at runtime — the agent generates an ad-hoc id
* of the form `{skill}-{slug}` for those. The /plan-tune skill surfaces frequently-
* firing ad-hoc ids as candidates for registry promotion.
*
* v1 coverage target: the ~30-50 most-common recurring question categories across
* ship, review, office-hours, plan-ceo-review, plan-eng-review, plan-design-review,
* plan-devex-review, qa, investigate, and land-and-deploy. One-way doors 100%.
*
* Adding a new entry
* ------------------
* 1. Pick a kebab-case id of the form `{skill}-{what-it-asks-about}`.
* 2. Classify `door_type`:
* - `one-way` for destructive ops, architecture/data-model forks,
* scope-adds > 1 day CC effort, security/compliance choices.
* ALWAYS asked regardless of user preference.
* - `two-way` for everything else (can be auto-decided by explicit preference).
* 3. Pick the `category` that describes the question's shape.
* 4. Add an optional `signal_key` if this question's answer should nudge a
* specific psychographic dimension. The signal map in scripts/psychographic-
* signals.ts uses (id, user_choice) to look up the dimension delta.
* 5. `options` is a short list of stable option keys. UI labels can vary; keys
* must stay the same so preferences survive wording changes.
* 6. Run `bun test test/plan-tune.test.ts` to verify format + uniqueness.
*/
export type QuestionCategory =
| 'approval' // proceed/stop gate (e.g., "approve this plan?")
| 'clarification' // need more info to proceed
| 'routing' // which path to take (modes, strategies)
| 'cherry-pick' // opt-in scope decision (add/defer/skip)
| 'feedback-loop'; // inline tune: prompt, iteration feedback
export type DoorType = 'one-way' | 'two-way';
/**
* Stable keys for the most-common user choice patterns. UI labels can vary
* (e.g., "Add to plan" vs "Include in scope"); the stored choice is the key.
* Skills may emit custom keys for uncategorizable questions — those still log
* but don't get psychographic signal attribution.
*/
export type StandardOption =
| 'accept'
| 'reject'
| 'defer'
| 'skip'
| 'investigate'
| 'approve'
| 'deny'
| 'expand'
| 'hold'
| 'reduce'
| 'selective'
| 'fix-now'
| 'fix-later'
| 'ack-and-ship'
| 'false-positive'
| 'continue'
| 'rerun'
| 'stop';
export interface QuestionDef {
/** Stable kebab-case id: `{skill}-{semantic-description}` */
id: string;
/** Skill that owns this question (must match a gstack skill directory name) */
skill: string;
/** Shape of the question */
category: QuestionCategory;
/** Safety classification. one-way is ALWAYS asked regardless of preference */
door_type: DoorType;
/** Stable option keys (skills may emit keys outside this list; those are logged but untagged) */
options?: StandardOption[] | string[];
/** Optional key into scripts/psychographic-signals.ts for dimension attribution */
signal_key?: string;
/** One-line description for docs and /plan-tune profile output */
description: string;
}
/**
* QUESTIONS — initial v1 coverage of recurring question categories.
* Grouped by skill for readability. Maintained by hand.
*
* When adding new skills or question types, extend this object. The CI lint
* test/plan-tune.test.ts verifies format, uniqueness, and required fields.
*/
export const QUESTIONS = {
// -----------------------------------------------------------------------
// /ship — pre-landing review, deploy, PR creation
// -----------------------------------------------------------------------
'ship-release-pipeline-missing': {
id: 'ship-release-pipeline-missing',
skill: 'ship',
category: 'approval',
door_type: 'two-way',
options: ['accept', 'defer', 'skip'],
signal_key: 'distribution-care',
description: "New artifact added without CI/CD release pipeline — add now, defer to TODOs, or skip?",
},
'ship-test-failure-triage': {
id: 'ship-test-failure-triage',
skill: 'ship',
category: 'approval',
door_type: 'one-way',
options: ['fix-now', 'investigate', 'ack-and-ship'],
signal_key: 'test-discipline',
description: "Failing tests detected — fix before shipping or investigate root cause?",
},
'ship-pre-landing-review-fix': {
id: 'ship-pre-landing-review-fix',
skill: 'ship',
category: 'approval',
door_type: 'two-way',
options: ['fix-now', 'skip'],
signal_key: 'code-quality-care',
description: "Pre-landing review flagged an issue — fix now or ship as-is?",
},
'ship-greptile-comment-valid': {
id: 'ship-greptile-comment-valid',
skill: 'ship',
category: 'approval',
door_type: 'two-way',
options: ['fix-now', 'ack-and-ship', 'false-positive'],
signal_key: 'code-quality-care',
description: "A review bot flagged a valid issue — fix, ack and ship, or mark false positive?",
},
'ship-greptile-comment-false-positive': {
id: 'ship-greptile-comment-false-positive',
skill: 'ship',
category: 'approval',
door_type: 'two-way',
options: ['reply', 'fix-anyway', 'ignore'],
description: "A review bot comment looks like a false positive — reply to explain, fix anyway, or ignore silently?",
},
'ship-todos-create': {
id: 'ship-todos-create',
skill: 'ship',
category: 'approval',
door_type: 'two-way',
options: ['accept', 'skip'],
description: "No TODOS.md found — create a skeleton file now?",
},
'ship-todos-reorganize': {
id: 'ship-todos-reorganize',
skill: 'ship',
category: 'approval',
door_type: 'two-way',
options: ['accept', 'skip'],
signal_key: 'detail-preference',
description: "TODOS.md doesn't follow the recommended structure — reorganize now?",
},
'ship-changelog-voice-polish': {
id: 'ship-changelog-voice-polish',
skill: 'ship',
category: 'approval',
door_type: 'two-way',
options: ['accept', 'skip'],
signal_key: 'detail-preference',
description: "CHANGELOG entry could be polished for voice — apply edits?",
},
'ship-version-bump-tier': {
id: 'ship-version-bump-tier',
skill: 'ship',
category: 'routing',
door_type: 'two-way',
options: ['major', 'minor', 'patch'],
description: "Version bump: major, minor, or patch?",
},
// -----------------------------------------------------------------------
// /review — pre-landing code review
// -----------------------------------------------------------------------
'review-finding-fix': {
id: 'review-finding-fix',
skill: 'review',
category: 'approval',
door_type: 'two-way',
options: ['fix-now', 'ack-and-ship', 'false-positive'],
signal_key: 'code-quality-care',
description: "Review finding — fix now, ack and ship, or false positive?",
},
'review-sql-safety': {
id: 'review-sql-safety',
skill: 'review',
category: 'approval',
door_type: 'one-way',
options: ['fix-now', 'investigate'],
description: "Potential SQL injection / unsafe query — fix or investigate further?",
},
'review-llm-trust-boundary': {
id: 'review-llm-trust-boundary',
skill: 'review',
category: 'approval',
door_type: 'one-way',
options: ['fix-now', 'investigate'],
description: "LLM trust boundary violation — fix before merge?",
},
'review-gate-disposition': {
id: 'review-gate-disposition',
skill: 'review',
category: 'approval',
door_type: 'one-way',
options: ['restore', 'keep-justified', 'keep-other', 'leave-open'],
description: "Gate edit (test, threshold, CI or suppression relaxed) — restore the gate, keep it with a reason, or leave it open for a later human?",
},
// -----------------------------------------------------------------------
// /office-hours — YC diagnostic + builder brainstorm
// -----------------------------------------------------------------------
'office-hours-mode-goal': {
id: 'office-hours-mode-goal',
skill: 'office-hours',
category: 'routing',
door_type: 'two-way',
options: ['startup', 'intrapreneur', 'hackathon', 'oss-research', 'learning', 'fun'],
signal_key: 'session-mode',
description: "What's your goal with this session? (Sets mode: startup vs builder)",
},
'office-hours-premise-confirm': {
id: 'office-hours-premise-confirm',
skill: 'office-hours',
category: 'approval',
door_type: 'two-way',
options: ['accept', 'reject'],
description: "Premise check — agree or disagree?",
},
'office-hours-cross-model-run': {
id: 'office-hours-cross-model-run',
skill: 'office-hours',
category: 'approval',
door_type: 'two-way',
options: ['accept', 'skip'],
description: "Want a second-opinion cross-model review of your brainstorm?",
},
'office-hours-landscape-privacy-gate': {
id: 'office-hours-landscape-privacy-gate',
skill: 'office-hours',
category: 'approval',
door_type: 'one-way',
options: ['accept', 'skip'],
description: "Run a web search for landscape awareness? (Sends generalized terms to search provider.)",
},
'office-hours-approach-choose': {
id: 'office-hours-approach-choose',
skill: 'office-hours',
category: 'routing',
door_type: 'two-way',
options: ['minimal', 'ideal', 'creative'],
signal_key: 'scope-appetite',
description: "Which implementation approach? (minimal viable vs ideal architecture vs creative lateral)",
},
'office-hours-design-doc-approve': {
id: 'office-hours-design-doc-approve',
skill: 'office-hours',
category: 'approval',
door_type: 'two-way',
options: ['accept', 'revise', 'restart'],
description: "Approve the design doc, revise sections, or start over?",
},
// -----------------------------------------------------------------------
// /plan-ceo-review — scope & strategy
// -----------------------------------------------------------------------
'plan-ceo-review-mode': {
id: 'plan-ceo-review-mode',
skill: 'plan-ceo-review',
category: 'routing',
door_type: 'two-way',
options: ['expand', 'selective', 'hold', 'reduce'],
signal_key: 'scope-appetite',
description: "Review mode: push scope up, cherry-pick expansions, hold scope, or cut to minimum?",
},
'plan-ceo-review-expansion-proposal': {
id: 'plan-ceo-review-expansion-proposal',
skill: 'plan-ceo-review',
category: 'cherry-pick',
door_type: 'two-way',
options: ['accept', 'defer', 'skip'],
signal_key: 'scope-appetite',
description: "Scope expansion proposal — add to plan, defer to TODOs, or skip?",
},
'plan-ceo-review-premise-revise': {
id: 'plan-ceo-review-premise-revise',
skill: 'plan-ceo-review',
category: 'approval',
door_type: 'one-way',
options: ['revise', 'hold'],
description: "Cross-model challenged an agreed premise — revise or keep?",
},
'plan-ceo-review-outside-voice': {
id: 'plan-ceo-review-outside-voice',
skill: 'plan-ceo-review',
category: 'approval',
door_type: 'two-way',
options: ['accept', 'skip'],
description: "Get an outside-voice second opinion on the plan?",
},
'plan-ceo-review-promote-to-docs': {
id: 'plan-ceo-review-promote-to-docs',
skill: 'plan-ceo-review',
category: 'approval',
door_type: 'two-way',
options: ['accept', 'keep-local', 'skip'],
description: "Promote the CEO plan to docs/designs/ in the repo?",
},
// -----------------------------------------------------------------------
// /plan-eng-review — architecture & tests (required gate)
// -----------------------------------------------------------------------
'plan-eng-review-arch-finding': {
id: 'plan-eng-review-arch-finding',
skill: 'plan-eng-review',
category: 'approval',
door_type: 'one-way',
options: ['fix-now', 'defer', 'accept-risk'],
signal_key: 'architecture-care',
description: "Architecture finding — fix, defer, or accept the risk?",
},
'plan-eng-review-scope-reduce': {
id: 'plan-eng-review-scope-reduce',
skill: 'plan-eng-review',
category: 'routing',
door_type: 'two-way',
options: ['reduce', 'hold'],
signal_key: 'scope-appetite',
description: "Plan touches 8+ files — reduce scope or hold?",
},
'plan-eng-review-structure': {
id: 'plan-eng-review-structure',
skill: 'plan-eng-review',
category: 'routing',
door_type: 'two-way',
options: ['original-arrangement', 'smaller-arrangement'],
description: "Complexity gate — Original arrangement or Smaller arrangement (file/class layout only)?",
},
'plan-eng-review-test-gap': {
id: 'plan-eng-review-test-gap',
skill: 'plan-eng-review',
category: 'approval',
door_type: 'two-way',
options: ['add-test', 'defer', 'skip'],
signal_key: 'test-discipline',
description: "Test gap identified — add now, defer, or skip?",
},
'plan-eng-review-outside-voice': {
id: 'plan-eng-review-outside-voice',
skill: 'plan-eng-review',
category: 'approval',
door_type: 'two-way',
options: ['accept', 'skip'],
description: "Get an outside-voice second opinion on the plan?",
},
'plan-eng-review-todo-add': {
id: 'plan-eng-review-todo-add',
skill: 'plan-eng-review',
category: 'cherry-pick',
door_type: 'two-way',
options: ['accept', 'skip', 'build-now'],
description: "Proposed TODO item — add to TODOs, skip, or build in this PR?",
},
// -----------------------------------------------------------------------
// /plan-design-review — UI/UX plan audit
// -----------------------------------------------------------------------
'plan-design-review-mode': {
id: 'plan-design-review-mode',
skill: 'plan-design-review',
category: 'routing',
door_type: 'two-way',
options: ['expand', 'polish', 'triage'],
signal_key: 'design-care',
description: "Design review depth: expand for competitive edge, polish every touchpoint, or triage critical gaps?",
},
'plan-design-review-fix': {
id: 'plan-design-review-fix',
skill: 'plan-design-review',
category: 'approval',
door_type: 'two-way',
options: ['fix-now', 'defer', 'skip'],
signal_key: 'design-care',
description: "Design issue flagged — fix now, defer to TODOs, or skip?",
},
// -----------------------------------------------------------------------
// /plan-devex-review — developer experience plan audit
// -----------------------------------------------------------------------
'plan-devex-review-persona': {
id: 'plan-devex-review-persona',
skill: 'plan-devex-review',
category: 'clarification',
door_type: 'two-way',
description: "Who is your target developer? (Determines persona for review.)",
},
'plan-devex-review-mode': {
id: 'plan-devex-review-mode',
skill: 'plan-devex-review',
category: 'routing',
door_type: 'two-way',
options: ['expand', 'polish', 'triage'],
signal_key: 'devex-care',
description: "DX review depth: expand for competitive advantage, polish every touchpoint, or triage critical gaps?",
},
'plan-devex-review-friction-fix': {
id: 'plan-devex-review-friction-fix',
skill: 'plan-devex-review',
category: 'approval',
door_type: 'two-way',
options: ['fix-now', 'defer', 'skip'],
signal_key: 'devex-care',
description: "Friction point in the developer journey — fix now, defer, or skip?",
},
// -----------------------------------------------------------------------
// /qa — QA testing
// -----------------------------------------------------------------------
'qa-bug-fix-scope': {
id: 'qa-bug-fix-scope',
skill: 'qa',
category: 'approval',
door_type: 'two-way',
options: ['fix-now', 'defer', 'skip'],
signal_key: 'code-quality-care',
description: "Bug found during QA — fix now, defer, or skip?",
},
'qa-tier': {
id: 'qa-tier',
skill: 'qa',
category: 'routing',
door_type: 'two-way',
options: ['quick', 'standard', 'deep'],
description: "QA tier: quick (critical/high only), standard (+medium), or deep (+low)?",
},
// -----------------------------------------------------------------------
// /investigate — root-cause debugging
// -----------------------------------------------------------------------
'investigate-hypothesis-confirm': {
id: 'investigate-hypothesis-confirm',
skill: 'investigate',
category: 'approval',
door_type: 'two-way',
options: ['accept', 'reject', 'refine'],
description: "Root-cause hypothesis — accept, reject, or refine before proceeding to fix?",
},
'investigate-fix-apply': {
id: 'investigate-fix-apply',
skill: 'investigate',
category: 'approval',
door_type: 'one-way',
options: ['accept', 'reject'],
description: "Apply the proposed fix?",
},
// -----------------------------------------------------------------------
// /land-and-deploy — merge + deploy + verify
// -----------------------------------------------------------------------
'land-and-deploy-merge-confirm': {
id: 'land-and-deploy-merge-confirm',
skill: 'land-and-deploy',
category: 'approval',
door_type: 'one-way',
options: ['accept', 'reject'],
signal_key: 'decision-autonomy',
description: "Merge this PR to base branch?",
},
'land-and-deploy-rollback': {
id: 'land-and-deploy-rollback',
skill: 'land-and-deploy',
category: 'approval',
door_type: 'one-way',
options: ['accept', 'reject'],
signal_key: 'decision-autonomy',
description: "Canary detected regressions — roll back the deploy?",
},
'land-and-deploy-ci-override': {
id: 'land-and-deploy-ci-override',
skill: 'land-and-deploy',
category: 'approval',
door_type: 'one-way',
options: ['accept', 'reject'],
description: "Merge this head while these named non-required CI checks are red or pending?",
},
'land-and-deploy-no-ci-confirm': {
id: 'land-and-deploy-no-ci-confirm',
skill: 'land-and-deploy',
category: 'approval',
door_type: 'one-way',
options: ['accept', 'reject'],
description: "No CI ran on this head — merge it anyway?",
},
// -----------------------------------------------------------------------
// /cso — security audit
// -----------------------------------------------------------------------
'cso-global-scan-approval': {
id: 'cso-global-scan-approval',
skill: 'cso',
category: 'approval',
door_type: 'one-way',
options: ['accept', 'deny'],
description: "Run a global security scan? (Scans files outside this branch.)",
},
'cso-finding-fix': {
id: 'cso-finding-fix',
skill: 'cso',
category: 'approval',
door_type: 'one-way',
options: ['fix-now', 'defer', 'accept-risk'],
description: "Security finding — fix, defer to TODOs, or accept the risk?",
},
// -----------------------------------------------------------------------
// /gstack-upgrade — version upgrade
// -----------------------------------------------------------------------
'gstack-upgrade-inline': {
id: 'gstack-upgrade-inline',
skill: 'gstack-upgrade',
category: 'approval',
door_type: 'two-way',
options: ['yes-upgrade', 'always-auto', 'not-now', 'never-ask'],
description: "Upgrade gstack now? (Also: always auto-upgrade, snooze, or disable the prompt.)",
},
// -----------------------------------------------------------------------
// Preamble one-time prompts (telemetry, proactive, routing)
// -----------------------------------------------------------------------
'preamble-telemetry-consent': {
id: 'preamble-telemetry-consent',
skill: 'preamble',
category: 'approval',
door_type: 'two-way',
options: ['community', 'anonymous', 'off'],
description: "Share usage data with gstack? community (recommended) / anonymous / off",
},
'preamble-proactive-behavior': {
id: 'preamble-proactive-behavior',
skill: 'preamble',
category: 'approval',
door_type: 'two-way',
options: ['core', 'all', 'off'],
description: "Let gstack proactively suggest skills based on conversation context? core (the four core skills, default) / all / off",
},
'preamble-routing-injection': {
id: 'preamble-routing-injection',
skill: 'preamble',
category: 'approval',
door_type: 'two-way',
options: ['accept', 'decline'],
description: "Add gstack skill routing rules to CLAUDE.md?",
},
'preamble-vendored-migration': {
id: 'preamble-vendored-migration',
skill: 'preamble',
category: 'approval',
door_type: 'two-way',
options: ['accept', 'keep-vendored'],
description: "This repo has vendored gstack (deprecated) — migrate to team mode?",
},
'preamble-completeness-intro': {
id: 'preamble-completeness-intro',
skill: 'preamble',
category: 'approval',
door_type: 'two-way',
options: ['accept', 'skip'],
description: "Open the Boil-the-Lake essay in your browser? (one-time intro)",
},
'preamble-cross-project-learnings': {
id: 'preamble-cross-project-learnings',
skill: 'preamble',
category: 'approval',
door_type: 'two-way',
options: ['accept', 'reject'],
description: "Enable cross-project learnings search? (local only, helpful for solo devs)",
},
// -----------------------------------------------------------------------
// /plan-tune — the skill itself
// -----------------------------------------------------------------------
'plan-tune-enable-setup': {
id: 'plan-tune-enable-setup',
skill: 'plan-tune',
category: 'approval',
door_type: 'two-way',
options: ['accept', 'skip'],
description: "Question tuning is off — enable it and set up your profile?",
},
'plan-tune-declared-dimension': {
id: 'plan-tune-declared-dimension',
skill: 'plan-tune',
category: 'clarification',
door_type: 'two-way',
description: "Self-declaration question (one per dimension during /plan-tune setup)",
},
'plan-tune-confirm-mutation': {
id: 'plan-tune-confirm-mutation',
skill: 'plan-tune',
category: 'approval',
door_type: 'two-way',
options: ['accept', 'reject'],
description: "Confirm profile change before writing (user sovereignty gate for free-form edits)",
},
// -----------------------------------------------------------------------
// /autoplan — sequential auto-review
// -----------------------------------------------------------------------
'autoplan-taste-decision': {
id: 'autoplan-taste-decision',
skill: 'autoplan',
category: 'approval',
door_type: 'two-way',
options: ['accept', 'override', 'investigate'],
description: "Autoplan surfaced a taste decision at the final gate — accept, override, or investigate?",
},
'autoplan-user-challenge': {
id: 'autoplan-user-challenge',
skill: 'autoplan',
category: 'approval',
door_type: 'one-way',
options: ['accept', 'reject', 'revise'],
description: "Both models agree your direction should change — accept, reject, or revise the plan?",
},
} as const satisfies Record<string, QuestionDef>;
export type RegisteredQuestionId = keyof typeof QUESTIONS;
/**
* Runtime lookup — returns undefined for ad-hoc question_ids (not registered).
* Ad-hoc ids still log; they just don't get psychographic signal attribution.
*/
export function getQuestion(id: string): QuestionDef | undefined {
return (QUESTIONS as Record<string, QuestionDef>)[id];
}
/** Get all registered one-way door question ids (used by sensitivity checker) */
export function getOneWayDoorIds(): Set<string> {
return new Set(
Object.values(QUESTIONS as Record<string, QuestionDef>)
.filter((q) => q.door_type === 'one-way')
.map((q) => q.id),
);
}
/** All registered question ids, for CI completeness checks */
export function getAllRegisteredIds(): Set<string> {
return new Set(Object.keys(QUESTIONS));
}
/** Registry stats, for /plan-tune stats */
export function getRegistryStats() {
const all = Object.values(QUESTIONS as Record<string, QuestionDef>);
const bySkill: Record<string, number> = {};
const byCategory: Record<string, number> = {};
let oneWay = 0;
let twoWay = 0;
for (const q of all) {
bySkill[q.skill] = (bySkill[q.skill] ?? 0) + 1;
byCategory[q.category] = (byCategory[q.category] ?? 0) + 1;
if (q.door_type === 'one-way') oneWay++;
else twoWay++;
}
return {
total: all.length,
one_way: oneWay,
two_way: twoWay,
by_skill: bySkill,
by_category: byCategory,
};
}