design: move ci.events webhook ledger from Supabase to Turso staging #5693

Activity

1. dezren39

   added a commit that references this issue on Nov 4, 2026

   docs: link the §9 migration design issues (#5690, #5691, #5692, #5693, …

   ...

   6a3b53c
2. github-actions

   assigned

   dezren39

   on Nov 5, 2026
3. dezren39

   added

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

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

   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

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

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

   

   dezren39

   on Nov 5, 2026

   MemberAuthor

   More actions

   🤖 Agent note · done (triage)

   • Agent: queue worker (repo-worker-code), lane code-t
   • Session / ID: task 10129
   • Found via: queue claim
   • Task: triaged design issue design: move ci.events webhook ledger from Supabase to Turso staging #5693; design basis verified merged, first-pass steps scoped into a follow-up task enqueued in this same pass (addendum comment below names its task id)
   • Expectation: done = issue design: move ci.events webhook ledger from Supabase to Turso staging #5693 routed with evidence; steps 1–2 proceed as the follow-up task
   • Links: PR docs: Scaler-era Atlas/Turso data architecture revision #5667, PR docs: Supabase placement audit addendum (§9) — what moves out of Postgres #5689

   Triage findings (verified fresh 2026-11-05):

   1. Design basis is on main. PR docs: Scaler-era Atlas/Turso data architecture revision #5667 (Scaler-era Atlas/Turso data architecture revision) and PR docs: Supabase placement audit addendum (§9) — what moves out of Postgres #5689 (Supabase placement audit addendum, §9) are both MERGED. The design doc doc/2026-11-04T21-27-34Z_design_atlas_scaler_revision/ names issue design: move ci.events webhook ledger from Supabase to Turso staging #5693 for ci.events: 10,952 rows / 31.8 MB, 10,957 inserts / 0 updates in the window — a pure append-only stream, matching the issue's placement argument.
   2. The inventory cannot be done by repo grep alone. Code search for ci.events and ci.recent_failures in developing-today/code hits ONLY the design doc — the webhook receiver and the view's consumers live outside this repo's code (Supabase-side objects and/or external alerting/dashboards). The follow-up's inventory step must enumerate Supabase-side views/functions and external consumers explicitly, with not-found results stated, not assumed.
   3. Gates preserved: this issue is design-scope only for its first pass (no data moves), and step 4's Postgres drop requires separate approval — the follow-up is scoped to steps 1–2 (inventory + Turso table / recent_failures-equivalent query / retention design, proposing the issue's 90-days-hot window) and explicitly excludes dual-write, backfill, and any cutover.

   Disposition: follow-up triage/design task enqueued in this pass (see addendum). Issue #5693 stays open for it.
5. 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 5, 2026
6. dezren39 commented on Nov 5, 2026

   

   dezren39

   on Nov 5, 2026

   MemberAuthor

   More actions

   🤖 Agent note · addendum to task 10129 triage

   • Agent: queue worker (repo-worker-code), lane code-t
   • Session / ID: task 10129
   • Task: the follow-up named in the triage note above is task 10484 (queue repo-health-code-pilot, status queued): issue design: move ci.events webhook ledger from Supabase to Turso staging #5693 steps 1–2 — inventory of the ci.events receiver/readers plus the Turso table, recent_failures-equivalent query, and retention design. Enqueued immediately after task 10129 completed, because the packet dedupe pattern reuses the standard triage key for issue design: move ci.events webhook ledger from Supabase to Turso staging #5693.
7. dezren39

   added

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

   and removed

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

   on Nov 5, 2026
8. 40 remaining items

   Load more
9. developing-today

   added

   status/parkedDeliberately paused with a recorded resume conditionDeliberately paused with a recorded resume condition

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

    

    dezren39

    on Nov 8, 2026

    MemberAuthor

    More actions

    🤖 Agent note · handed off

    • Agent: queue worker (repo-worker-code), lane code-b
    • Session / ID: task 13031
    • Found via: queue claim
    • Task: Task 13031 for issue design: move ci.events webhook ledger from Supabase to Turso staging #5693 handed off to the opencode claimant per execution-lane assignment; parked 1200s for the claimant to launch the bound session. Revalidated: issue design: move ci.events webhook ledger from Supabase to Turso staging #5693 OPEN, no hard-stop labels.
    • Expectation: claimant session performs the fix remainder.
11. developing-today commented on Nov 8, 2026

    

    developing-todayBot

    on Nov 8, 2026 – with developing.today

    Contributor

    More actions

    🤖 Agent note · handed off

    • Agent: queue worker (repo-worker-code), lane code-e
    • Session / ID: task 13031, repo-queue-worker-shift-e, 2026-11-08T13:54:27Z
    • Found via: queue claim
    • Task: task 13031 for issue design: move ci.events webhook ledger from Supabase to Turso staging #5693 (small_fix). Fresh check: issue design: move ci.events webhook ledger from Supabase to Turso staging #5693 is OPEN, no hard-stop labels (held / user/owned / do-not-merge / do-not-auto-edit). Execution-lane assignment returned opencode - handed off to the opencode claimant, which launches the bound opencode session; this lane does not work it directly. Attempts 4/4 for task 13031.
    • Expectation: claimant launches the bound opencode session and drives task 13031 to a terminal state; parked 20 minutes so task 13031 returns to the queue if the claimant does not bind.
    • Links: issue design: move ci.events webhook ledger from Supabase to Turso staging #5693
12. developing-today commented on Nov 8, 2026

    

    developing-todayBot

    on Nov 8, 2026 – with developing.today

    Contributor

    More actions

    🤖 Agent note · handed off

    • Agent: queue worker (repo-worker-code), lane code-g
    • Session / ID: task 13031
    • Found via: queue claim
    • Task: small_fix issue design: move ci.events webhook ledger from Supabase to Turso staging #5693 — handed off to the opencode claimant per execution-lane assignment (attempts 4/4)
    • Expectation: claimant launches the bound opencode session and drives task 13031 to a terminal state
    • Links: issue design: move ci.events webhook ledger from Supabase to Turso staging #5693
13. dezren39

    added

    queue/claimedQueue worker lifecycle stateQueue worker lifecycle state

    status/in-progressQueue worker lifecycle stateQueue worker lifecycle state

    and removed

    status/parkedDeliberately paused with a recorded resume conditionDeliberately paused with a recorded resume condition

    queue/parkedQueue task is parked (waiting on CI, time, or an event)Queue task is parked (waiting on CI, time, or an event)

    on Nov 8, 2026
14. dezren39 commented on Nov 8, 2026

    

    dezren39

    on Nov 8, 2026

    MemberAuthor

    More actions

    🤖 Agent note · picked up

    • Agent: queue worker (repo-worker-code), lane aea12c82-c5af-4e5a-9b66-f8e360f87177
    • Session / ID: OpenChamber scheduled lane; task 13031
    • Found via: queue claim
    • Task: design: move ci.events webhook ledger from Supabase to Turso staging #5693 cutover remainder; issue OPEN, no hard-stop labels, no competing open PR. PRs github-ci Worker: webhook receiver re-home (#5693) #6921 and github-ci Worker: fleet-repo set union (#5693) #6923 are merged.
    • Expectation: inspect current code/readers and cutover prerequisites, then execute only verified in-scope steps.
    • Links: task 13031 · PR github-ci Worker: webhook receiver re-home (#5693) #6921 · PR github-ci Worker: fleet-repo set union (#5693) #6923
15. dezren39

    added

    queue/blockedQueue or user escalation stateQueue or user escalation state

    status/blockedQueue or user escalation stateQueue or user escalation state

    and 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 8, 2026
16. dezren39 commented on Nov 8, 2026

    

    dezren39

    on Nov 8, 2026

    MemberAuthor

    More actions

    🤖 Agent note · blocked

    • Agent: queue worker (repo-worker-code), lane aea12c82-c5af-4e5a-9b66-f8e360f87177
    • Session / ID: OpenChamber scheduled lane; task 13031
    • Found via: queue claim + fresh GitHub verification
    • Task: blocked as packet_defect. Current design: move ci.events webhook ledger from Supabase to Turso staging #5693 says “Design scope only — no data moves in this issue’s first pass”; task 13031 instead requires live deployment, dual-run and reader/org flips without an explicit issue update authorizing that expansion.
    • Expectation: update design: move ci.events webhook ledger from Supabase to Turso staging #5693 with explicit operational cutover scope/approval and enqueue a corrected packet before work resumes. No code or deployment changes were made.
    • Links: task 13031 · issue design: move ci.events webhook ledger from Supabase to Turso staging #5693