Skip to content

Docs migration batch: Fleet designs, task-system schema & fleet machinery (hatch → code) #5978

Open

Description

@dezren39

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)

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 under pkgs/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 writing agent.repo_snapshots in 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 is pkgs/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.

Activity

  1. developing-today commented on Nov 5, 2026

    @developing-today
    Contributor
  2. added
    queue/queuedHas a queued task in the Supabase agent queue
    task/triageQueue packet kind: verify, reproduce, and route this item
    work/assignedQueue worker lifecycle state
    queue/claimedQueue worker lifecycle state
    and removed
    queue/queuedHas a queued task in the Supabase agent queue
    on Nov 5, 2026
  3. dezren39 commented on Nov 5, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · handed off

  4. added
    queue/parkedQueue task is parked (waiting on CI, time, or an event)
    status/parkedDeliberately paused with a recorded resume condition
    and removed
    queue/claimedQueue worker lifecycle state
    on Nov 5, 2026
  5. dezren39 commented on Nov 5, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · handed off

  6. 101 remaining items

  7. added
    status/parkedDeliberately paused with a recorded resume condition
    queue/claimedQueue worker lifecycle state
    and removed
    queue/claimedQueue worker lifecycle state
    status/parkedDeliberately paused with a recorded resume condition
    queue/parkedQueue task is parked (waiting on CI, time, or an event)
    on Nov 6, 2026
  8. dezren39 commented on Nov 6, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · picked up

    • Agent: queue worker (repo-worker-code), OpenChamber scheduled lane 9aca43b4-5439-4939-9f71-323f5d32521b
    • Task: queue task 10347, triage for issue Docs migration batch: Fleet designs, task-system schema & fleet machinery (hatch → code) #5978
    • Fresh check: issue OPEN; no hard-stop labels; no relevant PR found by GitHub search. Reclaimed after the prior opencode handoff window; this claim has no bound session ID.
    • Next: verify current-main repo state and scope a safe migration/follow-up plan; no code edits in this triage packet.
  9. added
    queue/blockedQueue or user escalation state
    status/blockedQueue or user escalation state
    user/reviewNeeds a user-look: Muse reviews first and handles what it can
    and removed
    queue/claimedQueue worker lifecycle state
    work/assignedQueue worker lifecycle state
    on Nov 6, 2026
  10. dezren39 commented on Nov 6, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · blocked — source packet needs correction

    • Agent: queue worker (repo-worker-code), OpenChamber scheduled lane 9aca43b4-5439-4939-9f71-323f5d32521b
    • Task: 10347 (triage); issue Docs migration batch: Fleet designs, task-system schema & fleet machinery (hatch → code) #5978 remains OPEN. No relevant PR found.
    • Current code main: 9e20032d0cf3034a2baea117caa60c115119138e. pkgs/fleet/ and doc/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 at doc/fleet-schedule-registry.md:88, pointing to /home/hatch/workspace/cron.d/minutely/archer-slack-review__interval@15m.md.
    • Source check: current dezren39/hatch-personal main is fff3830e9b7f910ca233a83680dfe02d35ef5980. Of the named paths, it contains only workspace/supabase/muse-dev/migrations/0018_home_domain.sql and 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.md is 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.
    • Triage: do not recreate or infer missing files. Please attach the authoritative source snapshot/commit (or correct the source paths) and make the migration plan available in a durable location. Then sequence: (1) verify the exact 29 migration files and target schema home/order; (2) copy the remaining docs/tools/schema into pkgs/fleet/ or doc/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.
    • Next: requeue once the source snapshot and plan are available. No code files were changed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

documentationImprovements or additions to documentationqueue/blockedQueue or user escalation statestatus/blockedQueue or user escalation statetask/triageQueue packet kind: verify, reproduce, and route this itemuser/reviewNeeds a user-look: Muse reviews first and handles what it can

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions