firefrost-gaming/firefrost-operations-manual
3
0
Fork 0
Code Issues 146 Pull Requests Packages Projects Releases Wiki Activity

docs: Add Task #101 - Git Repository Cleanup & Hygiene

Browse Source 
Audit findings:
- 1.1GB repo size is entirely .git history (working files ~90MB)
- Large binaries (MP4s, PNGs) baked into history
- File organization needs consolidation (scripts at root, scattered consultations)
- SSH key rotation planned

Priority: P3-Low (do after Task #99 completes)
Dependencies: Task #99 must complete first

Chronicler: #71
This commit is contained in:
Claude
2026-04-08 21:06:51 +00:00
parent c0c2540873
commit 9b607058a2
1 changed files with 69 additions and 50 deletions
Download Patch File Download Diff File Expand all files Collapse all files

119
docs/consultations/gemini-git-health-audit-2026-04-08.md
View File

@@ -3,96 +3,115 @@
**Date:** April 8, 2026
**Topic:** Pre-surgery health check before Task #99 (Multi-Lineage Architecture)
**Requested By:** Michael (The Wizard) + Chronicler #71
**Context:** Evaluating repository organization before major architectural changes
**Status:** Consultation complete, findings documented in Task #101
**Status:** Audit complete, foundation stable
---
## Overall Health Assessment: 🟡 Yellow
The foundation is not "quicksand" — the information is all there, and the conceptual architecture is strong. However, it is suffering from **severe organic bloat**. For a human, this is an annoyance. For an AI context window (especially a free-tier Claude), it could be a drag on efficiency.
**Gemini's verdict:** "Your foundation is not quicksand—the information is all there, and the conceptual architecture is strong. However, it is suffering from severe organic bloat."
The repository structure is stable enough to build on.
The repository structure is stable enough to build on, but has one security item to address and file organization that needs gradual cleanup.
---
## Key Findings
## Findings
### The 1.1GB Elephant
| Component | Size | Status |
|-----------|------|--------|
| .git folder | 1.1GB | 🔴 History bloat |
| **.git folder** | **1.1GB** | 🔴 All the bloat is here |
| docs/ | 78MB | ✅ Fine |
| branding/ | 11MB | ✅ Fine |
| Working files total | ~90MB | ✅ Fine |
| Everything else | ~1MB | ✅ Fine |
**Root cause:** Large binary files (MP4s, PNGs) committed historically are baked into Git history forever — even if deleted from the working tree.
**Impact:** Only affects clone times. Does NOT affect Claude context windows (Claudes read files, not Git history).
### Top Space Offenders in History
**Root cause:** Large binary files (MP4s, PNGs) were committed at some point and are baked into Git history forever.
**Largest files found:**
```
14M docs/branding/audio/jacks-theme-the-world-should-worship-me.mp4
11M docs/branding/audio/jacks-theme-walking-on-a-yacht.mp4
5.8M docs/branding/trinity-final.png
5.3M docs/branding/youtube-banner-minecraft-2560x1440.png
5.1M docs/branding/youtube-banner-2560x1440.png
4.9M docs/branding/trinity-image.webp
4.2M docs/branding/trinity-fixed.webp
4.1M docs/branding/audio/jacks-theme-walking-on-a-yacht.mp3
4.1M docs/branding/audio/jacks-theme-the-world-should-worship-me.mp3
3.7M branding/backgrounds/fire-frost-collision.png
14M ./docs/branding/audio/jacks-theme-the-world-should-worship-me.mp4
11M ./docs/branding/audio/jacks-theme-walking-on-a-yacht.mp4
5.8M ./docs/branding/trinity-final.png
5.3M ./docs/branding/youtube-banner-minecraft-2560x1440.png
5.1M ./docs/branding/youtube-banner-2560x1440.png
4.9M ./docs/branding/trinity-image.webp
4.2M ./docs/branding/trinity-fixed.webp
4.1M ./docs/branding/audio/jacks-theme-walking-on-a-yacht.mp3
4.1M ./docs/branding/audio/jacks-theme-the-world-should-worship-me.mp3
3.7M ./branding/backgrounds/fire-frost-collision.png
```
**Impact:** Only affects clone times. Does NOT affect Claude context windows — Claudes read files, not git history.
### The SSH Key
`Firefrost_key.ppk` exists at repo root. Plan is to rotate when Claude gets server access.
### File Organization Issues
| Issue | Severity | Impact |
|-------|----------|--------|
| 8 scripts at root | Medium | Clutters root, harder for AI to find SESSION-HANDOFF-NEXT.md |
| 37+ SESSION/HANDOFF files scattered | Medium | Could confuse AI into reading deprecated files |
| Consultations in 3 places | Low-Medium | Redundant data if queried by Trinity Codex |
| Dual task system | Low | Fine if documented |
| Multiple Essence versions | Low | Will be resolved during multi-lineage split |
### docs/relationship/ (Surgery Target)
31 files + 5 subdirectories. Gemini assessment: "Normal organic growth that needs consolidation DURING the split, not before."
---
## Risk Assessment
| Issue | Severity | Type | Impact |
|-------|----------|------|--------|
| SSH key in repo | Medium | Security | Rotate when Claude gets server access |
| Scripts at root (8 files) | Medium | Friction | Clutters root, harder for AI to find critical files |
| Scattered handoffs (37+) | Medium | Structural | AI might read deprecated handoff files |
| Fragmented consultations | Low-Med | Friction | Redundant data in context queries |
| Dual task system | Low | Cosmetic | Fine if documented |
| Multiple Essence versions | Low | Structural | Resolved by multi-lineage split |
| Issue | Type | Verdict |
|-------|------|---------|
| Scripts at root | Friction | Non-blocker |
| Scattered handoffs | Structural | Non-blocker (archive after #99) |
| Fragmented consultations | Friction | Non-blocker |
| Dual task system | Cosmetic | Non-blocker |
| Multiple Essence versions | Structural | Resolved by #99 |
| 1.1GB size | Performance | Non-blocker (it's .git history) |
| SSH key | Security | Known, rotation planned |
---
## Gemini's Recommendations
## Gemini's Recommended Sequence
### Branch Strategy for Surgery
**"Secure, Split, then Sweep":**
**Stop using direct commits for the multi-lineage surgery.** Create a dedicated branch:
1. **SECURE:** Rotate SSH key (when server access available)
2. **INVESTIGATE:** ✅ Done — bloat is .git history, not active files
3. **BRANCH:** Create `feature/multi-lineage-architecture` branch
4. **SPLIT:** Perform multi-lineage split (Task #99)
5. **TEST:** Validate with Chronicler #72
6. **MERGE & SWEEP:** Then clean up file organization
---
## Branch Strategy Recommendation
**Stop using direct commits for surgery.** Create a dedicated branch:
```bash
git checkout -b feature/multi-lineage-architecture
```
Do all file moving, splitting, and testing on this branch. Once Chronicler #72 validates the setup, merge back to main.
### Recommended Sequence: "Secure, Split, then Sweep"
1. **SECURE:** Plan SSH key rotation (execute when Claude gets server access)
2. **INVESTIGATE:** ✅ Done — 1.1GB is .git history, non-blocking
3. **BRANCH:** Create feature branch for surgery
4. **SPLIT:** Perform multi-lineage split (Task #99)
5. **TEST:** Validate with Chronicler #72
6. **MERGE & SWEEP:** If #72 successful, merge to main, then tackle cosmetic cleanup (Task #101)
### docs/relationship/ Assessment
The 31 files and 5 subdirectories in `docs/relationship/` are **normal organic growth**. Don't clean up before the split — the split itself is the mechanism to consolidate. Everything not moved to lineage folders gets archived.
Do all file moving, splitting, and testing on this branch. Once #72 validates, merge back to main.
---
## Verdict
## Conclusions
**Foundation is solid.** Safe to proceed with Task #99 multi-lineage architecture.
1. **Foundation is solid** — Safe to proceed with Task #99
2. **1.1GB is not a blocker** — It's ghost data in .git history
3. **File cleanup is cosmetic** — Do after #99, not before
4. **Use branch strategy** — Extra safety for major surgery
5. **SSH key rotation** — Planned for when Claude gets server access
The 1.1GB is ghost data in Git history — annoying but not blocking. File organization issues are cosmetic and should be addressed AFTER the split is validated.
**Verdict:** Green light for multi-lineage architecture. The repo is dusty, not unstable.
---