Docs migration batch: architecture & how-it-works docs, DB/platform tooling (hatch → code) #5980

Activity

1. dezren39

   added

   documentationImprovements or additions to documentationImprovements or additions to documentation

   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-1646
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-k
   • Session / ID: task 10349
   • Found via: queue claim
   • Task: Triage issue Docs migration batch: architecture & how-it-works docs, DB/platform tooling (hatch → code) #5980 (docs migration batch: architecture & how-it-works docs, DB/platform tooling, hatch → code)
   • Expectation: docs migration batch (25 files); triage done = batch scoped, load-bearing dependency and flagged items recorded below
   • Links: plan ~/workspace/scratch/docs-migration-plan-2026-11-04/plan.md §4.3 (verified present on the sandbox today, with the quota-recorder dependency noted in the plan)

   Triage findings (verified fresh 2026-11-05 via gh + local plan check):

   • Issue Docs migration batch: architecture & how-it-works docs, DB/platform tooling (hatch → code) #5980 is OPEN. Labels: documentation, task/triage, queue/queued. No hard-stop labels (held, user/owned, do-not-merge, do-not-auto-edit) and no user/review / user/escalated. Only comment is an automated Kaneo cross-link.
   • Batch scope (25 files, copy — never delete): tools/supabase-exec.py and tools/turso-exec.py → pkgs/fleet/ or pkgs/database/; tools/cloudflare/wrangler-authed.py + wrangler-secret.py → pkgs/cf/; library/toolchains/ (13 files, excl. binary-backup.md) → doc/platform/toolchains/; library/plans/ai-plans.md + hardware.md and library/inventory-summary.md → doc/platform/; notes/research/muse/ (6 files) → doc/platform/. Sources stay as historical copies; living docs get a one-line Canonical: header after landing.
   • Load-bearing dependency (the one real risk in this batch): the sandbox quota-recorder STAYS in hatch (Drew's ruling, plan §4.3/line 268) and calls tools/supabase-exec.py at its hatch path. The code copy becomes canonical for new work, but the hatch copy must remain functional until the quota-recorder is repointed — the implementing PR must either do that repoint or explicitly defer it in the PR body. Breaking the hatch copy breaks quota recording.
   • Flagged/borderline items, with the issue's own defaults (no Drew decision needed to proceed): library/toolchains/nix.md (overlaps TOOLS.d/nix.md) and muse-cli.md are flagged for Drew but the instruction is to move them with the cluster unless he says otherwise; library/inventory-summary.md is borderline → doc/platform/; the notes/research/muse/ set is tipped to MOVE by Drew's "how Muse tasks work" example. The implementing PR should name these four calls explicitly so the flag is visible at review.
   • Destination decision still open inside the batch: pkgs/fleet/ vs pkgs/database/ for the two SQL helpers — pick one in the PR and state why; everything else has a named destination.
   • Atlas: explicitly out of scope — no Atlas docs are in the repos; Atlas material is swept by the separate Atlas batch issue.
   • Ordering / blockers: none external. This batch is independent copy work; it does not gate, and is not gated by, the other migration batches beyond the shared copy-never-delete rule.

   Triage complete for task 10349; issue #5980 stays open for the migration PR.
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. github-actions

   assigned

   dezren39

   on Nov 5, 2026