Scrub PR #4305 references and past-tense narration from comments

Comments now describe current behavior only. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 2d44fd06-6323-4654-8a80-b756561ef669
nicolehaugen · Aug 25, 2026 · Aug 25, 2026 · Aug 25, 2026 · Aug 25, 2026 · Aug 25, 2026
commit 7a898ffecf5bf54e5454126c71c2119408543a09
@@ -58,14 +58,6 @@ export async function specifyArtifactList(root, { runner = defaultAsyncRunner }
     return JSON.parse(String(stdout));
 }
 
-// specifyArtifactInfo removed intentionally. Prior to spec-kit PR #4305 the
-// wizard called `specify artifact info <id>` once per artifact to obtain the
-// composition stack, which cost ~1s (Python cold-start) × N artifacts on
-// every boot. PR #4305 makes `list --json` return the same rich shape per
-// row, so the wizard no longer needs an info fetch. If a future feature
-// needs single-artifact detail beyond what `list` returns, add it back — but
-// do NOT reintroduce a per-artifact fan-out on the boot critical path.
-
 // ---------------------------------------------------------------------------
 // Shape mapping helpers
 // ---------------------------------------------------------------------------
@@ -384,19 +376,13 @@ function applyHookAttributions(artifacts, extensionHookInfo, hooksMap) {
  *
  * ## Upstream contract
  *
- * This function assumes `specify artifact list --json` now returns one row
- * per artifact carrying the FULL composition stack — i.e. list rows have
- * the same shape as `info --json` output (with `stack: [...]`). That
- * change ships in spec-kit PR #4305. Prior to that PR the CLI required a
- * separate `info` call per artifact to obtain the stack, which forced the
- * wizard to fan out N shell-outs on boot (~60s regression on stacks of
- * 60+ artifacts). See AGENTS.md: "CLI is the source of truth for
- * composition."
+ * `specify artifact list --json` returns one row per artifact carrying the
+ * FULL composition stack (i.e. list rows include `stack: [...]`). See
+ * AGENTS.md: "CLI is the source of truth for composition."
  *
- * If a rollback ever ships a CLI where `list --json` omits `stack`, this
- * function still returns a well-formed payload — artifacts get empty
- * stacks and the composition summary folds to `[]`. Not desirable, but not
- * a crash.
+ * If a CLI ships where `list --json` omits `stack`, this function still
+ * returns a well-formed payload — artifacts get empty stacks and the
+ * composition summary folds to `[]`. Not desirable, but not a crash.
  *
  * @param {object} opts
  * @param {string} opts.workspaceRoot   Absolute path to the workspace root.
@@ -411,13 +397,10 @@ export async function buildCompositionFromCli({
     extensionItems,
     runner = defaultAsyncRunner,
 } = {}) {
-    // 1. Single list call — each row now carries `stack` (PR #4305).
+    // 1. Single list call — each row carries `stack`.
     const list = await specifyArtifactList(workspaceRoot, { runner });
 
-    // 2. Shape each row directly. shapeArtifact already reads `stack` off
-    //    its input, so no code change needed there — the swap from
-    //    per-artifact `info` payloads to per-row list payloads is
-    //    transparent as long as the fields match.
+    // 2. Shape each row directly. shapeArtifact reads `stack` off its input.
     const artifactsRaw = [];
     for (const row of list) {
         const shaped = shapeArtifact(row);

@@ -25,15 +25,10 @@ import { readMarkdownArtifact, extractMarker } from "./project-scanner/markdown.
 
 export { readMarkdownArtifact };
 
-// Composition inventory used to be scanned from `.specify/presets.json` and
-// `.specify/extensions.json`, which no released `specify` CLI ever writes.
-// PR #4305 makes the CLI the authoritative source of composition data, so
-// the wizard now reads composition exclusively from
-// `specify artifact list --json` (see composition/artifact-cli.mjs) and
-// overlays it via `overlayCachedComposition`. There is intentionally no
-// direct fs read here for presets or extensions — see AGENTS.md governing
-// principles: "CLI is the source of truth for composition. No direct fs
-// reads. Ever."
+// Composition is read exclusively from `specify artifact list --json` (see
+// composition/artifact-cli.mjs) and overlaid via `overlayCachedComposition`.
+// No direct fs read here for presets or extensions — see AGENTS.md:
+// "CLI is the source of truth for composition. No direct fs reads. Ever."
 
 // deps shape:
 //   readFile(path, enc)     → Promise<string>

diff --git a/...it-copilot-wizard/extensions/speckit-wizard-canvas/test/artifact-cli.integration.test.mjs b/...it-copilot-wizard/extensions/speckit-wizard-canvas/test/artifact-cli.integration.test.mjs
@@ -33,10 +33,8 @@ function hasSpecifyCli() {
 }
 
 // Detect whether the installed `specify` CLI emits per-row `stack` on
-// `artifact list --json` (PR github/spec-kit#4305). Pre-#4305 CLIs return
-// bare rows and the live test would fail the "exactly one active layer"
-// invariant. Skip in that case — the fixture-drift test above covers the
-// same shape once the fixture is regenerated post-#4305.
+// `artifact list --json`. Without `stack` the live test would fail the
+// "exactly one active layer" invariant — skip in that case.
 function specifyListEmitsStack() {
     try {
         const out = execFileSync("specify", ["artifact", "list", "--json"], {
@@ -98,32 +96,28 @@ describe("artifact-cli — live CLI", { skip: skipLive }, () => {
 // Regenerate the snapshot with:
 //   specify artifact list --json > test/fixtures/live-cli-list.json
 //
-// Post PR #4305, `list --json` returns rows with the full composition stack
-// embedded, so a separate `info` fixture is no longer needed. If you're on
-// a pre-#4305 CLI the snapshot will lack `stack` and the test will fail —
-// that's the intended drift signal.
+// `list --json` returns rows with the full composition stack embedded, so
+// no separate `info` fixture is needed.
 describe("artifact-cli — fixture drift", () => {
     const listPath = join(FIXTURES_DIR, "live-cli-list.json");
     const snapshotAvailable = existsSync(listPath);
 
-    // Detect pre-#4305 snapshots: list rows without `stack`. In that case
-    // skip the drift assertion (rather than fail CI) — the test's purpose
-    // is to catch NEW drift once we're on the target contract, not to
-    // block on a stale capture. Regenerate the fixture once the CLI
-    // upgrade is in and the test will start guarding again.
-    let snapshotIsPre4305 = false;
+    // If a snapshot lacks `stack`, skip the drift assertion rather than
+    // fail CI — the test's purpose is to catch NEW drift against the
+    // current contract, not to block on a stale capture.
+    let snapshotMissingStack = false;
     if (snapshotAvailable) {
         try {
             const parsed = JSON.parse(readFileSync(listPath, "utf8"));
             if (Array.isArray(parsed) && parsed.length > 0 && !Object.hasOwn(parsed[0], "stack")) {
-                snapshotIsPre4305 = true;
+                snapshotMissingStack = true;
             }
         } catch {
             // fall through — snapshotAvailable stays true; the JSON.parse
             // in the test will surface the real error
         }
     }
-    const skipDrift = !snapshotAvailable || snapshotIsPre4305;
+    const skipDrift = !snapshotAvailable || snapshotMissingStack;
 
     test("captured list rows carry the fields the wizard reads (id/name/kind/description/stack[])", { skip: skipDrift }, () => {
         const rows = JSON.parse(readFileSync(listPath, "utf8"));

@@ -11,8 +11,8 @@ import { join } from "node:path";
 // ---------------------------------------------------------------------------
 // Fake runner — mimics the specify CLI for `artifact list --json`.
 //
-// Post PR #4305 the list payload IS the composition data: each row carries
-// its own `stack`. Fixtures are a flat array of rows.
+// The list payload IS the composition data: each row carries its own
+// `stack`. Fixtures are a flat array of rows.
 // ---------------------------------------------------------------------------
 
 function fakeRunner(rows) {

diff --git a/...pec-kit-copilot-wizard/extensions/speckit-wizard-canvas/test/fixtures/README.md b/...pec-kit-copilot-wizard/extensions/speckit-wizard-canvas/test/fixtures/README.md
@@ -10,8 +10,8 @@ shape regressions if the CLI's JSON contract changes.
 It is **not** consumed by the fixture-based unit tests in
 `test/artifact-cli.test.mjs` — those tests use synthetic fixtures inline.
 
-Post spec-kit PR #4305, `list --json` returns the full composition stack per
-row, so a separate `info` snapshot is no longer needed.
+`list --json` returns the full composition stack per row, so no separate
+`info` snapshot is needed.
 
 ### Regenerating