chore(plan-marshall): enable orchestrator auto_emit and set parallelization_scope - #127
Conversation
…zation_scope Records the two orchestrator autonomy knobs the api-sheriff-roadmap epic now runs under, set by operator decision on 2026-07-28/29: - auto_emit: false -> true. On every landing that frees a slot the orchestrator auto-fills toward parallelization_scope and auto-stamps the launched transition, instead of waiting for a per-plan confirmation. The disjointness, prep-readiness and slot-count guards are unchanged, and the emit-not-equal- running invariant still holds: the launched->running start stays operator- owned under either value. - parallelization_scope: 2, previously unset at the config default. The epic already carried 2 at the epic level (the value the next verb reads); setting it here makes the standing "always aim for two parallel plans" instruction durable rather than epic-local. Config only - no production code, tests or build behaviour is touched. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01XcDpCfoghp4KzkD6sQXJjn
There was a problem hiding this comment.
Sorry @cuioss-oliver, you have reached your weekly rate limit of 500000 diff characters.
Please try again later or upgrade to continue using Sourcery
|
Important Review skippedAuto reviews are limited based on label configuration. 🚫 Excluded labels (none allowed) (1)
Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository: cuioss/coderabbit/.coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
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. Comment |
What
Records the two orchestrator autonomy knobs the
api-sheriff-roadmapepic now runs under, set by operator decision on 2026-07-28/29."orchestrator": { - "auto_emit": false + "auto_emit": true, + "parallelization_scope": 2 },Why
auto_emit: true— on every landing that frees a slot, the orchestrator auto-fills towardparallelization_scopeand auto-stamps thelaunchedtransition, rather than waiting for a per-plan operator confirmation. What it does not change: the disjointness guard, the prep-readiness guard, theN − Rslot count, and the emit≠running invariant — thelaunched → runningstart stays operator-owned under either value, and a colliding or unprepared plan is never emitted just to fill a slot.parallelization_scope: 2— previously unset at the config default. The epic already carried2at the epic level (the value thenextverb actually reads), so this changes no current behaviour; it makes the standing "always aim for two parallel plans" instruction durable rather than epic-local.The knobs have been live for two plans already. PLAN-07B and PLAN-32 ran concurrently under them and produced zero rebase conflicts, and the post-landing auto-fill correctly skipped two blocked candidates to emit PLAN-31A.
Scope
Configuration only. No production code, no tests, no build behaviour. The file was modified in the working tree while PLAN-07B was in flight and is landed here as its own change rather than folded into an unrelated plan's PR.
Review
Labelled
skip-bot-reviewper operator instruction — a two-line config change with no reviewable surface.