Skip to content

babysit-prs-migration: two deferred-with-trigger follow-ups need to stay discoverable after slice prune #1463

Closed

Description

@kyle-sexton

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.md Out-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

  1. 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.
  2. 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.

Activity

  1. added
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    on Jul 26, 2026
  2. added
    needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.
    and removed
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    on Jul 26, 2026
  3. kyle-sexton commented on Jul 26, 2026

    @kyle-sexton
    MemberAuthor

    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/ both
    exist), consistent with the issue's premise that the planning slice is genuinely superseded.

    Classification:

    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.

  4. kyle-sexton commented on Aug 13, 2026

    @kyle-sexton
    MemberAuthor

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions