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/freemonoid-container-grounding 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]

Held draft — reset to clean base (e7e8fc4) pending a parent design decision.

By-execution A/B on the HostNative cutover (v2+dsl, corpus_repr forced to HostNative for measurement only):

• baseline, no FreeMonoid grounding: 15,342 cargo errors (E0308=12,607)
• • FreeMonoid->Vec type grounding: 15,563 (+221, E0308 +402)

The type-alias grounding regresses, because it grounds the FreeMonoid type to Vec while values are still constructed as the Empty/Cons coproduct -> type-vs-value mismatch. String and List were already host/Vec-grounded in the HostNative baseline independent of this change, so there is no additional collapse for a type-alias edit to capture. The dominant error class (E0308 ~82%) is the Rc/Box/coproduct value-wrapping fork (model-vs-realization), which requires value-side constructor/operation grounding, not type-aliasing.

The earlier CI-failing head (21ab7a2) carried an auto-committed measurement-force hack + a seed/dag desync; both removed. Not landing a regression. Awaiting decision on whether to pursue the value-side grounding here or route to the de-fork lane.