Skip to content

Standard task: per-repo hygiene census + cleanup documentation (low priority) #3205

Open

Description

@dezren39

Low priority — standing standard task + tracking. Established 2026-10-31 from a measured fleet-wide repo hygiene census ordered by Drew.

Source documents (sandbox workspace, ~/workspace/)

  • repo-history-census-2026-10-31.md — per-repo blob census of main-branch history: junk classes, packed/uncompressed sizes, fresh-clone simulations, rewrite verdicts
  • repo-inventory-2026-10-31.md — full inventory: every repo across dezren39 + all member orgs, with commit counts and first/last commit dates

Per-repo hygiene notes (filed 2026-10-31)

Fleet-wide findings

  • Scope: 863 repos across 17 owners (dezren39 + 16 orgs); 825 repos have commits; 635 are forks. Most fleet size is upstream history in forks, not our junk.
  • Fresh clones are already lean. For the six repos deep-dived (blob-level census), fresh main-only clones run 10–449 MB, and GitHub's repo sizes track the measured main packs within ~±10% — there is no hidden server-side bloat. (An early reading suggesting ~1.9 GB of GitHub-side sprawl was a fabricated tool output, retracted in the census doc after two independent re-runs agreed with on-disk measurement.)
  • No history rewrites anywhere. The best case in the fleet (hatch-personal) would save 55 MB packed; the costs — every clone/worktree invalidated (~150 sandbox worktrees plus laptop primaries), open PRs orphaned (code 53, opencode 15, openchamber 12, nix 6, re-measured 2026-10-31), all cited SHAs stale — exceed the saving everywhere. The two forks (opencode, openchamber) must never be rewritten: it would sever upstream sync permanently, and on public repos the old history survives in forks and PR refs regardless.
  • The only real saving is local-clone git gc + stale-ref cleanup (e.g. hatch-personal local .git 1.6 GB vs a 183 MB repo; hatch local 1.5 GB vs 100 MB). Deferred by Drew's choice ("locally is fine for now", 2026-10-31) — no SHAs change when it eventually happens.
  • Tip hygiene beats history surgery. hatch-personal PR Bump build/buck/preludes/buck2-prelude from 3a02ea3 to 40b94fa #11 (2026-10-31) untracked 4,433 scratch entries and gitignored the scratch classes; code's tip is already clean except one 12.5 MB doc file. Keeping junk out going forward is the whole game.

The recurring standard task

Quarterly (and ad hoc when triggered):

  1. Re-run the repo inventory (all owners, commit counts + date ranges) and the blob census for the fleet's actively developed repos.
  2. File or update a per-repo hygiene note (same title pattern: Repo hygiene: history & tip cleanup notes (low priority, measured <date>)) in any repo where:
    • the main-branch pack crosses ~250 MB, or
    • junk classes (build outputs, binaries, logs, scratch/dump dirs, committed databases) appear at the tip, or
    • a repo's verdict changes (e.g. Roc artifacts in code confirmed accidental → untrack + gitignore at tip).
  3. Update this issue with links to the new/updated per-repo notes and a one-line fleet summary.
  4. Never rewrite history as part of this task — especially never on forks. Any proposed rewrite needs Drew's explicit per-repo approval with the blast radius spelled out.
  5. Standing rules enforced by the census: gitignore scratch classes; no binaries/logs/build outputs at the tip; runtime state files live outside repos (~/.local/state/, pm-aggregator precedent) with summaries committed instead.

Open items carried by the per-repo notes

  • code: are pkgs/roc libhost.a / .rh / dynhost + build outputs intentional distribution artifacts? Is doc/NanoPi (12.5 MB, tip) a keeper?
  • hatch-personal: relocate in-place state JSONs out of the repo? Optional local git gc (deferred by choice).
  • nix: is .lootbox/lootbox.db (2.8 MB) intentional?
  • opencode / openchamber / hatch: measured clean or upstream-owned; no open actions.

Acceptance criteria

  • The per-repo hygiene census is re-run on the stated cadence (quarterly, or sooner if a repo's main pack crosses ~250 MB or junk classes appear at the tip) and the census + inventory documents are refreshed.
  • Every fleet repo's hygiene verdict (rewrite / never-rewrite / no action) stays on record in its per-repo notes issue, linked from this tracking issue.
  • No history rewrite is performed under this task without a fresh measured case that beats the verdicts already recorded.

Activity

  1. added
    priority/lowNice to have; do when convenient
    kind/docsDocumentation improvement or addition
    effort/mMedium: expected under 1 day of work
    meta/enrichedIntake review done: acceptance criteria, links, and normalized labels added
    on Oct 31, 2026
  2. dezren39 commented on Oct 31, 2026

    @dezren39
    MemberAuthor

    Intake review

    Fleet monitor intake pass (protocol §5), 2026-10-31.

    Related: Tracking issue for the fleet hygiene census (source docs: repo-history-census-2026-10-31.md, repo-inventory-2026-10-31.md). Per-repo notes: code#3204, opencode#1101, openchamber#1069, nix#1265, plus hatch-personal#12 and hatch#1 (outside the four fleet repos).

    Notes / risks / suggested approach: Documentation/tracking only — no action scheduled; the measured verdict for every deep-dived repo is NO history rewrite. Risk: the standing task is mistaken for pending cleanup work; it is a cadence + record-keeping task. Suggested approach: leave open as the census tracker; refresh the two source documents on each quarterly re-run.

  3. added
    queue/queuedHas a queued task in the Supabase agent queue
    source/creatorFiled by the new-issue-creator job
    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 3, 2026
  4. 12 remaining items

  5. dezren39 commented on Nov 3, 2026

    @dezren39
    MemberAuthor

    Launched queue task 8219 for execution in the bound OpenCode session ses_e5e5cb338b3ffeiXbSCE5eJCgu.

  6. dezren39 commented on Nov 3, 2026

    @dezren39
    MemberAuthor

    Triage — standing tracker remains live (2026-11-03)

    Verified issue state immediately before this note: OPEN. Rechecked repository main at dcca6cd510866556a00dedb2c92b7d21cf817e2b; worktree was clean.

    The per-repo record, code#3204, was closed on 2026-11-03 after a current-main tip check. I rechecked the relevant tracked paths at this newer main:

    • 5,973 tracked paths; only regular file above 2 MiB is the documented doc/NanoPi M3 - FriendlyELEC WiKi.pdf (13,078,807 bytes).
    • pkgs/id/id is a 17-byte tracked symlink to ./target/debug/id; its 912,901,552-byte target is ignored under **/target and is not part of the repository. pkgs/roc/build is likewise a symlink to lib/build.sh, not a checked-in build output.
    • pkgs/cold-store-reaper/worker/dist/worker.js (20,612 bytes) is the documented deployable worker bundle, not junk. The 313 tracked .log/.err/.out records total 2,326,917 bytes and are research/spike evidence under doc/.

    Disposition: no immediate cleanup or history rewrite is scoped. Keep this issue open as the quarterly fleet-census tracker; code#3204 remains the per-repo evidence record. No blocker prevents the next scheduled pass: rerun the fleet inventory/census by 2027-01-31, earlier only if the stated ~250 MB main-pack or tip-junk trigger is met. Do not reopen code#3204 or change files based on this tracker triage alone.

  7. added
    work/assignedQueue worker lifecycle state
    queue/claimedQueue worker lifecycle state
    and removed
    queue/queuedHas a queued task in the Supabase agent queue
    on Nov 4, 2026
  8. dezren39 commented on Nov 4, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · handed off

    • Agent: queue worker (repo-worker-code), lane code-h
    • Session / ID: task 8896
    • Task: Claimed by lane code-h; execution-lane assignment returned opencode — handed off to the laptop claimant, which launches the bound opencode session to triage this standing hygiene-census standard task. Queued/needs-triage labels were reset to the claimed set on pickup.
  9. dezren39 commented on Nov 4, 2026

    @dezren39
    MemberAuthor

    agent-note:v1
    event: handed-off
    task: 8896 (triage, repo-health-code-pilot; worker repo-worker-code; lane code-t)
    by: repo-queue-worker lane T

    Handed off to the opencode claimant (execution lane: opencode, lane-assignment row 1968). The claimant launches the bound session that drives task 8896 to its terminal state.

  10. dezren39 commented on Nov 4, 2026

    @dezren39
    MemberAuthor

    Re-claimed by lane code-k as task 8896 after the previous handoff lease lapsed unlaunched, and handed off to the opencode execution lane again: the laptop claimant will launch a bound session for task 8896. Issue #3205 is OPEN, labels already show queue/claimed + status/in-progress. Note: task 8896 is at attempt 3 of 4 — if this lease also lapses unlaunched, the attempt cap will need a raise.

  11. dezren39 commented on Nov 4, 2026

    @dezren39
    MemberAuthor

    agent-note:v1
    state: picked up
    task: 8896
    worker: repo-worker-code
    lane: 8ac61616-3815-4e7b-b33d-840a3829154a
    Fresh pickup check: issue #3205 is OPEN, with queue/claimed + status/in-progress + work/assigned labels and no hard-stop labels. It already has a prior triage finding (comment 6615867254) to keep the quarterly census tracker open; I am revalidating that finding at current main and will not redo or expand the census.

  12. dezren39 commented on Nov 4, 2026

    @dezren39
    MemberAuthor

    agent-note:v1
    state: triaged
    task: 8896
    worker: repo-worker-code
    lane: 8ac61616-3815-4e7b-b33d-840a3829154a
    Current-main recheck: origin/main 9c59763; issue #3205 is OPEN; no matching open PR; no hard-stop labels. The preceding current-main triage (comment 6615867254) records the measured no-rewrite verdicts, code#3204 as the per-repo evidence note, and no immediate tip cleanup. The relevant code paths have no changes since that review, and the next quarterly fleet census is due 2027-01-31.
    Verdict: keep #3205 open as the quarterly tracker. No immediate cleanup/fix task is confirmed, so no follow-up task is enqueued. Continue to prohibit history rewrites without a fresh measured case and Drew's explicit per-repo approval. No code edits or tests were needed; this was a state/evidence revalidation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

effort/mMedium: expected under 1 day of workkind/docsDocumentation improvement or additionmeta/enrichedIntake review done: acceptance criteria, links, and normalized labels addedpriority/lowNice to have; do when convenientsource/creatorFiled by the new-issue-creator jobtask/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