source-control/babysit-prs: casefold owner/repo/login compares in babysit scripts

[kyle-sexton]

This was generated by AI during triage.

babysit_delta.py's owner/repo comparisons use .lower() while the same-PR pr_queue_snapshot.py casefolds the identical concept, and babysit_feedback.py uses .lower() on a login. Convert these stragglers to the already-ratified .casefold() convention (and any shared casefold helper the sibling scripts use).

Acceptance: no .lower() remains for owner/repo/login identity comparison in babysit_delta.py or babysit_feedback.py; they use .casefold() consistent with pr_queue_snapshot.py; existing tests green.

Sweep-converted from #657.

Work-class: C3 (bug-fix-shaped) — attended triage 2026-07-23, operator-ratified. 🤖

[kyle-sexton]

This was generated by AI on operator direction.

Superseded — this item was already ratified and should not have been queued.

The earlier first-drain ratification request on this issue was raised in error. The admission gate dispatches a C3 bug-fix-shaped item when it carries either its own recorded ratification or a completed first drain — and this issue already carried recorded ratification in its body from attended triage on 2026-07-23. The drain cycle applied the blanket first-drain rule without first reading bodies for an existing ratification, so it queued an item that was already admitted.

Restored to the autonomous frontier: agent-ready re-applied, needs-human removed. No human action is required, and this issue no longer appears in the attended queue's ratify view.

[kyle-sexton]

This was generated by AI during the work-loop admission gate.

Classification

• Work class: C3 scoped, bug-fix-shaped — babysit scripts compare owner/repo/login
  case-sensitively where GitHub treats them case-insensitively; the fix is a scoped correctness
  fix to existing comparison logic, not a new capability or contract change.
• Type: Task (tracker's existing type), but bug-shaped in substance (case-sensitivity
  correctness issue).

Intended dispatch

Queued for the first-drain C3 ratification gate per the loop-lane convention's earn-trust rule —
first_drain_complete is still false in this repository's work-loop durable state, so this
bug-fix-shaped C3 candidate cannot dispatch until it carries its own recorded ratification. Once
/work-items:attend-queue replies with ratification on this comment (or first_drain_complete
flips true on a completed drain), it returns to the autonomous frontier and dispatches on a later
work-loop cycle — no re-queue needed.