pending-questions: verify live state of linked PRs/issues before presenting an item #6259

Activity

1. dezren39

   added

   meta/follow-upFollow-up spun out of earlier workFollow-up spun out of earlier work

   on Nov 5, 2026
2. developing-today commented on Nov 5, 2026

   

   developing-todayBot

   on Nov 5, 2026 – with developing.today

   Contributor

   More actions

   CODE-1835
3. dezren39

   added

   work/assignedQueue worker lifecycle stateQueue worker lifecycle state

   queue/claimedQueue worker lifecycle stateQueue worker lifecycle state

   status/in-progressQueue worker lifecycle stateQueue worker lifecycle state

   on Nov 6, 2026
4. dezren39 commented on Nov 6, 2026

   

   dezren39

   on Nov 6, 2026

   MemberAuthor

   More actions

   🤖 Agent note · picked up

   • Agent: repo queue worker, lane code-q (repo-worker-code)
   • Session / ID: cron repo-queue-worker-shift-q run 2026-11-06 06:04 CST; task 11042
   • Task: task 11042 triage for issue pending-questions: verify live state of linked PRs/issues before presenting an item #6259 (pending-questions live-state check). Execution lane is direct — verifying the defect against current main myself this shift.
   • Links: task 11042 · issue pending-questions: verify live state of linked PRs/issues before presenting an item #6259 · PR TEMPORARY (Nov 2-4 trough): workhorse primary defaults to Meta - DeepSeek leg parked (#2173 A3) #2984 (the stale item in the issue body)
5. dezren39

   added

   kind/bugSomething isn't working (prefixed form of the classic bug label)Something isn't working (prefixed form of the classic bug label)

   source/humanFiled directly by a humanFiled directly by a human

   priority/normalOrdinary priority (the default)Ordinary priority (the default)

   effort/sSmall: expected under 2 hours of workSmall: expected under 2 hours of work

   status/needs-triageNot yet triaged; needs a first lookNot yet triaged; needs a first look

   meta/enrichedIntake review done: acceptance criteria, links, and normalized labels addedIntake review done: acceptance criteria, links, and normalized labels added

   task/triageQueue packet kind: verify, reproduce, and route this itemQueue packet kind: verify, reproduce, and route this item

   on Nov 6, 2026
6. dezren39 commented on Nov 6, 2026

   

   dezren39

   on Nov 6, 2026

   MemberAuthor

   More actions

   Intake review

   • Related: the 2026-11-05 incident on this issue — PR TEMPORARY (Nov 2-4 trough): workhorse primary defaults to Meta - DeepSeek leg parked (#2173 A3) #2984 presented as an open merge decision two days after it closed as superseded; Drew answered against the stale item and the merge lane's own pre-merge verification was the only thing that stopped it.
   • Notes: Still live at intake — no merged PR references this fix. The defect is in the pending-questions discovery/presentation path, not in the merge lane (which behaved correctly).
   • Risks: a live-state check that caches or races reintroduces the same staleness at a smaller window; check at presentation time, not discovery time.
   • Suggested approach: add the gh live-state read at the present/mark-asked boundary for every gh: link, drop-or-revalidate on closed/merged, and verify claimed recommendations against the record before rendering.

   🤖 Fleet monitor intake (repo-fleet-monitor), 2026-11-06.
7. dezren39 commented on Nov 6, 2026

   

   dezren39

   on Nov 6, 2026

   MemberAuthor

   More actions

   🤖 Agent note · triage verdict: CONFIRMED (live, not yet fixed)

   • Agent: repo queue worker, lane code-q (repo-worker-code), task 11042 (triage, direct lane)
   • Fresh evidence (2026-11-06):
     • Issue pending-questions: verify live state of linked PRs/issues before presenting an item #6259 is OPEN; only label is meta/follow-up — no hard-stop labels.
     • PR TEMPORARY (Nov 2-4 trough): workhorse primary defaults to Meta - DeepSeek leg parked (#2173 A3) #2984 (the stale item): gh pr view → state CLOSED, closedAt 2026-11-03T10:46:26Z, mergedAt null, mergeable CONFLICTING — exactly as the issue describes (closed as superseded, premise reversed 2026-11-02).
     • The ledger side was repaired retroactively: pending-questions ledger item pr-2984 is now status dropped with a note recording the incident ("Item was stale when presented 03:28 … Never resurface").
     • The systemic fix has NOT landed: the live pending-questions-hourly job body (read in full this run) still goes ledger → discovery → pick → mark asked → compose, with no live-state check of an item's linked PRs/issues via gh before presenting or marking asked, and no check that a cited recommendation exists on the record. The same gap applies to the 24h re-ask path (step 1 returns asked items to pending with no state check).
     • Nothing in developing-today/code implements this path — grep for pending-questions / pending_questions across the repo at HEAD dfe3277 returns no presentation code; the presentation path is the Muse cron job pending-questions-hourly (goal pending-decisions-hourly-questions-for-drew), so the fix lands there, not in this repo.
   • Routing: follow-up fix task enqueued from this triage: add a live-state verification step to the pending-questions-hourly job body (repo-copy-first + cron.update per the standing cron rule) — for each candidate item with GitHub links, check linked PR/issue state via gh before presenting and before marking asked; drop/re-validate closed/merged items instead of presenting them; verify any cited recommendation exists on the record; apply the same check on the 24h re-ask path.
   • Links: task 11042 · issue pending-questions: verify live state of linked PRs/issues before presenting an item #6259 · PR TEMPORARY (Nov 2-4 trough): workhorse primary defaults to Meta - DeepSeek leg parked (#2173 A3) #2984
8. 1 remaining item

   Load more
9. dezren39

   added

   queue/queuedHas a queued task in the Supabase agent queueHas a queued task in the Supabase agent queue

   and removed

   queue/claimedQueue worker lifecycle stateQueue worker lifecycle state

   work/assignedQueue worker lifecycle stateQueue worker lifecycle state

   on Nov 6, 2026
10. dezren39 commented on Nov 6, 2026

    

    dezren39

    on Nov 6, 2026

    MemberAuthor

    More actions

    🤖 Agent note · triage done

    • Agent: repo queue worker, lane code-q (repo-worker-code), task 11042
    • Outcome: triaged — verdict CONFIRMED (see findings comment on issue pending-questions: verify live state of linked PRs/issues before presenting an item #6259). Follow-up fix enqueued as task 11121 (small_fix: add the live-state verification step to the pending-questions-hourly job body via the repo-copy-first + cron.update route). Issue pending-questions: verify live state of linked PRs/issues before presenting an item #6259 stays open until task 11121 lands.
    • Links: task 11042 · task 11121 · issue pending-questions: verify live state of linked PRs/issues before presenting an item #6259
11. dezren39

    added

    work/assignedQueue worker lifecycle stateQueue worker lifecycle state

    queue/claimedQueue worker lifecycle stateQueue worker lifecycle state

    status/in-progressQueue worker lifecycle stateQueue worker lifecycle state

    and removed

    status/needs-triageNot yet triaged; needs a first lookNot yet triaged; needs a first look

    queue/queuedHas a queued task in the Supabase agent queueHas a queued task in the Supabase agent queue

    on Nov 6, 2026
12. dezren39 commented on Nov 6, 2026

    

    dezren39

    on Nov 6, 2026

    MemberAuthor

    More actions

    🤖 Agent note · done

    • Agent: queue worker (repo-worker-code), lane code-u
    • Session / ID: task 11121 (fix task from triage task 11042)
    • Found via: queue claim
    • Task: Fix issue pending-questions: verify live state of linked PRs/issues before presenting an item #6259 — pending-questions-hourly presented PR TEMPORARY (Nov 2-4 trough): workhorse primary defaults to Meta - DeepSeek leg parked (#2173 A3) #2984 (closed 2026-11-03 as superseded, verified fresh again today: state CLOSED, closedAt 2026-11-03T10:46:26Z, mergedAt null) as an open merge decision on 2026-11-05 because the job never checked live state.
    • Expectation: effort/s — job-body fix only; no code change in this repo (the presentation path is the Muse cron job, not code here).
    • Links: live job pending-questions-hourly; repo copy goals/pending-decisions-hourly-questions-for-drew/crons/hourly/pending-questions-hourly__interval@1h.md in hatch-personal, commit f93c2ba15

    Fix delivered (2026-11-06):

    • The job body now has a new step 3, LIVE-STATE VERIFICATION: for every candidate item — the items about to be picked, and every asked item the 24h re-ask rule is about to return to pending (step 1 now gates on it explicitly) — the run checks EACH linked PR/issue live via the gh CLI BEFORE marking asked and BEFORE presenting. A closed/merged link means the item is dropped (status "dropped") or re-validated, with the artifact, its live state, and the verification date recorded in the item's note. A cited recommendation may only be presented if verified to exist on the record. Cadence (1h), item cap (1–2), delivery chats, and all other behavior are unchanged.
    • Delivery followed the standing cron rule: the new body text was prepared first, applied to the live job with cron.update (the repo-copy projection is tool-read-only, so the update regenerated it), the projection was verified byte-identical to the prepared text, and committed in hatch-personal as f93c2ba15 (git status for the path clean after commit). Read-back via cron.view shows the verification step verbatim in the live job.

    Dry-pass regression check (the packet's test): every pending/asked ledger item's links were checked live via gh on 2026-11-06:

    • All linked artifacts OPEN except two: issue SECURITY: live GitHub PAT committed in hatch-personal hygiene-scratch dumps — revoke + untrack #6097 (CLOSED — it is the already-completed step 3 of the scratch-git-leg-6100 item; the item's primary link issue Proposal: git second leg for workspace/scratch (+ untrack hygiene-scratch) — core-file backup coverage #6100 is OPEN and its steps 1–2 decision is still real, so under the new step it is re-validated, not dropped) and opencode issue mcpx(tasks): TTL is clocked from creation, not completion — a task still working at its TTL is deleted and cancelled mid-run, and a finished task's retention shrinks by its runtime #1653 (CLOSED — one of three links on wire-only-1825-remainder; primary issue P8.1 time & witnesses: witness protocol design (task-09 + owner's 2026-10-28 direction) #1825 OPEN, PR proxy-relay: RELAY_TARGET_PORTS silently drops invalid entries and reinterprets non-literals — a typo'd target list starts a healthy relay with the wrong targets #1844 OPEN; under the new step this item must be re-validated against the remainder before any re-presentation).
    • The incident shape (an item whose linked PR is closed presented as open) is now caught by step 3 before marking asked, before presenting, and on the 24h re-ask path.

    Closing this issue as fixed.
13. dezren39

    closed this as completedon Nov 6, 2026
14. developing-today

    added

    status:done

    on Nov 6, 2026
15. dezren39

    removed

    status/in-progressQueue worker lifecycle stateQueue worker lifecycle state

    queue/claimedQueue worker lifecycle stateQueue worker lifecycle state

    work/assignedQueue worker lifecycle stateQueue worker lifecycle state

    on Nov 6, 2026