Repository navigation
Open
Labels
documentationImprovements or additions to documentationImprovements or additions to documentationqueue/blockedQueue or user escalation stateQueue or user escalation statestatus/blockedQueue or user escalation stateQueue or user escalation statetask/triageQueue packet kind: verify, reproduce, and route this itemQueue packet kind: verify, reproduce, and route this itemuser/reviewNeeds a user-look: Muse reviews first and handles what it canNeeds a user-look: Muse reviews first and handles what it can
Description
Docs migration batch — Fleet designs & fleet machinery. Part of the hatch → code docs migration tracking issue. Full plan: ~/workspace/scratch/docs-migration-plan-2026-11-04/plan.md (§4.2).
Rule: copy, never delete. Sources stay as historical copies; add one-line Canonical: headers to living docs after landing. Grep for live references (cron bodies, TOOLS.d, goal workspaces) before declaring the code copy canonical.
Already done (no action)
tools/fleet-brokers/(13 files) — canonical source already moved 2026-11-04 (see fleet step 2: queue domain pilot — brokers into pkgs/fleet, one-flip-at-a-time migration #5430):pkgs/fleet/crates/fleet-queue/. Hatch copy is rollback evidence. Recorded here for enumeration completeness.
Files (42)
From hatch-personal (= dezren39/hatch) → code:
workspace/supabase/muse-dev/migrations/— all 29 migration files (0001_agent … 0024_fleet_repos_zettel_dezren39) → schema home underpkgs/fleet/(exact subdir: this issue's PR decides). This is the agent/task-queue database schema — the substrate of "how Muse tasks work."tools/fleet-fetch.py,tools/fleet-build-lock→pkgs/fleet/— repo-snapshot fetcher writingagent.repo_snapshotsin Supabase.workspace/archer-slack/(6 files: slack-agent-design.md, puller/, manifest, usage log, authority doc) →doc/fleet/+ implementation home.notes/architecture/mcpx-opencode-plan.md→doc/fleet/— mcpx + opencode design/plan (mcpx canonical home ispkgs/mcpx).tools/lane-claim.sh,tools/lane-handoff.sh,tools/repo-task-v1.schema.json,tools/enqueue-when-green.sh→pkgs/fleet/— pre-fleet-binary queue artifacts + repo-task schema. Borderline: grep live references first; some sandbox jobs may still execute these paths.
Done looks like
Copies committed via PR, pointer headers on living docs, references repointed, issue closed with PR link.
Metadata
Metadata
Assignees
Labels
documentationImprovements or additions to documentationImprovements or additions to documentationqueue/blockedQueue or user escalation stateQueue or user escalation statestatus/blockedQueue or user escalation stateQueue or user escalation statetask/triageQueue packet kind: verify, reproduce, and route this itemQueue packet kind: verify, reproduce, and route this itemuser/reviewNeeds a user-look: Muse reviews first and handles what it canNeeds a user-look: Muse reviews first and handles what it can
Activity
developing-today commentedon Nov 5, 2026
CODE-1644
dezren39 commentedon Nov 5, 2026
🤖 Agent note · handed off
dezren39 commentedon Nov 5, 2026
🤖 Agent note · handed off
101 remaining items
dezren39 commentedon Nov 6, 2026
🤖 Agent note · picked up
dezren39 commentedon Nov 6, 2026
🤖 Agent note · blocked — source packet needs correction
9aca43b4-5439-4939-9f71-323f5d32521b9e20032d0cf3034a2baea117caa60c115119138e.pkgs/fleet/anddoc/fleet/already exist; the requested migration targets are not present there. A tracked search for the listed script/schema/doc names found only the Archer Slack schedule-registry row atdoc/fleet-schedule-registry.md:88, pointing to/home/hatch/workspace/cron.d/minutely/archer-slack-review__interval@15m.md.dezren39/hatch-personalmain isfff3830e9b7f910ca233a83680dfe02d35ef5980. Of the named paths, it contains onlyworkspace/supabase/muse-dev/migrations/0018_home_domain.sqland Archer Slack state artifacts; it does not contain the other 28 claimed migrations,fleet-fetch.py,fleet-build-lock, the Archer docs/implementation,mcpx-opencode-plan.md, or the four queue scripts/schema. The cited/home/user/workspace/scratch/docs-migration-plan-2026-11-04/plan.mdis not present on this laptop. The local hatch checkout has staged deletions and is behind origin, so I did not use or modify it as a source of truth.pkgs/fleet/ordoc/fleet/, preserving the hatch copies; (3) grep and repoint live consumers, including the Archer schedule reference; (4) add canonical headers only after landing and validate references.