maniator / maniator/verticopolis
[P3] The vc-conflict-* stash has no player-facing surface or lifecycle
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
From the D4 adversarial review (PR #750). Hydration''s both-moved conflict stashes the losing local copy to vc-conflict-<id> and the boot bulletin promises "the local copy was set aside in case you need it", but no UI, export path, or recovery flow can reach it; only DevTools can. Stashes also accumulate against the same ~5MB quota the saves need (up to 6 x ~120KB), and a stale stash survives its slot''s deletion.
Wanted: a way to surface/export a stashed copy from the saves UI, plus a lifecycle (replace-on-new-conflict exists; add cleanup when the player dismisses or recovers it).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start from the saves UI and the hydration flow that creates the vc-conflict- stash; the issue does not name specific files or tests. Trace how DevTools currently reaches the stash and how slot deletion and the ~5MB quota are handled. Done means the saves UI can surface and export the copy, with cleanup when it is dismissed or recovered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100