🧪 #543 migrate PC document rows to Markdown

[taras]

Parent quest: #543

Purpose

Move the PC document rows that <Execution host="run"> faithfully observes into one checked-in Markdown suite.

Rows

• PC9 — missing required prop fails before any document effect.
• PC17 — a document without props is unaffected.
• PC21 — a targeted root keeps the declaring document's props and excludes its sibling.
• PC23 — a required prop remains required in a targeted root.

Layout

packages/cli/tests/document-suites/props/Props.test.md with ordinary sibling fixtures for the missing-required, plain, and sectioned roots. Fixture documents are .md, not .test.md.

Evidence

• Every <Test name> begins with its PC row ID.
• Every child binds and asserts the exact settled Result; output/effect claims use <CollectOutput> and positive/negative markers.
• Delete the four TypeScript row twins only after the recorded mutation makes the Markdown row fail by itself.
• Retain every other PC row in props-cli.test.ts, naming its distinct argv/environment/help fault.

Smallest mutation themes: delay root prop validation until after expansion; make prop-less roots require a schema; discard props/frontmatter during target projection.

Specifications

Update the Root Document Props acceptance text to name the Markdown owner and retained CLI source/help rows. Do not add #542's repository-wide policy.

Acceptance

• PC9/17/21/23 each appear once in Markdown and no longer in TypeScript.
• Their Markdown-only mutation evidence is recorded.
• Retained PC rows still prove their distinct command faults.
• The PC launcher passes under Deno, Node, and Bun.

Dependency

Blocked by #583. May proceed independently of CT and IE after that.

[taras]

Active quest step

#583 is complete. #584 is now active, starting from current origin/main at 8f0cdc56dbd1dc9d6ab2ab46d993c699b964d00c (the #593 merge).

Implement the frozen PC migration without changing the disposition matrix:

• Align the existing PC9 Markdown evidence and fixtures with the final packages/cli/tests/document-suites/props/Props.test.md layout.
• Add PC17, PC21, and PC23 to that one checked-in suite.
• Every child binds and asserts its exact settled Result; collect output only for the positive/negative effects the row claims.
• Record a discriminating Markdown-only mutation for each row before deleting its TypeScript twin.
• Retain every other PC subprocess row with its distinct argv, environment, help, or command fault; do not implement Add in-process xmd command execution to Markdown tests #581.
• Update the Root Document Props acceptance text to name the Markdown owner and retained CLI evidence, without adding Quest: Ensure every specification requirement has exactly one test #542 policy.
• Keep one PC launcher execution and prove it under Deno, Node, and Bun.

Resolve origin/main in a fresh worktree, preserve the dirty checkout, and return one exact feedback commit with every focused command and mutation result recorded.

[taras]

Planner closure — PASS

#584 is complete on main at merge commit cc79aa869b82d73a452eb8703f41d037d6a7e62e (PR #595; reviewed head 4be4251471ea70a7d23977eae556a0002c4bec6a).

• PC9, PC17, PC21, and PC23 have one Markdown owner at packages/cli/tests/document-suites/props/Props.test.md.
• Each row asserts the exact child settlement and its claimed positive/negative output observations.
• Recorded mutations discriminate PC17 and PC21/PC23; PC9 retains its earlier recorded mutation evidence.
• The TypeScript twins are removed while retained command rows keep their distinct argv, environment, help, and command faults.
• The Root Document Props specification names the Markdown and retained CLI evidence owners.
• The PC launcher passed under Deno, Node, and Bun without changing the shared runner or public testing contracts.

The explicit empty props schema on the outer suite is accepted: it states that the suite takes no props and keeps the prop-less-root mutation focused on PC17's child without changing that child's contract.

#584's frozen acceptance is satisfied.