Decouple AGENTS.md from specific tracks: keep only process, action and tracking guidance

AGENTS.md

@@ -28,8 +28,7 @@ The project should be developed in small, reviewable steps. Agents must keep pla
 
 `TODO.md` is the priority source. The active order is:
 
-1. unversioned development tracks (currently 3D model and local map re-evaluation, and
-   character development);
+1. unversioned development tracks;
 2. versioned release milestones, in version order;
 3. future/unversioned candidates and deferred work.
 
@@ -74,9 +73,6 @@ specialists the task needs:
 | Style direction (stylized / low-poly / realistic) | `stylized-style`, `lowpoly-style`, `realistic-style` |
 | Ship/no-ship review | `qa-review` |
 
-The same skills cover the local map track (procedural geometry, facade kits, OSM massing,
-splat reference renders) and the NPC roster work.
-
 ### Project rules that override a skill
 
 1. **The project contract wins.** `npc_base` mesh node, the 13 contract bones at their rest
@@ -124,8 +120,8 @@ All planned implementation work must be represented in `TODO.md`.
 - Order level-2 sections by current priority: unversioned development tracks first, then
   versioned release milestones in version order, then future/deferred work. Do not assign a
   version number to an unversioned track until it is scheduled for a release.
-- Use level-3 headings (`###`) for workstreams inside a milestone (for example, `0.8.1
-  First-shift tutorial`). Keep the hierarchy to three levels: milestone → workstream → checkbox.
+- Use level-3 headings (`###`) for workstreams inside a milestone. Keep the hierarchy to three
+  levels: milestone → workstream → checkbox.
 - Use checkbox items for each concrete task, normally under a level-3 workstream. Direct
   checkboxes under a level-2 section are acceptable for small, single-workstream sections.
 - Keep tasks small enough to complete and review independently.
@@ -144,32 +140,30 @@ Recommended format:
 ```md
 # TODO
 
-## Milestone 0.8.0 — First hour and content depth
+## Milestone X.Y.Z — goal and exit criterion
 
-### 0.8.1 First-shift tutorial
+### Workstream A
 
-- [x] Write the tutorial beat sheet.
-- [-] Implement the tutorial state machine. (claimed; implementation/verification in progress)
-- [ ] Add the tutorial smoke test.
+- [x] Completed task.
+- [-] Task in progress. (claimed; implementation/verification in progress)
+- [ ] Open task.
 
-### 0.8.2 Campaign shell
+### Workstream B
 
-- [ ] Define campaign data.
-- [ ] Persist campaign progress.
+- [ ] Another task.
 
-**Exit:** a first-time player completes a shift without external documentation.
+**Exit:** a verifiable statement of what "done" means for the milestone.
 
-## Documentation
+## Theme
 
-- [ ] Document the test procedure in `README.md`.
+- [ ] A small housekeeping task with no milestone.
 ```
 
 Recommended `DONE.md` format: a `# DONE` heading, followed by each moved level-2 section
 unchanged, with a completion date line under each section heading.
 
 Order the actual file as described in "Priority and Versioning": unversioned development tracks
-first (for example character and local-map development), then versioned milestones in version
-order, then future/deferred work.
+first, then versioned milestones in version order, then future/deferred work.
 
 ### 3. Move Completed Sections to `DONE.md`
 
@@ -305,8 +299,8 @@ Avoid unrelated refactors unless they are required for the task or explicitly ap
   below; a changelog entry alone is not a release.
 - **CI is a second gate, not a substitute.** Tag builds remain automated, but the local build is
   the required pre-tag check for every version.
-- **Unversioned tracks stay unversioned.** Character, map and other development tracks do not get
-  a placeholder version; the version is assigned when the work is scoped into a release.
+- **Unversioned tracks stay unversioned.** A development track does not get a placeholder
+  version; the version is assigned when the work is scoped into a release.
 
 **Release Procedure** — follow these steps in order for every major, minor, or patch version
 increment: