GET/POST /game/players/{id}/perk-state with versioned JSON, engine-backed
branch selection, PerkStateApiTests, Bruno collection, README, and E2.M3 alignment.
|
||
|---|---|---|
| .. | ||
| E1M3-prototype-backlog.md | ||
| E1M4-prototype-backlog.md | ||
| E2M3-pre-production-backlog.md | ||
| NEO-5-implementation-plan.md | ||
| NEO-6-implementation-plan.md | ||
| NEO-7-implementation-plan.md | ||
| NEO-8-implementation-plan.md | ||
| NEO-9-implementation-plan.md | ||
| NEO-10-implementation-plan.md | ||
| NEO-11-implementation-plan.md | ||
| NEO-12-implementation-plan.md | ||
| NEO-13-implementation-plan.md | ||
| NEO-14-implementation-plan.md | ||
| NEO-15-implementation-plan.md | ||
| NEO-16-implementation-plan.md | ||
| NEO-17-implementation-plan.md | ||
| NEO-18-implementation-plan.md | ||
| NEO-19-implementation-plan.md | ||
| NEO-20-implementation-plan.md | ||
| NEO-22-implementation-plan.md | ||
| NEO-23-implementation-plan.md | ||
| NEO-24-implementation-plan.md | ||
| NEO-25-implementation-plan.md | ||
| NEO-26-implementation-plan.md | ||
| NEO-27-implementation-plan.md | ||
| NEO-28-implementation-plan.md | ||
| NEO-29-implementation-plan.md | ||
| NEO-30-implementation-plan.md | ||
| NEO-31-implementation-plan.md | ||
| NEO-32-implementation-plan.md | ||
| NEO-33-implementation-plan.md | ||
| NEO-34-implementation-plan.md | ||
| NEO-35-implementation-plan.md | ||
| NEO-36-implementation-plan.md | ||
| NEO-37-implementation-plan.md | ||
| NEO-38-implementation-plan.md | ||
| NEO-39-implementation-plan.md | ||
| NEO-40-implementation-plan.md | ||
| NEO-41-implementation-plan.md | ||
| NEO-42-implementation-plan.md | ||
| NEO-43-implementation-plan.md | ||
| NEO-45-implementation-plan.md | ||
| NEO-46-implementation-plan.md | ||
| NEO-47-implementation-plan.md | ||
| NEO-48-implementation-plan.md | ||
| NEO-49-implementation-plan.md | ||
| NEON-29-implementation-plan.md | ||
| README.md | ||
| internal-content-authoring.md | ||
README.md
Implementation plans (docs/plans/)
Story-level implementation plans live here, keyed by Linear issue id (NEO-*) when the work is tracked in Linear (team NEO, Neon Sprawl).
Legacy NEON-* filenames
A small number of files keep the historical Jira / Atlassian NEON-* key in the filename only. They are not the active issue tracker for new work.
- Each such file includes a short Historical banner at the top pointing at the matching
NEO-*plan (same scope) where kickoff and commits should align. - Prefer opening and linking
NEO-*issues and plans for new contributors.
GitHub links in Linear (and docs)
The canonical public repo path is ViPro-Technologies/neon-sprawl (see git remote). Use that org in raw GitHub markdown links (https://github.com/ViPro-Technologies/neon-sprawl/blob/main/...). The path neon-sprawl/neon-sprawl is not the live repo and will 404.
Conventions
- New or moved plans:
docs/plans/{LINEAR_KEY}-implementation-plan.md(see story kickoff). - Cross-links from decomposition and game-design docs should use
NEO-*URLs (Linear) for current engineering work.