* feat(#3841): assert gsd-tools identity before any state-mutating verb only this package publishes. The path-based branches — a project-local install, a runtime config directory — had no such guarantee; they trusted their configured location. This closes them. Mechanism: once resolution finishes, and before any verb runs, the preamble probes the tool it picked with `runtime-identity --raw` and matches the answer with a shell `case` pattern ANCHORED to the start of the compact payload (`{"packageName":"@opengsd/gsd-core"`). An unanchored substring match accepts the decoy `{"packageName":"get-shit-done-cc","note":"@opengsd/gsd-core"}`, which any colliding package could publish. The outcome is exported as the two-valued `GSD_IDENTITY_STATUS` (`ok`/`unverified`), so the gate is asserted on a VALUE rather than on warning prose. Rollout is warn-then-fail per the #3146 ruling: `unverified` prints one line naming BOTH causes and continues, because `no_identity_verb` cannot tell a foreign package from an `@opengsd/gsd-core` older than the verb, and at rollout the old-version case is the common one. The blocker was byte budget, not design. The preamble is inlined into 112 shipped files and several sat within single-digit bytes of frozen ceilings (`gsd-verifier.md` 16 bytes, `gsd-executor.md` 33, `execute-phase.md` 234); a first attempt broke five of them. What made room was collapsing the resolver's twenty near-identical `elif [ -f … ]` arms into one candidate-list helper (`_gsd_at`), which buys far more than the assertion costs. The preamble is now 2,624 bytes against 4,500 — a net 1,876 bytes SMALLER per inlined file, so every capped file moved away from its ceiling rather than toward it. No cap raised, no size-budget exception added, no override token emitted. Resolution order, every runtime-home probe, the `unset -f gsd_run` re-source fix, the fail-closed `exit 1`, and the `CLAUDE_ENV_FILE` persistence are all preserved byte-for-byte in substring terms; the snippet still begins with `_GSD_SHIM_NAME=` and still ends with `fi`, which the parity extractors anchor on. `gsd-core/references/gsd-run-resolver.md` is re-synced byte-equal. Also fixes two stale claims found in passing: CONTEXT.md and FEATURES.md both described an `[ -x ]` guard as the load-bearing re-source defense. That guard was tried and REMOVED in #3831 — it rejected the bare function name, fell through every branch, and hit `exit 1`, which kills a sourced caller's shell. `unset -f gsd_run` is the actual mechanism. Refs #3841 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * fix(#3841): pair the anchor's brace by requiring a closed identity payload The matrix went red on `tests/new-project-mvp-prompt.test.cjs` — "new-project.md has unbalanced braces: net depth 2" — plus a knock-on report from its parent `bug #1516` describe, which is the same failure counted once at the child and once at the block. Root cause: that guard (:182-189, mirroring #3784 bd53925f) walks characters and increments on `{`, decrements on `}`, with no awareness of shell quoting. It scans `new-project.md` PLUS every `new-project/steps/*.md`, and both `new-project.md` and `steps/auto-mode-config.md` carry one inlined preamble copy — hence net 2 from a snippet that was off by exactly one. The unpaired brace was the `{` inside the single-quoted `case` pattern of the identity anchor, which is correct shell and invisible to a text scanner. Fix in the snippet, not the guard. The pattern now anchors at BOTH ends: `'{"packageName":"@opengsd/gsd-core"'*'}'`. That balances 51/51 with a brace that does real work rather than a cosmetic pair — a truncated payload whose prefix matches now fails too, where before it verified. Safe for any future additive field: a JSON object's own closing brace is always the last character, whatever type the last value has, which is pinned by two negative-space tests (a nested object and an array-valued last key must both still verify). Cost: +3 bytes, against the 1,873 the resolver fold already gave back. The alternative considered and rejected was dropping the literal `{` for a `?` glob. It balances too, but weakens the anchor from "must be an opening brace" to "must be any one character", and the anchor is the entire point. Two guards added so this cannot recur silently: - runtime-launcher-parity (F0) pins brace balance at the SNIPPET, so the next edit to that pattern fails on the file it broke instead of surfacing three files downstream in a test whose name mentions neither the launcher nor this issue. It also asserts depth never goes negative, since a `}` preceding its `{` nets to zero while being unbalanced at every prefix. - runtime-identity gains behavioral truncated-payload and trailing-garbage fixtures, so the added `}` is proven load-bearing rather than merely present. Verified: snippet 51/51 braces; new-project combined net depth 0; the seven other preamble-bearing files with nonzero depth are unchanged from merged next (their own prose, not the preamble, and not in any guard's scan set); all 112 inlined copies and the resolver reference re-synced byte-equal; sync:launcher idempotent on the second run. Refs #3841 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * chore(#3841): backfill changeset PR number Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> --------- Co-authored-by: sim <sim@local> Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
Tom Boucher
@@ -608,6 +608,46 @@ describe('runtime-launcher-parity (#373)', () => {
|
||||
}
|
||||
});
|
||||
|
||||
// ─── (F0) Brace balance — the preamble is inlined into brace-counted files ──
|
||||
//
|
||||
// Regression for the #3841 red matrix run. The preamble is inlined into 112
|
||||
// shipped files, and several downstream guards balance braces by scanning raw
|
||||
// TEXT with no string-context awareness — tests/new-project-mvp-prompt.test.cjs's
|
||||
// "balanced braces" guard (mirroring #3784 bd53925f) counts every `{` and `}`
|
||||
// across new-project.md plus its steps/. new-project.md and
|
||||
// new-project/steps/auto-mode-config.md each carry one preamble copy, so a
|
||||
// snippet that is off by one reports a combined net depth of TWO, in a test whose
|
||||
// name mentions neither the launcher nor this issue.
|
||||
//
|
||||
// The identity assertion's `case` pattern legitimately contains a `{` inside a
|
||||
// single-quoted shell literal. It is paired by requiring the payload to be a
|
||||
// CLOSED object (`*'}'`) — which is also a real strengthening, since a truncated
|
||||
// payload then fails. Pin the balance HERE, at the snippet, so the next edit to
|
||||
// that pattern fails on the file it broke rather than three files downstream.
|
||||
test('(F0) the snippet has balanced braces (#3841 — inlined into brace-counted files)', () => {
|
||||
const snippetContent = fs.readFileSync(SNIPPET_FILE, 'utf8');
|
||||
let depth = 0;
|
||||
let minDepth = 0;
|
||||
for (const ch of snippetContent) {
|
||||
if (ch === '{') depth++;
|
||||
if (ch === '}') depth--;
|
||||
if (depth < minDepth) minDepth = depth;
|
||||
}
|
||||
assert.equal(
|
||||
depth,
|
||||
0,
|
||||
`_runtime-launcher.snippet.sh has unbalanced braces: net depth ${depth}. ` +
|
||||
`The preamble is inlined into 112 shipped files, and downstream guards ` +
|
||||
`(tests/new-project-mvp-prompt.test.cjs) balance braces over raw text with no ` +
|
||||
`awareness of shell quoting — an unpaired brace here fails there instead, ` +
|
||||
`multiplied by the number of inlined copies in the scanned file set. ` +
|
||||
`Pair the brace in the snippet; do not relax the downstream guard.`,
|
||||
);
|
||||
// Never dips below zero: a `}` that precedes its `{` would still net to 0 while
|
||||
// being unbalanced at every prefix, which is what a text scanner actually reports.
|
||||
assert.equal(minDepth, 0, `brace depth went negative (min ${minDepth}) — a closing brace precedes its opener`);
|
||||
});
|
||||
|
||||
// ─── (F) Regression locks: no /gsd-tools substring; no do.md dispatcher false-positive ──
|
||||
test('(F) snippet has no /gsd-tools substring; do.md has no /gsd[:-][a-z] matches', () => {
|
||||
// (F1) The snippet must not contain the literal substring /gsd-tools.
|
||||
|
||||
Reference in New Issue
Block a user