# Open Threads — zlh-grind

This file tracks **active cross-repo and platform-level work only**.

Repo-specific work belongs in:
- `Codex/API/OPEN_ITEMS.md`
- `Codex/Portal/OPEN_ITEMS.md`
- `Codex/Agent/OPEN_ITEMS.md`

Keep this file short.

---

## Cross-Repo Active

### Game backup integration
- normalize backup response shape across API and Portal so list/create/restore/delete have stable success bodies and a consistent error envelope
- validate local Minecraft backup/restore flow on a real live server end-to-end
- confirm checkpoint metadata presentation once API exposes the final stable fields to Portal

### Dev access / IDE / SSH
- simplify and harden API `devProxy`
- complete SSH / CF tunnel access path across platform, API, Agent, and Portal UX
- add Portal SSH config snippet for power users

### Service discovery / launch validation
- service discovery migration for remaining hot-path references
- provisioning validation across current API/Agent/Portal assumptions
- Fabric / readiness / Velocity exposure final cross-component verification
- game server subdomain / player connection method verification

### Notifications / launch polish
- email notifications across backend contract + Portal UX
- remove stray `testdameon` / `testdaemon` binary from Portal repo

---

## Platform / Infrastructure Active

- upload testing
- stress testing: k6 IDE load, Minecraft bot load, code-server memory baseline
- OPNsense audit
- billing endpoint/path cleanup verification

### Backup boundary
- Agent-owned backups are local, app-aware rollback backups for Minecraft worlds/config
- PBS / platform backup strategy is the durability / disaster-recovery layer
- do not track PBS/offsite durability work as agent implementation work unless that ownership changes

---

## Platform Future

- CF Tunnel SSH completion beyond first working path
- artifact version promotion
- runtime rollback support
- Cloudflare R2 for large artifact/mod delivery
- admin panel
- referral / dev pipeline reward system
- uptime history
- revisit DDoS mitigation later if needed

---

## Cleaning Rule

- Root keeps only cross-repo/platform work
- Repo-specific items must be removed from root once they live only in one Codex tracker
- Completed items should be removed, not left in place as historical clutter
- Use `CURRENT_STATE.md` for durable implemented behavior
- Use `DECISIONS.md` for settled choices
- Re-open old items only when there is current evidence they are still unfinished or have regressed