Repository navigation
feat(kanban): deliberate single-sub worker pin --pin-sub <reason> (t_957ca870) - #1318
Merged
Merged
Conversation
…957ca870) Restores pinning a card/lane to one Claude sub (claude-bpx-N/apx-N), which #1116 removed with a blanket refusal, behind an explicit reason: - create / set-model (+batch) / lane-model set take --pin-sub REASON and --pin-sub-fallback; stored in tasks.pin_sub_reason/pin_sub_fallback and lane_model_overrides.pin_sub_reason (migrated); 'sub pin:' audit comment. - Without the flag single-sub routes stay refused (text now names the pool and the flag instead of 'workers never pin'). Pre-rename aliases are refused even with the flag. Admission reads usage-registry.json (row enabled; apx refused during burn-in); unreadable registry fails closed. Sub 0 is pinnable as a last resort (pool-side reservation protects it). - Dispatcher: card pin route source=pin (lane: pin(lane-override(..))); a capped/cooling/circuit-open pinned sub WAITS (deferred, pin_fallback= wait) instead of taking the profile ladder; --pin-sub-fallback rides the family pool when admissible. Flagship + load gates unchanged. - show/list print [PIN claude-bpx-N: reason]; new 'kanban pins [--json] [--stale-hours N]' lists live pins (exit 1 on stale = daily lint). - Any unpinned route write / edit --model clears the pin. Verified: test_kanban_sub_pin_optin.py 28 + test_kanban_pinned_sub_refusal.py 25 pass; neighbour kanban route/lane/pool/effort suites 194 pass. 8 mutants (predicate ignores flag, registry skipped, pin hold removed, source=pin removed, stale pin kept, fallback ignored, badge dropped, apx burn-in check dropped) each fail the new suite. 4 flagship tests fail identically on clean fork/main in a worker session (UNHOMED session guard) - inherited. Card: t_957ca870
|
🤖 merged-by: apollo · lane: kanban-merge-pass · gate: ADVISORY (FleetReview not green for 498b65f): fleetreview-advisory-20260927-standing.md · why: t_957ca870: FORK FEATURE: deliberate single-sub worker pin (--pin-sub ) — restore th; Argus off card review (Ace 13:08), CI green |
ang-fleet-ci-actuators
Bot
added
the
fleetreview:post-merge
FleetReviewFleetReview's daily member-call budget is spent (1200/1200 for 2026-09-27 UTC); review skipped. FleetReview · reviewKind: skipped-budget |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
feat(kanban): deliberate single-sub worker pin --pin-sub (t_957ca870)
Restores pinning a card/lane to one Claude sub (claude-bpx-N/apx-N),
which #1116 removed with a blanket refusal, behind an explicit reason:
--pin-sub-fallback; stored in tasks.pin_sub_reason/pin_sub_fallback and
lane_model_overrides.pin_sub_reason (migrated); 'sub pin:' audit comment.
and the flag instead of 'workers never pin'). Pre-rename aliases are
refused even with the flag. Admission reads usage-registry.json (row
enabled; apx refused during burn-in); unreadable registry fails closed.
Sub 0 is pinnable as a last resort (pool-side reservation protects it).
a capped/cooling/circuit-open pinned sub WAITS (deferred, pin_fallback=
wait) instead of taking the profile ladder; --pin-sub-fallback rides the
family pool when admissible. Flagship + load gates unchanged.
[--stale-hours N]' lists live pins (exit 1 on stale = daily lint).
Verified: test_kanban_sub_pin_optin.py 28 + test_kanban_pinned_sub_refusal.py
25 pass; neighbour kanban route/lane/pool/effort suites 194 pass. 8 mutants
(predicate ignores flag, registry skipped, pin hold removed, source=pin
removed, stale pin kept, fallback ignored, badge dropped, apx burn-in check
dropped) each fail the new suite. 4 flagship tests fail identically on
clean fork/main in a worker session (UNHOMED session guard) - inherited.
Card: t_957ca870
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.