Skip to content

Docs migration batch: backup scripts & backup documentation (hatch → code) #5976

Open

Description

@dezren39

Docs migration batch — backup scripts & backup documentation. Part of the hatch → code docs migration tracking issue. Full plan: ~/workspace/scratch/docs-migration-plan-2026-11-04/plan.md (§4.1) in the sandbox workspace.

Rule: copy, never delete. Source files stay in hatch-personal/hatch as historical copies; add a one-line Canonical: header to living docs after the copy lands. Verify no live cron/job references the old path as its only copy before declaring the code copy canonical (cron changes only via the cron tools).

Files (27)

From hatch-personal (= dezren39/hatch) → code:

  • tools/runtime-db-export/ (21 files) → pkgs/agent-backup/ — Muse runtime DB backup/export machinery (schema.sql, spec_m1–m8/r1–r2/s5.json, loaders, prune SQL, README)
  • tools/bws-backup-secrets.sh → pkgs/agent-backup/ — Bitwarden secrets backup. Do NOT run it as part of migration (known delete-then-create hazard).
  • reports/README.md, reports/backup-process-2026-10-21.md → doc/backups/
  • library/toolchains/binary-backup.md → doc/backups/
  • library/skills/muse-backup.md, archive/small-files/workspace/custom-skills/muse-backup/SKILL.md → doc/backups/

Done looks like

Copies committed in code via PR (worktree from origin/main), pointer headers added to the hatch copies of the living docs, references grepped + repointed, this issue closed with the 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 · picked up

    • Agent: queue worker (repo-worker-code), lane code-c
    • Session / ID: task 10345
    • Found via: queue claim
    • Task: Triage issue Docs migration batch: backup scripts & backup documentation (hatch → code) #5976 (docs migration batch: backup scripts & backup documentation, hatch → code) at current main: verify state, scope the migration, record what remains.
    • Expectation: s — triage complete with evidence; implementation enqueued as a follow-up task.
    • Links: plan §4.1 in the sandbox docs-migration plan (2026-11-04)
  4. dezren39 commented on Nov 5, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · done

    • Agent: queue worker (repo-worker-code), lane code-c
    • Session / ID: task 10345
    • Found via: queue claim
    • Task: Triage of issue Docs migration batch: backup scripts & backup documentation (hatch → code) #5976 complete — findings below; implementation follow-up enqueued as task 10506.
    • Expectation: done for task 10345 (triage); implementation proceeds under task 10506.
    • Links: follow-up task 10506 (small_fix, repo-health-code-pilot queue)

    Triage findings (task 10345, verified 2026-11-05)

    • State verified fresh: issue Docs migration batch: backup scripts & backup documentation (hatch → code) #5976 is OPEN, labels at claim were 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. No open PR owns this batch (open-PR search for backup / issue Docs migration batch: backup scripts & backup documentation (hatch → code) #5976 returned none).
    • Not done — verified against current main: pkgs/agent-backup/ exists on main but contains only backup.sh and test-backup.sh (2 files) — none of the 21 tools/runtime-db-export/ files (no schema.sql, no spec_*.json, no loaders/prune SQL) are there. doc/backups/ does not exist on main (contents API 404), so none of the 5 documentation files (reports ×2, library/toolchains/binary-backup.md, muse-backup docs ×2) have landed either.
    • Scope confirmed against the plan: the sandbox plan (docs-migration-plan-2026-11-04/plan.md §4.1, verified on disk) matches the issue exactly: 21 + 1 + 2 + 1 + 2 = 27 files to pkgs/agent-backup/ and doc/backups/. Copy, never delete; Canonical: headers on the living hatch docs after the copy lands; references grepped + repointed; cron/job references changed only via the cron tools.
    • Hazard carried forward: tools/bws-backup-secrets.sh is copied but must NOT be run as part of the migration (known delete-then-create hazard, per the issue and the plan).
    • Disposition: triaged — valid, concrete, and actionable now (not blocked on any parent decision). Implementation enqueued as task 10506 (small_fix) in the repo-health-code-pilot queue with the verified not-done evidence and the hazard note in its packet. Issue Docs migration batch: backup scripts & backup documentation (hatch → code) #5976 stays OPEN until that PR merges.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentationtask/triageQueue packet kind: verify, reproduce, and route this item

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions