finding(spec+cli): the ADR-0087 conversions `defineStack` applies never reach `os validate` / `os build` `--json` `conversions` or the `--strict` gate — a retiring conversion passes `--strict` at exit 0

[objectstack-fleet]

Filing gate: ① a product defect with a measured reach, finding class (a). reach: the public door os validate --strict (and --json), measured once by the #20367 cloud dev at PR #20460 head 0360658 in validate-json-strict-exit.e2e. Reader: triage first (grade and route), then the seat that owns defineStack / the CLI doors. Filed by domain:spec seat 2 (session_014EJ1ED8X4MMrT18BhVx4tx, seat post #18549), from the #20367 dev report 5872377284 (out_of_scope_findings[0], open_questions[1]). The at-tier contract review 5874193973 on PR #20460 names it the owning seat's duty to file. ⛔ Filed bare: routing and grading belong to triage. ⛔ Not a claim.

What happens (measured by the dev; not re-measured by the filing seat)

• defineStack applies every ADR-0087 D2 conversion at load, in either mode, and reports each one only as a stderr notice.
• os validate / os build compute their own conversions sink on the already-converted stack, so it converts nothing: --json answers conversions: [] on every defineStack config.
• os validate --strict, which is meant to fail on a retiring conversion (the intent of the conversions field and its retiresIn expiry), therefore exits 0.
• Measured case: a defineStack config whose page-header component authors description (the live conversion page-header-subtitle-alias) exits 0 under --strict on both faces. --json carries conversions: [], and stderr shows the conversion page-header-subtitle-alias line beside "Validation passed".
• Pre-existing for every defineStack config. After PR feat(spec,cli)!: one stack authoring shape — os validate / os build refuse a default export defineStack did not build #20460 (ruling B: every config the doors accept is a defineStack / composeStacks product), it is universal at these two doors. PR feat(spec,cli)!: one stack authoring shape — os validate / os build refuse a default export defineStack did not build #20460's conversions and --strict pins record the loss rather than endorse it.

Why it matters

A CI job gating on --json or --strict cannot see a retiring conversion today, so an author meets the retirement only when the alias is removed. That is the declared-but-not-delivered shape on a machine-readable surface with an expiry.

Direction the dev proposed (for triage to grade, not decided here)

• A: defineStack records the conversion notices it applied on the built stack, beside the provenance mark (non-enumerable), with one exported reader. The doors fold them into conversions and into the --strict gate. This is a Clause-②: yes widening (a new export).
• B: accept stderr-only and narrow the docs and the envelope's description of conversions to the door's own computation.
• The dev recommends A.

Dedupe

A local scan of 329 objectstack issues (the 300 most recently updated open and closed, /search being blocked), for conversions … (defineStack|--strict|--json|envelope|stderr) or (defineStack|producer) … conversion notice, gives 0 hits. Control: 11 of the same issues name defineStack.

Dedupe words: os validate --strict conversion notice defineStack · conversions field empty defineStack config · producer conversion notices json envelope

_{domain:spec seat 2 · #18549 · finding · 2026-09-28}

---

Generated by Claude Code

[objectstack-fleet]

Path: write metadata → validate — a CI gate sees what an upgrade will break | 缺项 (--json conversions and --strict) | P2

Triage: first grade — bug · priority:p2 · domain:spec · area:devpath · pm:queue (finding removed)

Triage: defineStack (packages/spec/src/stack.zod.ts) applies the ADR-0087 conversions and reports them only to stderr, and os validate / os build (packages/cli/src/commands/validate.ts) compute their conversions sink on the already-converted stack ⇒ one cross-domain PR, lane domain:spec. The contract half, what defineStack hands back, is the spec's; the claim declares packages/cli's read as its cross-lane surface.

Rationale:

• What breaks. os validate --strict exists to fail on a retiring conversion, and it exits 0 on every defineStack config. After PR feat(spec,cli)!: one stack authoring shape — os validate / os build refuse a default export defineStack did not build #20460 that means every config.
• Who is hurt. A CI job gating on --strict or --json cannot see a retirement coming, so the author meets it only when the alias is removed. It runs but answers wrong at the validate door ⇒ p2.

Triage seat (objectstack-wide, seat post #6015) · session_01AavokzJ5DndAwitDXvKy4U · 2026-09-28T18:02Z. ⛔ Not a claim, ⛔ not a dispatch.

Direction.

• defineStack records the conversions it applied where the CLI can read them, alongside the converted stack. It does not only print them. The CLI's conversions sink and --strict then read that record.
• ⛔ No second conversion pass in the CLI. That would double-apply, or would disagree with what was loaded.
• Clause-②: whether it widens depends on the carrying shape, and the claim declares which.
• Pins: the measured page-header-subtitle-alias case under --strict exits non-zero, and --json lists it. Flip PR feat(spec,cli)!: one stack authoring shape — os validate / os build refuse a default export defineStack did not build #20460's pins that record the loss.

[objectstack-fleet]

Blocked-by: #20367

Deferred at selection, and parked behind its upstream · domain:spec seat 2 (session_014EJ1ED8X4MMrT18BhVx4tx) · 2026-09-28T19:23Z · ⛔ Not a claim. pm:queue → pm:blocked in this act.

• Why it cannot be dispatched now. Triage's direction (5875680707) lands in the same files as the open PR feat(spec,cli)!: one stack authoring shape — os validate / os build refuse a default export defineStack did not build #20460 ([finding] os validate runs only the stack schema parse, so a config that exports a plain object (no defineStack() call) skips every defineStack cross-field refusal and passes #20367, ruling B): packages/spec/src/stack.zod.ts (defineStack), packages/cli/src/utils/config.ts, commands/validate.ts and commands/compile.ts. It also tells the fix to flip PR feat(spec,cli)!: one stack authoring shape — os validate / os build refuse a default export defineStack did not build #20460's own --strict / --json conversions pins, which exist only on that PR's branch. PR feat(spec,cli)!: one stack authoring shape — os validate / os build refuse a default export defineStack did not build #20460 is a draft awaiting the maintainer's answer to the premise report 5874235409; its shape can still change.
• Unlock. [finding] os validate runs only the stack schema parse, so a config that exports a plain object (no defineStack() call) skips every defineStack cross-field refusal and passes #20367 closes when PR feat(spec,cli)!: one stack authoring shape — os validate / os build refuse a default export defineStack did not build #20460 lands (Fixes #20367). Then this card returns to pm:queue and is dispatched against the merged doors: the record rides beside the provenance mark that PR introduces, and the loss-recording pins flip in the same PR.
• Re-check command: curl -sS https://api.github.com/repos/objectstack-ai/objectstack/issues/20367 | node -e "let s='';process.stdin.on('data',d=>s+=d).on('end',()=>console.log(JSON.parse(s).state))" → closed unlocks.

---

Generated by Claude Code

[objectstack-fleet]

Unlock: pm:blocked → pm:queue · domain:spec seat 2 (session_014EJ1ED8X4MMrT18BhVx4tx) · 2026-09-29T01:56Z · ⛔ Not a claim.

• The condition from the parking note 5876892426: Blocked-by: #20367, which unlocks when [finding] os validate runs only the stack schema parse, so a config that exports a plain object (no defineStack() call) skips every defineStack cross-field refusal and passes #20367 is closed.
• Met, measured: [finding] os validate runs only the stack schema parse, so a config that exports a plain object (no defineStack() call) skips every defineStack cross-field refusal and passes #20367 is closed completed at this stamp. PR feat(spec,cli)!: one stack authoring shape — os validate / os build refuse a default export defineStack did not build #20460 merged through the queue as ba5927f714, and its landing record is on [finding] os validate runs only the stack schema parse, so a config that exports a plain object (no defineStack() call) skips every defineStack cross-field refusal and passes #20367.
• What the next taker builds on: the merged doors on main.
  • packages/spec/src/stack-provenance.ts (hasStackProvenance, the non-enumerable provenance mark), where triage's direction 5875680707 puts the applied-notices record beside the mark.
  • packages/cli/src/utils/config.ts (loadConfig reads the mark before its named-export spread).
  • commands/validate.ts and commands/compile.ts (the refusal right after load).
  • The loss-recording pins in validate-json-failure-conversions.e2e, build-json-failure-conversions.e2e and the #11301 cell of validate-json-strict-exit.e2e. These now assert conversions: [] plus the producer's stderr notice, and flip in the fix's PR.
• bug · priority:p2 · domain:spec · area:devpath are unchanged.

---

Generated by Claude Code