ginnoir
7c7f6dfebc
Protects /config, selective labdata, and nightly DB dumps; documents homelab improvement plan briefs.
1.4 KiB
1.4 KiB
TB-007 — Romhacks → RomM handoff
Status: not started
Your call: (unset — talk first)
Talk first
Stop. Don't read Reference until we've talked. In chat, say "let's do TB-007" or "romhacks → romm handoff".
In one sentence: Finish the pipeline so downloaded ROM hacks land in RomM with cover art.
Why it came up: Orchestrator + JDownloader exist; moving files into the library isn't built yet.
Questions
- Is the Discord/JDownloader pipeline armed, or still theoretical?
- Worth finishing before arming, or drop the whole romhacks stack?
- How much automation vs 'I'll move files manually'?
Your options
| Option | Meaning |
|---|---|
| Do it | We're doing this — I'll implement or walk you through it |
| Later | Keep on the list, not now |
| Drop | Remove from plan — totally fine |
| Tweak | Change scope; tell me how |
What we decided
| Decision | |
| Notes | |
| Date |
Reference (only open if we're doing it)
Stack / files
stacks/romhacks/orchestrator/
If we do it — rough steps
- Complete handoff.py — incoming → Emulation/roms/
- RomM custom cover API
- Test with one staged folder
Done when
- Test ROM in RomM after handoff
- DRY_RUN still safe