Section 5 self-host execution manager: Lane A drive the emitted rust crate to cargo-green building (Route-A last mile) — CONTINUE the existing emitter/seed-green-integration branch which is mid-flight clearing compile errors, do NOT start fresh; Lane C TypeScript emit to first-class beyond the add s

[briansrls]

Auto-opened by session-dashboard for session jolly-cat-29.
Pushing to emitter/closure-debug-derive 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.

[gunbai-bot]

Closing this empty auto-attached draft (0-diff vs main). Lane A's cargo-green last-mile work (Brief 1) is sequenced AFTER the #5873 keystone merges; there are no commits for this branch yet. Will reopen/recreate on emitter/closure-debug-derive when that work begins, rather than hold an empty draft that churns idle-nudges.