WordPress containment model: territories, versioned projection, unified renderers

Work Orders G and H: the board now orders places by WordPress's own
containment instead of rendering equal tiles, with projection versioning
so recorded history never reinterprets silently.

- topologyVersion stamped at session.start; v1 sessions render v1
  semantics forever. New module src/trail/topology-version.mjs.
- Timelapse export rebased on the same topology/geometry as the browser
  board — record once, render many is now true of all three projections.
- Territories (Content, Design, Structure, Plugins, Settings, People)
  render as fixed-order background regions; plugin sub-regions group
  plugin-owned places without touching identity; parent relations from
  observed data draw static containment elbows with reparent cross-fades
  (src/wordpress/containment.mjs).
- Cross-visit change runs keep their verb when homogeneous ("2 renames");
  dead leaf places compact to tombstone cards, position stable.
- Camera: full fit at or under a 24-place ceiling; above it the active
  sentence (actor, flow, target) is framed whole and centered, held when
  activity settles; live, replay, and timelapse share the framing logic;
  user camera always wins. Territory filters are viewer-only.
- Contract: docs/topology-language.md gains regions-as-cartography,
  containment guides, and the movement doctrine ("the trail never moves
  a card; the viewer may"); docs/trail-format.md gains the observer-only
  authorship clause and topologyVersion.
- Fixtures: 200 places, 300 edits on one page, reparent + plugin option —
  canonical identity and coordinates preserved throughout.
- Tests: 49 Node, 30 Playwright across desktop and mobile.

Claude-Session: https://claude.ai/code/session_015TeFZdAbbdAUenkxakeGt8

Author: noeltock

PLAN.md

@@ -44,6 +44,14 @@ files: [src/board/**]
   from: post-0.1 QA
 - [x] Refresh observed place names and wrap desktop lanes with a stable layout seed {#board-place-refresh-wrap}
   from: post-0.1 QA
+- [x] Version topology projections and render WordPress territories without changing place identity {#board-topology-v2}
+  from: containment model
+- [x] Draw observed parent relations as static containment guides {#board-containment-guides}
+  from: containment model
+- [x] Collapse repeated change runs, compact dead leaves, and bound large-map flow density {#board-scale-relief}
+  from: containment model
+- [x] Contain the active sentence, retain homogeneous run verbs, and fix territory order {#board-framing-language}
+  from: live QA
 
 ## Replay any session {#replay}
 tech: scrub UI over trail; sparse snapshot index for seeking
@@ -60,6 +68,8 @@ needs: [replay]
 files: [src/timelapse/**]
 - [x] Render a shareable timelapse from any trail {#timelapse-render}
   from: roadmap
+- [x] Render exported frames from the same topology and geometry as the browser board {#timelapse-parity}
+  from: containment model
 
 ## Ship it {#ship}
 tech: npm package "aphelion" (name free as of 2026-08-25), npx-first

docs/topology-language.md

@@ -6,6 +6,8 @@ Binding for every topology surface (live, replay, timelapse). This document defi
 
 Everything on the canvas is exactly one of these. Nothing is ever two of them.
 
+Regions are cartography: labeled background territory, never a noun, card, or interactive target. The three-nouns rule governs spatial identity; regions and guides carry none.
+
 **A place** is somewhere on the site where state lives and where changes land: the site itself, a page or post, a setting, a plugin's domain, a menu, a term, a user, an ability. Places are the *nodes* — the only things with a position on the map.
 
 - Litmus test: *could you go there tomorrow, when nothing is happening, and it would still exist?* Page 464 passes. The site tagline passes. "A QA journey," "a WP-CLI run," "a session," "agent work" all fail — they are time, not territory.
@@ -53,6 +55,10 @@ Hard rules:
 
 ## 4. The change contract
 
+### Containment guides
+
+Containment guides are thin, quiet, static elbows for genuine parent/child relations recorded by the observer. They are structure, not flows: they never carry activity, never animate because trail time advanced, and never duplicate territory enclosure. An observed reparent event cross-fades the old guide into the new one while the child card keeps its canonical position.
+
 Where change text lives, by surface:
 
 - **On the card**: the change tail (§2, rows 4–5).
@@ -69,6 +75,8 @@ At any playhead moment the viewer should be able to say what is happening in one
 
 One moment, one focus: at most one flow is in the "in flight or landing" state per playhead instant (the trail is ordered; simultaneity is resolved by seq). Everything else on the canvas is memory — dimmer, still, and stable. A first-touch claim casts a provisional outline of the place at step 1 — visible, dim, marked awaiting. Confirmation at step 2 solidifies it in place. An outline whose session ends without confirmation persists, grey and marked unconfirmed; it is never silently removed. Existing places never move because time advanced.
 
+The trail never moves a card; the viewer may.
+
 ## 6. The three-questions test
 
 Every visual layer answers exactly one question, and each question is answered by exactly one layer:
@@ -81,6 +89,8 @@ Every visual layer answers exactly one question, and each question is answered b
 
 If a proposed element answers two questions at once, split it. If it answers none, delete it.
 
+The trail never moves a card; the viewer may. Canonical coordinates belong to the projection; pan, zoom, filter, collapse, and expand belong to viewer state.
+
 ## 7. Applied: correcting the 10:56 board (historical)
 
 *This section corrected the pre-contract board and is kept as the worked example that motivated the rules; the shipped board implements the contract above.*

docs/trail-format.md

@@ -33,7 +33,7 @@ One JSON object per line (JSONL), UTF-8, flushed per write:
 | `data` | Kind-specific payload. Unknown fields must be preserved by readers. |
 | `prev` | Optional SHA-256 link to the previous serialized event. Absent in the plain-default mode. |
 
-First event of every file is `kind: "session.start"` with `data` carrying target (repo path or site URL), agent identity if known, Aphelion version, and hostname. Sessions end with `session.end` when observed; readers must tolerate its absence (crashes happen).
+First event of every file is `kind: "session.start"` with `data` carrying target (repo path or site URL), agent identity if known, Aphelion version, `topologyVersion`, and hostname. `topologyVersion` selects the recorded projection contract: missing or `1` remains v1 forever; sessions recorded for the containment model use `2`. Replay never upgrades a historical session from currently installed site state. Sessions end with `session.end` when observed; readers must tolerate its absence (crashes happen).
 
 ## Rules