# SteamCache2 Improvement Plans

This directory contains prioritized, actionable plans extracted from the full code review.

Use these files as the source of truth for future implementation work (via `/implement`, manual PRs, or issue tracking).

## Files

| File   | Focus Area                        | Risk Level      | Recommended Order |
|--------|-----------------------------------|-----------------|-------------------|
| [P0.md](./P0.md) | Critical stability, crashes, leaks, startup validation | Ship-blocking | **First** |
| [P1.md](./P1.md) | Hardening, security, correctness, resource safety | High | After P0 |
| [P2.md](./P2.md) | Performance, refactoring, test coverage, maintainability | Medium | After P0/P1 |

## How to Use These Plans

1. Start with **P0** items — they are prerequisites for safe operation.
2. Each file contains:
   - Concrete numbered tasks (P0-01, P1-03, etc.)
   - Impact, affected files, suggested approach, and acceptance criteria
   - Effort estimates
   - Definition of Done for the whole milestone
3. Many tasks are designed to be small enough for focused PRs or subagent implementation sessions.

## Status Tracking (suggested)

You may add a simple checkbox table here or in each file as work progresses:

- [ ] P0-01 completed
- [ ] P0-02 completed
- ...

## Related

- Full original code review (in conversation history)
- `Makefile` (contains `test`, `test-race`, etc.)
- `.gitea/workflows/` (current CI)

---

**Ready for execution.** Pick any item from P0 and go.