* test(#4748): pin the letter-axis defect at the seven shell sites outside #4660's six
Extends tests/nsegment-phase-grammar.test.cjs one class over: for each of the
seven sites the live shell lines are read off disk by anchor and executed in
bash against a letter-suffixed fixture. The four `$((10#$PHASE_INT))` split
sites must yield PHASE_N without a shell error for `03A` / `12A` / `3A` /
`03A.1.2` and the commit-scope ERE they build must match both `feat(3A-01):`
and `feat(03A-1):`; the review-file lookup must bind init's `padded_phase`
rather than re-pad in shell; the `--from`/`--to`/`--only` and
plan-review-convergence extractions must return `12A` / `23A.1.2` (and
`23.1.2`) whole; the legacy normalizer must pad `3A` to `03A` and must not
mangle an already-padded `08`. Every pre-existing shape (`06`, `08.5`,
`23.1.2`, `36.14`) is a regression control.
tests/init.test.cjs asserts `init execute-phase` emits `padded_phase` for a
directory-backed `03A`, a ROADMAP-only `4B` (→ `04B`), the existing ROADMAP
fallback `1` (→ `01`), and `null` when the phase is not found.
Negative control against the unfixed tree: 41 failures in the grammar file,
exactly the "(fails before the fix)" cases and the three derived from them
(scope ERE, three-flag extraction, the `08` octal trap); 2 in init.test.cjs,
both the new assertions. Every regression control already green.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017cjzdZtYjcBAa3Lqh2VrLK
* fix(#4748): carry a letter-suffixed phase id through the seven shell sites that aborted or truncated it
The canonical phase-number grammar (src/phase-id.cts) is digits, an optional
uppercase letter, then dotted segments — `12A`, `3A`, `23A.1.2` are documented
shapes that `init`, `phase-id.cts` and `phase remove` renumbering already
round-trip. Seven shell sites in shipped workflows and references still
assumed digits-and-dots. Four classes, one fix each:
Class 1 — `PHASE_INT=${PHASE_NUMBER%%.*}; $((10#$PHASE_INT))` (execute-phase.md
×2, completion-reconciliation.md, tdd.md). The post-#4619 split stops at the
first DOT, so on `03A` the "integer" is `03A` and bash aborts with `value too
great for base`. Split at the first NON-DIGIT instead (`%%[!0-9]*`): the
integer half is a pure digit run, and the letter rides along in the rest the
way the dotted fraction already did — `03A.1.2` → PHASE_N `3A\.1\.2`, so the
#4003 zero-pad-tolerant scope ERE matches both `feat(3A-01):` and
`feat(03A-1):`. Byte-identical output for every id that worked before.
Class 2 — `PADDED=$(printf "%02d" "${PHASE_NUMBER}")` before the REVIEW.md
lookup (execute-phase.md). `printf` cannot pad a letter id (prints `03`,
exits 1) — and cannot even re-pad an already-padded `08`, which bash reads as
an invalid octal and prints as `00`, so the lookup resolved phases 08 and 09
to `00-REVIEW.md` today. The disk path hands the workflow the directory's
padded number but the ROADMAP fallback hands it the heading's bare one, which
is why the re-pad existed. `cmdInitExecutePhase` now emits `padded_phase`
through `normalizePhaseName`, exactly as the plan-phase and code-review inits
do, and the workflow binds `{padded_phase}` instead of re-deriving.
Class 3 — `grep -oE '[0-9]+\.?[0-9]*'` (autonomous.md `--from`/`--to`/`--only`,
plan-review-convergence.md). Stops at the letter, so `--from 12A` ran from
phase 12 with no error. Now the canonical ERE `[0-9]+[A-Z]?(\.[0-9]+)*`, which
also closes the single-segment dot-axis gap the same shape carried (`23.1.2`
→ `23.1`, #4568's class in a spelling neither lint saw).
Class 4 — the legacy manual normalizer (phase-argument-parsing.md, reached
from mvp-phase.md). Its two branches (`^[0-9]+$`, `^[0-9]+\.[0-9]+$`) left
`12A` unpadded and never padded `3A` to the `03A` a directory carries; its
integer branch also hit the same `printf` octal trap on `08`. One branch for
the whole canonical token now, padding the digit run via `$((10#…))`.
Whether this legacy surface should instead be retired in favour of `init`'s
normalization is the maintainer call the issue names; extending it keeps the
documented contract true either way.
Driven end to end: `init execute-phase 3A` on a fixture with a
`03A-letter-variant/` directory emits `phase_number: "03A"` and now
`padded_phase: "03A"`; on a ROADMAP-only `### Phase 4B:` it emits `"4B"` /
`"04B"`. The issue's own evidence line claimed `padded_phase` was already in
the execute-phase init output — it was not; that key is emitted by the
code-review / plan-phase inits, which is where the claim was read from.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017cjzdZtYjcBAa3Lqh2VrLK
* chore(#4634): extend lint-phase-id-drift with three ratchets for letter-hostile phase-id consumers
The rules that landed with #4619, #4568 and #4660 police grammar MIRRORS —
regexes that describe a phase id. The #4748 sites are CONSUMERS of one, and
every existing rule reported clean on them: the shell-arithmetic rule's
`_INT` escape trusts a NAME the dot-only split did not earn on `03A`; the
`[0-9]+\.?[0-9]*` shape is neither the bounded form the single-segment rule
bans nor the unbounded form the letterless rule inspects; and nothing looked
at `printf "%02d"` at all. Three narrow additions, one per shape:
- findDotOnlyIntegerSplitDrift — `X_INT=${<phase-var>%%.*}`; the safe split
is `%%[!0-9]*`. Keys on the SOURCE variable being phase-carrying.
- findLooseDottedPhaseRegexDrift — `[0-9]+\.?[0-9]*` / `\d+\.?\d*` on a
phase-carrying line; the canonical form is `[0-9]+[A-Z]?(\.[0-9]+)*`.
Disjoint from the two sibling regex rules by construction.
- findShellPhasePrintfPadDrift — `printf "%0Nd" …` whose arguments name a
phase-carrying, non-`_INT` variable; a pad of an `_INT` via `$((10#…))`
and a `{padded_phase}` binding are the sanctioned shapes.
Same `<!-- phase-id-owner: … -->` sanction, same scan roots as their nearest
sibling (shell idioms over workflows + references, the regex shape over
workflows + references + agents), same documented limit of a per-line
textual scan. The post-#4619 comment that described the `_INT` convention
as proven by `%%.*` is corrected to name the digit-run split. Confirmed
against the base commit: each rule fires on exactly its own unfixed sites
(2+1+1, 3+1, 1+1) and zero violations remain on the fixed tree.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017cjzdZtYjcBAa3Lqh2VrLK
* docs(#4748): add Fixed changeset
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017cjzdZtYjcBAa3Lqh2VrLK
* chore(#4748): refresh the compact-content benchmark baseline and acknowledge emitted growth
The three top-level workflow files below grew by the letter-aware split, the
canonical extraction ERE, the `{padded_phase}` binding, and the comment lines
that name the grammar each site now honours. The committed compact-content
benchmark moved with them; refreshed with `benchmark-compact-content.cjs
--write` (aggregate reduction 15.47% -> 15.45%).
Emitted-Drift-Ack-Growth: execute-phase.md — #4748: first-non-digit PHASE_INT split at the plan-selection and TDD-gate sites, `{padded_phase}` binding at the REVIEW.md lookup, and the comments naming why (482 bytes)
Emitted-Drift-Ack-Growth: autonomous.md — #4748: canonical `[0-9]+[A-Z]?(\.[0-9]+)*` at the --from/--to/--only extractions plus one comment naming the grammar (249 bytes)
Emitted-Drift-Ack-Growth: plan-review-convergence.md — #4748: canonical `[0-9]+[A-Z]?(\.[0-9]+)*` at the phase extraction plus one comment naming the grammar (160 bytes)
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017cjzdZtYjcBAa3Lqh2VrLK
* fix(#4748): name padded_phase in execute-phase.md's init parse list
A `{field}` token inside a workflow bash block is substituted from the init
JSON only for fields the workflow tells the model to parse. `phase_number`
is on that list; `padded_phase` was not, so the `PADDED="{padded_phase}"`
binding at the review lookup would have been a literal — for every phase,
not only letter ones. Found by the pre-file adversarial review (claim 2, the
author's own named suspicion); the test now asserts the parse list carries
the field beside `phase_number`.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017cjzdZtYjcBAa3Lqh2VrLK
* chore(#4634): key the dot-only split rule on its source and widen the printf rule to any %d form
Two false negatives from the pre-file adversarial review of the three #4748
ratchets: `PHASE_PREFIX=${PHASE_NUMBER%%.*}` escaped the split rule because
the destination did not end in `_INT` (the defect is the split, not the
name it lands in), and `printf '%02d'` / `printf "%2d"` escaped the printf
rule because it required double quotes and the zero flag (`%d` cannot parse
a letter id under any width). Both rules now key on the phase-carrying
SOURCE alone; base-site firing counts are unchanged (2+1+1, 1+1) and the
fixed tree stays at zero. The `[[:digit:]]` spelling and the `/phase/i`
heuristic remain the sibling rules' documented limits.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017cjzdZtYjcBAa3Lqh2VrLK
* chore(#4748): refresh the compact-content benchmark baseline after the parse-list edit
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017cjzdZtYjcBAa3Lqh2VrLK
* test(#4748): compose init's emitted padded_phase through the live REVIEW.md lookup
The Class 2 site is a `{padded_phase}` template token, which no test can
execute as written. This substitutes the value init emits
(`normalizePhaseName`) into the three live lookup lines and runs them
against a fixture, so the emitted value, the binding, the path construction
and the status extraction are exercised together — `03A-REVIEW.md` and
`08-REVIEW.md` each resolve to their own status. Suggested by the resumed
adversarial review pass (claim C).
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017cjzdZtYjcBAa3Lqh2VrLK
* test(#4748): move the #4619 and #4003 source-parity pins to the letter-safe split
tests/execute-phase-decimal-arithmetic.test.cjs and
tests/safe-resume-gate-anchoring.test.cjs pin the four Class 1 sites'
snippet byte-for-byte, so the first-non-digit split reddened both in the
whole-suite run (scripts/ci-test-scope.cjs does not select either file for
a workflow edit — the scoped run was green). The pinned snippet is now the
shipped one, and the behavioural half of the #4619 file gains the letter
case (`03A` → `3A`, `23A.1.2` → `23A\.1\.2`) beside its decimal cases.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017cjzdZtYjcBAa3Lqh2VrLK
* chore(#4634): key the dot-only split rule on the _INT destination again, tolerating the quoted spelling
Keying on the source alone (the previous commit's widening, from a review
probe) flags `PARENT_PHASE="${PHASE_NUMBER%%.*}"` in
gap-closure-artifacts.md — a correct derivation that wants everything
before the first dot, letter included. The defect this rule polices is a
dot split INTO the name the shell-arithmetic rule trusts as an integer, so
`_INT` is the discriminator on purpose; the quoted spelling that site uses
is now tolerated so the same shape into an `_INT` cannot hide behind it.
Base-site firing unchanged (2+1+1), zero on the fixed tree, and the
parent-phase line is pinned as a silent case.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017cjzdZtYjcBAa3Lqh2VrLK
* test(#4748): use t.after() for the composition test's fixture cleanup
CONTRIBUTING forbids try/finally inside a test body; the per-test cleanup
form is `t.after(() => cleanup(dir))`. Flagged by the filing driver's
test-ruleset gate before the PR was created.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017cjzdZtYjcBAa3Lqh2VrLK
* chore(#4748): set changeset fragment pr to 4768
* chore(#4748): refresh the compact-content benchmark baseline after rebasing onto next
Regenerated with `node scripts/benchmark-compact-content.cjs --write` on the
rebased tree (base 0d6bf19bf); `--check` confirms it matches the live recompute.
Only the execute-phase split and the aggregate totals differ from next's copy.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017cjzdZtYjcBAa3Lqh2VrLK
---------
Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
Co-authored-by: Tom Boucher <trekkie@nomorestars.com>
237 lines
14 KiB
JavaScript
237 lines
14 KiB
JavaScript
'use strict';
|
|
|
|
/**
|
|
* #4003 — the safe_resume_gate / TDD RED / completion spot-check commit greps.
|
|
*
|
|
* The gate keyed on the padded `{phase_number}-{plan_padded}` as a bare substring:
|
|
* unanchored (any prior milestone's same-numbered plan matches) and padding-blind
|
|
* (the commit protocol — agents/gsd-executor.md <task_commit_protocol>,
|
|
* gsd-core/references/tdd.md:99 — specifies no padding rule, and both spellings are
|
|
* live in this repository's history). Workflow text IS the deployed product here, so
|
|
* the shape assertions are the faithful check; the behavioral fixture row runs the
|
|
* actual pipeline against a crafted history.
|
|
*
|
|
* #4619 — the gate's PHASE_N derivation grew to zero-strip only the leading
|
|
* integer segment of a decimal/N-segment phase number (`01.1`, `23.1.2`) via
|
|
* base-10 arithmetic, instead of forcing the whole value through
|
|
* `$((10#...))` and hitting a hard shell syntax error on the first dot.
|
|
*/
|
|
|
|
const { test, describe } = require('node:test');
|
|
const assert = require('node:assert/strict');
|
|
const fs = require('node:fs');
|
|
const path = require('node:path');
|
|
const { createTempGitProject, cleanup } = require('./helpers.cjs');
|
|
const { gitOrThrow } = require('./helpers/git-fixture.cjs');
|
|
|
|
const WORKFLOW = path.join(__dirname, '..', 'gsd-core', 'workflows', 'execute-phase.md');
|
|
|
|
describe('#4003 — safe_resume_gate commit-scope greps', () => {
|
|
test('safe_resume_gate greps an anchored, padding-tolerant plan scope', () => {
|
|
const w = fs.readFileSync(WORKFLOW, 'utf8');
|
|
// Anchored, ERE, zero-pad-tolerant on BOTH components — matches feat(2-02): and
|
|
// feat(02-02): alike, never a substring elsewhere in the message.
|
|
assert.ok(w.includes('PHASE_INT=${PHASE_NUMBER%%[!0-9]*}; PHASE_REST=${PHASE_NUMBER#"$PHASE_INT"}') &&
|
|
w.includes('PHASE_N="$((10#$PHASE_INT))${PHASE_REST//./\\\\.}"'),
|
|
'phase component must be zero-stripped via arithmetic base-10 (#4619: leading integer segment only, decimal/N-segment tolerant; #4748: split at the first non-digit so a letter suffix rides through)');
|
|
assert.ok(w.includes('PLAN_N=$((10#{plan_padded}))'),
|
|
'plan component must be zero-stripped via arithmetic base-10');
|
|
assert.ok(w.includes('PLAN_SCOPE_RE="^[a-z]+\\((0*${PHASE_N})-(0*${PLAN_N})\\):"'),
|
|
'the scope regex must be anchored to the commit-scope position and zero-pad-tolerant');
|
|
assert.ok(w.includes('--grep="${PLAN_SCOPE_RE}"'),
|
|
'the gate must grep the derived scope regex, not a padded literal');
|
|
// The old unanchored padded-literal grep must be gone.
|
|
assert.ok(!w.includes('--grep="${CURRENT_PLAN_ID}"'),
|
|
'the bare substring grep over the padded id must not remain');
|
|
assert.ok(!w.includes('CURRENT_PLAN_ID="{phase_number}-{plan_padded}"'),
|
|
'the padded id derivation must not remain');
|
|
});
|
|
|
|
test('the gate bounds history to the current milestone with a no-tag fallback', () => {
|
|
const w = fs.readFileSync(WORKFLOW, 'utf8');
|
|
assert.ok(w.includes('git describe --tags --abbrev=0'),
|
|
'the milestone bound derives from the most recent reachable tag (complete-milestone git_tag)');
|
|
assert.ok(w.includes('${MILESTONE_BASE:+"$MILESTONE_BASE..HEAD"}'),
|
|
'the bounded invocation must range BASE..HEAD only when a base resolved');
|
|
// Degrade must keep the anchor: a repo with no tags still gets the positional grep.
|
|
assert.ok(w.includes('MILESTONE_BASE=$(git describe --tags --abbrev=0 2>/dev/null || echo "")'),
|
|
'a missing tag base must degrade to empty, not fail the gate');
|
|
});
|
|
|
|
test('tdd red gate tolerates both commit-scope spellings (#4011 keying untouched)', () => {
|
|
const w = fs.readFileSync(WORKFLOW, 'utf8');
|
|
assert.ok(w.includes('PHASE_INT=${PHASE_NUMBER%%[!0-9]*}; PHASE_REST=${PHASE_NUMBER#"$PHASE_INT"}') &&
|
|
w.includes('PHASE_N="$((10#$PHASE_INT))${PHASE_REST//./\\\\.}"') && w.includes('PLAN_N=$((10#${PLAN_ID}))'),
|
|
'the TDD block derives zero-stripped components (#4619: leading integer segment only, decimal/N-segment tolerant; #4748: letter-suffix tolerant)');
|
|
assert.ok(w.includes('RED_COMMIT=$(git log --oneline -E ${TDD_MILESTONE_BASE:+"$TDD_MILESTONE_BASE..HEAD"} --grep="${PLAN_SCOPE_RE}" -- "*.test.*"'),
|
|
'the RED grep must use the same anchored padding-tolerant scope, milestone-bounded');
|
|
assert.ok(!w.includes('--grep="^test(${PHASE_NUMBER}-${PLAN_ID})"'),
|
|
'the padded-literal RED grep must not remain');
|
|
assert.ok(w.includes('TDD_MILESTONE_BASE=$(git describe --tags --abbrev=0 2>/dev/null || echo "")'),
|
|
'the RED grep carries the same milestone bound as the resume gate (#4003 review)');
|
|
assert.ok(w.includes('${TDD_MILESTONE_BASE:+"$TDD_MILESTONE_BASE..HEAD"}'),
|
|
'the RED grep range bound is applied');
|
|
assert.ok(w.includes('if [ "$TDD_MODE" = "true" ]'), '#4011 TDD_MODE keying preserved');
|
|
});
|
|
|
|
test('tdd.md gate-enforcement examples use the anchored padding-tolerant scope', () => {
|
|
const ref = fs.readFileSync(path.join(__dirname, '..', 'gsd-core', 'references', 'tdd.md'), 'utf8');
|
|
assert.ok(!ref.includes('--grep="^test(${PHASE}-${PLAN})"'),
|
|
'the padded-literal example grep must not remain');
|
|
assert.ok(ref.includes('--grep="^test\\((0*${PHASE_N})-(0*${PLAN_N})\\):"'),
|
|
'the RED example is anchored and zero-pad-tolerant');
|
|
assert.ok(ref.includes('PHASE_INT=${PHASE%%[!0-9]*}; PHASE_REST=${PHASE#"$PHASE_INT"}') &&
|
|
ref.includes('PHASE_N="$((10#$PHASE_INT))${PHASE_REST//./\\\\.}"') && ref.includes('PLAN_N=$((10#${PLAN}))'),
|
|
'the examples derive zero-stripped components (#4619: leading integer segment only, decimal/N-segment tolerant; #4748: letter-suffix tolerant)');
|
|
});
|
|
|
|
test('completion spot-check uses the anchored scope and keeps its time bound', () => {
|
|
// #4217 moved the completion spot-check probes (with the whole reconciliation
|
|
// policy, both arms) into execute-phase/steps/completion-reconciliation.md —
|
|
// "extract, not bump" against the frozen host ceiling. The anchoring contract
|
|
// travels with them: negative shape against the host, positives against the
|
|
// fragment that now owns the probes.
|
|
const w = fs.readFileSync(WORKFLOW, 'utf8');
|
|
const frag = fs.readFileSync(path.join(__dirname, '..', 'gsd-core', 'workflows',
|
|
'execute-phase', 'steps', 'completion-reconciliation.md'), 'utf8');
|
|
assert.ok(!w.includes('--grep="{phase_number}-{plan_padded}"') && !frag.includes('--grep="{phase_number}-{plan_padded}"'),
|
|
'the raw padded placeholder substring grep must not remain');
|
|
assert.ok(frag.includes('SPOT_PHASE_INT=${SPOT_PHASE_NUMBER%%[!0-9]*}; SPOT_PHASE_REST=${SPOT_PHASE_NUMBER#"$SPOT_PHASE_INT"}') &&
|
|
frag.includes('SPOT_PHASE_N="$((10#$SPOT_PHASE_INT))${SPOT_PHASE_REST//./\\\\.}"') &&
|
|
frag.includes('SPOT_PLAN_N=$((10#{plan_padded}))'),
|
|
'the spot-check derives zero-stripped components (#4619: leading integer segment only, decimal/N-segment tolerant; #4748: letter-suffix tolerant)');
|
|
assert.ok(frag.includes('--since="1 hour ago"'), 'the spot-check keeps its temporal bound');
|
|
});
|
|
|
|
test('the gate pipeline separates same-scope commits across a milestone tag (behavioral)', (t) => {
|
|
// Reproduces the report on a crafted history: an OLD milestone commit with the
|
|
// same scope, a tag, then THIS plan's unpadded commits. The pipeline shape is
|
|
// the workflow's: tag base (when present) + anchored, padding-tolerant ERE.
|
|
const repo = createTempGitProject('gsd-4003-gate-');
|
|
t.after(() => cleanup(repo));
|
|
const g = (args) => gitOrThrow(args, { cwd: repo });
|
|
|
|
g(['commit', '--allow-empty', '-m', 'feat(02-02): old milestone same-scope commit']);
|
|
// Annotated: a plain `git tag` can demand a message under some git configs.
|
|
g(['tag', '-a', 'v9.0.0', '-m', 'milestone close']);
|
|
g(['commit', '--allow-empty', '-m', 'test(2-02): RED for this plan']);
|
|
g(['commit', '--allow-empty', '-m', 'feat(2-02): GREEN for this plan']);
|
|
g(['commit', '--allow-empty', '-m', 'feat(2-20): adjacent plan must not match']);
|
|
g(['commit', '--allow-empty', '-m', 'feat: mentions 02-02 in prose but not in scope']);
|
|
|
|
const scope = '^[a-z]+\\((0*2)-(0*2)\\):';
|
|
const base = g(['describe', '--tags', '--abbrev=0']).trim();
|
|
const bounded = g(['log', '--oneline', '-E', `${base}..HEAD`, `--grep=${scope}`]).trim().split('\n');
|
|
assert.ok(bounded.some((l) => /test\(2-02\): RED for this plan/.test(l)), 'this plan RED commit is found');
|
|
assert.ok(bounded.some((l) => /feat\(2-02\): GREEN for this plan/.test(l)), 'this plan GREEN commit is found');
|
|
assert.ok(!bounded.some((l) => /old milestone same-scope/.test(l)), 'the pre-tag same-scope commit is excluded');
|
|
assert.ok(!bounded.some((l) => /adjacent plan/.test(l)), 'an adjacent plan scope does not match');
|
|
assert.ok(!bounded.some((l) => /in prose/.test(l)), 'a prose mention outside the scope position does not match');
|
|
|
|
// No-tag fallback: strip the tag, keep the anchor — the old milestone commit
|
|
// becomes reachable again, but prose/adjacent scopes still never match.
|
|
g(['tag', '-d', 'v9.0.0']);
|
|
const unbounded = g(['log', '--oneline', '-E', `--grep=${scope}`]).trim().split('\n');
|
|
assert.ok(unbounded.some((l) => /old milestone same-scope/.test(l)),
|
|
'without a tag base the anchor alone cannot exclude prior milestones (degrade is honest)');
|
|
assert.ok(!unbounded.some((l) => /in prose/.test(l)), 'the anchor still holds without a tag');
|
|
});
|
|
});
|
|
|
|
// ─── #4379: the RED pathspec is language-agnostic, and matches at root ──────
|
|
//
|
|
// The pathspec IS this gate's definition of "a test file". It was JS/TS-only, so
|
|
// a commit adding `foo_test.go` was invisible and every behaviour-adding task in
|
|
// a Go project halted with `TDD GATE TRIPPED: missing RED commit` — while
|
|
// references/tdd.md:175-177 advertises `go test ./...` as supported.
|
|
//
|
|
// These rows drive the REAL pathspec, extracted from the shipped workflow, against
|
|
// a real git repo. Re-typing the pattern into the test would only assert that two
|
|
// copies of a string agree; running it answers the question the gate actually asks.
|
|
describe('#4379 — the TDD RED pathspec is language-agnostic', () => {
|
|
// Pull the pathspec out of the workflow rather than restating it: the thing
|
|
// under test is what SHIPS, not a copy maintained alongside it.
|
|
function shippedRedPathspec() {
|
|
const w = fs.readFileSync(WORKFLOW, 'utf8');
|
|
const line = w.split(/\r?\n/).find((l) => l.includes('RED_COMMIT=$(git log'));
|
|
assert.ok(line, 'the RED_COMMIT line must exist in execute-phase.md');
|
|
const tail = line.slice(line.indexOf('-- ') + 3, line.lastIndexOf('| head -1)'));
|
|
const specs = (tail.match(/"[^"]{1,200}"/g) || []).map((s) => s.slice(1, -1));
|
|
assert.ok(specs.length > 0, `expected quoted pathspecs, parsed none from: ${tail}`);
|
|
return specs;
|
|
}
|
|
|
|
// One seeded repo, one commit, reused by every row below.
|
|
function seedRepo(t) {
|
|
const dir = createTempGitProject('gsd-4379-');
|
|
t.after(() => cleanup(dir));
|
|
const files = [
|
|
'foo_test.go', 'pkg/bar_test.go', // Go — incl. ROOT level
|
|
'root.test.js', 'src/a.test.ts', // JS/TS — incl. ROOT level
|
|
'tests/c.py', '__tests__/d.js', // directory conventions
|
|
'test_mod.py', 'mod_test.py', // Python, outside tests/
|
|
'lib_spec.rb', 'x_test.exs', // Ruby, Elixir
|
|
'src/impl.go', 'src/lib.rs', // NOT tests — must never match
|
|
];
|
|
for (const rel of files) {
|
|
const abs = path.join(dir, rel);
|
|
fs.mkdirSync(path.dirname(abs), { recursive: true });
|
|
fs.writeFileSync(abs, 'x\n');
|
|
}
|
|
gitOrThrow(['add', '-A'], { cwd: dir });
|
|
gitOrThrow(['commit', '-m', 'test(1-01): seed every convention'], { cwd: dir });
|
|
return dir;
|
|
}
|
|
|
|
function matched(dir, specs) {
|
|
const out = gitOrThrow(['log', '--format=', '--name-only', '--', ...specs], { cwd: dir });
|
|
return new Set(out.split(/\r?\n/).map((l) => l.trim()).filter(Boolean));
|
|
}
|
|
|
|
test('every convention tdd.md advertises is visible to the RED detector', (t) => {
|
|
const dir = seedRepo(t);
|
|
const hits = matched(dir, shippedRedPathspec());
|
|
for (const rel of [
|
|
'foo_test.go', 'pkg/bar_test.go',
|
|
'test_mod.py', 'mod_test.py',
|
|
'lib_spec.rb', 'x_test.exs',
|
|
]) {
|
|
assert.ok(hits.has(rel), `${rel} must satisfy the RED detector (#4379); matched: ${[...hits].sort().join(', ')}`);
|
|
}
|
|
});
|
|
|
|
test('a ROOT-level test file is not invisible', (t) => {
|
|
// The pre-#4379 pathspec was `**/`-prefixed, and `**/` does not match a path
|
|
// with no directory component — so a root `foo.test.js` was missed even in
|
|
// the language the gate did support. This is the half the issue did not report.
|
|
const dir = seedRepo(t);
|
|
const hits = matched(dir, shippedRedPathspec());
|
|
assert.ok(hits.has('root.test.js'), 'a root-level .test.js must match');
|
|
assert.ok(hits.has('foo_test.go'), 'a root-level _test.go must match');
|
|
});
|
|
|
|
test('the existing JS/TS conventions still match (no regression)', (t) => {
|
|
const dir = seedRepo(t);
|
|
const hits = matched(dir, shippedRedPathspec());
|
|
for (const rel of ['src/a.test.ts', 'tests/c.py', '__tests__/d.js']) {
|
|
assert.ok(hits.has(rel), `${rel} must still match after widening`);
|
|
}
|
|
});
|
|
|
|
test('implementation files never match — the gate must still be able to trip', (t) => {
|
|
// A pathspec broad enough to catch ordinary source would make the gate pass on
|
|
// ANY in-scope commit, which is worse than the bug being fixed.
|
|
//
|
|
// `src/lib.rs` carries the Rust consequence: `#[test]` conventionally lives
|
|
// INSIDE the implementation file, so a Rust RED commit touches only source and
|
|
// no path-based gate can see it. That gap is a direct consequence of this row
|
|
// holding — the two cannot both be satisfied — which is why it is documented in
|
|
// references/tdd.md rather than "fixed" by widening the pathspec.
|
|
const dir = seedRepo(t);
|
|
const hits = matched(dir, shippedRedPathspec());
|
|
for (const rel of ['src/impl.go', 'src/lib.rs']) {
|
|
assert.ok(!hits.has(rel), `${rel} must NOT be treated as a test file`);
|
|
}
|
|
});
|
|
});
|