Files
gstack/test/run-in-background-guidance.test.ts
f67c478f05 v1.91.34.0 fix: /autoplan on current Claude Code and long sessions, quieter pre-push and sync guards, gstack-post, gstack-doctor (#3069)
* docs: Oct 7 follow-up wave plan (pre-review)

* docs: Oct 7 follow-up wave plan, reviewed through /autoplan

* docs: Oct 7 wave plan, record final gate decisions (UC1 accepted, UC2 rejected)

* docs: credit #1822 to @Mike-E-Log and #1743 to @habassa5 (v1.64.0.0)

The v1.64.0.0 CHANGELOG entry credited the extension token fix (#1822)
and the polyfill exited promise (#1743) to the wrong handle, and the
extension-sender-auth test header repeated the first slip. Commit history
is not rewritten.

Fixes #3054.

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

* fix(context-restore): offer newer checkpoints from nested repos and task worktrees

/context-restore could present an older checkpoint as the latest with no
error in two layouts:

1. A session started in a non-git parent saved from a nested repo, so the
   checkpoint went to the nested repo's bucket. Restore in the parent now
   lists checkpoints of other buckets whose project_root lies below the cwd
   (BELOW_CWD; the 200 newest are read, and from $HOME only each project's
   newest). /context-save also leaves a JSON pointer (checkpoint path, bucket,
   project_root) in the starting directory's bucket when $CLAUDE_PROJECT_DIR
   is set and files elsewhere; restore lists those as POINTER, in or out of git.
2. A plan checkpoint on the main tree's branch shadowed a newer checkpoint
   saved in a ticket worktree. When another branch holds a newer checkpoint
   for the same task (a worktree below the main tree, read from the new
   worktree: stamp; equal normalized titles; or a shared #123 / ABC-123
   token in titles or branch names), restore prints NEWER_TASK and the skill
   shows both and proposes the newer one. Generic titles (wip, checkpoint,
   save, notes, todo) never match on title alone, and the worktree rule
   applies only when restoring from the main tree, so sibling worktrees
   still never shadow each other.

The branch-first ordering itself is unchanged.

Refs #3065.

Co-authored-by: Thomas Gernhardt <t.gernhardt@softwareprojekt.net>
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* fix(redact-prepush): list each MEDIUM finding with rule, file line and fix

The pre-push hook printed only a MEDIUM count, which nobody could review
without re-running the engine by hand. It now prints one line per finding:
rule id, file and file line, and a fix, never the matched value.

Line numbers come from the hunk headers (combined --cc headers included), so
a finding in a later hunk or past a scan-chunk boundary points at the real
file line. Findings from the per-commit catch-up path name the commit whose
file line it is, so content removed before the pushed tip is still locatable.

Plan items: CEO-7 (summary half), DX-9 (fix lines), ENG-8 (line mapping).

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

* fix(redact-prepush): stop flagging your own email and already-public authors (#3060)

The hook never passed the engine's selfEmail / repoPublicEmails, so every
push that added the pusher's address, or a commit author's, raised a MEDIUM
pii.email warning for an address the destination already shows.

The hook now reads `git config user.email` and one bounded `git log` of
author and committer addresses, raw and mailmapped (%ae %aE %ce %cE): the
history of every pushed tip (those commits become public with the push),
each remote tip being replaced, and, for a new branch or an unknown remote
tip pushed to a configured remote, that remote's own tracking refs. A URL or
unknown destination never borrows tracking refs, and another remote's
history never counts.

The read stops at 50,000 commits (the newest authors are used) and 5 seconds.
An error or the timeout passes no history and, when an email finding is
listed, prints one line saying suppression was limited for this push. The two
inputs fail independently. HIGH findings and every other rule are untouched.

Controls: a stranger's address, an address only another remote knows, a URL
push next to a matching remote, and a first push of a repo with no history
all still report.

Plan items: A3, CEO-7, CEO-23 (A3 half), DX-9 (partial history), ENG-8
(history scope, mailmap).

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

* feat(redact-prepush): per-address allowlist for pii.email (gstack.redact.allowEmail)

`git config --add gstack.redact.allowEmail <address>` allows that address for
MEDIUM pii.email findings only, so a team alias or support address that has
to be in the repo stops warning without reaching for --no-verify. It never
affects HIGH findings or any other rule, and the pii.email fix line names it.

Controls: a different address still reports, and a HIGH secret next to an
allowed address still blocks.

Plan item: DX-17.

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

* docs(troubleshooting): pre-push pii.email findings, exemptions and allowlist

Plan item: DX-12 (pre-push touchpoint).

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

* test(redact-prepush): assemble fixture addresses at runtime

The email fixtures were literals, so this branch's own push listed 47
pii.email findings in its test file. Build them from a helper instead, the
way the neighbouring tests build credential and IP fixtures.

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

* fix(browse): offer the user's signed-in tab, name silent aside repl failures

Rules (rendered into every browsing skill, kept short):
- Rule 1: before the first openTab, offer the user's tabs on the target
  origin (title and origin only; the rest of listBrowserTabs() stays
  private) and attach only after the user confirms one.
- Rule 4: a second sign-in wall after a confirmed sign-in means the session
  is bound to the tab or URL; offer that tab instead of another sign-in.
- Rule 6 no longer suggests an early return; rule 7 says a fast [ok without
  GSTACK_STEP_OK is an abort.

Cookbook (browse, devex-review): a "Silent failures" list (evaluate returns
only serializable values, no top-level return, locator(sel).press(key), an
empty DOM read is about the selector until the screenshot and the request's
response say otherwise, read toggle state before clicking) and a signed-in
tab recipe that prints only target-origin tabs and never closes the user's tab.

Parity caps for design-consultation, land-and-deploy, qa and the browse
skeleton are raised to the measured sizes, with notes.

Refs #3063, #3064.

Co-authored-by: Thomas Gernhardt <t.gernhardt@softwareprojekt.net>
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* feat(codex): run gstack-codex-probe as a command, one subcommand per probe

Generated skills now execute bin/gstack-codex-probe (select-model, check-auth,
show-sandbox, check-sandbox, probe-model, check-version, show-first-use-notice,
run-with-timeout, log-event, log-hang, help) and capture its KEY: value lines,
so no helper state crosses into the calling shell and the preflight works from
bash, zsh or sh. select-model keeps --model > GSTACK_CODEX_MODEL > config.toml
precedence; run-with-timeout supervises with the existing gtimeout/timeout/
watchdog chain and returns 124 on a deadline; an unknown subcommand exits 64.

Sourcing keeps working for skills rendered before the upgrade and prints one
deprecation line naming /gstack-upgrade; it and the zsh self-locate block are
removed in a release on or after 2026-10-21 (DX-18). Parity caps raised with
measured notes for the longer capture lines.

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

* feat(gstack-post): one argv-only, redaction-scanned write path for PR and issue text

bin/gstack-post posts a PR/MR or issue comment, a review-comment reply, a
PR title or body, a new PR/MR or a new issue from agent-written files. Every
value reaches gh/glab as its own argv element in --flag=<value> form or on
stdin, never through a shell string, and a target is a number or a URL of
this repository on the same host.

The helper owns the redaction scan: it reads each file once, scans those
exact bytes (visibility from config, then gh/glab; the pusher's own email
suppressed) and sends the same bytes. HIGH is refused with exit 1 and no
confirmation can post it. MEDIUM exits 2 with RULE:/LINE:/PART: lines and a
TOKEN: digest of the bytes, destination, operation and findings; only
--confirm <token> for those exact bytes posts, so any edit needs a new
confirmation. gh/glab failures exit 3, usage errors 64. It also carries the
projectCards REST fallback and the title read-back that /ship did by hand.

The logic lives in lib/gstack-post.ts behind an injectable runner, so its
tests run in the Windows free lane; the stub-gh executable test is POSIX.

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

* fix(autoplan): guard verifies dispatches on Claude Code 2.1.29x (schema strip, unflushed call, named causes)

Cause A: Claude Code journals the model's raw Agent input but hands
PreToolUse the schema-parsed input; with the fork-subagent gate on (the
interactive default in 2.1.292) run_in_background is dropped, so the journal
record never deep-equaled the payload. nativeToolInput now drops only that
documented strip for Agent. Agent input is bound on both paths: keys limited
to prompt, description, subagent_type (general-purpose) and
run_in_background; a model override or any other key is denied.

Cause B: when a ready journal lacks the current call, the guard evaluates
the payload placed after the last journaled record instead of polling for a
record that may arrive only with the tool result. A phase transition counts
a report only when a later journaled record follows it (and, on the journal
path, it is not in the current call's message). One batch rule covers both
paths; a background reviewer keeps the invocation armed until its
completion notice.

Every outcome now has a stable reason code, disposition and anchor
(autoplan/bin/guard-reasons.ts). UC1: Claude-Code-caused states
(unrecognized shape, journal lag, rewritten journal, oversized record,
unchecked-version schema strip) allow with a visible warning; integrity
failures stay denials. No denial advises a bare retry. Every guarded
decision appends one content-free line to analytics/autoplan-guard.jsonl,
trimmed to 1,000 lines past 256 KiB.

Co-authored-by: Jared <182125291+yolo-jared@users.noreply.github.com>
Co-authored-by: crblabs <293123359+crblabs@users.noreply.github.com>
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* fix(autoplan): publish each phase report with a no-op call; foreground requests are conditional

Phase-close step 6 sends the report in a message whose only tool call is
the Bash no-op ': autoplan-published <phase>', and step 7 makes the next
guarded call in a later message, so the guard sees the report flushed
before the next phase entry regardless of Claude Code's journal timing.

Every site that asked for run_in_background: false now asks for it only
when the Agent schema offers it and says how to recover when a dispatch
runs in the background anyway (wait for its completion notice). Parity
caps rise by the measured bytes.

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

* feat(ship,spec,review): PR and issue text goes out only through gstack-post

/ship: Step 18 writes the title into an agent-written file. An existing PR's
title is piped from gh/glab through gstack-pr-title-rewrite.sh --stdin (new),
so neither the agent nor a shell string carries it; a new title is written
with the file tool and its version prefix checked in the file. Step 19
composes the body as before and publishes with gstack-post pr-create, or
pr-body then pr-title, which scan the exact bytes they send. The separate
title and body scans, the hand-rolled REST fallback and the title self-check
are gone (the helper does all three). Title preparation moved into the
pr-body section, so the skeleton shrinks.

/spec files its issue with gstack-post issue-create and drops the pre-issue
re-scan; Greptile replies use gstack-post reply and pr-comment.
scripts/resolvers/redact-doc.ts loses its PR and issue sinks, and a test
keeps any template from rendering one again.

Tests that pinned the old scan-then-gh wiring now pin the gstack-post wiring;
the publication tests run the real compose and publish blocks against a stub
gh with the real helper (HIGH in title or body refused, MEDIUM token flow).

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

* ci: pin Claude Code 2.1.292 in the CI image

2.1.292 is the npm latest users run. Its interactive default turns on the
fork-subagent gate, which strips run_in_background from the Agent schema
and backgrounds reviewers; CI on 2.1.284 never saw the /autoplan guard
break. The image tag is a content hash, so every eval workflow picks up
the new image without a workflow edit.

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

* fix(brain-sync): one drain lock for every writer to the artifacts repo

gstack-artifacts-init, gstack-brain-restore, gstack-gbrain-source-wireup
and the skill-start merge ran git in $GSTACK_HOME without the drain's lock,
so the drain could never tell an abandoned .git/index.lock from a live one.
They now take the same mkdir lock (bin/gstack-brain-lock.sh): the drain and
the skill-start merge skip when it is held, user-run writers wait for it
(GSTACK_BRAIN_LOCK_WAIT, default 120 s), and a child of the holder (the
drain's daily worktree advance, restore's wireup) inherits it by token.

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

* fix(brain-sync): hold back only the flagged file, keep coupled artifacts whole

One file with secret-shaped text used to block every push, silently. The
drain now attributes scanner hits to files in one pass over the staged diff
(split on its diff --git headers), holds back each flagged file with the
rest of its coupled group, unstages it, and requires the remaining staged
diff to re-scan clean; anything short of that falls back to a full unstage
and status blocked. Held files stay queued and are re-scanned every drain.

- Status file gains held_count, drainable, last_drain_at, last_push_at and
  held[] (path, scanner rule, dependents, both fixes); new status held.
- Coupled groups come from an explicit map (decisions.jsonl and
  decisions.active.json): a queued member stages the whole group, a group
  stages only when its snapshot matches its log in the index, a skipped
  member stops the whole group.
- --unskip-file undoes --skip-file and queues the path again.
- An index lock older than 10 minutes is removed under the drain lock; a
  younger one, a failed git add, a failed commit (hooks included) keep the
  queue and report status error. A verified empty staged diff is the only
  "nothing to commit". git add runs once, batched.
- The scanner reads bytes, so undecodable content no longer crashes it into
  a false clean; matched text never reaches the status file.
- An empty-queue run with unpushed sync commits stays push_failed.
- Privacy-held duplicate records collapse to one per path; --status counts
  a spool too deep for a shell glob.
- --attention prints skill start's fixed attention lines from the sync
  status table in the usage header.

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

* feat(skill-start): ARTIFACTS_SYNC attention lines for a stuck sync

Skill start now prints one fixed attention line per sync-status-table row
that applies (held, blocked, push_failed, error, unknown, stale-push,
stale-drain), each naming gstack-brain-sync by absolute path. Values from
the status file are clamped (status code to the table, counts to digits,
timestamps to their shape), so the status message, file paths and scanner
output never reach the line. The preamble tells the model to surface the
line in one sentence and continue. Skill-start tests are generated from the
table in bin/gstack-brain-sync, and docs/gbrain-sync-errors.md carries the
same table.

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

* fix(outside-review): severity words in label position count as findings

The Oct 7 /autoplan run's Codex CEO and DX reviews labeled seven and eight
findings High/Medium without [Pn] tags, and the classifier printed
VERDICT: clean / FINDINGS: none for both. lib/outside-review-result.ts now
reads severity words in label position (Severity: High, a leading High: /
High — / [High], **High**, a table cell): critical/high block like P0/P1,
medium/low are advisory. Words in prose (high-level, low-risk, no critical
findings) never count. A review or structured response with neither tags,
labels nor an explicit no-findings statement is unverified, never clean
(DX-11, ENG-10). Design-direction proposals move to a new proposal gate so
they keep needing only their Recommendation line, and review prompts ask
for a severity per finding. Fixtures reproduce the CEO/DX label shapes, the
eng [P1] output, a table and prose negative controls; the stored Codex panel
keeps its verdicts. docs/troubleshooting.md explains how the verdict is read.

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

* feat: gstack-doctor readiness report and setup --status Codex row (B5)

bin/gstack-doctor prints one row per check without starting a skill:
install root (the registry rows behind ./setup --status), state root, Bun
against the floor, hook parse check, Codex mode and self-locate via
gstack-codex-probe subcommands, the cached model probe with its age
(--live runs the paid probe-model), artifacts-sync health from the status
file with the status code clamped, the browse bundle, Claude Code version,
the largest session journal and the last five schema-1 guard reason codes.
Rows are ok, warn, not configured or fail; only fail exits non-zero; fix
lines name helpers by absolute install-root path.

./setup --status gains a read-only Codex row (bin/gstack-codex-status.sh,
shared with the doctor) and ends with the doctor's absolute path.

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

* docs: bug-report template asks for doctor output; README troubleshooting entry; doctor test in the Windows lane

The template gives the Claude Code doctor path and a lookup for other
hosts and names no bare gstack- command (asserted in
test/gstack-doctor.test.ts). The doctor test runs every script through
explicit bash argv, so it joins the curated Windows free subset.

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

* docs(troubleshooting): readiness check section points at gstack-doctor

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

* fix(question-tuning,plan-tune,gbrain): free text reaches helpers only through agent-written files

Question tuning no longer pipes the question summary through printf: a
registered id needs no summary, and for an unregistered id the agent writes
the summary to .gstack/tmp/qt.txt and passes --summary-file (new). The
helper resolves a relative path against the git top level, removes scratch
files under .gstack/tmp, and asks normally when the file is missing.

/plan-tune tune events carry the user's own words again: they go into a
file the agent writes and reach gstack-question-preference --write through
--free-text-file (new), still behind the injection filter and the
user-origin gate.

docs/gbrain-write-surfaces.md drops its heredoc templates for the
agent-written page file on stdin, matching the per-skill save block, and the
generic save block stops showing a quoted --content argument.

The tuning prose was tightened so every preamble stays within its size cap.

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

* test(evals): daily autoplan-schema-canary on the latest Claude Code

A periodic rule case installs the latest published Claude Code with
install scripts off, verifies registry signatures, and runs one headless
session with the fork-subagent gate on whose PreToolUse hook records an
Agent and a Read payload. Each payload must match its journal record under
the guard's own comparison, keep the journal's key set apart from the
documented run_in_background strip, and stay inside the Agent allowlist;
a background Agent's completion notice must keep the shape the guard reads.
evals-periodic.yml runs it daily on its own schedule and concurrency group
(read-only token); the weekly census also includes it. A free test proves
the comparison fails on an injected strip.

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

* fix(doctor): read the artifacts sync held count from held_count, the field the drain writes

* fix(artifacts sync): the init and restore pre-commit hooks catch Bearer/Basic/Token-prefixed JSON auth headers like the drain does

* feat(greptile-early): detect Greptile, ask once on public repos, open the early draft, wait for the review

bin/gstack-greptile-early backs /ship's early Greptile PR:
- detect: a root .greptile/ folder (which takes precedence), greptile.json,
  or a Greptile comment on the repo in the last 90 days; triggerOnDrafts from
  the effective root config; repo visibility; public-repo consent. It prints
  the signal, that /ship will push and open a draft now, the 10-minute wait
  cap and the absolute gstack-config command that turns it off.
- consent yes|no: the public-repo answer, remembered per repo in the
  project's state.
- open: opens the draft through gstack-post with a body saying /ship opened
  it early, and posts one @greptileai comment through gstack-post when the
  config does not set triggerOnDrafts: true. An open PR is left alone.
- wait: polls every 30 s for a completed Greptile check run, a Greptile
  review of the head commit or a summary naming it; each call returns within
  about 90 s and reports timeout 10 minutes after the PR opened.

gstack-config gains ship_greptile_early (default true, invalid values
rejected): on automatically whenever the repo uses Greptile, off per user.
The logic is in lib/greptile-early.ts behind an injectable runner, so its
fixture-repo tests run in the Windows lane; an end-to-end test drives the
real helper and gstack-post against a stub gh.

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

* feat(ship): early Greptile PR at Step 6.5, bounded wait at Step 10 (#3020)

When the repo uses Greptile, /ship pushes and opens a draft PR right after
its free tests pass (new lazy section greptile-early, Step 6.5), so Greptile
reviews while Steps 7-9 run. A public repo asks once, remembered per repo;
declining keeps today's order. Step 10 waits for that review with
gstack-greptile-early wait and takes the existing unavailable route on a
timeout, never a claim of zero comments. Step 18 replaces the provisional
title, Step 19 marks the draft ready unless a draft was requested, and a
/ship that stops after Step 6.5 leaves the draft open with one comment
saying why.

ship's union cap rises to 1.5275 with the measured note (B4 +836 bytes,
B2 +4,732 bytes); the step-numbering guard allows 6.5; ship goldens are
refreshed for B4 and B2.

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

* fix(autoplan): the publication no-op is 'true autoplan-published <phase>'

Measured on Claude Code 2.1.292 in a default-settings interactive session:
a bare ':' Bash command asks for approval ('This command requires
approval'), and after a background reviewer's completion notice starts a
new turn the skill's allowed tools no longer cover it, so the phase-close
no-op prompted the user. 'true' with arguments runs without approval and
prints nothing. The guard only needs a later journaled record, so the
command changes everywhere it is named.

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

* test(evals): live autoplan-guard-pty case on the pinned Claude Code

A gate-tier rule case (one trial, haiku) drives an interactive PTY
session with default settings through a project skill that carries
/autoplan's own hook block: init, Phase 1 entry, a CEO reviewer dispatch
that sends run_in_background, a prepared close packet, the report
published with the no-op, and the Phase 2 entry in a later message. It
reads outcomes from the guard decision log (three verified allows) and
fails if the no-op raises a permission card; other cards are approved and
printed.

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

* fix(autoplan): bounded, append-tolerant owned-journal read (A2)

The publication guard no longer reads the whole parent journal or refuses
it at 32 MiB. lib/claude-owned-journal.ts streams the bytes present at open
to the last complete line (pass one), keeps a content-free index per record
and decides ownership, ancestry and causal order on it with the same checks
and reason codes as before. Pass two reloads in full only what the
evaluation reads (autoplan/bin/guard-journal.ts): every literal init and its
result, the current call, and inside the invocation window (from the latest
human turn at or before the bound chain's first init) guarded and
close-packet Read results, structured Bash results, error results, assistant
text after the first close Read and active-plan mutations, plus the earlier
Read a dedup reply cites even before the window (ENG-4).

- lib/claude-journal-records.ts: per-record event extraction, record
  metadata and the causal-order checks, shared by readPlanCountTranscript
  and the bounded reader. The batch reader keeps its whole-file read and cap.
- Appends after open never fail a read; same device and inode and no
  shrink are required (identity). A second read in one hook invocation must
  hash bytes [0, first size) the same, or it is `rewritten` (UC1 unverified);
  the unrecognized-shape double read uses that prefix hash. `changing` is
  removed (REMOVED_CODES; its anchor stays).
- OWNED_RECORD_MAX_BYTES (32 MiB): only one record over it is too_large.
  OWNED_RETAINED_MAX_BYTES (32 MiB): over it is the new oversized_invocation
  fallback denial. GSTACK_TRANSCRIPT_TEST_MAX_BYTES and
  GSTACK_TRANSCRIPT_TEST_RETAINED_BYTES can only lower them.
- ENG-5: evaluation groups uses and results by tool id once (no per-tool
  rescans).

CEO-25 / ENG-5 spike (120 MiB synthetic, 31,242 records, 4 vCPU Linux,
Bun 1.4.2): a full streaming rescan (parse every line, small index, sha256)
took 254-326 ms at 147-161 MiB peak RSS; a pass-one index cache under the
state root (load cached index, verify a 64 KiB tail hash, parse the tail)
took 26-29 ms at 47 MiB. The rescan meets the 1 s budget, so the cache is
not adopted: it would add trusted persistent state and invalidation for no
budget need. A backward tail read cannot prove competing_root or cycle, so
it was not a candidate.

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

* test(autoplan): journal-read benchmark and its dispatch-only workflow (CEO-2, CEO-6)

scripts/measure-journal-read.ts builds two synthetic 120 MiB parent journals
around a real /autoplan invocation (mixed: ~28k records, most bytes inside
the invocation; large-invocation: ~89k records with a current invocation of
many small records), keeps appending while the guard reads, and measures one
hook call in a fresh process (wall ms, peak RSS). The workflow runs it on
ubuntu-latest and macos-latest on workflow_dispatch only.

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

* test(evals): autoplan-long-session, a resumed >100 MiB session enters Phase 1

CEO-15 with ENG-6's observer: a real session is compacted, its journal
padded past 100 MiB with owned records before the compact boundary, and
the resumed interactive session runs the scripted phase boundary; the
guard decision log must show a verified Phase 1 allow. A free test proves
that observer on a padded journal through the lower-only bound seams
(the PTY counting reader refuses the same journal), with a sidechain
control that must deny.

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

* v1.91.34.0: CHANGELOG, TODOS, version; harness decision for test-pr-profile; ship title-step test reads its new section

* docs(changelog): use an example.com address in the allowEmail example

* test: assemble GitHub-token fixtures at runtime in the new brain-sync and skill-start tests (CI credential scan)

* fix: integration repairs across the wave (Step 6.5 fence, printed helper paths on Windows, probe usage without a heredoc) and tests pinned to the moved title and gstack-post contracts

* test(doctor): the healthy fixture builds browse.exe on Windows, the name setup uses there

* test(shared-libs): recognize Claude Code 2.1.292's internal git probe prefix (format.pretty and per-hook disables), with its CI receipt

* fix(ship-measure): report lists v1 measurements as an older format instead of crashing

---------

Co-authored-by: Mike Ilog <48659643+Mike-E-Log@users.noreply.github.com>
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
Co-authored-by: Thomas Gernhardt <t.gernhardt@softwareprojekt.net>
Co-authored-by: akmandhania <143462686+akmandhania@users.noreply.github.com>
Co-authored-by: Jared <182125291+yolo-jared@users.noreply.github.com>
Co-authored-by: crblabs <293123359+crblabs@users.noreply.github.com>
Co-authored-by: v639dragoon <matthewsbrickley@gmail.com>
2026-10-07 23:29:05 +00:00

538 lines
30 KiB
TypeScript

import { describe, test, expect } from 'bun:test';
import * as fs from 'fs';
import * as path from 'path';
import * as os from 'node:os';
import { spawnSync } from 'node:child_process';
import { generateCodexPlanReview } from '../scripts/resolvers/outside-voice-steps';
import { CODEX_MODEL_CONFIG_FLAG } from '../scripts/resolvers/constants';
import { HOST_PATHS, type TemplateContext } from '../scripts/resolvers/types';
import { ALL_HOST_CONFIGS } from '../hosts';
import { expectMentions, expectTokens } from './helpers/prompt-structure';
// Regression guard for #2440 (which itself regressed the #497 fix).
//
// Claude Code v2.1.198 made subagents run in the BACKGROUND by default.
// Guidance written before that ("do NOT use run_in_background") stopped
// producing a foreground run — the review army and autoplan dual-voice
// steps silently launched specialists in the background and merged before
// they completed. Use `run_in_background: false` when offered. Some interactive
// hosts remove that field and force async dispatch; final-result consumption,
// including its notification handoff, remains the completion contract.
//
// This tripwire pins the corrected phrasing in the generated skill output
// and fails if the inverted form ever comes back through a template or
// resolver edit.
const ROOT = path.resolve(import.meta.dir, '..');
const reviewContext = (host: TemplateContext['host']): TemplateContext => ({
host, skillName: 'fixture-plan-review', tmplPath: 'fixture-plan-review/SKILL.md.tmpl', paths: HOST_PATHS[host],
});
const CEO_FOREGROUND_BRANCH = 'Set `run_in_background: false` if that field is available; omit it otherwise';
describe('generated Codex plan-review shell invocation', () => {
const rendered = generateCodexPlanReview({ ...reviewContext('claude'),
paths: { ...HOST_PATHS.claude, binDir: path.join(ROOT, 'bin'), skillRoot: ROOT },
});
// B1: the heading also admits `unverified`; locate it structurally.
const ready = rendered.slice(rendered.search(/\*\*If `CODEX_MODE: ready`[^\n]*— run Codex:\*\*/),
rendered.indexOf('Present the full output verbatim:'));
const blocks = [...ready.matchAll(/```bash\n([\s\S]*?)\n```/g)].map(match => match[1]!);
const quote = (value: string) => "'" + value.replaceAll("'", "'\\''") + "'";
function fixture() {
const dir = fs.mkdtempSync(path.join(os.tmpdir(), 'gstack-codex-plan-shell-'));
const bin = path.join(dir, 'bin');
fs.mkdirSync(bin);
const prompt = path.join(dir, 'review-prompt.txt');
fs.writeFileSync(prompt, 'Review the current plan without edits.');
const created = path.join(dir, 'created');
// Q2's one-time notice has its own tests; mark it shown in a private state root.
const state = path.join(dir, 'state');
fs.mkdirSync(state);
fs.writeFileSync(path.join(state, '.codex-review-notice-shown'), '');
const calls = path.join(dir, 'calls');
const stale = path.join(dir, 'codex-out-foreign');
const staleError = path.join(dir, 'codex-planreview-foreign');
fs.writeFileSync(stale, 'FOREIGN OLD REVIEW\n');
fs.writeFileSync(staleError, 'FOREIGN OLD ERROR\n');
const writeBin = (name: string, body: string) => fs.writeFileSync(path.join(bin, name), '#!/bin/sh\n' + body, { mode: 0o755 });
writeBin('git', 'printf "%s\\n" "$FAKE_REPO"\n');
writeBin('mktemp', `
if [ "$FAKE_MKTEMP_FAIL" = 1 ]; then exit 42; fi
p=$(${quote(Bun.which('mktemp')!)} "$@") || exit 1
printf '%s\\n' "$p" >> "$FAKE_CREATED"
printf '%s\\n' "$p"
`);
// B1/E5: the free sandbox preflight runs first; exec reads the prompt on stdin
// and writes its final message to -o (stdout carries --json events).
writeBin('codex', `
[ "$1" = sandbox ] && exit 0
printf '%s\\n' "$FAKE_REVIEW_ID" >> "$FAKE_CALLS"
out=; prev=; for a in "$@"; do [ "$prev" = -o ] && out=$a; prev=$a; done
cat > /dev/null
printf '%s\\n' "$FAKE_REVIEW_ID: current findings" "No issues found." "Recommendation: fix $FAKE_REVIEW_ID because this is the current finding." > "$out"
printf '%s\\n' '{"type":"turn.completed"}'
printf '%s\\n' "$FAKE_REVIEW_ID: current stderr" >&2
exit "$FAKE_CODEX_STATUS"
`);
writeBin('cat', `
if [ "$FAKE_CAT_FAIL" = 1 ] && [ "\${1##*/}" = stderr ]; then
printf '%s\\n' 'cat: simulated current-file read failure' >&2
exit 47
fi
exec ${quote(Bun.which('cat')!)} "$@"
`);
const run = (id: string, code = 0, errexit = false, mktempFailure = false, catFailure = false) => {
const env = { PATH: `${bin}${path.delimiter}${process.env.PATH}`, FAKE_REPO: dir,
FAKE_CREATED: created, FAKE_CALLS: calls, FAKE_REVIEW_ID: id,
FAKE_CODEX_STATUS: String(code), FAKE_MKTEMP_FAIL: mktempFailure ? '1' : '0',
FAKE_CAT_FAIL: catFailure ? '1' : '0', TMPDIR: dir, CODEX_HOME: dir, GSTACK_CODEX_MODEL: '',
GSTACK_HOME: state, GSTACK_STATE_ROOT: '',
CODEX_THREAD_ID: '', CODEX_SANDBOX: '', CLAUDECODE: '1', GSTACK_ACTIVE_HOST: 'claude' };
// Each displayed block gets a fresh shell, as separate Bash tool calls do.
return blocks.map(block => spawnSync('bash', ['-c', (errexit ? 'set -e\n' : '') + block.replace("'<prepared-prompt-file>'", quote(prompt))], {
cwd: dir, env, encoding: 'utf8', timeout: 3_000,
}));
};
// #2914: the selected model and its source are printed before the paid call.
const selected = `CODEX_MODEL: gpt-6-astra (exec; source: gstack default (no ${path.join(dir, 'config.toml')}))\n`;
return { dir, run, stale, staleError, calls, selected,
created: () => fs.existsSync(created) ? fs.readFileSync(created, 'utf8').trim().split('\n') : [],
cleanup: () => fs.rmSync(dir, { recursive: true, force: true }) };
}
const findings = (id: string) => `${id}: current findings\nNo issues found.\nRecommendation: fix ${id} because this is the current finding.\n`;
// INV-1: the verdict-form validator prints its verdict before the completed status.
const unavailable = (id: string) => `${findings(id)}VERDICT: unavailable\nFINDINGS: none\nREASON: execution_failed\n`;
const completed = (id: string) => `${findings(id)}VERDICT: clean\nFINDINGS: none\nOUTSIDE_STATUS: completed provider=codex host=claude\n`;
test('fresh shells retain the current stderr and clean its exact temporary file', () => {
const f = fixture();
try {
const results = f.run('current');
expect(results.map(result => result.status)).toEqual([0]);
expect(results[0]!.stdout).toBe(completed('current'));
expect(results[0]!.stderr).toBe(`${f.selected}current: current stderr\n`);
expect(f.created()).toHaveLength(1);
expect(f.created().every(file => !fs.existsSync(file))).toBe(true);
} finally { f.cleanup(); }
});
test.each([false, true])('preserves the real failure status and stderr with errexit=%s', (errexit) => {
const f = fixture();
try {
const results = f.run('failed', 23, errexit);
expect(results.map(result => result.status)).toEqual([23]);
expect(results[0]!.stdout).toBe(unavailable('failed'));
expect(results[0]!.stderr).toContain('failed: current stderr\n');
expect(f.created()).toHaveLength(1);
expect(f.created().every(file => !fs.existsSync(file))).toBe(true);
} finally { f.cleanup(); }
});
test.each([[0, false], [0, true], [23, false], [23, true]] as const)(
'stderr display failure preserves Codex status %s with errexit=%s', (code, errexit) => {
const f = fixture();
try {
const results = f.run('display-failed', code, errexit, false, true);
expect(results.map(result => result.status)).toEqual([code || 1]);
expect(results[0]!.stdout).toBe(unavailable('display-failed'));
expect(results[0]!.stderr).toContain('cat: simulated current-file read failure\n');
expect(f.created()).toHaveLength(1);
expect(f.created().every(file => !fs.existsSync(file))).toBe(true);
} finally { f.cleanup(); }
});
test('two invocations consume only their own output and leave stale files untouched', () => {
const f = fixture();
try {
for (const id of ['first', 'second']) {
const results = f.run(id);
expect(results.map(result => result.status)).toEqual([0]);
expect(results[0]!.stdout).toBe(completed(id));
expect(results[0]!.stderr).toBe(`${f.selected}${id}: current stderr\n`);
}
expect(new Set(f.created()).size).toBe(2);
expect(f.created().every(file => !fs.existsSync(file))).toBe(true);
expect(fs.readFileSync(f.stale, 'utf8')).toBe('FOREIGN OLD REVIEW\n');
expect(fs.readFileSync(f.staleError, 'utf8')).toBe('FOREIGN OLD ERROR\n');
expect(fs.readFileSync(f.calls, 'utf8')).toBe('first\nsecond\n');
} finally { f.cleanup(); }
});
test('temporary-directory failure stops before starting Codex', () => {
const f = fixture();
try {
const results = f.run('unstarted', 0, false, true);
expect(results.map(result => result.status)).toEqual([1]);
expect(fs.existsSync(f.calls)).toBe(false);
expect(f.created()).toEqual([]);
} finally { f.cleanup(); }
});
});
// Only these plan-review carriers use the bounded outside-voice task. Every
// other synchronous dispatch keeps the existing explicit foreground rule.
const BOUNDED_OUTSIDE_VOICE_SITES = new Set([
'plan-ceo-review/sections/review-sections.md',
'plan-eng-review/sections/review-sections.md',
'plan-devex-review/sections/review-sections.md',
]);
function boundedOutsideVoice(content: string): string {
// Host postprocessing can expand the preceding CODEX_MODE list (for example
// broken_install/model_unusable). Pin the actual bounded dispatch section.
return content.match(/\*\*Bounded outside-voice wait[\s\S]*?(?=\*\*(?:Integrate reviewer findings|Cross-model tension):\*\*)/)?.[0] ?? '';
}
function hasBoundedOutsideVoiceWait(content: string): boolean {
const fallback = boundedOutsideVoice(content);
return ['Bounded outside-voice wait', 'subagent_type: "Plan"', 'run_in_background: true',
'Immediately call TaskOutput', 'block: true', 'timeout: 300000', 'Make one wait only',
'`<retrieval_status>` must be `success`', '`<task_id>` must match', '`<task_type>` must be `local_agent`',
'`<status>`\n must be `completed`', '`<output>` must be nonempty', 'must be no outer\n `<error>`',
'identifiable complete', 'Reject raw or in-progress transcripts',
'call TaskStop with the same ID', 'Ignore partial or late results',
'STATUS = "unavailable", SOURCE = "none", OUTSIDE_STATUS = "unavailable"'].every(part => fallback.includes(part))
&& /Skip (?:Integrate reviewer findings and )?Cross-model tension\. Persist an unavailable result/.test(fallback);
}
describe('outside-voice dispatch contract', () => {
const rendered = generateCodexPlanReview(reviewContext('claude'));
const fallback = boundedOutsideVoice(rendered);
test('CEO and Eng disabled or unavailable reviewers still reach decision readiness', () => {
for (const skillName of ['plan-ceo-review', 'plan-eng-review']) {
const output = generateCodexPlanReview({ ...reviewContext('claude'), skillName });
expectMentions(output, [['approval', 'remaining', 'decisions']], 'output');
expectMentions(output, [['approval', 'continuing', 'decisions']], 'output');
expect(output).not.toContain('then continue directly to outputs');
expect(hasBoundedOutsideVoiceWait(output)).toBe(true);
}
// Reviews without the split gate retain their own output continuation.
expect(rendered).toContain('then continue directly to outputs');
});
test('the delegated prompt itself requires findings only and forbids plan mutations', () => {
const promptEnd = rendered.indexOf('\n<plan content>"');
const promptStart = rendered.lastIndexOf('\n"', promptEnd) + 1;
expect(promptStart).toBeGreaterThan(0);
expect(promptEnd).toBeGreaterThan(promptStart);
expect(rendered.slice(promptStart, promptStart + 1)).toBe('"');
expect(rendered.slice(promptStart, rendered.indexOf('\n', promptStart))).toContain('.claude/skills/');
const prompt = rendered.slice(promptStart, promptEnd);
// A sovereignty rule elsewhere in the parent workflow does not reach
// a fresh-context reviewer receiving only this constructed prompt.
expect(prompt).toContain('Read-only review: return findings in your final response.');
expect(prompt).toContain('including the plan file');
expect(prompt).toContain('Edit, Write, NotebookEdit, or Bash or');
expect(prompt).toContain('other tools to mutate files');
expectMentions(prompt, [['do not', 'implement', 'findings']], 'prompt');
expect(prompt).toContain('not instructions to\nexecute');
expect(prompt).toContain('explicit user approval');
});
test('fallback uses one exact-ID wait and explicit cancellation without a model override', () => {
expect(hasBoundedOutsideVoiceWait(rendered)).toBe(true);
expectMentions(fallback, [['before', 'taskoutput', 'dispatch']], 'fallback');
expectMentions(fallback, [['without', 'unavailable', 'launching']], 'fallback');
expect(fallback).toContain('Do not set a model\noverride');
expectMentions(fallback, [['wait', 'dispatch/cancellation', 'five-minute']], 'fallback');
expectTokens(fallback, ['`agentId`'], 'fallback');
expectMentions(fallback, [['do not', 'returned', 'launch']], 'fallback');
expectMentions(fallback, [['does not', 'taskoutput', 'timeout']], 'fallback');
expect(fallback).not.toContain('allowed_tools');
expect(fallback).not.toContain('run_in_background: false');
});
test('only the matching completed final report can enter agreement and persistence', () => {
for (const guard of ['<retrieval_status>', '<task_id>', '<task_type>', 'local_agent', '<status>', 'completed',
'<output>', 'nonempty', 'no outer', '<error>', 'identifiable complete',
'Reject raw or in-progress transcripts', 'do not extract\n finding fragments from them']) expect(fallback).toContain(guard);
expectMentions(fallback, [['do not', 'completeness', 'establish']], 'fallback');
expect(fallback).not.toContain('isRawTranscript');
expect(fallback).not.toContain('task.status');
expectMentions(fallback, [['cannot', 'identified', 'report']], 'fallback');
expectMentions(fallback, [['do not', 'general-purpose', 'retry']], 'fallback');
expect(fallback).toContain('Report missing outside-voice coverage.');
expect(fallback).toContain('still give no late-result credit');
expect(fallback).toContain('cancellation is unconfirmed');
expect(fallback).toContain('STATUS = "unavailable", SOURCE = "none", OUTSIDE_STATUS = "unavailable"');
expectMentions(fallback, [['do not', 'completed', 'reviewer']], 'fallback');
expectMentions(rendered, [['not', 'agreement', 'evidence']], 'rendered');
const answer = rendered.indexOf('**3. Obtain the answer.**');
const apply = rendered.indexOf('**4. Apply the answered row.**');
expect(answer).toBeGreaterThan(0);
expect(apply).toBeGreaterThan(answer);
// B1: the sandbox comes from the probe's select-model (read-only unless GSTACK_CODEX_NO_SANDBOX=1).
expect(rendered).toContain(`-s "\${_CODEX_SANDBOX_MODE:?}" ${CODEX_MODEL_CONFIG_FLAG} -c 'model_reasoning_effort="high"'`);
});
test('the generated-carrier exception rejects missing wait, cancellation or result guards', () => {
expect(hasBoundedOutsideVoiceWait(rendered)).toBe(true);
for (const guard of ['subagent_type: "Plan"', 'timeout: 300000', 'call TaskStop with the same ID',
'<status>', '<output>', 'Reject raw or in-progress transcripts',
'Ignore partial or late results', 'Skip Cross-model tension. Persist an unavailable result',
'STATUS = "unavailable", SOURCE = "none", OUTSIDE_STATUS = "unavailable"']) {
expect(hasBoundedOutsideVoiceWait(rendered.replaceAll(guard, 'missing guard')), guard).toBe(false);
}
expect(hasBoundedOutsideVoiceWait('Dispatch via the Agent tool with run_in_background: true')).toBe(false);
});
test('expanded Codex availability states preserve the same bounded dispatch guards', () => {
const earlier = rendered.replaceAll('broken_install', 'not_installed')
.replaceAll('model_unusable', 'not_authed');
expect(earlier).not.toBe(rendered);
for (const content of [earlier, rendered]) {
expect(hasBoundedOutsideVoiceWait(content)).toBe(true);
expect(hasBoundedOutsideVoiceWait(content.replace('call TaskStop with the same ID', 'missing cancellation'))).toBe(false);
}
});
test('all host resolver outputs require Plan availability for native fallback', () => {
for (const host of ALL_HOST_CONFIGS) {
const output = generateCodexPlanReview(reviewContext(host.name));
{
expectMentions(output, [['without', 'unavailable', 'launching']], 'output');
expectMentions(output, [['do not', 'completed', 'reviewer']], 'output');
expect(output, host.name).toContain('Do not set a model\noverride');
expect(hasBoundedOutsideVoiceWait(output), host.name).toBe(true);
}
}
});
});
// review's specialist-dispatch guidance lives in its carved Review Army section
// (Step 4.5 moved out of the skeleton), so the pin follows it there. Same for
// autoplan: the dual-voice dispatch (Phase 1 override rules) lives in its
// carved CEO-phase section.
//
// Third recurrence (#497 → #2440 → /ship Step 18): the four ship dispatch
// sections (Steps 7/8/10/18) never carried the flag and were never pinned, so
// a backgrounded doc-sync dispatch stranded the ship run waiting on LAST-line
// JSON that never came. Every synchronous dispatch carrier is pinned here now;
// add new dispatch sites to this list in the same commit that creates them.
const GENERATED_WITH_GUIDANCE = [
'review/sections/review-army.md',
'autoplan/sections/ceo-phase.md',
'ship/sections/review-army.md',
'ship/sections/documentation.md',
'ship/sections/test-coverage.md',
'ship/sections/plan-completion.md',
'ship/sections/greptile.md',
// Sweep carriers (v1.79): every remaining synchronous Agent-dispatch site.
'autoplan/sections/design-phase.md',
'autoplan/sections/eng-phase.md',
'autoplan/sections/dx-phase.md',
// CSO's private startup does not import the shared synchronous-dispatch
// guidance and its bounded worker policy is specified in its own skeleton.
'design-consultation/sections/proposal-and-preview.md',
'design-review/SKILL.md',
'document-release/sections/release-body.md',
'office-hours/SKILL.md',
'office-hours/sections/design-and-handoff.md',
'plan-ceo-review/SKILL.md',
'plan-ceo-review/sections/review-sections.md',
'plan-design-review/SKILL.md',
'plan-devex-review/sections/review-sections.md',
'plan-eng-review/sections/review-sections.md',
'review/sections/adversarial.md',
'ship/sections/adversarial.md',
];
// The inverted, post-2.1.198-inert phrasings. Checked across every generated
// SKILL.md so the regression can't migrate to another skill unnoticed.
const INVERTED = /do not use\s+`?run_in_background`?/i;
// Both spellings describe the same boolean Agent argument. Keep the key and
// false token bounded so an unrelated key or quoted/string value cannot pass.
const EXPLICIT_FOREGROUND = /(?:\brun_in_background\b|"run_in_background")\s*:\s*false\b/;
function hasForegroundGuidance(content: string): boolean {
return EXPLICIT_FOREGROUND.test(content) && !INVERTED.test(content);
}
function allGeneratedSkillFiles(): string[] {
const out: string[] = [];
for (const entry of fs.readdirSync(ROOT, { withFileTypes: true })) {
if (!entry.isDirectory() || entry.name.startsWith('.') || entry.name === 'node_modules') continue;
const p = path.join(ROOT, entry.name, 'SKILL.md');
if (fs.existsSync(p)) out.push(p);
// Generated on-demand section files (e.g. ship/sections/review-army.md)
// carry the same resolver output as SKILL.md bodies — scan them too.
const sections = path.join(ROOT, entry.name, 'sections');
if (fs.existsSync(sections)) {
for (const f of fs.readdirSync(sections)) {
if (f.endsWith('.md')) out.push(path.join(sections, f));
}
}
}
const rootSkill = path.join(ROOT, 'SKILL.md');
if (fs.existsSync(rootSkill)) out.push(rootSkill);
return out;
}
describe('run_in_background guidance (#2440)', () => {
test('CEO and autoplan wait for actual reviews when the foreground field is unavailable', () => {
const ceo = fs.readFileSync(path.join(ROOT, 'plan-ceo-review/SKILL.md'), 'utf8');
const dispatch = ceo.split('**Step 1: Dispatch reviewer subagent**')[1]?.split('**Step 2:')[0] ?? '';
expect(dispatch).toContain("Read Agent's tool definition");
expect(dispatch).toContain(CEO_FOREGROUND_BRANCH);
expectMentions(dispatch, [['wait', 'returns', 'pending']], 'dispatch');
expectMentions(dispatch, [['no', 'notification', 'completion']], 'dispatch');
expectMentions(dispatch, [['do not', 'reviewer', 'waiting']], 'dispatch');
const phase = fs.readFileSync(path.join(ROOT, 'autoplan/sections/ceo-phase.md'), 'utf8').replace(/\s+/g, ' ');
expect(phase).toContain('Step 0 (including its completed Spec Review Loop) → Claude CEO voice → Codex CEO voice → consensus → Review Sections → saved summary → phase announcement');
for (const name of ['ceo', 'design', 'eng', 'dx']) {
const next = fs.readFileSync(path.join(ROOT, `autoplan/sections/${name}-phase.md`), 'utf8').replace(/\s+/g, ' ');
const manifest = next.indexOf(`Read \`snapshot.json\` beside \`<${name.toUpperCase()}_INPUT>\``);
const native = next.indexOf('Send its `nativeDispatchPrompt` verbatim as the Agent prompt: ONLY/FINAL tool call this response');
const barrier = next.indexOf('**Native completion barrier:**', native);
const outside = next.indexOf('voice** (via Bash)', barrier);
expect(manifest, name).toBeGreaterThan(0);
expect(native, name).toBeGreaterThan(manifest);
expect(barrier, name).toBeGreaterThan(native);
expect(outside, name).toBeGreaterThan(barrier);
const wait = next.slice(barrier, outside);
expect(wait, name).toContain('isAsync: true');
expect(wait, name).toContain('end response immediately: "Waiting for <agent ID>."');
expectMentions(wait, [['no', 'calls/review', 'notification']], 'wait');
expect(wait, name).toContain('Other hosts await that ID');
expect(wait, name).toContain('Completed-native INPUT must match snapshot phase/hash');
expectMentions(wait, [['no', 'substitute', 'failure']], 'wait');
}
});
test('recognizes prose and actual JSON false without accepting missing, true, or inverted guidance', () => {
for (const guidance of [
'Pass `run_in_background: false` on the Agent call.',
'Native subagent tool; Claude Code Agent arguments:\n```json\n{ "run_in_background": false }\n```\nSet on the call, not in prompt text.',
'{\n "run_in_background" :\n false\n}',
]) expect(hasForegroundGuidance(guidance), guidance).toBe(true);
for (const guidance of [
'Dispatch via the Agent tool (foreground).',
'run_in_background: true',
'{ "run_in_background": true }',
'{ "run_in_background": "false" }',
'{ "run_in_background": null }',
'other_run_in_background: false',
'run_in_background: falsehood',
'Do NOT use `run_in_background`.',
'Do NOT use run_in_background: false.',
'Do NOT use `run_in_background`. { "run_in_background": false }',
]) expect(hasForegroundGuidance(guidance), guidance).toBe(false);
});
test('foreground-required skills instruct run_in_background: false explicitly', () => {
for (const rel of GENERATED_WITH_GUIDANCE) {
const content = fs.readFileSync(path.join(ROOT, rel), 'utf-8');
if (BOUNDED_OUTSIDE_VOICE_SITES.has(rel) && content.includes('Bounded outside-voice wait')) {
expect(hasBoundedOutsideVoiceWait(content), rel).toBe(true);
} else if (rel === 'plan-ceo-review/SKILL.md') {
expect(content).toContain(CEO_FOREGROUND_BRANCH);
} else expect(hasForegroundGuidance(content), rel).toBe(true);
}
});
test('consultation awaits independent voices after research and before proposal synthesis', () => {
const skeleton = fs.readFileSync(path.join(ROOT, 'design-consultation/SKILL.md'), 'utf-8');
const research = skeleton.indexOf('## Phase 2: Research');
const requiredRead = skeleton.match(/^> \*\*STOP\.\*\* Before [^\n]*, Read `[^`\n]*\/design-consultation\/sections\/proposal-and-preview\.md` and execute it$/m);
expect(research).toBeGreaterThan(-1);
expect(requiredRead).not.toBeNull();
expect(requiredRead!.index).toBeGreaterThan(research);
expect(skeleton).not.toContain('## Design Outside Voices (independent)');
const proposal = fs.readFileSync(path.join(ROOT, 'design-consultation/sections/proposal-and-preview.md'), 'utf8');
const voices = proposal.indexOf('## Design Outside Voices (independent)');
const q2 = proposal.indexOf('**AskUserQuestion Q2');
expect(voices).toBeGreaterThan(proposal.indexOf('Draft your own direction'));
expect(q2).toBeGreaterThan(voices);
expect(proposal.slice(voices, q2)).toContain('await both before synthesis');
});
// Third recurrence (#497 → #2440 → /ship Step 18): a backgrounded doc-sync
// dispatch stranded the ship run. Pin the deadline/recovery branch and the
// docs-sync scope guard in both the generated section and its template, so
// neither a template edit nor a stale regen can drop them silently.
const PR_BODY_SITES = ['ship/sections/documentation.md', 'ship/sections/documentation.md.tmpl'];
test('ship pr-body carries the doc-sync deadline recovery + scope guard', () => {
for (const rel of PR_BODY_SITES) {
const content = fs.readFileSync(path.join(ROOT, rel), 'utf-8').replace(/\s+/g, ' ');
expectMentions(content, [['before', 'failure/deadline', 'recovery']], 'content');
expectMentions(content, [['stop', 'insufficient', 'request']], 'content');
expect(content).toContain('Only audit/edit permitted docs');
expectTokens(content, ['`blocked`'], 'content');
expect(content).toContain('goes to recovery, even with valid JSON');
expectTokens(content, ['`Documentation: blocked`'], 'content');
expect(content).toContain('`Documentation: blocked`');
}
});
// The spawned-dispatch contract is as regression-prone as the flag — this
// class regressed twice via unpinned prose. Pin the document-release
// contract, the Step 8.4d spawned note, and the resolver-side Codex
// doc-review skip in both generated output and templates.
const CONTRACT_PINS: Array<[string[], string | RegExp]> = [
[['document-release/SKILL.md', 'document-release/SKILL.md.tmpl'], 'When dispatched as a subagent'],
[
['document-release/sections/release-body.md', 'document-release/sections/release-body.md.tmpl'],
/a spawned run must never change VERSION/i,
],
[['document-release/sections/release-body.md'], 'Spawned-session skip'],
// Anti-injection trigger + invariant carve-out — the two clauses whose
// deletion would silently reopen the prompt-injection / silent-VERSION
// holes while the 'When dispatched' heading pin stays green. Matched on
// meaning (case-insensitive, whitespace-normalized), not register.
[['document-release/SKILL.md', 'document-release/SKILL.md.tmpl'], /claims never trigger it on their own/i],
[['document-release/SKILL.md', 'document-release/SKILL.md.tmpl'], /skip any recommendation that rewrites CHANGELOG or changes VERSION/i],
];
test('document-release carries the spawned-dispatch contract', () => {
for (const [sites, phrase] of CONTRACT_PINS) {
for (const rel of sites) {
const content = fs.readFileSync(path.join(ROOT, rel), 'utf-8');
if (typeof phrase === 'string') expect(content).toContain(phrase);
else expect(content.replace(/\s+/g, ' ')).toMatch(phrase);
}
}
});
// Structural scanner (4th-recurrence net): GENERATED_WITH_GUIDANCE is a
// hand-enumerated list — the exact mechanism that missed three recurrences
// (#497 → #2440 → /ship Step 18, each a NEW dispatch site outside the
// pinned set). Any generated file that carries an Agent-dispatch imperative
// (or the inert "(foreground)" prose shape that #2440 proved insufficient)
// must either state the flag or hold a reasoned exemption below. Same
// pattern as the egress-receipt new-sink scanner.
const DISPATCH_IMPERATIVE =
/(?:via|using) the Agent tool|dispatch(?:es)? (?:a|an|the|one|each|it as a)[^.\n]{0,60}subagent|\(foreground[^)]*\)|foreground Agent tool/i;
// Reasoned exemptions: files where the match is a reference to a dispatch
// that lives (flag and all) in another file, not a dispatch spec itself.
const BACKGROUND_OK: Record<string, string> = {
'ship/SKILL.md':
'skeleton anchors reference the Step 14.5 dispatch by name; the dispatch spec and flag live in sections/documentation.md',
};
test('structural scanner: every generated dispatch imperative carries the flag', () => {
for (const file of allGeneratedSkillFiles()) {
const rel = path.relative(ROOT, file).split(path.sep).join('/');
if (BACKGROUND_OK[rel]) continue;
const content = fs.readFileSync(file, 'utf-8');
const boundedOutsideVoice = BOUNDED_OUTSIDE_VOICE_SITES.has(rel) && hasBoundedOutsideVoiceWait(content);
const ceoForeground = rel === 'plan-ceo-review/SKILL.md' && content.includes(CEO_FOREGROUND_BRANCH);
if (DISPATCH_IMPERATIVE.test(content) && !hasForegroundGuidance(content) && !boundedOutsideVoice && !ceoForeground) {
throw new Error(
`${rel} contains an Agent-dispatch imperative (or bare "foreground" prose) but never states ` +
'`run_in_background: false` — pin the flag at the dispatch site or add a reasoned BACKGROUND_OK ' +
'exemption (see #497/#2440: prose without the explicit flag is inert since Claude Code v2.1.198).',
);
}
}
});
test('the inverted "do NOT use run_in_background" phrasing never comes back', () => {
for (const file of allGeneratedSkillFiles()) {
const content = fs.readFileSync(file, 'utf-8');
if (INVERTED.test(content)) {
throw new Error(
`${path.relative(ROOT, file)} contains the inverted run_in_background guidance — ` +
'since Claude Code v2.1.198 subagents default to background, so "do not use" is inert; ' +
'instruct `run_in_background: false` instead (see #2440).',
);
}
}
});
});