Phase 1 — complete the agnostic orchestration emit so the intent graph can express what pushed workflows to bash_build. Brief: docs/plans/shell-intent-emit-realization-design.md phase 1. In src/v2/std/orchestration.dag the emit has holes: While/bounded-poll is rejected and Retry is hardcoded to two

[briansrls]

Auto-opened by session-dashboard for session nimble-tern-201.
Pushing to session/nimble-tern-201 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.

[cursor]

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

[gunbai-bot]

Thanks — verified both findings against the current tree (review 39633).

Finding 1 (valid, will reconcile). Confirmed: shell_emission_model.dag still asserts For/While refuse by design / NOT in scope / While stays emitter-unsupported at the control-flow li, the 2026-07-03 census p, and the Slice-1 li — on the premise that no pre-runtime site needs While. Phase 1 (#6832) falsified that premise: it lowers While/BoundedPoll in the same 05_emit_orchestration.dag emitter and ci_floor_peak_emit.dag is a live pre-runtime While consumer. So those rows are stale, and adding the landing note without reconciling them makes the carrier self-contradictory. I'll update them to record that the census's 'zero pre-runtime While sites' finding was superseded by #6832 (a pre-runtime readiness-poll site emerged), rather than leave them as present-tense design decisions.

Finding 2 (won't forge; proposing done: false + sign-pending). The sibling landed rows carry sign(…, signed(by: "operator", …)), and this carrier's invariant is that every done: true row is operator-signed. #6832 was merged, not operator-signed — I can't add an operator attestation on the operator's behalf. Per the Slice-2 precedent (work observably complete → done: false, 'operator sign-off pending'), I'll set 6-shell-intent-phase1 to done: false with a merged-#6832/sign-pending note, so the invariant holds without a fabricated signature. The operator can flip it to done: true + signed(...) whenever they sign.

Regenerating DESIGN.md/ROADMAP.md to clear the drift gate is part of the same fix. Landing is pending the operator's go/no-go on carrying this doc-status PR at all. — sent from calm-ferret-849

[gunbai-bot]

Superseded by #6878, which carries this same Phase-0/1 landing record rebased onto current main (after #6853/#6854 merged) with the review 39633 findings addressed and CI green. Verified green-by-execution: roadmap_authority_witnesses, live_deploy_emit_holds, generated_artifact_drift_witnesses all pass. — sent from calm-ferret-849