chore(meta): plan Sprint 24: Signal
10 tickets across server (6), client (3), copy (1). Capstone sprint for v0.1 — everything converges on a full playthrough from main menu through storyteller activation. Closed stale epics: #38, #369, #455, #575, #596. Sprint goal: wire TriangleActivated into player-visible signal, thread character archetype through session lifecycle. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Claude Opus 4.6
Binary file not shown.
@@ -0,0 +1,149 @@
|
||||
# Sprint 24: Signal — Client Tasks
|
||||
|
||||
**Goal:** Wire the storyteller's activation event into player-visible consequences, thread character archetype through the full session lifecycle, and deliver the first unscripted end-to-end v0.1 playthrough — from main menu to triangle activation.
|
||||
|
||||
**Branch:** `client`
|
||||
**Agents:** Stig (UI/rendering), Hoshe (QA)
|
||||
|
||||
> **This is the capstone sprint for v0.1.** Client work this sprint wires the player-facing signal
|
||||
> that makes the simulation legible as a story: the character select screen, the triangle
|
||||
> activation response, and the news ticker. All three must land before #593 (playthrough proof)
|
||||
> can be filed as done. Sprint 25 is playtest. There is no Sprint 26 before v0.1 ships.
|
||||
|
||||
---
|
||||
|
||||
## New Tickets
|
||||
|
||||
| # | Title | Blocked by |
|
||||
|---|-------|------------|
|
||||
| #588 | Character archetype selection — client: character select screen before session start | #587 (server: archetype in StartupMessage) |
|
||||
| #590 | Triangle activation consumer — client: react to triangle_crisis_events (monologue chime + urgent overlay) | #589 (server: tell escalation emitted) |
|
||||
| #592 | News ticker — client: scrolling ticker HUD element in The Last Shift zone | #591 (server: ticker in snapshot) |
|
||||
|
||||
Use `tooling/db/ticket show <id>` for full details.
|
||||
|
||||
---
|
||||
|
||||
## Key Decisions
|
||||
|
||||
- `decisions/scope.md` — D-027 (vertical slice success criteria — the 4 tests this sprint's work must satisfy), D-039 (wow moments — #1 Arrival: opening monologue; #5 News Ticker Gut-Punch: same ticker, opposite monologue reactions)
|
||||
- `decisions/architecture.md` — D-020 (ObserverSnapshot is the only data crossing IPC; StartupMessage is the client→server init message; PROTOCOL_VERSION gates wire compatibility), D-042 (UI microcopy in `client/data/ui-strings.yaml` via UIStrings autoload)
|
||||
- `decisions/content.md` — D-032 (separate monologue pools per character — client does not select the pool; the character string in StartupMessage drives server-side selection), D-074 (audio aesthetic — monologue chime = insert-tech: synthetic, precise, no reverb)
|
||||
- `decisions/perception.md` — D-067 (recognition chime fires at onset of cognitive delay — `sfx_monologue_chime_urgent.ogg` is the correct asset for triangle activation), D-016 (internal monologue as perception bridge — client only displays what server sends; no client-side monologue logic)
|
||||
|
||||
---
|
||||
|
||||
## Notes
|
||||
|
||||
### #588 — Character archetype select screen
|
||||
|
||||
**What exists:** `client/ui/main_menu.gd` (130 lines) — "New Game" button triggers `SessionManager.new_game()` which creates a save directory and seeds `GameState.world_seed`. It then loads `GAME_SCENE` directly, with no character selection step. `client/scripts/autoloads/session_manager.gd` — `new_game()` returns a `game_id` but does not record which archetype was chosen. `client/scripts/autoloads/game_state.gd` — check whether a `character_archetype` field already exists (likely not — add it). `CharacterArchetype` is a server-side enum; the client needs to record the chosen value as a string (`"smuggler"` or `"detective"`) and include it in `StartupMessage` sent over IPC.
|
||||
|
||||
**What to deliver:**
|
||||
|
||||
1. `GameState.character_archetype: String` — new field, default `"detective"`. Persisted alongside `world_seed` in the save directory (`user://saves/<game-id>/character.txt` or extend the existing seed file format).
|
||||
|
||||
2. Character select scene — insert a step between "New Game" and loading `main.tscn`. This can be a new scene (`client/scenes/character_select.tscn`) or a modal panel within `main_menu.tscn`. Show two options: **Smuggler** and **Detective**. Each option shows the character name, a one-line role description, and a two-line tone description (see below). On selection, set `GameState.character_archetype`, then proceed to `main.tscn`.
|
||||
|
||||
**Smuggler card:**
|
||||
- Name: `Smuggler`
|
||||
- Role: `Freight logistics worker — Sova Transit`
|
||||
- Tone: `Insider access. Social camouflage. The ring is your daily life.`
|
||||
|
||||
**Detective card:**
|
||||
- Name: `Detective`
|
||||
- Role: `Commission investigator — External assignment`
|
||||
- Tone: `Institutional authority. Analytical lattice. You were sent here.`
|
||||
|
||||
These strings belong in `client/data/ui-strings.yaml` (D-042), not hardcoded in GDScript.
|
||||
|
||||
3. `Protocol.encode_startup_message()` update — add `character_archetype` to the StartupMessage dict before it is serialized. The server's `StartupMessage` struct now has `pub character_archetype: CharacterArchetype` (#587). Map client string `"smuggler"` → server enum variant `Smuggler`. In MessagePack/GDScript, this is just a string field added to the dict: `{ "world_seed": ..., "character_archetype": "Smuggler" }`.
|
||||
|
||||
4. `Protocol.PROTOCOL_VERSION = 19` — bump to match server #587. The client must send the new version on handshake. This is a **hard coordination point** with Dudley — client and server PRs must land together or in the same merge window. A version mismatch will crash the connection on the handshake check.
|
||||
|
||||
**UI constraints:** The character select screen must feel intentional, not an afterthought. Two full-width cards, dark background, character name in the sprint's color palette (consistent with main menu). No portraits (art is deferred). Cards are selectable via keyboard (left/right arrows) and mouse click. The selection is confirmed with Enter or a "Begin" button. ESC cancels back to the main menu without creating a save directory.
|
||||
|
||||
**Non-obvious gotcha:** `SessionManager.new_game()` currently creates the save directory before any game scene loads. The character select step happens after `new_game()` creates the directory but before the game scene loads. `GameState.character_archetype` must be set before `SimBridge` sends the `StartupMessage` — which happens when `main.tscn` is ready and `SimBridge._ready()` connects to the server. Verify the ordering: `new_game()` → character select panel → user picks archetype → `GameState.character_archetype` set → `main.tscn` loads → `SimBridge._ready()` fires → `StartupMessage` includes archetype.
|
||||
|
||||
**Blocked by:** #587 (server must define `character_archetype` field in `StartupMessage` before client serialization is finalized).
|
||||
|
||||
---
|
||||
|
||||
### #590 — Triangle activation consumer
|
||||
|
||||
**What exists:** `client/scripts/snapshot_event_router.gd` — routes snapshot fields to registered handlers. `client/scripts/main.gd` — registers handlers on `_router`. `client/scripts/autoloads/sim_bridge.gd` — `_on_snapshot_received()` decodes and emits snapshot. `client/scripts/protocol/protocol.gd` — `decode_snapshot()` returns a dict from the MessagePack bytes. The server snapshot wire type (`ObserverSnapshotWire`) has a `triangle_crisis_events: Vec<TriangleCrisisEventWire>` field (see `server/src/bridge/types.rs` line ~181). This field is present in the MessagePack output. **The client currently ignores it entirely** — there is no decode path for `triangle_crisis_events` in `protocol.gd` and no handler registered in `main.gd`.
|
||||
|
||||
**What to deliver:**
|
||||
|
||||
1. **Decode `triangle_crisis_events`** in `protocol.gd` `decode_snapshot()`. The field is an array of dicts, each with at minimum `{ "triangle_id": int }`. Add it to the returned snapshot dict as `"triangle_crisis_events": Array`.
|
||||
|
||||
2. **Handle activation in `main.gd`** — register a handler that reads `triangle_crisis_events` from the snapshot. When the array is non-empty (at least one event), fire the urgent monologue chime: `AudioManager.play_one_shot(AudioManager.CHIME_RECOGNITION, AudioManager.BUS_UI_SOUNDS)` — wait, check the constant name. The correct asset is `sfx_monologue_chime_urgent.ogg` (D-038, D-067 "sharper variant for contradiction/anomaly"). `AudioManager` has `const CHIME_RECOGNITION := "sfx_monologue_chime"` — add `const CHIME_ACTIVATION := "sfx_monologue_chime_urgent"` if it doesn't exist, then call `AudioManager.play_one_shot(CHIME_ACTIVATION, BUS_UI_SOUNDS)`.
|
||||
|
||||
3. **Deduplication** — the triangle activation is a one-shot event (v0.1 fires once per session per D-072/D-089). The client must not fire the chime on every subsequent tick that includes the event in the array. Track activated triangle IDs in a local `Set` in `main.gd`. If `triangle_id` is already in the set, skip. Add to set on first encounter.
|
||||
|
||||
4. **No overlay UI** — the monologue chime is the client-side signal. The copy team (#597) authors the proximity monologue lines that fire when the player observes the activated NPC's `tell_state: RoutineDeviation`. The client does not need to render a special overlay or notification — the tell state on the entity and the subsequent proximity monologue are the visible consequence. Keep client reaction to: chime + deduplication tracking only.
|
||||
|
||||
**Why no overlay:** D-039 wow moment #2 ("The Character's Eye") is about the monologue noticing something the player didn't. Adding a UI overlay would make it a notification, not a character observation. The feel is: you're wandering near Kael, suddenly you hear the chime — then the next monologue line is your character's internal voice noticing something is off. The server sends the `tell_state: RoutineDeviation` on the NPC entity; the client's entity renderer already renders this as visible entity data that can trigger `observe_npc` monologue.
|
||||
|
||||
**Blocked by:** #589 (server must send non-empty `triangle_crisis_events` for client to handle).
|
||||
|
||||
---
|
||||
|
||||
### #592 — News ticker HUD
|
||||
|
||||
**What exists:** `client/ui/hud.gd` and `hud.tscn` — main HUD container. `client/ui/time_display.gd` — insert-style time display already wired via `_router.register_always(time_display.update_from_state)` in `main.gd`. No ticker node or script exists. Server snapshot will carry `current_ticker: Optional<{ id, text, category }>` when player is in the bar zone (#591).
|
||||
|
||||
**What to deliver:**
|
||||
|
||||
1. `client/ui/news_ticker.gd` + `news_ticker.tscn` — a horizontal scrolling text bar. Design: narrow strip (24–32px tall), anchored top of screen or bottom above the dialogue box, full width. Background: dark semi-transparent (`Color(0.05, 0.05, 0.07, 0.75)`). Text: scrolls left at a constant rate (~60px/sec). Text content: the `text` field from `current_ticker`. When `current_ticker` is `null` (player is not in bar zone), the ticker hides itself (`visible = false`).
|
||||
|
||||
2. Wire in `main.gd` — add `@onready var news_ticker = $UILayer/NewsTicker` and register: `_router.register_always(news_ticker.update_from_state)`. Implement `news_ticker.update_from_state(snapshot: Dictionary)`: read `snapshot.get("current_ticker")`, update text if changed, show/hide based on null.
|
||||
|
||||
3. **Insert overlay compatibility** — the ticker lives on `UILayer` (z-layer 7 per D-049). When the insert overlay is open (`GameState.insert_active = true`), the ticker should NOT be hidden — the news terminal is a real-world object the player can see while their insert is open. Do not call `set_insert_active` on the ticker.
|
||||
|
||||
4. **Scrolling behavior** — the headline scrolls in from the right and exits left. When it exits, it restarts from the right with the same text (the server rotates the headline every 200 ticks; client just loops whatever it currently has). No crossfade, no fade-in. Pure marquee.
|
||||
|
||||
**UI location:** Confirm with the sprint visual check that the ticker does not occlude the time display (top-right insert) or the monologue display (top-center). If there is a conflict, anchor the ticker at the bottom-center above the dialogue box, 4px margin above.
|
||||
|
||||
**Blocked by:** #591 (server must send `current_ticker` field in snapshot before client has real data to render; before that, the ticker renders nothing and stays hidden).
|
||||
|
||||
---
|
||||
|
||||
## Dependency Chain
|
||||
|
||||
```
|
||||
#587 (server: archetype in StartupMessage)
|
||||
└→ #588 (character select screen) ← start after #587 is merged
|
||||
└→ PROTOCOL_VERSION 17→19 bump (coordinate with server)
|
||||
|
||||
#589 (server: tell escalation)
|
||||
└→ #590 (triangle activation consumer) ← start after #589 is merged
|
||||
|
||||
#591 (server: ticker in snapshot)
|
||||
└→ #592 (news ticker HUD) ← start after #591 is merged
|
||||
|
||||
#588 + #590 + #592 → #593 (playthrough proof — server ticket)
|
||||
```
|
||||
|
||||
All three client tickets are blocked on their respective server tickets. Start with `protocol.gd` decode additions speculatively (no server data yet — verify against `server/src/bridge/types.rs` for field names), then wire the handlers once server branches are merged to main.
|
||||
|
||||
---
|
||||
|
||||
## PR Workflow
|
||||
|
||||
```bash
|
||||
tea pr create --repo jpmschweitzer/settled-reach --login schweitz \
|
||||
--title "feat(client): character archetype select screen" \
|
||||
--description "body" --base main --head client
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Sprint Completion (Client Criteria)
|
||||
|
||||
1. From main menu, "New Game" → character select screen appears. Both cards render. Keyboard and mouse selection work. ESC cancels without creating a save directory.
|
||||
2. Selected archetype is persisted in `GameState.character_archetype` and sent in `StartupMessage`. Server receives correct archetype (verify via debug console `status` — it should report the active archetype if Dudley adds it to the status response).
|
||||
3. `PROTOCOL_VERSION = 19` — client matches server. Connection handshake succeeds.
|
||||
4. When `triangle_crisis_events` is non-empty in snapshot, `sfx_monologue_chime_urgent.ogg` fires once. Does not re-fire on subsequent ticks.
|
||||
5. News ticker visible and scrolling in The Last Shift zone. Hidden in all other zones. Text matches the server-sent headline.
|
||||
6. `make test-client` green on client branch. No regressions in existing test suite.
|
||||
@@ -0,0 +1,147 @@
|
||||
# Sprint 24: Signal — Copy Tasks
|
||||
|
||||
**Goal:** Wire the storyteller's activation event into player-visible consequences, thread character archetype through the full session lifecycle, and deliver the first unscripted end-to-end v0.1 playthrough — from main menu to triangle activation.
|
||||
|
||||
**Branch:** `copy`
|
||||
**Agents:** Mellanie (dialogue), Paula (narrative), Gestalt (systems)
|
||||
|
||||
> **This is the capstone sprint for v0.1.** The lines authored here are the player's first
|
||||
> experience of the storyteller doing its job. When the triangle activates and Kael's behavior
|
||||
> shifts, the character's internal voice is the signal. These lines carry D-039 wow moment #2
|
||||
> ("The Character's Eye") — the moment the monologue notices something the player didn't.
|
||||
> Sprint 25 is playtest. Get these lines right.
|
||||
|
||||
---
|
||||
|
||||
## New Tickets
|
||||
|
||||
| # | Title | Blocked by |
|
||||
|---|-------|------------|
|
||||
| #597 | Triangle activation — copy: author 3–5 proximity monologue lines for TriangleActivated (per archetype) | — |
|
||||
|
||||
Use `tooling/db/ticket show <id>` for full details.
|
||||
|
||||
---
|
||||
|
||||
## Key Decisions
|
||||
|
||||
- `decisions/scope.md` — D-039 (wow moment #2: "The Character's Eye" — monologue flags something the player didn't notice; urgent chime fires), D-027 (vertical slice criterion: the observe→notice→follow→discover sequence must emerge from systems, not scripts)
|
||||
- `decisions/content.md` — D-032 (separate monologue pools per character — no shared lines between smuggler and detective), D-035 (tag taxonomy: `trigger: observe_npc`, `situation: [triangle_activated]`, `character`, `prerequisite` fields required), D-090 (PC voice registers — smuggler: contracted, street-cadenced, risk-calculating; detective: analytical, institutional, uncontracted)
|
||||
- `decisions/content.md` — D-016 (monologue functions: perception bridge, atmosphere, diegetic hint, unreliable narrator — these lines are observation, not exposition), D-034 (THE FRIEND: Kael Davan is smuggler's FRIEND; Sera Venn is detective's FRIEND — these are the primary triangle anchor NPCs)
|
||||
- `decisions/content.md` — D-024 (tell system — `RoutineDeviation` tell fires when NPC is off schedule; these lines should feel like the character noticing the deviation, not naming the conspiracy)
|
||||
|
||||
---
|
||||
|
||||
## Open Questions to Resolve Early
|
||||
|
||||
None blocking this ticket. The tag schema is fully specified (D-035). The character voice registers are documented (D-090). The NPC identities are confirmed (D-034). Author without waiting for server/client tickets to land — the content files are independent of the implementation.
|
||||
|
||||
---
|
||||
|
||||
## Notes
|
||||
|
||||
### #597 — Triangle activation proximity monologue lines
|
||||
|
||||
**What exists:** The monologue pool system (`server/src/simulation/monologue.rs`) selects lines by `trigger`, `character`, `situation`, and `prerequisite`. The `observe_npc` trigger fires when the player is proximate to a specific NPC and has LOS to them. `RoutineDeviation` tell state is the server signal that a triangle anchor NPC is activated. The system can gate monologue lines on situation tags that correspond to game state — `triangle_activated` is a valid situation tag that the server can emit when `TriangleActivatedQueue` is non-empty.
|
||||
|
||||
**What to deliver:** 3–5 monologue lines per character (smuggler and detective), placed in the correct pool files.
|
||||
|
||||
**File locations:**
|
||||
- Smuggler: `content/campaigns/main/systems/krenn/stations/sova/districts/transit/monologue/smuggler/the-terminal.yaml`
|
||||
- Detective: `content/campaigns/main/systems/krenn/stations/sova/districts/transit/monologue/detective/the-terminal.yaml`
|
||||
|
||||
(Kael and Torek are Terminal NPCs. Sera is also a Terminal presence. These lines fire when the player observes those NPCs post-activation while at The Terminal or maintenance corridors.)
|
||||
|
||||
**Tag specification (D-035 required fields):**
|
||||
|
||||
```yaml
|
||||
- id: pc-smuggler_m_s_NNN # NNN = next available index in the smuggler pool
|
||||
text: "..."
|
||||
role: player_character
|
||||
access: [public]
|
||||
trust: surface
|
||||
situation: [triangle_activated]
|
||||
trigger: observe_npc
|
||||
mood: [suspicious] # or [anxious] depending on line content
|
||||
priority: 8 # higher than ambient lines; lower than opening hook (10)
|
||||
cooldown: 9999 # fires once per activation per session
|
||||
tags: [triangle-signal, tell-observation]
|
||||
prerequisite:
|
||||
npc_in_los: true # only fires when actively observing an NPC
|
||||
```
|
||||
|
||||
**Smuggler lines — Kael Davan (triangle anchor: T1 hub-power)**
|
||||
|
||||
The smuggler knows Kael. Kael is a colleague, possibly a friend. The lines must feel like noticing something personal about a familiar person, not flagging a conspiracy suspect. The smuggler's register (D-090): contracted, casual, risk-reading.
|
||||
|
||||
Three beats to cover in 3–5 lines (one line per beat, no doubling):
|
||||
1. Physical observation — Kael's behavior is off in a specific, observable way (posture, timing, direction).
|
||||
2. Internal rationalization — the smuggler finds a mundane explanation first. This is deniable.
|
||||
3. Doubt — the rationalization doesn't quite hold. The smuggler can't name what's wrong. The reader can.
|
||||
|
||||
Example tone (do not use as final lines — author fresh):
|
||||
- Beat 1: "Kael's on the main corridor. He doesn't usually work this route." (Too on-the-nose; soften)
|
||||
- Beat 2: "Could just be a schedule swap. Voss does that sometimes."
|
||||
- Beat 3: "...but Kael doesn't swap shifts."
|
||||
|
||||
These are tone illustrations, not copy. Paula and Mellanie should author the actual lines.
|
||||
|
||||
**Detective lines — Sera Venn and Torek Lintar (triangle anchor: T2 informant-question)**
|
||||
|
||||
The detective is external — these are analytical observations about NPCs whose behavior creates a logical anomaly in the investigation pattern. Detective register (D-090): uncontracted, institutional framing, evidence-cataloguing internal voice.
|
||||
|
||||
Three beats:
|
||||
1. Pattern recognition — the detective logs a behavioral deviation as data.
|
||||
2. Hypothesis formation — what does this deviation imply? (stated as a question, not a conclusion)
|
||||
3. Procedural next step — the detective's internal instinct is to act, not just observe.
|
||||
|
||||
Example tone:
|
||||
- Beat 1: "Sera avoided eye contact with Torek again. Third occurrence in four observations."
|
||||
- Beat 2: "If she knows something about his manifest discrepancy, why the silence?"
|
||||
- Beat 3: "Worth a conversation. But not here."
|
||||
|
||||
**What these lines must NOT do:**
|
||||
- Name the conspiracy directly ("Kael is in the ring" / "Torek is covering evidence")
|
||||
- Be omniscient — the character observes behavior, not motive
|
||||
- Be too long — 1–2 sentences maximum per line; monologue is a flash of interiority
|
||||
- Repeat vocabulary across lines — each line should use different sensory or cognitive entry
|
||||
|
||||
**Verification:** Run the line previewer CLI to confirm schema compliance before committing:
|
||||
```bash
|
||||
tooling/db/sqlite-query 'SELECT * FROM ...' # check via line previewer if available
|
||||
# Or: server/target/debug/line-previewer path/to/the-terminal.yaml
|
||||
```
|
||||
|
||||
Confirm with `make validate-content` that the YAML parses without errors.
|
||||
|
||||
---
|
||||
|
||||
## Dependency Chain
|
||||
|
||||
```
|
||||
#597 (proximity monologue lines) — no blockers, author immediately
|
||||
|
||||
#597 → #593 (playthrough proof — must land before sprint is closed)
|
||||
```
|
||||
|
||||
Start authoring #597 immediately. It is unblocked. The lines need to be in the content files before the playthrough proof (#593) can be run.
|
||||
|
||||
---
|
||||
|
||||
## PR Workflow
|
||||
|
||||
```bash
|
||||
tea pr create --repo jpmschweitzer/settled-reach --login schweitz \
|
||||
--title "feat(copy): triangle activation proximity monologue lines" \
|
||||
--description "body" --base main --head copy
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Sprint Completion (Copy Criteria)
|
||||
|
||||
1. 3–5 smuggler monologue lines in `monologue/smuggler/the-terminal.yaml` with `situation: [triangle_activated]`, correct tag schema (D-035), `cooldown: 9999`, `trigger: observe_npc`.
|
||||
2. 3–5 detective monologue lines in `monologue/detective/the-terminal.yaml` with the same schema.
|
||||
3. `make validate-content` passes — YAML parses, required fields present, no FactId typos.
|
||||
4. Voice consistency: smuggler lines are contracted, risk-reading; detective lines are analytical, institutional. Paula reviews before PR.
|
||||
5. Lines do not name the conspiracy — they observe behavior and feel personal to the character.
|
||||
@@ -0,0 +1,120 @@
|
||||
# Sprint 24: Signal — Joint / Integration
|
||||
|
||||
**Goal:** Wire the storyteller's activation event into player-visible consequences, thread character archetype through the full session lifecycle, and deliver the first unscripted end-to-end v0.1 playthrough — from main menu to triangle activation.
|
||||
|
||||
**Agents:** All implementation agents (Dudley, Tyre, Hoshe, Stig, Mellanie, Paula, Gestalt)
|
||||
|
||||
> **This is the capstone sprint for v0.1.** Sprint 23 built the world. Sprint 24 makes it
|
||||
> legible as a story. Sprint 25 is playtest. Every ticket in this sprint feeds into a single
|
||||
> proof: a real human can boot the game, pick a character, play for 30 minutes, and experience
|
||||
> the storyteller doing its job — without scripted interventions or debug shortcuts.
|
||||
|
||||
---
|
||||
|
||||
## Pre-Sprint Actions
|
||||
|
||||
These must happen at sprint start, before implementation tickets begin:
|
||||
|
||||
| Action | Owner | Blocks |
|
||||
|--------|-------|--------|
|
||||
| Confirm `StartupMessage` wire format with `character_archetype` field | Dudley + Stig sync (day 1) | #588 — client serialization cannot be finalized until server field is published in `bridge/types.rs` |
|
||||
| Confirm PROTOCOL_VERSION bump: 18 → 19 | Dudley + Stig | #587 server + #588 client must land together — version mismatch crashes handshake |
|
||||
| Confirm `triangle_crisis_events` decode path for `TriangleCrisisEventWire` field names | Dudley + Stig sync (day 1) | #590 — client `protocol.gd` decode speculates from `bridge/types.rs`; confirm field names before merging |
|
||||
| Confirm `current_ticker` snapshot field structure (`id`, `text`, `category`) | Dudley + Stig sync (day 1) | #592 — client ticker decode needs field names from server `bridge/types.rs` |
|
||||
|
||||
---
|
||||
|
||||
## Cross-Team Dependencies
|
||||
|
||||
| Dependency | Direction | Notes |
|
||||
|------------|-----------|-------|
|
||||
| `character_archetype` in StartupMessage | Server (#587) → Client (#588) | Client cannot send archetype until server defines the field. Stig reads `bridge/types.rs` for the field name before finalizing `Protocol.encode_startup_message()`. |
|
||||
| PROTOCOL_VERSION 18 → 19 | Server (#587) ↔ Client (#588) | Both must land in the same merge window. A mismatch crashes the handshake. |
|
||||
| `RoutineDeviation` tell in snapshot | Server (#589) → Client (#590) | Client registers `triangle_crisis_events` handler; server populates it after tell escalation is wired. |
|
||||
| `current_ticker` in snapshot | Server (#591) → Client (#592) | Client ticker hides when field is absent (null). Client can be merged before server; it simply renders nothing until server sends data. |
|
||||
| Triangle activation monologue lines | Copy (#597) → Server (#593) | Lines must be in YAML files before playthrough proof run. Copy is unblocked — merge first. |
|
||||
| Playthrough proof | All tickets → Server (#593) | #593 is the convergence gate. Cannot be filed done until all upstream tickets are merged and CI is green across all branches. |
|
||||
|
||||
---
|
||||
|
||||
## Housekeeping Done at Sprint Planning
|
||||
|
||||
The following tickets were closed during planning as their work was already complete:
|
||||
|
||||
| # | Reason |
|
||||
|---|--------|
|
||||
| #38 | Client-Server Integration epic — all 11 children done across Sprints 1–22 |
|
||||
| #369 | v0.1 Content Scoping Workshop Outputs — all 39 children done |
|
||||
| #455 | QA Strategy & Test Infrastructure — all 59 children done |
|
||||
| #575 | LOS boundary bug — fixed by #584/#585 in Sprint 23 |
|
||||
| #596 | Opening monologue content — fully authored in Sprint 12 (#299 smuggler, #300 detective) |
|
||||
|
||||
---
|
||||
|
||||
## Sprint Completion Proof
|
||||
|
||||
The sprint is done when **all of the following are observable in a live production session** (no `--gauntlet`, no `SR_TEST=1`, no forced debug shortcuts):
|
||||
|
||||
1. **Character selection works.** From the main menu, click "New Game." A character select screen appears with two cards: Smuggler and Detective. Both keyboard and mouse selection work. ESC cancels without creating a save. Selecting a character proceeds to the game.
|
||||
|
||||
2. **Opening monologue is character-correct.** The first monologue line that fires on session start matches the selected archetype. Smuggler opening: contracted, dock-worker voice, insider framing. Detective opening: analytical, institutional framing, uncontracted. Both fire within the first 5 seconds of game load.
|
||||
|
||||
3. **Storyteller activates naturally.** Play as Smuggler. Walk to The Terminal. Observe Kael for ~3 game-minutes (no teleport, no debug shortcut). Eventually (after ~30 game-minutes real or via debug `contaminate`): the urgent monologue chime fires. The next time you approach Kael, a proximity monologue line fires from the `triangle_activated` situation pool.
|
||||
|
||||
4. **Tell state is observable.** After activation, stand near Kael. The debug console `npc <kael_entity_id>` reports `tell_state: RoutineDeviation`. The entity renderer colors/indicators for Kael reflect the tell (future animation deferred — tell state emitted is sufficient for v0.1).
|
||||
|
||||
5. **News ticker displays in The Last Shift.** Walk to The Last Shift bar. A scrolling text headline is visible in the HUD. Leaving the bar hides it. Returning shows a headline (possibly different, if 200 ticks have elapsed).
|
||||
|
||||
6. **CI green across all branches.** `make ci` passes on `main`, `server`, `client`, `copy` branches. No regressions.
|
||||
|
||||
---
|
||||
|
||||
## Test Plan Alignment (D-030)
|
||||
|
||||
Sprint 24 is Phase 3 territory (D-030 Phase 3: CauseChain verification + divergent snapshots):
|
||||
|
||||
- **#587/#588:** Protocol round-trip test — `StartupMessage { character_archetype: Smuggler }` survives serialize/deserialize. Phase 1 (data structure).
|
||||
- **#589:** Unit test — after `TriangleActivatedQueue` is populated, triangle NPCs have `RoutineDeviation`; `derive_tell_state()` returns `RoutineDeviation`. Phase 1.
|
||||
- **#591:** Unit test — `TickerPool` loads 30 headlines from YAML, rotation advances deterministically with `SimRng`. Phase 1.
|
||||
- **#595:** Integration test — 1-tick simulation with `StartupMessage { character_archetype: Smuggler }` emits opening monologue line from smuggler pool (not detective pool). Phase 2.
|
||||
- **#590:** Client test — mock snapshot with `triangle_crisis_events: [{ triangle_id: 1 }]` triggers `CHIME_ACTIVATION` play call once; second snapshot with same triangle_id does not retrigger. Phase 2.
|
||||
- **#593:** End-to-end integration test — `test_v0_1_integration_playthrough` (server `tests/` directory). Boot server, send Smuggler startup message, advance to contamination via debug command, assert TriangleActivated and RoutineDeviation in golden snapshot. Phase 3.
|
||||
|
||||
---
|
||||
|
||||
## Open Questions
|
||||
|
||||
| ID | Question | Blocks | Action |
|
||||
|----|----------|--------|--------|
|
||||
| Q-052 | Storyteller hint delivery channels | — | Resolved at v0.1 scope this sprint. #589 implements channel 1 (behavioral tell escalation), #597 implements channel 7 (proximity monologue). Channels 2 (environmental change) and 4 (overheard NPC conversation) deferred to v0.2. File resolution note in `decisions/questions-content.md` after sprint. |
|
||||
|
||||
---
|
||||
|
||||
## PR Merge Order
|
||||
|
||||
To avoid conflicts on shared files (`bridge/types.rs`, `protocol.gd`, `PROTOCOL_VERSION`):
|
||||
|
||||
1. Copy PR (#597) — no code dependencies; merge first. Lines must be in `main` before playthrough proof runs.
|
||||
2. Server PRs (#589, #591, #594) — no client dependencies; merge in any order. These are independent.
|
||||
3. **Server PR #587 (StartupMessage + archetype) + Client PR #588 (character select)** — must land together. Both bump `PROTOCOL_VERSION` to 19. Coordinate merge timing.
|
||||
4. Client PR #590 (triangle consumer) — merge after server #589 is in main.
|
||||
5. Client PR #592 (ticker HUD) — can merge before server #591 (renders nothing when field absent); merge after for clean integration test.
|
||||
6. Server PR #595 (opening monologue gate) — merge after server #587 is in main.
|
||||
7. Server PR #593 (playthrough proof) — last to merge. Requires all upstream PRs green.
|
||||
|
||||
**Critical:** #587 and #588 share the PROTOCOL_VERSION bump. Do not merge one without the other.
|
||||
|
||||
---
|
||||
|
||||
## v0.1 Readiness After This Sprint
|
||||
|
||||
After Sprint 24 ships, the vertical slice (D-027) satisfies:
|
||||
|
||||
| D-027 Criterion | Sprint 24 Delivery | Status |
|
||||
|----------------|-------------------|--------|
|
||||
| 30 minutes of daily-life breathing room before contamination | Contamination delay (Sprint 22 #254) + storyteller lifecycle (Sprint 23 #572) | Done — Sprint 22/23 |
|
||||
| Both playthroughs feel fundamentally different | Character archetype select (#587/#588) + archetype-gated monologue (#595) + character voice (#597) | Done — this sprint |
|
||||
| Player names an NPC they felt conflicted about | Kael/Sera content (Sprint 12–22) + tell escalation (#589) + proximity monologue (#597) | Done — this sprint |
|
||||
| Observe→notice→follow→discover emerges from systems | Tell escalation (#589) + proximity monologue (#597) + existing dialogue/knowledge graph | Done — this sprint |
|
||||
|
||||
Sprint 25 will address wow moments #3 (THE FRIEND's Contradiction) and #6 (The Quiet Moment) — the two that require deeper playtest-driven tuning. The core loop is complete after Sprint 24.
|
||||
@@ -0,0 +1,199 @@
|
||||
# Sprint 24: Signal — Server Tasks
|
||||
|
||||
**Goal:** Wire the storyteller's activation event into player-visible consequences, thread character archetype through the full session lifecycle, and deliver the first unscripted end-to-end v0.1 playthrough — from main menu to triangle activation.
|
||||
|
||||
**Branch:** `server`
|
||||
**Agents:** Dudley (simulation), Tyre (architecture), Hoshe (QA)
|
||||
|
||||
> **This is the capstone sprint for v0.1.** Everything server-side must converge on a production
|
||||
> playthrough: correct character spawned, opening monologue fired, storyteller active, triangle
|
||||
> escalation observable. Sprint 25 is playtest. There is no Sprint 26 before v0.1 ships.
|
||||
|
||||
---
|
||||
|
||||
## New Tickets
|
||||
|
||||
| # | Title | Blocked by |
|
||||
|---|-------|------------|
|
||||
| #587 | Character archetype — server: accept archetype in StartupMessage, spawn correct PC | — |
|
||||
| #589 | Triangle activation consumer — server: behavioral tell escalation on TriangleActivated | — |
|
||||
| #591 | News ticker — server: load ticker YAML, emit current headline in snapshot | — |
|
||||
| #595 | Opening monologue trigger — server: emit opening lines at session start based on archetype | #587 |
|
||||
| #593 | v0.1 playthrough proof: full session from main menu through storyteller activation | #587, #589, #591, #595 (+ client #588, #590, #592 + copy #597) |
|
||||
| #594 | Tile data model design — produce D-record for extensible tile properties | — (design only, unblocks post-v0.1) |
|
||||
|
||||
Use `tooling/db/ticket show <id>` for full details.
|
||||
|
||||
---
|
||||
|
||||
## Key Decisions
|
||||
|
||||
- `decisions/scope.md` — D-027 (vertical slice success criteria — the 4 tests the playthrough must satisfy), D-039 (6 wow moments — opening arrival, character's eye, FRIEND contradiction, divergence reveal, news ticker gut-punch, quiet moment)
|
||||
- `decisions/content.md` — D-032 (separate monologue pools: `character` tag is a hard partition, not a filter), D-035 (tag taxonomy: `trigger`, `character`, `prerequisite` fields on monologue lines), D-023 (three-tier content model — storyteller activates Tier 1 modules based on engagement)
|
||||
- `decisions/content.md` — D-024 (NPC 10-axis model — tell system axis 9; tells flow from simulation state not authored), D-036 (Sova Transit District — The Terminal, The Last Shift, news ticker content at `ticker/the-last-shift.yaml`)
|
||||
- `decisions/architecture.md` — D-020 (StartupMessage is the only initialization crossing IPC; PROTOCOL_VERSION gates wire compatibility), D-041 (knowledge graph data model — KnowledgeConfidence confidence levels), D-010 principle 3 (no player identity baked into game loop — archetype is a configuration, not a special case)
|
||||
|
||||
---
|
||||
|
||||
## Open Questions to Resolve Early
|
||||
|
||||
- **Q-052: Storyteller hint delivery channels** — #589 implements channels 1 (behavioral tell escalation) and 7 (proximity monologue, via copy #597). Environmental change (channel 2) and overheard NPC conversation (channel 4) are deferred to Sprint 25. This sprint resolves Q-052 at v0.1 scope. No design discussion needed — the channel inventory is decided; implementation scope is constrained to what's achievable this sprint.
|
||||
|
||||
---
|
||||
|
||||
## Notes
|
||||
|
||||
### #587 — Character archetype in StartupMessage
|
||||
|
||||
**What exists:** `StartupMessage` in `server/src/bridge/types.rs` has one field: `pub world_seed: u64`. The production startup path initializes all NPCs and spawns the player entity without any archetype selection — the player entity carries `CharacterArchetype::Detective` by default (see `server/src/simulation/monologue.rs` line ~174: `character: "detective".to_string()`). `CharacterArchetype` enum is already defined in `bridge/types.rs` with `Smuggler` and `Detective` variants (used by phase-2 verb filter in `server/src/perception/observer/mod.rs`).
|
||||
|
||||
**What to deliver:**
|
||||
|
||||
1. Add `pub character_archetype: CharacterArchetype` to `StartupMessage`. Default to `Detective` if absent during deserialization (backward-compatible via `#[serde(default)]`).
|
||||
|
||||
2. In the production startup path (`server/src/main.rs` or `server/src/content/spawn.rs`), read `startup_msg.character_archetype` and insert the correct `CharacterArchetype` component on the player entity. The player entity is currently spawned without an archetype component — insert it here.
|
||||
|
||||
3. In `server/src/simulation/monologue.rs`, read the `CharacterArchetype` component from the player entity at `MonologueState` initialization (or on first tick) and set `MonologueState.character` from it: `"smuggler"` or `"detective"`. This is the string that gates all monologue pool selection.
|
||||
|
||||
4. Bump `PROTOCOL_VERSION` to 19. The new field in `StartupMessage` is a breaking change — old clients send a message that omits `character_archetype`, new server will default it correctly, but old servers receiving the new format will fail. Coordinate with Stig (#588) on timing.
|
||||
|
||||
**Gotcha:** `CharacterArchetype` already serializes via serde. The existing `impl From<CharacterArchetype> for ObserverSnapshot` path in bridge tests validates round-trips — make sure the new `StartupMessage` test also covers the default case (`Smuggler` serializes and round-trips; missing field deserializes as `Detective`).
|
||||
|
||||
**Unblocks:** #595 (opening monologue), #588 (client select screen can now send the archetype).
|
||||
|
||||
---
|
||||
|
||||
### #589 — Triangle activation consumer: behavioral tell escalation
|
||||
|
||||
**What exists:** `server/src/npc/tell_state.rs` — `TellCategory` enum (Nervous, Angry, Friendly, Guarded, RoutineDeviation) and `derive_tell_state()` function. Tell state is derived from NPC axis values each tick and emitted in `ObserverSnapshot.entities[].tell_state`. `RoutineDeviation` component exists. The storyteller emits `TriangleActivated { triangle_id, npc_entity }` into `TriangleActivatedQueue`.
|
||||
|
||||
**What to deliver:** A system `escalate_tells_on_activation()` that:
|
||||
|
||||
1. Drains `TriangleActivatedQueue` each tick (non-destructively — queue must still be readable by other consumers; use `events()` pattern or check if existing drain is appropriate).
|
||||
|
||||
2. For each `TriangleActivatedEvent`, find the anchor NPC entity (`event.npc_entity`) and the 1-2 NPCs who are in the same triangle (via `TriangleState` query). These are the triangle's NPCs.
|
||||
|
||||
3. Insert a `RoutineDeviation` component on all triangle NPCs. `RoutineDeviation` is the strongest tell category per `derive_tell_state()` priority order — it overrides Nervous/Angry/Guarded. This makes the triangle NPCs immediately observable as anomalous.
|
||||
|
||||
4. The `RoutineDeviation` component should carry a `expires_at_tick: u64` field (if not already present) so it can be removed after a configurable window (suggest `TELL_ESCALATION_DURATION_TICKS = 300` = 30 game-minutes). Add a system to remove expired `RoutineDeviation` components.
|
||||
|
||||
**Why this is the right channel:** D-024 axis 9 (tell system) is a simulation output, not authored content. The `RoutineDeviation` tell fires when the NPC is off their usual schedule — which is exactly true post-activation (the triangle is hot). No new content required. Client sees it as `tell_state: RoutineDeviation` on the visible entity. Copy (#597) authors the monologue lines the client fires when the player observes this tell.
|
||||
|
||||
**Integration point:** `TriangleActivatedQueue` is in `server/src/storyteller/mod.rs`. The new system should live in `server/src/storyteller/` or `server/src/simulation/pressure.rs` — either is appropriate. Register in `StorytellerPlugin.build()`.
|
||||
|
||||
**Test:** `cargo test` — verify that after `TriangleActivatedQueue` is populated with a test event, triangle NPCs have `RoutineDeviation` inserted and `derive_tell_state()` returns `RoutineDeviation` for them.
|
||||
|
||||
---
|
||||
|
||||
### #591 — News ticker: server-side
|
||||
|
||||
**What exists:** `content/campaigns/main/systems/krenn/stations/sova/districts/transit/ticker/the-last-shift.yaml` — 30 authored headlines (freight, politics, infrastructure, sports, commission, community categories). The YAML is fully authored (Sprint 12, #306). It is NOT loaded at runtime — the content loader (`server/src/content/loader.rs`) does not parse ticker files. `ObserverSnapshotWire` in `server/src/bridge/types.rs` has no ticker field.
|
||||
|
||||
**What to deliver:**
|
||||
|
||||
1. `TickerLine` struct: `id: String`, `text: String`, `category: String`. Add to `bridge/types.rs`.
|
||||
|
||||
2. Add `current_ticker: Option<TickerLine>` to `ObserverSnapshotWire`. Only populated when player is in The Last Shift zone (zone_id `"bar"` — check `server/src/simulation/zone.rs`). `None` in all other zones.
|
||||
|
||||
3. `TickerPool` resource: loads `ticker/the-last-shift.yaml` at startup via the content loader. Holds all 30 headlines. Uses `SimRng` to advance to a new headline every `TICKER_ROTATION_TICKS = 200` ticks (20 game-minutes). Deterministic under D-010 — always use `SimRng`, never system randomness.
|
||||
|
||||
4. In the observer snapshot system (`server/src/perception/observer/mod.rs`), read `TickerPool` and populate `current_ticker` when player zone is `"bar"`.
|
||||
|
||||
**Gotcha:** The ticker rotation must use `SimRng` (the seeded bevy resource), not `rand::thread_rng()`. D-010 principle 4 — deterministic simulation. A ticker rotation driven by `thread_rng()` would produce different headlines on replay, breaking golden-file tests.
|
||||
|
||||
**Content note:** The ticker content file at `ticker/the-last-shift.yaml` uses a `dual_lens` field per headline (separate monologue notes for smuggler vs detective perspective). These notes are for copy authoring reference only — do NOT include them in the `TickerLine` wire struct. The `text` field is what crosses the boundary; `dual_lens` is authoring metadata.
|
||||
|
||||
---
|
||||
|
||||
### #595 — Opening monologue trigger
|
||||
|
||||
**What exists:** `server/src/simulation/monologue.rs` — `MonologueState` has `pub character: String` (initialized as `"detective"`) and `pub enter_location_fired: bool`. The system `tick_monologue()` calls `select_monologue_line()` which filters pools by `pool.character != character` — so the character string gate already works. Opening monologue content is fully authored at:
|
||||
- `content/campaigns/main/.../monologue/detective/opening.yaml` (12 lines, Sprint 12 #300)
|
||||
- `content/campaigns/main/.../monologue/smuggler/opening.yaml` (Sprint 12 #299)
|
||||
|
||||
Both files use `trigger: enter_location` and `situation: [arrival, shift_start]`. The `enter_location` trigger fires on the first tick (`MonologueState.enter_location_fired = false` → fires → sets `true`).
|
||||
|
||||
**What to deliver:** This ticket is small because the infrastructure is almost complete. The only missing piece is that `MonologueState.character` is initialized as `"detective"` before the archetype is known. Fix:
|
||||
|
||||
1. After #587 lands (archetype inserted on player entity), read `CharacterArchetype` in `MonologuePlugin.build()` or the first-tick setup system and set `MonologueState.character` correctly: `CharacterArchetype::Smuggler → "smuggler"`, `CharacterArchetype::Detective → "detective"`.
|
||||
|
||||
2. Verify that `select_monologue_line()` with `trigger = "enter_location"` and `character = "smuggler"` correctly selects from `opening.yaml` in the smuggler subdirectory. Run the existing monologue integration test with a smuggler archetype — it should already pass once #587 sets the character string.
|
||||
|
||||
3. Add a regression test: spawn two sessions (smuggler + detective), advance 1 tick each, assert different `character` on `MonologueState`. This verifies the archetype flows end-to-end.
|
||||
|
||||
**Blocked by:** #587 (needs `CharacterArchetype` on player entity before this system can read it).
|
||||
|
||||
---
|
||||
|
||||
### #594 — Tile data model design (D-record)
|
||||
|
||||
**What exists:** Current tile format is single characters (`F/W/V/R`) in string arrays in location YAML files. This cannot represent per-tile properties (door access lists, container contents, damage state, visual variant, sound properties, trigger zones). Epic #586 tracks this. This ticket produces the design only — no migration, no implementation.
|
||||
|
||||
**What to deliver:** A filed D-record in `decisions/architecture.md` via `tooling/db/decision claim D architecture "Tile data model — extensible per-tile properties"` before writing. The D-record must:
|
||||
|
||||
1. Survey what tile-level data the game needs across systems (doors, containers, damage, visual variants, trigger zones, material properties).
|
||||
2. Choose between: (a) tile palette/registry (tiles are typed by ID, properties on the type), (b) per-tile property bags (each tile can have arbitrary key-value), (c) ECS-style tile components (tiles are entities), or (d) hybrid.
|
||||
3. Specify the YAML authoring format (human-writable, survives merge conflicts), the loader contract (how the server parses it), and the runtime representation (what ECS queries use).
|
||||
4. Estimate migration effort for the 5 existing location YAMLs.
|
||||
|
||||
**Scope:** This is design work only. No code changes. The D-record is the deliverable. Tyre should author it; Dudley reviews for implementation feasibility. File via the standard decision workflow (`decision claim` → edit `decisions/architecture.md` → commit with pre-commit hook running `decisions-sync`).
|
||||
|
||||
---
|
||||
|
||||
### #593 — v0.1 playthrough proof
|
||||
|
||||
**What exists:** By the time this ticket starts, all upstream tickets are merged: archetype in StartupMessage (#587), tell escalation (#589), ticker in snapshot (#591), opening monologue archetype-gated (#595), client character select (#588), client triangle consumer (#590), client ticker (#592), copy activation monologue lines (#597).
|
||||
|
||||
**What to deliver:** This is an integration proof ticket, not an implementation ticket. Deliverable is a written test plan execution + green CI.
|
||||
|
||||
1. **Full playthrough test (manual):** Boot server in production mode (no `--gauntlet`). Boot client in production mode (no `SR_TEST=1`). From main menu, click "New Game." Character select screen appears — select Smuggler. Game scene loads. Confirm: opening monologue fires (Smuggler voice). Walk to The Terminal. Observe Kael for ~3 game-minutes (check `EngagementRecord` via debug console `npc <id>`). Use debug console `contaminate` to skip to contamination phase. Wait for activation pass — `triangles` command shows one triangle in Active phase. Walk back to Kael — `tell_state` is `RoutineDeviation`. Proximity monologue fires (from copy #597). Walk to The Last Shift — news ticker visible. CI green.
|
||||
|
||||
2. **Automated integration test (server):** Add `test_v0_1_integration_playthrough` in `server/tests/`. Uses the existing test-client infrastructure (tooling/test-client): boot server, send `StartupMessage { world_seed: 12345, character_archetype: Smuggler }`, advance 1 tick, assert snapshot contains smuggler opening monologue, advance to tick 3000, send `SkipToContamination` debug command, advance 10 more ticks, assert `TriangleActivatedQueue` is non-empty in server state (via golden snapshot comparison).
|
||||
|
||||
3. **PR merge coordination:** Server #593 and client #588/#590/#592 must all be green on their respective branches before this ticket can be filed as done. The playthrough proof is the collective gate for the sprint.
|
||||
|
||||
**Gotcha — PROTOCOL_VERSION:** #587 bumps to 19. Client #588 must update `Protocol.PROTOCOL_VERSION` to 19 simultaneously. The version mismatch is a connection crash. Coordinate with Stig on merge timing.
|
||||
|
||||
---
|
||||
|
||||
## Dependency Chain
|
||||
|
||||
```
|
||||
#587 (archetype in StartupMessage) ─────────────────────────────────────────────────┐
|
||||
└→ #595 (opening monologue archetype-gated) │
|
||||
└→ #588 (client: character select screen) ← client work │
|
||||
↓
|
||||
#589 (tell escalation on TriangleActivated) ─────────────────────────────────────── #593
|
||||
└→ #590 (client: triangle consumer) ← client work (v0.1
|
||||
playthrough
|
||||
#591 (news ticker in snapshot) ─────────────────────────────────────────────────── proof)
|
||||
└→ #592 (client: ticker HUD) ← client work │
|
||||
│
|
||||
#597 (copy: activation monologue lines) ← copy work ────────┘
|
||||
|
||||
#594 (tile data model D-record) ← standalone design track, no v0.1 dependency
|
||||
```
|
||||
|
||||
Parallel server tracks: #587, #589, #591, #594 are all independent — start all simultaneously. #595 blocked on #587.
|
||||
|
||||
---
|
||||
|
||||
## PR Workflow
|
||||
|
||||
```bash
|
||||
tea pr create --repo jpmschweitzer/settled-reach --login schweitz \
|
||||
--title "feat(server): character archetype in StartupMessage and monologue gating" \
|
||||
--description "body" --base main --head server
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Sprint Completion (Server Criteria)
|
||||
|
||||
1. `cargo test` green on server branch. All existing tests pass. New tests for archetype round-trip and tell escalation pass.
|
||||
2. `StartupMessage` with `character_archetype: Smuggler` produces a smuggler player entity with `MonologueState.character = "smuggler"` on tick 1.
|
||||
3. After `TriangleActivated` fires, triangle NPCs have `RoutineDeviation` inserted and `tell_state: RoutineDeviation` appears in the snapshot.
|
||||
4. Snapshot contains `current_ticker` (non-null headline) when player is in `"bar"` zone.
|
||||
5. Opening monologue (enter_location) fires on tick 1 with lines from the correct character pool.
|
||||
6. Integration test `test_v0_1_integration_playthrough` passes end-to-end.
|
||||
7. `PROTOCOL_VERSION = 19` — matches client.
|
||||
Reference in New Issue
Block a user