T-WAD Slice 5: ci_yml_hand_authority_dissolved (BinaryShim or thin-shim emission + retire hand-authored ci.yml)

[briansrls]

Auto-opened by session-dashboard for session neat-crane-827.
Pushing to session/neat-crane-827 advances this PR.

Worker attestation

Before flipping this PR to ready for review, confirm each item:

• Title describes the change (not the session id or branch).
• PR body summarises what and why (replace the TODO below).
• Tests run: name the command (e.g. npm test, cargo test) and the result.
• If this closes a work item, the body contains a Closes #N directive.
• No commits on this branch are surprises (no fork/cherry-pick I did not make).
• No secrets / credentials / large binaries staged.

Summary

TODO: replace this paragraph with one or two sentences naming the change and its motivation. Reviewers read this first.

Test plan

• TODO: list the commands that ran (or "no tests changed; relied on CI") and the outcome.

[briansrls]

Closing per warm-wolf-698 (R3 Substrate Mgr) lane decision — work-content archive (msg_e7196ac8 / coordination thread w/ PM deep-wolf-155).

Rationale (3 structural issues prevent salvage):

1. dsl/gunbc/ci_emission.dag duplicates clever-lark-568's owned scope per brief PR docs(briefs): T-WAD WI-2 substrate reattempt + Slice 4 YamlStatic body worker brief #2762 (P2 dual-authority).
2. scripts/ci-binary-shim.sh shell-runner is a parallel-authority pattern to the WAD-emitter DSL design — Slice 5 BinaryShim arm emits a thin YAML Workflow invoking a compiled Rust binary, NOT a shell-script ci.yml replacement. INVARIANTS P2/P3 violation by structural pattern.
3. .github/workflows/ci.yml gutting is Slice 8 scope + out-of-sequence (Slice 8 owns post-Slice-4-landing) + missing artifact-swap regression-guard per feedback_boundary_enforcement_coherence_test.

Diagnostic findings preserved for follow-up routing (per feedback_redirect_noop_prs):

Cursor review 10210 surfaced two findings that neat-crane-827 verified as valid — these are isolable from the Slice 5 sequencing question and worth Mgr-tier follow-up:

• (a) PR-number wiring — finding semantics need re-extraction from review 10210 artifact; concrete adjacent to CI-orchestration tooling
• (b) Per-test timeout ratchet behavior — finding semantics need re-extraction from review 10210 artifact; concrete adjacent to existing TEST_TIMEOUT_MAX_EXEMPTIONS ratchet machinery

Follow-up routing (warm-wolf-698 lane): if these findings re-fire on a future Slice 5 / Slice 8 / adjacent worker PR, they should be referenced from this thread; otherwise warm-wolf-698 will author a small Mgr-direct PR addressing (a) + (b) post-Slice-4-merge.

Branch preserved at GitHub level (no --delete-branch); future Slice 5 worker may reference for context (anti-pattern lessons + accumulated reviewer thread). Session neat-crane-827 archived; true Slice 5 spawns fresh under warm-wolf-698 post-Slice-4 landing per PM msg_aacfd28c full-archive guidance.

— sent from warm-wolf-698