feat(orchestrator): mirror the gentle-ai sdd-orchestrator canon into the Pi prompt surface

[Alan-TheGentleman]

Closes #312. Umbrellas: #311, #256.

Pi's orchestrator prompt surface becomes a carbon copy of the gentle-ai sdd-orchestrator canon (rc.8 + the #3249 pi runtime registration), byte-faithful where the contract is shared (<!-- canon:start/end --> markers), Pi overlays only where the runtime genuinely differs.

• Canon sections mirrored byte-faithful: Lossless Blocking Prompts (with the #3070 symmetric ordinal-alias domain), Gentle AI Provider Defect Handoff (evidence-channel routing), SDD Edit-Authority Consent Relay, Language Domain Contract, Delegation Rules + Mandatory Delegation Triggers, Native Checking Contract, the full review-ledger contract (route, forecast, all 18 stop-reason continuations, consent/v3, capture rules, read-only git recipe, correction, Authority-First Terminal Procedure, Delivery), Cost and Context Balance.
• Pi bindings where the runtime differs: ask_user_question as the classified native question UI, agent: pi on STATUS routes, and the new pi-binding paragraph — registered host-mediated identity (gentle-ai#3249), GENTLE_PI_REVIEW_RELAY_CONTRACT=gentle-pi.review-relay/v1 declared by the launcher (admission fails closed without it), collect inputs without --agent, fresh locked-down print-mode pi subprocess per capture, raw bytes via --result-artifact-file.
• Pi overlays preserved verbatim: identity/persona header, LB1–LB5, Work Routing Ladder, compact controller lane, trigger runtime bindings, all {{GENTLE_PI_*_PATH}} injection points.
• PR feat(sdd): adopt native attempt authority #303's Native Runtime Attempt Authority sections untouched; always-on injection stays under the 10,240 B rendered budget.

Verification: full suite 1021 pass / 0 fail / 1 pre-existing skip; orchestrator-budget 39/39; native-sdd-attempt-authority 17/17; check:transaction-runner and verify-package-files green.

[coderabbitai]

Warning

Review limit reached

@Alan-TheGentleman, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 48 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Repository UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 24c5f392-ed3e-4dad-a28d-f403a85a6851

📥 Commits

Reviewing files that changed from the base of the PR and between 6546a5c and 2f8552c.

📒 Files selected for processing (3)

• assets/orchestrator-delegation.md
• assets/orchestrator.md
• tests/orchestrator-budget.test.ts

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}