The /pipeline page speaks the home page's language #9838

/pipeline now reads like the home page: one <h1>, then each of the four steps as a plain section under its own <h2> ("1. Check" through "4. Live"). The tests I ran pass: the new test/pipeline-language.test.ts, plus test/pipeline-path.test.ts and test/pipeline-steps.test.ts. bun x tsc --noEmit and bun scripts/design-lint.ts are clean. I didn't run the full suite; the forge runs the full check on push. I didn't run bun scripts/gate.ts or confirm the new test fails on main.

• What changed: the page no longer uses card(, card-body or the step rows. Each step is a <section> with its meaning line and a <details> fold holding what it waits for, what it catches, what is inside, and the measured stats. The "Where to look next" box is now a plain section with the same words and links (Boards, the full-suite report, the MCP note).
• New test: the test fetches /pipeline signed out. It checks for one <h1>, no class="card or card-body inside <main>, and a heading for every step.
• Left alone: flow-panel.ts and /boards, and the exported STEP_DETAIL and STEP_MEASURES. I added no new classes, so there is no docs/design/areas/pipeline.md change.
• Fold kept: I kept the fold on each step because test/pipeline-path.test.ts requires four <details id="inside-…"> elements. The fold's summary reads "What is inside", which is new wording.
• To try it: open /pipeline.

Closes #9835

/pipeline now reads like the home page: one <h1>, then each of the four steps as a plain section under its own <h2> ("1. Check" through "4. Live"). The tests I ran pass: the new test/pipeline-language.test.ts, plus test/pipeline-path.test.ts and test/pipeline-steps.test.ts. bun x tsc --noEmit and bun scripts/design-lint.ts are clean. I didn't run the full suite; the forge runs the full check on push. I didn't run bun scripts/gate.ts or confirm the new test fails on main.

• What changed: the page no longer uses card(, card-body or the step rows. Each step is a <section> with its meaning line and a <details> fold holding what it waits for, what it catches, what is inside, and the measured stats. The "Where to look next" box is now a plain section with the same words and links (Boards, the full-suite report, the MCP note).
• New test: the test fetches /pipeline signed out. It checks for one <h1>, no class="card or card-body inside <main>, and a heading for every step.
• Left alone: flow-panel.ts and /boards, and the exported STEP_DETAIL and STEP_MEASURES. I added no new classes, so there is no docs/design/areas/pipeline.md change.
• Fold kept: I kept the fold on each step because test/pipeline-path.test.ts requires four <details id="inside-…"> elements. The fold's summary reads "What is inside", which is new wording.
• To try it: open /pipeline.

I added an empty commit with a Try: line ("open /pipeline on the preview signed out and read the four step sections"), which is what the gate rule asked for. bun scripts/gate.ts now runs clean here, and the push went through without a force. I didn't re-run the tests, because the only new commit is an empty one. The forge's check on the new head will confirm it.