rcf-lite 0.27.0 → 0.28.0

package/rcf/test-suites/ts-192.json

@@ -0,0 +1,37 @@
+{
+  "createdAt": "2026-09-16T17:23:12Z",
+  "updatedAt": "2026-09-16T17:23:12Z",
+  "purpose": "Cover AC-15901-1 (submit --yes files entries under the ambient gh login, stamps submitted with issueUrl and dedupe, prints one line per entry, exit 0) and AC-15901-2 (submit without --yes on a non-TTY exits 2 naming --yes; env passed to gh has no synthesised GH_TOKEN or GITHUB_TOKEN key).",
+  "testLevel": "integration",
+  "acIds": [
+    "AC-15901-1",
+    "AC-15901-2"
+  ],
+  "id": "TS-192",
+  "usId": "US-15901",
+  "title": "Slice 4 (FBS-183): submit --yes files under the reporter's ambient gh login and refuses on a non-TTY without --yes; the CLI never synthesises GH_TOKEN or GITHUB_TOKEN",
+  "testCases": [
+    {
+      "id": "TC-192-submit-yes-happy-path",
+      "acId": "AC-15901-1",
+      "description": "Cover AC-15901-1 via the CLI test: two pending entries, zero-hit search, distinct URLs returned; both entries fold to status submitted with issueUrl and dedupe: new; stdout carries two '<id> -> <url> (new)' lines.",
+      "status": "pending",
+      "testPointer": "test/cli/feedback-submit.test.js::AC-15901-1: submit --yes with zero-hit search creates each entry, marks submitted, prints URL"
+    },
+    {
+      "id": "TC-192-submit-refuses-without-yes",
+      "acId": "AC-15901-2",
+      "description": "Cover AC-15901-2 (refusal arm) via the CLI test: submit without --yes on a non-TTY child exits 2, stderr names --yes as required, and no gh call is made.",
+      "status": "pending",
+      "testPointer": "test/cli/feedback-submit.test.js::AC-15901-2: submit without --yes on a non-TTY exits 2, names --yes, no gh call is made"
+    },
+    {
+      "id": "TC-192-submit-no-token-synthesised",
+      "acId": "AC-15901-2",
+      "description": "Cover AC-15901-2 (env arm) via the CLI test: launch with a stripped env (no GH_TOKEN, no GITHUB_TOKEN); the fake ghIssueCreate call records ghToken:null and githubToken:null so the CLI never synthesised either.",
+      "status": "pending",
+      "testPointer": "test/cli/feedback-submit.test.js::AC-15901-2: the CLI does not synthesise GH_TOKEN or GITHUB_TOKEN before calling gh"
+    }
+  ],
+  "status": "draft"
+}

package/rcf/test-suites/ts-193.json

@@ -0,0 +1,60 @@
+{
+  "createdAt": "2026-09-16T17:23:12Z",
+  "updatedAt": "2026-09-16T17:23:12Z",
+  "purpose": "Cover AC-15902-1 (label pre-check drops labels the destination repo does not carry and stamps droppedLabels[] on the entry state), AC-15902-2 (scripts/bootstrap-feedback-labels.mjs idempotently creates the six labels), AC-15902-3 (rendered issue title carries the prefix and the body carries the fingerprint on its own line and inside an HTML comment) and AC-15902-4 (the six-label catalogue is exported from src/feedback/labels.js and a grep test refuses bare literals for these names outside the allowed consumers).",
+  "testLevel": "integration",
+  "acIds": [
+    "AC-15902-1",
+    "AC-15902-2",
+    "AC-15902-3",
+    "AC-15902-4"
+  ],
+  "id": "TS-193",
+  "usId": "US-15902",
+  "title": "Slice 4 (FBS-183): label pre-check + bootstrap script + title/fingerprint handles + label-catalogue single-source guard",
+  "testCases": [
+    {
+      "id": "TC-193-label-precheck-drops-missing",
+      "acId": "AC-15902-1",
+      "description": "Cover AC-15902-1 via the CLI test: the fake labelList returns { rcf-feedback, severity:major } but not area:core; submit creates the issue with the reduced label set and stamps droppedLabels: ['area:core'] on the entry state.",
+      "status": "pending",
+      "testPointer": "test/cli/feedback-submit.test.js::AC-15902-1: submit drops labels the destination does not carry and records droppedLabels"
+    },
+    {
+      "id": "TC-193-bootstrap-creates-six",
+      "acId": "AC-15902-2",
+      "description": "Cover AC-15902-2 (first run) via the unit test: with the fake labelList returning names:[], the bootstrap script creates all six labels via ghLabelCreate with descriptions and colours.",
+      "status": "pending",
+      "testPointer": "test/feedback/bootstrap-labels.test.js::AC-15902-2: bootstrap creates every missing label on the first run"
+    },
+    {
+      "id": "TC-193-bootstrap-idempotent-full",
+      "acId": "AC-15902-2",
+      "description": "Cover AC-15902-2 (idempotency) via the unit test: with the fake labelList returning every catalogue label, the bootstrap script makes zero ghLabelCreate calls.",
+      "status": "pending",
+      "testPointer": "test/feedback/bootstrap-labels.test.js::AC-15902-2: bootstrap makes zero create calls when every label is already present"
+    },
+    {
+      "id": "TC-193-bootstrap-partial-subset",
+      "acId": "AC-15902-2",
+      "description": "Cover AC-15902-2 (partial arm) via the unit test: with only two of the six labels present, the bootstrap script creates the missing four (area:blueprint, area:core, severity:major, severity:minor).",
+      "status": "pending",
+      "testPointer": "test/feedback/bootstrap-labels.test.js::AC-15902-2: bootstrap creates only the missing subset (partial second run)"
+    },
+    {
+      "id": "TC-193-title-prefix-and-fingerprint-twin",
+      "acId": "AC-15902-3",
+      "description": "Cover AC-15902-3 via the CLI test: the ghIssueCreate call sees a title starting with [rcf-lite] and a body carrying the fingerprint on its own line and inside an HTML comment (asserted end-to-end in the render unit test at test/feedback/render.test.js and reasserted at submit time here).",
+      "status": "pending",
+      "testPointer": "test/cli/feedback-submit.test.js::AC-15902-3: rendered title prefix and body fingerprint twin are on the create call"
+    },
+    {
+      "id": "TC-193-labels-catalogue-single-source",
+      "acId": "AC-15902-4",
+      "description": "Cover AC-15902-4 via the unit test: FEEDBACK_LABELS is the six-label frozen catalogue exported from src/feedback/labels.js, and a scanner walks src/, scripts/, bin/ refusing any bare literal for these names outside labels.js, its tests, the bootstrap script and render.js's re-export shim.",
+      "status": "pending",
+      "testPointer": "test/feedback/labels-catalogue.test.js::AC-15902-4: no bare literal for any catalogue label appears outside labels.js and its allowed consumers"
+    }
+  ],
+  "status": "draft"
+}

package/rcf/test-suites/ts-194.json

@@ -0,0 +1,67 @@
+{
+  "createdAt": "2026-09-16T17:23:12Z",
+  "updatedAt": "2026-09-16T17:23:12Z",
+  "purpose": "Cover AC-16001-1 (four preflight branches each routing to a bundle with a distinct one-line message), AC-16001-2 (create/comment failure retries once without labels and then bundles that entry, other entries continue, exit 0 when every entry ended submitted or bundled), AC-16001-3 (bundled entries are terminal for the ask loop: list default hides them, list --all reports status bundled, submit picks up only pending entries on a subsequent run), and AC-16001-4 (destination unresolved case writes an unresolved-slug bundle with publisher contact on the same line as the outbox path, no gh call for that entry, exit 0).",
+  "testLevel": "integration",
+  "acIds": [
+    "AC-16001-1",
+    "AC-16001-2",
+    "AC-16001-3",
+    "AC-16001-4"
+  ],
+  "id": "TS-194",
+  "usId": "US-16001",
+  "title": "Slice 4 (FBS-183): four preflight cases + retry-then-bundle + terminal bundled entries + unresolved-destination bundle",
+  "testCases": [
+    {
+      "id": "TC-194-preflight-gh-missing",
+      "acId": "AC-16001-1",
+      "description": "Cover AC-16001-1 case (1) via the CLI test: onPath fake returns { present: false }; the entry lands in .rcf/feedback/outbox/<ISO>-stravica-rcf-lite[-<id>].md; the bundle Reason not filed line names gh; stdout carries the outbox path and the issues/new URL on one line; entry state is bundled; exit 0.",
+      "status": "pending",
+      "testPointer": "test/cli/feedback-submit.test.js::AC-16001-1a: gh missing on PATH routes to bundle"
+    },
+    {
+      "id": "TC-194-preflight-auth-off",
+      "acId": "AC-16001-1",
+      "description": "Cover AC-16001-1 case (2) via the CLI test: auth fake returns { authed: false }; bundle reason names 'run gh auth login'; entry state is bundled; exit 0.",
+      "status": "pending",
+      "testPointer": "test/cli/feedback-submit.test.js::AC-16001-1b: gh auth status non-zero routes to bundle"
+    },
+    {
+      "id": "TC-194-preflight-private-none",
+      "acId": "AC-16001-1",
+      "description": "Cover AC-16001-1 case (3) via the CLI test: repoView returns visibility PRIVATE and viewerPermission NONE; bundle reason names 'no access to private repo'; exit 0.",
+      "status": "pending",
+      "testPointer": "test/cli/feedback-submit.test.js::AC-16001-1c: private repo with viewerPermission NONE routes to bundle"
+    },
+    {
+      "id": "TC-194-preflight-issues-disabled",
+      "acId": "AC-16001-1",
+      "description": "Cover AC-16001-1 case (4) via the CLI test: repoView returns hasIssuesEnabled false; bundle reason names 'issues are disabled on <repo>'; exit 0.",
+      "status": "pending",
+      "testPointer": "test/cli/feedback-submit.test.js::AC-16001-1d: hasIssuesEnabled false routes to bundle"
+    },
+    {
+      "id": "TC-194-retry-without-labels-then-bundle",
+      "acId": "AC-16001-2",
+      "description": "Cover AC-16001-2 via the CLI test: create fake returns ratelimit twice for entry A, twice for entry B, then success for entry C; A and B end bundled, C ends submitted; two bundle files under outbox (one per bundled entry); exit 0.",
+      "status": "pending",
+      "testPointer": "test/cli/feedback-submit.test.js::AC-16001-2: create 429 retries without labels, still fails, bundles that entry; another submits"
+    },
+    {
+      "id": "TC-194-bundled-terminal-for-ask",
+      "acId": "AC-16001-3",
+      "description": "Cover AC-16001-3 via the CLI test: after a preflight-forced bundle for entry X, list --json (default pending) omits X; list --all --json includes X with status bundled; a subsequent submit --yes with a working fake only creates for the still-pending entry (bundled entries are terminal, not re-picked-up).",
+      "status": "pending",
+      "testPointer": "test/cli/feedback-submit.test.js::AC-16001-3: list default hides bundled; submit <id> re-attempts one bundled entry"
+    },
+    {
+      "id": "TC-194-unresolved-destination-bundle",
+      "acId": "AC-16001-4",
+      "description": "Cover AC-16001-4 via the CLI test: an applied library whose registry entry carries neither issuesRepo nor a derivable github source, plus publisher.contact 'orphan-owners@example.com'; submit writes .rcf/feedback/outbox/<ISO>-unresolved[-<id>].md, prints publisher.contact on the same line as the outbox path, makes no gh create/comment/search call for that entry, entry state is bundled, exit 0.",
+      "status": "pending",
+      "testPointer": "test/cli/feedback-submit.test.js::AC-16001-4: unresolved destination writes an unresolved-slug bundle with publisher contact, no gh call"
+    }
+  ],
+  "status": "draft"
+}

package/rcf/test-suites/ts-195.json

@@ -0,0 +1,52 @@
+{
+  "createdAt": "2026-09-16T19:20:00Z",
+  "updatedAt": "2026-09-16T19:20:00Z",
+  "purpose": "Cover AC-16101-1 (shouldAsk applies the design-3.5 quiet rule: silent unless not-opted-out + pending + not-asked-this-session + stop-hook-inactive AND one of ask-now/older-than-quietMinutes/queue-complete/carried-over), AC-16101-2 (Stop on Claude Code exits 2 with the ask on stderr; Stop on Codex emits { decision: 'block', reason } on stdout with exit 0; the asked ledger is appended in both cases) and AC-16101-3 (a same-session second Stop is silent, a fresh session_id re-asks, and a Stop with stop_hook_active is silent even on a fresh session).",
+  "testLevel": "integration",
+  "acIds": [
+    "AC-16101-1",
+    "AC-16101-2",
+    "AC-16101-3"
+  ],
+  "id": "TS-195",
+  "usId": "US-16101",
+  "title": "Slice 5 (FBS-184): quiet-rule truth table plus per-harness Stop emit and same-session ledger idempotency",
+  "testCases": [
+    {
+      "id": "TC-195-quiet-rule-truth-table",
+      "acId": "AC-16101-1",
+      "description": "Cover AC-16101-1 via the unit test: shouldAsk is total, deterministic and pure; a table walks opt-out (file/env), pending count, asked-this-session, stop-hook-active, ask-now, age-vs-quietMinutes (14 min: silent; 15 min: ask; 60 min: ask; quietMinutes 0/60 boundaries), queue-complete and carried-over rows and asserts the expected 'ask'/'silent' verdict on each; buildAskReason names all four next-step verbs and the do-not-ask clause.",
+      "status": "pending",
+      "testPointer": "test/feedback/hook-quiet-rule.test.js::AC-16101-1: shouldAsk is ask when the newest pending entry crosses quietMinutes"
+    },
+    {
+      "id": "TC-195-hook-stop-claude-code",
+      "acId": "AC-16101-2",
+      "description": "Cover AC-16101-2 (Claude Code half) via the CLI test: rcf feedback hook stop --harness claude-code with one pending entry and a mock Stop payload exits 2, writes the reason (all four verbs + do-not-ask) to stderr, writes nothing on stdout, and appends exactly one asked record to .rcf/feedback/state.json for the payload session_id.",
+      "status": "pending",
+      "testPointer": "test/cli/feedback-hook.test.js::AC-16101-2: Stop on Claude Code exits 2 with the ask on stderr and appends ledger"
+    },
+    {
+      "id": "TC-195-hook-stop-codex",
+      "acId": "AC-16101-2",
+      "description": "Cover AC-16101-2 (Codex half) via the CLI test: rcf feedback hook stop --harness codex emits stdout JSON parseable as { decision: 'block', reason: <same clause> }, exits 0, writes nothing on stderr, and appends exactly one asked record to state.json for the payload session_id.",
+      "status": "pending",
+      "testPointer": "test/cli/feedback-hook.test.js::AC-16101-2: Stop on Codex emits stdout JSON block, exit 0, ledger appended"
+    },
+    {
+      "id": "TC-195-hook-same-session-silent-then-fresh-reasks",
+      "acId": "AC-16101-3",
+      "description": "Cover AC-16101-3 via the CLI test: two Stop invocations with the same session_id in sequence produce ask (exit 2) then silent (exit 0, no stderr); a third invocation with a fresh session_id re-asks (exit 2) because the pending entry is carried over; state.json ends with exactly two asked records for the two distinct sessionIds.",
+      "status": "pending",
+      "testPointer": "test/cli/feedback-hook.test.js::AC-16101-3: same-session second Stop is silent; a fresh session_id re-asks"
+    },
+    {
+      "id": "TC-195-hook-stop-hook-active-silent",
+      "acId": "AC-16101-3",
+      "description": "Cover AC-16101-3 (stop_hook_active branch) via the CLI test: a Stop payload with stop_hook_active: true and a fresh session_id and a pending --ask-now entry still exits 0 with no reason emitted; the loop-guard fires even when every other trigger would.",
+      "status": "pending",
+      "testPointer": "test/cli/feedback-hook.test.js::AC-16101-3: Stop with stop_hook_active is silent even on a fresh session"
+    }
+  ],
+  "status": "draft"
+}

package/rcf/test-suites/ts-196.json

@@ -0,0 +1,58 @@
+{
+  "createdAt": "2026-09-16T19:20:00Z",
+  "updatedAt": "2026-09-16T19:20:00Z",
+  "purpose": "Cover AC-16102-1 (rcf feedback opt-out writes rcf/feedback-settings.json ask: false with the defaults merged, the hook returns silent under ask: false, and add/preview keep working) and AC-16102-2 (RCF_FEEDBACK_DISABLE=1 makes add a no-op that prints 'feedback disabled by env' and writes nothing; RCF_FEEDBACK_ASK=0 silences the hook while leaving add working; precedence order env DISABLE > env ASK=0 > file ask false > file ask true).",
+  "testLevel": "integration",
+  "acIds": [
+    "AC-16102-1",
+    "AC-16102-2"
+  ],
+  "id": "TS-196",
+  "usId": "US-16102",
+  "title": "Slice 5 (FBS-184): rcf feedback opt-out / opt-in write ask false / true; env DISABLE and env ASK override the file with the documented precedence",
+  "testCases": [
+    {
+      "id": "TC-196-optout-writes-settings-and-silences-hook",
+      "acId": "AC-16102-1",
+      "description": "Cover AC-16102-1 via the CLI test: rcf feedback opt-out on a fresh project writes rcf/feedback-settings.json with { settingsVersion: 1, ask: false, quietMinutes: 15, redaction: { allowHosts: [] } }; a subsequent Stop hook on a pending --ask-now entry exits 0 silently; add and preview keep working under ask: false.",
+      "status": "pending",
+      "testPointer": "test/cli/feedback-opt-out.test.js::AC-16102-1: opt-out writes ask: false and preserves defaults; the hook goes silent"
+    },
+    {
+      "id": "TC-196-optin-restores-ask-true",
+      "acId": "AC-16102-1",
+      "description": "Cover AC-16102-1 (round-trip) via the CLI test: rcf feedback opt-in after an opt-out flips ask back to true and preserves quietMinutes and redaction.allowHosts on the file.",
+      "status": "pending",
+      "testPointer": "test/cli/feedback-opt-out.test.js::AC-16102-1: opt-in restores ask true and preserves other fields"
+    },
+    {
+      "id": "TC-196-env-disable-no-ops-add",
+      "acId": "AC-16102-2",
+      "description": "Cover AC-16102-2 (DISABLE branch) via the CLI test: rcf feedback add under RCF_FEEDBACK_DISABLE=1 prints exactly 'feedback disabled by env' on stdout, exits 0 and writes nothing under .rcf/feedback/.",
+      "status": "pending",
+      "testPointer": "test/cli/feedback-opt-out.test.js::AC-16102-2: RCF_FEEDBACK_DISABLE=1 makes `add` a no-op that prints the disabled line"
+    },
+    {
+      "id": "TC-196-env-ask-silences-hook-only",
+      "acId": "AC-16102-2",
+      "description": "Cover AC-16102-2 (ASK=0 branch) via the CLI test: with ask: true on the file, rcf feedback add works normally; rcf feedback hook stop under RCF_FEEDBACK_ASK=0 exits 0 silently on a pending --ask-now entry.",
+      "status": "pending",
+      "testPointer": "test/cli/feedback-opt-out.test.js::AC-16102-2: RCF_FEEDBACK_ASK=0 keeps add working, silences the hook"
+    },
+    {
+      "id": "TC-196-precedence-order",
+      "acId": "AC-16102-2",
+      "description": "Cover AC-16102-2 (precedence) via the CLI test: the same fixture with a pending --ask-now entry walks four combinations (no-env + file ask:true -> ask; file ask:false -> silent; file ask:true + env ASK=0 -> silent; env DISABLE -> silent) so the documented env-DISABLE > env-ASK > file precedence is asserted end-to-end.",
+      "status": "pending",
+      "testPointer": "test/cli/feedback-opt-out.test.js::AC-16102-2: env DISABLE > env ASK=0 > file ask false > file ask true (precedence)"
+    },
+    {
+      "id": "TC-196-status-reports-optout-source",
+      "acId": "AC-16102-2",
+      "description": "Cover AC-16102-2 (surfacing) via the CLI test: rcf feedback status --json reports optOutSource='file:rcf/feedback-settings.json' after opt-out; the same JSON call under env ASK=0 reports optOutSource='env:RCF_FEEDBACK_ASK=0'; under env DISABLE it reports 'env:RCF_FEEDBACK_DISABLE'.",
+      "status": "pending",
+      "testPointer": "test/cli/feedback-opt-out.test.js::AC-16102-2: status reports the opt-out source verbatim"
+    }
+  ],
+  "status": "draft"
+}

package/rcf/test-suites/ts-197.json

@@ -0,0 +1,66 @@
+{
+  "createdAt": "2026-09-16T19:20:00Z",
+  "updatedAt": "2026-09-17T03:30:00Z",
+  "purpose": "Cover AC-16103-1 (rcf feedback hook session-end writes a byte-idempotent outbox bundle for the pending set and completes in well under the shared Claude Code 1.5s SessionEnd budget), AC-16103-2 (rcf feedback hook session-start on Claude Code prints a single carry-over context line; on Codex emits the additionalContext JSON shape; state.json is not mutated on session-start; with no carried-over entries the hook is silent) and AC-16103-3 (defer means \"not now, ask again next session\": deferredUntilSession entries carried over from a prior sessionId return to pending on SessionStart and on Stop; idempotent per session).",
+  "testLevel": "integration",
+  "acIds": [
+    "AC-16103-1",
+    "AC-16103-2",
+    "AC-16103-3"
+  ],
+  "id": "TS-197",
+  "usId": "US-16103",
+  "title": "Slice 5 (FBS-184): SessionEnd flushes a bundle idempotently, SessionStart re-surfaces a carried-over ask per harness, and defer requeues on the next session",
+  "testCases": [
+    {
+      "id": "TC-197-session-end-writes-idempotent-bundle",
+      "acId": "AC-16103-1",
+      "description": "Cover AC-16103-1 via the CLI test: rcf feedback hook session-end with one pending entry writes a single .rcf/feedback/outbox/<ISO>-session-end.md file with the design section 4.2 header; a re-run with the same pending set does not create a second file (byte-idempotent); the two-call round trip completes in well under the SessionEnd budget.",
+      "status": "pending",
+      "testPointer": "test/cli/feedback-hook.test.js::AC-16103-1: SessionEnd writes one bundle and is byte-idempotent on a re-run"
+    },
+    {
+      "id": "TC-197-session-start-claude-code-line",
+      "acId": "AC-16103-2",
+      "description": "Cover AC-16103-2 (Claude Code shape) via the CLI test: rcf feedback hook session-start --harness claude-code with a pending entry recorded under a different sessionId prints the exact carry-over line naming the count and citing RULE 17 to stdout; exit 0; state.json is not created (the ledger is set on Stop, not on session-start).",
+      "status": "pending",
+      "testPointer": "test/cli/feedback-hook.test.js::AC-16103-2: SessionStart on Claude Code prints the carry-over line for a new session"
+    },
+    {
+      "id": "TC-197-session-start-codex-additional-context",
+      "acId": "AC-16103-2",
+      "description": "Cover AC-16103-2 (Codex shape) via the CLI test: rcf feedback hook session-start --harness codex emits a stdout JSON with additionalContext carrying the same carry-over line.",
+      "status": "pending",
+      "testPointer": "test/cli/feedback-hook.test.js::AC-16103-2: SessionStart on Codex emits the additionalContext JSON shape"
+    },
+    {
+      "id": "TC-197-session-start-silent-when-nothing-carried-over",
+      "acId": "AC-16103-2",
+      "description": "Cover AC-16103-2 (silence branch) via the CLI test: rcf feedback hook session-start on a project with no pending entries writes nothing on stdout and exits 0.",
+      "status": "pending",
+      "testPointer": "test/cli/feedback-hook.test.js::AC-16103-2: SessionStart with no carried-over entries is silent"
+    },
+    {
+      "id": "TC-197-session-start-requeues-deferred-then-stop-asks",
+      "acId": "AC-16103-3",
+      "description": "Cover AC-16103-3 (SessionStart-path requeue) via the CLI test: add one entry and defer it in session A; run rcf feedback hook session-start --harness claude-code with session_id B; the entry is written back to pending (a { status: pending } state line appended, no sessionId field so the fold preserves A) and rcf feedback list shows it as pending; the stdout prints the carry-over line naming the count and RULE 17; a subsequent rcf feedback hook stop --harness claude-code with session_id B exits 2 with the ask on stderr and appends exactly one asked record for session B.",
+      "status": "pending",
+      "testPointer": "test/cli/feedback-hook.test.js::AC-16103-3: SessionStart requeues a deferred entry from a prior session and Stop asks in the new session"
+    },
+    {
+      "id": "TC-197-stop-only-path-requeues-deferred",
+      "acId": "AC-16103-3",
+      "description": "Cover AC-16103-3 (Stop-only fallback) via the CLI test: add one entry and defer it in session A; skip the SessionStart hook entirely and run rcf feedback hook stop --harness claude-code with session_id B directly; the Stop hook requeues the deferred entry back to pending, exits 2 with the ask on stderr and appends one asked record for session B (the carried-over trigger fires the quiet rule regardless of age).",
+      "status": "pending",
+      "testPointer": "test/cli/feedback-hook.test.js::AC-16103-3: Stop without a prior SessionStart still requeues a deferred entry and asks"
+    },
+    {
+      "id": "TC-197-session-start-idempotent-same-session",
+      "acId": "AC-16103-3",
+      "description": "Cover AC-16103-3 (idempotency per session) via the CLI test: add one entry and defer it in session A; run rcf feedback hook session-start --harness claude-code with session_id A (same as the defer's session); no requeue transition is written and stdout is empty. A second SessionStart in session B requeues once; a third SessionStart also in session B is a no-op (no new transition, silent stdout).",
+      "status": "pending",
+      "testPointer": "test/cli/feedback-hook.test.js::AC-16103-3: SessionStart is a no-op when the deferred session id matches the incoming session id"
+    }
+  ],
+  "status": "draft"
+}

package/rcf/test-suites/ts-198.json

@@ -0,0 +1,87 @@
+{
+  "createdAt": "2026-09-16T19:20:00Z",
+  "updatedAt": "2026-09-16T19:20:00Z",
+  "purpose": "Cover AC-16104-1 (rcf init merges three feedback hook entries into .claude/settings.json and .codex/hooks.json with the design-3.5 shape, the matcher startup|resume on SessionStart, timeouts 10/5/5, is byte-idempotent on re-init, preserves neighbouring hooks and honours --bin-path with the node <path> pinned shape), AC-16104-2 (--no-feedback-hooks writes neither file and prints the RULE 17 fallback line once) and AC-16104-3 (rcf doctor --check feedback-hooks reports missing-hook per file per event when absent, --fix installs them, foreign-hook is refused with the entry left in place, a clean tree exits 0 with no writes, and a parse-error on the settings file is refused).",
+  "testLevel": "integration",
+  "acIds": [
+    "AC-16104-1",
+    "AC-16104-2",
+    "AC-16104-3"
+  ],
+  "id": "TS-198",
+  "usId": "US-16104",
+  "title": "Slice 5 (FBS-184): rcf init installs the feedback hooks and rcf doctor feedback-hooks keeps them honest across clones",
+  "testCases": [
+    {
+      "id": "TC-198-init-writes-both-configs",
+      "acId": "AC-16104-1",
+      "description": "Cover AC-16104-1 via the CLI test: rcf init on a fresh project writes three feedback hook entries into .claude/settings.json (Stop 10s, SessionEnd 5s, SessionStart 5s with matcher startup|resume) and three matching entries into .codex/hooks.json (Codex JSON shape); every command line is 'npx rcf-lite feedback hook <event> --harness <h>'.",
+      "status": "pending",
+      "testPointer": "test/cli/init-feedback-hooks.test.js::AC-16104-1: rcf init writes three feedback hook entries into both harness files"
+    },
+    {
+      "id": "TC-198-init-idempotent",
+      "acId": "AC-16104-1",
+      "description": "Cover AC-16104-1 (idempotency) via the CLI test: a second rcf init against the same tree produces no byte change on either .claude/settings.json or .codex/hooks.json.",
+      "status": "pending",
+      "testPointer": "test/cli/init-feedback-hooks.test.js::AC-16104-1: re-init on the same tree is byte-idempotent"
+    },
+    {
+      "id": "TC-198-init-preserves-existing-hooks",
+      "acId": "AC-16104-1",
+      "description": "Cover AC-16104-1 (preserve) via the CLI test: a pre-existing .claude/settings.json with an unrelated Stop hook AND an unrelated top-level key survives rcf init; the feedback Stop entry is added alongside the unrelated one, not in place of it.",
+      "status": "pending",
+      "testPointer": "test/cli/init-feedback-hooks.test.js::AC-16104-1: pre-existing hooks are preserved; feedback entries added alongside"
+    },
+    {
+      "id": "TC-198-init-bin-path-pins-node",
+      "acId": "AC-16104-1",
+      "description": "Cover AC-16104-1 (--bin-path pinned shape) via the CLI test: rcf init --bin-path /opt/pinned-rcf/rcf.js writes hook commands as 'node /opt/pinned-rcf/rcf.js feedback hook <event> --harness <h>' instead of the npx rcf-lite shape.",
+      "status": "pending",
+      "testPointer": "test/cli/init-feedback-hooks.test.js::AC-16104-1: --bin-path pins the hook command to node <path>"
+    },
+    {
+      "id": "TC-198-init-no-feedback-hooks",
+      "acId": "AC-16104-2",
+      "description": "Cover AC-16104-2 via the CLI test: rcf init --no-feedback-hooks exits 0, writes neither .claude/settings.json nor .codex/hooks.json, and prints the no-feedback-hooks fallback line naming RULE 17.",
+      "status": "pending",
+      "testPointer": "test/cli/init-feedback-hooks.test.js::AC-16104-2: --no-feedback-hooks writes neither file and prints the fallback line"
+    },
+    {
+      "id": "TC-198-doctor-missing-hooks",
+      "acId": "AC-16104-3",
+      "description": "Cover AC-16104-3 (missing-hook detection) via the CLI test: rcf doctor --check feedback-hooks --json against a project scaffolded without hook install reports exactly three missing-hook rows for .claude/settings.json and three for .codex/hooks.json; exit 3.",
+      "status": "pending",
+      "testPointer": "test/cli/doctor-feedback-hooks.test.js::AC-16104-3: doctor reports missing-hook per file per event when both configs are absent"
+    },
+    {
+      "id": "TC-198-doctor-fix-installs-and-reruns-clean",
+      "acId": "AC-16104-3",
+      "description": "Cover AC-16104-3 (--fix repair) via the CLI test: rcf doctor --check feedback-hooks --fix writes the missing entries; a re-run reports clean and exits 0.",
+      "status": "pending",
+      "testPointer": "test/cli/doctor-feedback-hooks.test.js::AC-16104-3: doctor --fix installs the missing entries and re-runs clean"
+    },
+    {
+      "id": "TC-198-doctor-foreign-hook-refused",
+      "acId": "AC-16104-3",
+      "description": "Cover AC-16104-3 (foreign-hook refusal) via the CLI test: after a clean init, mutating the Stop hook's command to add an unknown flag makes doctor --check feedback-hooks --fix --json emit exactly one foreign-hook drift row on .claude/settings.json; the mutated command survives (--fix did not overwrite it) and doctor exits 3.",
+      "status": "pending",
+      "testPointer": "test/cli/doctor-feedback-hooks.test.js::AC-16104-3: doctor refuses a foreign-hook entry and leaves it in place"
+    },
+    {
+      "id": "TC-198-doctor-clean-tree-no-writes",
+      "acId": "AC-16104-3",
+      "description": "Cover AC-16104-3 (clean tree) via the CLI test: rcf doctor --check feedback-hooks --fix on a freshly initialised project makes no byte changes to either config file and exits 0.",
+      "status": "pending",
+      "testPointer": "test/cli/doctor-feedback-hooks.test.js::AC-16104-3: a clean tree makes no writes and stays exit 0"
+    },
+    {
+      "id": "TC-198-doctor-parse-error-refused",
+      "acId": "AC-16104-3",
+      "description": "Cover AC-16104-3 (parse-error refusal) via the CLI test: an unparseable .claude/settings.json makes doctor --check feedback-hooks --fix emit one parse-error drift row on that file, leave the file untouched, and exit 3.",
+      "status": "pending",
+      "testPointer": "test/cli/doctor-feedback-hooks.test.js::AC-16104-3: doctor rejects an unparseable settings file with parse-error and refuses --fix"
+    }
+  ],
+  "status": "draft"
+}

package/rcf/test-suites/ts-199.json

@@ -0,0 +1,51 @@
+{
+  "createdAt": "2026-09-16T21:06:54Z",
+  "updatedAt": "2026-09-16T21:06:54Z",
+  "purpose": "Cover AC-16201-1 (RULE 17 lands in guidance/managed/agent-instructions-block.md with the wording in design 3.4, byte-exact against test/fixtures/managed/rule-17.md; block hash regenerated; naming and static-wording invariants) and AC-16201-2 (rcf init writes RULE 17 into CLAUDE.md and AGENTS.md between the managed markers; an existing project on the pre-slice block picks up RULE 17 on rcf doctor --fix without --force in non-interactive mode).",
+  "testLevel": "integration",
+  "acIds": [
+    "AC-16201-1",
+    "AC-16201-2"
+  ],
+  "id": "TS-199",
+  "usId": "US-16201",
+  "title": "Slice 6 (FBS-185): RULE 17 landed in the managed block and reaches every project through init and doctor --fix",
+  "testCases": [
+    {
+      "id": "TC-199-rule-17-slice-byte-exact-against-fixture",
+      "acId": "AC-16201-1",
+      "description": "Cover AC-16201-1 via the guidance test: the RULE 17 slice extracted from guidance/managed/agent-instructions-block.md is byte-for-byte identical to the design 3.4 fixture at test/fixtures/managed/rule-17.md.",
+      "status": "pending",
+      "testPointer": "test/guidance/rule-17.test.js::AC-16201-1: the RULE 17 slice of the block is byte-for-byte the fixture"
+    },
+    {
+      "id": "TC-199-rule-17-names-verbs-and-redaction-posture",
+      "acId": "AC-16201-1",
+      "description": "Cover AC-16201-1 (naming clause) via the guidance test: RULE 17 names rcf feedback add, preview, submit --yes, defer, opt-out and carries the redaction posture sentence and the one-ask-per-session posture.",
+      "status": "pending",
+      "testPointer": "test/guidance/rule-17.test.js::AC-16201-1: RULE 17 names all four verbs and the redaction posture"
+    },
+    {
+      "id": "TC-199-rule-17-static-wording-no-em-dash-no-version-no-date",
+      "acId": "AC-16201-1",
+      "description": "Cover AC-16201-1 (static-wording clause) via the guidance test: the RULE 17 fixture carries no em-dash, no ISO date and no semver, so the block hash moves exactly once on the release that ships the rule.",
+      "status": "pending",
+      "testPointer": "test/guidance/rule-17.test.js::AC-16201-1: RULE 17 carries no em-dash and no version or date string"
+    },
+    {
+      "id": "TC-199-init-writes-rule-17-into-both-instructions-files",
+      "acId": "AC-16201-2",
+      "description": "Cover AC-16201-2 (fresh-init path) via the CLI test: rcf init on a fresh project writes CLAUDE.md and AGENTS.md with the managed block; RULE 17 sits between the managed markers on both files and its slice is byte-identical to the fixture.",
+      "status": "pending",
+      "testPointer": "test/cli/init-rule-17.test.js::AC-16201-2: rcf init writes RULE 17 into CLAUDE.md and AGENTS.md between the managed markers"
+    },
+    {
+      "id": "TC-199-existing-project-picks-up-rule-17-on-doctor-fix",
+      "acId": "AC-16201-2",
+      "description": "Cover AC-16201-2 (upgrade path) via the CLI test: a project initialised on the pre-slice block (block minus RULE 17) reports stale-hash on rcf doctor and picks up RULE 17 on rcf doctor --fix without --force in non-interactive mode, on both CLAUDE.md and AGENTS.md.",
+      "status": "pending",
+      "testPointer": "test/cli/init-rule-17.test.js::AC-16201-2: an existing project on the pre-slice block reports stale-hash and picks up RULE 17 on doctor --fix"
+    }
+  ],
+  "status": "draft"
+}

package/rcf/test-suites/ts-200.json

@@ -0,0 +1,30 @@
+{
+  "createdAt": "2026-09-16T22:20:45Z",
+  "updatedAt": "2026-09-16T22:20:45Z",
+  "purpose": "Cover AC-16301-1 (supersededBy broken pointer surfaces as brokenReference with field=supersededBy) and AC-16301-2 (relatedAdrs unknown entry stays SILENT; the compatibility carry keeps the ratified `rcf define blueprint supersede` workflow unbroken). The tests scaffold a fresh RCF project with initProject, mutate adr-001.json's cross-links, then walkTree and assert the presence / absence of brokenReference entries accordingly.",
+  "testLevel": "integration",
+  "acIds": [
+    "AC-16301-1",
+    "AC-16301-2"
+  ],
+  "id": "TS-200",
+  "usId": "US-16301",
+  "title": "referee-validate ADR cross-link walker: AC-16301-1 supersededBy broken, AC-16301-2 relatedAdrs unknown",
+  "testCases": [
+    {
+      "id": "TC-200-superseded-by-broken",
+      "acId": "AC-16301-1",
+      "description": "Fresh project via initProject; set adr-001.json supersededBy to ADR-999; walkTree; assert errors contain a brokenReference with documentId=ADR-001 and field=supersededBy.",
+      "status": "pending",
+      "testPointer": "test/store/walker.test.js::walkTree flags an ADR with a broken supersededBy pointer as brokenReference (REQ-163 AC-16301-1)"
+    },
+    {
+      "id": "TC-200-related-adrs-silent",
+      "acId": "AC-16301-2",
+      "description": "Fresh project via initProject; set adr-001.json relatedAdrs to [ADR-777]; walkTree; assert NO brokenReference targets the relatedAdrs field on ADR-001 (compatibility carry: the ratified `rcf define blueprint supersede` workflow leaves a transient unresolved relatedAdrs pointer between the supersede write and the closing re-add step).",
+      "status": "pending",
+      "testPointer": "test/store/walker.test.js::walkTree stays silent on an ADR with an unknown id in relatedAdrs (referee-guarantee C-7 compatibility carry: soft-reference half deferred)"
+    }
+  ],
+  "status": "approved"
+}

package/rcf/test-suites/ts-201.json

@@ -0,0 +1,38 @@
+{
+  "createdAt": "2026-09-16T22:28:54Z",
+  "updatedAt": "2026-09-16T22:28:54Z",
+  "purpose": "Cover the strict-by-default default (AC-16401-1), the --mode shallow-any opt-out (AC-16401-2), and the conflict / unknown-mode usage refusals (AC-16401-3). Every test scaffolds a fresh RCF project and invokes the coverage bin as an out-of-process subprocess, matching the pattern the rest of `test/cli/coverage.test.js` uses.",
+  "testLevel": "integration",
+  "acIds": [
+    "AC-16401-1",
+    "AC-16401-2",
+    "AC-16401-3"
+  ],
+  "id": "TS-201",
+  "usId": "US-16401",
+  "title": "coverage --mode selector: strict-by-default, shallow-any opt-out, conflict refusal",
+  "testCases": [
+    {
+      "id": "TC-201-strict-by-default-exit-4",
+      "acId": "AC-16401-1",
+      "description": "Fresh project via initProject (AC-101-1 uncovered by construction); invoke `rcf audit coverage` with no flag; assert exit code 4.",
+      "status": "pending",
+      "testPointer": "test/cli/coverage.test.js::rcf coverage (strict-by-default) with a gap exits 4"
+    },
+    {
+      "id": "TC-201-shallow-any-opt-out",
+      "acId": "AC-16401-2",
+      "description": "Fresh project via initProject; invoke `rcf audit coverage --mode shallow-any`; assert exit code 0 and stdout matches /Coverage mode: shallow-any/.",
+      "status": "pending",
+      "testPointer": "test/cli/coverage.test.js::rcf coverage --mode shallow-any prints gaps and exits 0 (explicit opt-out)"
+    },
+    {
+      "id": "TC-201-conflicting-flags-exit-2",
+      "acId": "AC-16401-3",
+      "description": "Fresh project via initProject; invoke `rcf audit coverage --mode shallow-any --strict`; assert exit code 2 and stderr matches /--mode shallow-any conflicts with --strict/.",
+      "status": "pending",
+      "testPointer": "test/cli/coverage.test.js::rcf coverage --mode shallow-any --strict exits 2 (conflicting flags)"
+    }
+  ],
+  "status": "approved"
+}

package/rcf/test-suites/ts-202.json

@@ -0,0 +1,38 @@
+{
+  "createdAt": "2026-09-16T22:38:04Z",
+  "updatedAt": "2026-09-16T22:38:04Z",
+  "purpose": "Cover AC-16501-1 (UI-BASELINE-UNMET refusal, C-28 + C-36), AC-16501-2 (BROWSER-VERIFICATION-MISSING refusal, C-29) and AC-16501-3 (SCOPE-MISMATCH refusal, C-30). Each test scaffolds a fresh RCF project with initProject, wires a stub verify subprocess that writes a passing report carrying the named per-AC verdict, invokes rcf build finalise, and asserts exit 4 with the expected stderr message.",
+  "testLevel": "integration",
+  "acIds": [
+    "AC-16501-1",
+    "AC-16501-2",
+    "AC-16501-3"
+  ],
+  "id": "TS-202",
+  "usId": "US-16501",
+  "title": "finalise per-AC refusals: UI-BASELINE-UNMET, BROWSER-VERIFICATION-MISSING, SCOPE-MISMATCH",
+  "testCases": [
+    {
+      "id": "TC-202-ui-baseline-unmet-refusal",
+      "acId": "AC-16501-1",
+      "description": "Fresh project via initProject with FBS-001 at complete; stub verify writes a passing report with perAcVerdicts = [{acId: AC-101-1, verdict: UI-BASELINE-UNMET}]; invoke rcf build finalise; assert exit 4, FBS at complete, stderr matches /UI-BASELINE-UNMET/ and /Referee-guarantees claims C-28 and C-36/.",
+      "status": "pending",
+      "testPointer": "test/cli/finalise-referee-refusals.test.js::finalise refuses to promote on a passing verify report that carries UI-BASELINE-UNMET (referee-guarantees C-28, C-36)"
+    },
+    {
+      "id": "TC-202-browser-verification-missing-refusal",
+      "acId": "AC-16501-2",
+      "description": "Same scaffold; perAcVerdicts = [{acId: AC-101-1, verdict: BROWSER-VERIFICATION-MISSING}]; assert exit 4, FBS at complete, stderr matches /BROWSER-VERIFICATION-MISSING/ and /Referee-guarantees claim C-29/.",
+      "status": "pending",
+      "testPointer": "test/cli/finalise-referee-refusals.test.js::finalise refuses to promote on a passing verify report that carries BROWSER-VERIFICATION-MISSING (referee-guarantees C-29)"
+    },
+    {
+      "id": "TC-202-scope-mismatch-refusal",
+      "acId": "AC-16501-3",
+      "description": "Same scaffold; perAcVerdicts = [{acId: AC-101-1, verdict: SCOPE-MISMATCH}]; assert exit 4, FBS at complete, stderr matches /SCOPE-MISMATCH/ and /Referee-guarantees claim C-30/.",
+      "status": "pending",
+      "testPointer": "test/cli/finalise-referee-refusals.test.js::finalise refuses to promote on a passing verify report that carries SCOPE-MISMATCH (referee-guarantees C-30)"
+    }
+  ],
+  "status": "approved"
+}