You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
babysit-prs-migration: two deferred-with-trigger follow-ups need to stay discoverable after slice prune #1463
This was generated by AI during work-loop execution.
Companion to #1424 Phase A, filed in response to a review finding on #1459. docs/topics/babysit-prs-migration/ is being pruned (the engine it plans — /source-control:babysit-prs
and /source-control:babysit-loop — has shipped; #1424 classifies the slice's remaining [DOING]/[TODO]
marks as stale). Its PLAN.mdOut-of-scope section records two items deferred with an explicit
trigger condition, and a target-tree search confirms neither trigger survives anywhere outside the
slice. docs/conventions/topic-docs/README.md requires actionable follow-ups to graduate to the tracker
before a slice is pruned, so they are routed here rather than silently dropped.
Deferred-with-trigger items
Cross-machine lease/claim infrastructure (L4 claim markers). Trigger: L1–L3 detection proves
insufficient in real multi-machine operation. Today one machine owning a given repo's babysit is a
human convention — L3-detected, not enforced.
Review-bot interface/adapter layer. Trigger: a feedback-form configuration cannot express a
review bot. The generalized review-trigger module currently keeps every GitHub-side AI reviewer
working through config alone; the adapter arrives only if that stops holding.
Disposition
Neither trigger has fired as of this filing. This issue exists so the two items and their trigger
conditions stay discoverable after the source slice is deleted — it is not an instruction to act now.
Whoever revisits should re-check each trigger before treating the item as actionable.
The slice's other deferred entries need no routing: its USER-RESERVED question (freshness/re-anchor
skill name and placement) was routed to #312 and settled there, and the remaining deferred questions
were resolved at the Phase-2 architect pass ("Open questions: None for Phases 1–2").
Source
docs/topics/babysit-prs-migration/PLAN.md, Brief section — Out-of-scope bullets 1–2, as of origin/main before the #1459 Phase A prune.
Redundancy check: no existing tracker item covers babysit-prs-migration's two deferred items; not
a duplicate. No docs/out-of-scope/ ledger in this repo.
Verification: confirmed against PR #1459 (merged), whose body names this issue by number as the
routing destination for the babysit-prs-migration exposure found during its review. The referenced
engine (/source-control:babysit-prs, /source-control:babysit-loop) is confirmed shipped
(plugins/source-control/skills/babysit-prs/, plugins/source-control/skills/babysit-loop/ both
exist), consistent with the issue's premise that the planning slice is genuinely superseded.
Classification:
Type: Task.
Priority: low — both items are trigger-gated and unfired ("L1-L3 detection proves insufficient in
real multi-machine operation"; "a feedback-form config cannot express a review bot"), matching the
low tier.
Batching determination: see #1464's comment for the shared reasoning across #1464/#1463/#1457 —
same procedural pattern, disjoint content and triggers, no PR/code work to consolidate, so this stays
a separate item rather than merging with the other two.
Activity
kyle-sexton commentedon Jul 26, 2026
This was generated by AI during triage.
Triage
Redundancy check: no existing tracker item covers babysit-prs-migration's two deferred items; not
a duplicate. No
docs/out-of-scope/ledger in this repo.Verification: confirmed against PR #1459 (merged), whose body names this issue by number as the
routing destination for the babysit-prs-migration exposure found during its review. The referenced
engine (
/source-control:babysit-prs,/source-control:babysit-loop) is confirmed shipped(
plugins/source-control/skills/babysit-prs/,plugins/source-control/skills/babysit-loop/bothexist), consistent with the issue's premise that the planning slice is genuinely superseded.
Classification:
low— both items are trigger-gated and unfired ("L1-L3 detection proves insufficient inreal multi-machine operation"; "a feedback-form config cannot express a review bot"), matching the
low tier.
and recognizing that a trigger has fired is a human/product judgment call, not a bounded
implementation task. Kept open; not closed, per the issue's own stated discoverability purpose.
Batching determination: see #1464's comment for the shared reasoning across #1464/#1463/#1457 —
same procedural pattern, disjoint content and triggers, no PR/code work to consolidate, so this stays
a separate item rather than merging with the other two.
kyle-sexton commentedon Aug 13, 2026
Frontier disposition (drain session)
Ruling: Close as completed.
babysit-prs-migration deferred-with-trigger follow-ups routed to this tracker surface before slice deletion; triggers remain unfired.
Re-open trigger: When a babysit-prs-migration deferred trigger fires.