📖About

DIAGNOSIS: Shipper (SH-S1) has been failing since 09:00 today. Initially due to syntax error in test_albus_enablement.py (now fixed), but the 14:00 run reveals a permanent blocker: initiatives.db is 102MB, exceeding GitHub 100MB file size limit. The .gitignore only excludes .db-journal/wal/shm but NOT .db itself. The Shipper runs git add -A (line 69 of sh_s1.py) which stages all DB files. Three unpushed commits (e303bb61, 17644266, 01f3b6e7) contain the oversized DB.

PROPOSED FIX: 1. Add *.db to .gitignore 2. git rm --cached all .db files to untrack them 3. Soft-reset the 3 unpushed commits and re-commit without DB files 4. Verify Shipper can push successfully

EVIDENCE:

• ls -lh: initiatives.db is 102MB
• journalctl carol-sh_s1: "File apps/initiatives/initiatives.db is 100.48 MB; this exceeds GitHub file size limit of 100.00 MB"
• plangenerator.db is 27MB and growing (future risk)
• .gitignore has .db-journal but NOT .db

⚖️Decisions

• INI-411 orphan sweep: all bypass executions for this initiative were swept as orphaned (>1200s with no owning process). Transitioning to blocked for operator or resume-loop triage. (elrond.orphan_sweep)
• Reopened to blocked: mis-closed in 2026-06-02 bulk sweep. — Git history rewrite never happened; Shipper is failing on a large DB blob in an unpushed commit. Core deliverable incomplete. (orion)
• Closed as obsolete by Orion triage: git push --dry-run --all succeeds (pushes all refs clean) and *.db/*.db-wal/*.db-shm are now gitignored. The Shipper push failure no longer reproduces. The 2.8G .git history is large but does not block the push. — Situation on the ground changed — push works now. (orion)