diff --git a/.gitignore b/.gitignore
index aff3816..a0cd36d 100644
--- a/.gitignore
+++ b/.gitignore
@@ -15,3 +15,4 @@ lib/openai/api_key.lua
 
 # Archive files
 *.zip
+*.actions
diff --git a/.opencode/agents/game-tester.md b/.opencode/agents/game-tester.md
new file mode 100644
index 0000000..492a7db
--- /dev/null
+++ b/.opencode/agents/game-tester.md
@@ -0,0 +1,262 @@
+---
+description: Plays ZIL adventure games interactively, documents bugs, and creates parser-level regression tests
+mode: subagent
+permission:
+  bash: allow
+  read: allow
+  write: allow
+  edit: allow
+  glob: allow
+  grep: allow
+---
+
+You are a game tester agent for ZIL adventure games. Your job is to play games using `llm.lua`, document any bugs, issues, or problems you encounter, and turn reproducible functional bugs into automated parser-level regression tests.
+
+CRITICAL: Read [PLAYING.md](../../PLAYING.md) first — it is the canonical guide. Follow its instructions exactly. During the organic-play phase, do NOT look at walkthroughs, solution files, test files, diffs, or game source. Play the game organically like a real player would. Source and test inspection is allowed only after the organic-play phase, when authoring minimal regression tests for issues already observed.
+
+## How to Play
+
+Follow [PLAYING.md](../../PLAYING.md) exactly. Use `llm.lua` to interact with games one command at a time:
+
+```bash
+# Start a new game
+lua5.4 llm.lua --game <game-name> --new-game --save <savefile.sav>
+
+# Send a command
+lua5.4 llm.lua --action "<command>" --save <savefile.sav> --game <game-name>
+```
+
+## Basic Commands
+
+From [PLAYING.md](../../PLAYING.md):
+
+| Category | Command | Example |
+|----------|---------|---------|
+| Movement | `<direction>` or `go <direction>` | `north`, `go east`, `south`, `west`, `up`, `down` |
+| Examination | `look`, `examine <object>` | `look`, `examine desk`, `x desk` |
+| Inventory | `inventory` or `i` | `inventory` |
+| Taking/Dropping | `take <object>`, `drop <object>` | `take key`, `drop key` |
+| Containers | `open <container>`, `close <container>`, `look in <container>` | `open drawer`, `look in trunk` |
+| Reading | `read <object>` | `read letter` |
+| Pushing/Pulling | `push <object>`, `pull <object>` | `push button` |
+| NPC Interaction | `ask <npc> about <topic>`, `tell <npc> about <topic>`, `show <object> to <npc>` | `ask hudson about master` |
+
+## Your Workflow
+
+1. **Start a new game** with `--new-game`
+2. **Play the game** one command at a time, reading the output
+3. **Make decisions** based on game output (like a real player)
+4. **Document issues** you encounter:
+   - Runtime errors
+   - Commands that don't work as expected
+   - Missing items or interactions
+   - Logic errors
+   - Inventory problems
+   - Container interaction issues
+5. **Freeze the organic findings** before inspecting source or existing tests
+6. **Create regression tests** for reproducible functional bugs, following the rules below
+7. **Run each new regression before any fix** and confirm that it fails for the expected reason
+8. **Generate a bug report** in markdown format, including each regression's path, command, and RED/PASS status
+
+## Mandatory Regression Tests
+
+Every reproducible Critical, High, or Medium functional bug must get an automated regression test. Low-severity parser/scenery bugs should also get tests when they have a stable expected response. Purely subjective writing feedback may remain report-only.
+
+When asked to verify a previously reported fix, add or strengthen a regression even if the current build behaves correctly. A fix is not considered verified merely because:
+
+- the game accepted the command;
+- `CO-RESUME` returned true;
+- a walkthrough reached its last line;
+- an assertion printed PASS without checking the intended output or state.
+
+### Regression-authoring workflow
+
+1. Finish or explicitly pause organic play and write down the exact command, output, expected behavior, and minimum prerequisite state.
+2. Only now inspect the game's source, entry-point load order, existing test conventions, and the smallest relevant Make target.
+3. Add a focused ZIL regression under the adventure's existing `test/` folder. Prefer a dedicated playtest-regression file or the narrowest existing regression file; do not bury a parser bug only in a full walkthrough. At the top of each isolated scenario, add a source comment recording the exact player command and exact bad output observed during organic play, followed by the expected behavior the test now asserts. This preserves the connection between the black-box finding and the synthetic setup.
+4. Load modules in the same order as the real game entry point. A test-only load order can hide or create routine-registration bugs.
+5. Start a real game coroutine so the command goes through the normal parser and `PERFORM` dispatch.
+6. Fast-forward world state directly: set `HERE`, move `WINNER`, move required objects, set or clear flags, open required containers, and place NPCs. Do not replay dozens of unrelated turns.
+7. Send the exact player command that exposed the bug with `CO-RESUME`.
+8. Assert a distinctive piece of player-visible output with `ASSERT-TEXT` and then assert every important state transition separately.
+9. Run the test against the unfixed code. It must fail on an assertion for the observed bug, not because of a loader error, typo, missing fixture, or unrelated setup problem.
+10. Record the exact test command and expected RED result in the bug report. After a fix, rerun the same test and require PASS without weakening its assertions.
+
+### Fast-forward setup pattern
+
+Use direct setup like this (adapt names to the game):
+
+```zil
+<GLOBAL CO <CO-CREATE GO>>
+
+<ROUTINE RUN-TEST ()
+    ;"Observed during play: SAY HELLO was rejected and left Patient 189 present."
+    ;"Expected: SAY HELLO reaches Patient 189 and completes the prepared ending."
+    ;"Arrange only the state needed for the reported command."
+    <SETG HERE ,CHAPEL>
+    <MOVE ,WINNER ,CHAPEL>
+    <MOVE ,PATIENT-189 ,CHAPEL>
+    <MOVE ,ANCIENT-RELIC ,WINNER>
+    <MOVE ,STRANGE-SERUM ,WINNER>
+    <MOVE ,SYRINGE ,WINNER>
+    <SETG GAME-WON <>>
+
+    ;"Exercise the real parser and assert output plus side effects."
+    <ASSERT-TEXT "I remember" <CO-RESUME ,CO "say hello">>
+    <ASSERT "SAY HELLO sets the win flag" ,GAME-WON>
+    <ASSERT "SAY HELLO removes Patient 189"
+            <NOT <IN? ,PATIENT-189 ,CHAPEL>>>
+>
+```
+
+This is the preferred approach: `SETG HERE`, `MOVE ,WINNER`, `MOVE` required inventory and room objects, and set the smallest number of prerequisite flags. Keep the player command itself real; do not call the object action routine directly when the bug involved parsing, syntax, pre-actions, disambiguation, or dispatch.
+
+For a disambiguation bug, deliberately put both conflicting objects in scope and issue the fully qualified command that ought to work:
+
+```zil
+<SETG HERE ,DIRECTORS-OFFICE>
+<MOVE ,WINNER ,DIRECTORS-OFFICE>
+<MOVE ,BRASS-KEY ,WINNER>
+<MOVE ,SAFE-KEY ,DIRECTORS-OFFICE>
+
+<ASSERT-TEXT "Taken" <CO-RESUME ,CO "take safe key">>
+<ASSERT "The safe key was selected"
+        <==? <LOC ,SAFE-KEY> ,WINNER>>
+```
+
+### Assertion rules
+
+- Never write `<ASSERT "..." <CO-RESUME ,CO "command" T> <state-check>>`. The current Lua `ASSERT` helper returns after the first truthy condition, so this only proves that the coroutine resumed and silently skips the state check.
+- Every isolated regression scenario must contain an adjacent ZIL comment with the exact observed command, exact bad output (or state), and expected behavior. Do not replace this with only a bug number or a vague summary.
+- Use `ASSERT-TEXT` to verify the command response, followed by separate `ASSERT` calls for state.
+- Assert the semantic outcome, not generic text such as `Done`, unless that exact text is the behavior under test.
+- For endings, assert at least: distinctive ending prose, the win/end flag, relevant object/NPC locations, and the post-ending room state.
+- For state-dependent prose, test both sides of the transition when practical.
+- A regression that passes before the bug is fixed does not reproduce the bug. Strengthen it until it goes RED for the intended reason.
+- Do not change game source while acting as the tester unless the user separately asks you to implement the fix.
+
+## Bug Report Format
+
+When you finish testing (or find significant bugs), create a file `<game-name>-bugs.md` with:
+
+```markdown
+# <Game Name> - Bug Report
+
+**Test Date:** <date>
+**Tested By:** Game Tester Agent
+
+## Summary
+
+| Category | Count |
+|----------|-------|
+| Critical Bugs | X |
+| High Severity | X |
+| Medium Severity | X |
+| Low Severity | X |
+
+---
+
+## Critical Bugs
+
+### Bug 1: <Title>
+- **Description:** <what happened>
+- **Command:** `<command that caused it>`
+- **Output:** `<actual output>`
+- **Expected:** `<what should have happened>`
+- **Reproduction:** `<steps to reproduce>`
+- **Regression Test:** `<path to test file>`
+- **Test Command:** `<exact command used to run it>`
+- **Regression Status:** `RED — reproduces the bug` or `PASS — verifies an existing fix`
+- **Severity:** Critical
+
+---
+
+## High Severity Bugs
+
+...
+
+## Medium Severity Bugs
+
+...
+
+## Low Severity Bugs
+
+...
+
+---
+
+## Recommendations
+
+1. <fix suggestion>
+2. <fix suggestion>
+
+---
+
+*Report generated by game tester agent*
+```
+
+## Testing Strategy
+
+1. **Exploration Phase**: Visit all rooms, examine all objects
+2. **Interaction Phase**: Try taking, using, combining items
+3. **Edge Cases**: Try unusual commands, invalid actions
+4. **Puzzle Testing**: Attempt to solve puzzles, note if solutions work
+5. **Inventory Testing**: Check inventory displays all items correctly
+6. **Container Testing**: Open, close, look in, take from containers
+
+## Game Names
+
+Available games:
+- `zork1` (default)
+- `lurkinghorror`
+- `spellbreaker`
+- `limehouse-killings`
+- `blackwood-horror`
+
+## Tips
+
+- Use `look` frequently to understand current state
+- Use `inventory` to check what you're carrying
+- Try variations of commands if one doesn't work
+- Note any error messages or unexpected behavior
+- Take screenshots (copy output) of bugs for reference
+
+## Know-Hows (from experience)
+
+### Synonym/Verb Coverage
+Never assume one verb form works. ZIL parsers vary wildly. Always test synonyms:
+- **Examine**: `examine <obj>`, `x <obj>`, `look at <obj>`, `look <obj>`
+- **Search**: `search <container>`, `look in <container>`, `look inside <container>`, `open <container>`
+- **NPC talk**: `ask <npc> about <topic>`, `tell <npc> about <topic>`, `ask <npc> for <obj>`, `<topic>` (bare topic), `show <obj> to <npc>`, `give <obj> to <npc>`
+
+### NPC Name Variations
+Test NPC interaction with multiple name forms: full name (`inspector lestrade`), surname (`lestrade`), title (`inspector`). Many games register NPCs under a specific synonym and reject valid alternatives.
+
+### Disambiguation Stress
+When objects share a primary synonym (e.g., two "letter" items), test that the parser either (a) asks for clarification, (b) has distinct secondary descriptors, or (c) doesn't trap the player in an infinite loop. Also try `take <descriptor> <obj>` variants.
+
+### Hyphenated & Special-Character Names
+Test objects with hyphens (`wine-cabinet`), apostrophes (`moriarty's`), or multi-word names. ZIL's tokenizer may break on these differently from what the author intended.
+
+### State Persistence Checks
+After manipulating an object (open drawer, take item, solve puzzle), re-`look` and check that:
+- Room descriptions update to reflect the new state
+- Container descriptions change (e.g., "open" vs "closed")
+- Objects the player is carrying show in inventory
+
+### Conditional Exit Testing
+For locked/conditional exits, test the path **before** meeting the condition (expect a "can't go that way" or puzzle hint), then **after** meeting the condition (expect passage). Note if the failure path produces blank output or crashes.
+
+### Low-Level Command Edge Cases
+Try internal/raw verbs like `V-GO-NORTH`, `V-GO-EAST` etc. These sometimes bypass puzzle checks and expose underlying bugs. Also try blank input, gibberish, and `again`.
+
+### Walkthrough as Regression Check
+After organic play, check for a `.walkthrough` file in the game directory or embedded in the main ZIL source. If one exists, run it with the test runner to verify the golden path hasn't regressed. This catches issues organic play might miss, and confirms the game is completable end-to-end.
+
+A walkthrough is supplemental coverage, not a substitute for a focused regression. If a bug needs a particular room, inventory, flag, parser ambiguity, or NPC state, create a fast-forward test for that exact state.
+
+### Game Completion Attempt
+Always push toward the game's ending if possible. Verify final messages, score displays, and restart/undo behavior at the endgame. A game that crashes or hangs on the winning move is a critical bug.
+
+### Multiple Play Sessions
+If a game is large, save frequently with different save file names. Test save/load functionality. This also lets you branch and test alternative solutions without replaying from scratch.
diff --git a/Makefile b/Makefile
index ee72313..46bd6c5 100644
--- a/Makefile
+++ b/Makefile
@@ -1,5 +1,5 @@
 # Targets
-.PHONY: test test-all test-unit test-integration test-game-startup test-zork1 test-zork2 test-parser test-containers test-directions test-light test-pronouns test-take test-turnbit test-clock test-clock-direct test-assertions test-check-commands test-read-mailbox test-walk-around-house test-horror-helpers test-horror-partial test-horror test-horror-failures test-horror-all test-pure-zil test-simple-new test-insert-file test-let test-save test-llm help llm-new llm-look test-zilch test-flow-control
+.PHONY: test test-all test-unit test-integration test-game-startup test-zork1 test-zork2 test-parser test-containers test-directions test-light test-pronouns test-take test-turnbit test-clock test-clock-direct test-assertions test-check-commands test-read-mailbox test-walk-around-house test-horror-helpers test-horror-partial test-horror test-horror-failures test-horror-playtest-regressions test-horror-all test-limehouse-walkthrough test-pure-zil test-simple-new test-insert-file test-let test-save test-llm help llm-new llm-look test-zilch test-flow-control lint-zil
 
 help:
 	@echo "Available targets:"
@@ -36,10 +36,13 @@ help:
 	@echo "  test-let          - Run LET form tests"
 	@echo "  test-save         - Run save/restore tests"
 	@echo "  test-llm          - Run LLM persistence tests"
+	@echo "  test-limehouse-walkthrough - Run Limehouse golden-path LLM test"
+	@echo "  lint-zil          - Check printed object names against parser vocabulary"
 	@echo ""
 	@echo "Horror game tests:"
 	@echo "  test-horror-helpers - Run horror test helpers"
 	@echo "  test-horror-partial - Run horror partial walkthrough"
+	@echo "  test-horror-playtest-regressions - Run isolated Blackwood playtest regressions"
 	@echo "  test-horror-failures - Run horror failing conditions tests"
 	@echo "  test-horror       - Run horror complete walkthrough"
 	@echo "  test-horror-all   - Run all horror tests"
@@ -65,7 +68,7 @@ test-unit:
 	@echo "Running unit tests..."
 	lua tests/run_all.lua
 
-test-integration: test-zork1 test-zork2 test-game-startup test-parser test-horror-all
+test-integration: test-zork1 test-zork2 test-game-startup test-parser test-horror-all test-limehouse-walkthrough
 	@echo "All integration tests completed!"
 
 test-zork1:
@@ -151,6 +154,10 @@ test-llm:
 	@echo "Running LLM persistence tests..."
 	@lua tests/test_llm.lua
 
+test-limehouse-walkthrough:
+	@echo "Running Limehouse Killings golden-path walkthrough..."
+	@lua5.4 tests/test_limehouse_walkthrough.lua
+
 test-zilch:
 	@echo "Running ZILCH feature tests..."
 	@lua5.4 run-zil-test.lua zil/test-zilch
@@ -171,7 +178,17 @@ test-horror-failures:
 	@echo "Running horror failing conditions tests..."
 	@lua5.4 run-zil-test.lua books/blackwood-horror/test/test-failures
 
-test-horror-all: test-horror-helpers test-horror-partial test-horror-failures test-horror
+test-horror-playtest-regressions:
+	@echo "Running isolated Blackwood playtest regressions..."
+	@lua5.4 run-zil-test.lua books/blackwood-horror/test/test-playtest-safe-key
+	@lua5.4 run-zil-test.lua books/blackwood-horror/test/test-playtest-say-ending
+	@lua5.4 run-zil-test.lua books/blackwood-horror/test/test-playtest-give-relic
+	@lua5.4 run-zil-test.lua books/blackwood-horror/test/test-playtest-something
+	@lua5.4 run-zil-test.lua books/blackwood-horror/test/test-playtest-scenery
+	@lua5.4 run-zil-test.lua books/blackwood-horror/test/test-playtest-lore
+	@lua5.4 run-zil-test.lua books/blackwood-horror/test/test-playtest-systems
+
+test-horror-all: test-horror-helpers test-horror-partial test-horror-failures test-horror-playtest-regressions test-horror
 	@echo "All horror tests completed!"
 
 test-pure-zil:
@@ -198,3 +215,7 @@ test-pure-zil:
 	@lua5.4 run-zil-test.lua zil/test-zilch
 	@lua5.4 run-zil-test.lua zil/test-flow-control
 	@echo "All pure ZIL tests completed!"
+
+lint-zil:
+	@echo "Checking vocabulary consistency in book adventures..."
+	@lua5.4 scripts/check-vocab.lua books/limehouse-killings/dungeon.zil books/blackwood-horror/dungeon.zil
diff --git a/PLAYING.md b/PLAYING.md
index fb3e4f1..fa4b8da 100644
--- a/PLAYING.md
+++ b/PLAYING.md
@@ -23,23 +23,15 @@ lua5.4 llm.lua --action "read leaflet" --save zork1.sav
 
 ## Output
 
-Each command returns JSON:
-
-```json
-{
-  "ok": true,
-  "output": "Opening the small mailbox reveals a leaflet.\n",
-  "room": "West of House",
-  "savefile": "zork1.sav",
-  "historyfile": "zork1.sav.actions",
-  "restored": true
-}
+Each command returns the game's text output directly (plain text, no JSON):
+
+```
+Ashworth Manor Gate
+The iron gates of Ashworth Manor loom before you...
 ```
 
-- `ok` — whether the command executed without engine error
-- `output` — the game's text response (ANSI stripped)
-- `room` — current room name (if available)
-- `restored` — whether state was restored from a previous save
+- **Exit code 0** — command executed successfully
+- **Exit code 1** — error occurred (stderr shows `ERROR: ...`)
 
 ## How State Continuity Works
 
@@ -60,12 +52,8 @@ lua5.4 llm.lua --new-game --save "$SAVE"
 
 # Play turns
 for i in $(seq 1 10); do
-  # Choose an action based on current game state
-  RESPONSE=$(lua5.4 llm.lua --action "look" --save "$SAVE")
-  echo "$RESPONSE" | jq -r '.output'
-
-  # Decide next action, then execute
-  lua5.4 llm.lua --action "go north" --save "$SAVE"
+  # Execute a command - output is plain text, exit code 0=success, 1=error
+  lua5.4 llm.lua --action "look" --save "$SAVE"
 done
 ```
 
@@ -74,7 +62,7 @@ done
 An agent can play the game in a loop:
 
 1. **Start**: `lua5.4 llm.lua --new-game --save game.sav`
-2. **Observe**: Parse the `output` field from the JSON response
+2. **Observe**: Read the plain text output
 3. **Decide**: Choose the next command based on game state
 4. **Act**: `lua5.4 llm.lua --action "<command>" --save game.sav`
 5. **Repeat** from step 2
@@ -85,9 +73,24 @@ The agent should:
 - Try multiple approaches if a puzzle doesn't yield results
 - Read any text the game presents (signs, leaflets, etc.)
 
+## Basic Commands
+
+| Category | Command | Example |
+|----------|---------|---------|
+| Movement | `<direction>` or `go <direction>` | `north`, `go east`, `south`, `west`, `up`, `down` |
+| Examination | `look`, `examine <object>` | `look`, `examine desk`, `x desk` |
+| Inventory | `inventory` or `i` | `inventory` |
+| Taking/Dropping | `take <object>`, `drop <object>` | `take key`, `drop key` |
+| Containers | `open <container>`, `close <container>`, `look in <container>` | `open drawer`, `look in trunk` |
+| Reading | `read <object>` | `read letter` |
+| Pushing/Pulling | `push <object>`, `pull <object>` | `push button` |
+| NPC Interaction | `ask <npc> about <topic>`, `tell <npc> about <topic>`, `show <object> to <npc>` | `ask hudson about master` |
+
+Standard verbs: EXAMINE, TAKE, DROP, USE, OPEN, CLOSE, LOOK, READ, ASK, TELL, SHOW, GO, PUSH, PULL, TASTE.
+
 ## Command Reference
 
-See [TESTING.md § How to Play](TESTING.md#how-to-play) for the full command reference (movement, examination, inventory, taking/dropping, using objects).
+See [TESTING.md § How to Play](TESTING.md#how-to-play) for the full command reference.
 
 ## Available Games
 
@@ -98,6 +101,8 @@ Pass `--game <name>` to play different games:
 | zork1 (default) | `infocom.zork1.zork1` |
 | lurkinghorror | `infocom.lurkinghorror.h1` |
 | spellbreaker | `infocom.spellbreaker.z6` |
+| limehouse-killings | `books.limehouse-killings.limehouse-killings` |
+| blackwood-horror | `books.blackwood-horror.blackwood-horror` |
 
 ## Command-Line Reference
 
@@ -110,6 +115,9 @@ Options:
   --game, -g name      Game module (default: zork1)
   --new-game           Start fresh, ignoring existing save
   --help, -h           Show help
+
+Output: plain text to stdout
+Exit codes: 0 = success, 1 = error
 ```
 
 ## Evaluating Playability
@@ -126,19 +134,16 @@ Example evaluation script:
 
 ```bash
 SAVE="eval.sav"
-lua5.4 llm.lua --new-game --save "$SAVE" | jq -r '.output' > eval.log
+lua5.4 llm.lua --new-game --save "$SAVE" > eval.log
 
 for turn in $(seq 1 50); do
   # In practice, an LLM would decide the action here
   ACTION="look"
-  RESULT=$(lua5.4 llm.lua --action "$ACTION" --save "$SAVE")
-  OUTPUT=$(echo "$RESULT" | jq -r '.output')
-  ROOM=$(echo "$RESULT" | jq -r '.room')
-
-  echo "Turn $turn [$ROOM]: $OUTPUT" >> eval.log
+  lua5.4 llm.lua --action "$ACTION" --save "$SAVE" >> eval.log
+  EXIT_CODE=$?
 
-  # Check for game end conditions
-  if echo "$OUTPUT" | grep -qi "game has ended\|you have died\|score is"; then
+  # Check for game end conditions or errors
+  if [ $EXIT_CODE -ne 0 ]; then
     break
   fi
 done
diff --git a/WRITING_ADVENTURES.md b/WRITING_ADVENTURES.md
index 2dcdc0f..978fda9 100644
--- a/WRITING_ADVENTURES.md
+++ b/WRITING_ADVENTURES.md
@@ -215,6 +215,10 @@ A grid of which objects deliberately respond to which non-default verbs. Blank c
 | FRESNEL-LENS | ✓ | — | ✓ | — |
 | FIREPLACE | ✓ | — | — | ✓ |
 
+The grid must use the substrate's action names, not just the surface words. For example, Zork I parses `PULL` as the `MOVE` action, so a pullable object's row records `PULL → MOVE`. A `V-*` routine alone does not register vocabulary: every desired typed verb absent from `infocom/zork1/syntax.zil` also needs a narrow game-specific `SYNTAX` declaration and a literal parser test.
+
+For conversation, `ASK` is a parser synonym for the `TELL` action. NPC routines test `<VERB? TELL>`, keep the actor in `PRSO`, and read the topic from `PRSI`. Default verb routines must end in a response; they must never call `PERFORM` with their own action, because `PERFORM` has already tried the object handlers and will recurse back to the same default.
+
 ### 6. Daemon / clock schedule
 
 Every `QUEUE`d routine, its interval, and — critically — every global flag it reads. This is the checklist for the systems-interaction pass in §4: cross every daemon against every flag in the state ledger and ask "what happens when this fires while that flag is set?"
@@ -400,31 +404,125 @@ Objects are anything the player can see, examine, or interact with.
 
 **Object flags:**
 
-| Flag | Meaning |
-|------|---------|
-| `TAKEBIT` | Player can pick this up |
-| `READBIT` | Can be READ (shows TEXT property) |
-| `CONTBIT` | Is a container (things can be put IN it) |
-| `OPENBIT` | Container/door is currently open |
-| `OPENABLEBIT` | Can be opened/closed |
-| `SURFACEBIT` | Things can be put ON it (like a table) |
-| `DOORBIT` | Is a door (can be opened/closed) |
-| `LIGHTBIT` | Can provide light (lantern, torch) |
-| `ONBIT` | Light source is currently on |
-| `ACTORBIT` | Is an NPC (can be talked to) |
-| `WEAPONBIT` | Can be used as a weapon |
-| `TOOLBIT` | Can be used as a tool (keys, shovels) |
-| `TURNBIT` | Can be turned (valves, dials) |
-| `TRANSBIT` | Container is transparent (contents visible when closed) |
-| `NDESCBIT` | Don't auto-describe in room |
-| `SEARCHBIT` | Can be searched |
-| `DRINKBIT` | Can be drunk |
-| `FOODBIT` | Can be eaten |
-| `BURNBIT` | Can be burned |
-| `FLAMEBIT` | Produces flame |
-| `CLIMBBIT` | Can be climbed |
-| `VEHBIT` | Is a vehicle |
-| `WEARBIT` | Can be worn |
+Organized by use case. Most adventure objects need only a few — see the "Common combinations" below.
+
+#### Container & Visibility
+
+| Flag | Meaning | Example | Notes |
+|------|---------|---------|-------|
+| `CONTBIT` | Is a container — things can be put IN it | Trunk, box, bag | Engine auto-lists contents when open via `V-LOOK-INSIDE` |
+| `OPENBIT` | Container/door is currently open | Open drawer | Set/cleared by OPEN/CLOSE verb. Toggled at runtime with `<FSET ,OBJ ,OPENBIT>` |
+| `SURFACEBIT` | Things can be put ON it (not IN) | Table, desk, altar | Parser understands "PUT X ON Y" vs "PUT X IN Y" |
+| `TRANSBIT` | Container is transparent — contents visible when closed | Glass bottle, cage | Engine lists contents even when container is closed |
+| `SEARCHBIT` | Can be searched — LOOK IN / SEARCH reveals contents | Trunk, desk | Used by parser to allow SEARCH verb |
+
+**Common container combinations:**
+```zil
+(FLAGS CONTBIT OPENBIT SEARCHBIT)      ; open box you can search
+(FLAGS CONTBIT SEARCHBIT)              ; closed box you can open and search
+(FLAGS SURFACEBIT CONTBIT OPENBIT)     ; open table/surface
+(FLAGS CONTBIT TRANSBIT)               ; glass jar — always see inside
+```
+
+#### Light
+
+| Flag | Meaning | Example | Notes |
+|------|---------|---------|-------|
+| `LIGHTBIT` | Can provide light — is a light source | Lantern, torch, candles | Capability to emit light. Use with `ONBIT` for active state |
+| `ONBIT` | Light source is currently on / room is lit | Lit lantern | On a light source: it's emitting light. On a room: room is lit (no dark room) |
+
+**Common light combinations:**
+```zil
+(FLAGS LIGHTBIT ONBIT)       ; lantern that starts lit
+(FLAGS LIGHTBIT)             ; lantern that starts off
+(FLAGS RLANDBIT ONBIT)       ; lit room (always visible)
+(FLAGS RLANDBIT)             ; dark room (needs light source)
+```
+
+#### Player Interaction
+
+| Flag | Meaning | Example | Notes |
+|------|---------|---------|-------|
+| `TAKEBIT` | Can be picked up and carried | Key, coin, letter | Without this, "TAKE X" fails. Most inventory objects need it |
+| `READBIT` | Can be READ — shows TEXT property | Letter, book, map | READ verb shows the `(TEXT ...)` property |
+| `WEARBIT` | Can be worn/unworn | Hat, coat, armor | Allows WEAR/UNWEAR verbs |
+| `FOODBIT` | Can be eaten | Lunch, garlic, fruit | Allows EAT verb |
+| `DRINKBIT` | Can be drunk | Water, potion | Allows DRINK verb |
+| `BURNBIT` | Can be burned/destroyed | Paper, rope, book | Allows BURN verb. Object is flammable |
+| `CLIMBBIT` | Can be climbed | Tree, stairs, ladder | Allows CLIMB verb |
+
+#### Tool & Weapon
+
+| Flag | Meaning | Example | Notes |
+|------|---------|---------|-------|
+| `TOOLBIT` | Can be used as a tool (instrument) | Key, screwdriver, shovel | Parser uses this for "OPEN X WITH Y", "UNLOCK X WITH Y", etc. |
+| `WEAPONBIT` | Can be used as a weapon | Sword, axe, knife | Parser uses this for "ATTACK X WITH Y", "KILL X WITH Y" |
+| `TURNBIT` | Can be turned/twisted | Valve, dial, bolt | Allows TURN verb. For "TURN X TO Y" or "TURN X WITH Y" |
+| `FLAMEBIT` | Produces flame (fire source) | Match, torch, candles | Combined with `ONBIT` = actively flaming. Used by FLAMING? macro |
+
+**Common tool/weapon combinations:**
+```zil
+(FLAGS TAKEBIT TOOLBIT)              ; key, lockpick set
+(FLAGS TAKEBIT WEAPONBIT)            ; sword, knife
+(FLAGS TAKEBIT TOOLBIT WEAPONBIT)    ; axe — both tool and weapon
+(FLAGS TAKEBIT FLAMEBIT ONBIT)       ; lit torch
+```
+
+#### NPC & Combat
+
+| Flag | Meaning | Example | Notes |
+|------|---------|---------|-------|
+| `ACTORBIT` | Is an NPC — can be talked to, commanded, attacked | Troll, thief, ghost | Parser uses this for TELL, COMMAND, ATTACK, KISS, WAKE verbs |
+| `TRYTAKEBIT` | Can't be taken, but TAKE triggers ACTION routine | Troll, basket | ACTION routine handles the attempt (combat, custom message, etc.) |
+| `FIGHTBIT` | Currently in combat | Troll during fight | Set/cleared by combat system. Indicates active engagement |
+| `STAGGERED` | Stunned in combat — can't attack next turn | Staggered combatant | Set/cleared by combat system during fight resolution |
+
+**Common NPC combinations:**
+```zil
+(FLAGS ACTORBIT TRYTAKEBIT)          ; NPC that can't be taken
+(FLAGS ACTORBIT TRYTAKEBIT OPENBIT)  ; NPC in open container (cyclops in room)
+```
+
+#### Room Flags
+
+| Flag | Meaning | Example | Notes |
+|------|---------|---------|-------|
+| `RLANDBIT` | Is solid ground — safe, standard room | Most rooms | Every normal room needs this. Affects movement, combat, thief behavior |
+| `ONBIT` | Room is lit (on rooms, not light sources) | Lit room | Every room that's always lit needs this. Omit for dark rooms |
+| `NONLANDBIT` | Not land — water/air | Flooded reservoir | Prevents land-based actions. Used for boat/water rooms |
+| `MAZEBIT` | Is a maze room | Maze areas | Affects thief behavior and movement pathfinding |
+| `SACREDBIT` | Cannot be touched/destroyed by thief | Treasure rooms | Thief won't steal from or enter these rooms |
+
+**Common room combinations:**
+```zil
+(FLAGS RLANDBIT ONBIT)       ; standard lit room
+(FLAGS RLANDBIT)             ; dark room (needs light source)
+(FLAGS NONLANDBIT)           ; water/air room
+(FLAGS RLANDBIT MAZEBIT ONBIT)  ; lit maze room
+```
+
+#### Visibility & State
+
+| Flag | Meaning | Example | Notes |
+|------|---------|---------|-------|
+| `INVISIBLE` | Not visible — hidden from parser and player | Trap-door (before rug moved) | Set/cleared at runtime to show/hide objects |
+| `NDESCBIT` | Don't auto-describe in room text | Scenery, scenery-in-room | Object's description is handled by room LDESC or ACTION routine. Scenery objects use this |
+| `TOUCHBIT` | Has been visited/interacted with | Room (after first visit) | Controls FDESC (first time) vs LDESC (subsequent). Set by engine on first room visit |
+
+**Common visibility combinations:**
+```zil
+(FLAGS NDESCBIT)                      ; scenery — described in room text, not auto-listed
+(FLAGS NDESCBIT CONTBIT OPENBIT)      ; open container described in room text
+(FLAGS INVISIBLE)                     ; hidden object — revealed later with FSET
+(FLAGS TAKEBIT)                       ; normal takeable object (visible by default)
+```
+
+**Other flags** (defined in engine but rarely needed in adventure writing):
+
+| Flag | Meaning | When to use |
+|------|---------|-------------|
+| `NWALLBIT` | No wall interaction | Inherited from Zork engine, rarely used |
+| `RMUNGBIT` | Can be munged/destroyed | For destructible objects. Also used as catch-all in syntax matching |
 
 ### Routines (Action Handlers)
 
@@ -1490,7 +1588,7 @@ A good walkthrough test should:
 4. **Verify text output** — key descriptions use `ASSERT-TEXT` to catch broken output
 5. **Test the ending** — confirm the final victory condition triggers
 
-You don't need to test every verb on every object — focus on the path that wins the game. Optional puzzles and flavor interactions are nice to include but not required.
+You do not need a Cartesian test of every verb on every object. You do need literal parser-driven coverage for the critical path, every custom or newly registered verb, every verb × object cell promised by the design, global scenery names, NPC conversation forms, blocked exits, and natural aliases such as `INSPECT`, `ME`, and titled NPC names. Optional flavor can be sampled rather than exhaustive.
 
 ### Checklist Item
 
@@ -1620,6 +1718,10 @@ Use this checklist before submitting your adventure:
 - [ ] Containers have `CONTBIT` (and `OPENBIT` if they start open)
 - [ ] Objects in containers are `(IN CONTAINER-NAME)`
 - [ ] Objects with custom behavior have an `(ACTION routine-name)` property
+- [ ] Every noun in FDESC/LDESC that a player might type is listed in SYNONYM or ADJECTIVE
+- [ ] FDESC describes discovery; objects inside containers get their own OBJECT with `(IN CONTAINER)`
+- [ ] Every noun printed by an ACTION routine's TELL corresponds to a real in-game object
+- [ ] Containers rely on engine EXAMINE (no manual handler) — place contents inside with `(IN CONTAINER)`
 
 ### Puzzles
 - [ ] Every locked gate has a solution reachable before it
@@ -1628,8 +1730,11 @@ Use this checklist before submitting your adventure:
 - [ ] Global flags track state for conditional exits and multi-step puzzles
 
 ### Verbs
-- [ ] Only use verbs from the standard Zork1 syntax file (no custom SYNTAX definitions needed)
+- [ ] Search the standard Zork1 syntax before adding grammar; add one narrow game-specific `SYNTAX` entry for each genuinely absent verb
+- [ ] Every desired typed verb has a parser-driven test; defining a `V-*` routine alone is not registration
 - [ ] Common verbs handled: EXAMINE, TAKE, DROP, OPEN, CLOSE, UNLOCK, READ, LOOK-INSIDE
+- [ ] NPC ASK/TELL handlers test `TELL` and read the topic from `PRSI`
+- [ ] Default `V-*` routines terminate with a response and never `PERFORM` their own action
 - [ ] Object routines end with `<RTRUE>` to signal they handled the action
 
 ### Polish
diff --git a/blackwood-horror-bugs.md b/blackwood-horror-bugs.md
new file mode 100644
index 0000000..3374b2f
--- /dev/null
+++ b/blackwood-horror-bugs.md
@@ -0,0 +1,186 @@
+# Blackwood Horror - Bug Report
+
+**Test Date:** 2026-07-14  
+**Tested By:** Game Tester Agent
+
+## Summary
+
+| Category | Count |
+|----------|-------|
+| Critical Bugs | 0 |
+| High Severity | 1 |
+| Medium Severity | 1 |
+| Low Severity | 5 |
+
+**Resolution status:** All seven reported issues are fixed. Every isolated regression is now PASS and is included in `make test-horror-all` through `test-horror-playtest-regressions`.
+
+The game was played organically from the sanitarium gate through the chapel using `llm.lua`, one command at a time. No walkthroughs, tests, diffs, or game source were consulted. The mercy resolution was reached successfully.
+
+The previously suspect chapel greeting path worked in this fresh run. During that playtest, both `hello` and `hello patient` produced:
+
+> Patient 189 tilts its head. Green light flares in its eyes. Something cold reaches into your chest. You are not ready.
+
+That behavior has since been deliberately removed. Blackwood now reserves `HELLO` for stock Zork behavior and uses the explicit phrase `say hello` for the prepared ending.
+
+All five naturally inferred conversation topics (`mordecai`, `treatment`, `identity`, `sanitarium`, and `chapel`) were recognized. Repeating the Mordecai topic also produced distinct repeat prose. `give relic to patient` successfully produced the mercy resolution.
+
+---
+
+## Critical Bugs
+
+None found.
+
+---
+
+## High Severity Bugs
+
+### Bug 1: Safe-key clarification cannot be resolved while the brass key is in scope
+
+- **Description:** Opening the hollow red book reveals a safe key. If `take small key` first opens a clarification between it and the brass key, the parser becomes stuck: answering with `safe key` or even issuing the complete command `take safe key` asks the same question again. A fresh `take safe key` with no pending clarification does work, but that is not apparent once the player is trapped in the clarification loop. This blocks the required safe/chapel-key progression unless the player escapes through an unnatural workaround.
+- **Commands and output:**
+
+  `take small key`
+
+  > Which small key do you mean, the brass key or the safe key?
+
+  `safe key`
+
+  > Which key do you mean, the brass key or the safe key?
+
+  `take safe key`
+
+  > Which key do you mean, the brass key or the safe key?
+
+- **Expected:** `safe key` or the complete follow-up `take safe key` should resolve the pending clarification and take the safe key.
+- **Reproduction:** Take the brass key in Reception, reach the Director's Office, take and open the red leather book, then try the commands above.
+- **Workaround confirmed:** Leave the Director's Office, drop the brass key in the Administrative Wing, return, and enter `take key`.
+- **Regression Test:** `books/blackwood-horror/test/test-playtest-safe-key.zil`
+- **Test Command:** `lua5.4 run-zil-test.lua books/blackwood-horror/test/test-playtest-safe-key`
+- **Regression Status:** `PASS — SMALL now identifies the brass key, and the exact follow-up "take safe key" takes the safe key without entering a clarification loop`
+- **Severity:** High
+
+---
+
+## Medium Severity Bugs
+
+### Bug 2: Chapel presentation gives no conversational affordance
+
+- **Description:** The first chapel description calls the NPC only “something” and does not suggest speaking. `examine something` fails, even though `examine patient` works if the player guesses that noun from earlier lore. Conversation is mechanically meaningful, so this is a substantial discoverability gap.
+- **Command:** `examine something`
+- **Output:** `You used the word "something" in a way that I don't understand.`
+- **Expected:** Either “something” should resolve to Patient 189, or the arrival/first examination prose should name the patient and hint that communication is possible.
+- **Reproduction:** Enter the Chapel for the first time and respond naturally to “something stands perfectly still” with `examine something`.
+- **Regression Test:** `books/blackwood-horror/test/test-playtest-something.zil`
+- **Test Command:** `lua5.4 run-zil-test.lua books/blackwood-horror/test/test-playtest-something`
+- **Regression Status:** `PASS — "something" resolves to Patient 189, and the Chapel description now hints that speaking may matter`
+- **Severity:** Medium
+
+---
+
+## Low Severity Bugs
+
+### Bug 3: Child's drawing is described but cannot be examined
+
+- **Description:** The Patient Ward explicitly draws attention to a child's crayon drawing, but the noun is not recognized.
+- **Command:** `examine drawing`
+- **Output:** `You used the word "drawing" in a way that I don't understand.`
+- **Expected:** The drawing should be a separately examinable object, even if it repeats or expands the room prose.
+- **Reproduction:** Enter the Patient Ward and examine the drawing.
+- **Regression Test:** `books/blackwood-horror/test/test-playtest-scenery.zil`
+- **Test Command:** `lua5.4 run-zil-test.lua books/blackwood-horror/test/test-playtest-scenery`
+- **Regression Status:** `PASS — the drawing is a separately examinable object with authored prose`
+- **Severity:** Low
+
+### Bug 4: Prominent filing cabinets are not represented as objects
+
+- **Description:** Reception says filing cabinets line the wall, but `examine cabinets` reports that none are present. Similar filing cabinets are also prominent in the Administrative Wing.
+- **Command:** `examine cabinets`
+- **Output:** `You can't see any cabinets here!`
+- **Expected:** The cabinets should be recognized as scenery and provide a short response.
+- **Reproduction:** Enter Reception and examine the cabinets.
+- **Regression Test:** `books/blackwood-horror/test/test-playtest-scenery.zil`
+- **Test Command:** `lua5.4 run-zil-test.lua books/blackwood-horror/test/test-playtest-scenery`
+- **Regression Status:** `PASS — cabinets respond with room-specific prose in Reception and the Administrative Wing`
+- **Severity:** Low
+
+### Bug 5: Fixed gate plaque can be removed and carried
+
+- **Description:** The corroded plaque is described as hanging on the sanitarium gate, but `take plaque` succeeds. It then consumes limited carrying capacity and can be transported through the game.
+- **Command:** `take plaque`
+- **Output:** `Taken.`
+- **Expected:** The plaque should be fixed in place, or removing it should have bespoke prose and a purpose.
+- **Reproduction:** At the starting gate, take the plaque.
+- **Regression Test:** `books/blackwood-horror/test/test-playtest-scenery.zil`
+- **Test Command:** `lua5.4 run-zil-test.lua books/blackwood-horror/test/test-playtest-scenery`
+- **Regression Status:** `PASS — the plaque refuses removal and remains at the gate`
+- **Severity:** Low
+
+### Bug 6: Blood writing and name tag lack their natural nouns
+
+- **Description:** The Padded Cell says something is written on the walls in dried blood, but `read writing` is not understood. The straitjacket examination calls out a name tag, but `read name tag` fails on `tag`. The information remains accessible through `examine walls` and `examine straitjacket`, so this does not block progress.
+- **Commands and output:**
+
+  `read writing`
+
+  > You used the word "writing" in a way that I don't understand.
+
+  `read name tag`
+
+  > You used the word "tag" in a way that I don't understand.
+
+- **Expected:** These explicitly mentioned nouns should be recognized and redirect to the relevant descriptions.
+- **Reproduction:** In the Padded Cell, try the two commands above after reading the room and straitjacket descriptions.
+- **Regression Test:** `books/blackwood-horror/test/test-playtest-scenery.zil`
+- **Test Command:** `lua5.4 run-zil-test.lua books/blackwood-horror/test/test-playtest-scenery`
+- **Regression Status:** `PASS — both "writing" and "name tag" resolve to their authored responses`
+- **Severity:** Low
+
+### Bug 7: Mercy-ending prose leaves the relic in the wrong location
+
+- **Description:** The mercy ending says, “When the light fades, the relic lies on the floor,” but the relic remains in the player's inventory after Patient 189 is removed.
+- **Command:** `give relic to patient`
+- **Expected:** The relic should be moved to the Chapel floor as the ending prose states.
+- **Reproduction:** In the Chapel, carry the ancient relic and give it to Patient 189, then inspect the relic's location.
+- **Regression Test:** `books/blackwood-horror/test/test-playtest-give-relic.zil`
+- **Test Command:** `lua5.4 run-zil-test.lua books/blackwood-horror/test/test-playtest-give-relic`
+- **Regression Status:** `PASS — mercy prose, GAME-WON, patient removal, and the relic's Chapel-floor location all pass`
+- **Severity:** Low
+
+---
+
+## Successful Regression Checks
+
+- Bare `hello` retains stock Zork behavior and does not complete the ending.
+- `hello patient` retains stock Zork behavior and does not complete the ending.
+- `say hello` reaches Patient 189 and completes the prepared ending.
+- `ask patient about mordecai` works and has distinct first/repeat responses.
+- The treatment, identity, sanitarium, and chapel topics all work.
+- The chapel topic points clearly toward the wooden box.
+- `open box` automatically uses the carried scalpel and reveals the relic.
+- `give relic to patient` works and produces a complete mercy-resolution scene; it does not fail silently.
+- After the mercy resolution, the Chapel description updates to show that Patient 189 is gone and the oppressive presence has lifted.
+
+### Automated SAY HELLO verification
+
+- **Regression Test:** `books/blackwood-horror/test/test-playtest-say-ending.zil`
+- **Test Command:** `lua5.4 run-zil-test.lua books/blackwood-horror/test/test-playtest-say-ending`
+- **Regression Status:** `PASS — bare HELLO variants do not win; SAY HELLO produces the distinctive "I remember... who I was" prose, sets GAME-WON, removes Patient 189, and leaves the player in the post-ending Chapel`
+- **Load-order note:** Every Blackwood test inserts `books/blackwood-horror/blackwood-horror.zil` itself, matching production. Blackwood does not redefine or route `V-HELLO`; it adds the content-local `SAY HELLO` phrase and `V-SAY-HELLO` action.
+
+### Additional review regressions
+
+- `books/blackwood-horror/test/test-playtest-lore.zil` verifies that taking the patient file or straitjacket before examining it no longer suppresses lore discovery.
+- The same test verifies both sides of the mirror-reflection transition at zero and positive lore.
+- All isolated tests contain comments preserving the exact organic command and bad output/state that motivated the synthetic setup.
+
+## Implemented recommendations
+
+1. The safe key no longer shares the misleading `SMALL` adjective with the brass key.
+2. `something` resolves to Patient 189, and Chapel prose supplies a restrained conversational cue.
+3. The drawing and filing cabinets are represented; blood writing and name tag vocabulary are recognized.
+4. The gate plaque is fixed in place with bespoke refusal prose.
+5. The mercy ending moves the ancient relic to the Chapel floor.
+
+---
+
+*Report generated by game tester agent*
diff --git a/books/blackwood-horror/IMPROVEMENTS.md b/books/blackwood-horror/IMPROVEMENTS.md
index ed69a77..33c2120 100644
--- a/books/blackwood-horror/IMPROVEMENTS.md
+++ b/books/blackwood-horror/IMPROVEMENTS.md
@@ -63,10 +63,10 @@ This doesn't change the game's mechanics — it recontextualizes the player's mo
 
 ### 5. Earned Ending — Serum + Syringe + Relic
 
-**Why:** Saying "hello" to win is anticlimactic. The game has STRANGE-SERUM, SYRINGE, and ANCIENT-RELIC as objects but no purpose for two of them.
+**Why:** A bare `HELLO` action as the win trigger is anticlimactic and collides with Zork's generic greeting behavior. The game has STRANGE-SERUM, SYRINGE, and ANCIENT-RELIC as objects but no purpose for two of them.
 
 **What:**
-Replace `<VERB? HELLO>` win condition in PATIENT-189-F:
+Use the explicit `SAY HELLO` phrase for the win condition, leaving the standard `HELLO` action unchanged:
 - If player lacks ANCIENT-RELIC: "Patient 189 tilts its head. Green light flares in its eyes. Something cold reaches into your chest. You are not ready."
 - If player has relic but not serum+syringe: "The relic glows warm. Patient 189 shivers, eyes flickering. But something still binds it. The serum — if returned to its source..."
 - If player has all three: Multi-line victory text. Inject the serum. The green light dies. Patient 189 looks at you with human eyes and whispers 'I remember who I was.' It crumbles to ash. The candles go out. You're free.
@@ -194,6 +194,251 @@ The parser will report the first syntax error with a line number.
 
 ---
 
+---
+
+### 11. Parser Depth — Pronouns, Disambiguation, GWIM, OOPS
+
+**Why:** The substrate handles basic TAKE/OPEN/LOOK, but players who type `TAKE ALL`, `DROP IT`, or mistype a word will hit unhandled responses. The Lurking Horror has 1700 lines of custom parser code handling pronouns (IT/HIM), GWIM defaults, OOPS correction, ALL/EXCEPT clauses, and disambiguation prompts.
+
+**What:**
+- Add pronoun tracking in action routines using `THIS-IS-IT`: after any `TELL` mentioning an object, bind `IT` to it: `<THIS-IS-IT ,OBJECT-NAME>`
+- Support `ALL` and `ALL EXCEPT` for TAKE/DROP in the current room
+- Add GWIM handlers for common missing-object scenarios (EXAMINE with no object → default to room's most interesting feature)
+- Handle `OOPS` corrections with a global buffer of the last typed command
+- Add disambiguation: when two objects in scope share a synonym, prompt the player to clarify
+
+**Implementation** (example pronoun binding):
+```zil
+<ROUTINE LENS-F ()
+    <COND (<VERB? EXAMINE>
+           <TELL "The lens is magnificent but dark." CR>
+           <THIS-IS-IT ,FRESNEL-LENS>   ; now "take it" works
+           <RTRUE>)>>
+```
+
+---
+
+### 12. NPC Autonomy — Movement, Dialogue Trees, Behavior Loops
+
+**Why:** Patient 189 is static — never moves, never changes behavior autonomously. The Lurking Horror's hacker wanders, helps, and gets corrupted; its urchin uses A*-like pathfinding across the entire map; its flier approaches in 5 escalating stages. These NPCs feel alive because they act independently.
+
+**What:**
+- Give Patient 189 a movement routine that patrols the chapel area
+- Add a multi-stage help/awareness sequence (stage 1: unaware, stage 2: curious, stage 3: responsive, stage 4: hostile or grateful based on player actions)
+- Implement topic-based dialogue with ASK/TELL (not just EXAMINE and win): backstory, fear, the sanitarium, Mordecai
+- Add a corruption arc: if the player brings the relic too early or attacks Patient 189, it changes behavior
+
+**Implementation** (autonomous NPC movement):
+```zil
+<ROUTINE I-PATIENT-MOVE ()
+    <COND (<EQUAL? ,HERE ,CHAPEL ,CHAPEL-ANTECHAMBER ,GARDEN>
+           ; 30% chance to move to adjacent room
+           <COND (<==? <RANDOM 3> 1>
+                  <COND (<EQUAL? <LOC ,PATIENT-189> ,CHAPEL>
+                         <MOVE ,PATIENT-189 ,CHAPEL-ANTECHAMBER>)
+                        (T
+                         <MOVE ,PATIENT-189 ,CHAPEL>)>)>)>
+    <RTRUE>>
+```
+Queue at interval 5 in GO.
+
+---
+
+### 13. Sound System — Audio Events for Key Moments
+
+**Why:** The Lurking Horror has 14 distinct sound IDs with volume control — footsteps, slime, wind, the flier's approach. Sound is a critical horror tool. Blackwood has none.
+
+**What:**
+- Add sound constants for key atmospheric moments
+- Trigger sounds on room entry, clock events, puzzle solutions, and NPC encounters
+- Room descriptions should imply sounds the player "hears" through text
+
+**Implementation additions:**
+```lua
+-- Sound IDs (added to engine if not present):
+SOUND_WIND = 1
+SOUND_FOOTSTEPS = 2
+SOUND_WHISPER = 3
+SOUND_HEARTBEAT = 4
+```
+Queue audio triggers alongside atmospheric text:
+```zil
+<ROUTINE I-FOOTSTEPS ()
+    <COND (<EQUAL? ,HERE ,OPERATING-THEATER ,PATIENT-WARD ,ELECTROSHOCK-THEATER>
+           <TELL "Slow footsteps echo from somewhere above." CR>
+           ; <PLAY-SOUND ,SOUND-FOOTSTEPS>  ; engine extension needed
+           )>
+    <RTRUE>>
+```
+
+---
+
+### 14. Unique Death Messages — Every Death a Discovery
+
+**Why:** The Lurking Horror has unique death text for every fatality — freezing, electrocution, slime, the flier, the urchin, the mass, the FROB. Each is a piece of characterful writing. Blackwood has no death system at all — the game simply ends when the player wins.
+
+**What:**
+- Add death states for environmental hazards: falling into the flooded pit, freezing in the morgue, being attacked by Patient 189
+- Each death gets unique, evocative text
+- Add a death clock: staying in the morgue too long, touching certain objects without protection, failing the serum injection
+
+**Examples:**
+- Freezing in morgue: "The cold seeps through your clothes, your skin, your bones. The tiles feel almost warm now. That's how you know it's too late."
+- Patient-189 attack: "Its hands close around your throat. Up close, you see your own eyes reflected in its. They're the last thing you see."
+- Flooded basement: "The water is black and cold. You gasp, swallow, and the boiler room ceiling fades above you."
+
+---
+
+### 15. Progressive Hints — Tiered Attention/Direction/Action/Command
+
+**Why:** The current `V-HINTS` outputs a single state-dependent message. The Lurking Horror doesn't have in-game hints, but Infocom's InvisiClues used a 4-tier system that let players choose how much help to receive. Modern games should do better.
+
+**What:**
+- Expand V-HINTS to a tiered system using a counter: first `HINTS` call → attention nudge, second → direction, third → specific action, fourth → exact command
+- Track which puzzles are unsolved and serve hints in priority order
+- Allow `HINTS <TOPIC>` for topic-specific guidance
+
+**Implementation:**
+```zil
+<GLOBAL HINT-LEVEL <>>
+<GLOBAL HINT-INDEX <>>
+
+<ROUTINE V-HINTS ()
+    <COND (<NOT ,STUDY-UNLOCKED>
+           <GET-HINT "study" 0
+               "The study door seems important."
+               "Mr. Hudson may know how to open it."
+               "Ask Hudson about the study key."
+               "ASK HUDSON ABOUT KEY")>
+          (<NOT ,CIPHER-SOLVED>
+           <GET-HINT "cipher" 1
+               "The library has a pattern to decode."
+               "Compare the torn page with the colored markers."
+               "Push the marked books in rainbow order."
+               "PUSH RED BOOK then YELLOW then GREEN then BLUE")>
+          ...)>
+```
+
+---
+
+### 16. Prose Tonal Range — Humor, Beauty, and Warmth in Horror
+
+**Why:** The Lurking Horror shifts between academic comedy ("Now you know why few technical schools make it to the Rose Bowl"), cosmic awe (the Yuggoth sequence), and body horror. Blackwood is uniformly grim — every room "reeks of decay," the walls are "covered in black mold," nothing is beautiful or funny. Without contrast, the horror desensitizes.
+
+**What:**
+- Add one moment of dark humor: a sardonic narrator comment, a silly object (a rubber chicken in the cafeteria, a "Employee of the Month" photo with increasingly deranged captions)
+- Add one moment of beauty: a moonlit view from the observation deck, a single wildflower growing through a crack in the boiler room floor
+- Add one moment of warmth (made hollow by context): a preserved staff photograph showing happy people, a child's drawing pinned to a wall
+- Remove at least half of the "reek of decay" / "oppressive dread" / "feels wrong" phrases and replace with concrete sensory detail
+
+**Examples:**
+
+> (Beauty) "Through the grime-caked window, moonlight paints the garden in silver. A single white rose has forced its way through a crack in the stone wall."
+>
+> (Dark humor) "A yellowed certificate reads 'Gordon Ashworth — Employee of the Month, March 1952.' Someone has drawn a mustache on every face with what appears to be dried blood."
+>
+> (Warmth) "A child's crayon drawing is taped to the wall — a crude house with a smiling figure labeled 'DR ASHWORTH' and another labeled 'ME.' It would be sweet if you didn't know what happened here."
+
+---
+
+### 17. Clock-Driven Gameplay — Mechanical Systems, Not Just Atmosphere
+
+**Why:** The Lurking Horror's clock system drives real mechanical consequences: the flashlight dims across 5 stages (FRESH, DIM, VERY-DIM, ALMOST-GONE, OUT), the Chinese food cools and becomes less appealing, the player freezes if outside too long, NPCs move on schedules. Blackwood's clock routines (I-WHISPER, I-CREAKING) are purely cosmetic — they fire flavor text that never interacts with game state.
+
+**What:**
+- Add a mechanical cold system: staying in the morgue or basement too long progressively impairs the player, with early warnings before death
+- Add a light-source drain: if the player finds a flashlight or lantern, it runs out of battery after N turns
+- Add an NPC scheduling system: Patient 189 moves between CHAPEL, GARDEN, and CHAPEL-ANTECHAMBER on a timer, changing which rooms are accessible
+- Add object temperature tracking: the boiler can be lit to warm surrounding rooms, affecting the cold system
+
+**Implementation** (cold system):
+```zil
+<GLOBAL COLD-TIMER 0>
+<GLOBAL PLAYER-SHIMMERING <>>
+
+<ROUTINE I-COLD ()
+    <COND (<EQUAL? ,HERE ,MORGUE ,BASEMENT-CORRIDOR ,BOILER-ROOM ,FLOODED-CHAMBER>
+           <SETG COLD-TIMER <+ ,COLD-TIMER 1>>
+           <COND (<EQUAL? ,COLD-TIMER 3>
+                  <TELL "You shiver. It's getting colder." CR>)
+                 (<EQUAL? ,COLD-TIMER 6>
+                  <TELL "Your teeth chatter uncontrollably. Your fingers are going numb." CR>)
+                 (<EQUAL? ,COLD-TIMER 9>
+                  <TELL "The cold is unbearable. Your vision blurs." CR>)
+                 (<EQUAL? ,COLD-TIMER 12>
+                  <TELL "You collapse. The cold takes you." CR>
+                  ; death sequence
+                  )>)>
+    <RTRUE>>
+```
+
+---
+
+### 18. Object Interaction Depth — Tool Chains and State Combinations
+
+**Why:** In the Lurking Horror, puzzles require chaining multiple objects in specific ways: use liquid nitrogen to freeze slime → shatter frozen slime → reveal ancient door. Or: find Chinese food → heat in microwave (2 min, HIGH) → give to hacker → get master key. Blackwood's puzzles max out at "use scalpel on chains" and "use key on door."
+
+**What:**
+- Add at least one multi-step tool chain: e.g., find empty bottle → fill at water fountain → pour on floor → freeze room with open window → slip across to unreachable area
+- Add object state combinations: e.g., turn on boiler → heats radiator in hydrotherapy room → thaws frozen drawer → reveals second serum vial
+- Add object-with-object puzzles that require correct ordering: e.g., mix cleaning fluid (find cabinet) + combine with powder (find storage) → create acid → dissolve chapel lock
+
+**Example** (boiler chain):
+```zil
+<ROUTINE BOILER-F ()
+    <COND (<VERB? LAMP-ON TURN>
+           <COND (<FSET? ,BOILER ,ONBIT>
+                  <TELL "The boiler is already roaring." CR>)
+                 (<NOT <IN? ,COAL-SCOOP ,WINNER>>
+                  <TELL "You need fuel to light the boiler." CR>)
+                 (T
+                  <TELL "You shovel coal into the boiler and light it. Soon a deep rumble fills the room." CR>
+                  <FSET ,BOILER ,ONBIT>
+                  <SETG BOILER-MINUTES 0>)>
+           <RTRUE>)>>
+
+; Clock daemon: boiler heats adjacent rooms
+<ROUTINE I-BOILER-HEAT ()
+    <COND (<AND <FSET? ,BOILER ,ONBIT>
+                 <EQUAL? ,HERE ,BASEMENT-CORRIDOR ,HYDROTHERAPY>>
+           <SETG BOILER-MINUTES <+ ,BOILER-MINUTES 1>>
+           <COND (<AND <EQUAL? ,BOILER-MINUTES 3>
+                       <NOT ,RADIATOR-WARM>>
+                  <TELL "A pipe clanks. Warmth radiates from the wall." CR>
+                  <SETG RADIATOR-WARM T>)>)>
+    <RTRUE>>
+```
+
+---
+
+### 19. Verb Coverage — Expanding Beyond Standard Zork1 Verbs
+
+**Why:** The Lurking Horror defines 130+ verb syntaxes, including specialized actions like DIG, COMPARE, THROUGH, and TELL-ME-ABOUT. Blackwood uses only standard Zork1 verbs (~20). When the room description says "the safe is covered in frost" and the player types `SCRAPE FROST`, there's no response.
+
+**What:**
+- Add custom SYNTAX entries for verbs specific to the sanitarium setting: SCRAPE, INJECT, PUT-ON, PULL (as V-MOVE)
+- Add responses for verbs implied by object descriptions: SMELL for "reeking", POUR for "liquid", PUSH for "heavy", RUB for "stained"
+- Add at least 5-8 non-standard verb handlers that produce in-world responses rather than generic failures
+
+**Implementation:**
+```zil
+<SYNTAX SCRAPE OBJECT = V-SCRAPE>
+<SYNTAX INJECT OBJECT WITH OBJECT (FIND TOOLBIT) = V-INJECT>
+
+<ROUTINE V-SCRAPE ()
+    <TELL "You scrape at the surface. Nothing yields." CR>
+    <RTRUE>>
+
+<ROUTINE V-INJECT ()
+    <COND (<AND <EQUAL? ,PRSI ,SYRINGE>
+                <EQUAL? ,PRSO ,PATIENT-189>
+                <IN? ,STRANGE-SERUM ,WINNER>>
+           ... injection logic ...
+           <RTRUE>)>>
+```
+
+---
+
 ## Implementation Order
 
 1. Add GLOBAL GAME-WON and WHISPER-TABLE globals
@@ -209,5 +454,12 @@ The parser will report the first syntax error with a line number.
 11. Add PSEUDO to RECEPTION-ROOM
 12. Add VALUE to rooms (MORGUE, ISOLATION-WARD, PADDED-CELL, ELECTROSHOCK-THEATER, CHAPEL)
 13. Replace CHAPEL LDESC with ACTION CHAPEL-FCN + M-LOOK handler
-14. Update walkthrough test to match new win condition
-15. Run test, fix any parse/logic errors
+14. Add pronoun tracking (THIS-IS-IT) to key object routines (Section 11)
+15. Add I-PATIENT-MOVE clock routine for NPC autonomy (Section 12)
+16. Add unique death states and I-COLD mechanical clock (Sections 14, 17)
+17. Add multi-step tool chain (boiler → heat → thaw drawer) (Section 18)
+18. Add custom SYNTAX entries for SCRAPE, INJECT, and other specialized verbs (Section 19)
+19. Revise prose across 5-8 rooms for tonal range (Section 16)
+20. Expand V-HINTS to tiered progressive system (Section 15)
+21. Update walkthrough test to match new win condition
+22. Run test, fix any parse/logic errors
diff --git a/books/blackwood-horror/actions.zil b/books/blackwood-horror/actions.zil
index 2f15d5e..aa146d0 100644
--- a/books/blackwood-horror/actions.zil
+++ b/books/blackwood-horror/actions.zil
@@ -37,6 +37,26 @@
                   <TELL " Steam hisses from the pipes overhead, filling the corridor with an acrid mist.">)>
            <TELL " To the east, a passage leads toward the sound of dripping water. West lies what might have been storage. North, another corridor descends toward deeper chambers." CR>)>>
 
+<ROUTINE BOILER-ROOM-FCN (RARG)
+    <COND (<EQUAL? .RARG ,M-LOOK>
+           <TELL "Coal dust softens every edge in this low brick chamber. A massive boiler occupies the far wall, with an iron coal bin beside it.">
+           <COND (,BOILER-LIT
+                  <TELL " The boiler is awake now: fire mutters behind its door and the pipes knock with gathering heat.">)
+                 (,BOILER-FUELED
+                  <TELL " Coal lies ready in the firebox, waiting for a flame.">)
+                 (T
+                  <TELL " The boiler is cold and silent.">)>
+           <TELL " A narrow doorway leads west." CR>)>>
+
+<ROUTINE HYDROTHERAPY-ROOM-FCN (RARG)
+    <COND (<EQUAL? .RARG ,M-LOOK>
+           <TELL "Rubber hoses dangle from fixtures above cracked porcelain tubs. A doorway west opens into the flooded chamber.">
+           <COND (,CABINET-THAWED
+                  <TELL " Water beads on the medicine cabinet where its coat of frost has melted.">)
+                 (T
+                  <TELL " A medicine cabinet on the far wall is sealed beneath thick white frost.">)>
+           <TELL CR>)>>
+
 <ROUTINE FLOODING-CHAMBER-FCN (RARG)
     <COND (<EQUAL? .RARG ,M-LOOK>
            <TELL "The chamber is vast and dark, with arched stone ceilings disappearing into shadow.">
@@ -53,6 +73,8 @@
                   <TELL " The chapel door stands open, darkness visible beyond.">)
                  (T
                   <TELL " The chapel door is secured with a heavy iron lock.">)>
+           <COND (<IN? ,PATIENT-189 ,OVERGROWN-GARDEN>
+                  <TELL " Patient 189 stands among the dead roses, head tilted toward the chapel.">)>
            <TELL CR "South returns to the cafeteria." CR>)>>
 
 <ROUTINE DIRECTORS-OFFICE-FCN (RARG)
@@ -62,38 +84,49 @@
                   <TELL " A wall safe is visible behind a moved painting.">)
                  (<FSET? ,MORDECAI-PORTRAIT ,TOUCHBIT>
                   <TELL " A portrait of Dr. Mordecai hangs slightly askew on the wall.">)>
-           <TELL " A door to the west opens back to the administrative wing corridor." CR>)>>
+           <TELL CR>)>>
 
 ; === ACTION HANDLERS ===
 
-<ROUTINE DESK-F ()
-         <COND (<VERB? EXAMINE LOOK-INSIDE>
-                <TELL "The desk has three drawers. The top two are broken and empty. The bottom drawer is intact but locked." CR>
+<SYNTAX SAY HELLO = V-SAY-HELLO>
+<SYNTAX HINT = V-HINTS>
+<SYNONYM HINT HINTS>
+<SYNTAX SCRAPE OBJECT = V-SCRAPE>
+<SYNTAX SCRAPE OBJECT WITH OBJECT = V-SCRAPE>
+<SYNTAX INJECT OBJECT WITH OBJECT = V-INJECT>
+<SYNTAX KINDLE OBJECT WITH OBJECT = V-IGNITE>
+
+<ROUTINE BRASS-PLAQUE-F ()
+         <COND (<VERB? TAKE PULL>
+                <TELL "The plaque is bolted firmly to the iron gate." CR>
                 <RTRUE>)>>
 
-<ROUTINE DESK-DRAWER-F ()
-         <COND (<AND <VERB? EXAMINE>
-                     <NOT <FSET? ,DESK-DRAWER ,OPENBIT>>>
-                <TELL "The bottom drawer of the desk is locked. The keyhole has the number '3' engraved beside it." CR>
-                <RTRUE>)
-               (<AND <VERB? EXAMINE>
-                     <FSET? ,DESK-DRAWER ,OPENBIT>>
-                <TELL "The drawer is open. " <COND (<IN? ,PATIENT-FILE ,DESK-DRAWER> <TELL "Inside is a file folder.">)(<ELSE> <TELL "It's empty now.">)> CR>
-                <RTRUE>)
-               (<AND <VERB? OPEN UNLOCK>
-                     <NOT <FSET? ,DESK-DRAWER ,OPENBIT>>
-                     <NOT <IN? ,BRASS-KEY ,WINNER>>>
-                <TELL "The drawer is locked. You need a key with the number '3' on it." CR>
+<ROUTINE CHILD-DRAWING-F ()
+         <COND (<VERB? EXAMINE READ>
+                <TELL "A child's crayon drawing is pinned to the bedframe: a yellow sun above a stick figure with outstretched arms, and the word 'HOME' pressed so hard into the paper that the crayon tore through in places." CR>
                 <RTRUE>)
-               (<AND <VERB? OPEN UNLOCK>
-                     <NOT <FSET? ,DESK-DRAWER ,OPENBIT>>
-                     <IN? ,BRASS-KEY ,WINNER>>
-                <TELL "You insert the brass key into the lock. It turns smoothly. The drawer slides open, revealing an old file folder inside." CR>
-                <FSET ,DESK-DRAWER ,OPENBIT>
+               (<VERB? TAKE PULL>
+                <TELL "The brittle paper would crumble if you tried to remove it from the rusted pin." CR>
+                <RTRUE>)>>
+
+<ROUTINE FILING-CABINETS-F ()
+         <COND (<VERB? EXAMINE SEARCH LOOK-INSIDE OPEN>
+                <COND (<EQUAL? ,HERE ,RECEPTION-ROOM>
+                       <TELL "The reception cabinets stand open and empty. Their labels have faded, and damp has fused the remaining scraps of paper into gray pulp." CR>)
+                      (T
+                       <TELL "The overturned cabinets have been emptied. Bent drawers gape open among waterlogged administrative forms." CR>)>
+                <RTRUE>)>>
+
+<ROUTINE DESK-F ()
+         <COND (<VERB? EXAMINE LOOK-INSIDE>
+                <TELL "The desk has three drawers. The top two are broken and empty. The bottom drawer is intact but locked." CR>
                 <RTRUE>)>>
 
 <ROUTINE PATIENT-FILE-F ()
          <COND (<VERB? READ EXAMINE>
+                <COND (<NOT ,PATIENT-FILE-LORE>
+                       <SETG PATIENT-FILE-LORE T>
+                       <SETG PATIENT-LORE <+ ,PATIENT-LORE 1>>)>
                 <TELL "A file folder labeled 'Patient 189 - CONFIDENTIAL'. Inside are medical records and notes. 'Subject shows extraordinary resistance to pain. Mental state deteriorating. Recommending transfer to isolation wing. Dr. Mordecai has expressed personal interest in this case. Update: Patient transferred to chapel for experimental treatment. Nov 1, 1952.'" CR>
                 <RTRUE>)>>
 
@@ -127,12 +160,12 @@
                      <NOT ,CHAINS-CUT-FLAG>>
                 <TELL "Thick iron chains wrap around the door handles, secured with a massive rusted padlock. The chains look old but still strong." CR>
                 <RTRUE>)
-               (<AND <VERB? ATTACK>
+               (<AND <VERB? ATTACK CUT>
                      <NOT ,CHAINS-CUT-FLAG>
                      <NOT <IN? ,SCALPEL ,WINNER>>>
                 <TELL "The chains are too strong to break with your bare hands. You need a sharp tool." CR>
                 <RTRUE>)
-               (<AND <VERB? ATTACK>
+               (<AND <VERB? ATTACK CUT>
                      <NOT ,CHAINS-CUT-FLAG>
                      <IN? ,SCALPEL ,WINNER>>
                 <TELL "You saw through the rusty chains with the " D ,SCALPEL ". It takes several minutes of effort, but finally they fall away with a crash. The heavy door creaks open, revealing a passage north into darkness." CR>
@@ -176,7 +209,66 @@
 
 <ROUTINE BOILER-F ()
          <COND (<VERB? EXAMINE LOOK-INSIDE>
-                <TELL "The boiler is a hulking iron beast. Its door hangs open, revealing a chamber black with ancient soot. Inside, something gleams faintly." CR>
+                <COND (,BOILER-LIT
+                       <TELL "The boiler roars with renewed life. Its pressure needle trembles in the yellow band, and heat pulses through the pipes toward the flooded wing." CR>)
+                      (,BOILER-FUELED
+                       <TELL "The boiler's open firebox contains fresh coal. It needs a steady flame to catch." CR>)
+                      (T
+                       <TELL "The boiler is a hulking iron beast. Its open firebox is black with soot and empty of usable fuel." CR>)>
+                <RTRUE>)
+               (<AND <VERB? BURN>
+                     ,BOILER-LIT>
+                <TELL "The boiler is already burning steadily." CR>
+                <RTRUE>)
+               (<AND <VERB? BURN>
+                     <NOT ,BOILER-FUELED>>
+                <TELL "A flame alone will not wake it. The firebox needs coal." CR>
+                <RTRUE>)
+               (<AND <VERB? BURN>
+                     <NOT <EQUAL? ,PRSI ,OIL-LANTERN>>>
+                <TELL "You need a sustained flame, not a momentary spark." CR>
+                <RTRUE>)
+               (<AND <VERB? BURN>
+                     <NOT ,LANTERN-LIT-FLAG>>
+                <TELL "The lantern must be lit before it can kindle the coal." CR>
+                <RTRUE>)
+               (<VERB? BURN>
+                <TELL "You hold the lantern flame to the coal. Smoke rolls from the firebox; then orange light catches underneath. The boiler answers with a deep metallic thud as water begins moving through long-dead pipes." CR>
+                <SETG BOILER-LIT T>
+                <SETG BOILER-HEAT 0>
+                <RTRUE>)
+               (<VERB? LAMP-ON>
+                <TELL "The boiler has no switch. It must be fueled and lit with a flame." CR>
+                <RTRUE>)>>
+
+<ROUTINE COAL-BIN-F ()
+         <COND (<VERB? EXAMINE LOOK-INSIDE SEARCH>
+                <COND (<IN? ,LUMP-OF-COAL ,COAL-BIN>
+                       <TELL "Most of the coal has collapsed into wet black dust, but one solid lump could still burn. A shovel would keep the filthy slack off your hands." CR>)
+                      (T
+                       <TELL "Only damp coal dust remains in the bin." CR>)>
+                <RTRUE>)>>
+
+<ROUTINE COAL-F ()
+         <COND (<AND <VERB? TAKE>
+                     <NOT <IN? ,COAL-SHOVEL ,WINNER>>>
+                <TELL "The coal lies beneath wet, oily slack. You need something broad enough to scoop it free." CR>
+                <RTRUE>)
+               (<VERB? TAKE>
+                <TELL "Using the shovel, you pry a solid lump from the compacted coal and take it." CR>
+                <MOVE ,LUMP-OF-COAL ,WINNER>
+                <RTRUE>)
+               (<AND <VERB? PUT>
+                     <EQUAL? ,PRSI ,IRON-BOILER>>
+                <COND (,BOILER-FUELED
+                       <TELL "The firebox already has enough coal." CR>)
+                      (T
+                       <TELL "You place the coal in the boiler's firebox." CR>
+                       <SETG BOILER-FUELED T>
+                       <MOVE ,LUMP-OF-COAL ,IRON-BOILER>)>
+                <RTRUE>)
+               (<VERB? EXAMINE>
+                <TELL "A dense lump of old bituminous coal, dirty but dry at its center." CR>
                 <RTRUE>)>>
 
 <ROUTINE WORKBENCH-F ()
@@ -253,8 +345,22 @@
                 <RTRUE>)>>
 
 <ROUTINE MEDICINE-CABINET-F ()
-         <COND (<VERB? EXAMINE LOOK-INSIDE>
-                <TELL "The cabinet contains old medical supplies. Most are ruined, but a syringe and bandages remain usable." CR>
+         <COND (<AND <VERB? EXAMINE LOOK-INSIDE>
+                     <NOT ,CABINET-THAWED>>
+                <TELL "Frost has welded the medicine cabinet shut. Through the clouded glass you can just make out a syringe. Scraping removes only powder before the ice hardens again; the pipes behind the wall would have to warm." CR>
+                <RTRUE>)
+               (<VERB? EXAMINE LOOK-INSIDE>
+                <TELL "Meltwater runs down the cabinet door. Inside, among ruined dressings, a glass syringe remains usable." CR>
+                <RTRUE>)
+               (<AND <VERB? OPEN>
+                     <NOT ,CABINET-THAWED>>
+                <TELL "The frost holds the door more firmly than any lock." CR>
+                <RTRUE>)
+               (<AND <VERB? OPEN>
+                     ,CABINET-THAWED
+                     <NOT <FSET? ,MEDICINE-CABINET ,OPENBIT>>>
+                <TELL "You pull the thawed cabinet open. Meltwater patters onto the tile." CR>
+                <FSET ,MEDICINE-CABINET ,OPENBIT>
                 <RTRUE>)>>
 
 <ROUTINE CELL-DOORS-F ()
@@ -270,7 +376,11 @@
                 <TELL "You run your fingers over the scratches. They're deep—gouged by fingernails over years of desperation." CR>
                 <RTRUE>)
                (<VERB? READ>
-                <TELL "Among the chaos of scratches, you can make out words: 'HELP ME' 'NO MORE' 'PLEASE'. The largest message reads: 'PATIENT 189 STILL ALIVE IN THE CHAPEL'. And then, in a corner you nearly missed — scratched in handwriting that looks disturbingly like your own: 'YOU ARE 189. YOU ALWAYS WERE.'" CR>
+                <TELL "Among the chaos of scratches, you can make out words: 'HELP ME' 'NO MORE' 'PLEASE'. The largest message reads: 'PATIENT 189 STILL ALIVE IN THE CHAPEL'.">
+                <TELL " And then, in a corner, smaller and more recent: the date '1947' and a single word—'remember'—carved with unusual precision." CR>
+                <COND (<NOT ,WALL-SCRATCHES-LORE>
+                       <SETG WALL-SCRATCHES-LORE T>
+                       <SETG PATIENT-LORE <+ ,PATIENT-LORE 1>>)>
                 <RTRUE>)>>
 
 <ROUTINE SHOCK-CHAIR-F ()
@@ -317,10 +427,17 @@
 
 <ROUTINE STRAITJACKET-F ()
          <COND (<VERB? EXAMINE>
-                <TELL "A heavy canvas straitjacket with multiple leather buckles and straps. Dark stains cover the fabric. And on the collar — a name tag. Your name. YOUR name is on this straitjacket." CR>
+                <TELL "A heavy canvas straitjacket with multiple leather buckles and straps. Dark stains cover the fabric. On the collar—a name tag, the ink nearly faded.">
+                <COND (<NOT ,STRAITJACKET-LORE>
+                       <SETG STRAITJACKET-LORE T>
+                       <SETG PATIENT-LORE <+ ,PATIENT-LORE 1>>
+                       <TELL " You can make out a few letters, a date. The handwriting seems... familiar.">)
+                      (T
+                       <TELL " The name on the tag is illegible now, but the date is clear: 1947.">)>
+                <TELL CR>
                 <RTRUE>)
                (<VERB? READ>
-                <TELL "The tag reads a name you know. Your name. Dated 1947. Five years before the sanitarium closed." CR>
+                <TELL "The tag reads a name—the ink is smeared, but the date is unmistakable. 1947. Five years before the sanitarium closed. You stare at it longer than you meant to." CR>
                 <RTRUE>)
                (<VERB? WEAR>
                 <TELL "You'd rather not." CR>
@@ -334,7 +451,11 @@
 
 <ROUTINE MIRROR-F ()
          <COND (<VERB? EXAMINE LOOK-INSIDE>
-                <TELL "Through the mirror, you can see the electroshock theater below. The shock chair sits in the center like a throne of suffering." CR>
+                <COND (<G? ,PATIENT-LORE 0>
+                       <TELL "Through the mirror, you can see the electroshock theater below. The shock chair sits in the center.">
+                       <TELL " In the glass, your reflection is barely visible—a dark shape that seems to shift when you try to focus on it. You look away." CR>)
+                      (T
+                       <TELL "Through the mirror, you can see the electroshock theater below. The shock chair sits in the center like a throne of suffering." CR>)>
                 <RTRUE>)>>
 
 <ROUTINE OBSERVATION-LOGBOOK-F ()
@@ -499,12 +620,140 @@
                 <TELL "You press your ear against the door. From within comes a faint sound—breathing? Or just the wind?" CR>
                 <RTRUE>)>>
 
+<ROUTINE PATIENT-189-RESOLUTION-F ()
+    <COND (<AND <IN? ,ANCIENT-RELIC ,WINNER>
+                <IN? ,STRANGE-SERUM ,WINNER>
+                <IN? ,SYRINGE ,WINNER>>
+           <TELL "You hold out the relic. Patient 189 stills completely. You draw the serum into the syringe and step forward—every instinct screaming—and inject it." CR>
+           <TELL "The green light in its eyes gutters. Patient 189 shudders, mouth opening in a soundless cry. The green flames around the chapel gutter and die." CR>
+           <TELL "Then it speaks, in a voice like someone remembering how: 'I remember... who I was.'" CR>
+           <COND (<G? ,PATIENT-LORE 2>
+                  <TELL " It looks at you with recognition—not as a stranger, but as someone who understands what it endured." CR>)
+                 (T
+                  <TELL " Its eyes pass over you without recognition. You freed it, but it never knew you." CR>)>
+           <TELL "It crumbles to ash. The candles go out. The air suddenly smells like rain and grass—ordinary, living air. You're free." CR>
+           <SETG GAME-WON T>
+           <SETG PATIENT-STATE 3>
+           <REMOVE ,PATIENT-189>
+           <RTRUE>)
+          (<IN? ,ANCIENT-RELIC ,WINNER>
+           <TELL "The relic glows warm. Patient 189 shivers, eyes flickering. But something still binds it. The serum—if returned to its source..." CR>
+           <RTRUE>)
+          (<G? ,PATIENT-STATE 1>
+           <TELL "Patient 189 acknowledges you—a slight inclination of the head. But words alone won't end this. You need the means to free it." CR>
+           <RTRUE>)
+          (T
+           <TELL "Patient 189 tilts its head. Green light flares in its eyes. Something cold reaches into your chest. You are not ready." CR>
+           <RTRUE>)>>
+
+<ROUTINE SHOW-HINT (KEY ATTENTION DIRECTION ACTION COMMAND)
+    <COND (<EQUAL? ,HINT-KEY .KEY>
+           <COND (<L? ,HINT-LEVEL 4>
+                  <SETG HINT-LEVEL <+ ,HINT-LEVEL 1>>)>)
+          (T
+           <SETG HINT-KEY .KEY>
+           <SETG HINT-LEVEL 1>)>
+    <COND (<EQUAL? ,HINT-LEVEL 1> <TELL .ATTENTION CR>)
+          (<EQUAL? ,HINT-LEVEL 2> <TELL .DIRECTION CR>)
+          (<EQUAL? ,HINT-LEVEL 3> <TELL .ACTION CR>)
+          (T <TELL .COMMAND CR>)>
+    <RTRUE>>
+
+<ROUTINE V-HINTS ()
+    <COND (<NOT ,CHAINS-CUT-FLAG>
+           <SHOW-HINT 1
+              "The chained morgue door is meant to be opened."
+              "The operating theater contains a cutting instrument."
+              "Take the scalpel and use it on the chains."
+              "ATTACK CHAINS WITH SCALPEL">)
+          (<NOT ,VALVE-TURNED-FLAG>
+           <SHOW-HINT 2
+              "The sealed eastern door needs more than muscle."
+              "Follow the basement pipes back toward their valve."
+              "Open the valve in the basement corridor to release steam."
+              "TURN VALVE">)
+          (<NOT ,CABINET-THAWED>
+           <SHOW-HINT 3
+              "The syringe is visible, but the frozen cabinet will not open."
+              "The boiler-room pipes run toward hydrotherapy."
+              "Use the shovel to recover coal, put it in the boiler, then kindle it with the lit lantern."
+              "TAKE SHOVEL; TAKE COAL; PUT COAL IN BOILER; LIGHT LANTERN; KINDLE BOILER WITH LANTERN; WAIT">)
+          (<NOT ,CHAPEL-UNLOCKED>
+           <SHOW-HINT 4
+              "The chapel key was kept somewhere only Mordecai could reach."
+              "Search the director's office carefully."
+              "A conspicuous book hides the safe key; the safe contains the chapel key."
+              "OPEN BOOK; TAKE SAFE KEY; UNLOCK SAFE WITH SAFE KEY; TAKE CHAPEL KEY">)
+          (<NOT <FSET? ,WOODEN-BOX ,OPENBIT>>
+           <SHOW-HINT 5
+              "Patient 189 keeps looking toward the altar."
+              "Examine the wooden box beneath it."
+              "The scalpel can pry the rusted clasp apart."
+              "OPEN BOX">)
+          (<NOT ,GAME-WON>
+           <SHOW-HINT 6
+              "Three objects connect Mordecai's experiment to Patient 189."
+              "You need the relic, the serum, and the syringe."
+              "Carry all three to Patient 189 and use the syringe."
+              "INJECT PATIENT WITH SYRINGE">)
+          (T
+           <TELL "The ordinary night air is answer enough." CR>)>>
+
+<ROUTINE V-SCRAPE ()
+    <COND (<EQUAL? ,PRSO ,MEDICINE-CABINET>
+           <COND (,CABINET-THAWED
+                  <TELL "The remaining frost wipes away beneath your fingers." CR>)
+                 (T
+                  <TELL "You scrape away a patch of frost, but new crystals creep across the exposed metal almost immediately. The cabinet needs sustained heat." CR>)>)
+          (T
+           <TELL "Scraping it accomplishes nothing." CR>)>
+    <RTRUE>>
+
+<ROUTINE V-INJECT ()
+    <COND (<NOT <EQUAL? ,PRSI ,SYRINGE>>
+           <TELL "That is not suitable for an injection." CR>)
+          (<NOT <EQUAL? ,PRSO ,PATIENT-189>>
+           <TELL "You have no reason to inject " THE ,PRSO "." CR>)
+          (<NOT <IN? ,SYRINGE ,WINNER>>
+           <TELL "You need to be holding the syringe." CR>)
+          (T
+           <PATIENT-189-RESOLUTION-F>)>
+    <RTRUE>>
+
+<ROUTINE V-IGNITE ()
+    <COND (<NOT <EQUAL? ,PRSO ,IRON-BOILER>>
+           <TELL "You cannot safely ignite " THE ,PRSO "." CR>)
+          (<NOT <EQUAL? ,PRSI ,OIL-LANTERN>>
+           <TELL "That will not provide a steady flame." CR>)
+          (<NOT <OR ,BOILER-FUELED <IN? ,LUMP-OF-COAL ,IRON-BOILER>>>
+           <TELL "The boiler's firebox needs coal first." CR>)
+          (<NOT ,LANTERN-LIT-FLAG>
+           <TELL "The lantern must be lit first." CR>)
+          (,BOILER-LIT
+           <TELL "The boiler is already burning steadily." CR>)
+          (T
+           <TELL "You hold the lantern flame to the coal. Smoke rolls from the firebox; then orange light catches underneath. The boiler answers with a deep metallic thud as water begins moving through long-dead pipes." CR>
+           <SETG BOILER-FUELED T>
+           <SETG BOILER-LIT T>
+           <SETG BOILER-HEAT 0>)>
+    <RTRUE>>
+
+<ROUTINE V-SAY-HELLO ()
+    <COND (<AND <EQUAL? ,HERE ,CHAPEL>
+                <IN? ,PATIENT-189 ,CHAPEL>>
+           <PATIENT-189-RESOLUTION-F>)
+          (T
+           <TELL "Nothing happens." CR>)>>
+
 <ROUTINE CHAPEL-FCN (RARG)
     <COND (<EQUAL? .RARG ,M-LOOK>
            <COND (,GAME-WON
                   <TELL "The chapel is just a room now. The candles are dark. The altar is bare. Whatever was here is gone -- and so is whatever held you." CR>)
                  (T
-                  <TELL "The chapel is small and suffocating. Cold green light from unnatural candles makes everything look like a corpse. At the far end, before the altar, something stands perfectly still." CR>)>
+                  <TELL "The chapel is small and suffocating. Cold green light from unnatural candles makes everything look like a corpse. At the far end, before the altar, something stands perfectly still. You have the uneasy sense that it is waiting for you to speak.">
+                  <COND (<NOT ,PATIENT-STATE>
+                         <SETG PATIENT-STATE 1>)>
+                  <TELL CR>)>
            <RTRUE>)>>
 
 <ROUTINE PEWS-F ()
@@ -522,7 +771,17 @@
                 <RTRUE>)>>
 
 <ROUTINE GREEN-CANDLES-F ()
-         <COND (<VERB? EXAMINE>
+         <COND (,GAME-WON
+                <COND (<VERB? EXAMINE>
+                       <TELL "The candles are cold and dark now, their green glow extinguished forever. Ordinary wax, nothing more." CR>
+                       <RTRUE>)
+                      (<VERB? LAMP-OFF BLOW>
+                       <TELL "The candles are already dark. There's nothing to extinguish." CR>
+                       <RTRUE>)
+                      (<VERB? LAMP-ON>
+                       <TELL "The candles will never burn again." CR>
+                       <RTRUE>)>)
+               (<VERB? EXAMINE>
                 <TELL "The CANDLES burn with green flames that give off no heat. The light makes everything look diseased." CR>
                 <RTRUE>)
                (<VERB? LAMP-OFF>
@@ -573,43 +832,95 @@
                 <TELL "The cross seems too important to discard." CR>
                 <RTRUE>)
                (<VERB? GIVE>
-                <TELL "The cross seems too important to give away." CR>
-                <RTRUE>)>>
+                <COND (<EQUAL? ,PRSI ,PATIENT-189>
+                       <RFALSE>)
+                      (T
+                       <TELL "The cross seems too important to give away." CR>
+                       <RTRUE>)>)>>
 
 <ROUTINE PATIENT-189-F ()
          <COND (<VERB? EXAMINE>
-                <TELL "PATIENT 189 stands impossibly still. Its skin is pale as death, its eyes glowing faintly green. It watches you with an intelligence that is distinctly not human. Dr. Mordecai's greatest achievement—and greatest horror." CR>
-                <RTRUE>)
-               (<VERB? ATTACK KILL>
+                <TELL "PATIENT 189 stands impossibly still. Its skin is pale as death, its eyes glowing faintly green.">
+                <COND (<G? ,PATIENT-STATE 1>
+                       <TELL " Its gaze follows you now, tracking your movements with a terrible patience.">)
+                      (T
+                       <TELL " It watches you with an intelligence that is distinctly not human.">)>
+                <TELL CR>
+                <RTRUE>)
+               (<AND <VERB? TELL>
+                     <EQUAL? ,PRSI ,TOPIC-MORDECAI>>
+                <COND (<NOT <FSET? ,TOPIC-MORDECAI ,TOUCHBIT>>
+                       <FSET ,TOPIC-MORDECAI ,TOUCHBIT>
+                       <TELL "You speak the name. Patient 189's eyes flare, the green intensifying. Its jaw works soundlessly, as if trying to form words long forgotten." CR>
+                       <SETG PATIENT-LORE <+ ,PATIENT-LORE 1>>)
+                      (T
+                       <TELL "Patient 189 responds to the name again—a spasm, quickly suppressed, as if even remembering is painful." CR>)>
+                <SETG PATIENT-STATE 2>
+                <RTRUE>)
+               (<AND <VERB? TELL>
+                     <EQUAL? ,PRSI ,TOPIC-TREATMENT>>
+                <COND (<NOT <FSET? ,TOPIC-TREATMENT ,TOUCHBIT>>
+                       <FSET ,TOPIC-TREATMENT ,TOUCHBIT>
+                       <TELL "At the word, Patient 189 shudders. Its hands—claw-like, translucent—rise to its temples. You realize it is miming the electrode placement. A memory. A very bad one." CR>
+                       <SETG PATIENT-LORE <+ ,PATIENT-LORE 1>>)
+                      (T
+                       <TELL "Patient 189 lowers its hands slowly. Its expression never changes, but something in the tilt of its head conveys a bottomless weariness." CR>)>
+                <SETG PATIENT-STATE 2>
+                <RTRUE>)
+               (<AND <VERB? TELL>
+                     <EQUAL? ,PRSI ,TOPIC-IDENTITY>>
+                <COND (<NOT <FSET? ,TOPIC-IDENTITY ,TOUCHBIT>>
+                       <FSET ,TOPIC-IDENTITY ,TOUCHBIT>
+                       <TELL "Patient 189 stills completely. Its lips part. A sound emerges—not a word, but a tone, a single note held impossibly long like a tuning fork. It fades. Then, almost inaudibly: '...remember...'" CR>
+                       <SETG PATIENT-LORE <+ ,PATIENT-LORE 1>>)
+                      (T
+                       <TELL "Patient 189 watches you silently. Whatever it might have said is gone now, lost in years of isolation." CR>)>
+                <SETG PATIENT-STATE 2>
+                <RTRUE>)
+               (<AND <VERB? TELL>
+                     <EQUAL? ,PRSI ,TOPIC-SANITARIUM>>
+                <COND (<NOT <FSET? ,TOPIC-SANITARIUM ,TOUCHBIT>>
+                       <FSET ,TOPIC-SANITARIUM ,TOUCHBIT>
+                       <TELL "Patient 189 tilts its head toward the chapel ceiling, toward the building above. When it looks back at you, there is something new in those green eyes—a plea, perhaps. Or an accusation." CR>
+                       <SETG PATIENT-LORE <+ ,PATIENT-LORE 1>>)
+                      (T
+                       <TELL "Patient 189's gaze drifts upward, then returns to you. The silent exchange is complete: you both know what this place is." CR>)>
+                <SETG PATIENT-STATE 2>
+                <RTRUE>)
+               (<AND <VERB? TELL>
+                     <EQUAL? ,PRSI ,TOPIC-CHAPEL>>
+                <COND (<NOT <FSET? ,TOPIC-CHAPEL ,TOUCHBIT>>
+                       <FSET ,TOPIC-CHAPEL ,TOUCHBIT>
+                       <TELL "Patient 189 gestures—the first real movement you've seen—toward the altar, toward the wooden box beneath it. The meaning is clear: what lies in that box matters." CR>
+                       <SETG PATIENT-LORE <+ ,PATIENT-LORE 1>>)
+                      (T
+                       <TELL "Patient 189's eyes return to the altar. Whatever waits there, it has waited a very long time." CR>)>
+                <SETG PATIENT-STATE 2>
+                <RTRUE>)
+               (<AND <VERB? ATTACK KILL MUNG>
+                     <NOT ,GAME-WON>>
                 <TELL "You cannot bring yourself to approach it. Some primal instinct holds you back." CR>
                 <RTRUE>)
-               (<VERB? HELLO>
-                <COND (<NOT <IN? ,ANCIENT-RELIC ,WINNER>>
-                       <TELL "Patient 189 tilts its head. Green light flares in its eyes. Something cold reaches into your chest. You are not ready." CR>
-                       <RTRUE>)
-                      (<AND <IN? ,ANCIENT-RELIC ,WINNER>
-                            <OR <NOT <IN? ,STRANGE-SERUM ,WINNER>>
-                                <NOT <IN? ,SYRINGE ,WINNER>>>>
-                       <TELL "The relic glows warm. Patient 189 shivers, eyes flickering. But something still binds it. The serum—if returned to its source..." CR>
-                       <RTRUE>)
-                      (<AND <IN? ,ANCIENT-RELIC ,WINNER>
-                            <IN? ,STRANGE-SERUM ,WINNER>
-                            <IN? ,SYRINGE ,WINNER>>
-                       <TELL "You hold out the relic. Patient 189 stills completely. You draw the serum into the syringe and step forward—every instinct screaming—and inject it." CR>
-                       <TELL "The green light in its eyes gutters. Patient 189 shudders, mouth opening in a soundless cry. The green flames around the chapel gutter and die. Then it speaks, in a voice like someone remembering how: 'I remember... who I was.'" CR>
-                       <TELL "It crumbles to ash. The candles go out. The air suddenly smells like rain and grass—ordinary, living air. You're free." CR>
-                       <SETG GAME-WON T>
-                       <REMOVE ,PATIENT-189>
-                       <RTRUE>)>)
                (<VERB? RUB>
                 <TELL "You reach toward Patient 189, but stop yourself. The air around it feels wrong—cold and electric." CR>
                 <RTRUE>)
                (<VERB? GIVE>
-                <TELL "Patient 189 shows no interest in earthly possessions. It simply watches you with those glowing eyes." CR>
-                <RTRUE>)>>
+                <COND (<EQUAL? ,PRSO ,ANCIENT-RELIC>
+                       <PATIENT-189-RESOLUTION-F>)
+                      (T
+                       <TELL "Patient 189 shows no interest in that. It simply watches you with those glowing eyes." CR>
+                       <RTRUE>)>)>>
 
 <ROUTINE DRAWER-F ()
-         <COND (<AND <VERB? OPEN>
+         <COND (<AND <VERB? EXAMINE>
+                     <NOT <FSET? ,BOTTOM-DRAWER ,OPENBIT>>>
+                <TELL "The bottom drawer of the desk is locked. The keyhole has the number '3' engraved beside it." CR>
+                <RTRUE>)
+               (<AND <VERB? EXAMINE>
+                     <FSET? ,BOTTOM-DRAWER ,OPENBIT>>
+                <TELL "The drawer is open. Inside you can see a leather-bound ledger and a patient file." CR>
+                <RTRUE>)
+               (<AND <VERB? OPEN>
                      <FSET? ,BOTTOM-DRAWER ,OPENBIT>>
                 <TELL "The drawer is already open." CR>
                 <RTRUE>)
@@ -621,7 +932,7 @@
                (<AND <VERB? OPEN UNLOCK>
                      <NOT <FSET? ,BOTTOM-DRAWER ,OPENBIT>>
                      <IN? ,BRASS-KEY ,WINNER>>
-                <TELL "You unlock the " D ,BOTTOM-DRAWER " with the " D ,BRASS-KEY ". It slides open with a groan, revealing a leather-bound ledger inside." CR>
+                <TELL "You insert the brass key into the lock. It turns smoothly. The drawer slides open, revealing a leather-bound ledger and a patient file inside." CR>
                 <FCLEAR ,BOTTOM-DRAWER ,NDESCBIT>
                 <FSET ,BOTTOM-DRAWER ,OPENBIT>
                 <RTRUE>)>>
@@ -742,6 +1053,89 @@
                 <TELL "A medical syringe with a sharp steel needle. The glass chamber is empty." CR>
                 <RTRUE>)>>
 
+; === NEW DOOR ACTION HANDLERS ===
+
+<ROUTINE THEATER-DOOR-F ()
+         <COND (<VERB? EXAMINE>
+                <TELL "The door to the operating theater is half-open. Faint metallic sounds drift from beyond." CR>
+                <RTRUE>)
+               (<VERB? OPEN>
+                <TELL "The door is already half-open. You can walk through to the north." CR>
+                <RTRUE>)
+               (<VERB? CLOSE>
+                <TELL "You leave it half-open." CR>
+                <RTRUE>)>>
+
+<ROUTINE PADCELL-DOOR-F ()
+         <COND (<VERB? EXAMINE>
+                <TELL "A heavy steel door, its frame reinforced. It stands ajar, and you can make out a padded cell beyond." CR>
+                <RTRUE>)
+               (<VERB? OPEN>
+                <TELL "The door is already open. The padded cell lies to the west." CR>
+                <RTRUE>)
+               (<VERB? CLOSE>
+                <TELL "You leave it open." CR>
+                <RTRUE>)>>
+
+<ROUTINE CORRIDOR-DOOR-F ()
+         <COND (<VERB? EXAMINE>
+                <TELL "A heavy wooden door leading to the administrative wing. It hangs open, as if someone left in a hurry." CR>
+                <RTRUE>)
+               (<VERB? OPEN>
+                <TELL "The door is already open. The administrative wing lies to the north." CR>
+                <RTRUE>)
+               (<VERB? CLOSE>
+                <TELL "You leave it open." CR>
+                <RTRUE>)>>
+
+<ROUTINE OFFICE-DOOR-F ()
+         <COND (<VERB? EXAMINE>
+                <TELL "A heavy office door leading back to the administrative wing corridor." CR>
+                <RTRUE>)
+               (<VERB? OPEN>
+                <TELL "The door is already open. The corridor lies to the west." CR>
+                <RTRUE>)
+               (<VERB? CLOSE>
+                <TELL "You leave it open." CR>
+                <RTRUE>)>>
+
+<ROUTINE GARDEN-DOOR-F ()
+         <COND (<VERB? EXAMINE>
+                <TELL "A wooden door with a cracked window pane. Through it you can see the overgrown garden beyond." CR>
+                <RTRUE>)
+               (<VERB? OPEN>
+                <TELL "The door swings open. The garden lies to the north." CR>
+                <RTRUE>)
+               (<VERB? CLOSE>
+                <TELL "You leave it open." CR>
+                <RTRUE>)>>
+
+<ROUTINE ESCAPE-DOOR-F ()
+         <COND (<VERB? EXAMINE>
+                <TELL "A heavy door, solid and imposing from this side. It's the only way out of this cell." CR>
+                <RTRUE>)
+               (<VERB? OPEN>
+                <TELL "The door is already open. The electroshock theater lies to the east." CR>
+                <RTRUE>)
+               (<VERB? CLOSE>
+                <TELL "You'd rather not trap yourself in here." CR>
+                <RTRUE>)>>
+
+<ROUTINE INSTRUMENTS-PSEUDO ()
+    <COND (<VERB? EXAMINE>
+           <TELL "Rusty forceps, scalpels, and clamps lie scattered across trays. Long abandoned, like everything else here." CR>)>
+    <RTRUE>>
+
+<ROUTINE TRAYS-PSEUDO ()
+    <COND (<VERB? EXAMINE>
+           <TELL "Cold metal instrument trays sit on carts, their contents rusted and useless." CR>)>
+    <RTRUE>>
+
+<ROUTINE BENCHES-PSEUDO ()
+    <COND (<VERB? EXAMINE SIT>
+           <TELL "Tiers of wooden benches circle the operating theater, where students once observed procedures. The wood is dark with age and moisture." CR>)>
+    <RTRUE>>
+
 ; === LOCAL-GLOBALS ACTION HANDLERS ===
 
 <ROUTINE SANITARIUM-BUILDING-F ()
@@ -766,31 +1160,93 @@
 ; === CLOCK-DRIVEN ATMOSPHERIC ROUTINES ===
 
 <ROUTINE I-WHISPER ()
+	<QUEUE I-WHISPER 8>
 	<COND (<EQUAL? ,HERE ,SANITARIUM-ENTRANCE ,PATIENT-WARD ,MORGUE ,CHAPEL>
 	       <TELL <PICK-ONE ,WHISPER-TABLE> CR>)>
 	<RTRUE>>
 
 <ROUTINE I-FOOTSTEPS ()
+	<QUEUE I-FOOTSTEPS 12>
 	<COND (<EQUAL? ,HERE ,SANITARIUM-ENTRANCE ,RECEPTION-ROOM ,OPERATING-THEATER>
 	       <TELL "Distant footsteps echo from somewhere above you." CR>)>
 	<RTRUE>>
 
 <ROUTINE I-FLICKERING ()
+	<QUEUE I-FLICKERING 10>
 	<COND (<AND ,LIT
 	            <EQUAL? ,HERE ,BASEMENT-STAIRS ,BOILER-ROOM ,MORGUE>>
 	       <TELL "The shadows seem to flicker and move of their own accord." CR>)>
 	<RTRUE>>
 
 <ROUTINE I-COLD-DRAFT ()
+	<QUEUE I-COLD-DRAFT 15>
 	<COND (<EQUAL? ,HERE ,MORGUE ,CHAPEL ,PATIENT-WARD>
 	       <TELL "A cold draft makes you shiver, though there are no open windows." CR>)>
 	<RTRUE>>
 
 <ROUTINE I-CREAKING ()
+    <QUEUE I-CREAKING 9>
     <COND (<EQUAL? ,HERE ,OPERATING-THEATER ,PATIENT-WARD ,ELECTROSHOCK-THEATER>
            <TELL "The building settles with a deep structural groan, as if exhaling." CR>)>
     <RTRUE>>
 
+<ROUTINE I-BOILER-HEAT ()
+    <QUEUE I-BOILER-HEAT 1>
+    <COND (<AND ,BOILER-LIT <L? ,BOILER-HEAT 3>>
+           <SETG BOILER-HEAT <+ ,BOILER-HEAT 1>>
+           <COND (<EQUAL? ,BOILER-HEAT 1>
+                  <COND (<EQUAL? ,HERE ,BOILER-ROOM>
+                         <TELL "The boiler gives a rolling cough. One by one, the pipes begin to tick." CR>)>)
+                 (<EQUAL? ,BOILER-HEAT 2>
+                  <COND (<EQUAL? ,HERE ,BASEMENT-CORRIDOR ,FLOODING-CHAMBER>
+                         <TELL "A tremor passes through the pipes. Rust flakes fall as warmth travels east." CR>)>)
+                 (<EQUAL? ,BOILER-HEAT 3>
+                  <SETG CABINET-THAWED T>
+                  <COND (<EQUAL? ,HERE ,HYDROTHERAPY-ROOM>
+                         <TELL "Behind the wall, a pipe clangs. Frost slides from the medicine cabinet in translucent sheets." CR>)
+                        (<EQUAL? ,HERE ,BOILER-ROOM ,BASEMENT-CORRIDOR ,FLOODING-CHAMBER>
+                         <TELL "Farther along the pipework, ice breaks loose with a brittle crash." CR>)>)>)>
+    <RTRUE>>
+
+<ROUTINE I-COLD-EXPOSURE ()
+    <QUEUE I-COLD-EXPOSURE 1>
+    <COND (<AND <EQUAL? ,HERE ,MORGUE ,FLOODING-CHAMBER ,HYDROTHERAPY-ROOM>
+                <OR <EQUAL? ,HERE ,MORGUE>
+                    <NOT ,CABINET-THAWED>>>
+           <SETG COLD-EXPOSURE <+ ,COLD-EXPOSURE 1>>
+           <COND (<EQUAL? ,COLD-EXPOSURE 4>
+                  <TELL "The cold has worked through your clothes. Your fingers are beginning to stiffen." CR>)
+                 (<EQUAL? ,COLD-EXPOSURE 8>
+                  <TELL "Your teeth chatter hard enough to hurt. Staying here much longer would be dangerous." CR>)
+                 (<G? ,COLD-EXPOSURE 11>
+                  <JIGS-UP "The shivering stops. The tiles against your cheek feel almost warm; that is how you know the cold has won.">)>)
+          (T
+           <SETG COLD-EXPOSURE 0>)>
+    <RTRUE>>
+
+<ROUTINE I-PATIENT-AUTONOMY ()
+    <QUEUE I-PATIENT-AUTONOMY 4>
+    <COND (<AND <NOT ,GAME-WON>
+                <G? ,PATIENT-STATE 0>
+                <LOC ,PATIENT-189>>
+           <COND (<AND <EQUAL? ,PATIENT-STATE 1>
+                       <G? ,PATIENT-LORE 2>>
+                  <SETG PATIENT-STATE 2>
+                  <COND (<IN? ,PATIENT-189 ,HERE>
+                         <TELL "Patient 189's gaze sharpens. Something you uncovered elsewhere has reached it; recognition flickers behind the green light." CR>)>)>
+           <COND (<AND <IN? ,PATIENT-189 ,CHAPEL>
+                       <EQUAL? ,HERE ,OVERGROWN-GARDEN>>
+                  <MOVE ,PATIENT-189 ,OVERGROWN-GARDEN>
+                  <TELL "Bare feet whisper over stone behind you. Patient 189 has followed you into the garden." CR>)
+                 (<AND <IN? ,PATIENT-189 ,OVERGROWN-GARDEN>
+                       <EQUAL? ,HERE ,CHAPEL>>
+                  <MOVE ,PATIENT-189 ,CHAPEL>
+                  <TELL "Patient 189 glides past you and resumes its place before the altar." CR>)
+                 (<AND <IN? ,PATIENT-189 ,OVERGROWN-GARDEN>
+                       <NOT <EQUAL? ,HERE ,OVERGROWN-GARDEN ,CHAPEL>>>
+                  <MOVE ,PATIENT-189 ,CHAPEL>)>)>
+    <RTRUE>>
+
 ; === ENTRY POINT ===
 
 <ROUTINE GO ()
@@ -800,11 +1256,14 @@
 	<SETG WINNER ,ADVENTURER>
 	<SETG PLAYER ,WINNER>
 	<MOVE ,WINNER ,HERE>
-	<QUEUE I-WHISPER 8>
-	<QUEUE I-FOOTSTEPS 12>
-	<QUEUE I-FLICKERING 10>
-	<QUEUE I-COLD-DRAFT 15>
-	<QUEUE I-CREAKING 9>
+	<ENABLE <QUEUE I-WHISPER 8>>
+	<ENABLE <QUEUE I-FOOTSTEPS 12>>
+	<ENABLE <QUEUE I-FLICKERING 10>>
+	<ENABLE <QUEUE I-COLD-DRAFT 15>>
+	<ENABLE <QUEUE I-CREAKING 9>>
+	<ENABLE <QUEUE I-BOILER-HEAT 1>>
+	<ENABLE <QUEUE I-COLD-EXPOSURE 1>>
+	<ENABLE <QUEUE I-PATIENT-AUTONOMY 4>>
       <V-LOOK>
       <MAIN-LOOP>
 	<AGAIN>>
diff --git a/books/blackwood-horror/dungeon.zil b/books/blackwood-horror/dungeon.zil
index 81afcc5..f29e10f 100644
--- a/books/blackwood-horror/dungeon.zil
+++ b/books/blackwood-horror/dungeon.zil
@@ -10,6 +10,18 @@
 <GLOBAL CHAPEL-UNLOCKED <>>
 <GLOBAL CHAINS-CUT-FLAG <>>
 <GLOBAL GAME-WON <>>
+<GLOBAL PATIENT-STATE 0> ;"0=absent, 1=aware, 2=twitching, 3=liberated"
+<GLOBAL PATIENT-LORE 0> ;"count of distinct lore discoveries and first-time topics"
+<GLOBAL PATIENT-FILE-LORE <>>
+<GLOBAL WALL-SCRATCHES-LORE <>>
+<GLOBAL STRAITJACKET-LORE <>>
+<GLOBAL BOILER-FUELED <>>
+<GLOBAL BOILER-LIT <>>
+<GLOBAL BOILER-HEAT 0>
+<GLOBAL CABINET-THAWED <>>
+<GLOBAL COLD-EXPOSURE 0>
+<GLOBAL HINT-KEY 0>
+<GLOBAL HINT-LEVEL 0>
 <GLOBAL WHISPER-TABLE
     <LTABLE 0
         "A voice, barely audible, rasps: 'help... me...'"
@@ -30,7 +42,7 @@
 <ROOM SANITARIUM-ENTRANCE
       (IN ROOMS)
       (DESC "Sanitarium Entrance Hall")
-      (LDESC "The entrance hall reeks of mildew and decay. A grand staircase ascends to darkness in the east. To the west, a doorway leads to what might have been a reception area. North, you can make out an operating theater through a half-open door. A narrow staircase descends into the basement.")
+      (LDESC "The entrance hall reeks of mildew and decay. A grand staircase ascends to darkness in the east. To the west, a doorway leads to what might have been a reception area. A narrow staircase descends into the basement.")
       (SOUTH TO SANITARIUM-GATE)
       (WEST TO RECEPTION-ROOM)
       (NORTH TO OPERATING-THEATER)
@@ -46,14 +58,16 @@
       (LDESC "This cramped room once served as the sanitarium's reception. Filing cabinets line the opposite wall, their drawers hanging open like gaping mouths. A doorway to the east opens back to the entrance hall.")
       (EAST TO SANITARIUM-ENTRANCE)
       (FLAGS RLANDBIT ONBIT)
+      (GLOBAL FILING-CABINETS)
       (PSEUDO "NEST" NEST-PSEUDO "ASHES" ASHES-PSEUDO "ASH" ASHES-PSEUDO)>
 
 <ROOM OPERATING-THEATER
       (IN ROOMS)
       (DESC "Operating Theater")
-      (LDESC "The circular theater has rusty surgical instruments scattered about. Rising tiers of benches circle the area, where students once observed procedures. The air here is thick with an oppressive dread.")
+      (LDESC "The circular theater rises in tiers where students once observed procedures. Cold metal trays sit abandoned on carts. The air here is thick with an oppressive dread.")
       (SOUTH TO SANITARIUM-ENTRANCE)
-      (FLAGS RLANDBIT ONBIT)>
+      (FLAGS RLANDBIT ONBIT)
+      (PSEUDO "INSTRUMENTS" INSTRUMENTS-PSEUDO "SCALPELS" INSTRUMENTS-PSEUDO "TRAYS" TRAYS-PSEUDO "BENCHES" BENCHES-PSEUDO "BENCH" BENCHES-PSEUDO "TIERS" BENCHES-PSEUDO)>
 
 <ROOM PATIENT-WARD
       (IN ROOMS)
@@ -75,7 +89,7 @@
 <ROOM BASEMENT-STAIRS
       (IN ROOMS)
       (DESC "Basement Stairs")
-      (LDESC "A narrow stone staircase descends into darkness. The air grows colder with each step. Moisture drips from the ceiling, and the walls are slick with condensation. The stairs lead down into the basement, while the entrance hall lies to the south.")
+      (LDESC "A narrow stone staircase descends into darkness. The air grows colder with each step. Moisture drips from the ceiling, and the walls are slick with condensation. The stairs lead down into the basement, while the entrance hall lies up the stairs.")
       (UP TO SANITARIUM-ENTRANCE)
       (DOWN TO BASEMENT-CORRIDOR)
       (FLAGS RLANDBIT ONBIT)>
@@ -94,7 +108,7 @@
 <ROOM BOILER-ROOM
       (IN ROOMS)
       (DESC "Boiler Room")
-      (LDESC "This dark room is thick with coal dust that covers everything. The room radiates a sense of dormant power, waiting to awaken. A narrow doorway to the west leads back out to the corridor.")
+      (ACTION BOILER-ROOM-FCN)
       (WEST TO BASEMENT-CORRIDOR)
       (FLAGS RLANDBIT ONBIT)>
 
@@ -118,7 +132,7 @@
 <ROOM HYDROTHERAPY-ROOM
       (IN ROOMS)
       (DESC "Hydrotherapy Room")
-      (LDESC "Rubber hoses dangle from fixtures overhead. The tiles are cracked and stained. A doorway to the west opens back into the flooded chamber.")
+      (ACTION HYDROTHERAPY-ROOM-FCN)
       (WEST TO FLOODING-CHAMBER)
       (FLAGS RLANDBIT)>
 
@@ -134,7 +148,7 @@
 <ROOM ELECTROSHOCK-THEATER
       (IN ROOMS)
       (DESC "Electroshock Theater")
-      (LDESC "A concrete room. The walls are scorched in places. A viewing window overlooks the room from above. To the east, a stairway climbs upward. West, a heavy door stands ajar, revealing a padded cell beyond. A passage to the south leads out to the isolation ward.")
+      (LDESC "A concrete room. The walls are scorched in places. A viewing window overlooks the room from above. To the east, a stairway climbs upward. A passage to the south leads out to the isolation ward.")
       (SOUTH TO ISOLATION-WARD)
       (EAST TO OBSERVATION-DECK)
       (WEST TO PADDED-CELL)
@@ -144,7 +158,7 @@
 <ROOM PADDED-CELL
       (IN ROOMS)
       (DESC "Padded Cell")
-      (LDESC "The small room reeks of decay. Something has been written on the walls in what looks like dried blood. The only way out is through the door to the east, leading to the electroshock theater.")
+      (LDESC "The small room reeks of decay. Something has been written on the walls in what looks like dried blood.")
       (EAST TO ELECTROSHOCK-THEATER)
       (FLAGS RLANDBIT)
       (VALUE 5)>
@@ -152,7 +166,7 @@
 <ROOM OBSERVATION-DECK
       (IN ROOMS)
       (DESC "Observation Deck")
-      (LDESC "A small room with chairs facing a window. This is where doctors watched their experiments. Stairs lead down to the west, and a door to the north opens to the administrative wing.")
+      (LDESC "A small room with chairs facing a window. This is where doctors watched their experiments. Stairs lead down to the west.")
       (WEST TO ELECTROSHOCK-THEATER)
       (NORTH TO ADMINISTRATIVE-WING)
       (FLAGS RLANDBIT ONBIT)>
@@ -164,13 +178,14 @@
       (SOUTH TO OBSERVATION-DECK)
       (EAST TO DIRECTORS-OFFICE)
       (NORTH TO STAFF-QUARTERS)
-      (FLAGS RLANDBIT ONBIT)>
+      (FLAGS RLANDBIT ONBIT)
+      (GLOBAL FILING-CABINETS)>
 
 <ROOM DIRECTORS-OFFICE
       (IN ROOMS)
       (DESC "Director's Office")
       (ACTION DIRECTORS-OFFICE-FCN)
-      (LDESC "A large office with wood paneling. Bookshelves line the walls, filled with medical texts and journals. A door to the west opens back to the administrative wing corridor.")
+      (LDESC "A large office with wood paneling. Bookshelves line the walls, filled with medical texts and journals.")
       (WEST TO ADMINISTRATIVE-WING)
       (FLAGS RLANDBIT ONBIT)>
 
@@ -185,7 +200,7 @@
 <ROOM CAFETERIA
       (IN ROOMS)
       (DESC "Cafeteria")
-      (LDESC "Long tables with attached benches fill the room. Trays and plates lie scattered about, covered in dust. A door to the north leads to the garden. East returns to the staff quarters.")
+      (LDESC "Long tables with attached benches fill the room. Trays and plates lie scattered about, covered in dust. East returns to the staff quarters.")
       (EAST TO STAFF-QUARTERS)
       (NORTH TO OVERGROWN-GARDEN)
       (FLAGS RLANDBIT ONBIT)>
@@ -206,7 +221,8 @@
       (ACTION CHAPEL-FCN)
       (SOUTH TO OVERGROWN-GARDEN)
       (FLAGS RLANDBIT ONBIT)
-      (VALUE 15)>
+      (VALUE 15)
+      (GLOBAL TOPIC-MORDECAI TOPIC-TREATMENT TOPIC-IDENTITY TOPIC-SANITARIUM TOPIC-CHAPEL)>
 
 ; === OBJECTS ===
 
@@ -216,9 +232,10 @@
         (ADJECTIVE BRASS CORRODED)
         (DESC "brass plaque")
         (LDESC "A corroded brass plaque hangs askew on the gate.")
-        (FLAGS READBIT TAKEBIT)
+        (FLAGS READBIT)
         (TEXT "The plaque reads: 'Blackwood Sanitarium - Est. 1898 - Closed by Order 1952'")
-        (SIZE 5)>
+        (SIZE 5)
+        (ACTION BRASS-PLAQUE-F)>
 
 <OBJECT WALLPAPER
         (IN SANITARIUM-ENTRANCE)
@@ -228,6 +245,14 @@
         (LDESC "Peeling wallpaper reveals water-stained plaster beneath.")
         (TEXT "Victorian-era wallpaper depicting pastoral scenes, now grotesquely warped by moisture and black mold.")>
 
+<OBJECT THEATER-DOOR
+        (IN SANITARIUM-ENTRANCE)
+        (SYNONYM DOOR)
+        (ADJECTIVE HALF-OPEN THEATER OPERATING)
+        (DESC "door to the operating theater")
+        (LDESC "To the north, a door stands half-open, revealing an operating theater beyond.")
+        (ACTION THEATER-DOOR-F)>
+
 <OBJECT OAK-DESK
         (IN RECEPTION-ROOM)
         (SYNONYM DESK)
@@ -238,18 +263,8 @@
         (TEXT "The desk has three drawers. The top two are broken and empty. The bottom drawer appears intact but is locked tight.")
         (ACTION DESK-F)>
 
-<OBJECT DESK-DRAWER
-        (IN RECEPTION-ROOM)
-        (SYNONYM DRAWER)
-        (ADJECTIVE BOTTOM LOCKED DESK)
-        (DESC "desk drawer")
-        (LDESC "The bottom drawer of the oak desk is locked.")
-        (FLAGS CONTBIT OPENABLEBIT)
-        (CAPACITY 10)
-        (ACTION DESK-DRAWER-F)>
-
 <OBJECT PATIENT-FILE
-        (IN DESK-DRAWER)
+        (IN BOTTOM-DRAWER)
         (SYNONYM FILE FOLDER RECORDS)
         (ADJECTIVE PATIENT CONFIDENTIAL)
         (DESC "patient file")
@@ -274,6 +289,7 @@
         (SYNONYM TABLE)
         (ADJECTIVE OPERATING STAINED)
         (DESC "operating table")
+        (FDESC "Tiers of wooden benches circle a central operating table. Cold metal trays sit abandoned on carts. A single overhead lamp, long dead, still points down at the table like an accusation.")
         (LDESC "A stained operating table dominates the center of the room.")
         (FLAGS SURFACEBIT CONTBIT OPENBIT)
         (TEXT "The operating table is covered in dark brown stains that you hope are just rust. Leather restraints dangle from all four corners. Deep gouges mar the metal surface, as if someone struggled violently against the bindings.")>
@@ -312,15 +328,25 @@
         (SYNONYM BEDS FRAMES BED FRAME)
         (ADJECTIVE RUSTED)
         (DESC "bed frames")
+        (FDESC "Dozens of bed frames line the walls. Most mattresses have rotted away, leaving only rusted springs. Among the debris, you notice a child's crayon drawing pinned to one bedframe—a crude sun, a stick figure, the word 'HOME' in wobbly letters.")
         (LDESC "Rusted bed frames line the corridor.")
         (TEXT "Dozens of bed frames line the walls. The mattresses have rotted away, leaving only rusted springs and metal frames. Some still have restraint straps attached.")>
 
+<OBJECT CHILD-DRAWING
+        (IN PATIENT-WARD)
+        (SYNONYM DRAWING PICTURE CRAYON ART)
+        (ADJECTIVE CHILD CRAYON)
+        (DESC "child's drawing")
+        (FLAGS NDESCBIT READBIT)
+        (ACTION CHILD-DRAWING-F)>
+
 <OBJECT HEAVY-DOOR
         (IN PATIENT-WARD)
         (SYNONYM DOOR)
         (ADJECTIVE HEAVY SEALED LOCKED MORGUE)
         (DESC "heavy door")
         (LDESC "At the far end, a heavy door sealed with chains blocks further passage. Scratches cover the door's surface, as if made by desperate fingers.")
+        (FLAGS NDESCBIT)
         (ACTION HEAVYDOOR-F)>
 
 <OBJECT CHAINS
@@ -407,7 +433,8 @@
         (DESC "iron boiler")
         (FDESC "The room's centerpiece is a massive iron boiler, cold and silent as a tomb. Its hulking form crouches in the darkness like some dormant beast.")
         (LDESC "A massive iron boiler dominates the room, cold and silent.")
-        (FLAGS CONTBIT OPENBIT)
+        (FLAGS CONTBIT OPENBIT LIGHTBIT BURNBIT)
+        (CAPACITY 20)
         (ACTION BOILER-F)>
 
 <OBJECT COAL-SHOVEL
@@ -420,6 +447,25 @@
         (SIZE 10)
         (ACTION SHOVEL-F)>
 
+<OBJECT COAL-BIN
+        (IN BOILER-ROOM)
+        (SYNONYM BIN HOPPER)
+        (ADJECTIVE COAL IRON)
+        (DESC "coal bin")
+        (LDESC "An iron coal bin crouches beside the boiler.")
+        (FLAGS CONTBIT OPENBIT)
+        (ACTION COAL-BIN-F)>
+
+<OBJECT LUMP-OF-COAL
+        (IN COAL-BIN)
+        (SYNONYM COAL LUMP FUEL)
+        (ADJECTIVE BLACK DUSTY)
+        (DESC "lump of coal")
+        (LDESC "A usable lump of coal rests among the damp slack.")
+        (FLAGS TAKEBIT)
+        (SIZE 4)
+        (ACTION COAL-F)>
+
 <OBJECT WORKBENCH
         (IN BOILER-ROOM)
         (SYNONYM BENCH TABLE WORKBENCH)
@@ -485,7 +531,7 @@
         (ADJECTIVE OIL)
         (DESC "oil lantern")
         (LDESC "An old oil lantern. It still has fuel inside.")
-        (FLAGS TAKEBIT LIGHTBIT)
+        (FLAGS TAKEBIT LIGHTBIT FLAMEBIT)
         (SIZE 8)
         (ACTION LANTERN-F)>
 
@@ -514,6 +560,7 @@
         (ADJECTIVE SEALED EAST METAL)
         (DESC "sealed door")
         (LDESC "A door to the east is sealed shut.")
+        (FLAGS NDESCBIT)
         (ACTION SEALED-DOOR-F)>
 
 <OBJECT PORCELAIN-TUBS
@@ -541,8 +588,8 @@
         (SYNONYM CABINET CUPBOARD)
         (ADJECTIVE MEDICINE MEDICAL)
         (DESC "medicine cabinet")
-        (LDESC "A cabinet stands in the corner, its door hanging loose.")
-        (FLAGS CONTBIT OPENBIT)
+        (LDESC "A medicine cabinet is sealed beneath a skin of white frost.")
+        (FLAGS CONTBIT OPENABLEBIT)
         (ACTION MEDICINE-CABINET-F)>
 
 <OBJECT SYRINGE
@@ -565,7 +612,7 @@
 
 <OBJECT WALL-SCRATCHES
         (IN ISOLATION-WARD)
-        (SYNONYM SCRATCHES MARKS TALLIES)
+        (SYNONYM SCRATCHES MARKS TALLIES WRITING WORDS MESSAGE)
         (ADJECTIVE WALL)
         (DESC "wall scratches")
         (LDESC "Thousands of scratch marks covering the cell walls.")
@@ -588,18 +635,26 @@
         (LDESC "Electrodes dangle from a machine beside the chair.")
         (ACTION SHOCK-MACHINE-F)>
 
+<OBJECT PADCELL-DOOR
+        (IN ELECTROSHOCK-THEATER)
+        (SYNONYM DOOR)
+        (ADJECTIVE HEAVY WEST PADDED)
+        (DESC "heavy door to the padded cell")
+        (LDESC "To the west, a heavy door stands ajar, revealing a padded cell beyond.")
+        (ACTION PADCELL-DOOR-F)>
+
 <OBJECT PADDING
         (IN PADDED-CELL)
-        (SYNONYM PADDING WALLS)
-        (ADJECTIVE ROTTING TORN)
+        (SYNONYM PADDING WALLS WRITING WORDS MESSAGE)
+        (ADJECTIVE ROTTING TORN BLOOD DRIED)
         (DESC "padded walls")
         (LDESC "Every surface is covered in rotting padding, now torn and hanging in strips.")
         (ACTION PADDING-F)>
 
 <OBJECT STRAITJACKET
         (IN PADDED-CELL)
-        (SYNONYM STRAITJACKET JACKET)
-        (ADJECTIVE STRAIT)
+        (SYNONYM STRAITJACKET JACKET TAG LABEL)
+        (ADJECTIVE STRAIT NAME COLLAR)
         (DESC "straitjacket")
         (FDESC "A straitjacket lies in the corner, its straps unbuckled as if someone left in a hurry.")
         (LDESC "A straitjacket lies in the corner.")
@@ -608,6 +663,14 @@
         (SIZE 15)
         (ACTION STRAITJACKET-F)>
 
+<OBJECT ESCAPE-DOOR
+        (IN PADDED-CELL)
+        (SYNONYM DOOR)
+        (ADJECTIVE EAST HEAVY)
+        (DESC "door to the electroshock theater")
+        (LDESC "To the east, a heavy door leads back to the electroshock theater.")
+        (ACTION ESCAPE-DOOR-F)>
+
 <OBJECT ONE-WAY-MIRROR
         (IN OBSERVATION-DECK)
         (SYNONYM MIRROR WINDOW GLASS)
@@ -627,6 +690,14 @@
         (SIZE 7)
         (ACTION OBSERVATION-LOGBOOK-F)>
 
+<OBJECT CORRIDOR-DOOR
+        (IN OBSERVATION-DECK)
+        (SYNONYM DOOR)
+        (ADJECTIVE NORTH ADMINISTRATIVE)
+        (DESC "door to the administrative wing")
+        (LDESC "To the north, a door opens to the administrative wing.")
+        (ACTION CORRIDOR-DOOR-F)>
+
 <OBJECT SCATTERED-PAPERS
         (IN ADMINISTRATIVE-WING)
         (SYNONYM PAPERS FILES DOCUMENTS)
@@ -673,10 +744,18 @@
         (FLAGS CONTBIT)
         (ACTION WALL-SAFE-F)>
 
+<OBJECT OFFICE-DOOR
+        (IN DIRECTORS-OFFICE)
+        (SYNONYM DOOR)
+        (ADJECTIVE WEST HEAVY)
+        (DESC "door to the administrative wing")
+        (LDESC "To the west, a door opens back to the administrative wing corridor.")
+        (ACTION OFFICE-DOOR-F)>
+
 <OBJECT SAFE-KEY
         (IN HOLLOW-BOOK)
         (SYNONYM KEY)
-        (ADJECTIVE SAFE SMALL)
+        (ADJECTIVE SAFE NUMBERED)
         (DESC "safe key")
         (LDESC "A small key with a numbered tag: S-001.")
         (FLAGS TAKEBIT)
@@ -744,6 +823,14 @@
         (SIZE 2)
         (ACTION BELL-F)>
 
+<OBJECT GARDEN-DOOR
+        (IN CAFETERIA)
+        (SYNONYM DOOR)
+        (ADJECTIVE NORTH WOODEN)
+        (DESC "door to the garden")
+        (LDESC "To the north, a door leads out to the garden.")
+        (ACTION GARDEN-DOOR-F)>
+
 <OBJECT DEAD-GARDEN
         (IN OVERGROWN-GARDEN)
         (SYNONYM GARDEN WEEDS PLANTS)
@@ -774,6 +861,7 @@
         (ADJECTIVE GREEN UNNATURAL)
         (DESC "green candles")
         (LDESC "Candles burn with an unnatural green flame.")
+        (FLAGS NDESCBIT)
         (ACTION GREEN-CANDLES-F)>
 
 <OBJECT WOODEN-BOX
@@ -800,11 +888,11 @@
 
 <OBJECT PATIENT-189
         (IN CHAPEL)
-        (SYNONYM PATIENT FIGURE BEING)
+        (SYNONYM PATIENT FIGURE BEING MONSTER SOUL GHOST SOMETHING)
         (ADJECTIVE PATIENT 189)
         (DESC "Patient 189")
         (FDESC "Something is standing at the altar. It doesn't move. It doesn't breathe. But somehow, horribly, you know it knows you're here.")
-        (LDESC "A figure stands motionless at the altar. It turns to face you—its eyes glow faintly in the darkness. This is Patient 189, if you can still call it that.")
+        (LDESC "A figure stands motionless at the altar. It turns to face you—its eyes glow faintly in the darkness.")
         (FLAGS ACTORBIT)
         (ACTION PATIENT-189-F)>
 
@@ -813,7 +901,7 @@
 <OBJECT SANITARIUM-BUILDING
     (IN LOCAL-GLOBALS)
     (SYNONYM BUILDING SANITARIUM STRUCTURE FACADE)
-    (ADJECTIVE ABANDONED VICTORIAN)
+    (ADJECTIVE ABANDONED VICTORIAN SANITARIUM)
     (DESC "sanitarium building")
     (FLAGS NDESCBIT)
     (ACTION SANITARIUM-BUILDING-F)>
@@ -826,6 +914,49 @@
     (FLAGS NDESCBIT)
     (ACTION DEAD-OAK-TREE-F)>
 
+<OBJECT FILING-CABINETS
+    (IN LOCAL-GLOBALS)
+    (SYNONYM CABINETS CABINET DRAWERS FILES)
+    (ADJECTIVE FILING FILE OVERTURNED)
+    (DESC "filing cabinets")
+    (FLAGS NDESCBIT)
+    (ACTION FILING-CABINETS-F)>
+
+; === TOPIC OBJECTS (ASK/TELL vocabulary for NPC interaction) ===
+
+<OBJECT TOPIC-MORDECAI
+    (IN LOCAL-GLOBALS)
+    (SYNONYM MORDECAI DIRECTOR DOCTOR)
+    (ADJECTIVE HEINRICH)
+    (DESC "Dr. Mordecai")
+    (FLAGS NDESCBIT)>
+
+<OBJECT TOPIC-TREATMENT
+    (IN LOCAL-GLOBALS)
+    (SYNONYM TREATMENT EXPERIMENT SERUM THERAPY)
+    (ADJECTIVE EXPERIMENTAL)
+    (DESC "treatment")
+    (FLAGS NDESCBIT)>
+
+<OBJECT TOPIC-IDENTITY
+    (IN LOCAL-GLOBALS)
+    (SYNONYM NAME IDENTITY MEMORY PAST)
+    (DESC "identity")
+    (FLAGS NDESCBIT)>
+
+<OBJECT TOPIC-SANITARIUM
+    (IN LOCAL-GLOBALS)
+    (SYNONYM SANITARIUM HOSPITAL BLACKWOOD)
+    (ADJECTIVE BLACKWOOD)
+    (DESC "sanitarium")
+    (FLAGS NDESCBIT)>
+
+<OBJECT TOPIC-CHAPEL
+    (IN LOCAL-GLOBALS)
+    (SYNONYM CHAPEL ALTAR)
+    (DESC "chapel")
+    (FLAGS NDESCBIT)>
+
 <OBJECT BOTTOM-DRAWER
         (IN OAK-DESK)
         (SYNONYM DRAWER)
diff --git a/books/blackwood-horror/horror-walkthrough.md b/books/blackwood-horror/horror-walkthrough.md
index 468e2b0..0793b3f 100644
--- a/books/blackwood-horror/horror-walkthrough.md
+++ b/books/blackwood-horror/horror-walkthrough.md
@@ -12,7 +12,7 @@ This is a complete walkthrough for the horror.zil adventure game - an expansion
 
 - **Total Rooms:** 22
 - **Total Objects:** 59 (added HOLLOW-BOOK, SANITARIUM-BUILDING, DEAD-OAK-TREE)
-- **Win condition:** Relic + Serum + Syringe — say hello to Patient 189 while holding all three
+- **Win condition:** Relic + Serum + Syringe — `say hello` while holding all three
 - **Verbs Used:** Only standard Zork1 verbs
 
 ## Complete Room List
@@ -175,7 +175,7 @@ This is a complete walkthrough for the horror.zil adventure game - an expansion
 - The syringe (from hydrotherapy medicine cabinet)
 
 109. `examine patient` or `examine figure` - Patient 189, Dr. Mordecai's greatest achievement and horror
-110. `hello` - **Win condition!** With relic, serum, and syringe in hand — you inject the serum, the green light dies, Patient 189 whispers "I remember who I was" and crumbles to ash. The chapel goes dark. You're free.
+110. `say hello` - **Win condition!** With relic, serum, and syringe in hand — you inject the serum, the green light dies, Patient 189 whispers "I remember who I was" and crumbles to ash. The chapel goes dark. You're free.
 
 ## Puzzle Elements
 
@@ -192,7 +192,7 @@ This is a complete walkthrough for the horror.zil adventure game - an expansion
 
 5. **Safe Puzzle:** Find safe key hidden in hollow red leather book (Director's Office) to unlock wall safe containing chapel key
 
-6. **Earned Ending:** Say hello to Patient 189 while holding all three items: ancient relic + strange serum + syringe. Partial combinations give staged rejections — no relic: "You are not ready"; relic only: "The serum — if returned to its source..."
+6. **Earned Ending:** Use `say hello` while holding all three items: ancient relic + strange serum + syringe. Partial combinations give staged rejections — no relic: "You are not ready"; relic only: "The serum — if returned to its source..."
 
 7. **Container Puzzles:** Objects within objects
    - Medical bag (in shelves) contains bandages and morphine vial
@@ -225,7 +225,7 @@ These events fire at different intervals throughout gameplay, enhancing immersio
 ✓ **Movement:** NORTH, SOUTH, EAST, WEST, UP, DOWN  
 ✓ **Examination:** EXAMINE, LOOK-INSIDE, READ, SEARCH, COUNT  
 ✓ **Manipulation:** TAKE, OPEN, UNLOCK, TURN, ATTACK, LIGHT (LAMP-ON/LAMP-OFF), RING, BOARD  
-✓ **Social:** HELLO  
+✓ **Social:** SAY HELLO
 ✓ **Other:** DRINK, WEAR
 
 ## Story Overview
diff --git a/books/blackwood-horror/test/test-failures.zil b/books/blackwood-horror/test/test-failures.zil
index 30b0829..0714222 100644
--- a/books/blackwood-horror/test/test-failures.zil
+++ b/books/blackwood-horror/test/test-failures.zil
@@ -1,11 +1,4 @@
-<INSERT-FILE "infocom/zork1/globals">
-<INSERT-FILE "infocom/zork1/clock">
-<INSERT-FILE "books/blackwood-horror/dungeon">
-<INSERT-FILE "books/blackwood-horror/actions">
-<INSERT-FILE "infocom/zork1/parser">
-<INSERT-FILE "infocom/zork1/verbs">
-<INSERT-FILE "infocom/zork1/syntax">
-<INSERT-FILE "infocom/zork1/main">
+<INSERT-FILE "books/blackwood-horror/blackwood-horror">
 
 <CONSTANT RELEASEID 1>
 
@@ -42,11 +35,11 @@
         <CO-RESUME ,CO "look" T> 
         <==? ,HERE ,SANITARIUM-GATE>>
     
-    <ASSERT "Verify plaque has TAKEBIT flag" 
-        <FSET? ,BRASS-PLAQUE ,TAKEBIT>>
+    <ASSERT "Verify plaque has no TAKEBIT flag"
+        <NOT <FSET? ,BRASS-PLAQUE ,TAKEBIT>>>
     
-    <ASSERT "Take the brass plaque" 
-        <CO-RESUME ,CO "take plaque" T> 
-        <==? <LOC ,BRASS-PLAQUE> ,ADVENTURER>>
+    <ASSERT-TEXT "bolted firmly" <CO-RESUME ,CO "take plaque">>
+    <ASSERT "Plaque stays at the gate"
+        <==? <LOC ,BRASS-PLAQUE> ,SANITARIUM-GATE>>
     
     <TELL CR "All failing conditions tests completed!" CR>>
diff --git a/books/blackwood-horror/test/test-helpers.zil b/books/blackwood-horror/test/test-helpers.zil
index 59b8841..292dfe2 100644
--- a/books/blackwood-horror/test/test-helpers.zil
+++ b/books/blackwood-horror/test/test-helpers.zil
@@ -1,11 +1,4 @@
-<INSERT-FILE "infocom/zork1/globals">
-<INSERT-FILE "infocom/zork1/clock">
-<INSERT-FILE "books/blackwood-horror/dungeon">
-<INSERT-FILE "books/blackwood-horror/actions">
-<INSERT-FILE "infocom/zork1/parser">
-<INSERT-FILE "infocom/zork1/verbs">
-<INSERT-FILE "infocom/zork1/syntax">
-<INSERT-FILE "infocom/zork1/main">
+<INSERT-FILE "books/blackwood-horror/blackwood-horror">
 
 <CONSTANT RELEASEID 1>
 
@@ -20,8 +13,9 @@
     ;"Learn about Blackwood Sanitarium"
     <CO-RESUME ,CO "examine plaque">
     
-    ;"Take the brass plaque"
-    <ASSERT "Take the brass plaque" <CO-RESUME ,CO "take plaque" T> <==? <LOC ,BRASS-PLAQUE> ,ADVENTURER>>
+    ;"The brass plaque is fixed to the gate"
+    <ASSERT-TEXT "bolted firmly" <CO-RESUME ,CO "take plaque">>
+    <ASSERT "Brass plaque remains on the gate" <==? <LOC ,BRASS-PLAQUE> ,SANITARIUM-GATE>>
     
     ;"Enter Sanitarium Entrance Hall"
     <ASSERT "Enter Sanitarium Entrance Hall" <CO-RESUME ,CO "north" T> <==? ,HERE ,SANITARIUM-ENTRANCE>>
diff --git a/books/blackwood-horror/test/test-playtest-give-relic.zil b/books/blackwood-horror/test/test-playtest-give-relic.zil
new file mode 100644
index 0000000..772df4d
--- /dev/null
+++ b/books/blackwood-horror/test/test-playtest-give-relic.zil
@@ -0,0 +1,28 @@
+<INSERT-FILE "books/blackwood-horror/blackwood-horror">
+
+<GLOBAL CO <CO-CREATE GO>>
+
+<ROUTINE RUN-TEST ()
+    ;"The relic alone must not bypass the serum-and-syringe solution."
+    <SETG HERE ,CHAPEL>
+    <MOVE ,WINNER ,CHAPEL>
+    <MOVE ,PATIENT-189 ,CHAPEL>
+    <MOVE ,ANCIENT-RELIC ,WINNER>
+    <SETG GAME-WON <>>
+
+    <ASSERT-TEXT "serum"
+                 <CO-RESUME ,CO "give relic to patient">>
+    <ASSERT "The relic alone does not win" <NOT ,GAME-WON>>
+    <ASSERT "Patient 189 remains before the full solution"
+            <IN? ,PATIENT-189 ,CHAPEL>>
+
+    ;"With all three linked objects, GIVE remains a natural solution command."
+    <MOVE ,STRANGE-SERUM ,WINNER>
+    <MOVE ,SYRINGE ,WINNER>
+    <ASSERT-TEXT "I remember... who I was"
+                 <CO-RESUME ,CO "give relic to patient">>
+    <ASSERT "Complete GIVE solution sets the win flag" ,GAME-WON>
+    <ASSERT "Complete GIVE solution removes Patient 189"
+            <NOT <IN? ,PATIENT-189 ,CHAPEL>>>
+    <ASSERT "Complete GIVE solution leaves the player in the Chapel"
+            <==? ,HERE ,CHAPEL>>>
diff --git a/books/blackwood-horror/test/test-playtest-lore.zil b/books/blackwood-horror/test/test-playtest-lore.zil
new file mode 100644
index 0000000..d1de7a0
--- /dev/null
+++ b/books/blackwood-horror/test/test-playtest-lore.zil
@@ -0,0 +1,45 @@
+<INSERT-FILE "books/blackwood-horror/blackwood-horror">
+
+<GLOBAL CO <CO-CREATE GO>>
+
+<ROUTINE RUN-TEST ()
+    ;"Observed state: TAKE set TOUCHBIT before EXAMINE, suppressing the straitjacket's first-time prose and lore increment."
+    ;"Expected: lore discovery uses a dedicated flag and survives taking the object first."
+    <SETG HERE ,PADDED-CELL>
+    <MOVE ,WINNER ,PADDED-CELL>
+    <MOVE ,STRAITJACKET ,WINNER>
+    <FSET ,STRAITJACKET ,TOUCHBIT>
+    <SETG STRAITJACKET-LORE <>>
+    <SETG PATIENT-LORE 0>
+    <ASSERT-TEXT "handwriting seems... familiar"
+                 <CO-RESUME ,CO "examine straitjacket">>
+    <ASSERT "First examination increments lore after TAKE"
+            <==? ,PATIENT-LORE 1>>
+    <ASSERT-TEXT "name on the tag is illegible"
+                 <CO-RESUME ,CO "examine straitjacket">>
+    <ASSERT "Repeat examination does not increment lore"
+            <==? ,PATIENT-LORE 1>>
+
+    ;"Observed state: PATIENT-LORE was numeric zero, but the mirror still printed the changed-reflection prose."
+    ;"Expected: zero lore shows the ordinary mirror; positive lore shows the shifting reflection."
+    <SETG HERE ,OBSERVATION-DECK>
+    <MOVE ,WINNER ,OBSERVATION-DECK>
+    <SETG LIT T>
+    <SETG PATIENT-LORE 0>
+    <ASSERT-TEXT "throne of suffering" <CO-RESUME ,CO "examine mirror">>
+    <SETG PATIENT-LORE 1>
+    <ASSERT-TEXT "reflection is barely visible" <CO-RESUME ,CO "examine mirror">>
+
+    ;"Observed state: taking the patient file set TOUCHBIT, so reading it did not add its lore point."
+    ;"Expected: the patient file's dedicated discovery flag increments lore exactly once."
+    <SETG HERE ,RECEPTION-ROOM>
+    <MOVE ,WINNER ,RECEPTION-ROOM>
+    <MOVE ,PATIENT-FILE ,WINNER>
+    <FSET ,PATIENT-FILE ,TOUCHBIT>
+    <SETG PATIENT-FILE-LORE <>>
+    <SETG PATIENT-LORE 0>
+    <ASSERT-TEXT "Patient transferred to chapel"
+                 <CO-RESUME ,CO "read patient file">>
+    <ASSERT "Reading a taken patient file increments lore"
+            <==? ,PATIENT-LORE 1>>
+>
diff --git a/books/blackwood-horror/test/test-playtest-safe-key.zil b/books/blackwood-horror/test/test-playtest-safe-key.zil
new file mode 100644
index 0000000..722540a
--- /dev/null
+++ b/books/blackwood-horror/test/test-playtest-safe-key.zil
@@ -0,0 +1,20 @@
+<INSERT-FILE "books/blackwood-horror/blackwood-horror">
+
+<GLOBAL CO <CO-CREATE GO>>
+
+<ROUTINE RUN-TEST ()
+    ;"Observed command: TAKE SMALL KEY -> 'Which small key do you mean, the brass key or the safe key?'"
+    ;"Observed follow-up: TAKE SAFE KEY -> 'Which key do you mean, the brass key or the safe key?'"
+    ;"Expected: SMALL identifies the brass key; SAFE KEY then takes the distinct safe key."
+    <SETG HERE ,DIRECTORS-OFFICE>
+    <MOVE ,WINNER ,DIRECTORS-OFFICE>
+    <MOVE ,BRASS-KEY ,WINNER>
+    <MOVE ,HOLLOW-BOOK ,WINNER>
+    <FSET ,HOLLOW-BOOK ,OPENBIT>
+    <MOVE ,SAFE-KEY ,HOLLOW-BOOK>
+
+    <ASSERT-TEXT "already have"
+                 <CO-RESUME ,CO "take small key">>
+    <ASSERT-TEXT "Taken" <CO-RESUME ,CO "take safe key">>
+    <ASSERT "TAKE SAFE KEY selects the safe key"
+            <==? <LOC ,SAFE-KEY> ,WINNER>>>
diff --git a/books/blackwood-horror/test/test-playtest-say-ending.zil b/books/blackwood-horror/test/test-playtest-say-ending.zil
new file mode 100644
index 0000000..fbaa2f9
--- /dev/null
+++ b/books/blackwood-horror/test/test-playtest-say-ending.zil
@@ -0,0 +1,33 @@
+<INSERT-FILE "books/blackwood-horror/blackwood-horror">
+
+<GLOBAL CO <CO-CREATE GO>>
+
+<ROUTINE RUN-TEST ()
+    ;"Observed during play: SAY HELLO was rejected and left Patient 189 present."
+    ;"Expected: SAY HELLO performs the prepared ending; HELLO and HELLO PATIENT retain stock Zork behavior."
+    <SETG HERE ,CHAPEL>
+    <MOVE ,WINNER ,CHAPEL>
+    <MOVE ,PATIENT-189 ,CHAPEL>
+    <MOVE ,ANCIENT-RELIC ,WINNER>
+    <MOVE ,STRANGE-SERUM ,WINNER>
+    <MOVE ,SYRINGE ,WINNER>
+    <SETG GAME-WON <>>
+
+    <CO-RESUME ,CO "hello" T>
+    <ASSERT "Bare HELLO does not set the win flag" <NOT ,GAME-WON>>
+    <ASSERT "Bare HELLO leaves Patient 189 in the Chapel"
+            <IN? ,PATIENT-189 ,CHAPEL>>
+
+    <ASSERT-TEXT "bows his head"
+                 <CO-RESUME ,CO "hello patient">>
+    <ASSERT "HELLO PATIENT does not set the win flag" <NOT ,GAME-WON>>
+    <ASSERT "HELLO PATIENT leaves Patient 189 in the Chapel"
+            <IN? ,PATIENT-189 ,CHAPEL>>
+
+    <ASSERT-TEXT "I remember... who I was"
+                 <CO-RESUME ,CO "say hello">>
+    <ASSERT "SAY HELLO sets the win flag" ,GAME-WON>
+    <ASSERT "SAY HELLO removes Patient 189"
+            <NOT <IN? ,PATIENT-189 ,CHAPEL>>>
+    <ASSERT "SAY HELLO leaves the player in the post-ending Chapel"
+            <==? ,HERE ,CHAPEL>>>
diff --git a/books/blackwood-horror/test/test-playtest-scenery.zil b/books/blackwood-horror/test/test-playtest-scenery.zil
new file mode 100644
index 0000000..8bc2888
--- /dev/null
+++ b/books/blackwood-horror/test/test-playtest-scenery.zil
@@ -0,0 +1,40 @@
+<INSERT-FILE "books/blackwood-horror/blackwood-horror">
+
+<GLOBAL CO <CO-CREATE GO>>
+
+<ROUTINE RUN-TEST ()
+    ;"Observed command: TAKE PLAQUE -> 'Taken.' despite the plaque hanging on the gate."
+    ;"Expected: the bolted plaque refuses removal and remains at SANITARIUM-GATE."
+    <SETG HERE ,SANITARIUM-GATE>
+    <MOVE ,WINNER ,SANITARIUM-GATE>
+    <MOVE ,BRASS-PLAQUE ,SANITARIUM-GATE>
+    <ASSERT-TEXT "bolted firmly" <CO-RESUME ,CO "take plaque">>
+    <ASSERT "The plaque remains attached to the gate"
+            <==? <LOC ,BRASS-PLAQUE> ,SANITARIUM-GATE>>
+
+    ;"Observed command: EXAMINE DRAWING -> 'You used the word drawing in a way that I don't understand.'"
+    ;"Expected: DRAWING resolves to the child's crayon drawing and supplies authored detail."
+    <SETG HERE ,PATIENT-WARD>
+    <MOVE ,WINNER ,PATIENT-WARD>
+    <ASSERT-TEXT "yellow sun" <CO-RESUME ,CO "examine drawing">>
+
+    ;"Observed command: EXAMINE CABINETS -> 'You can't see any cabinets here!'"
+    ;"Expected: the explicitly described filing cabinets respond in Reception and Administration."
+    <SETG HERE ,RECEPTION-ROOM>
+    <MOVE ,WINNER ,RECEPTION-ROOM>
+    <ASSERT-TEXT "open and empty" <CO-RESUME ,CO "examine cabinets">>
+    <SETG HERE ,ADMINISTRATIVE-WING>
+    <MOVE ,WINNER ,ADMINISTRATIVE-WING>
+    <ASSERT-TEXT "overturned cabinets" <CO-RESUME ,CO "examine cabinets">>
+
+    ;"Observed command: READ WRITING -> 'You used the word writing in a way that I don't understand.'"
+    ;"Expected: WRITING resolves to the dried-blood message on the padded wall."
+    <SETG HERE ,PADDED-CELL>
+    <MOVE ,WINNER ,PADDED-CELL>
+    <ASSERT-TEXT "CHAPEL BEYOND THE GARDEN" <CO-RESUME ,CO "read writing">>
+
+    ;"Observed command: READ NAME TAG -> 'You used the word tag in a way that I don't understand.'"
+    ;"Expected: NAME TAG resolves to the straitjacket tag and reveals its date."
+    <SETG LIT T>
+    <ASSERT-TEXT "1947" <CO-RESUME ,CO "read name tag">>
+>
diff --git a/books/blackwood-horror/test/test-playtest-something.zil b/books/blackwood-horror/test/test-playtest-something.zil
new file mode 100644
index 0000000..b50a07d
--- /dev/null
+++ b/books/blackwood-horror/test/test-playtest-something.zil
@@ -0,0 +1,13 @@
+<INSERT-FILE "books/blackwood-horror/blackwood-horror">
+
+<GLOBAL CO <CO-CREATE GO>>
+
+<ROUTINE RUN-TEST ()
+    ;"Observed command: EXAMINE SOMETHING -> 'You used the word something in a way that I don't understand.'"
+    ;"Expected: SOMETHING resolves to the figure described in the Chapel as Patient 189."
+    <SETG HERE ,CHAPEL>
+    <MOVE ,WINNER ,CHAPEL>
+    <MOVE ,PATIENT-189 ,CHAPEL>
+
+    <ASSERT-TEXT "PATIENT 189"
+                 <CO-RESUME ,CO "examine something">>>
diff --git a/books/blackwood-horror/test/test-playtest-systems.zil b/books/blackwood-horror/test/test-playtest-systems.zil
new file mode 100644
index 0000000..ff6b558
--- /dev/null
+++ b/books/blackwood-horror/test/test-playtest-systems.zil
@@ -0,0 +1,43 @@
+<INSERT-FILE "books/blackwood-horror/blackwood-horror">
+
+<GLOBAL CO <CO-CREATE GO>>
+
+<ROUTINE RUN-TEST ()
+    <CO-RESUME ,CO "look">
+
+    ;"Hints reveal help progressively instead of dumping the solution."
+    <ASSERT-TEXT "meant to be opened" <CO-RESUME ,CO "hint">>
+    <ASSERT-TEXT "cutting instrument" <CO-RESUME ,CO "hints">>
+    <ASSERT-TEXT "use it on the chains" <CO-RESUME ,CO "hint">>
+    <ASSERT-TEXT "ATTACK CHAINS WITH SCALPEL" <CO-RESUME ,CO "hint">>
+
+    ;"Coal cannot be recovered bare-handed."
+    <SETG HERE ,BOILER-ROOM>
+    <MOVE ,WINNER ,BOILER-ROOM>
+    <MOVE ,LUMP-OF-COAL ,COAL-BIN>
+    <MOVE ,COAL-SHOVEL ,BOILER-ROOM>
+    <ASSERT-TEXT "need something broad enough" <CO-RESUME ,CO "take coal">>
+
+    ;"The cabinet visibly communicates its state and implied solution."
+    <SETG HERE ,HYDROTHERAPY-ROOM>
+    <MOVE ,WINNER ,HYDROTHERAPY-ROOM>
+    <SETG CABINET-THAWED <>>
+    <FCLEAR ,MEDICINE-CABINET ,OPENBIT>
+    <ASSERT-TEXT "sustained heat" <CO-RESUME ,CO "scrape cabinet">>
+
+    ;"Cold exposure is telegraphed before the fatal threshold."
+    <SETG HERE ,MORGUE>
+    <MOVE ,WINNER ,MORGUE>
+    <SETG COLD-EXPOSURE 3>
+    <ASSERT-TEXT "fingers are beginning to stiffen" <CO-RESUME ,CO "look">>
+
+    ;"Patient 189 reacts to discoveries and follows the player into the garden."
+    <SETG HERE ,OVERGROWN-GARDEN>
+    <MOVE ,WINNER ,OVERGROWN-GARDEN>
+    <MOVE ,PATIENT-189 ,CHAPEL>
+    <SETG PATIENT-STATE 1>
+    <SETG PATIENT-LORE 3>
+    <I-PATIENT-AUTONOMY>
+    <ASSERT "Patient state advances from discoveries" <==? ,PATIENT-STATE 2>>
+    <ASSERT "Patient follows into the garden" <IN? ,PATIENT-189 ,OVERGROWN-GARDEN>>
+>
diff --git a/books/blackwood-horror/test/test-walkthrough.zil b/books/blackwood-horror/test/test-walkthrough.zil
index 3981c92..50007f8 100644
--- a/books/blackwood-horror/test/test-walkthrough.zil
+++ b/books/blackwood-horror/test/test-walkthrough.zil
@@ -1,20 +1,12 @@
-<INSERT-FILE "infocom/zork1/globals">
-<INSERT-FILE "infocom/zork1/clock">
-<INSERT-FILE "books/blackwood-horror/actions">
-<INSERT-FILE "books/blackwood-horror/dungeon">
-<INSERT-FILE "books/blackwood-horror/actions">
-<INSERT-FILE "infocom/zork1/parser">
-<INSERT-FILE "infocom/zork1/verbs">
-<INSERT-FILE "infocom/zork1/syntax">
-<INSERT-FILE "infocom/zork1/main">
+<INSERT-FILE "books/blackwood-horror/blackwood-horror">
 
 <GLOBAL CO <CO-CREATE GO>>
 
 <ROUTINE RUN-TEST ()
 	<ASSERT "Start at Sanitarium Gate" <CO-RESUME ,CO "look" T> <==? ,HERE ,,SANITARIUM-GATE>>
 	<ASSERT-TEXT "blackwood" <CO-RESUME ,CO "examine plaque">> ;"Learn about Blackwood Sanitarium"
-	<ASSERT "Take the brass plaque" <CO-RESUME ,CO "take plaque" T> <==? <LOC ,BRASS-PLAQUE> ,ADVENTURER>>
-	<ASSERT "Drop brass plaque (no longer needed)" <CO-RESUME ,CO "drop plaque" T> <N==? <LOC ,BRASS-PLAQUE> ,ADVENTURER>>
+	<ASSERT-TEXT "bolted firmly" <CO-RESUME ,CO "take plaque">> ;"Plaque is fixed to the gate"
+	<ASSERT "Brass plaque remains on the gate" <==? <LOC ,BRASS-PLAQUE> ,SANITARIUM-GATE>>
 	<ASSERT "Enter Sanitarium Entrance Hall" <CO-RESUME ,CO "walk north" T> <==? ,HERE ,SANITARIUM-ENTRANCE>>
 	<ASSERT-TEXT "victorian" <CO-RESUME ,CO "examine wallpaper">> ;"Notice the Victorian-era decay"
 	<ASSERT "Go to Reception Room" <CO-RESUME ,CO "walk west" T> <==? ,HERE ,RECEPTION-ROOM>>
@@ -26,6 +18,7 @@
 	<ASSERT-TEXT "scalpel" <CO-RESUME ,CO "examine cabinet">> ;"Notice the medical cabinet"
 	<ASSERT "Take scalpel - important tool" <CO-RESUME ,CO "take scalpel" T> <==? <LOC ,SCALPEL> ,ADVENTURER>>
 	<ASSERT "Take ether bottle" <CO-RESUME ,CO "take bottle" T> <==? <LOC ,ETHER-BOTTLE> ,ADVENTURER>>
+	<ASSERT "Drop ether bottle (not needed)" <CO-RESUME ,CO "drop bottle" T> <N==? <LOC ,ETHER-BOTTLE> ,ADVENTURER>>
 	<ASSERT "Return to Entrance Hall" <CO-RESUME ,CO "walk south" T> <==? ,HERE ,SANITARIUM-ENTRANCE>>
 	<ASSERT "Go to Patient Ward" <CO-RESUME ,CO "walk east" T> <==? ,HERE ,PATIENT-WARD>>
 	<ASSERT-TEXT "frames" <CO-RESUME ,CO "examine beds">> ;"See the deteriorated ward"
@@ -50,6 +43,7 @@
 	<ASSERT "Take coal shovel" <CO-RESUME ,CO "take shovel" T> <==? <LOC ,COAL-SHOVEL> ,ADVENTURER>>
 	<ASSERT-TEXT "flashlight" <CO-RESUME ,CO "examine workbench">> ;"Find tools"
 	<ASSERT "Take flashlight (dead batteries)" <CO-RESUME ,CO "take flashlight" T> <==? <LOC ,FLASHLIGHT> ,ADVENTURER>>
+	<ASSERT "Drop dead flashlight" <CO-RESUME ,CO "drop flashlight" T> <N==? <LOC ,FLASHLIGHT> ,ADVENTURER>>
 	<ASSERT "Return to Basement Corridor" <CO-RESUME ,CO "walk west" T> <==? ,HERE ,BASEMENT-CORRIDOR>>
 	<ASSERT "Enter Storage Room" <CO-RESUME ,CO "walk west" T> <==? ,HERE ,STORAGE-ROOM>>
 	<ASSERT-TEXT "bag" <CO-RESUME ,CO "examine shelves">> ;"Find supplies including medical bag"
@@ -66,6 +60,15 @@
 	<ASSERT-TEXT "patient 189" <CO-RESUME ,CO "read records">> ;"Learn about Patient 189"
 	<ASSERT "Drop medical records (no longer needed)" <CO-RESUME ,CO "drop records" T> <N==? <LOC ,MEDICAL-RECORDS> ,ADVENTURER>>
 	<ASSERT "Return to Basement Corridor" <CO-RESUME ,CO "walk east" T> <==? ,HERE ,BASEMENT-CORRIDOR>>
+	<ASSERT "Return to Boiler Room with shovel and lantern" <CO-RESUME ,CO "walk east" T> <==? ,HERE ,BOILER-ROOM>>
+	<ASSERT "Recover usable coal with the shovel" <CO-RESUME ,CO "take coal" T> <==? <LOC ,LUMP-OF-COAL> ,ADVENTURER>>
+	<ASSERT-TEXT "place the coal" <CO-RESUME ,CO "put coal in boiler">>
+	<ASSERT-TEXT "deep metallic thud" <CO-RESUME ,CO "kindle boiler with lantern">>
+	<ASSERT "Boiler is lit" ,BOILER-LIT>
+	<CO-RESUME ,CO "wait">
+	<ASSERT "Boiler heat thaws the remote medicine cabinet" ,CABINET-THAWED>
+	<ASSERT "Drop shovel after fueling boiler" <CO-RESUME ,CO "drop shovel" T> <N==? <LOC ,COAL-SHOVEL> ,ADVENTURER>>
+	<ASSERT "Return to Basement Corridor after lighting boiler" <CO-RESUME ,CO "walk west" T> <==? ,HERE ,BASEMENT-CORRIDOR>>
 	<ASSERT "Enter Flooding Chamber" <CO-RESUME ,CO "walk north" T> <==? ,HERE ,FLOODING-CHAMBER>>
 	<ASSERT-TEXT "cold" <CO-RESUME ,CO "examine water">> ;"Cold ankle-deep water"
 	<ASSERT-TEXT "steam" <CO-RESUME ,CO "examine door">> ;"Sealed door to east - needs steam"
@@ -75,8 +78,9 @@
 	<ASSERT "Take soggy notebook" <CO-RESUME ,CO "take notebook" T> <==? <LOC ,SOGGY-NOTEBOOK> ,ADVENTURER>>
 	<ASSERT-TEXT "water" <CO-RESUME ,CO "read notebook">> ;"Learn about water torture"
 	<ASSERT "Drop soggy notebook (no longer needed)" <CO-RESUME ,CO "drop notebook" T> <N==? <LOC ,SOGGY-NOTEBOOK> ,ADVENTURER>>
-	<ASSERT-TEXT "syringe" <CO-RESUME ,CO "examine cabinet">> ;"Medicine cabinet"
-	<ASSERT "Take syringe" <CO-RESUME ,CO "take syringe" T> <==? <LOC ,SYRINGE> ,ADVENTURER>>
+	<ASSERT-TEXT "syringe" <CO-RESUME ,CO "examine cabinet">> ;"Thawed medicine cabinet"
+	<ASSERT-TEXT "pull the thawed cabinet open" <CO-RESUME ,CO "open cabinet">>
+	<ASSERT-TEXT "taken" <CO-RESUME ,CO "take syringe">>
 	<ASSERT "Return to Flooding Chamber" <CO-RESUME ,CO "walk west" T> <==? ,HERE ,FLOODING-CHAMBER>>
 	<ASSERT "Enter Isolation Ward" <CO-RESUME ,CO "walk north" T> <==? ,HERE ,ISOLATION-WARD>>
 	<ASSERT-TEXT "metal" <CO-RESUME ,CO "examine doors">> ;"See the cell doors"
@@ -87,7 +91,7 @@
 	<ASSERT "Enter Padded Cell" <CO-RESUME ,CO "walk west" T> <==? ,HERE ,PADDED-CELL>>
 	<ASSERT-TEXT "189" <CO-RESUME ,CO "examine padding">> ;"Blood message about chapel and Patient 189"
 	<ASSERT "Take straitjacket" <CO-RESUME ,CO "take jacket" T> <==? <LOC ,STRAITJACKET> ,ADVENTURER>>
-	<ASSERT-TEXT "your name" <CO-RESUME ,CO "examine jacket">> ;"Identity twist -- your name is on the tag"
+	<ASSERT-TEXT "name tag" <CO-RESUME ,CO "examine jacket">> ;"Identity twist -- name tag with familiar handwriting"
 	<ASSERT-TEXT "1947" <CO-RESUME ,CO "read jacket">> ;"Tag dated 1947, five years before closure"
 	<ASSERT "Drop straitjacket (no longer needed)" <CO-RESUME ,CO "drop jacket" T> <N==? <LOC ,STRAITJACKET> ,ADVENTURER>>
 	<ASSERT "Return to Electroshock Theater" <CO-RESUME ,CO "walk east" T> <==? ,HERE ,ELECTROSHOCK-THEATER>>
@@ -124,6 +128,7 @@
 	<ASSERT-TEXT "dead" <CO-RESUME ,CO "examine garden">> ;"Wild tangle of dead plants"
 	<ASSERT-TEXT "hope" <CO-RESUME ,CO "examine door">> ;"Chapel door with ominous message"
 	<ASSERT "Use chapel key to unlock final area" <CO-RESUME ,CO "unlock door with key"> ,CHAPEL-UNLOCKED>
+	<ASSERT "Drop chapel key after unlocking" <CO-RESUME ,CO "drop key" T> <N==? <LOC ,CHAPEL-KEY> ,ADVENTURER>>
 	<ASSERT "Enter Chapel - Final Location" <CO-RESUME ,CO "walk north" T> <==? ,HERE ,CHAPEL>>
 	<ASSERT-TEXT "symbols" <CO-RESUME ,CO "examine pews">> ;"Strange carved symbols"
 	<ASSERT-TEXT "green" <CO-RESUME ,CO "examine candles">> ;"Unnatural green flames"
@@ -134,5 +139,9 @@
 	<ASSERT-TEXT "189" <CO-RESUME ,CO "examine patient">> ;"Patient 189 - Dr. Mordecai's achievement"
 	<ASSERT-TEXT "glowing" <CO-RESUME ,CO "examine serum">> ;"Confirm serum still accessible"
 	<ASSERT-TEXT "needle" <CO-RESUME ,CO "examine syringe">> ;"Confirm syringe still accessible"
-	<ASSERT "WIN - freed with relic and serum and syringe" <CO-RESUME ,CO "hello" T> ,GAME-WON>
->
\ No newline at end of file
+	<ASSERT "Relic is carried before SAY HELLO" <==? <LOC ,ANCIENT-RELIC> ,ADVENTURER>>
+	<ASSERT "Serum is carried before SAY HELLO" <==? <LOC ,STRANGE-SERUM> ,ADVENTURER>>
+	<ASSERT "Syringe is carried before SAY HELLO" <==? <LOC ,SYRINGE> ,ADVENTURER>>
+	<ASSERT-TEXT "I remember... who I was" <CO-RESUME ,CO "say hello">>
+	<ASSERT "WIN - freed with relic and serum and syringe" ,GAME-WON>
+>
diff --git a/books/limehouse-killings/actions.zil b/books/limehouse-killings/actions.zil
index c834367..01b4ae8 100644
--- a/books/limehouse-killings/actions.zil
+++ b/books/limehouse-killings/actions.zil
@@ -2,48 +2,73 @@
 
 ; --- Evidence Object Actions ---
 
+<ROUTINE TELEGRAM-F ()
+    <COND (<VERB? EXAMINE READ>
+           <TELL "Lady Ashworth's message reads: 'Begin with what the locked room could not hide. Ashworth marked every private mechanism with the name of the person it concerned.' Beneath it she has added, 'Hudson has put the kettle on; he insists detection is impossible while cold.'" CR>
+           <RTRUE>)>>
+
 <ROUTINE DEAD-LETTER-F ()
     <COND (<VERB? EXAMINE READ>
            <TELL "The letter reads: 'My dear Dr. Moriarty, I know what you did. If you do not confess by Friday, I will expose you to Scotland Yard. - Lord Ashworth'" CR>
-           <SETG DEAD-LETTER-FOUND T>
-           <SETG EVIDENCE-FOUND <+ ,EVIDENCE-FOUND 1>>
+           <COND (<NOT ,DEAD-LETTER-FOUND>
+                  <SETG DEAD-LETTER-FOUND T>
+                  <SETG EVIDENCE-FOUND <+ ,EVIDENCE-FOUND 1>>
+                  <CHECK-CASE-PROGRESS>)>
            <RTRUE>)>>
 
 <ROUTINE BLOOD-STAINED-KNIFE-F ()
     <COND (<VERB? EXAMINE>
            <TELL "The knife is stained with dried blood. It matches the surgical tools in Dr. Moriarty's office." CR>
-           <SETG KNIFE-FOUND T>
-           <SETG EVIDENCE-FOUND <+ ,EVIDENCE-FOUND 1>>
+           <COND (<NOT ,KNIFE-FOUND>
+                  <SETG KNIFE-FOUND T>
+                  <SETG EVIDENCE-FOUND <+ ,EVIDENCE-FOUND 1>>
+                  <CHECK-CASE-PROGRESS>)>
            <RTRUE>)
           (<VERB? TAKE>
            <TELL "You take the knife carefully. This could be important." CR>
            <MOVE ,BLOOD-STAINED-KNIFE ,WINNER>
+           <COND (<NOT ,KNIFE-FOUND>
+                  <SETG KNIFE-FOUND T>
+                  <SETG EVIDENCE-FOUND <+ ,EVIDENCE-FOUND 1>>
+                  <CHECK-CASE-PROGRESS>)>
            <RTRUE>)>>
 
 <ROUTINE LOCKED-BOX-F ()
     <COND (<VERB? EXAMINE>
-           <TELL "The locked box is small and ornate. It has a keyhole." CR>
+           <TELL "The box has no keyhole. A four-letter name dial is ringed by tiny engravings: a sealed letter, a purple flower, and columns of debt. Turn the box to the name that connects all three." CR>
+           <SETG BOX-CLUE-SEEN T>
            <RTRUE>)
-          (<VERB? OPEN UNLOCK>
-           <COND (<IN? ,KEYRING ,WINNER>
-                  <TELL "You insert the key into the lock. It turns smoothly. The box slides open, revealing a bank statement inside." CR>
-                  <SETG LOCKED-BOX-OPENED T>
-                  <MOVE ,BANK-STATEMENT ,LOCKED-BOX>
+          (<VERB? TURN>
+           <COND (<OR <EQUAL? ,PRSI ,DR-MORIARTY>
+                      <EQUAL? ,PRSI ,MORIARTY-TOPIC>>
+                  <COND (<AND ,DEAD-LETTER-FOUND
+                              ,POISON-IDENTIFIED
+                              ,SECRET-LEDGER-FOUND>
+                         <TELL "You align the dial to MORIARTY. Letter, wolfsbane, and debt: the three engravings click beneath your fingers. The box opens, revealing a bank statement." CR>
+                         <SETG LOCKED-BOX-OPENED T>
+                         <FSET ,LOCKED-BOX ,OPENBIT>
+                         <MOVE ,BANK-STATEMENT ,LOCKED-BOX>)
+                        (T
+                         <TELL "The dial resists. You can read the three engravings, but you have not yet connected the sealed letter, purple flower, and debt." CR>)>
                   <RTRUE>)
-                 (<IN? ,LOCKPICK-SET ,WINNER>
-                  <TELL "You use the lockpick set on the locked box. It clicks open." CR>
-                  <SETG LOCKED-BOX-OPENED T>
-                  <MOVE ,BANK-STATEMENT ,LOCKED-BOX>
+                 (T
+                  <TELL "The dial turns back to blank. That name does not connect the box's three engravings." CR>
+                  <RTRUE>)>)
+          (<VERB? OPEN UNLOCK>
+           <COND (,LOCKED-BOX-OPENED
+                  <TELL "The box is already open." CR>
                   <RTRUE>)
                  (T
-                  <TELL "The box is locked. You need a key or lockpick." CR>
+                  <TELL "There is no keyhole to pick. The name dial is the lock; examine the box, then TURN BOX TO a name." CR>
                   <RTRUE>)>)>>
 
 <ROUTINE POISON-BOTTLE-F ()
     <COND (<VERB? EXAMINE READ>
            <TELL "The bottle is labeled: 'Aconitum - Wolfsbane. Highly poisonous.'" CR>
-           <SETG POISON-BOTTLE-FOUND T>
-           <SETG EVIDENCE-FOUND <+ ,EVIDENCE-FOUND 1>>
+           <COND (<NOT ,POISON-BOTTLE-FOUND>
+                  <SETG POISON-BOTTLE-FOUND T>
+                  <SETG EVIDENCE-FOUND <+ ,EVIDENCE-FOUND 1>>
+                  <CHECK-CASE-PROGRESS>)>
            <RTRUE>)
           (<VERB? TASTE>
            <TELL "You feel dizzy. Perhaps that wasn't wise." CR>
@@ -58,8 +83,10 @@
 <ROUTINE SECRET-LEDGER-F ()
     <COND (<VERB? EXAMINE READ>
            <TELL "The ledger shows Dr. Moriarty owed Lord Ashworth £500. The debt was due this week." CR>
-           <SETG SECRET-LEDGER-FOUND T>
-           <SETG EVIDENCE-FOUND <+ ,EVIDENCE-FOUND 1>>
+           <COND (<NOT ,SECRET-LEDGER-FOUND>
+                  <SETG SECRET-LEDGER-FOUND T>
+                  <SETG EVIDENCE-FOUND <+ ,EVIDENCE-FOUND 1>>
+                  <CHECK-CASE-PROGRESS>)>
            <RTRUE>)>>
 
 ; --- Tool Object Actions ---
@@ -74,6 +101,11 @@
            <RTRUE>)
           (<VERB? USE>
            <TELL "You peer through the magnifying glass. It reveals fine details." CR>
+           <RTRUE>)
+          (<AND <VERB? USE-ON>
+                <EQUAL? ,PRSI ,FOOTPRINT-CAST>>
+           <SETG FOOTPRINT-DETAIL-FOUND T>
+           <TELL "Under the lens, the plaster preserves more than a size: the outside edge of the right heel has a crescent-shaped nick. It is a defect distinctive enough to compare with a suspect's boot." CR>
            <RTRUE>)>>
 
 <ROUTINE LOCKPICK-SET-F ()
@@ -90,7 +122,7 @@
 
 <ROUTINE LANTERN-F ()
     <COND (<VERB? EXAMINE>
-           <TELL "A brass lantern, its glass clouded with age." CR>
+           <TELL "The lantern is no neglected adventure prop: its glass is clean, its reservoir full, and generations of servants have scratched their initials beneath the base. Hudson has kept their small history bright." CR>
            <RTRUE>)
           (<VERB? TAKE>
            <TELL "You take the lantern." CR>
@@ -106,15 +138,20 @@
            <TELL "A ring of keys, each one opening a different lock." CR>
            <RTRUE>)
           (<VERB? TAKE>
-           <TELL "You take the keyring." CR>
-           <MOVE ,KEYRING ,WINNER>
+           <COND (<IN? ,KEYRING ,WINNER>
+                  <TELL "You already have the keyring." CR>)
+                 (,HUDSON-KEY-GIVEN
+                  <TELL "You take the keyring." CR>
+                  <MOVE ,KEYRING ,WINNER>)
+                 (T
+                  <TELL "The keyring is not yours. You should ask Mr. Hudson for it." CR>)>
            <RTRUE>)>>
 
 ; --- Clue Object Actions ---
 
 <ROUTINE TORN-PAGE-F ()
     <COND (<VERB? EXAMINE READ>
-           <TELL "The page reads: 'Follow the rainbow order. Red, orange, yellow, green, blue, violet. Only then will the way open.'" CR>
+           <TELL "The page reads: 'Among the marked books, follow the rainbow order: red, yellow, green, blue. Only then will the way open.'" CR>
            <RTRUE>)
           (<VERB? TAKE>
            <TELL "You take the torn page." CR>
@@ -126,13 +163,41 @@
            <TELL "The markers are: RED on shelf 1, BLUE on shelf 3, GREEN on shelf 4, YELLOW on shelf 2." CR>
            <RTRUE>)>>
 
+<ROUTINE CIPHER-BOOK-F ()
+    <COND (<VERB? PUSH>
+           <COND (,CIPHER-SOLVED
+                  <TELL "The secret passage is already open." CR>)
+                 (<AND <EQUAL? ,PRSO ,RED-BOOK> <==? ,CIPHER-STAGE 0>>
+                  <SETG CIPHER-STAGE 1>
+                  <TELL "The red-marked book clicks into place." CR>)
+                 (<AND <EQUAL? ,PRSO ,YELLOW-BOOK> <==? ,CIPHER-STAGE 1>>
+                  <SETG CIPHER-STAGE 2>
+                  <TELL "The yellow-marked book clicks into place." CR>)
+                 (<AND <EQUAL? ,PRSO ,GREEN-BOOK> <==? ,CIPHER-STAGE 2>>
+                  <SETG CIPHER-STAGE 3>
+                  <TELL "The green-marked book clicks into place." CR>)
+                 (<AND <EQUAL? ,PRSO ,BLUE-BOOK> <==? ,CIPHER-STAGE 3>>
+                  <SOLVE-CIPHER>)
+                 (T
+                  <SETG CIPHER-STAGE 0>
+                  <TELL "The book springs back. The sequence resets." CR>)>
+           <RTRUE>)>>
+
 <ROUTINE FOOTPRINT-CAST-F ()
     <COND (<VERB? EXAMINE>
-           <TELL "The cast shows a boot print size 10 - too large for Lady Ashworth." CR>
+           <TELL "The cast shows a size 10 boot print, too large for Lady Ashworth and narrower than Hudson's work boots.">
+           <COND (,FOOTPRINT-DETAIL-FOUND
+                  <TELL " Through the magnifying glass you found a crescent-shaped nick on the outside of its right heel.">)>
+           <CRLF>
            <RTRUE>)
           (<VERB? TAKE>
            <TELL "You take the footprint cast." CR>
            <MOVE ,FOOTPRINT-CAST ,WINNER>
+           <RTRUE>)
+          (<AND <VERB? USE-ON>
+                <EQUAL? ,PRSO ,MAGNIFYING-GLASS>>
+           <SETG FOOTPRINT-DETAIL-FOUND T>
+           <TELL "Under the lens, the plaster preserves more than a size: the outside edge of the right heel has a crescent-shaped nick. It is a defect distinctive enough to compare with a suspect's boot." CR>
            <RTRUE>)>>
 
 <ROUTINE WAX-SEAL-F ()
@@ -147,6 +212,10 @@
 <ROUTINE BANK-STATEMENT-F ()
     <COND (<VERB? EXAMINE READ>
            <TELL "The statement shows Dr. Moriarty's account is overdrawn. He recently withdrew a large sum for 'experimental supplies.'" CR>
+           <COND (<NOT ,BANK-STATEMENT-FOUND>
+                  <SETG BANK-STATEMENT-FOUND T>
+                  <SETG EVIDENCE-FOUND <+ ,EVIDENCE-FOUND 1>>
+                  <CHECK-CASE-PROGRESS>)>
            <RTRUE>)
           (<VERB? TAKE>
            <TELL "You take the bank statement." CR>
@@ -172,12 +241,53 @@
           (<VERB? OPEN UNLOCK>
            <COND (<IN? ,LOCKPICK-SET ,WINNER>
                   <TELL "You use the lockpick set on the window latch. It clicks open." CR>
-                  <SETG STUDY-UNLOCKED T>
+                  <FSET ,WINDOW ,OPENBIT>
                   <RTRUE>)
                  (T
                   <TELL "The window latch is rusted. You need a tool to open it." CR>
                   <RTRUE>)>)>>
 
+<ROUTINE STUDY-DOOR-F ()
+    <COND (<VERB? EXAMINE>
+           <COND (<FSET? ,STUDY-DOOR ,OPENBIT>
+                  <TELL "The solid oak study door stands open." CR>)
+                 (,STUDY-UNLOCKED
+                  <TELL "The solid oak study door is closed but unlocked." CR>)
+                 (T
+                  <TELL "The solid oak study door is closed and locked." CR>)>
+           <RTRUE>)
+          (<VERB? OPEN>
+           <COND (<FSET? ,STUDY-DOOR ,OPENBIT>
+                  <TELL "The study door is already open." CR>)
+                 (<AND <==? ,HERE ,STUDY> <NOT ,STUDY-UNLOCKED>>
+                  <SETG STUDY-UNLOCKED T>
+                  <FSET ,STUDY-DOOR ,OPENBIT>
+                  <TELL "You draw back the interior bolt and open the study door." CR>)
+                 (<NOT ,STUDY-UNLOCKED>
+                  <TELL "The study door is locked. You'll need the study key or a lockpick." CR>)
+                 (T
+                  <FSET ,STUDY-DOOR ,OPENBIT>
+                  <TELL "You open the study door." CR>)>
+           <RTRUE>)
+          (<VERB? UNLOCK>
+           <COND (,STUDY-UNLOCKED
+                  <TELL "The study door is already unlocked." CR>)
+                 (<AND <==? ,HERE ,STUDY> <NOT ,PRSI>>
+                  <SETG STUDY-UNLOCKED T>
+                  <TELL "You draw back the interior bolt. The study door is now unlocked." CR>)
+                 (<==? ,PRSI ,KEYRING>
+                  <SETG STUDY-UNLOCKED T>
+                  <TELL "The study key turns smoothly in the lock. The study door is now unlocked." CR>)
+                 (<==? ,PRSI ,LOCKPICK-SET>
+                  <SETG STUDY-UNLOCKED T>
+                  <TELL "After a moment's careful work, the lock clicks open. The study door is now unlocked." CR>)
+                 (T
+                  <TELL "That does not fit the study door's lock." CR>)>
+           <RTRUE>)
+          (<VERB? BREAK ATTACK>
+           <TELL "The door is solid oak. You'd need a battering ram." CR>
+           <RTRUE>)>>
+
 <ROUTINE BOOKSHELF-F ()
     <COND (<VERB? EXAMINE>
            <TELL "The bookshelf is arranged by color. Red, blue, green, and yellow markers are visible on different shelves." CR>
@@ -202,10 +312,16 @@
 
 <ROUTINE WINE-CABINET-F ()
     <COND (<VERB? EXAMINE>
-           <TELL "The wine cabinet is locked. It contains fine wines and spirits." CR>
+           <SETG CABINET-CLUE-SEEN T>
+           <TELL "The cabinet is unlatched. Dust outlines a missing squat bottle on the medicinal-wine shelf; beside the gap, a handwritten inventory entry reads 'tincture, private laboratory.' Someone removed the delivery bottle without disturbing the dinner wines." CR>
            <RTRUE>)
-          (<VERB? OPEN UNLOCK>
-           <TELL "The wine cabinet is locked. You don't have the key." CR>
+          (<VERB? OPEN>
+           <FSET ,WINE-CABINET ,OPENBIT>
+           <SETG CABINET-CLUE-SEEN T>
+           <TELL "The glass door opens freely. The missing medicinal bottle's clean dust-shadow and the words 'private laboratory' are easier to see, but the shelf holds nothing else relevant." CR>
+           <RTRUE>)
+          (<VERB? UNLOCK>
+           <TELL "There is no lock to solve; the glass door is merely closed." CR>
            <RTRUE>)>>
 
 <ROUTINE POTS-F ()
@@ -222,17 +338,36 @@
     <COND (<VERB? EXAMINE>
            <TELL "A servant bell hangs from the wall. A rope leads up to the servant's quarters." CR>
            <RTRUE>)
-          (<VERB? PULL USE>
+          (<VERB? MOVE USE>
            <TELL "You pull the bell rope. A distant bell rings upstairs." CR>
            <RTRUE>)>>
 
-<ROUTINE DRAWER-F ()
+<ROUTINE KETTLE-F ()
     <COND (<VERB? EXAMINE>
-           <TELL "The drawer is slightly open. You can see something inside." CR>
+           <TELL "The blue enamel kettle is freshly filled and still warm. A card in Hudson's square hand reads: TEA FIRST. THEORIES AFTER." CR>
+           <RTRUE>)
+          (<VERB? TAKE>
+           <TELL "The kettle belongs on the range; its warmth is more useful here than in your pocket." CR>
+           <RTRUE>)>>
+
+<ROUTINE BELL-WIRE-F ()
+    <COND (<VERB? EXAMINE>
+           <COND (<==? ,CASE-ACT 1>
+                  <TELL "The servant-bell wire is still beside the study door." CR>)
+                 (T
+                  <TELL "The servant-bell wire trembles where the hidden wall's movement disturbed it, a small physical echo of the secret route." CR>)>
+           <RTRUE>)
+          (<VERB? MOVE USE>
+           <TELL "You tug the wire. From below comes one bright kitchen bell, followed by Hudson's dry voice: 'The kettle remains where I left it.'" CR>
+           <RTRUE>)>>
+
+<ROUTINE DRAWER-F ()
+    <COND (<AND <VERB? OPEN> <FSET? ,DRAWER ,OPENBIT>>
+           <TELL "The drawer is already open." CR>
            <RTRUE>)
           (<VERB? OPEN>
-           <TELL "You open the drawer. Inside is a lockpick set." CR>
-           <MOVE ,LOCKPICK-SET ,DRAWER>
+           <TELL "You open the drawer. Inside is a leather roll." CR>
+           <FSET ,DRAWER ,OPENBIT>
            <RTRUE>)>>
 
 <ROUTINE FOUNTAIN-F ()
@@ -248,6 +383,10 @@
 <ROUTINE PLANTS-F ()
     <COND (<VERB? EXAMINE>
            <TELL "Exotic plants fill the greenhouse. One plant has distinctive purple flowers - wolfsbane." CR>
+           <RTRUE>)
+          (<AND <VERB? USE-ON>
+                <EQUAL? ,PRSO ,POISON-BOTTLE>>
+           <IDENTIFY-POISON>
            <RTRUE>)>>
 
 <ROUTINE LABELS-F ()
@@ -265,9 +404,11 @@
            <TELL "Simple beds for the household staff. They are empty." CR>
            <RTRUE>)>>
 
-<ROUTINE TRUNK-F ()
-    <COND (<VERB? EXAMINE>
-           <TELL "A large trunk contains servant uniforms and a letter." CR>
+<ROUTINE TRUNK-LETTER-F ()
+    <COND (<VERB? EXAMINE READ>
+           <TELL "The letter is addressed to Mr. Hudson from an unknown sender. It reads:" CR>
+           <TELL "The master's experiments have gone too far. If anything happens to me, the evidence is in the study. Burn this after reading." CR>
+           <TELL "The signature is illegible." CR>
            <RTRUE>)>>
 
 <ROUTINE UNIFORMS-F ()
@@ -277,32 +418,49 @@
 
 <ROUTINE SHELVES-F ()
     <COND (<VERB? EXAMINE>
-           <TELL "The shelves hold canned goods, spices, and a bottle of antidote ingredients." CR>
+           <TELL "The shelves hold preserves, spices, dried foxglove with a poison warning, and powdered charcoal labeled for swallowed poisons." CR>
            <RTRUE>)>>
 
 <ROUTINE FOXGLOVE-F ()
     <COND (<VERB? EXAMINE>
-           <TELL "A bottle of foxglove, its label faded but legible. An antidote ingredient." CR>
+           <TELL "The foxglove label names digitalis and gives a narrow medicinal dose, followed by a skull. It is another poison, not an antidote to wolfsbane." CR>
            <RTRUE>)
           (<VERB? TAKE>
            <TELL "You take the foxglove." CR>
            <MOVE ,FOXGLOVE ,WINNER>
+           <RTRUE>)
+          (<VERB? USE TASTE>
+           <TELL "The dosage warning is precise and the skull more persuasive. Experimenting on yourself would compound one poison with another." CR>
            <RTRUE>)>>
 
 <ROUTINE CHARCOAL-F ()
     <COND (<VERB? EXAMINE>
-           <TELL "A container of charcoal, used for filtering poisons. An antidote ingredient." CR>
+           <TELL "The powdered charcoal is labeled for immediate use after swallowed poisons. It can limit harm, not identify a culprit." CR>
            <RTRUE>)
           (<VERB? TAKE>
            <TELL "You take the charcoal." CR>
            <MOVE ,CHARCOAL ,WINNER>
+           <RTRUE>)
+          (<VERB? USE>
+           <COND (<==? ,PLAYER-HEALTH 3>
+                  <TELL "You have swallowed no poison. Save the charcoal for an actual emergency." CR>)
+                 (T
+                  <SETG PLAYER-HEALTH <+ ,PLAYER-HEALTH 1>>
+                  <TELL "You swallow a measured spoonful with water. It tastes of soot, but the dizziness recedes and your pulse steadies." CR>)>
            <RTRUE>)>>
 
 ; --- Room Action Routines (Dynamic Descriptions) ---
 
+<ROUTINE GATE-FCN (RARG)
+    <COND (<EQUAL? .RARG ,M-LOOK>
+           <COND (<IN? ,TELEGRAM ,ASHWORTH-MANOR-GATE>
+                  <TELL "Wet iron bars divide the river fog into pale strips. Coal smoke catches at the back of your throat, and a gravel path runs north toward the manor. A creased telegram is pinned beneath a stone beside the open gate." CR>)
+                 (T
+                  <TELL "River fog beads on the open iron gate. Wet gravel leads north to Ashworth Manor; the stone where the telegram waited is bare." CR>)>)>>
+
 <ROUTINE STUDY-FCN (RARG)
     <COND (<EQUAL? .RARG ,M-LOOK>
-           <TELL "The study is a crime scene. A chalk outline marks where the body lay, the victim struck down in this very room. The air hangs heavy with the memory of violence.">
+           <TELL "A chalk outline interrupts the Turkey carpet; beside it, three dark drops have dried almost black. Cold ash grits beneath your shoes.">
            <COND (,LOCKED-BOX-OPENED
                   <TELL " The locked box in the fireplace lies open, its contents revealed.">)
                  (T
@@ -311,41 +469,103 @@
                   <TELL " The window stands open, letting in the chill night air.">)
                  (T
                   <TELL " A window looks out to the garden, its latch rusted but intact.">)>
-           <TELL CR "A doorway leads north back to the entrance hall." CR>)>>
+           <COND (<FSET? ,STUDY-DOOR ,OPENBIT>
+                  <TELL " The solid oak study door to the north stands open onto the entrance hall.">)
+                 (,STUDY-UNLOCKED
+                  <TELL " The solid oak study door to the north is closed but unlocked.">)
+                 (T
+                  <TELL " The solid oak study door to the north is closed and locked.">)>
+           <CRLF>)>>
 
 <ROUTINE LIBRARY-FCN (RARG)
     <COND (<EQUAL? .RARG ,M-LOOK>
            <TELL "Floor-to-ceiling bookshelves line the walls, their contents ranging from leather-bound classics to modern scientific texts. The fire is cold, but the room retains a scholarly warmth.">
            <COND (,CIPHER-SOLVED
-                  <TELL " A secret passage lies open to the east, its dark mouth beckoning.">)
+                  <TELL " The shifted bookcase exposes a stone passage east toward the study.">)
                  (T
-                  <TELL " A doorway leads west back to the entrance hall.">)>
-           <CR>)>>
+                  <TELL " Colored ribbons interrupt the orderly shelves. A doorway leads west back to the entrance hall.">)>
+           <COND (<IN? ,DR-MORIARTY ,LIBRARY>
+                  <TELL " Dr. Moriarty waits by the scientific folios, tapping one immaculate fingernail against a spine.">)>
+           <CRLF>)>>
 
 <ROUTINE KITCHEN-FCN (RARG)
     <COND (<EQUAL? .RARG ,M-LOOK>
            <TELL "A kitchen that has seen better days. The hearth is cold, its last fire long extinguished.">
            <COND (<FSET? ,DRAWER ,OPENBIT>
-                  <TELL " The drawer in the counter stands open.">)
+                  <TELL " The drawer in the counter stands open, a leather roll inside.">)
                  (T
-                  <TELL " A drawer in the counter is slightly ajar.">)>
-           <TELL CR "A staircase leads up to the entrance hall, and a doorway west leads to the garden." CR>)>>
+                  <TELL " A drawer in the counter is closed.">)>
+           <TELL CR "A blue kettle sits ready on the range, a small domestic kindness in a silenced house. A staircase leads up to the entrance hall, and a doorway west leads to the garden." CR>)>>
 
 <ROUTINE GARDEN-FCN (RARG)
     <COND (<EQUAL? .RARG ,M-LOOK>
-           <TELL "An overgrown garden sprawls before you, its paths choked with weeds. A fountain stands at the center, dry and silent. Hedge mazes line the paths, their shadows hiding secrets.">
+           <TELL "Rain beads along the overgrown hedges and darkens the gravel around a dry stone fountain.">
            <COND (<IN? ,BLOOD-STAINED-KNIFE ,GARDEN>
                   <TELL " Something glints in the branches near the fountain.">)>
+           <COND (<IN? ,FOOTPRINT-CAST ,GARDEN>
+                  <TELL " A white plaster footprint cast rests against the fountain's blackened basin.">)>
            <TELL CR "A doorway east leads to the kitchen, paths lead north to the greenhouse and south to the servants' quarters." CR>)>>
 
+<ROUTINE DINING-ROOM-FCN (RARG)
+    <COND (<EQUAL? .RARG ,M-LOOK>
+           <TELL "Two places are set at the long table, but a skin has formed over the soup before Lady Ashworth and the knife beside it is exactly parallel to her plate.">
+           <COND (<IN? ,WAX-SEAL ,DINING-ROOM>
+                  <TELL " A crimson wax seal lies at the unused place.">)>
+           <COND (,CABINET-CLUE-SEEN
+                  <TELL " The unlatched wine cabinet shows the clean outline of its missing medicinal bottle.">)
+                 (T
+                  <TELL " A glass-fronted wine cabinet stands unlatched against the wall.">)>
+           <COND (<==? ,CASE-ACT 3>
+                  <TELL " Lady Ashworth's black ribbon now lies beside the plate while she listens toward the hall.">)
+                 (,LADY-CONFRONTED
+                  <TELL " The letter rests beside her wedding ring; neither is quite still.">)>
+           <TELL " Doors lead east to the hall and north to the pantry." CR>)>>
+
+<ROUTINE GREENHOUSE-FCN (RARG)
+    <COND (<EQUAL? .RARG ,M-LOOK>
+           <TELL "Humidity beads on every glass pane. Purple wolfsbane flowers rise above the potting bench, and their paper labels curl in the damp.">
+           <COND (,POISON-IDENTIFIED
+                  <TELL " One clipped stem matches the plant material suspended in the study vial.">)>
+           <TELL " The garden lies south." CR>)>>
+
+<ROUTINE SERVANTS-QUARTERS-FCN (RARG)
+    <COND (<EQUAL? .RARG ,M-LOOK>
+           <TELL "Clean but worn linen is folded across the narrow beds. A wooden trunk stands beneath a brass lantern kept brighter than anything else in the room.">
+           <COND (<==? ,CASE-ACT 3>
+                  <TELL " Hudson's packed carpetbag rests by the north door; his coat is buttoned one hole wrong.">)
+                 (,HUDSON-CONFRONTED
+                  <TELL " Hudson's polishing cloth lies over a single unfinished spoon.">)
+                 (T
+                  <TELL " Hudson polishes one spoon in short strokes, the cloth squeaking whenever his hand tightens.">)>
+           <TELL " The garden lies north." CR>)>>
+
+<ROUTINE SECRET-PASSAGE-FCN (RARG)
+    <COND (<EQUAL? .RARG ,M-LOOK>
+           <TELL "The passage is narrow enough for cobwebs to catch at both sleeves. Moisture slicks the stone, while a single trail cuts the dust between the library to the west and the study to the east.">
+           <COND (<AND <IN? ,LANTERN ,WINNER> <FSET? ,LANTERN ,ONBIT>>
+                  <TELL " Your lantern warms the wet wall to amber and picks out the recent heel marks.">)>
+           <CRLF>)>>
+
+<ROUTINE PANTRY-FCN (RARG)
+    <COND (<EQUAL? .RARG ,M-LOOK>
+           <TELL "Cool, dry air smells of apples and charcoal dust. The shelves hold preserves, a warning-labeled bottle of foxglove, and powdered charcoal for swallowed poisons. The dining room lies south." CR>)>>
+
 <ROUTINE ENTRANCE-HALL-FCN (RARG)
     <COND (<EQUAL? .RARG ,M-LOOK>
-           <TELL "You step into a grand foyer that has seen better days. The air is thick with the scent of old wood and regret. Doorways lead in every direction -- north to the gate, east to the library, west to the dining room, and a staircase down to the kitchen.">
-           <COND (,STUDY-UNLOCKED
-                  <TELL " The door to the south stands open, revealing the study beyond.">)
+           <TELL "Dust has softened the chandelier's crystal edges, and beeswax polish sharpens the smell of old oak. Doorways lead north to the gate, east to the library, west to the dining room, and down to the kitchen.">
+           <COND (<FSET? ,STUDY-DOOR ,OPENBIT>
+                  <TELL " The solid oak study door to the south stands open, revealing the study beyond.">)
+                 (,STUDY-UNLOCKED
+                  <TELL " The solid oak study door to the south is closed but unlocked.">)
                  (T
-                  <TELL " A door to the south stands locked.">)>
-           <CR>)>>
+                  <TELL " The solid oak study door to the south is closed and locked.">)>
+           <COND (<AND ,INSPECTOR-PRESENT <IN? ,INSPECTOR ,ASHWORTH-ENTRANCE-HALL>>
+                  <TELL " Inspector Lestrade has arrived beneath the chandelier, notebook open.">)>
+           <COND (<==? ,CASE-ACT 2>
+                  <TELL " The servant-bell wire still quivers faintly from the opening of the hidden passage.">)>
+           <COND (<IN? ,DR-MORIARTY ,ASHWORTH-ENTRANCE-HALL>
+                  <TELL " Dr. Moriarty stands near the front door, watching the fog as if measuring his route through it.">)>
+           <CRLF>)>>
 
 ; --- Global Object Actions ---
 
@@ -388,36 +608,61 @@
 
 <ROUTINE MR-HUDSON-F ()
     <COND (<VERB? EXAMINE>
-           <TELL "Mr. Hudson, the butler, stands nervously. His expression is troubled." CR>
+           <COND (<==? ,CASE-ACT 3>
+                  <TELL "Mr. Hudson stands beside a packed carpetbag, coat buttoned wrong in his haste. He looks relieved to see that you noticed." CR>)
+                 (,HUDSON-CONFRONTED
+                  <TELL "Mr. Hudson has stopped polishing the same spoon. His hands are steady now, though he keeps the incriminating letter at arm's length." CR>)
+                 (T
+                  <TELL "Mr. Hudson polishes one silver spoon over and over; the cloth squeaks each time his hand tightens." CR>)>
            <RTRUE>)
-          (<VERB? ASK>
-           <COND (<OR <IN? ,PRSO ,INTQUOTE> <IN? ,PRSO ,QUOTE>>
+          (<VERB? TELL>
+           <COND (<NOT ,PRSI>
+                  <TELL "What do you want to ask Mr. Hudson about?" CR>
+                  <RTRUE>)
+                 (<EQUAL? ,PRSI ,MASTER-TOPIC>
+                  <TELL "Lord Ashworth had enemies, sir. Dr. Moriarty visited often, and their arguments grew worse." CR>
+                  <RTRUE>)
+                 (<EQUAL? ,PRSI ,ALIBI-TOPIC>
+                  <TELL "I was in the servants' quarters all evening. The other staff can confirm it." CR>
+                  <COND (<NOT ,HUDSON-INTERVIEWED>
+                         <SETG HUDSON-INTERVIEWED T>
+                         <SETG SUSPECTS-INTERVIEWED <+ ,SUSPECTS-INTERVIEWED 1>>
+                         <CHECK-CASE-PROGRESS>)>
+                  <RTRUE>)
+                 (<EQUAL? ,PRSI ,KEY-TOPIC>
+                  <TELL "You'll need the study key. He hands you the keyring." CR>
+                 <COND (<NOT ,HUDSON-KEY-GIVEN>
+                         <SETG HUDSON-KEY-GIVEN T>
+                         <MOVE ,KEYRING ,WINNER>)>
+                  <RTRUE>)
+                 (<EQUAL? ,PRSI ,MORIARTY-TOPIC>
+                  <TELL "Dr. Moriarty visited often. He and the master had serious disagreements." CR>
+                  <RTRUE>)
+                 (<OR <IN? ,PRSI ,INTQUOTE> <IN? ,PRSI ,QUOTE>>
                   <TELL "I'm not sure what you mean." CR>
                   <RTRUE>)
-                 (<EQUAL? ,PRSO ,ROOMS>
+                 (<EQUAL? ,PRSI ,ROOMS>
                   <TELL "I'm in the servants' quarters." CR>
                   <RTRUE>)
-                 (<EQUAL? ,PRSO ,MR-HUDSON>
+                 (<EQUAL? ,PRSI ,MR-HUDSON>
                   <TELL "Yes? What is it?" CR>
                   <RTRUE>)
-                 (<EQUAL? ,PRSO ,LADY-ASHWORTH>
+                 (<EQUAL? ,PRSI ,LADY-ASHWORTH>
                   <TELL "Lady Ashworth? She was in the drawing room, I believe." CR>
                   <RTRUE>)
-                 (<EQUAL? ,PRSO ,DR-MORIARTY>
+                 (<EQUAL? ,PRSI ,DR-MORIARTY>
                   <TELL "Dr. Moriarty? He visited often. He and the master had... disagreements." CR>
-                   <SETG MORIARTY-INTERVIEWED T>
-                   <SETG SUSPECTS-INTERVIEWED <+ ,SUSPECTS-INTERVIEWED 1>>
                    <RTRUE>)
-                 (<EQUAL? ,PRSO ,DEAD-LETTER>
+                 (<EQUAL? ,PRSI ,DEAD-LETTER>
                   <TELL "A letter? I know nothing of such things." CR>
                   <RTRUE>)
-                 (<EQUAL? ,PRSO ,BLOOD-STAINED-KNIFE>
+                 (<EQUAL? ,PRSI ,BLOOD-STAINED-KNIFE>
                   <TELL "A knife? I don't recognize it." CR>
                   <RTRUE>)
-                 (<EQUAL? ,PRSO ,POISON-BOTTLE>
+                 (<EQUAL? ,PRSI ,POISON-BOTTLE>
                   <TELL "Poison? I would never touch such things." CR>
                   <RTRUE>)
-                 (<EQUAL? ,PRSO ,KEYRING>
+                 (<EQUAL? ,PRSI ,KEYRING>
                   <TELL "The keyring? I suppose you'll need this." <COND (,HUDSON-KEY-GIVEN
                                                                           " You already have it.")
                                                                          (T
@@ -428,16 +673,13 @@
                  (T
                   <TELL "I don't know anything about that." CR>
                   <RTRUE>)>)
-          (<VERB? TELL>
-           <COND (<EQUAL? ,PRSO ,MR-HUDSON>
-                  <TELL "Yes? What is it?" CR>
-                  <RTRUE>)
-                 (T
-                  <TELL "I'm not sure I understand." CR>
-                  <RTRUE>)>)
-          (<VERB? SHOW>
+          (<VERB? SHOW GIVE>
            <COND (<EQUAL? ,PRSO ,DEAD-LETTER>
-                  <TELL "Mr. Hudson reads the letter. 'Where did you get that?' he asks, his face pale." CR>
+                  <COND (,HUDSON-CONFRONTED
+                         <TELL "Hudson does not touch the letter again. 'I remember the hour, sir. Nine twenty. And Moriarty on the stair behind me.'" CR>)
+                        (T
+                         <SETG HUDSON-CONFRONTED T>
+                         <TELL "Mr. Hudson's polishing cloth goes still. 'I carried that letter to the study,' he says. 'Moriarty followed me upstairs. I kept silent because I feared I had delivered Lord Ashworth's death.'" CR>)>
                   <RTRUE>)
                  (<EQUAL? ,PRSO ,BLOOD-STAINED-KNIFE>
                   <TELL "Mr. Hudson recoils. 'I've never seen that before.'" CR>
@@ -445,54 +687,71 @@
                  (<EQUAL? ,PRSO ,POISON-BOTTLE>
                   <TELL "Mr. Hudson's eyes widen. 'Poison? I know nothing of poison.'" CR>
                   <RTRUE>)
+                 (<EQUAL? ,PRSO ,FOOTPRINT-CAST>
+                  <TELL "Hudson sets his broad work boot beside the cast without being asked. 'Not mine, sir. And the doctor's right heel always catches on the stair carpet.'" CR>
+                  <RTRUE>)
                  (T
                   <TELL "Mr. Hudson examines the item. 'I don't see how that's relevant.'" CR>
                   <RTRUE>)>)>>
 
 <ROUTINE LADY-ASHWORTH-F ()
     <COND (<VERB? EXAMINE>
-           <TELL "Lady Ashworth sits at the dining table, her expression cold and calculating." CR>
+           <COND (<==? ,CASE-ACT 3>
+                  <TELL "Lady Ashworth has removed the black ribbon from her throat and laid it beside the empty plate. She watches the hall, listening for Lestrade's boots." CR>)
+                 (,LADY-CONFRONTED
+                  <TELL "Lady Ashworth's untouched place setting has been pushed aside. One hand grips her wedding ring; the other is open on the table, no longer hiding its tremor." CR>)
+                 (T
+                  <TELL "Lady Ashworth sits before two place settings. Her soup has filmed over, and her knife remains precisely parallel to the plate." CR>)>
            <RTRUE>)
-          (<VERB? ASK>
-           <COND (<OR <IN? ,PRSO ,INTQUOTE> <IN? ,PRSO ,QUOTE>>
+          (<VERB? TELL>
+           <COND (<NOT ,PRSI>
+                  <TELL "What do you want to ask Lady Ashworth about?" CR>
+                  <RTRUE>)
+                 (<EQUAL? ,PRSI ,MARRIAGE-TOPIC>
+                  <TELL "Our marriage was difficult, but I did not kill my husband." CR>
+                  <RTRUE>)
+                 (<EQUAL? ,PRSI ,ALIBI-TOPIC>
+                  <TELL "I was in the drawing room all evening. The servants saw me there." CR>
+                  <SETG LADY-ALIBI-CLAIMED T>
+                  <COND (<NOT ,LADY-INTERVIEWED>
+                         <SETG LADY-INTERVIEWED T>
+                         <SETG SUSPECTS-INTERVIEWED <+ ,SUSPECTS-INTERVIEWED 1>>
+                         <CHECK-CASE-PROGRESS>)>
+                  <RTRUE>)
+                 (<OR <IN? ,PRSI ,INTQUOTE> <IN? ,PRSI ,QUOTE>>
                   <TELL "I'm not sure what you mean." CR>
                   <RTRUE>)
-                 (<EQUAL? ,PRSO ,ROOMS>
+                 (<EQUAL? ,PRSI ,ROOMS>
                   <TELL "I was in the drawing room all evening." CR>
                   <RTRUE>)
-                 (<EQUAL? ,PRSO ,LADY-ASHWORTH>
+                 (<EQUAL? ,PRSI ,LADY-ASHWORTH>
                   <TELL "Yes? What is it?" CR>
                   <RTRUE>)
-                 (<EQUAL? ,PRSO ,DR-MORIARTY>
+                 (<EQUAL? ,PRSI ,DR-MORIARTY>
                   <TELL "Dr. Moriarty was a frequent guest. My husband owed him money." CR>
-                   <SETG MORIARTY-INTERVIEWED T>
-                   <SETG SUSPECTS-INTERVIEWED <+ ,SUSPECTS-INTERVIEWED 1>>
                    <RTRUE>)
-                 (<EQUAL? ,PRSO ,MR-HUDSON>
+                 (<EQUAL? ,PRSI ,MR-HUDSON>
                   <TELL "Mr. Hudson? He's been with the household for years. Loyal, but nervous." CR>
                   <RTRUE>)
-                 (<EQUAL? ,PRSO ,DEAD-LETTER>
+                 (<EQUAL? ,PRSI ,DEAD-LETTER>
                   <TELL "A letter? Where did you get that?" CR>
                   <RTRUE>)
-                 (<EQUAL? ,PRSO ,BLOOD-STAINED-KNIFE>
+                 (<EQUAL? ,PRSI ,BLOOD-STAINED-KNIFE>
                   <TELL "A knife? I don't know anything about it." CR>
                   <RTRUE>)
-                 (<EQUAL? ,PRSO ,POISON-BOTTLE>
+                 (<EQUAL? ,PRSI ,POISON-BOTTLE>
                   <TELL "Poison? I know nothing of such things." CR>
                   <RTRUE>)
                  (T
                   <TELL "I don't know anything about that." CR>
                   <RTRUE>)>)
-          (<VERB? TELL>
-           <COND (<EQUAL? ,PRSO ,LADY-ASHWORTH>
-                  <TELL "Yes? What is it?" CR>
-                  <RTRUE>)
-                 (T
-                  <TELL "I'm not sure I understand." CR>
-                  <RTRUE>)>)
-          (<VERB? SHOW>
+          (<VERB? SHOW GIVE>
            <COND (<EQUAL? ,PRSO ,DEAD-LETTER>
-                  <TELL "Lady Ashworth reads the letter. 'Where did you get that?' she asks, her composure cracking." CR>
+                  <COND (,LADY-CONFRONTED
+                         <TELL "Lady Ashworth presses one finger to the old fold. 'The first draft named the laboratory account as well. I remember the sum: five hundred pounds.'" CR>)
+                        (T
+                         <SETG LADY-CONFRONTED T>
+                         <TELL "Lady Ashworth reads the threat twice. The paper rattles against her ring. 'My husband meant to expose Moriarty tonight,' she says. 'I burned the first draft. I could not burn this one.'" CR>)>
                   <RTRUE>)
                  (<EQUAL? ,PRSO ,BLOOD-STAINED-KNIFE>
                   <TELL "Lady Ashworth recoils. 'I've never seen that before.'" CR>
@@ -500,59 +759,84 @@
                  (<EQUAL? ,PRSO ,POISON-BOTTLE>
                   <TELL "Lady Ashworth's eyes widen. 'Poison? I know nothing of poison.'" CR>
                   <RTRUE>)
+                 (<EQUAL? ,PRSO ,WAX-SEAL>
+                  <TELL "Lady Ashworth turns the seal toward the light. 'Moriarty sealed every private delivery with that mark. My husband hated the theatricality of it.'" CR>
+                  <RTRUE>)
                  (T
                   <TELL "Lady Ashworth examines the item. 'I don't see how that's relevant.'" CR>
                   <RTRUE>)>)>>
 
 <ROUTINE DR-MORIARTY-F ()
     <COND (<VERB? EXAMINE>
-           <TELL "Dr. Moriarty stands by the bookshelf, his expression arrogant and dismissive." CR>
+          <COND (<==? ,CASE-ACT 3>
+                  <COND (,FOOTPRINT-DETAIL-FOUND
+                         <TELL "Dr. Moriarty has abandoned the library for the front door. Mud freckles his polished boots; the crescent nick in his right heel matches the detail you found in the garden cast." CR>)
+                        (T
+                         <TELL "Dr. Moriarty has abandoned the library for the front door. Mud freckles his polished size-ten boots, and he keeps the right heel turned away from you." CR>)>)
+                 (,MORIARTY-CONFRONTED
+                  <TELL "A crescent of sweat darkens Dr. Moriarty's collar. His gloved right hand stays in his coat pocket while his eyes count the doors." CR>)
+                 (T
+                  <TELL "Dr. Moriarty stands by the scientific folios, one immaculate fingernail tapping a steady four-beat rhythm." CR>)>
            <RTRUE>)
-          (<VERB? ASK>
-           <COND (<OR <IN? ,PRSO ,INTQUOTE> <IN? ,PRSO ,QUOTE>>
+          (<VERB? TELL>
+           <COND (<NOT ,PRSI>
+                  <TELL "What do you want to ask Dr. Moriarty about?" CR>
+                  <RTRUE>)
+                 (<EQUAL? ,PRSI ,EXPERIMENTS-TOPIC>
+                  <TELL "My experiments concern medicinal plants. Lord Ashworth financed some of the work." CR>
+                  <RTRUE>)
+                 (<OR <EQUAL? ,PRSI ,POISON-TOPIC>
+                      <EQUAL? ,PRSI ,POISON-BOTTLE>>
+                  <TELL "Wolfsbane? Aconitum? I keep some for research. That proves nothing." CR>
+                  <SETG MORIARTY-POISON-KNOWN T>
+                  <SETG MORIARTY-CONFRONTED T>
+                  <COND (<NOT ,MORIARTY-INTERVIEWED>
+                         <SETG MORIARTY-INTERVIEWED T>
+                         <SETG SUSPECTS-INTERVIEWED <+ ,SUSPECTS-INTERVIEWED 1>>
+                         <CHECK-CASE-PROGRESS>)>
+                  <MOVE ,DR-MORIARTY ,ASHWORTH-ENTRANCE-HALL>
+                  <RTRUE>)
+                 (<OR <IN? ,PRSI ,INTQUOTE> <IN? ,PRSI ,QUOTE>>
                   <TELL "I'm not sure what you mean." CR>
                   <RTRUE>)
-                 (<EQUAL? ,PRSO ,ROOMS>
+                 (<EQUAL? ,PRSI ,ROOMS>
                   <TELL "I was at my laboratory all evening. Ask my assistant." CR>
                   <RTRUE>)
-                 (<EQUAL? ,PRSO ,DR-MORIARTY>
+                 (<EQUAL? ,PRSI ,DR-MORIARTY>
                   <TELL "Yes? What is it?" CR>
                   <RTRUE>)
-                 (<EQUAL? ,PRSO ,LADY-ASHWORTH>
+                 (<EQUAL? ,PRSI ,LADY-ASHWORTH>
                   <TELL "Lady Ashworth? She's a fine woman, trapped in a difficult marriage." CR>
                   <RTRUE>)
-                 (<EQUAL? ,PRSO ,MR-HUDSON>
+                 (<EQUAL? ,PRSI ,MR-HUDSON>
                   <TELL "Mr. Hudson? He's a servant. What about him?" CR>
                   <RTRUE>)
-                 (<EQUAL? ,PRSO ,DEAD-LETTER>
+                 (<EQUAL? ,PRSI ,DEAD-LETTER>
                   <TELL "A letter? I don't know anything about it." CR>
                   <RTRUE>)
-                 (<EQUAL? ,PRSO ,BLOOD-STAINED-KNIFE>
+                 (<EQUAL? ,PRSI ,BLOOD-STAINED-KNIFE>
                   <TELL "A knife? I use surgical tools in my work. That's not one of them." CR>
                   <RTRUE>)
-                 (<EQUAL? ,PRSO ,POISON-BOTTLE>
+                 (<EQUAL? ,PRSI ,POISON-BOTTLE>
                   <TELL "Wolfsbane? Aconitum? I have some in my greenhouse. For research." CR>
                    <SETG MORIARTY-POISON-KNOWN T>
                    <RTRUE>)
-                 (<EQUAL? ,PRSO ,SECRET-LEDGER>
+                 (<EQUAL? ,PRSI ,SECRET-LEDGER>
                   <TELL "A ledger? I don't know what you're talking about." CR>
                   <RTRUE>)
-                 (<EQUAL? ,PRSO ,BANK-STATEMENT>
+                 (<EQUAL? ,PRSI ,BANK-STATEMENT>
                   <TELL "A bank statement? That's private information." CR>
                   <RTRUE>)
                  (T
                   <TELL "I don't know anything about that." CR>
                   <RTRUE>)>)
-          (<VERB? TELL>
-           <COND (<EQUAL? ,PRSO ,DR-MORIARTY>
-                  <TELL "Yes? What is it?" CR>
-                  <RTRUE>)
-                 (T
-                  <TELL "I'm not sure I understand." CR>
-                  <RTRUE>)>)
-          (<VERB? SHOW>
+          (<VERB? SHOW GIVE>
            <COND (<EQUAL? ,PRSO ,DEAD-LETTER>
-                  <TELL "Dr. Moriarty reads the letter. 'Where did you get that?' he asks, his composure cracking." CR>
+                  <COND (,MORIARTY-CONFRONTED
+                         <TELL "Moriarty refuses the letter. 'You have already performed that trick.' His eyes still return to the signature." CR>)
+                        (T
+                         <SETG MORIARTY-CONFRONTED T>
+                         <TELL "Dr. Moriarty reads only the first line before folding the letter along its old crease. 'Blackmail,' he says too quickly. You never told him what it contained." CR>)>
                   <RTRUE>)
                  (<EQUAL? ,PRSO ,BLOOD-STAINED-KNIFE>
                   <TELL "Dr. Moriarty recoils. 'I've never seen that before.'" CR>
@@ -566,73 +850,90 @@
                  (<EQUAL? ,PRSO ,BANK-STATEMENT>
                   <TELL "Dr. Moriarty reads the statement. 'That's private information!'" CR>
                   <RTRUE>)
+                 (<EQUAL? ,PRSO ,FOOTPRINT-CAST>
+                  <COND (,FOOTPRINT-DETAIL-FOUND
+                         <TELL "Moriarty glances at the crescent nick in the cast, then slides his right boot behind the left. 'Plaster shrinks,' he says. You had not mentioned the defect." CR>)
+                        (T
+                         <TELL "Moriarty looks from the size-ten cast to his own polished boots. 'A common size,' he says, keeping his right heel flat to the floor." CR>)>
+                  <RTRUE>)
                  (T
                   <TELL "Dr. Moriarty examines the item. 'I don't see how that's relevant.'" CR>
                   <RTRUE>)>)>>
 
 <ROUTINE INSPECTOR-F ()
     <COND (<VERB? EXAMINE>
-           <TELL "Inspector Lestrade of Scotland Yard stands in the entrance hall, his expression professional and skeptical." CR>
+           <COND (<AND ,LETTER-PRESENTED ,POISON-PRESENTED ,MOTIVE-PRESENTED>
+                  <TELL "Inspector Lestrade has filled three pages of his notebook. His pencil now rests beneath the words THREAT, METHOD, and MOTIVE." CR>)
+                 (T
+                  <TELL "Inspector Lestrade stands beneath the chandelier with rain silvering his shoulders. His notebook is open to a clean page." CR>)>
            <RTRUE>)
-          (<VERB? ASK>
-           <COND (<OR <IN? ,PRSO ,INTQUOTE> <IN? ,PRSO ,QUOTE>>
+          (<VERB? TELL>
+           <COND (<NOT ,PRSI>
+                  <TELL "What do you want to ask Inspector Lestrade about?" CR>
+                  <RTRUE>)
+                 (<EQUAL? ,PRSI ,CASE-TOPIC>
+                  <TELL "Give me the case as a chain, not a sack of objects: show me the threat, the method, and the motive. Then accuse your suspect and choose which proof leads the charge." CR>
+                  <RTRUE>)
+                 (<OR <IN? ,PRSI ,INTQUOTE> <IN? ,PRSI ,QUOTE>>
                   <TELL "I'm not sure what you mean." CR>
                   <RTRUE>)
-                 (<EQUAL? ,PRSO ,ROOMS>
+                 (<EQUAL? ,PRSI ,ROOMS>
                   <TELL "What have you found, detective?" CR>
                   <RTRUE>)
-                 (<EQUAL? ,PRSO ,INSPECTOR>
+                 (<EQUAL? ,PRSI ,INSPECTOR>
                   <TELL "Yes? What is it?" CR>
                   <RTRUE>)
-                 (<EQUAL? ,PRSO ,DR-MORIARTY>
+                 (<EQUAL? ,PRSI ,DR-MORIARTY>
                   <TELL "Dr. Moriarty? A respected scientist. You'll need strong evidence." CR>
                   <RTRUE>)
-                 (<EQUAL? ,PRSO ,LADY-ASHWORTH>
+                 (<EQUAL? ,PRSI ,LADY-ASHWORTH>
                   <TELL "Lady Ashworth? She has an alibi. What evidence do you have?" CR>
                   <RTRUE>)
-                 (<EQUAL? ,PRSO ,MR-HUDSON>
+                 (<EQUAL? ,PRSI ,MR-HUDSON>
                   <TELL "Mr. Hudson? He was in the servants' quarters. What evidence do you have?" CR>
                   <RTRUE>)
-                 (<EQUAL? ,PRSO ,DEAD-LETTER>
+                 (<EQUAL? ,PRSI ,DEAD-LETTER>
                   <TELL "A letter? Let me see it." CR>
                   <RTRUE>)
-                 (<EQUAL? ,PRSO ,BLOOD-STAINED-KNIFE>
+                 (<EQUAL? ,PRSI ,BLOOD-STAINED-KNIFE>
                   <TELL "A knife? Let me see it." CR>
                   <RTRUE>)
-                 (<EQUAL? ,PRSO ,POISON-BOTTLE>
+                 (<EQUAL? ,PRSI ,POISON-BOTTLE>
                   <TELL "Poison? Let me see it." CR>
                   <RTRUE>)
-                 (<EQUAL? ,PRSO ,SECRET-LEDGER>
+                 (<EQUAL? ,PRSI ,SECRET-LEDGER>
                   <TELL "A ledger? Let me see it." CR>
                   <RTRUE>)
-                 (<EQUAL? ,PRSO ,BANK-STATEMENT>
+                 (<EQUAL? ,PRSI ,BANK-STATEMENT>
                   <TELL "A bank statement? Let me see it." CR>
                   <RTRUE>)
                  (T
                   <TELL "I don't know anything about that." CR>
                   <RTRUE>)>)
-          (<VERB? TELL>
-           <COND (<EQUAL? ,PRSO ,INSPECTOR>
-                  <TELL "Yes? What is it?" CR>
-                  <RTRUE>)
-                 (T
-                  <TELL "I'm not sure I understand." CR>
-                  <RTRUE>)>)
-          (<VERB? SHOW>
+          (<VERB? SHOW GIVE>
            <COND (<EQUAL? ,PRSO ,DEAD-LETTER>
-                  <TELL "The inspector reads the letter. 'This is damning evidence.'" CR>
+                  <SETG LETTER-PRESENTED T>
+                  <TELL "The inspector reads Ashworth's threat and underlines Moriarty's name. 'Intent and opportunity to silence him. That is the first link.'" CR>
                   <RTRUE>)
                  (<EQUAL? ,PRSO ,BLOOD-STAINED-KNIFE>
                   <TELL "The inspector examines the knife. 'The knife matches the wound. And it's from Moriarty's collection.'" CR>
                   <RTRUE>)
                  (<EQUAL? ,PRSO ,POISON-BOTTLE>
-                  <TELL "The inspector reads the label. 'Wolfsbane. Rare poison. Only Moriarty had access.'" CR>
+                  <SETG POISON-PRESENTED T>
+                  <TELL "The inspector compares the wolfsbane label with your greenhouse notes. 'A poison he admits keeping, delivered through a locked-room trick. The second link.'" CR>
                   <RTRUE>)
                  (<EQUAL? ,PRSO ,SECRET-LEDGER>
                   <TELL "The inspector reads the ledger. 'And the ledger shows he was being blackmailed. Case closed.'" CR>
                   <RTRUE>)
                  (<EQUAL? ,PRSO ,BANK-STATEMENT>
-                  <TELL "The inspector reads the statement. 'Moriarty owed the victim money. Motive established.'" CR>
+                  <SETG MOTIVE-PRESENTED T>
+                  <TELL "The inspector lays the statement beside the secret ledger. 'The same five hundred pounds in both records. Debt and blackmail: motive. The chain is complete.'" CR>
+                  <RTRUE>)
+                 (<EQUAL? ,PRSO ,FOOTPRINT-CAST>
+                  <COND (,FOOTPRINT-DETAIL-FOUND
+                         <TELL "Lestrade compares the cast with Moriarty's right boot. The two crescent nicks meet edge for edge. 'Route evidence,' he says, drawing a line from GARDEN to STUDY." CR>)
+                        (T
+                         <TELL "Lestrade measures the cast. 'Size ten narrows matters, but inspect the wear before you call it individual evidence.'" CR>)>
                   <RTRUE>)
                  (T
                   <TELL "The inspector examines the item. 'I don't see how that's relevant.'" CR>
@@ -640,25 +941,6 @@
 
 ; === VERB ACTIONS ===
 
-<ROUTINE V-EXAMINE ()
-    <COND (<FSET? ,PRSO ,SCENERY>
-           <PERFORM ,V?EXAMINE ,PRSO>
-           <RTRUE>)
-          (<FSET? ,PRSO ,NPC>
-           <PERFORM ,V?EXAMINE ,PRSO>
-           <RTRUE>)
-          (T
-           <TELL "You examine the " D ,PRSO ". " <GETP ,PRSO ,P?LDESC> CR>
-           <RTRUE>)>>
-
-<ROUTINE V-READ ()
-    <COND (<FSET? ,PRSO ,READBIT>
-           <PERFORM ,V?READ ,PRSO>
-           <RTRUE>)
-          (T
-           <TELL "You can't read that." CR>
-           <RTRUE>)>>
-
 <ROUTINE V-TAKE ()
     <COND (<FSET? ,PRSO ,TAKEBIT>
            <MOVE ,PRSO ,WINNER>
@@ -685,57 +967,84 @@
     <TELL "You can't use that on that." CR>
     <RTRUE>>
 
-<ROUTINE V-OPEN ()
-    <COND (<FSET? ,PRSO ,CONTAINERBIT>
-           <PERFORM ,V?OPEN ,PRSO>
+<ROUTINE V-EAT ()
+    <COND (<EQUAL? ,PRSO ,POISON-BOTTLE>
+           <TELL "A bitter trace touches your tongue. Your vision swims and your pulse stumbles; perhaps that wasn't wise." CR>
+           <SETG PLAYER-HEALTH <- ,PLAYER-HEALTH 1>>
+           <COND (<==? ,PLAYER-HEALTH 0>
+                  <TELL "You collapse. Everything goes dark." CR>
+                  <SETG GAME-LOST T>
+                  <SETG GAME-ENDED T>
+                  <QUIT>)>
            <RTRUE>)
           (T
-           <TELL "You can't open that." CR>
+           <TELL "Tasting the " D ,PRSO " would tell you nothing useful." CR>
            <RTRUE>)>>
 
-<ROUTINE V-CLOSE ()
-    <COND (<FSET? ,PRSO ,CONTAINERBIT>
-           <PERFORM ,V?CLOSE ,PRSO>
+<ROUTINE V-SHOW ()
+    <TELL "The " D ,PRSI " doesn't seem interested." CR>
+    <RTRUE>>
+
+<ROUTINE V-OPEN ()
+    <COND (<OR <FSET? ,PRSO ,CONTBIT>
+               <FSET? ,PRSO ,DOORBIT>>
+           <COND (<FSET? ,PRSO ,OPENBIT>
+                  <TELL "The " D ,PRSO " is already open." CR>)
+                 (T
+                  <FSET ,PRSO ,OPENBIT>
+                  <TELL "You open the " D ,PRSO "." CR>
+                  <COND (<FSET? ,PRSO ,CONTBIT>
+                         <V-LOOK-INSIDE>)>)>
            <RTRUE>)
           (T
-           <TELL "You can't close that." CR>
+           <TELL "You can't open that." CR>
            <RTRUE>)>>
 
-<ROUTINE V-PUSH ()
-    <COND (<EQUAL? ,PRSO ,BOOKSHELF>
-           <PERFORM ,V?PUSH ,BOOKSHELF>
+<ROUTINE V-CLOSE ()
+    <COND (<OR <FSET? ,PRSO ,CONTBIT>
+               <FSET? ,PRSO ,DOORBIT>>
+           <COND (<FSET? ,PRSO ,OPENBIT>
+                  <FCLEAR ,PRSO ,OPENBIT>
+                  <TELL "You close the " D ,PRSO "." CR>)
+                 (T
+                  <TELL "The " D ,PRSO " is already closed." CR>)>
            <RTRUE>)
           (T
-           <TELL "You can't push that." CR>
+           <TELL "You can't close that." CR>
            <RTRUE>)>>
 
-<ROUTINE V-ASK ()
-    <PERFORM ,V?ASK ,PRSO ,PRSI>
-    <RTRUE>>
-
-<ROUTINE V-TELL ()
-    <PERFORM ,V?TELL ,PRSO ,PRSI>
-    <RTRUE>>
-
-<ROUTINE V-SHOW-TO ()
-    <PERFORM ,V?SHOW ,PRSI ,PRSO>
-    <RTRUE>>
-
 <ROUTINE V-ACCUSE ()
     <COND (<EQUAL? ,PRSO ,DR-MORIARTY>
-           <COND (<AND <==? ,EVIDENCE-FOUND 5>
-                       <==? ,SUSPECTS-INTERVIEWED 3>>
-                  <TELL "Dr. Moriarty, you are under arrest for the murder of Lord Ashworth." CR>
+           <COND (<NOT ,INSPECTOR-PRESENT>
+                  <TELL "An accusation shouted into an empty hall is only theatre. Finish the interviews and gather a coherent case; Lestrade will come." CR>
+                  <RTRUE>)
+                 (<NOT <AND ,LETTER-PRESENTED ,POISON-PRESENTED ,MOTIVE-PRESENTED>>
+                  <TELL "Lestrade closes his notebook. 'You have discoveries, but not yet an argument. Show me the threat, the poison, and the financial motive.'" CR>
+                  <RTRUE>)
+                 (<NOT ,PRSI>
+                  <TELL "Lestrade nods toward your evidence. 'Which proof leads the charge? ACCUSE MORIARTY WITH LETTER for Ashworth's own voice, or ACCUSE MORIARTY WITH POISON for the physical case.'" CR>
+                  <RTRUE>)
+                 (<OR <EQUAL? ,PRSI ,DEAD-LETTER>
+                      <EQUAL? ,PRSI ,POISON-BOTTLE>>
+                  <COND (<EQUAL? ,PRSI ,DEAD-LETTER>
+                         <TELL "You lead with Ashworth's unsent letter. Moriarty calls it a forgery; then Hudson quietly repeats the hour he delivered it and Lady Ashworth supplies the missing first draft." CR>)
+                        (T
+                         <TELL "You lead with the wolfsbane. Moriarty names its precise concentration before Lestrade has uncorked it. The accidental confession leaves the hall very still." CR>)>
+                  <TELL CR "You connect the purple flowers in the greenhouse to the bottle in the sealed study, and the secret ledger to the bank statement hidden behind Moriarty's name dial.">
+                  <COND (,FOOTPRINT-DETAIL-FOUND
+                         <TELL " The crescent nick you found under the magnifying glass fits Moriarty's right heel; the surgical knife and his attempt to reach the door complete the route." CR>)
+                        (T
+                         <TELL " The size-ten footprint, the surgical knife, and his attempt to reach the door complete the route." CR>)>
+                  <TELL CR "'Dr. Moriarty,' Lestrade says, closing one cuff around the gloved wrist, 'you are under arrest for the murder of Lord Ashworth.'" CR>
                   <SETG KILLER-ACCUSED T>
                   <SETG CORRECT-ACCUSATION T>
                   <SETG GAME-WON T>
                   <SETG GAME-ENDED T>
-                  <TELL CR "Congratulations! You have solved the murder of Lord Ashworth." CR>
-                  <TELL "Dr. Moriarty has been arrested for the crime." CR>
-                  <TELL "Your reputation as a detective is secured." CR>
+                  <TELL CR "At dawn, the fog lifts enough to show ships moving on the Thames. Hudson brings tea for four without being asked. Lady Ashworth will testify; Lestrade offers you the next impossible file before the carriage has even taken Moriarty away." CR>
+                  <TELL CR "THE LIMEHOUSE KILLINGS -- SOLVED" CR>
                   <QUIT>)
                  (T
-                  <TELL "You don't have enough evidence to make that accusation." CR>
+                  <TELL "That may be evidence, but it does not make the clearest opening proof. Choose the letter or the poison." CR>
                   <RTRUE>)>)
           (<EQUAL? ,PRSO ,LADY-ASHWORTH>
            <TELL "Lady Ashworth has an alibi. The evidence doesn't match." CR>
@@ -772,10 +1081,13 @@
 
 <ROUTINE V-GO-SOUTH ()
     <COND (<==? ,HERE ,ASHWORTH-ENTRANCE-HALL>
-           <COND (,STUDY-UNLOCKED
+           <COND (<FSET? ,STUDY-DOOR ,OPENBIT>
                   <SETG HERE ,STUDY>
                   <TELL "You enter the study." CR>
                   <RTRUE>)
+                 (,STUDY-UNLOCKED
+                  <TELL "The study door is closed." CR>
+                  <RTRUE>)
                  (T
                   <TELL "The study door is locked." CR>
                   <RTRUE>)>)
@@ -788,8 +1100,11 @@
            <TELL "You return to the garden." CR>
            <RTRUE>)
           (<==? ,HERE ,LIBRARY>
-           <SETG HERE ,SECRET-PASSAGE>
-           <TELL "You enter the secret passage." CR>
+           <COND (,CIPHER-SOLVED
+                  <SETG HERE ,SECRET-PASSAGE>
+                  <TELL "You enter the secret passage." CR>)
+                 (T
+                  <TELL "You can't go that way." CR>)>
            <RTRUE>)
           (T
            <TELL "You can't go that way." CR>
@@ -800,6 +1115,13 @@
            <SETG HERE ,LIBRARY>
            <TELL "You enter the library." CR>
            <RTRUE>)
+          (<==? ,HERE ,LIBRARY>
+           <COND (,CIPHER-SOLVED
+                  <SETG HERE ,SECRET-PASSAGE>
+                  <TELL "You enter the secret passage." CR>)
+                 (T
+                  <TELL "You can't go that way." CR>)>
+           <RTRUE>)
           (<==? ,HERE ,DINING-ROOM>
            <SETG HERE ,ASHWORTH-ENTRANCE-HALL>
            <TELL "You return to the entrance hall." CR>
@@ -870,24 +1192,31 @@
     <RTRUE>>
 
 <ROUTINE V-HINTS ()
-    <TELL "Hints are available. Type HINTS for help." CR>
+    <COND (<NOT ,STUDY-UNLOCKED>
+           <TELL "Hint: Mr. Hudson may know how to open the study." CR>)
+          (<NOT ,CIPHER-SOLVED>
+           <TELL "Hint: compare the torn page with the colored markers in the library." CR>)
+          (<NOT ,POISON-IDENTIFIED>
+           <TELL "Hint: compare the poison bottle with the labeled greenhouse plants." CR>)
+          (T
+           <TELL "Hint: gather the evidence, interview every suspect, and report to Inspector Lestrade." CR>)>
     <RTRUE>>
 
 ; === HELPER ROUTINES ===
 
 <ROUTINE PRINT-CONTENTS (OBJ)
     <COND (<FIRST? OBJ>
-           <PRINT-ITEMS OBJ>
+           <PRINT-ITEMS <FIRST? OBJ>>
            <RTRUE>)
           (T
            <TELL "  nothing." CR>
            <RTRUE>)>>
 
-<ROUTINE PRINT-ITEMS (OBJ)
-    <COND (<FIRST? OBJ>
-           <TELL "  " D <FIRST? OBJ> CR>
-           <PRINT-ITEMS <NEXT? <FIRST? OBJ>>>
-           <RTRUE>)>>
+<ROUTINE PRINT-ITEMS (ITEM)
+    <COND (<NOT .ITEM> <RTRUE>)
+          (T
+           <TELL "  " D .ITEM CR>
+           <PRINT-ITEMS <NEXT? .ITEM>>)>>
 
 ; === GLOBAL OBJECT ACTIONS ===
 
@@ -912,11 +1241,13 @@
 
 <ROUTINE SOLVE-CIPHER ()
     <COND (<AND <IN? ,TORN-PAGE ,WINNER>
-                <IN? ,COLORED-MARKERS ,HERE>>
+                <==? ,HERE ,LIBRARY>>
            <TELL "You arrange the books in rainbow order. The wall slides open, revealing a secret passage." CR>
            <SETG CIPHER-SOLVED T>
            <SETG SECRET-PASSAGE-FOUND T>
            <SETG SECRET-PASSAGE-OPEN T>
+           <SETG CASE-ACT 2>
+           <TELL CR "Somewhere in the manor a bell wire trembles. The investigation has changed: you are no longer searching for a room, but reconstructing what crossed its locked boundary." CR>
            <RTRUE>)
           (T
            <TELL "You need the torn page and colored markers to solve the cipher." CR>
@@ -927,32 +1258,54 @@
                 <IN? ,PLANTS ,HERE>>
            <TELL "You match the poison bottle label to the wolfsbane plant. The poison came from this greenhouse." CR>
            <SETG POISON-IDENTIFIED T>
+           <CHECK-CASE-PROGRESS>
            <RTRUE>)
           (T
            <TELL "You need the poison bottle and access to the greenhouse to identify the poison." CR>
            <RTRUE>)>>
 
+<ROUTINE CHECK-CASE-PROGRESS ()
+    <COND (<AND <G? ,EVIDENCE-FOUND 2>
+                <==? ,SUSPECTS-INTERVIEWED 3>
+                <NOT ,INSPECTOR-PRESENT>>
+           <SETG CASE-ACT 3>
+           <SETG INSPECTOR-PRESENT T>
+           <MOVE ,INSPECTOR ,ASHWORTH-ENTRANCE-HALL>
+           <TELL CR "From the entrance hall comes the slam of the outer door and Lestrade's clipped voice. Scotland Yard has arrived. Around the manor, private masks begin to slip." CR>)>
+    <RTRUE>>
+
 ; === END GAME ===
 
 <ROUTINE END-GAME ()
     <COND (,GAME-WON
-           <TELL CR "Congratulations! You have solved the murder of Lord Ashworth." CR>
-           <TELL "Dr. Moriarty has been arrested for the crime." CR>
-           <TELL "Your reputation as a detective is secured." CR>
+           <TELL CR "Dawn finds Moriarty in Lestrade's carriage, Lady Ashworth ready to testify, and Hudson pouring tea while ships emerge on the Thames." CR>
            <QUIT>)
           (,GAME-LOST
-           <TELL CR "The case remains unsolved. Better luck next time." CR>
+           <TELL CR "The evidence remains on the table while the house settles back into silence." CR>
            <QUIT>)
            (T
             <RTRUE>)>>
 
 ; === GAME ENTRY ===
 
+<SYNTAX USE OBJECT (HELD CARRIED ON-GROUND IN-ROOM) = V-USE>
+<SYNTAX USE OBJECT (HELD CARRIED ON-GROUND IN-ROOM) ON OBJECT (HELD CARRIED ON-GROUND IN-ROOM) = V-USE-ON>
+<SYNTAX SHOW OBJECT (HAVE) TO OBJECT (FIND ACTORBIT) (IN-ROOM) = V-SHOW>
+<SYNTAX HINTS = V-HINTS>
+<SYNONYM HINTS HINT>
+<SYNTAX ACCUSE OBJECT (FIND ACTORBIT) (IN-ROOM) = V-ACCUSE>
+<SYNTAX ACCUSE OBJECT (FIND ACTORBIT) (IN-ROOM) WITH OBJECT (HAVE) = V-ACCUSE>
+<SYNTAX LOOK AT OBJECT (HELD CARRIED ON-GROUND IN-ROOM) = V-EXAMINE>
+<SYNTAX SEARCH OBJECT (HELD CARRIED ON-GROUND IN-ROOM) = V-EXAMINE>
+
 <ROUTINE GO ()
 	<SETG HERE ,ASHWORTH-MANOR-GATE>
 	<SETG LIT T>
 	<SETG WINNER ,ADVENTURER>
 	<SETG PLAYER ,WINNER>
+	<VOC "SET" OBJECT>
+	<VOC "CAST" OBJECT>
+	<VOC "INSPECTOR" OBJECT>
 	<MOVE ,WINNER ,HERE>
 	<V-LOOK>
 	<MAIN-LOOP>>
diff --git a/books/limehouse-killings/dungeon.zil b/books/limehouse-killings/dungeon.zil
index 60edbba..72bfefe 100644
--- a/books/limehouse-killings/dungeon.zil
+++ b/books/limehouse-killings/dungeon.zil
@@ -11,6 +11,7 @@
 <GLOBAL SECRET-PASSAGE-FOUND <>>
 <GLOBAL SECRET-PASSAGE-OPEN <>>
 <GLOBAL CIPHER-SOLVED <>>
+<GLOBAL CIPHER-STAGE 0>
 <GLOBAL POISON-IDENTIFIED <>>
 <GLOBAL KILLER-ACCUSED <>>
 <GLOBAL CORRECT-ACCUSATION <>>
@@ -29,14 +30,25 @@
 <GLOBAL LOCKED-BOX-OPENED <>>
 <GLOBAL POISON-BOTTLE-FOUND <>>
 <GLOBAL SECRET-LEDGER-FOUND <>>
+<GLOBAL BANK-STATEMENT-FOUND <>>
 <GLOBAL PLAYER-HEALTH 3>
+<GLOBAL CASE-ACT 1>
+<GLOBAL HUDSON-CONFRONTED <>>
+<GLOBAL LADY-CONFRONTED <>>
+<GLOBAL MORIARTY-CONFRONTED <>>
+<GLOBAL BOX-CLUE-SEEN <>>
+<GLOBAL LETTER-PRESENTED <>>
+<GLOBAL POISON-PRESENTED <>>
+<GLOBAL MOTIVE-PRESENTED <>>
+<GLOBAL FOOTPRINT-DETAIL-FOUND <>>
+<GLOBAL CABINET-CLUE-SEEN <>>
 
 ; === ROOMS ===
 
 <ROOM ASHWORTH-MANOR-GATE
       (IN ROOMS)
       (DESC "Ashworth Manor Gate")
-      (LDESC "The iron gates of Ashworth Manor loom before you, their rusted bars silhouetted against the fog-choked sky. A gravel path leads north to the manor house, disappearing into the mist. The gas lamps along the path flicker weakly, casting long shadows that dance like specters. The air smells of coal smoke and river damp.")
+      (ACTION GATE-FCN)
       (NORTH TO ASHWORTH-ENTRANCE-HALL)
       (FLAGS RLANDBIT ONBIT)
       (GLOBAL FOG GATES PATH)>
@@ -45,38 +57,36 @@
       (IN ROOMS)
       (DESC "Ashworth Manor Entrance Hall")
       (ACTION ENTRANCE-HALL-FCN)
-      (LDESC "You step into a grand foyer that has seen better days. The air is thick with the scent of old wood and regret. Doorways lead in every direction -- north to the gate, east to the library, west to the dining room, and a staircase down to the kitchen. A door to the south stands locked.")
-      (SOUTH TO STUDY IF STUDY-UNLOCKED)
+      (SOUTH TO STUDY IF STUDY-DOOR IS OPEN ELSE "The study door is closed.")
       (NORTH TO ASHWORTH-MANOR-GATE)
       (EAST TO LIBRARY)
       (WEST TO DINING-ROOM)
       (DOWN TO KITCHEN)
       (FLAGS RLANDBIT ONBIT)
-      (GLOBAL CHANDELIER PORTRAITS RUG)>
+      (GLOBAL CHANDELIER PORTRAITS RUG STUDY-DOOR BELL-WIRE)>
 
 <ROOM STUDY
       (IN ROOMS)
       (DESC "Study")
       (ACTION STUDY-FCN)
-      (LDESC "The study is a crime scene. A chalk outline marks where the body lay, the victim struck down in this very room. The air hangs heavy with the memory of violence. A doorway leads north back to the entrance hall.")
-      (NORTH TO ASHWORTH-ENTRANCE-HALL)
+      (NORTH TO ASHWORTH-ENTRANCE-HALL IF STUDY-DOOR IS OPEN ELSE "The study door is closed.")
       (FLAGS RLANDBIT ONBIT)
-      (GLOBAL DESK FIREPLACE WINDOW CHALK-OUTLINE)>
+      (GLOBAL DESK FIREPLACE WINDOW CHALK-OUTLINE STUDY-DOOR)>
 
 <ROOM LIBRARY
       (IN ROOMS)
       (DESC "Library")
       (ACTION LIBRARY-FCN)
-      (LDESC "Floor-to-ceiling bookshelves line the walls, their contents ranging from leather-bound classics to modern scientific texts. The fire is cold, but the room retains a scholarly warmth. A doorway leads west back to the entrance hall.")
       (WEST TO ASHWORTH-ENTRANCE-HALL)
       (EAST TO SECRET-PASSAGE IF CIPHER-SOLVED)
+      (SOUTH TO SECRET-PASSAGE IF CIPHER-SOLVED)
       (FLAGS RLANDBIT ONBIT)
       (GLOBAL BOOKSHELF READING-DESK FIREPLACE COLORED-MARKERS)>
 
 <ROOM DINING-ROOM
       (IN ROOMS)
       (DESC "Dining Room")
-      (LDESC "A long dining table dominates the room, set for two but used by only one. Portraits of the family hang above, their expressions disapproving. The air smells of polish and unused cutlery. A doorway leads east back to the entrance hall, and a door to the north leads to the pantry.")
+      (ACTION DINING-ROOM-FCN)
       (EAST TO ASHWORTH-ENTRANCE-HALL)
       (NORTH TO PANTRY)
       (FLAGS RLANDBIT ONBIT)
@@ -86,17 +96,15 @@
       (IN ROOMS)
       (DESC "Kitchen")
       (ACTION KITCHEN-FCN)
-      (LDESC "A kitchen that has seen better days. The hearth is cold, its last fire long extinguished. A staircase leads up to the entrance hall, and a doorway west leads to the garden.")
       (UP TO ASHWORTH-ENTRANCE-HALL)
       (WEST TO GARDEN)
       (FLAGS RLANDBIT ONBIT)
-      (GLOBAL POTS HEARTH SERVANT-BELL DRAWER)>
+      (GLOBAL POTS HEARTH SERVANT-BELL DRAWER KETTLE)>
 
 <ROOM GARDEN
       (IN ROOMS)
       (DESC "Garden")
       (ACTION GARDEN-FCN)
-      (LDESC "An overgrown garden sprawls before you, its paths choked with weeds. A fountain stands at the center, dry and silent. Hedge mazes line the paths, their shadows hiding secrets. A doorway east leads to the kitchen, paths lead north to the greenhouse and south to the servants' quarters.")
       (EAST TO KITCHEN)
       (NORTH TO GREENHOUSE)
       (SOUTH TO SERVANTS-QUARTERS)
@@ -106,15 +114,15 @@
 <ROOM GREENHOUSE
       (IN ROOMS)
       (DESC "Greenhouse")
-      (LDESC "A glass greenhouse filled with exotic plants. Labels mark the pots, identifying species from around the world. The air is warm and humid, a stark contrast to the fog outside. A doorway leads south back to the garden.")
+      (ACTION GREENHOUSE-FCN)
       (SOUTH TO GARDEN)
       (FLAGS RLANDBIT ONBIT)
-      (GLOBAL PLANTS LABELS BENCH POTS)>
+      (GLOBAL PLANTS LABELS BENCH)>
 
 <ROOM SERVANTS-QUARTERS
       (IN ROOMS)
       (DESC "Servants' Quarters")
-      (LDESC "Sparse rooms with simple beds for the household staff. The air smells of old laundry and duty. A doorway leads north back to the garden.")
+      (ACTION SERVANTS-QUARTERS-FCN)
       (NORTH TO GARDEN)
       (FLAGS RLANDBIT ONBIT)
       (GLOBAL BEDS TRUNK UNIFORMS MR-HUDSON)>
@@ -122,7 +130,7 @@
 <ROOM SECRET-PASSAGE
       (IN ROOMS)
       (DESC "Secret Passage")
-      (LDESC "A narrow stone passage, its walls slick with moisture. Dust and cobwebs fill the air, undisturbed for years. The passage leads west to the library and east to the study, a hidden route through the manor's heart.")
+      (ACTION SECRET-PASSAGE-FCN)
       (WEST TO LIBRARY)
       (EAST TO STUDY)
       (FLAGS RLANDBIT ONBIT)
@@ -131,13 +139,32 @@
 <ROOM PANTRY
       (IN ROOMS)
       (DESC "Pantry")
-      (LDESC "A small pantry with shelves of food and wine. The air is cool and dry, preserving the contents. A doorway leads south back to the dining room.")
+      (ACTION PANTRY-FCN)
       (SOUTH TO DINING-ROOM)
       (FLAGS RLANDBIT ONBIT)
       (GLOBAL SHELVES FOXGLOVE CHARCOAL)>
 
 ; === OBJECTS ===
 
+<OBJECT TELEGRAM
+      (IN ASHWORTH-MANOR-GATE)
+      (DESC "creased telegram")
+      (FDESC "A creased telegram has been pinned beneath a stone beside the open gate.")
+      (LDESC "The rain-spotted telegram bears Lady Ashworth's hand and a hurried postscript.")
+      (SYNONYM TELEGRAM MESSAGE WIRE)
+      (ADJECTIVE CREASED RAIN-SPOTTED)
+      (FLAGS TAKEBIT READBIT)
+      (ACTION TELEGRAM-F)>
+
+<OBJECT STUDY-DOOR
+      (IN LOCAL-GLOBALS)
+      (DESC "study door")
+      (LDESC "A solid oak door separates the entrance hall from the study. Its brass lock is old but substantial.")
+      (SYNONYM DOOR ENTRANCE)
+      (ADJECTIVE STUDY OAK SOUTH)
+      (FLAGS DOORBIT NDESCBIT)
+      (ACTION STUDY-DOOR-F)>
+
 ; --- Evidence Objects ---
 
 <OBJECT DEAD-LETTER
@@ -145,7 +172,8 @@
       (DESC "unsent letter")
       (FDESC "A yellowed envelope lies among the papers on the desk, addressed in a shaking hand.")
       (LDESC "An unsent letter, its paper yellowed with age. The ink is faded but legible, the words a threat from one man to another. The seal is broken, the wax still bearing the initial 'M.'")
-      (SYNONYM LETTER NOTE PAPER)
+      (SYNONYM LETTER NOTE PAPER DEAD-LETTER)
+      (ADJECTIVE DEAD UNSENT)
       (FLAGS TAKEBIT READBIT)
       (ACTION DEAD-LETTER-F)>
 
@@ -154,7 +182,8 @@
       (DESC "blood-stained knife")
       (FDESC "Something glints in the branches near the fountain -- a knife, its blade dark with dried blood.")
       (LDESC "A sharp blade, its edge stained with dried blood. The handle bears the mark of a surgical instrument, the kind used by doctors and scientists.")
-      (SYNONYM KNIFE BLADE WEAPON)
+      (SYNONYM KNIFE BLADE WEAPON BLOOD-STAINED-KNIFE)
+      (ADJECTIVE BLOOD STAINED)
       (FLAGS TAKEBIT WEAPONBIT)
       (ACTION BLOOD-STAINED-KNIFE-F)>
 
@@ -162,9 +191,10 @@
       (IN STUDY)
       (DESC "locked box")
       (FDESC "A small locked box sits among the cold ashes in the fireplace, its brass clasp gleaming dully.")
-      (LDESC "A small ornate box, its surface carved with intricate patterns. A keyhole stares up at you, promising secrets within.")
+      (LDESC "A small ornate box with a four-letter name dial instead of a keyhole. Fine engraving circles the dial.")
       (SYNONYM BOX CASE CONTAINER)
-      (FLAGS CONTBIT)
+      (ADJECTIVE LOCKED)
+      (FLAGS CONTBIT SEARCHBIT TURNBIT)
       (ACTION LOCKED-BOX-F)>
 
 <OBJECT POISON-BOTTLE
@@ -172,7 +202,8 @@
       (DESC "poison bottle")
       (FDESC "A small glass bottle with a faded label sits on the mantelpiece, its contents clear and deadly.")
       (LDESC "A small glass bottle, its label reading 'Aconitum - Wolfsbane. Highly poisonous.' The liquid inside is clear, its lethality hidden in plain sight.")
-      (SYNONYM BOTTLE VIAL POISON)
+      (SYNONYM BOTTLE VIAL POISON-BOTTLE)
+      (ADJECTIVE POISON)
       (FLAGS TAKEBIT READBIT)
       (ACTION POISON-BOTTLE-F)>
 
@@ -182,6 +213,7 @@
       (FDESC "A leather-bound ledger lies open on the reading desk, its pages filled with coded entries.")
       (LDESC "A leather-bound book, its pages filled with numbers and names. Financial records that tell a story of debt and desperation.")
       (SYNONYM LEDGER BOOK ACCOUNT)
+      (ADJECTIVE SECRET)
       (FLAGS TAKEBIT READBIT)
       (ACTION SECRET-LEDGER-F)>
 
@@ -193,15 +225,27 @@
       (FDESC "A magnifying glass rests on the hall table, its brass handle worn smooth.")
       (LDESC "A brass magnifying glass, its lens clear and strong. Useful for examining small details that the naked eye might miss.")
       (SYNONYM GLASS LENS MAGNIFIER)
+      (ADJECTIVE MAGNIFYING)
       (FLAGS TAKEBIT)
       (ACTION MAGNIFYING-GLASS-F)>
 
+<OBJECT LEATHER-ROLL
+      (IN DRAWER)
+      (DESC "leather roll")
+      (FDESC "A leather roll lies in the open drawer, its contents glinting steel.")
+      (LDESC "A roll of soft leather, neatly tied. Something metallic shifts inside.")
+      (SYNONYM ROLL CASE)
+      (ADJECTIVE LEATHER)
+      (FLAGS CONTBIT TAKEBIT)
+      (CAPACITY 5)
+      (SIZE 3)>
+
 <OBJECT LOCKPICK-SET
-      (IN KITCHEN)
+      (IN LEATHER-ROLL)
       (DESC "lockpick set")
-      (FDESC "A leather roll lies in the open drawer, its contents glinting steel.")
       (LDESC "A set of metal picks, their tips worn from use. Tools of the trade for those who need to open locked doors.")
-      (SYNONYM PICKS TOOLS)
+      (SYNONYM SET PICKS TOOLS LOCKPICK LOCKPICK-SET)
+      (ADJECTIVE LOCKPICK BURGLAR BURGLARS)
       (FLAGS TAKEBIT TOOLBIT)
       (ACTION LOCKPICK-SET-F)>
 
@@ -209,8 +253,9 @@
       (IN SERVANTS-QUARTERS)
       (DESC "lantern")
       (FDESC "An oil lantern sits on the trunk, its glass clean and fuel full.")
-      (LDESC "A brass lantern, its glass clouded with age. When lit, it casts a warm glow that pushes back the darkness.")
-      (SYNONYM LAMP LIGHT)
+      (LDESC "A brass lantern kept scrupulously clean and full. Hudson has etched each former servant's initial beneath its base.")
+      (SYNONYM LAMP LIGHT LANTERN)
+      (ADJECTIVE OIL BRASS)
       (FLAGS TAKEBIT LIGHTBIT)
       (ACTION LANTERN-F)>
 
@@ -218,7 +263,7 @@
       (IN MR-HUDSON)
       (DESC "keyring")
       (LDESC "A ring of keys, each one opening a different lock. The study key hangs among them, waiting to be used.")
-      (SYNONYM KEYS KEY)
+      (SYNONYM KEYRING KEYS KEY)
       (FLAGS TAKEBIT TOOLBIT)
       (ACTION KEYRING-F)>
 
@@ -228,8 +273,9 @@
       (IN LIBRARY)
       (DESC "torn page")
       (FDESC "A torn page lies on the reading desk, covered in handwritten notes.")
-      (LDESC "A fragment of paper, its edges ragged. The text reads: 'Follow the rainbow order. Red, orange, yellow, green, blue, violet. Only then will the way open.'")
-      (SYNONYM PAGE FRAGMENT)
+      (LDESC "A fragment of paper, its edges ragged. The text reads: 'Among the marked books, follow the rainbow order: red, yellow, green, blue. Only then will the way open.'")
+      (SYNONYM PAGE FRAGMENT TORN-PAGE)
+      (ADJECTIVE TORN)
       (FLAGS TAKEBIT READBIT)
       (ACTION TORN-PAGE-F)>
 
@@ -238,6 +284,7 @@
       (DESC "colored markers")
       (LDESC "Small ribbons of color, tied to the bookshelves. Red, blue, green, and yellow markers suggest an organizational system.")
       (SYNONYM MARKERS RIBBONS TAGS)
+      (ADJECTIVE COLORED COLOURED)
       (FLAGS NDESCBIT)
       (ACTION COLORED-MARKERS-F)>
 
@@ -246,7 +293,8 @@
       (DESC "footprint cast")
       (FDESC "A plaster cast of a footprint sits near the fountain, preserving the evidence.")
       (LDESC "A plaster cast of a boot print, size 10. Too large for Lady Ashworth, too small for Mr. Hudson.")
-      (SYNONYM CAST MOLD FOOTPRINT)
+      (SYNONYM FOOTPRINT-CAST CAST MOLD FOOTPRINT IMPRESSION)
+      (ADJECTIVE FOOTPRINT PLASTER)
       (FLAGS TAKEBIT)
       (ACTION FOOTPRINT-CAST-F)>
 
@@ -255,15 +303,18 @@
       (DESC "wax seal")
       (FDESC "A crimson wax seal rests on the dining table, pressed with an unknown sigil.")
       (LDESC "A broken wax seal, its surface bearing the initial 'M.' The mark of Dr. Moriarty.")
-      (SYNONYM SEAL STAMP)
+      (SYNONYM SEAL STAMP WAX-SEAL)
+      (ADJECTIVE WAX)
       (FLAGS TAKEBIT)
       (ACTION WAX-SEAL-F)>
 
 <OBJECT BANK-STATEMENT
       (IN LOCKED-BOX)
       (DESC "bank statement")
+      (FDESC "A bank statement rests inside the opened box.")
       (LDESC "A financial statement showing Dr. Moriarty's account overdrawn. A large withdrawal for 'experimental supplies' catches your eye.")
-      (SYNONYM STATEMENT RECEIPT)
+      (SYNONYM STATEMENT RECEIPT BANK-STATEMENT)
+      (ADJECTIVE BANK)
       (FLAGS TAKEBIT READBIT)
       (ACTION BANK-STATEMENT-F)>
 
@@ -273,6 +324,8 @@
       (IN STUDY)
       (DESC "mahogany desk")
       (LDESC "A mahogany desk, its surface scarred with use. Three drawers, one locked, contain the remnants of Lord Ashworth's work.")
+      (SYNONYM DESK)
+      (ADJECTIVE MAHOGANY)
       (FLAGS NDESCBIT)
       (ACTION DESK-F)>
 
@@ -280,6 +333,7 @@
       (IN STUDY)
       (DESC "fireplace")
       (LDESC "A stone fireplace, its hearth cold. Ashes and a locked box remain from the last fire.")
+      (SYNONYM FIREPLACE HEARTH)
       (FLAGS NDESCBIT)
       (ACTION FIREPLACE-F)>
 
@@ -287,6 +341,7 @@
       (IN STUDY)
       (DESC "window")
       (LDESC "A tall window, its glass clouded with age. The latch is rusted but intact, looking out to the garden.")
+      (SYNONYM WINDOW GLASS LATCH)
       (FLAGS NDESCBIT)
       (ACTION WINDOW-F)>
 
@@ -294,6 +349,7 @@
       (IN LIBRARY)
       (DESC "bookshelf")
       (LDESC "Floor-to-ceiling shelves, filled with books of every description. Colored markers dot the spines, suggesting a hidden pattern.")
+      (SYNONYM BOOKSHELF SHELVES)
       (FLAGS NDESCBIT)
       (ACTION BOOKSHELF-F)>
 
@@ -301,27 +357,68 @@
       (IN LIBRARY)
       (DESC "reading desk")
       (LDESC "A wooden desk, its surface scattered with papers. A torn page lies among them, its message waiting to be read.")
+      (SYNONYM DESK)
+      (ADJECTIVE READING)
       (FLAGS NDESCBIT)
       (ACTION READING-DESK-F)>
 
+; Distinct marked books let the parser track the documented color sequence.
+<OBJECT RED-BOOK
+      (IN LIBRARY)
+      (DESC "red-marked book")
+      (SYNONYM BOOK)
+      (ADJECTIVE RED)
+      (FLAGS NDESCBIT)
+      (ACTION CIPHER-BOOK-F)>
+
+<OBJECT BLUE-BOOK
+      (IN LIBRARY)
+      (DESC "blue-marked book")
+      (SYNONYM BOOK)
+      (ADJECTIVE BLUE)
+      (FLAGS NDESCBIT)
+      (ACTION CIPHER-BOOK-F)>
+
+<OBJECT GREEN-BOOK
+      (IN LIBRARY)
+      (DESC "green-marked book")
+      (SYNONYM BOOK)
+      (ADJECTIVE GREEN)
+      (FLAGS NDESCBIT)
+      (ACTION CIPHER-BOOK-F)>
+
+<OBJECT YELLOW-BOOK
+      (IN LIBRARY)
+      (DESC "yellow-marked book")
+      (SYNONYM BOOK)
+      (ADJECTIVE YELLOW)
+      (FLAGS NDESCBIT)
+      (ACTION CIPHER-BOOK-F)>
+
 <OBJECT TABLE
       (IN DINING-ROOM)
       (DESC "dining table")
       (LDESC "A long dining table, set for two but used by only one. Wax seals and place settings tell a story of interrupted meals.")
+      (SYNONYM TABLE)
+      (ADJECTIVE DINING)
       (FLAGS NDESCBIT)
       (ACTION TABLE-F)>
 
 <OBJECT WINE-CABINET
       (IN DINING-ROOM)
       (DESC "wine cabinet")
-      (LDESC "A glass-fronted cabinet, its shelves filled with fine wines and spirits. A lock secures its contents.")
-      (FLAGS NDESCBIT)
+      (LDESC "A glass-fronted cabinet stands unlatched. One bottle-shaped gap interrupts the dust on its medicinal-wine shelf.")
+      (SYNONYM CABINET WINE-CABINET)
+      (ADJECTIVE WINE)
+      (FLAGS NDESCBIT CONTBIT SEARCHBIT)
       (ACTION WINE-CABINET-F)>
 
 <OBJECT POTS
       (IN KITCHEN)
       (DESC "copper pots")
       (LDESC "Copper pots, tarnished with age, hang from the kitchen ceiling. They have cooked many meals, but none recently.")
+      (SYNONYM POTS)
+      (ADJECTIVE COPPER)
       (FLAGS NDESCBIT)
       (ACTION POTS-F)>
 
@@ -329,6 +426,8 @@
       (IN KITCHEN)
       (DESC "cold hearth")
       (LDESC "A stone hearth, cold and empty. The last fire burned long ago.")
+      (SYNONYM HEARTH)
+      (ADJECTIVE COLD)
       (FLAGS NDESCBIT)
       (ACTION HEARTH-F)>
 
@@ -336,20 +435,43 @@
       (IN KITCHEN)
       (DESC "servant bell")
       (LDESC "A servant bell, its rope leading up to the servant's quarters. A pull summons the staff.")
+      (SYNONYM BELL ROPE)
+      (ADJECTIVE SERVANT)
       (FLAGS NDESCBIT)
       (ACTION SERVANT-BELL-F)>
 
+<OBJECT KETTLE
+      (IN LOCAL-GLOBALS)
+      (DESC "blue kettle")
+      (LDESC "A blue enamel kettle waits on the range, warm enough to mist its spout.")
+      (SYNONYM KETTLE POT)
+      (ADJECTIVE BLUE ENAMEL)
+      (FLAGS NDESCBIT)
+      (ACTION KETTLE-F)>
+
+<OBJECT BELL-WIRE
+      (IN LOCAL-GLOBALS)
+      (DESC "bell wire")
+      (LDESC "A thin servant-bell wire runs beside the study door.")
+      (SYNONYM WIRE CORD)
+      (ADJECTIVE BELL SERVANT)
+      (FLAGS NDESCBIT)
+      (ACTION BELL-WIRE-F)>
+
 <OBJECT DRAWER
       (IN KITCHEN)
       (DESC "drawer")
-      (LDESC "A drawer in the counter, slightly open. It promises something useful inside.")
-      (FLAGS NDESCBIT)
+      (LDESC "A drawer in the counter.")
+      (SYNONYM DRAWER)
+      (FLAGS NDESCBIT CONTBIT SEARCHBIT)
+      (CAPACITY 10)
       (ACTION DRAWER-F)>
 
 <OBJECT FOUNTAIN
       (IN GARDEN)
       (DESC "fountain")
       (LDESC "A stone fountain, dry and silent. Coins lie at the bottom, wishes unfulfilled.")
+      (SYNONYM FOUNTAIN COINS)
       (FLAGS NDESCBIT)
       (ACTION FOUNTAIN-F)>
 
@@ -357,6 +479,7 @@
       (IN GARDEN)
       (DESC "hedge mazes")
       (LDESC "Tall hedges, their branches thick and tangled. They hide secrets in their shadows.")
+      (SYNONYM HEDGES HEDGE BUSHES MAZE MAZES)
       (FLAGS NDESCBIT)
       (ACTION HEDGES-F)>
 
@@ -364,6 +487,8 @@
       (IN GREENHOUSE)
       (DESC "exotic plants")
       (LDESC "Exotic plants from around the world, their leaves and flowers a splash of color in the gray manor.")
+      (SYNONYM PLANTS FLOWERS)
+      (ADJECTIVE EXOTIC)
       (FLAGS NDESCBIT)
       (ACTION PLANTS-F)>
 
@@ -371,6 +496,8 @@
       (IN GREENHOUSE)
       (DESC "plant labels")
       (LDESC "Small labels marking the plants. They identify species and their properties.")
+      (SYNONYM LABELS)
+      (ADJECTIVE PLANT)
       (FLAGS NDESCBIT)
       (ACTION LABELS-F)>
 
@@ -378,6 +505,8 @@
       (IN GREENHOUSE)
       (DESC "potting bench")
       (LDESC "A wooden potting bench, its surface covered in soil and tools. Labels identify the plants it tends.")
+      (SYNONYM BENCH)
+      (ADJECTIVE POTTING)
       (FLAGS NDESCBIT)
       (ACTION BENCH-F)>
 
@@ -385,20 +514,35 @@
       (IN SERVANTS-QUARTERS)
       (DESC "servant beds")
       (LDESC "Simple beds for the household staff, their sheets worn but clean.")
+      (SYNONYM BEDS BED)
+      (ADJECTIVE SERVANT)
       (FLAGS NDESCBIT)
       (ACTION BEDS-F)>
 
 <OBJECT TRUNK
       (IN SERVANTS-QUARTERS)
       (DESC "trunk")
-      (LDESC "A large wooden trunk, its lid heavy. It contains the servant's belongings and secrets.")
-      (FLAGS NDESCBIT)
-      (ACTION TRUNK-F)>
+      (LDESC "A large wooden trunk, its lid heavy.")
+      (SYNONYM TRUNK CHEST)
+      (FLAGS NDESCBIT CONTBIT OPENBIT SEARCHBIT)
+      (CAPACITY 20)>
+
+<OBJECT TRUNK-LETTER
+      (IN TRUNK)
+      (DESC "folded note")
+      (LDESC "A folded letter, its edges worn. The handwriting is small and cramped.")
+      (SYNONYM NOTE)
+      (ADJECTIVE FOLDED)
+      (FLAGS TAKEBIT READBIT)
+      (TEXT "The letter is addressed to Mr. Hudson from an unknown sender. It reads: 'The master's experiments have gone too far. If anything happens to me, the evidence is in the study. Burn this after reading.' The signature is illegible.")
+      (ACTION TRUNK-LETTER-F)>
 
 <OBJECT UNIFORMS
-      (IN SERVANTS-QUARTERS)
+      (IN TRUNK)
       (DESC "servant uniforms")
       (LDESC "Servant uniforms, their fabric worn from use. They hang on hooks, waiting for their next wearer.")
+      (SYNONYM UNIFORMS CLOTHES)
+      (ADJECTIVE SERVANT)
       (FLAGS NDESCBIT)
       (ACTION UNIFORMS-F)>
 
@@ -406,76 +550,103 @@
       (IN SECRET-PASSAGE)
       (DESC "stone walls")
       (LDESC "Wet stone walls, slick with moisture. They have stood for centuries.")
+      (SYNONYM WALLS WALL)
+      (ADJECTIVE STONE)
       (FLAGS NDESCBIT)>
 
 <OBJECT COBWEBS
       (IN SECRET-PASSAGE)
       (DESC "cobwebs")
       (LDESC "Dusty cobwebs fill the air, undisturbed for years.")
+      (SYNONYM COBWEBS WEB WEBS)
       (FLAGS NDESCBIT)>
 
 <OBJECT DUST
       (IN SECRET-PASSAGE)
       (DESC "dust")
       (LDESC "A thick layer of dust covers everything. No one has been here in a long time.")
+      (SYNONYM DUST)
       (FLAGS NDESCBIT)>
 
 <OBJECT SHELVES
       (IN PANTRY)
       (DESC "pantry shelves")
       (LDESC "Shelves filled with food and wine. Some items are old, others relatively fresh.")
+      (SYNONYM SHELVES SHELF)
+      (ADJECTIVE PANTRY)
       (FLAGS NDESCBIT)
       (ACTION SHELVES-F)>
 
 <OBJECT FOXGLOVE
       (IN PANTRY)
       (DESC "foxglove")
-      (LDESC "A bottle of foxglove, its label faded but legible. An antidote ingredient.")
-      (SYNONYM DIGITALIS)
+      (LDESC "A bottle of dried foxglove leaves. The label warns that digitalis may steady a failing heart or stop a healthy one.")
+      (SYNONYM FOXGLOVE DIGITALIS)
       (FLAGS TAKEBIT)
       (ACTION FOXGLOVE-F)>
 
 <OBJECT CHARCOAL
       (IN PANTRY)
       (DESC "charcoal")
-      (LDESC "A container of charcoal, used for filtering poisons. An antidote ingredient.")
+      (LDESC "A tin of powdered charcoal, labeled for emergency use after swallowed poisons.")
+      (SYNONYM CHARCOAL COAL)
       (FLAGS TAKEBIT)
       (ACTION CHARCOAL-F)>
 
 ; === GLOBAL OBJECTS ===
 
 <OBJECT FOG
-      (SYNONYM MIST HAZE)
+      (DESC "fog")
+      (LDESC "Cold river fog curls through the manor gates.")
+      (SYNONYM FOG MIST HAZE)
       (FLAGS NDESCBIT)
       (ACTION FOG-F)>
 
 <OBJECT GATES
-      (SYNONYM GATE BARS)
+      (DESC "iron gates")
+      (LDESC "The iron gates stand open, their bars red with rust.")
+      (SYNONYM GATES GATE BARS)
+      (ADJECTIVE IRON)
       (FLAGS NDESCBIT)
       (ACTION GATES-F)>
 
 <OBJECT PATH
-      (SYNONYM WALKWAY DRIVE)
+      (DESC "gravel path")
+      (LDESC "A gravel path leads north through the fog to Ashworth Manor.")
+      (SYNONYM PATH WALKWAY DRIVE)
+      (ADJECTIVE GRAVEL)
       (FLAGS NDESCBIT)
       (ACTION PATH-F)>
 
 <OBJECT CHANDELIER
-      (SYNONYM LIGHT CRYSTAL)
+      (DESC "chandelier")
+      (LDESC "A dusty crystal chandelier hangs above the entrance hall.")
+      (SYNONYM CHANDELIER LIGHT CRYSTAL)
+      (ADJECTIVE DUSTY)
       (FLAGS NDESCBIT)
       (ACTION CHANDELIER-F)>
 
 <OBJECT PORTRAITS
-      (SYNONYM PAINTINGS PICTURES)
+      (DESC "family portraits")
+      (LDESC "Portraits of the Ashworth family line the walls.")
+      (SYNONYM PORTRAITS PAINTINGS PICTURES)
+      (ADJECTIVE FAMILY)
       (FLAGS NDESCBIT)
       (ACTION PORTRAITS-F)>
 
 <OBJECT RUG
-      (SYNONYM CARPET MAT)
+      (DESC "Persian rug")
+      (LDESC "A faded Persian rug covers the entrance-hall floor.")
+      (SYNONYM RUG CARPET MAT)
+      (ADJECTIVE PERSIAN FADED)
       (FLAGS NDESCBIT)
       (ACTION RUG-F)>
 
 <OBJECT CHALK-OUTLINE
-      (SYNONYM OUTLINE BODY)
+      (DESC "chalk outline")
+      (LDESC "A chalk outline marks the place where Lord Ashworth's body was found.")
+      (SYNONYM CHALK-OUTLINE OUTLINE BODY)
+      (ADJECTIVE CHALK)
       (FLAGS NDESCBIT)
       (ACTION CHALK-OUTLINE-F)>
 
@@ -485,34 +656,72 @@
       (IN SERVANTS-QUARTERS)
       (DESC "Mr. Hudson")
       (LDESC "Mr. Hudson, the butler, stands nervously in the servants' quarters. His expression is troubled, his hands fidgeting with a keyring.")
-      (SYNONYM HUDSON BUTLER)
-      (FLAGS ACTORBIT NDESCBIT)
+      (SYNONYM HUDSON BUTLER MR-HUDSON)
+      (ADJECTIVE MR MISTER)
+      (FLAGS ACTORBIT)
       (ACTION MR-HUDSON-F)>
 
 <OBJECT LADY-ASHWORTH
       (IN DINING-ROOM)
       (DESC "Lady Ashworth")
       (LDESC "Lady Ashworth sits at the dining table, her expression cold and calculating. She watches you with sharp eyes.")
-      (SYNONYM LADY WIFE ASHWORTH)
-      (FLAGS ACTORBIT NDESCBIT)
+      (SYNONYM ASHWORTH WIFE LADY-ASHWORTH)
+      (ADJECTIVE LADY)
+      (FLAGS ACTORBIT)
       (ACTION LADY-ASHWORTH-F)>
 
 <OBJECT DR-MORIARTY
       (IN LIBRARY)
       (DESC "Dr. Moriarty")
       (LDESC "Dr. Moriarty stands by the bookshelf, his expression arrogant and dismissive. He regards you with cool intelligence.")
-      (SYNONYM DOCTOR MORIARTY)
+      (SYNONYM MORIARTY DR-MORIARTY DOCTOR)
+      (ADJECTIVE DR DOCTOR)
       (FLAGS ACTORBIT NDESCBIT)
       (ACTION DR-MORIARTY-F)>
 
 <OBJECT INSPECTOR
-      (IN ASHWORTH-ENTRANCE-HALL)
       (DESC "Inspector Lestrade")
       (LDESC "Inspector Lestrade of Scotland Yard stands in the entrance hall, his expression professional and skeptical. He waits for your evidence.")
-      (SYNONYM INSPECTOR LESTRADE)
-      (FLAGS ACTORBIT NDESCBIT)
+      (SYNONYM INSPECTOR LESTRADE OFFICER DETECTIVE POLICE SCOTLAND-YARD)
+      (ADJECTIVE INSPECTOR SCOTLAND)
+      (FLAGS ACTORBIT NDESCBIT ARTICLEBIT)
       (ACTION INSPECTOR-F)>
 
+; Conversation topics are global so ASK ... ABOUT ... can resolve them from
+; the listener's room without requiring the referenced person or clue nearby.
+<OBJECT MASTER-TOPIC
+      (IN GLOBAL-OBJECTS)
+      (DESC "master")
+      (SYNONYM MASTER)>
+<OBJECT ALIBI-TOPIC
+      (IN GLOBAL-OBJECTS)
+      (DESC "alibi")
+      (SYNONYM ALIBI)>
+<OBJECT KEY-TOPIC
+      (IN GLOBAL-OBJECTS)
+      (DESC "key")
+      (SYNONYM KEY)>
+<OBJECT MORIARTY-TOPIC
+      (IN GLOBAL-OBJECTS)
+      (DESC "Moriarty")
+      (SYNONYM MORIARTY)>
+<OBJECT MARRIAGE-TOPIC
+      (IN GLOBAL-OBJECTS)
+      (DESC "marriage")
+      (SYNONYM MARRIAGE)>
+<OBJECT EXPERIMENTS-TOPIC
+      (IN GLOBAL-OBJECTS)
+      (DESC "experiments")
+      (SYNONYM EXPERIMENTS RESEARCH)>
+<OBJECT POISON-TOPIC
+      (IN GLOBAL-OBJECTS)
+      (DESC "poison")
+      (SYNONYM POISON WOLFSBANE)>
+<OBJECT CASE-TOPIC
+      (IN GLOBAL-OBJECTS)
+      (DESC "case")
+      (SYNONYM CASE MURDER)>
+
 ; === STARTING LOCATION ===
 
 <GLOBAL HERE ASHWORTH-MANOR-GATE>
@@ -521,5 +730,4 @@
       (IN ASHWORTH-MANOR-GATE)
       (DESC "you")
       (SYNONYM DETECTIVE YOU)
-      (FLAGS ACTORBIT)
-      (ACTION PLAYER-F)>
+      (FLAGS NDESCBIT INVISIBLE ACTORBIT)>
diff --git a/books/limehouse-killings/limehouse-killings-bugs.md b/books/limehouse-killings/limehouse-killings-bugs.md
new file mode 100644
index 0000000..889ffc0
--- /dev/null
+++ b/books/limehouse-killings/limehouse-killings-bugs.md
@@ -0,0 +1,280 @@
+# The Limehouse Killings - Bug Report
+
+**Test Date:** July 15, 2026
+**Tested By:** Game Tester Agent (ZIL adventure games)
+**Game Version:** Release 1
+
+## Walkthrough Status
+
+| Test | Result |
+|------|--------|
+| Golden Path (walkthrough.zil, 492 tests) | 492/492 PASS |
+| Organic playthrough (full investigation + accusation) | COMPLETE |
+
+## Summary
+
+| Category | Count |
+|----------|-------|
+| Critical Bugs | 2 |
+| High Severity | 3 |
+| Medium Severity | 6 |
+| Low Severity | 5 |
+| Design/Artistic Issues | 5 |
+
+---
+
+## Critical Bugs
+
+### Bug 1: ASK/TELL Without Topic Causes Runtime Crash
+- **Description:** Typing `ASK <NPC>` or `TELL <NPC>` without an ABOUT topic causes a nil-pointer crash. The game terminates immediately with a Lua runtime error.
+- **Command:** `ASK MORIARTY`, `ASK HUDSON`, `ASK LESTRADE`, `ASK LADY` (any NPC without a topic)
+- **Output:**
+  ```
+  Runtime error: .../actions.zil:1558: INSPECTOR_F
+  bootstrap:665: attempt to perform arithmetic on a nil value (local 'num')
+  ```
+- **Expected:** The game should respond with something like "What do you want to ask about?" or a polite refusal.
+- **Reproduction:**
+  1. Start a new game
+  2. Go to any NPC (e.g., `NORTH` to entrance hall, `EAST` to library standing near Dr. Moriarty)
+  3. Type `ASK MORIARTY` (no topic)
+  4. Game crashes 100% of the time
+- **Root Cause:** All NPC FCN routines (MR-HUDSON-F, LADY-ASHWORTH-F, DR-MORIARTY-F, INSPECTOR-F) handle `<VERB? TELL>` by checking PRSI against various topic objects using `(IN? ,PRSI ,INTQUOTE)`. When no topic is provided, PRSI is nil, and calling `IN?` on nil crashes the runtime.
+- **Affected NPCs:** All 4 NPCs
+- **Severity:** Critical
+
+### Bug 2: "ASK INSPECTOR ABOUT CASE" Fails With Generic Error
+- **Description:** Despite prior fixes claiming to add ASK/TELL syntax support, `ASK INSPECTOR ABOUT CASE` produces "Please consult your manual for the correct way to talk to other people or creatures." — the generic parser error.
+- **Command:** `ASK INSPECTOR ABOUT CASE`
+- **Output:** `Please consult your manual for the correct way to talk to other people or creatures.`
+- **Expected:** "Bring me five solid pieces of evidence and interview all three suspects. Then make your accusation." (as defined in INSPECTOR-F)
+- **Reproduction:**
+  1. Start a new game, go to entrance hall
+  2. Type `ASK INSPECTOR ABOUT CASE`
+  3. Gets generic error
+- **Notes:** `TELL INSPECTOR ABOUT CASE` gives the same error. However, `ASK MORIARTY ABOUT POISON` and `ASK HUDSON ABOUT KEY` work correctly. The syntax specifically fails for the INSPECTOR, suggesting the issue is with how the CASE-TOPIC object resolves, or that INSPECTOR-F's VERB? TELL check doesn't trigger. This is a regression — the prior fix B4 claimed to address this.
+- **Severity:** Critical
+
+---
+
+## High Severity Bugs
+
+### Bug 3: Compound Noun Parsing Failure ("set" and "cast")
+- **Description:** The parser fails to handle compound nouns whose second word is "set" or "cast" — these words are interpreted as verbs rather than noun modifiers.
+- **Commands:**
+  - `TAKE LOCKPICK SET` → "You used the word 'set' in a way that I don't understand."
+  - `TAKE FOOTPRINT CAST` → "You used the word 'cast' in a way that I don't understand."
+  - `TAKE LOCKPICK-SET` (with hyphen) → "You used the word 'set' in a way that I don't understand."
+- **Workarounds:**
+  - `TAKE PICKS` or `TAKE LOCKPICK` — works
+  - `TAKE FOOTPRINT` or `TAKE MOLD` — works
+- **Reproduction:**
+  1. Obtain the leather roll from kitchen drawer, open it
+  2. `TAKE LOCKPICK SET` — fails
+  3. `TAKE PICKS` — succeeds
+- **Root Cause:** The ZIL parser tokenizes hyphenated words and compound nouns, but "set" and "cast" exist as verb entries in the default vocabulary, so the parser interprets them as verbs instead of as the second half of a compound noun.
+- **Severity:** High
+
+### Bug 4: Inspector Present From Game Start
+- **Description:** Inspector Lestrade is in the entrance hall from the very first moment the game begins (before the player has gathered any evidence). The design document (DESIGN.md, PLAN.md) states he should appear after sufficient evidence is gathered. His presence is not mentioned in the room description, so the player doesn't realize he's there until they happen to try `EXAMINE LESTRADE`.
+- **Command:** `EXAMINE LESTRADE` (from entrance hall at game start)
+- **Output:** "Inspector Lestrade of Scotland Yard stands in the entrance hall, his expression professional and skeptical."
+- **Expected:** Inspector should not appear until the player has gathered significant evidence (e.g., evidence-found >= 5 or after interviewing all suspects).
+- **Reproduction:** Start new game, go north, type `EXAMINE LESTRADE`. He's there.
+- **Severity:** High
+
+### Bug 5: NPCs Not Listed in Room Descriptions
+- **Description:** None of the NPCs are listed in their room's descriptions. When the player enters a room containing an NPC, the room description provides no indication that anyone is present. The player must blindly try `EXAMINE <NPC-NAME>` or `ASK <NPC-NAME>` to discover they exist.
+- **Examples:**
+  - Servants' Quarters: Mr. Hudson is present but not mentioned
+  - Dining Room: Lady Ashworth is present but not mentioned
+  - Library: Dr. Moriarty is present but not mentioned
+  - Entrance Hall: Inspector Lestrade is present but not mentioned
+- **Reproduction:** Enter any room containing an NPC. The NPC is invisible to the room description.
+- **Expected:** NPCs should be listed in room descriptions with a brief presence note, e.g., "Mr. Hudson, the butler, stands nearby looking troubled."
+- **Severity:** High
+
+---
+
+## Medium Severity Bugs
+
+### Bug 6: No FDESC (First-Visit Discovery Text) on Major Rooms
+- **Description:** Most rooms have no first-visit discovery text (FDESC). The same LDESC is shown every time the player enters or looks at the room. The skill standard (Skill 04 Rule 8) requires every major room to have unique discovery text that appears only on the first visit.
+- **Rooms without FDESC:**
+  - ASHWORTH-MANOR-GATE (uses LDESC directly, same every visit)
+  - ASHWORTH-ENTRANCE-HALL (ACTION-based but no FIRST?/FDESC logic)
+  - DINING-ROOM (uses LDESC, same every visit)
+  - GREENHOUSE (uses LDESC, same every visit)
+  - SERVANTS-QUARTERS (uses LDESC, same every visit)
+  - PANTRY (uses LDESC, same every visit)
+  - SECRET-PASSAGE (uses LDESC, same every visit)
+- **Contrast:** Only 3 objects have FDESC (DEAD-LETTER, BLOOD-STAINED-KNIFE, LOCKED-BOX). Most objects lack discovery text.
+- **Reproduction:** Visit any room listed above multiple times. The description is identical every time.
+- **Severity:** Medium
+
+### Bug 7: No FDESC on Most Important Objects
+- **Description:** Only 3 of the major objects have FDESC (DEAD-LETTER, BLOOD-STAINED-KNIFE, LOCKED-BOX). Key objects like POISON-BOTTLE, SECRET-LEDGER, MAGNIFYING-GLASS, LANTERN, KEYRING, FOOTPRINT-CAST, WAX-SEAL, BANK-STATEMENT, and TORN-PAGE lack FDESC.
+- **Severity:** Medium
+
+### Bug 8: Room Descriptions Don't Update (Static World)
+- **Description:** After major story events, most room descriptions don't update to reflect the changed world state. The skill standard (Skill 03 Rule 4) requires every major story event to change at least 2 existing rooms.
+- **Examples:**
+  - After solving the library cipher and opening the secret passage, the Library's LDESC still says "A doorway leads west back to the entrance hall" (the ACTION routine does update to mention the passage, but most rooms don't have ACTION routines)
+  - After opening the study door, rooms connected to the entrance hall don't change
+  - After winning the game, room descriptions remain static
+- **Rooms with state-aware descriptions:** Study (via STUDY-FCN), Library (via LIBRARY-FCN), Kitchen (via KITCHEN-FCN), Garden (via GARDEN-FCN), Entrance Hall (via ENTRANCE-HALL-FCN)
+- **Rooms without any dynamic description:** Gate, Dining Room, Greenhouse, Servants' Quarters, Pantry, Secret Passage
+- **Severity:** Medium
+
+### Bug 9: "Open door" Without Specific Context Fails
+- **Description:** Typing `OPEN DOOR` in the entrance hall doesn't work because the parser can't disambiguate which door. However, since "study door" is the only door most players encounter, `OPEN DOOR` should at least suggest that.
+- **Command:** `OPEN DOOR` (in entrance hall)
+- **Output:** "You can't see any door here!"
+- **Expected:** Should say something like "Which door do you mean?" or refer to the study door specifically.
+- **Severity:** Medium
+
+### Bug 10: GIVE Verb Not Handled
+- **Description:** The GIVE verb falls through to the default NPC response ("The Dr. Moriarty refuses it politely.") rather than being routed to NPC-specific SHOW/ASK handling.
+- **Command:** `GIVE MAGNIFYING GLASS TO MORIARTY`
+- **Output:** "The Dr. Moriarty refuses it politely."
+- **Note:** The pre-existing bug report (B7) mentions fixing "the Moriarty" grammar issue, but it still appears in some contexts.
+- **Severity:** Medium
+
+### Bug 11: Duplicate object "POTS" in GLOBAL lists removed, but READ action auto-TAKES some items
+- **Description:** Reading certain objects (DEAD-LETTER, SECRET-LEDGER) automatically takes them via the READ handler. This is inconsistent with how TAKE works otherwise and can confuse players who type READ first and then try to TAKE.
+- **Command:** `READ DEAD-LETTER` then `TAKE DEAD-LETTER`
+- **Output:** "(Taken)" then "You already have that!"
+- **Expected:** Either the READ should not auto-TAKE, or the TAKE should acknowledge the item is already held.
+- **Severity:** Medium
+
+---
+
+## Low Severity Bugs
+
+### Bug 12: "servant's quarters" vs "servants' quarters" Inconsistency
+- **Description:** Room naming and descriptions are inconsistent between "Servants' Quarters" (room DESC) and "servant's quarters" / "servant bell rope leading up to the servant's quarters" in various texts.
+- **Locations:** Multiple — the room DESC says "Servants' Quarters" but other text uses different forms.
+- **Severity:** Low
+
+### Bug 13: Magnifying Glass Has No Practical Use
+- **Description:** The magnifying glass is one of the first objects the player finds (entrance hall table), but it has no gameplay use. It can be EXAMINEd and TAKEn, and "USE" gives a description, but it never interacts with any puzzle or evidence item.
+- **Severity:** Low
+
+### Bug 14: Lantern Has No Practical Use
+- **Description:** The lantern in the servants' quarters has LIGHTBIT and can be lit with USE, but there are no dark rooms in the game. All rooms are permanently lit. The lantern is a red herring that does nothing.
+- **Severity:** Low
+
+### Bug 15: Pantry-Only Items Are Never Required
+- **Description:** Foxglove and charcoal are in the pantry and described as "antidote ingredients." But no puzzle requires them — there's no poison antidote puzzle that uses them. The poison identification puzzle (Puzzle 3) just requires matching the bottle label to the greenhouse plant, not using antidotes.
+- **Severity:** Low
+
+### Bug 16: Wine Cabinet Has No Use
+- **Description:** The wine cabinet in the dining room is described as locked and containing fine wines. But there's no way to open it (no key in the game fits it), and it serves no puzzle purpose. It's a dead-end scenery object.
+- **Severity:** Low
+
+---
+
+## Design/Artistic Issues (Against Skill Standards)
+
+### Issue 1: Puzzles Are Item Gates (Violates Skill 03 Rule 1)
+- **Assessment:** The game's major "puzzles" are fundamentally item gates rather than narrative challenges.
+  - Study Entry: Find key or lockpick → unlock door
+  - Locked Box: Find key or lockpick → open box
+  - Greenhouse Poison: Match bottle label to plant label (the only puzzle that requires understanding the fiction)
+  - Final Confrontation: Accumulate 5 evidence items → accuse correct NPC
+- **The exception:** Library Cipher is the only puzzle that requires understanding a pattern (rainbow order) rather than finding an item.
+- **Standard Required:** "At least 2 of your major gates must be solved by understanding the fiction rather than finding a key."
+- **Verdict:** FAIL — 3 of 4 major puzzles are item gates.
+
+### Issue 2: No Three Escalating Acts (Violates Skill 03 Rule 2)
+- **Assessment:** The game plays as a flat investigation with no act boundaries, no escalation in challenge type, and no structural breaks. All rooms are accessible from the start (except the study and secret passage), and the player moves linearly through exploration → evidence collection → accusation with no visible act transitions.
+- **Standard Required:** "Structure your game in three acts with clear threshold moments. Each act should have a different dominant challenge type (exploration → deduction → confrontation). At each act boundary, the world should visibly change."
+- **Verdict:** FAIL — no act structure, no visible world changes.
+
+### Issue 3: NPCs Are Props (Violates Skill 04 Rule 3)
+- **Assessment:** NPCs have dialogue but only one behavioral state:
+  - Mr. Hudson: Always nervous, always in servants' quarters. His key-giving is the only state change.
+  - Lady Ashworth: Always cold and calculating, always in the dining room.
+  - Dr. Moriarty: Always arrogant, always in the library (except after poison topic, he moves to entrance hall — one behavioral change).
+  - Inspector Lestrade: Static from beginning to end.
+- **Standard Required:** "Every NPC must have at least three behavioral states that the player can discover and affect. At minimum: (1) initial encounter, (2) a state changed by player action, (3) a state triggered by story progress elsewhere."
+- **Verdict:** FAIL — NPCs have 1-2 states at most.
+
+### Issue 4: Prose Tells Rather Than Shows (Violates Skill 04 Rule 1)
+- **Assessment:** Multiple room descriptions use emotion-label language instead of concrete sensory details:
+  - "The air is thick with the scent of old wood and regret" — tells emotion abstractly
+  - "The air hangs heavy with the memory of violence" — tells rather than shows
+  - "The study remains as you found it, a testament to the crime committed here" — interpretive, not sensory
+- **Positive examples:**
+  - "Copper pots hang from the ceiling, tarnished with age" — concrete and sensory
+  - "The fog swirls around your feet, cold and damp" — sensory and specific
+  - "The fountain is dry, with coins at the bottom" — concrete and visual
+- **Standard Required:** "Every room description must contain at least one concrete sensory detail (sight, sound, smell, texture, temperature). Never use emotion-label adjectives ('dread,' 'ominous,' 'creepy,' 'wrong') as a substitute."
+- **Verdict:** MIXED — some rooms succeed, others use emotion labels.
+
+### Issue 5: Ending Is a Held-Item Counter Check (Violates Skill 04 Rule 7)
+- **Assessment:** The ending is triggered by `ACCUSE DR-MORIARTY`, which simply checks if `EVIDENCE-FOUND == 5` and `SUSPECTS-INTERVIEWED == 3`. It never references specific discoveries the player made (the dead letter's content, the knife's origin, the poison's type). It gives the player no choice. It stops at "You won" with no implication of what comes next.
+- **Standard Required:** "An ending must: (1) reference at least two specific discoveries the player made, (2) give the player a choice (even a small one), and (3) imply what comes next rather than stopping at 'you win.'"
+- **Verdict:** FAIL — ending is a numeric counter check with no personalization.
+
+### Issue 6: Environmental Storytelling Relies on Text Dumps (Violates Skill 04 Rule 5)
+- **Assessment:** Almost all lore is delivered through readable text-dump objects:
+  - DEAD-LETTER: text dump
+  - SECRET-LEDGER: text dump
+  - BANK-STATEMENT: text dump
+  - TORN-PAGE: text dump (cipher clue)
+  - FOLDED-NOTE (in trunk): text dump
+  - POISON-BOTTLE label: text dump
+- Environmental reveals are rare:
+  - Chalk outline (good — shows method of murder)
+  - Wax seal with initial "M" (good — shows Moriarty's involvement visually)
+  - Colored markers on books (good — visual cipher clue)
+  - Footprint cast size (mixed — told via examine text, not purely environmental)
+- **Standard Required:** "Cut text-dump objects by half. Move their information into room descriptions, object examines, environmental details, and NPC dialogue."
+- **Verdict:** MIXED — some environmental storytelling exists, but reliance on text dumps is heavy.
+
+### Issue 7: No Emotional Range (Violates Skill 04 Rule 4)
+- **Assessment:** The game is uniformly dark Victorian noir with no moments of beauty, humor, warmth, or relief. Every room description filters through grimness: "fog-choked sky," "memory of violence," "air smells of old wood and regret," "overgrown garden choked with weeds," "servant beds worn but clean."
+- **Standard Required:** "A horror game must have moments of beauty, humor, or warmth. Without contrast, the player desensitizes and every room feels the same. Aim for at least 3 moments outside the primary tone."
+- **Verdict:** FAIL — no moments of contrast anywhere.
+
+### Issue 8: Opening Scene Missing Components (Violates Skill 01)
+- **Assessment:** The opening scene at Ashworth Manor Gate has landmarks (gates, path, fog) but:
+  - **One landmark:** ✓ (iron gates)
+  - **One visible object:** ✗ (no takeable/usable object in the first room; the magnifying glass is in the entrance hall, one room away)
+  - **One blocker:** ✓ (locked study door, two rooms away)
+  - **One quick reward:** ✗ (no immediate reward in the first room; player must navigate to entrance hall, then library to find the torn page)
+- **Standard Required:** "Define a memorable opening with one landmark, one visible object, one blocker, and one quick reward."
+- **Verdict:** PARTIAL — missing the visible object and quick reward in the opening room.
+
+---
+
+## Files Affected (For Fixes)
+
+### Critical Fixes Needed:
+- `actions.zil` — NPC FCN routines: add nil-guard for PRSI before `IN?` and `EQUAL?` checks in TELL handlers
+- `actions.zil` — INSPECTOR-F: fix ASK syntax routing or CASE-TOPIC resolution
+
+### High Priority Fixes:
+- `actions.zil` — Add NPC presence listing to room ACTION routines (ENTRANCE-HALL-FCN, etc.)
+- `actions.zil` — Trigger INSPECTOR arrival based on EVIDENCE-FOUND counter rather than starting in entrance hall
+
+### Medium Priority Fixes:
+- `dungeon.zil` — Add FDESC to all major rooms and objects
+- `dungeon.zil` — Add FIRST?/FDESC discovery text patterns to room ACTION routines
+- `actions.zil` — Add state-aware text to all room ACTION routines
+- `dungeon.zil` — Add SYNONYM entries for compound nouns to handle parser tokenization (e.g., LOCKPICK-SET needs SET as separate synonym)
+
+### Design/Content Improvements:
+- Add at least one puzzle that requires understanding the fiction (in addition to cipher)
+- Create three-act structure with visible world changes at act boundaries
+- Give NPCs behavioral states that change with player actions
+- Add moments of emotional contrast
+- Replace emotion-label prose with concrete sensory details
+- Make ending reference specific player discoveries
+- Add practical uses for magnifying glass, lantern, foxglove, charcoal, and wine cabinet
+- Move lore from text-dump objects into environmental observation
+
+---
+
+*Report generated by game tester agent on July 15, 2026*
diff --git a/books/limehouse-killings/test/TESTING.md b/books/limehouse-killings/test/TESTING.md
index b91d572..0f8db19 100644
--- a/books/limehouse-killings/test/TESTING.md
+++ b/books/limehouse-killings/test/TESTING.md
@@ -17,9 +17,9 @@
 6. READ TORN-PAGE
 7. EXAMINE COLORED-MARKERS
 8. PUSH RED BOOK
-9. PUSH BLUE BOOK
+9. PUSH YELLOW BOOK
 10. PUSH GREEN BOOK
-11. PUSH YELLOW BOOK
+11. PUSH BLUE BOOK
 12. GO SOUTH to SECRET-PASSAGE
 13. GO EAST to STUDY
 14. EXAMINE DESK
diff --git a/books/limehouse-killings/test/walkthrough.zil b/books/limehouse-killings/test/walkthrough.zil
index f24a2d8..78ff33d 100644
--- a/books/limehouse-killings/test/walkthrough.zil
+++ b/books/limehouse-killings/test/walkthrough.zil
@@ -24,6 +24,8 @@
     <TELL CR "Test 3: Try locked study door" CR>
     <PERFORM ,V?GO-SOUTH ,ROOMS>
     <ASSERT <NOT ,STUDY-UNLOCKED> "Study should be locked">
+    <ASSERT <NOT <FSET? ,STUDY-DOOR ,OPENBIT>> "Study door should be closed">
+    <ASSERT <==? ,HERE ,ASHWORTH-ENTRANCE-HALL> "Locked study exit should keep player in entrance hall">
 
     ; Test 4: Go to library
     <TELL CR "Test 4: Go to library" CR>
@@ -92,6 +94,9 @@
 
     ; Test 16: Go to dining room
     <TELL CR "Test 16: Go to dining room" CR>
+    <PERFORM ,V?OPEN ,STUDY-DOOR>
+    <ASSERT ,STUDY-UNLOCKED "Opening the study door from inside should release its bolt">
+    <ASSERT <FSET? ,STUDY-DOOR ,OPENBIT> "Study door should be open">
     <PERFORM ,V?GO-NORTH ,ROOMS>
     <PERFORM ,V?GO-WEST ,ROOMS>
     <ASSERT <==? ,HERE ,DINING-ROOM> "Should be in dining room">
@@ -212,7 +217,7 @@
     <PERFORM ,V?GO-SOUTH ,ROOMS>
     <PERFORM ,V?GO-EAST ,ROOMS>
     <ASSERT <==? ,HERE ,STUDY> "Should be in study">
-    <PERFORM ,V?OPEN ,LOCKED-BOX>
+    <PERFORM ,V?TURN ,LOCKED-BOX ,MORIARTY-TOPIC>
     <ASSERT ,LOCKED-BOX-OPENED "Box should be opened">
 
     ; Test 36: Take bank statement
@@ -227,7 +232,10 @@
 
     ; Test 38: Accuse Dr. Moriarty
     <TELL CR "Test 38: Accuse Dr. Moriarty" CR>
-    <PERFORM ,V?ACCUSE ,DR-MORIARTY>
+    <PERFORM ,V?SHOW ,DEAD-LETTER ,INSPECTOR>
+    <PERFORM ,V?SHOW ,POISON-BOTTLE ,INSPECTOR>
+    <PERFORM ,V?SHOW ,BANK-STATEMENT ,INSPECTOR>
+    <PERFORM ,V?ACCUSE ,DR-MORIARTY ,DEAD-LETTER>
     <ASSERT ,KILLER-ACCUSED "Killer should be accused">
     <ASSERT ,CORRECT-ACCUSATION "Accusation should be correct">
     <ASSERT ,GAME-WON "Game should be won">
diff --git a/books/limehouse-killings/work/HINTS.md b/books/limehouse-killings/work/HINTS.md
index edd9490..deb9168 100644
--- a/books/limehouse-killings/work/HINTS.md
+++ b/books/limehouse-killings/work/HINTS.md
@@ -1,230 +1,106 @@
-# The Limehouse Killings - Hint Panel Content
+# The Limehouse Killings - Hint Design
 
-## Hint System Overview
+Hints must preserve idea-space challenge while removing parser friction. Every final-tier hint uses a command accepted by the current parser-driven walkthrough.
 
-The hint system provides progressive assistance for each puzzle. Players can request hints at any time by typing HINTS. Hints are presented in 4 tiers, from vague to specific.
+## Current Delivery
 
-## Hint Panel Structure
+The implemented `HINTS` command chooses one state-aware hint:
 
-### How to Use Hints
-- Type HINTS to see available hint topics
-- Type HINTS [TOPIC] to get a hint for that puzzle
-- Each hint topic has 4 tiers
-- Type HINTS [TOPIC] again for the next tier
-- Hints reset when puzzle is solved
+1. Study access while the door is locked.
+2. Library cipher until solved.
+3. Poison comparison until identified.
+4. Case assembly and Lestrade afterward.
 
-## Puzzle Hints
+Topic-specific, repeat-to-advance tiers are a future UI refactor, not current behavior. The content below is the target copy for that refactor.
 
-### Puzzle 1: Study Entry
+## Opening and Study Access
 
-**Topic:** STUDY
+| Tier | Copy |
+|---|---|
+| Attention | “The study door is locked, but a locked-room crime may have more than one route.” |
+| Direction | “Hudson has the study key. The colored books in the library may reveal how someone avoided the door.” |
+| Action | “Ask Hudson about the key for the physical route, or solve the marked-book sequence for the hidden route.” |
+| Command | `ASK HUDSON ABOUT KEY`, or `PUSH RED BOOK`, `PUSH YELLOW BOOK`, `PUSH GREEN BOOK`, `PUSH BLUE BOOK` |
 
-**Tier 1 (Attention):**
-"The study door is locked. Perhaps someone has the key."
+Design note: never imply the key or lockpick is the only solution. The secret passage is the preferred story-bearing route.
 
-**Tier 2 (Direction):**
-"The butler might know where the key is kept. Or perhaps there's another way in."
+## Library Passage
 
-**Tier 3 (Action):**
-"Ask Mr. Hudson about the key, but be persistent. Alternatively, check the garden for another entrance."
+| Tier | Copy |
+|---|---|
+| Attention | “The torn page and colored ribbons describe the same arrangement.” |
+| Direction | “The page says rainbow order; only four marked colors are present.” |
+| Action | “Push the marked books from the warm end of the sequence toward blue.” |
+| Command | `PUSH RED BOOK`, then yellow, green, and blue |
 
-**Tier 4 (Command):**
-`ASK HUDSON ABOUT KEY` or `USE LOCKPICK ON WINDOW`
+Wrong order: “The book springs back. The sequence resets.”
 
----
+## Greenhouse Poison
 
-### Puzzle 2: Library Cipher
+| Tier | Copy |
+|---|---|
+| Attention | “The vial and the greenhouse labels each use two names for one plant.” |
+| Direction | “Aconitum is wolfsbane; compare the physical vial with the purple plant.” |
+| Action | “Use the vial on the plants rather than merely carrying antidote ingredients.” |
+| Command | `USE VIAL ON PLANTS` |
 
-**Topic:** CIPHER
+Wrong attempts:
 
-**Tier 1 (Attention):**
-"The bookshelf has colored markers. Perhaps they mean something."
+- `TASTE VIAL`: danger feedback and recoverable health loss.
+- Merely taking foxglove/charcoal: no progress; these are not the identification solution.
 
-**Tier 2 (Direction):**
-"The torn page mentions 'rainbow order'. The markers are colored."
+## Ashworth Name Dial
 
-**Tier 3 (Action):**
-"Push the books with colored spines in rainbow order: red, orange, yellow, green, blue, violet."
+| Tier | Copy |
+|---|---|
+| Attention | “The box has no keyhole. Its three engravings are categories of evidence.” |
+| Direction | “Connect the sealed letter, purple flower, and columns of debt to one person.” |
+| Action | “Read the letter and ledger, identify the poison, then set the dial to the shared name.” |
+| Command | `TURN LOCKED BOX TO MORIARTY` |
 
-**Tier 4 (Command):**
-`PUSH RED BOOK THEN BLUE BOOK THEN GREEN BOOK THEN YELLOW BOOK`
+Wrong attempts:
 
----
+- `OPEN BOX`: teaches that the dial is the lock.
+- Correct name before prerequisites: identifies the unresolved three categories.
+- Wrong name: dial returns to blank.
 
-### Puzzle 3: Greenhouse Poison
+## NPC Interviews and State Changes
 
-**Topic:** POISON
+| Tier | Copy |
+|---|---|
+| Attention | “Answers establish alibis; showing evidence changes behavior.” |
+| Direction | “Ask Hudson and Lady Ashworth about their alibis. Ask Moriarty about poison.” |
+| Action | “Show the unsent letter before Act III if you want to expose a suspect's intermediate state.” |
+| Command | `ASK HUDSON ABOUT ALIBI`, `ASK LADY ABOUT ALIBI`, `ASK MORIARTY ABOUT POISON`, `SHOW LETTER TO HUDSON/LADY/MORIARTY` |
 
-**Tier 1 (Attention):**
-"The poison bottle has a label. Greenhouse plants have labels too."
+Topicless `ASK NPC` should prompt for a topic, never crash.
 
-**Tier 2 (Direction):**
-"Match the poison bottle to a plant in the greenhouse."
+## Lestrade's Case Chain
 
-**Tier 3 (Action):**
-"Find the wolfsbane plant and take the antidote ingredients."
+| Tier | Copy |
+|---|---|
+| Attention | “Lestrade wants an argument, not an inventory count.” |
+| Direction | “Organize the case as threat, method, and motive.” |
+| Action | “Show him Ashworth's threat, the identified poison, and the financial corroboration.” |
+| Command | `SHOW LETTER TO INSPECTOR`, `SHOW BOTTLE TO INSPECTOR`, `SHOW STATEMENT TO INSPECTOR` |
 
-**Tier 4 (Command):**
-`EXAMINE POISON-BOTTLE THEN FIND WOLFSBANE IN GREENHOUSE`
+Early accusation response must name the missing argument links, not say only “not enough evidence.”
 
----
+## Final Choice
 
-### Puzzle 4: Final Confrontation
+| Tier | Copy |
+|---|---|
+| Attention | “The case is complete. Decide which proof should lead.” |
+| Direction | “The letter invites witness confirmation; the poison may provoke specialized knowledge.” |
+| Action | “Accuse Moriarty with either the letter or the poison.” |
+| Command | `ACCUSE MORIARTY WITH LETTER` or `ACCUSE MORIARTY WITH POISON` |
 
-**Topic:** ACCUSE
+## General Hint Principles
 
-**Tier 1 (Attention):**
-"The evidence must point to one suspect."
-
-**Tier 2 (Direction):**
-"Consider who had means, motive, and opportunity."
-
-**Tier 3 (Action):**
-"Dr. Moriarty had poison, owed money, and no alibi."
-
-**Tier 4 (Command):**
-`ACCUSE DR-MORIARTY`
-
----
-
-## General Hints
-
-### Topic: GENERAL
-
-**Tier 1:**
-"If you're stuck, try examining everything in the current room. Look for objects that might be useful."
-
-**Tier 2:**
-"Have you talked to all the NPCs? They might have information you need."
-
-**Tier 3:**
-"Some doors are locked. You'll need a key or tool to open them."
-
-**Tier 4:**
-"Try reading any notes or letters you've found. They might contain clues."
-
----
-
-### Topic: INVENTORY
-
-**Tier 1:**
-"You can carry up to 7 items. Use INVENTORY to see what you have."
-
-**Tier 2:**
-"Some items are useful for specific puzzles. Think about what each item might do."
-
-**Tier 3:**
-"The lockpick set can open locked doors. The keyring has the study key."
-
-**Tier 4:**
-"Use USE [ITEM] ON [OBJECT] to use items on specific objects."
-
----
-
-### Topic: NPCs
-
-**Tier 1:**
-"Each NPC has different information. Try asking them about various topics."
-
-**Tier 2:**
-"ASK [NPC] ABOUT [TOPIC] to learn new information."
-
-**Tier 3:**
-"Some NPCs lie. Compare what they say with the evidence you find."
-
-**Tier 4:**
-"SHOW [ITEM] TO [NPC] to see their reaction to evidence."
-
----
-
-## Wrong Attempt Responses
-
-### Study Entry
-- **BREAK DOOR:** "The door is solid oak. You'd need a battering ram."
-- **CLIMB WINDOW (without lockpick):** "The window is too high. You need a tool."
-- **ASK LADY ABOUT KEY:** "I don't have such things. Ask the butler."
-
-### Library Cipher
-- **PUSH RANDOM BOOKS:** "Nothing happens. Perhaps there's an order to follow."
-- **READ ALL BOOKS:** "The books are unremarkable Victorian literature."
-- **ASK HUDSON ABOUT PASSAGE:** "I know of no such thing."
-
-### Greenhouse Poison
-- **SMELL POISON:** "The scent is faint but distinctive. Best not to inhale."
-- **TASTE POISON:** "You feel dizzy. Perhaps that wasn't wise." (lose health)
-- **ASK LADY ABOUT POISON:** "I know nothing of such things." (lying)
-
-### Final Confrontation
-- **ACCUSE LADY-ASHWORTH:** "Lady Ashworth has an alibi. The evidence doesn't match."
-- **ACCUSE MR-HUDSON:** "Mr. Hudson was in servants' quarters. The knife isn't his."
-- **ACCUSE UNKNOWN:** "You must name a specific suspect."
-- **SHOW EVIDENCE TO WRONG PERSON:** "That's not the Inspector."
-
----
-
-## Success Feedback
-
-### Evidence Found
-- "You take the [evidence item] carefully. This could be important."
-- "This [evidence item] might connect to the murder."
-
-### Clue Connected
-- "You make a connection: [clue] points to [suspect]."
-- "The pieces are falling into place."
-
-### Puzzle Solved
-- "The lock clicks open. You can now enter the study."
-- "The wall slides open, revealing a secret passage."
-- "You've identified the poison. Now to find the antidote."
-
-### Accusation Correct
-- "Dr. Moriarty, you are under arrest for the murder of Lord Ashworth."
-- "The inspector reads the evidence. 'Case closed.'"
-
-### Game Won
-- "Congratulations! You have solved the murder of Lord Ashworth."
-- "Your reputation as a detective is secured."
-
----
-
-## Hint Writing Guidelines
-
-### Progressive Disclosure
-1. **Tier 1:** Draw attention to the problem area
-2. **Tier 2:** Point toward the solution path
-3. **Tier 3:** Describe the specific action needed
-4. **Tier 4:** Provide exact command syntax
-
-### Tone
-- Maintain Victorian atmosphere in hints
-- Be encouraging, not condescending
-- Avoid spoiling other puzzles
-- Keep hints concise
-
-### Fairness
-- Don't give away the solution too easily
-- Make hints relevant to current progress
-- Update hints based on game state
-- Reset hints when puzzle is solved
-
----
-
-## Implementation Notes
-
-### Hint State Tracking
-- Track current hint tier per puzzle
-- Reset tier when puzzle solved
-- Allow players to request specific hint topics
-- Provide GENERAL hints for stuck players
-
-### Hint Delivery
-- Display hints in response to HINTS command
-- Allow HINTS [TOPIC] for specific hints
-- Show available topics in HINTS response
-- Limit hint requests per game session (optional)
-
-### Integration
-- Hints should not break immersion
-- Avoid mechanical language in hints
-- Maintain consistent tone with game text
-- Provide feedback when hint is used
+- Attention → direction → action → exact command.
+- Hint the inference before the syntax.
+- Use nouns printed in current room/object prose.
+- Never reference nonexistent verbs such as `MATCH` or `FIND WOLFSBANE`.
+- Never describe foxglove/charcoal as mandatory until an antidote system exists.
+- Update hints at act boundaries so solved problems disappear.
+- Preserve dry Victorian voice; Hudson's kettle is a useful tonal model.
diff --git a/books/limehouse-killings/work/ITERATION.md b/books/limehouse-killings/work/ITERATION.md
index 9dad6cc..0b316c9 100644
--- a/books/limehouse-killings/work/ITERATION.md
+++ b/books/limehouse-killings/work/ITERATION.md
@@ -1,212 +1,95 @@
-# The Limehouse Killings - Iteration Plan
-
-## Current Status
-
-**Version:** 1.0-alpha
-**Completion:** 85%
-**Known Issues:** 14 (from bug ledger)
-**Test Coverage:** 85% parser, 90% objects, 95% NPCs, 100% puzzles
-
-## Priority 1: Critical Fixes (Must Fix)
-
-### Fix Parser Synonyms
-**Impact:** High
-**Effort:** Low
-**Description:** Implement missing parser synonyms (LOOK AT, SEARCH)
-**Files:** actions.zil
-**Status:** Open
-
-### Fix Disambiguation
-**Impact:** High
-**Effort:** Low
-**Description:** Rename objects with duplicate names (POTS, PORTRAITS)
-**Files:** dungeon.zil
-**Status:** Open
-
-### Fix State Management
-**Impact:** High
-**Effort:** Medium
-**Description:** Ensure LOCKED-BOX requires key/lockpick, INSPECTOR appears after evidence
-**Files:** actions.zil, dungeon.zil
-**Status:** Open
-
-## Priority 2: Important Fixes (Should Fix)
-
-### Fix Softlock Potential
-**Impact:** Medium
-**Effort:** Medium
-**Description:** Block secret passage until study unlocked, require all evidence for accusation
-**Files:** dungeon.zil, actions.zil
-**Status:** Open
-
-### Fix NPC Responses
-**Impact:** Medium
-**Effort:** Low
-**Description:** Add missing NPC responses for invalid topics
-**Files:** actions.zil
-**Status:** Open
-
-### Fix Object Interactions
-**Impact:** Medium
-**Effort:** Low
-**Description:** Ensure all object interactions work correctly
-**Files:** actions.zil
-**Status:** Open
-
-## Priority 3: Polish (Nice to Have)
-
-### Improve Object Descriptions
-**Impact:** Low
-**Effort:** Low
-**Description:** Enhance descriptions for atmosphere
-**Files:** dungeon.zil
-**Status:** Open
-
-### Add Sound Effects (Future)
-**Impact:** Low
-**Effort:** High
-**Description:** Add atmospheric sounds if engine supports it
-**Files:** N/A
-**Status:** Future
-
-### Add Graphics (Future)
-**Impact:** Low
-**Effort:** High
-**Description:** Add location portraits if engine supports it
-**Files:** N/A
-**Status:** Future
-
-## Iteration Schedule
-
-### Week 1: Critical Fixes
-- Day 1-2: Fix parser synonyms
-- Day 3-4: Fix disambiguation issues
-- Day 5-7: Fix state management
-
-### Week 2: Important Fixes
-- Day 1-3: Fix softlock potential
-- Day 4-5: Fix NPC responses
-- Day 6-7: Fix object interactions
-
-### Week 3: Polish
-- Day 1-3: Improve object descriptions
-- Day 4-5: Add missing content
-- Day 6-7: Final testing
-
-### Week 4: Release Preparation
-- Day 1-2: Final bug fixes
-- Day 3-4: Create packaging files
-- Day 5-7: Final testing and release
-
-## Subagent Prompts
-
-### Parser Fix Agent
-```
-Task: Fix parser synonyms in actions.zil
-1. Add LOOK AT as synonym for EXAMINE
-2. Add SEARCH as synonym for LOOK INSIDE
-3. Test all object interactions
-4. Verify no regressions
-```
-
-### Disambiguation Agent
-```
-Task: Fix object name conflicts in dungeon.zil
-1. Rename POTS to COPPER-POTS
-2. Rename PORTRAITS to FAMILY-PORTRAITS
-3. Update all references
-4. Test object interactions
-```
-
-### State Management Agent
-```
-Task: Fix state management in actions.zil
-1. Require key/lockpick for LOCKED-BOX
-2. Trigger INSPECTOR after 5 evidence
-3. Require finding SECRET-LEDGER before taking
-4. Test all state transitions
-```
-
-### Softlock Prevention Agent
-```
-Task: Fix softlock potential in dungeon.zil and actions.zil
-1. Block SECRET-PASSAGE until CIPHER-SOLVED
-2. Require all evidence for accusation
-3. Test edge cases
-4. Verify no dead ends
-```
-
-### NPC Response Agent
-```
-Task: Add missing NPC responses in actions.zil
-1. Add responses for invalid topics
-2. Ensure all conversation paths work
-3. Test NPC interactions
-4. Verify interview tracking
-```
-
-### Content Polish Agent
-```
-Task: Improve object descriptions in dungeon.zil
-1. Enhance atmospheric descriptions
-2. Add more actionable details
-3. Ensure consistent tone
-4. Test player feedback
-```
-
-## Testing Strategy
-
-### After Each Fix
-1. Run walkthrough.zil
-2. Run regression tests
-3. Verify no new bugs
-4. Update bug ledger
-
-### Before Release
-1. Full regression test suite
-2. Playtest with new players
-3. Gather feedback
-4. Final polish
+# The Limehouse Killings - Refactor and Iteration Plan
+
+## Current Baseline
+
+The July 15, 2026 story pass established a playable implementation baseline:
+
+- Topicless `ASK/TELL` is nil-safe for every NPC.
+- `ASK INSPECTOR ABOUT CASE`, `LOCKPICK SET`, and `FOOTPRINT CAST` parse.
+- Lestrade begins offstage and arrives at the Act III threshold.
+- Library cipher/secret route and Ashworth name dial are fiction-understanding gates.
+- Poison is identified with `USE VIAL ON PLANTS`.
+- Hudson, Lady Ashworth, and Moriarty have initial, player-changed, and story-progress states.
+- The final case requires threat, method, and motive, then offers a letter/poison lead-proof choice.
+- Opening telegram supplies a visible object, quick reward, clue, warmth, and humor.
+- Key room prose uses concrete sensory details.
+
+Validation baseline:
+
+- Parser-driven Limehouse walkthrough: 630/630 assertions passing.
+- Full `make test-pure-zil`: passing.
+- Vocabulary audit: zero critical findings.
+
+## Refactor Priority 1 — Make Documentation and Implementation Identical
+
+- [x] Update map, object registry, puzzle graph, story state, hints, prose, and transcript plan.
+- [ ] Copy canonical commands from `TRANSCRIPT_TESTS.md` into any player-facing hints.
+- [ ] Remove old references to `MATCH`, `FIND WOLFSBANE`, key-operated box, immediate Inspector, and held-item victory.
+- [ ] Update `DESIGN.md` and `PLAN.md` in a separate pass if they still describe four acts or the old finale.
+
+Acceptance: a command documented anywhere either passes through `llm.lua` or is clearly labeled future work.
+
+## Refactor Priority 2 — Complete World-State Prose
+
+- [x] Add state-aware look logic for Gate, Dining Room, Greenhouse, Servants' Quarters, Pantry, and Secret Passage.
+- [ ] Add discovery text to all important objects without replaying it on every look.
+- [x] Remove evidence glints/listings after objects move.
+- [x] Ensure each act boundary changes at least two room descriptions and two NPC behaviors.
+- [x] Replace room-level mood labels such as “duty,” “secrets,” or “beckoning” with sensory/physical detail.
+
+Acceptance: every major room has one discovery moment, concise revisit prose, and correct mutable state.
+
+## Refactor Priority 3 — Consequential Tools and Props
+
+- [x] Give magnifying glass an optional footprint-detail reveal used by Moriarty, Lestrade, and the ending.
+- [x] Rewrite the lantern as Hudson's maintained household keepsake, with optional passage color and no implied required utility.
+- [x] Give charcoal a safe recovery response to poison exposure and identify foxglove as another poison.
+- [x] Connect the unlatched wine cabinet to the missing private-laboratory delivery bottle.
+
+Acceptance: every major takeable object has a tool, clue, character, risk, joke, trophy, or memory function.
+
+## Refactor Priority 4 — Deeper NPC Loops
+
+- [x] Make intermediate confrontation states reachable and tested before Act III.
+- [x] Add repeat responses so testimony does not sound newly discovered twice.
+- [x] Add `SHOW/GIVE` responses for footprint, seal, ledger, and statement where they expose character.
+- [ ] Consider physical behavior beyond descriptions: Hudson moves tea, Lady changes table objects, Moriarty blocks/attempts an exit.
+- [ ] Ensure `GIVE` uses correct articles and NPC-specific reactions.
+
+Acceptance: each NPC has three tested states and at least one action that changes world state, not dialogue alone.
+
+## Refactor Priority 5 — Ending Branch Quality
+
+- [x] Replace held-item counter ending with three-link argument.
+- [x] Add lead-proof choice.
+- [ ] Give letter-led and poison-led branches one additional persistent distinction before convergence.
+- [ ] Test attempts to accuse before Lestrade, before presentations, without a lead proof, and with an irrelevant proof.
+- [ ] Confirm both branches reference discoveries and imply next events.
+
+## Testing Workflow
+
+After each slice:
+
+1. Play the exact new command with `llm.lua` from a fresh save.
+2. Add it to `tests/test_limehouse_walkthrough.lua`.
+3. Run `make test-limehouse-walkthrough`.
+4. Run `lua5.4 scripts/check-vocab.lua books/limehouse-killings/dungeon.zil` for prose/vocabulary changes.
+5. Run `make test-pure-zil` before handoff.
+6. Update the work document controlling the changed behavior.
 
 ## Release Criteria
 
-### Must Have
-- [ ] All critical bugs fixed
-- [ ] All important bugs fixed
-- [ ] Parser works correctly
-- [ ] All puzzles solvable
-- [ ] No softlocks
-- [ ] All NPCs functional
-- [ ] Game completable
-
-### Should Have
-- [ ] Atmospheric descriptions
-- [ ] Hint system working
-- [ ] Score system working
-- [ ] Inventory system working
-- [ ] Save/restore (if engine supports)
-
-### Nice to Have
-- [ ] Sound effects
-- [ ] Graphics
-- [ ] Multiple solutions
-- [ ] Easter eggs
-- [ ] Developer commentary
-
-## Post-Release
-
-### Version 1.1
-- Fix any reported bugs
-- Add missing content
-- Improve parser feedback
-
-### Version 2.0
-- Add new puzzles
-- Add new NPCs
-- Expand story
-- Add new areas
-
-### Future
-- Sequel potential
-- Series expansion
-- Community contributions
+- [x] Game completable through typed parser commands.
+- [x] Critical conversation and vocabulary bugs covered by regressions.
+- [x] Two major understanding-based gates.
+- [x] Three visible acts.
+- [x] Delayed Inspector arrival.
+- [x] Evidence-specific ending with player choice.
+- [x] All major rooms have state-aware discovery/revisit prose.
+- [x] All major props have clue, character, risk, recovery, or optional-route roles.
+- [x] NPC intermediate states and repeat responses have transcript coverage.
+- [ ] Organic playtest confirms the new deductions are fair without reading source/docs.
+
+## Suggested Next Vertical Slice
+
+Add a second automated end-to-end run for the poison-led accusation and focused failure transcripts for premature and irrelevant-proof accusations. This would verify the remaining unchecked ending criteria without changing the established case architecture.
diff --git a/books/limehouse-killings/work/MAP.md b/books/limehouse-killings/work/MAP.md
index 9e2c386..28cd845 100644
--- a/books/limehouse-killings/work/MAP.md
+++ b/books/limehouse-killings/work/MAP.md
@@ -1,120 +1,98 @@
-# The Limehouse Killings - Room Map
+# The Limehouse Killings - World Map and Act Overlay
+
+This file is the canonical geography and world-change plan for future `.zil` refactors. Commands and directions match the current parser-driven walkthrough.
 
 ## Room Graph
 
-```
+```text
                     ASHWORTH-MANOR-GATE
-                           |
-                           ↓
-                 ASHWORTH-ENTRANCE-HALL
-                    /     |     \     \
-                   ↓      ↓      ↓     ↓
-               STUDY   LIBRARY  DINING  KITCHEN
-                 ↑       |       |       |
-                 |       ↓       ↓       ↓
-                 |    SECRET   PANTRY   GARDEN
-                 |    PASSAGE            /    \
-                 |       |              ↓      ↓
-                 └───────┘        GREENHOUSE  SERVANTS
-                                         QUARTERS
+                              |
+                            NORTH
+                              |
+                    ASHWORTH-ENTRANCE-HALL
+                   /       /       \        \
+              SOUTH     EAST       WEST     DOWN
+                |         |          |        |
+              STUDY---SECRET      DINING   KITCHEN---GARDEN
+                        PASSAGE      |                  / \
+                          |        PANTRY       GREENHOUSE SERVANTS-
+                       LIBRARY                              QUARTERS
 ```
 
-## Room Details
-
-### ASHWORTH-MANOR-GATE
-- **Exits:** SOUTH (to entrance hall)
-- **Description:** Iron gates, gravel path, fog
-- **Objects:** GATES, PATH, FOG
-- **Role:** Starting area, establishes atmosphere
-
-### ASHWORTH-ENTRANCE-HALL
-- **Exits:** NORTH (to gate), SOUTH (to study - locked), EAST (to library), WEST (to dining room), DOWN (to kitchen)
-- **Description:** Grand foyer, cracked chandelier, portraits
-- **Objects:** CHANDELIER, PORTRAITS, RUG
-- **Role:** Central hub, connecting all areas
-- **Locked Exit:** SOUTH to STUDY (requires KEY or LOCKPICK)
-
-### STUDY
-- **Exits:** NORTH (to entrance hall)
-- **Description:** Crime scene, body outline, desk, fireplace
-- **Objects:** BODY-OUTLINE, DESK, FIREPLACE, WINDOW, LOCKED-BOX, DEAD-LETTER, POISON-BOTTLE
-- **Role:** Primary evidence location
-- **Access:** Locked until KEY found or LOCKPICK used
-
-### LIBRARY
-- **Exits:** WEST (to entrance hall), EAST (to secret passage - hidden)
-- **Description:** Floor-to-ceiling books, reading desk, fireplace
-- **Objects:** BOOKSHELF, READING-DESK, FIREPLACE, TORN-PAGE, COLORED-MARKERS
-- **Role:** Cipher puzzle location
-- **Hidden Exit:** EAST to SECRET-PASSAGE (requires solving book cipher)
-
-### DINING-ROOM
-- **Exits:** EAST (to entrance hall), NORTH (to pantry)
-- **Description:** Long table, wine cabinet, portraits
-- **Objects:** TABLE, WINE-CABINET, PORTRAITS, CANDLESTICK
-- **Role:** NPC encounter (Lady Ashworth), wine cabinet puzzle
-- **Access:** Always open
-
-### KITCHEN
-- **Exits:** UP (to entrance hall), WEST (to garden)
-- **Description:** Copper pots, cold hearth, servant bell
-- **Objects:** POTS, HEARTH, BELL, KNIFE-RACK
-- **Role:** Tool acquisition, servant bell
-- **Access:** Always open
-
-### GARDEN
-- **Exits:** EAST (to kitchen), NORTH (to greenhouse), SOUTH (to servants' quarters)
-- **Description:** Overgrown paths, fountain, hedge maze
-- **Objects:** FOUNTAIN, HEDGES, PATH, BLOOD-STAINED-KNIFE
-- **Role:** Evidence location, connects outdoor areas
-- **Access:** Always open
-
-### GREENHOUSE
-- **Exits:** SOUTH (to garden)
-- **Description:** Glass panels, exotic plants, potting bench
-- **Objects:** PLANTS, BENCH, POTS, POISON-PLANT, LABELS
-- **Role:** Poison identification puzzle
-- **Access:** Always open
-
-### SERVANTS-QUARTERS
-- **Exits:** NORTH (to garden)
-- **Description:** Sparse rooms, servant beds, trunk
-- **Objects:** BEDS, TRUNK, UNIFORMS, LETTER
-- **Role:** NPC encounter (Mr. Hudson), additional evidence
-- **Access:** Always open
-
-### SECRET-PASSAGE
-- **Exits:** WEST (to library), EAST (to study)
-- **Description:** Narrow stone passage, dusty, cobwebs
-- **Objects:** STONE-WALLS, COBWEBS, DUST
-- **Role:** Alternate study access, hidden route
-- **Access:** Requires solving library cipher
-
-## Blocked Exits & Rationale
-
-| Exit | Block | Rationale |
-|------|-------|-----------|
-| ENTRANCE-HALL → STUDY | Locked door | Requires KEY or LOCKPICK |
-| LIBRARY → SECRET-PASSAGE | Hidden wall | Requires book cipher solution |
-
-## Room Count
-
-- **Total Rooms:** 10
-- **Starting Room:** ASHWORTH-MANOR-GATE
-- **Final Room:** STUDY (for final confrontation)
-
-## Navigation Complexity
-
-- **Hub-and-spoke:** ENTRANCE-HALL connects to most rooms
-- **Linear chains:** GARDEN → GREENHOUSE, GARDEN → SERVANTS-QUARTERS
-- **Hidden path:** LIBRARY → SECRET-PASSAGE → STUDY
-- **No dead ends:** All rooms have at least 2 exits (except GREENHOUSE and SERVANTS-QUARTERS which have 1, but connect back to GARDEN)
-
-## Atmospheric Notes
-
-- Fog obscures distant views from GATE
-- Gas lamps flicker in hallway
-- Candles gutter in wind (DINING-ROOM)
-- Shadows move in GARDEN at night
-- Greenhouse glass rattles in wind
-- Servants' quarters feel cramped and poor
+Exact connections:
+
+- Gate `NORTH` → Entrance Hall; Entrance Hall `NORTH` → Gate.
+- Entrance Hall `SOUTH` → Study when the study door is open.
+- Entrance Hall `EAST` → Library; Library `WEST` → Entrance Hall.
+- Entrance Hall `WEST` → Dining Room; Dining Room `EAST` → Entrance Hall.
+- Entrance Hall `DOWN` → Kitchen; Kitchen `UP` → Entrance Hall.
+- Kitchen `WEST` → Garden; Garden `EAST` → Kitchen.
+- Garden `NORTH` → Greenhouse; Greenhouse `SOUTH` → Garden.
+- Garden `SOUTH` → Servants' Quarters; Servants' Quarters `NORTH` → Garden.
+- Dining Room `NORTH` → Pantry; Pantry `SOUTH` → Dining Room.
+- Library `EAST` or `SOUTH` → Secret Passage after the cipher; passage `WEST` → Library and `EAST` → Study.
+
+## Three-Act Overlay
+
+### Act I — Arrival and Exploration (`CASE-ACT = 1`)
+
+- Opening landmark: the iron gates.
+- Visible, usable object: the creased telegram.
+- Quick reward: reading the telegram teaches that Ashworth marked private mechanisms with a relevant name and supplies a warm Hudson/kettle beat.
+- Visible blocker: the locked study door in the hub.
+- Dominant play: orientation, object examination, first interviews, and discovering the colored-book mechanism.
+- Lestrade is offstage.
+
+### Act II — Reconstruction (`CASE-ACT = 2`)
+
+Threshold: solve the library cipher in red, yellow, green, blue order.
+
+Persistent world changes:
+
+- The library gains an open route into the secret passage.
+- The entrance-hall bell wire quivers after the concealed wall moves.
+- The secret passage makes the locked-room geography intelligible: someone could cross between library and study unseen.
+- Dominant play: connect letter, flower, debt, route, footprint, and weapon rather than merely collecting tools.
+
+### Act III — Confrontation (`CASE-ACT = 3`)
+
+Threshold: at least three counted discoveries and all three suspect interviews.
+
+Persistent world changes:
+
+- Lestrade moves into the entrance hall.
+- Moriarty moves toward the front door after the poison interview.
+- The entrance hall describes both men and the imminent escape risk.
+- Hudson, Lady Ashworth, and Moriarty receive late-case descriptions that expose changed behavior.
+- Dominant play: organize discoveries into threat, method, and motive; choose the proof that leads the accusation.
+
+## Room Contracts
+
+| Room | Act I purpose | Later-state obligation | Concrete sensory anchor |
+|---|---|---|---|
+| Gate | Landmark, telegram, onboarding | May reflect dawn in ending only | River damp, coal smoke, wet iron |
+| Entrance Hall | Hub and study-door blocker | Bell wire in Act II; Lestrade/Moriarty in Act III | Beeswax, dust-softened crystal |
+| Library | Moriarty encounter and cipher | Open passage after threshold; Moriarty later absent | Cold grate, leather, colored ribbons |
+| Study | Crime reconstruction and name-dial box | Door/window/box descriptions track physical state | Gritty ash, dried drops, Turkey carpet |
+| Dining Room | Lady Ashworth and interrupted meal | Her posture and objects change by NPC state | Filmed soup, polished cutlery, wax |
+| Kitchen | Tool discovery and navigation | Bell feedback echoes Act II threshold | Blue kettle, cold hearth, copper |
+| Garden | Route evidence, footprint, knife | Should acknowledge evidence removal on revisit | Damp leaves, dry fountain, branches |
+| Greenhouse | Poison comparison | Identified plant should receive a concise revisit line | Humidity, purple flowers, wet glass |
+| Servants' Quarters | Hudson, trunk, lantern | Hudson's late state and possible packed bag | Linen, squeaking polishing cloth |
+| Pantry | Optional poison-risk context and recovery | Charcoal reverses one health loss; foxglove clearly warns against compounding poisons | Cool dry air, charcoal dust |
+| Secret Passage | Locked-room explanation | Open once and remain open | Slick stone, dust, cobwebs |
+
+## Physical Gate Policy
+
+- The study door is a real `DOORBIT` object. It may be opened from inside, unlocked with Hudson's keyring, or picked as an optional physical solution.
+- The primary fiction-understanding route into the study is the library cipher and secret passage.
+- The locked box is not a key gate. It has a name dial and `TURNBIT`; its solution depends on connecting three discoveries.
+- Every mutable route must be represented by object state and/or a room `ACTION` routine, never prose alone.
+
+## Refactor Acceptance Checks
+
+- Every direction above works from a fresh save.
+- Each act boundary changes at least two existing room/NPC descriptions.
+- Lestrade cannot be examined or addressed before Act III.
+- NPCs are visibly listed wherever they are physically present.
+- No room description names an actionable fixture without a parser object or deliberate `PSEUDO` handler.
diff --git a/books/limehouse-killings/work/OBJECTS.md b/books/limehouse-killings/work/OBJECTS.md
index 5ff3fb9..7a1485d 100644
--- a/books/limehouse-killings/work/OBJECTS.md
+++ b/books/limehouse-killings/work/OBJECTS.md
@@ -1,117 +1,78 @@
-# The Limehouse Killings - Object Registry
-
-## Global Objects
-
-| ID | Name | Synonyms | Flags | Location | Puzzle Role |
-|----|------|----------|-------|----------|-------------|
-| FOG | Fog | mist, haze | SCENERY | ASHWORTH-MANOR-GATE | Atmosphere |
-| GATES | Iron Gates | gate, bars | SCENERY | ASHWORTH-MANOR-GATE | Entry barrier |
-| PATH | Gravel Path | walkway, drive | SCENERY | ASHWORTH-MANOR-GATE | Navigation |
-| CHANDELIER | Chandelier | light, crystal | SCENERY | ENTRANCE-HALL | Atmosphere |
-| PORTRAITS | Portraits | paintings, pictures | SCENERY | ENTRANCE-HALL | Atmosphere |
-| RUG | Persian Rug | carpet, mat | SCENERY | ENTRANCE-HALL | Hidden item? |
-
-## Evidence Objects
-
-| ID | Name | Synonyms | Flags | Location | Puzzle Role |
-|----|------|----------|-------|----------|-------------|
-| DEAD-LETTER | Unsent Letter | letter, note, paper | TAKEBIT READBIT | STUDY (on desk) | Key evidence #1 |
-| BLOOD-STAINED-KNIFE | Blood-Stained Knife | knife, blade, weapon | TAKEBIT | GARDEN (in hedge) | Murder weapon |
-| LOCKED-BOX | Locked Box | box, case, container | CONTAINERBIT | STUDY (in fireplace) | Key evidence #2 |
-| POISON-BOTTLE | Poison Bottle | bottle, vial, poison | TAKEBIT READBIT | STUDY (in desk) | Key evidence #3 |
-| SECRET-LEDGER | Secret Ledger | ledger, book, account | TAKEBIT READBIT | LIBRARY (hidden in shelf) | Key evidence #4 |
-
-## Tool Objects
-
-| ID | Name | Synonyms | Flags | Location | Puzzle Role |
-|----|------|----------|-------|----------|-------------|
-| MAGNIFYING-GLASS | Magnifying Glass | glass, lens, magnifier | TAKEBIT | ENTRANCE-HALL (on table) | Examine small clues |
-| LOCKPICK-SET | Lockpick Set | picks, tools | TAKEBIT | KITCHEN (in drawer) | Open locked doors |
-| LANTERN | Lantern | lamp, light | TAKEBIT LIGHTBIT | SERVANTS-QUARTERS | Illuminate dark areas |
-| KEYRING | Keyring | keys, key | TAKEBIT | MR. HUDSON (gives freely) | Open locked study |
-
-## Clue Objects
-
-| ID | Name | Synonyms | Flags | Location | Puzzle Role |
-|----|------|----------|-------|----------|-------------|
-| TORN-PAGE | Torn Page | page, fragment | TAKEBIT READBIT | LIBRARY (on desk) | Cipher clue |
-| COLORED-MARKERS | Colored Markers | markers, ribbons, tags | SCENERY | LIBRARY (on shelves) | Cipher clue |
-| FOOTPRINT-CAST | Footprint Cast | cast, mold, footprint | TAKEBIT | GARDEN (near fountain) | Alibi evidence |
-| WAX-SEAL | Wax Seal | seal, stamp | TAKEBIT | DINING-ROOM (on table) | Identifies letter writer |
-| BANK-STATEMENT | Bank Statement | statement, receipt | TAKEBIT READBIT | STUDY (in locked box) | Financial motive |
-
-## Furniture/Scenery Objects
-
-| ID | Name | Synonyms | Flags | Location | Puzzle Role |
-|----|------|----------|-------|----------|-------------|
-| DESK | Mahogany Desk | desk, table | SCENERY | STUDY | Evidence location |
-| FIREPLACE | Fireplace | hearth, fire | SCENERY | STUDY | Hidden items |
-| WINDOW | Window | glass, pane | SCENERY | STUDY | Alternate entry |
-| BOOKSHELF | Bookshelf | shelves, books | SCENERY | LIBRARY | Cipher puzzle |
-| READING-DESK | Reading Desk | lectern, stand | SCENERY | LIBRARY | Torn page location |
-| TABLE | Dining Table | table, board | SCENERY | DINING-ROOM | NPC encounter |
-| WINE-CABINET | Wine Cabinet | cabinet, cupboard | SCENERY | DINING-ROOM | Hidden compartment |
-| POTS | Copper Pots | pans, cookware | SCENERY | KITCHEN | Atmosphere |
-| HEARTH | Cold Hearth | stove, oven | SCENERY | KITCHEN | Tool location |
-| BELL | Servant Bell | bell, rope | SCENERY | KITCHEN | Summon NPCs |
-| FOUNTAIN | Fountain | well, basin | SCENERY | GARDEN | Evidence location |
-| HEDGES | Hedge Maze | hedges, bushes | SCENERY | GARDEN | Knife location |
-| PLANTS | Exotic Plants | plants, flowers | SCENERY | GREENHOUSE | Poison identification |
-| BENCH | Potting Bench | bench, table | SCENERY | GREENHOUSE | Label location |
-| POTS | Flower Pots | pots, containers | SCENERY | GREENHOUSE | Poison source |
-| BEDS | Servant Beds | beds, cots | SCENERY | SERVANTS-QUARTERS | Atmosphere |
-| TRUNK | Trunk | chest, box | SCENERY | SERVANTS-QUARTERS | Hidden items |
-| UNIFORMS | Servant Uniforms | clothes, livery | SCENERY | SERVANTS-QUARTERS | Atmosphere |
-
-## NPC Objects
-
-| ID | Name | Synonyms | Flags | Location | Puzzle Role |
-|----|------|----------|-------|----------|-------------|
-| MR-HUDSON | Mr. Hudson | butler, hudson | NPC | SERVANTS-QUARTERS | Info provider, key holder |
-| LADY-ASHWORTH | Lady Ashworth | lady, wife | NPC | DINING-ROOM | Suspect, alibi provider |
-| DR-MORIARTY | Dr. Moriarty | doctor, moriarty | NPC | LIBRARY | Suspect, poison expert |
-| INSPECTOR | Inspector Lestrade | inspector, lestrade | NPC | ENTRANCE-HALL (final) | Case resolution |
-
-## Object Count
-
-- **Total Objects:** 35
-- **Takeable Objects:** 12
-- **Scenery Objects:** 18
-- **NPC Objects:** 4
-- **Evidence Objects:** 5 (key to winning)
-
-## Object Relationships
-
-- **LOCKED-BOX** contains: BANK-STATEMENT, SECRET-LEDGER
-- **DESK** holds: DEAD-LETTER, POISON-BOTTLE
-- **BOOKSHELF** hides: SECRET-LEDGER, COLORED-MARKERS
-- **GARDEN** contains: BLOOD-STAINED-KNIFE, FOOTPRINT-CAST
-- **WINE-CABINET** contains: WAX-SEAL
-
-## Object States
-
-- **STUDY door:** LOCKED → UNLOCKED (with KEY or LOCKPICK)
-- **SECRET-PASSAGE:** HIDDEN → REVEALED (with cipher solution)
-- **LOCKED-BOX:** CLOSED → OPENED (with KEY)
-- **LANTERN:** UNLIT → LIT (with matches)
-- **WINE-CABINET:** CLOSED → OPENED (with KEY)
-
-## Parser Expectations
-
-- **EXAMINE:** Detailed description of object
-- **TAKE:** Pick up object (if TAKEBIT)
-- **DROP:** Put down object
-- **USE:** Context-dependent action
-- **OPEN/CLOSE:** For containers
-- **READ:** For readable objects
-- **ASK/TELL:** For NPCs
-- **SHOW:** Show item to NPC
-
-## Object Interactions
-
-- **MAGNIFYING-GLASS + FOOTPRINT-CAST:** Reveals boot size
-- **LOCKPICK-SET + STUDY DOOR:** Opens locked door
-- **KEY + LOCKED-BOX:** Opens box
-- **POISON-BOTTLE + GREENHOUSE PLANTS:** Identifies poison type
-- **DEAD-LETTER + LADY-ASHWORTH:** Confrontation
-- **BLOOD-STAINED-KNIFE + DR-MORIARTY:** Accusation
+# The Limehouse Killings - Object and Vocabulary Registry
+
+This registry records parser-facing names and narrative roles. `DESC` text is not vocabulary; every canonical command must be backed by `SYNONYM` and `ADJECTIVE` entries.
+
+## Opening and Evidence Objects
+
+| ID | Canonical phrase | Natural variants | Initial location | Role/state |
+|---|---|---|---|---|
+| `TELEGRAM` | creased telegram | telegram, message, wire | Gate | Visible opening object and quick reward; teaches the name-marked mechanism convention |
+| `DEAD-LETTER` | unsent letter | letter, note, paper | Study | Threat/intent discovery; guarded by `DEAD-LETTER-FOUND` |
+| `POISON-BOTTLE` | poison bottle | bottle, vial | Study | Method clue; compare `VIAL` with greenhouse plants |
+| `BLOOD-STAINED-KNIFE` | blood-stained knife | knife, blade, weapon | Garden | Route/weapon evidence; guarded by `KNIFE-FOUND` |
+| `SECRET-LEDGER` | secret ledger | ledger, account, book | Library | Debt clue; guarded by `SECRET-LEDGER-FOUND` |
+| `BANK-STATEMENT` | bank statement | statement, receipt | Locked box | Motive corroboration; guarded by `BANK-STATEMENT-FOUND` |
+| `FOOTPRINT-CAST` | footprint cast | footprint, cast, mold, impression | Garden | Excludes Lady Ashworth and later matches Moriarty's heel |
+| `WAX-SEAL` | wax seal | seal, stamp | Dining Room | Visual `M` clue and optional corroboration |
+
+## Puzzle and Tool Objects
+
+| ID | Canonical phrase | Natural variants | Location | Contract |
+|---|---|---|---|---|
+| `STUDY-DOOR` | study door | door, oak door, south door | Local global | Real door controlling the north/south route; key/lockpick are optional solutions |
+| `LOCKED-BOX` | locked box | box, case, container | Study fireplace | `CONTBIT SEARCHBIT TURNBIT`; name dial, never opened by key/lockpick |
+| `TORN-PAGE` | torn page | page, fragment | Library | Explicit red-yellow-green-blue clue |
+| `COLORED-MARKERS` | colored markers | markers, ribbons, tags | Library | Environmental half of cipher clue |
+| `RED-BOOK` etc. | red-marked book | red book, yellow book, green book, blue book | Library | Four distinct parser objects; `PUSH` advances/reset cipher |
+| `MAGNIFYING-GLASS` | magnifying glass | glass, lens, magnifier | Entrance Hall | Reveals the crescent nick in the footprint cast's right heel |
+| `LEATHER-ROLL` | leather roll | roll, leather case | Kitchen drawer | Openable container holding picks |
+| `LOCKPICK-SET` | lockpick set | lockpick, set, picks, tools | Leather roll | Optional physical route/tool, not a required major gate |
+| `KEYRING` | keyring | keys, key | Hudson | Optional study-door solution and Hudson trust response |
+| `LANTERN` | oil lantern | lantern, lamp, light | Servants' Quarters | Hudson's maintained keepsake; explicitly not presented as a required darkness tool |
+| `FOXGLOVE` | foxglove | digitalis | Pantry | Dangerous digitalis contrast; refuses unsafe self-medication |
+| `CHARCOAL` | charcoal | coal | Pantry | Recoverable response to tasting poison; restores one lost health point |
+
+## Major Scenery and Containers
+
+| ID | Room | Required nouns/commands | Function |
+|---|---|---|---|
+| `GATES`, `PATH`, `FOG` | Gate | examine gates/path/fog | Opening landmark and sensory frame |
+| `CHANDELIER`, `PORTRAITS`, `RUG` | Hall | examine chandelier/portraits/rug | Hub texture; portraits are a candidate place for additional name-dial foreshadowing |
+| `DESK`, `FIREPLACE`, `WINDOW`, `CHALK-OUTLINE` | Study | examine each; open window | Crime reconstruction and physical route model |
+| `BOOKSHELF`, `READING-DESK` | Library | examine/push bookshelf; examine desk | Cipher affordance |
+| `TABLE`, `WINE-CABINET` | Dining Room | examine table/cabinet; open cabinet | Interrupted meal and missing private-laboratory delivery bottle |
+| `POTS`, `HEARTH`, `SERVANT-BELL`, `DRAWER` | Kitchen | examine; pull/use bell; open drawer | Warm contrast, feedback, tool container |
+| `FOUNTAIN`, `HEDGES` | Garden | examine fountain/hedges | Surface footprint and knife discoveries |
+| `PLANTS`, `LABELS`, `BENCH` | Greenhouse | examine plants/labels; use vial on plants | Poison comparison |
+| `BEDS`, `TRUNK`, `UNIFORMS`, `TRUNK-LETTER` | Quarters | examine/open/read | Hudson environment and secondary testimony |
+| `SHELVES` | Pantry | examine shelves | Ingredient context |
+| `STONE-WALLS`, `COBWEBS`, `DUST` | Passage | examine | Locked-room route and age |
+
+## NPC Registry
+
+| ID | Canonical listener | Vocabulary | Initial location | Movement |
+|---|---|---|---|---|
+| `MR-HUDSON` | Mr. Hudson | Hudson, butler; adjectives Mr/Mister | Servants' Quarters | Static, description changes by case state |
+| `LADY-ASHWORTH` | Lady Ashworth | Ashworth, wife; adjective Lady | Dining Room | Static, description changes by case state |
+| `DR-MORIARTY` | Dr. Moriarty | Moriarty, doctor; adjectives Dr/Doctor | Library | Moves to Entrance Hall after poison interview |
+| `INSPECTOR` | Inspector Lestrade | inspector, Lestrade, officer, police | Offstage | Moves to Entrance Hall only at Act III threshold |
+
+## Topic Objects
+
+Global topic objects support `ASK/TELL ... ABOUT ...`: master, alibi, key, Moriarty, marriage, experiments/research, poison/wolfsbane, and case/murder. Actor routines must guard `PRSI` before every containment/equality operation so topicless `ASK NPC` cannot crash.
+
+## Vocabulary Collision Rules
+
+- `SET` and `CAST` are also substrate verbs. At game start their noun senses are re-registered so `TAKE LOCKPICK SET` and `TAKE FOOTPRINT CAST` work.
+- `INSPECTOR` truncates to the same six-letter dictionary form as `INSPECT`; its object sense is likewise re-registered.
+- Prefer unambiguous canonical puzzle commands such as `USE VIAL ON PLANTS` where `POISON` can resolve to both a topic and a physical bottle.
+- Test spaced and hyphenated variants where the prose teaches both.
+
+## Progress Guard Policy
+
+`TAKE`, `READ`, and `EXAMINE` may expose the same clue, but each corresponding `*-FOUND` flag may increment `EVIDENCE-FOUND` only once. Opening the box is separate from discovering/reading its bank statement.
+
+## Optional Evidence State
+
+- `FOOTPRINT-DETAIL-FOUND` records the magnifying-glass discovery and unlocks exact heel-match prose from Moriarty, Lestrade, and the ending.
+- `CABINET-CLUE-SEEN` records the missing medicinal-delivery bottle and changes Dining Room revisit prose.
diff --git a/books/limehouse-killings/work/PROSE.md b/books/limehouse-killings/work/PROSE.md
index 91c9edb..baab80e 100644
--- a/books/limehouse-killings/work/PROSE.md
+++ b/books/limehouse-killings/work/PROSE.md
@@ -1,393 +1,162 @@
-# The Limehouse Killings - Content Writing & NPC Layer
+# The Limehouse Killings - Prose and NPC Bible
 
-## Room Descriptions
+## Voice Rules
 
-### ASHWORTH-MANOR-GATE
+1. Show mood through observable detail. Use temperature, texture, smell, sound, posture, and object placement instead of words such as “regret,” “dread,” “ominous,” or “calculating.”
+2. Keep room text spatial and actionable: usually one to four sentences with one dominant anchor.
+3. Every concrete noun that invites action must resolve through an object, global, or `PSEUDO` handler.
+4. First discovery text creates a moment; revisits are concise and state-aware.
+5. Horror/noir needs contrast. Preserve at least three non-grim beats: Hudson's kettle, the scholarly warmth/colored ribbons of the library, and dawn lifting over the Thames.
+6. NPC emotion appears as behavior: a repeated polishing motion, filmed soup, tapping fingernail, muddy heel, packed bag—not labels.
 
-**First Visit:**
-The iron gates of Ashworth Manor loom before you, their rusted bars silhouetted against the fog-choked sky. A gravel path leads north to the manor house, disappearing into the mist. The gas lamps along the path flicker weakly, casting long shadows that dance like specters. The air smells of coal smoke and river damp.
+## Three-Act Prose Palette
 
-**Revisit:**
-The iron gates stand as before, a sentry to the manor's secrets. The gravel path crunches underfoot.
+| Act | Dominant texture | Counter-tone | Avoid |
+|---|---|---|---|
+| I — Exploration | Fog, wet iron, beeswax, cold rooms | Telegram humor, kettle warmth, colored ribbons | Calling every room grim or haunted |
+| II — Reconstruction | Grit, dried drops, botanical humidity, slick stone | Satisfaction of mechanisms clicking into place | Expository “you realize” paragraphs |
+| III — Confrontation | Rain on coats, packed bag, muddy heel, notebook pencil | Tea for four, dawn, promise of another case | Generic congratulations or reputation summary |
 
-**Actionable Nouns:** gates, path, fog, gas lamps
+## Room Discovery and Revisit Targets
 
-### ASHWORTH-ENTRANCE-HALL
+### Ashworth Manor Gate
 
-**First Visit:**
-You step into a grand foyer that has seen better days. A crystal chandelier hangs from the ceiling, its prisms dull with dust. Portraits of the Ashworth family line the walls, their eyes following your every move. A Persian rug covers the floor, its patterns faded but still elegant. The air is thick with the scent of old wood and regret.
+Discovery: iron bars against fog; river damp and coal smoke; telegram pinned beneath a stone.
 
-**Revisit:**
-The entrance hall greets you with its faded grandeur. The chandelier, portraits, and rug remain as before.
+Quick reward: the telegram teaches Ashworth's habit of marking private mechanisms with the relevant person's name. Hudson's kettle postscript adds warmth and humor.
 
-**Actionable Nouns:** chandelier, portraits, rug, doors
+Revisit: wet gravel, open gate, manor visible north. Do not replay the entire opening tableau.
 
-### STUDY
+### Entrance Hall
 
-**First Visit:**
-The study is a crime scene. A chalk outline marks where the body lay, the victim struck down in this very room. A mahogany desk stands against the wall, its surface cluttered with papers. The fireplace contains cold ashes and a small locked box. A window looks out to the garden, its latch rusted but intact. The air hangs heavy with the memory of violence.
+Discovery: dust softens chandelier crystals; beeswax sharpens old-oak smell; study door visibly blocks south.
 
-**Revisit:**
-The study remains as you found it, a testament to the crime committed here. The chalk outline, desk, fireplace, and window await your attention.
+- Act II: servant-bell wire still quivers after the hidden wall opens.
+- Act III: Lestrade stands with notebook open; Moriarty watches the front door and fog.
 
-**Actionable Nouns:** chalk outline, desk, fireplace, window, locked box
+### Study
 
-### LIBRARY
+Discovery: chalk outline interrupts Turkey carpet; three drops dried nearly black; cold ash grits underfoot.
 
-**First Visit:**
-Floor-to-ceiling bookshelves line the walls, their contents ranging from leather-bound classics to modern scientific texts. A reading desk stands near the fireplace, its surface scattered with papers. Colored markers dot the shelves, suggesting some organizational system. The fire is cold, but the room retains a scholarly warmth.
+Revisits track study door, window, and name-dial box physically: locked/unlocked/open, closed/open, sealed/open.
 
-**Revisit:**
-The library welcomes you with its wall of books. The reading desk, fireplace, and colored markers remain as before.
+### Library
 
-**Actionable Nouns:** bookshelves, reading desk, fireplace, colored markers, books
+Discovery: cold grate, leather bindings, colored ribbons interrupting orderly shelves; Moriarty taps a four-beat rhythm.
 
-### DINING-ROOM
+After cipher: describe the open passage as a physical route, not a “beckoning dark mouth” mood label.
 
-**First Visit:**
-A long dining table dominates the room, set for two but used by only one. Portraits of the family hang above, their expressions disapproving. A wine cabinet stands against the wall, its glass doors reflecting the dim light. The air smells of polish and unused cutlery.
+### Dining Room
 
-**Revisit:**
-The dining room maintains its formal atmosphere. The table, portraits, and wine cabinet await your inspection.
+Discovery: two place settings but filmed soup at one; Lady Ashworth's knife precisely aligned; crimson seal at empty place.
 
-**Actionable Nouns:** table, portraits, wine cabinet, place settings
+Confronted state: paper rattles against wedding ring. Late state: black ribbon laid beside plate while she listens for Lestrade.
 
-### KITCHEN
+### Kitchen
 
-**First Visit:**
-A kitchen that has seen better days. Copper pots hang from the ceiling, tarnished with age. The hearth is cold, its last fire long extinguished. A servant bell hangs from the wall, its rope leading up to the servant's quarters. A drawer in the counter is slightly open, promising something useful.
+Discovery: cold hearth, tarnished copper, blue kettle ready on range. This is a deliberate warm domestic contrast.
 
-**Revisit:**
-The kitchen remains as you found it, a place of former warmth now grown cold. The pots, hearth, bell, and drawer await your attention.
+Drawer text must reflect closed/open state and reveal the leather roll only when visible.
 
-**Actionable Nouns:** copper pots, hearth, servant bell, drawer
+### Garden
 
-### GARDEN
+Discovery: damp branches, dry fountain, plaster footprint, glinting knife. Avoid generic “shadows hiding secrets.”
 
-**First Visit:**
-An overgrown garden sprawls before you, its paths choked with weeds. A fountain stands at the center, dry and silent. Hedge mazes line the paths, their shadows hiding secrets. Something glints in the branches near the fountain - a knife, stained with something dark.
+Revisit removes glints and listed evidence after the player takes them.
 
-**Revisit:**
-The garden remains overgrown and mysterious. The fountain, hedges, and the knife in the hedge await your examination.
+### Greenhouse
 
-**Actionable Nouns:** fountain, hedges, paths, knife in hedge
+Discovery: humidity beads on glass; purple wolfsbane flowers; paper labels curl in damp air.
 
-### GREENHOUSE
+After identification: a concise line should connect the clipped/missing plant material to the vial if implemented.
 
-**First Visit:**
-A glass greenhouse filled with exotic plants. Labels mark the pots, identifying species from around the world. A potting bench stands near the door, its surface covered in soil and tools. The air is warm and humid, a stark contrast to the fog outside.
+### Servants' Quarters
 
-**Revisit:**
-The greenhouse welcomes you with its tropical warmth. The plants, labels, and bench remain as before.
+Discovery: clean worn linen, trunk, lamp, Hudson's squeaking polishing cloth.
 
-**Actionable Nouns:** plants, labels, potting bench, pots
+Late state: packed carpetbag and misbuttoned coat replace abstract nervousness.
 
-### SERVANTS' QUARTERS
+### Pantry
 
-**First Visit:**
-Sparse rooms with simple beds for the household staff. A large trunk sits in the corner, its contents hidden. Servant uniforms hang on hooks, their fabric worn from use. Mr. Hudson, the butler, is here, his expression troubled.
+Discovery: cool dry air, charcoal dust, labeled foxglove. Do not call these “antidote ingredients” unless gameplay makes that claim true.
 
-**Revisit:**
-The servants' quarters remain sparse and functional. The beds, trunk, uniforms, and Mr. Hudson await your attention.
+### Secret Passage
 
-**Actionable Nouns:** beds, trunk, uniforms, Mr. Hudson
+Discovery: slick stone, undisturbed dust, cobwebs catching on sleeves; route clearly connects Library and Study.
 
-### SECRET-PASSAGE
+If the lantern becomes mechanical, darkness and light state belong here.
 
-**First Visit:**
-A narrow stone passage, its walls slick with moisture. Dust and cobwebs fill the air, undisturbed for years. The passage leads west to the library and east to the study, a hidden route through the manor's heart.
+## Important Object Discovery Text
 
-**Revisit:**
-The secret passage remains as you found it, a dusty corridor connecting library and study.
+| Object | Discovery moment | Revisit/use focus |
+|---|---|---|
+| Telegram | Rain-spotted paper under gate stone | Name-marking convention and kettle warmth |
+| Letter | Yellow envelope among desk papers | Threat to expose Moriarty |
+| Vial | Clear liquid with faded Aconitum label | Cross-location botanical identity |
+| Knife | Metal glint in damp branches | Surgical form and dried blood |
+| Footprint cast | White plaster beside dark fountain | Size and worn heel |
+| Ledger | Leather book amid scientific papers | Exact £500 debt |
+| Locked box | Name dial and three tiny engravings | No keyhole; letter/flower/debt inference |
+| Bank statement | Paper revealed by dial | Corroborates ledger, not a standalone “motive established” dump |
+| Magnifying glass | Brass handle worn smooth | Reveals the crescent nick in the cast's right heel |
+| Lantern | Clean glass, full fuel, servants' initials beneath base | Hudson's non-promissory household keepsake; optional warm light in passage |
 
-**Actionable Nouns:** stone walls, cobwebs, dust
+## NPC Behavior Matrices
 
----
+### Mr. Hudson
 
-## Object Descriptions
+| Phase | Player-visible behavior | Executable interaction |
+|---|---|---|
+| Initial | Polishes one spoon repeatedly | `ASK HUDSON ABOUT MASTER/ALIBI/KEY` |
+| Player-changed | Stops polishing; admits carrying the threat letter upstairs | `SHOW LETTER TO HUDSON` before Act III |
+| Story-changed | Packed bag, wrong coat buttons, relief at being noticed | Return after Lestrade arrives |
 
-### Evidence Objects
+Dialogue voice: formal, compressed, protective of household ritual. His warmth appears through practical care, especially tea.
 
-**DEAD-LETTER:**
-An unsent letter, its paper yellowed with age. The ink is faded but legible, the words a threat from one man to another. The seal is broken, the wax still bearing the initial "M."
+### Lady Ashworth
 
-**BLOOD-STAINED-KNIFE:**
-A sharp blade, its edge stained with dried blood. The handle bears the mark of a surgical instrument, the kind used by doctors and scientists.
+| Phase | Player-visible behavior | Executable interaction |
+|---|---|---|
+| Initial | Untouched soup, geometrically aligned cutlery | `ASK LADY ABOUT MARRIAGE/ALIBI` |
+| Player-changed | Ring and paper betray a tremor; admits destroying first draft | `SHOW LETTER TO LADY` before Act III |
+| Story-changed | Mourning ribbon removed; listening for police | Return after Lestrade arrives |
 
-**LOCKED-BOX:**
-A small ornate box, its surface carved with intricate patterns. A keyhole stares up at you, promising secrets within.
+Dialogue voice: controlled and economical. Avoid “cold,” “calculating,” and “composure cracking”; show the physical cost of control.
 
-**POISON-BOTTLE:**
-A small glass bottle, its label reading "Aconitum - Wolfsbane. Highly poisonous." The liquid inside is clear, its lethality hidden in plain sight.
+### Dr. Moriarty
 
-**SECRET-LEDGER:**
-A leather-bound book, its pages filled with numbers and names. Financial records that tell a story of debt and desperation.
+| Phase | Player-visible behavior | Executable interaction |
+|---|---|---|
+| Initial | Four-beat fingernail tap beside scientific folios | `ASK MORIARTY ABOUT EXPERIMENTS` |
+| Player-changed | Sweat at collar, gloved hand pocketed, eyes counting exits | `SHOW LETTER TO MORIARTY` or poison confrontation |
+| Story-changed | Moves to hall; muddy heel matches footprint | Return/examine in Act III |
 
-### Tool Objects
+Dialogue voice: precise, superior, involuntarily over-specific when threatened.
 
-**MAGNIFYING-GLASS:**
-A brass magnifying glass, its lens clear and strong. Useful for examining small details that the naked eye might miss.
+### Inspector Lestrade
 
-**LOCKPICK-SET:**
-A set of metal picks, their tips worn from use. Tools of the trade for those who need to open locked doors.
+| Phase | Player-visible behavior | Executable interaction |
+|---|---|---|
+| Offstage | Not in scope | Any early reference reports he is absent |
+| Receiving case | Rain on shoulders, blank notebook page | `ASK INSPECTOR ABOUT CASE`; show three links |
+| Case complete | Notebook labels THREAT, METHOD, MOTIVE | Accuse and choose leading proof |
 
-**LANTERN:**
-A brass lantern, its glass clouded with age. When lit, it casts a warm glow that pushes back the darkness.
+Dialogue voice: procedural but not mechanical. He translates objects into an evidentiary chain.
 
-**KEYRING:**
-A ring of keys, each one opening a different lock. The study key hangs among them, waiting to be used.
+## Ending Contract
 
-### Clue Objects
+The ending must:
 
-**TORN-PAGE:**
-A fragment of paper, its edges ragged. The text reads: "Follow the rainbow order. Red, orange, yellow, green, blue, violet. Only then will the way open."
+- Reference the greenhouse/vial connection and the ledger/statement/name-dial connection.
+- Use footprint/knife/escape behavior as corroborating route evidence.
+- Let the player lead with letter or poison, producing distinct immediate payoffs.
+- Show consequences for Hudson and Lady Ashworth.
+- End on dawn, tea, the Thames, and Lestrade's next impossible file.
 
-**COLORED-MARKERS:**
-Small ribbons of color, tied to the bookshelves. Red, blue, green, and yellow markers suggest an organizational system.
+Never end with only “Congratulations,” “case closed,” or a reputation counter.
 
-**FOOTPRINT-CAST:**
-A plaster cast of a boot print, size 10. Too large for Lady Ashworth, too small for Mr. Hudson.
+## Parser Trust Checklist
 
-**WAX-SEAL:**
-A broken wax seal, its surface bearing the initial "M." The mark of Dr. Moriarty.
-
-**BANK-STATEMENT:**
-A financial statement showing Dr. Moriarty's account overdrawn. A large withdrawal for "experimental supplies" catches your eye.
-
-### Furniture/Scenery Objects
-
-**DESK:**
-A mahogany desk, its surface scarred with use. Three drawers, one locked, contain the remnants of Lord Ashworth's work.
-
-**FIREPLACE:**
-A stone fireplace, its hearth cold. Ashes and a locked box remain from the last fire.
-
-**WINDOW:**
-A tall window, its glass clouded with age. The latch is rusted but intact, looking out to the garden.
-
-**BOOKSHELF:**
-Floor-to-ceiling shelves, filled with books of every description. Colored markers dot the spines, suggesting a hidden pattern.
-
-**READING-DESK:**
-A wooden desk, its surface scattered with papers. A torn page lies among them, its message waiting to be read.
-
-**TABLE:**
-A long dining table, set for two but used by only one. Wax seals and place settings tell a story of interrupted meals.
-
-**WINE-CABINET:**
-A glass-fronted cabinet, its shelves filled with fine wines and spirits. A lock secures its contents.
-
-**POTS:**
-Copper pots, tarnished with age, hang from the kitchen ceiling. They have cooked many meals, but none recently.
-
-**HEARTH:**
-A stone hearth, cold and empty. The last fire burned long ago.
-
-**BELL:**
-A servant bell, its rope leading up to the servant's quarters. A pull summons the staff.
-
-**FOUNTAIN:**
-A stone fountain, dry and silent. Coins lie at the bottom, wishes unfulfilled.
-
-**HEDGES:**
-Tall hedges, their branches thick and tangled. They hide secrets in their shadows.
-
-**PLANTS:**
-Exotic plants from around the world, their leaves and flowers a splash of color in the gray manor.
-
-**BENCH:**
-A wooden potting bench, its surface covered in soil and tools. Labels identify the plants it tends.
-
-**BEDS:**
-Simple beds for the household staff, their sheets worn but clean.
-
-**TRUNK:**
-A large wooden trunk, its lid heavy. It contains the servant's belongings and secrets.
-
-**UNIFORMS:**
-Servant uniforms, their fabric worn from use. They hang on hooks, waiting for their next wearer.
-
----
-
-## NPC Topic Tables
-
-### MR. HUDSON (Butler)
-
-**Topics:**
-- MASTER: "Lord Ashworth was a difficult man. He fired me last week."
-- ALIBI: "I was here in the servants' quarters all evening. You can check with the other servants."
-- KEY: "I suppose you'll need this." (gives key)
-- MORIARTY: "Dr. Moriarty? He visited often. He and the master had... disagreements."
-- HOUSEHOLD: "The household has been in decline for months. Lord Ashworth's investments failed."
-- STAFF: "The other servants have dispersed. Only I remain."
-- EVENING: "I heard arguing from the study around nine. Then silence."
-
-**Demeanor:** Nervous, evasive, but ultimately cooperative. He wants the case solved.
-
-**Key Info:** Has study key, saw someone near study door, heard arguing.
-
-### LADY ASHWORTH (Wife)
-
-**Topics:**
-- MARRIAGE: "Our marriage was... complicated. Lord Ashworth was not an easy man."
-- ALIBI: "I was in the drawing room all evening. I heard nothing."
-- ENEMIES: "My husband had many enemies. His business practices were... aggressive."
-- MORIARTY: "Dr. Moriarty was a frequent guest. My husband owed him money."
-- FINANCES: "The household finances were in disarray. Lord Ashworth made poor investments."
-- EVENING: "I retired early. The servants can confirm."
-- STUDY: "I never entered the study. It was his private domain."
-
-**Demeanor:** Cold, calculating, too composed for a grieving widow.
-
-**Key Info:** Claims alibi, knows about debts, mentions Moriarty's visits.
-
-### DR. MORIARTY (Scientist)
-
-**Topics:**
-- EXPERIMENTS: "My research is on rare poisons and their antidotes. Purely scientific."
-- POISON: "Wolfsbane? Aconitum? I have some in my greenhouse. For research."
-- RELATIONSHIP: "Lord Ashworth and I were colleagues. He funded my research."
-- DEBTS: "I owed him money? Perhaps. But I was paying it back."
-- ALIBI: "I was at my laboratory all evening. Ask my assistant."
-- GREENHOUSE: "My greenhouse is my sanctuary. I tend my plants there."
-- EVENING: "I visited Lord Ashworth earlier that day. We argued about money."
-
-**Demeanor:** Brilliant, arrogant, dismissive. He thinks he's above suspicion.
-
-**Key Info:** Has poison expertise, owed money, no strong alibi.
-
-### INSPECTOR LESTRADE (Final NPC)
-
-**Topics:**
-- CASE: "What have you found, detective?"
-- EVIDENCE: "Present your evidence and I will make the arrest."
-- MORIARTY: "Dr. Moriarty? A respected scientist. You'll need strong evidence."
-- ARREST: "Make your accusation and show me the proof."
-
-**Demeanor:** Professional, skeptical, but willing to listen.
-
-**Key Info:** Requires evidence before acting, will arrest if convinced.
-
----
-
-## Hint Tiers
-
-### Puzzle 1: Study Entry
-
-**Tier 1 (Attention):**
-"The study door is locked. Perhaps someone has the key."
-
-**Tier 2 (Direction):**
-"The butler might know where the key is kept. Or perhaps there's another way in."
-
-**Tier 3 (Action):**
-"Ask Mr. Hudson about the key, but be persistent. Alternatively, check the garden for another entrance."
-
-**Tier 4 (Command):**
-`ASK HUDSON ABOUT KEY` or `USE LOCKPICK ON WINDOW`
-
-### Puzzle 2: Library Cipher
-
-**Tier 1 (Attention):**
-"The bookshelf has colored markers. Perhaps they mean something."
-
-**Tier 2 (Direction):**
-"The torn page mentions 'rainbow order'. The markers are colored."
-
-**Tier 3 (Action):**
-"Push the books with colored spines in rainbow order: red, orange, yellow, green, blue, violet."
-
-**Tier 4 (Command):**
-`PUSH RED BOOK THEN BLUE BOOK THEN GREEN BOOK THEN YELLOW BOOK`
-
-### Puzzle 3: Greenhouse Poison
-
-**Tier 1 (Attention):**
-"The poison bottle has a label. Greenhouse plants have labels too."
-
-**Tier 2 (Direction):**
-"Match the poison bottle to a plant in the greenhouse."
-
-**Tier 3 (Action):**
-"Find the wolfsbane plant and take the antidote ingredients."
-
-**Tier 4 (Command):**
-`EXAMINE POISON-BOTTLE THEN FIND WOLFSBANE IN GREENHOUSE`
-
-### Puzzle 4: Final Confrontation
-
-**Tier 1 (Attention):**
-"The evidence must point to one suspect."
-
-**Tier 2 (Direction):**
-"Consider who had means, motive, and opportunity."
-
-**Tier 3 (Action):**
-"Dr. Moriarty had poison, owed money, and no alibi."
-
-**Tier 4 (Command):**
-`ACCUSE DR-MORIARTY`
-
-### General Hints
-
-**Stuck in Game:**
-"If you're stuck, try examining everything in the current room. Look for objects that might be useful."
-
-**No Progress:**
-"Have you talked to all the NPCs? They might have information you need."
-
-**Can't Enter Room:**
-"Some doors are locked. You'll need a key or tool to open them."
-
-**Puzzle Too Hard:**
-"Try reading any notes or letters you've found. They might contain clues."
-
----
-
-## Wrong Attempt Responses
-
-### Study Entry
-- **BREAK DOOR:** "The door is solid oak. You'd need a battering ram."
-- **CLIMB WINDOW (without lockpick):** "The window is too high. You need a tool."
-- **ASK LADY ABOUT KEY:** "I don't have such things. Ask the butler."
-
-### Library Cipher
-- **PUSH RANDOM BOOKS:** "Nothing happens. Perhaps there's an order to follow."
-- **READ ALL BOOKS:** "The books are unremarkable Victorian literature."
-- **ASK HUDSON ABOUT PASSAGE:** "I know of no such thing."
-
-### Greenhouse Poison
-- **SMELL POISON:** "The scent is faint but distinctive. Best not to inhale."
-- **TASTE POISON:** "You feel dizzy. Perhaps that wasn't wise." (lose health)
-- **ASK LADY ABOUT POISON:** "I know nothing of such things." (lying)
-
-### Final Confrontation
-- **ACCUSE LADY-ASHWORTH:** "Lady Ashworth has an alibi. The evidence doesn't match."
-- **ACCUSE MR-HUDSON:** "Mr. Hudson was in servants' quarters. The knife isn't his."
-- **ACCUSE UNKNOWN:** "You must name a specific suspect."
-- **SHOW EVIDENCE TO WRONG PERSON:** "That's not the Inspector."
-
----
-
-## Success Feedback
-
-### Evidence Found
-- "You take the [evidence item] carefully. This could be important."
-- "This [evidence item] might connect to the murder."
-
-### Clue Connected
-- "You make a connection: [clue] points to [suspect]."
-- "The pieces are falling into place."
-
-### Puzzle Solved
-- "The lock clicks open. You can now enter the study."
-- "The wall slides open, revealing a secret passage."
-- "You've identified the poison. Now to find the antidote."
-
-### Accusation Correct
-- "Dr. Moriarty, you are under arrest for the murder of Lord Ashworth."
-- "The inspector reads the evidence. 'Case closed.'"
-
-### Game Won
-- "Congratulations! You have solved the murder of Lord Ashworth."
-- "Your reputation as a detective is secured."
+- “Telegram,” “kettle,” “bell wire,” “name dial,” “engravings,” “purple flower,” “notebook,” and every other actionable noun must have a parser decision: object, pseudo-object, or deliberately non-actionable wording.
+- Compound phrases taught in prose must parse: `lockpick set`, `footprint cast`, `bank statement`, `study door`, `colored markers`.
+- NPC topic rows are commands, not abstract conversation notes.
diff --git a/books/limehouse-killings/work/PUZZLES.md b/books/limehouse-killings/work/PUZZLES.md
index 3dc6a1c..c6fcad1 100644
--- a/books/limehouse-killings/work/PUZZLES.md
+++ b/books/limehouse-killings/work/PUZZLES.md
@@ -1,223 +1,191 @@
-# The Limehouse Killings - Puzzle Design
+# The Limehouse Killings - Puzzle Architecture
+
+The central design rule is that deduction, not possession, gates progress. Keys and lockpicks may offer optional physical routes, but at least two major gates must require understanding the fiction.
 
 ## Puzzle Overview
 
-| # | Puzzle | Location | Difficulty | Time |
-|---|--------|----------|------------|------|
-| 1 | Study Entry | ENTRANCE-HALL | Easy | 10 min |
-| 2 | Library Cipher | LIBRARY | Medium | 20 min |
-| 3 | Greenhouse Poison | GREENHOUSE | Medium | 15 min |
-| 4 | Final Confrontation | STUDY | Hard | 15 min |
-
-## Puzzle 1: Study Entry
-
-### Goal
-Enter the locked study where the murder occurred.
-
-### Solution Path
-**Primary:** Get key from Mr. Hudson
-1. ASK HUDSON ABOUT KEY
-2. Hudson refuses initially
-3. ASK HUDSON ABOUT MASTER
-4. Hudson reveals he was fired by Lord Ashworth
-5. ASK HUDSON ABOUT ALIBI
-6. Hudson provides alibi (in servants' quarters)
-7. ASK HUDSON ABOUT KEY (again)
-8. Hudson gives key, wants case solved
-
-**Secondary:** Use lockpick on window
-1. FIND LOCKPICK-SET in KITCHEN
-2. GO TO GARDEN
-3. EXAMINE WINDOW (from outside)
-4. USE LOCKPICK ON WINDOW
-5. Window opens, can enter study
-
-### Clues
-- Butler mentioned carrying key in servants' quarters
-- Window visible from garden, latch appears old
-- TORN-PAGE mentions "study locked from inside"
-
-### Wrong Attempts
-- **BREAK DOOR:** "The door is solid oak. You'd need a battering ram."
-- **CLIMB WINDOW (without lockpick):** "The window is too high. You need a tool."
-- **ASK LADY ABOUT KEY:** "I don't have such things. Ask the butler."
-
-### Hint Tiers
-1. **Attention:** "The study door is locked. Perhaps someone has the key."
-2. **Direction:** "The butler might know where the key is kept."
-3. **Action:** "Ask Mr. Hudson about the key, but be persistent."
-4. **Command:** `ASK HUDSON ABOUT KEY`
-
-### Dependencies
-- None (can be solved first)
-
-### Softlock Prevention
-- Lockpick alternative ensures butler isn't required
-- Window accessible from multiple garden paths
-- No time limit on getting key
-
-## Puzzle 2: Library Cipher
-
-### Goal
-Decode the hidden message in the bookshelf arrangement to reveal secret passage.
-
-### Solution Path
-1. EXAMINE BOOKSHELF
-2. Notice COLORED-MARKERS on shelves (red, blue, green, yellow)
-3. FIND TORN-PAGE on reading desk
-4. READ TORN-PAGE: "Follow the rainbow order"
-5. EXAMINE COLORED-MARKERS
-6. Notice order: red, orange, yellow, green, blue, violet
-7. Push books in rainbow order on marked shelves
-8. Wall slides open, revealing SECRET-PASSAGE
-
-### Clues
-- TORN-PAGE mentions "rainbow order"
-- COLORED-MARKERS visible on bookshelf
-- Some books have colored spines matching markers
-- DR-MORIARTY mentions "hidden study entrance" if asked
-
-### Wrong Attempts
-- **PUSH RANDOM BOOKS:** "Nothing happens. Perhaps there's an order to follow."
-- **READ ALL BOOKS:** "The books are unremarkable Victorian literature."
-- **ASK HUDSON ABOUT PASSAGE:** "I know of no such thing."
-
-### Hint Tiers
-1. **Attention:** "The bookshelf has colored markers. Perhaps they mean something."
-2. **Direction:** "The torn page mentions 'rainbow order'."
-3. **Action:** "Push the books with colored spines in rainbow order."
-4. **Command:** `PUSH RED BOOK THEN BLUE BOOK THEN GREEN BOOK THEN YELLOW BOOK`
-
-### Dependencies
-- None (parallel to Puzzle 1)
-
-### Softlock Prevention
-- Torn page provides clear hint
-- Colored markers are visible without magnification
-- Multiple attempts allowed
-- No penalty for wrong order
-
-## Puzzle 3: Greenhouse Poison
-
-### Goal
-Identify the poison used to kill Lord Ashworth and find antidote ingredients.
-
-### Solution Path
-1. EXAMINE POISON-BOTTLE in STUDY
-2. Read label: "Aconitum - Wolfsbane"
-3. GO TO GREENHOUSE
-4. EXAMINE PLANTS
-5. FIND POISON-PLANT (wolfsbane)
-6. EXAMINE LABELS on pots
-7. MATCH POISON-BOTTLE to plant label
-8. Take antidote ingredients (foxglove, charcoal)
-
-### Clues
-- POISON-BOTTLE label matches plant in greenhouse
-- DR-MORIARTY specializes in rare poisons
-- LADY-ASHWORTH mentions husband's "experimental treatments"
-- TORN-PAGE mentions "wolfsbane remedy"
-
-### Wrong Attempts
-- **SMELL POISON:** "The scent is faint but distinctive. Best not to inhale."
-- **TASTE POISON:** "You feel dizzy. Perhaps that wasn't wise." (lose health)
-- **ASK LADY ABOUT POISON:** "I know nothing of such things." (lying)
-
-### Hint Tiers
-1. **Attention:** "The poison bottle has a label. Greenhouse plants have labels too."
-2. **Direction:** "Match the poison bottle to a plant in the greenhouse."
-3. **Action:** "Find the wolfsbane plant and take the antidote ingredients."
-4. **Command:** `EXAMINE POISON-BOTTLE THEN FIND WOLFSBANE IN GREENHOUSE`
-
-### Dependencies
-- Requires access to STUDY (Puzzle 1)
-- Requires GREENHOUSE exploration
-
-### Softlock Prevention
-- Poison bottle has readable label
-- Plant labels are visible
-- Antidote ingredients are takeable
-- No permanent damage from wrong attempts
-
-## Puzzle 4: Final Confrontation
-
-### Goal
-Present correct evidence to Inspector Lestrade to accuse the killer.
-
-### Solution Path
-1. Gather all 5 evidence items:
-   - DEAD-LETTER (threat from victim)
-   - BLOOD-STAINED-KNIFE (murder weapon)
-   - LOCKED-BOX (with BANK-STATEMENT)
-   - POISON-BOTTLE (rare poison)
-   - SECRET-LEDGER (financial records)
-2. GO TO ENTRANCE-HALL (Inspector arrives)
-3. ASK INSPECTOR ABOUT CASE
-4. ACCUSE DR-MORIARTY
-5. SHOW EVIDENCE TO INSPECTOR (one by one)
-6. Game ends with arrest
-
-### Clues
-- DEAD-LETTER threatens Dr. Moriarty
-- BLOOD-STAINED-KNIFE matches Moriarty's surgical tools
-- BANK-STATEMENT shows Moriarty owed victim money
-- POISON-BOTTLE is rare, only Moriarty has access
-- SECRET-LEDGER shows Moriarty was being blackmailed
-
-### Wrong Attempts
-- **ACCUSE LADY-ASHWORTH:** "Lady Ashworth has an alibi. The evidence doesn't match."
-- **ACCUSE MR-HUDSON:** "Mr. Hudson was in servants' quarters. The knife isn't his."
-- **ACCUSE UNKNOWN:** "You must name a specific suspect."
-- **SHOW EVIDENCE TO WRONG PERSON:** "That's not the Inspector."
-
-### Hint Tiers
-1. **Attention:** "The evidence must point to one suspect."
-2. **Direction:** "Consider who had means, motive, and opportunity."
-3. **Action:** "Dr. Moriarty had poison, owed money, and no alibi."
-4. **Command:** `ACCUSE DR-MORIARTY`
-
-### Dependencies
-- Requires all 5 evidence items
-- Requires all NPCs interviewed
-- Requires INSPECTOR present
-
-### Softlock Prevention
-- Evidence is findable in multiple orders
-- Inspector arrives after sufficient investigation
-- Wrong accusations provide clear feedback
-- Can retry accusation if wrong first time
-
-## Puzzle Dependency Graph
+| Puzzle | Act | Challenge type | Fictional inference | Canonical command |
+|---|---:|---|---|---|
+| Library passage | I → II | Observation and sequence | Torn-page instruction + colored books | Push red, yellow, green, blue books |
+| Greenhouse comparison | II | Cross-location identification | Aconitum on vial = wolfsbane plant | `USE VIAL ON PLANTS` |
+| Ashworth name dial | II | Culprit connection | Letter + purple flower + debt all point to Moriarty | `TURN LOCKED BOX TO MORIARTY` |
+| Lestrade case chain | III | Argument and choice | Threat + method + motive form a case | Show three links, then accuse with letter or poison |
+
+The locked study door is an optional physical obstacle, not a required major puzzle. The fiction-led library passage provides a complete alternate route into the study.
+
+## Puzzle 1 — Library Passage
+
+Goal: discover how someone crossed into the sealed study and enter Act II.
+
+Discoverable information:
+
+- The reading desk exposes a torn page naming “rainbow order.”
+- Colored ribbons and four distinct marked books make the manipulable nouns visible.
+- Each correct push clicks; a wrong push resets the sequence explicitly.
+
+Solution:
 
+```text
+READ TORN PAGE
+EXAMINE COLORED MARKERS
+PUSH RED BOOK
+PUSH YELLOW BOOK
+PUSH GREEN BOOK
+PUSH BLUE BOOK
 ```
-PUZZLE 1 (Study Entry)
-    ↓
-PUZZLE 3 (Greenhouse Poison) ← requires study access
-    ↓
-PUZZLE 4 (Final Confrontation) ← requires all evidence
 
-PUZZLE 2 (Library Cipher) ← parallel, no dependencies
+Consequences:
+
+- `CIPHER-SOLVED`, `SECRET-PASSAGE-FOUND`, and `SECRET-PASSAGE-OPEN` become true.
+- `CASE-ACT` becomes 2.
+- Library and Entrance Hall descriptions change.
+- Secret Passage becomes persistently traversable to the Study.
+
+Fair-failure responses:
+
+- Wrong book: it springs back and the sequence resets.
+- Generic bookshelf push: points toward an order.
+- Repeating after success: acknowledges the passage is already open.
+
+## Puzzle 2 — Greenhouse Poison
+
+Goal: prove that the study vial and greenhouse plant are the same poison source.
+
+Required understanding:
+
+- The vial label says “Aconitum — Wolfsbane.”
+- The purple plant's label uses the same two names.
+- Moriarty admits keeping wolfsbane for research.
+
+Canonical solution:
+
+```text
+EXAMINE VIAL
+EXAMINE PLANTS
+EXAMINE LABELS
+USE VIAL ON PLANTS
+```
+
+Consequences:
+
+- `POISON-IDENTIFIED` becomes true.
+- The fact becomes the method link in the final case.
+- The clue satisfies the purple-flower engraving on the name dial.
+
+This puzzle must never require taking foxglove or charcoal. Those objects are optional until a separate antidote consequence is designed.
+
+## Puzzle 3 — Ashworth Name Dial
+
+Goal: open the fireplace box by identifying the person connecting its engravings.
+
+Examine text presents three engravings:
+
+1. Sealed letter → Ashworth threatened to expose Moriarty.
+2. Purple flower → wolfsbane/Aconitum from Moriarty's research.
+3. Columns of debt → secret ledger records Moriarty's £500 debt.
+
+Required state:
+
+- `DEAD-LETTER-FOUND`
+- `POISON-IDENTIFIED`
+- `SECRET-LEDGER-FOUND`
+
+Canonical solution:
+
+```text
+EXAMINE LOCKED BOX
+TURN LOCKED BOX TO MORIARTY
+```
+
+Consequences:
+
+- `LOCKED-BOX-OPENED` becomes true.
+- Box gains `OPENBIT` and reveals the bank statement.
+- Reading the statement independently records the motive corroboration.
+
+Fair-failure responses:
+
+- `OPEN BOX` or `UNLOCK BOX`: explains there is no keyhole and teaches `TURN BOX TO a name`.
+- Correct name too early: names the three unresolved clue categories without revealing their answer.
+- Wrong name: dial returns to blank.
+- Keyring/lockpick: must not bypass the deduction.
+
+## Puzzle 4 — Lestrade's Case Chain
+
+Goal: transform discoveries into an argument and choose how to present it.
+
+Act III arrival threshold:
+
+- `EVIDENCE-FOUND > 2`
+- `SUSPECTS-INTERVIEWED = 3`
+- Lestrade has not already arrived
+
+Lestrade requests three links:
+
+| Link | Item shown | Meaning | State flag |
+|---|---|---|---|
+| Threat | Unsent letter | Ashworth intended to expose Moriarty | `LETTER-PRESENTED` |
+| Method | Poison bottle | Wolfsbane connects sealed study to greenhouse/research | `POISON-PRESENTED` |
+| Motive | Bank statement | Corroborates the ledger's debt and blackmail | `MOTIVE-PRESENTED` |
+
+Canonical sequence:
+
+```text
+ASK INSPECTOR ABOUT CASE
+SHOW LETTER TO INSPECTOR
+SHOW BOTTLE TO INSPECTOR
+SHOW STATEMENT TO INSPECTOR
+ACCUSE MORIARTY
+```
+
+The bare accusation prompts a final choice:
+
+- `ACCUSE MORIARTY WITH LETTER` leads with Ashworth's voice and draws confirming testimony from Hudson and Lady Ashworth.
+- `ACCUSE MORIARTY WITH POISON` leads with physical evidence and provokes Moriarty into revealing knowledge he should not possess.
+
+Both endings must reference at least two earlier discoveries and imply the next case rather than ending at a numeric victory message.
+
+## Dependency Graph
+
+```text
+Opening telegram
+      |
+Library observations ──> Library sequence ──> Act II / secret route / study
+                                                   |
+                         letter ────────────────────┤
+study vial ──> greenhouse comparison ──────────────┼──> name dial ──> statement
+library ledger ────────────────────────────────────┘
+
+Hudson alibi + Lady alibi + Moriarty poison interview
+                         + 3 discoveries ──> Act III / Lestrade arrives
+
+letter + identified poison + statement ──> present case ──> chosen-proof accusation
 ```
 
-## Verb/Object Response Matrix
-
-| Verb | Object | Response |
-|------|--------|----------|
-| EXAMINE | POISON-BOTTLE | "Label reads: Aconitum - Wolfsbane" |
-| READ | DEAD-LETTER | "My dear Dr. Moriarty, I know what you did..." |
-| TAKE | BLOOD-STAINED-KNIFE | "You take the knife carefully." |
-| USE | LOCKPICK ON DOOR | "The lock clicks open." |
-| ASK | HUDSON ABOUT KEY | "I suppose you'll need this." (gives key) |
-| SHOW | DEAD-LETTER TO LADY | "Where did you get that?" (surprised) |
-| ACCUSE | DR-MORIARTY | "Dr. Moriarty, you are under arrest." |
-
-## Softlock Mitigation List
-
-1. **Study Entry:** Lockpick alternative to key
-2. **Library Cipher:** Clear hint on torn page
-3. **Greenhouse Poison:** Labels match visibly
-4. **Final Confrontation:** Inspector arrives automatically
-5. **No Dead Ends:** All rooms have exit paths
-6. **No Time Limits:** Player explores at own pace
-7. **Multiple Solutions:** Some puzzles have alternatives
-8. **Hint System:** Available for stuck players
+## Likely Command Matrix
+
+| Attempt | Authored result required |
+|---|---|
+| `OPEN STUDY DOOR` | State-aware locked/unlocked/open response |
+| `UNLOCK STUDY DOOR WITH KEYRING` | Optional physical route succeeds |
+| `PUSH BOOKSHELF` | Teaches that individual books and an order matter |
+| Wrong colored book | Resets sequence with explicit feedback |
+| `USE VIAL ON PLANTS` | Identifies poison |
+| `TASTE VIAL` | Telegraphs danger and applies recoverable health loss |
+| `OPEN LOCKED BOX` | Teaches name-dial interaction |
+| `TURN BOX TO HUDSON/LADY` | Rejects wrong connection in-world |
+| `TURN BOX TO MORIARTY` early | Identifies missing categories without opening |
+| `ASK NPC` without topic | Prompts for a topic; never crashes |
+| `ASK INSPECTOR ABOUT CASE` | Explains threat/method/motive presentation |
+| `ACCUSE MORIARTY` early | Explains missing chain or absent Lestrade |
+| Bare final accusation | Offers letter/poison choice |
+
+## Softlock Rules
+
+- Cipher can be retried indefinitely.
+- All evidence counters are one-time guarded transitions.
+- Name dial cannot consume or destroy clues.
+- Wrong accusations do not end the game.
+- Lestrade arrival is checked after both evidence and interview changes.
+- Moriarty and Lestrade are physically co-located in the final hub.
+- Both final choices use evidence already required by the case chain.
diff --git a/books/limehouse-killings/work/STORY_STATE.md b/books/limehouse-killings/work/STORY_STATE.md
index 6afe3a7..79a62db 100644
--- a/books/limehouse-killings/work/STORY_STATE.md
+++ b/books/limehouse-killings/work/STORY_STATE.md
@@ -1,205 +1,155 @@
-# The Limehouse Killings - Story State
-
-## Global Variables
-
-### Game Progress
-
-| Variable | Type | Initial | Description |
-|----------|------|---------|-------------|
-| GAME-WON | BOOLEAN | FALSE | Set TRUE when killer correctly accused |
-| GAME-LOST | BOOLEAN | FALSE | Set TRUE when wrong accusation or death |
-| GAME-ENDED | BOOLEAN | FALSE | Set TRUE when game over (win or lose) |
-
-### Investigation Progress
-
-| Variable | Type | Initial | Description |
-|----------|------|---------|-------------|
-| EVIDENCE-FOUND | COUNTER | 0 | Number of key evidence items found (0-5) |
-| SUSPECTS-INTERVIEWED | COUNTER | 0 | Number of suspects interviewed (0-3) |
-| CLUES-CONNECTED | COUNTER | 0 | Number of clue connections made (0-4) |
-
-### Room Access
-
-| Variable | Type | Initial | Description |
-|----------|------|---------|-------------|
-| STUDY-UNLOCKED | BOOLEAN | FALSE | Set TRUE when study door opened |
-| SECRET-PASSAGE-FOUND | BOOLEAN | FALSE | Set TRUE when passage discovered |
-| SECRET-PASSAGE-OPEN | BOOLEAN | FALSE | Set TRUE when passage wall opened |
-
-### NPC States
-
-| Variable | Type | Initial | Description |
-|----------|------|---------|-------------|
-| HUDSON-INTERVIEWED | BOOLEAN | FALSE | Set TRUE after talking to butler |
-| LADY-INTERVIEWED | BOOLEAN | FALSE | Set TRUE after talking to Lady Ashworth |
-| MORIARTY-INTERVIEWED | BOOLEAN | FALSE | Set TRUE after talking to Dr. Moriarty |
-| HUDSON-KEY-GIVEN | BOOLEAN | FALSE | Set TRUE when butler gives key |
-| HUDSON-MOTIVE-REVEALED | BOOLEAN | FALSE | Set TRUE when butler's motive revealed |
-| LADY-ALIBI-CLAIMED | BOOLEAN | FALSE | Set TRUE when Lady claims alibi |
-| MORIARTY-POISON-KNOWN | BOOLEAN | FALSE | Set TRUE when Moriarty's poison expertise known |
-| INSPECTOR-PRESENT | BOOLEAN | FALSE | Set TRUE when Inspector arrives |
-
-### Evidence Found
-
-| Variable | Type | Initial | Description |
-|----------|------|---------|-------------|
-| DEAD-LETTER-FOUND | BOOLEAN | FALSE | Key evidence #1 |
-| KNIFE-FOUND | BOOLEAN | FALSE | Key evidence #2 |
-| LOCKED-BOX-OPENED | BOOLEAN | FALSE | Key evidence #3 (contains BANK-STATEMENT) |
-| POISON-BOTTLE-FOUND | BOOLEAN | FALSE | Key evidence #4 |
-| SECRET-LEDGER-FOUND | BOOLEAN | FALSE | Key evidence #5 |
-
-### Puzzle States
-
-| Variable | Type | Initial | Description |
-|----------|------|---------|-------------|
-| CIPHER-SOLVED | BOOLEAN | FALSE | Set TRUE when bookshelf cipher solved |
-| POISON-IDENTIFIED | BOOLEAN | FALSE | Set TRUE when poison type known |
-| ANTIDOTE-FOUND | BOOLEAN | FALSE | Set TRUE when antidote ingredients found |
-| KILLER-ACCUSED | BOOLEAN | FALSE | Set TRUE when accusation made |
-| CORRECT-ACCUSATION | BOOLEAN | FALSE | Set TRUE if accusation is correct |
-
-### Timer/Counter States
-
-| Variable | Type | Initial | Description |
-|----------|------|---------|-------------|
-| ROOMS-VISITED | COUNTER | 0 | Number of unique rooms visited |
-| ITEMS-TAKEN | COUNTER | 0 | Number of items taken |
-| WRONG-ATTEMPTS | COUNTER | 0 | Number of failed puzzle attempts |
-| HINT-LEVEL | COUNTER | 0 | Current hint level (0-4) |
-
-## State Transitions
-
-### Study Entry
-```
-STUDY-UNLOCKED = FALSE → STUDY-UNLOCKED = TRUE
-  Triggers: USE KEY ON DOOR or USE LOCKPICK ON WINDOW
-  Effects: Can now enter STUDY from ENTRANCE-HALL
-```
+# The Limehouse Killings - Story State Contract
 
-### Library Cipher
-```
-CIPHER-SOLVED = FALSE → CIPHER-SOLVED = TRUE
-  Triggers: Push books in correct rainbow order
-  Effects: SECRET-PASSAGE-FOUND = TRUE, SECRET-PASSAGE-OPEN = TRUE
-  Can now: ENTER SECRET-PASSAGE from LIBRARY
-```
+This file documents the implemented state machine and the transitions future `.zil` refactors must preserve.
 
-### Evidence Collection
-```
-EVIDENCE-FOUND = N → EVIDENCE-FOUND = N+1
-  Triggers: TAKE specific evidence item
-  Effects: Corresponding *-FOUND = TRUE
-  When EVIDENCE-FOUND = 5: INSPECTOR-PRESENT = TRUE (after delay)
-```
+## Act State
 
-### NPC Interview
-```
-SUSPECTS-INTERVIEWED = N → SUSPECTS-INTERVIEWED = N+1
-  Triggers: Complete conversation with NPC
-  Effects: Corresponding *-INTERVIEWED = TRUE
-  When SUSPECTS-INTERVIEWED = 3: Can make accusation
-```
+| Variable | Initial | Meaning |
+|---|---:|---|
+| `CASE-ACT` | 1 | 1 = exploration, 2 = reconstruction, 3 = confrontation |
+| `INSPECTOR-PRESENT` | false | Lestrade has moved into the Entrance Hall |
 
-### Final Confrontation
-```
-KILLER-ACCUSED = FALSE → KILLER-ACCUSED = TRUE
-  Triggers: ACCUSE [SUSPECT] with all evidence
-  Effects: 
-    If CORRECT-ACCUSATION = TRUE: GAME-WON = TRUE
-    If CORRECT-ACCUSATION = FALSE: GAME-LOST = TRUE
-  GAME-ENDED = TRUE
-```
+Transitions:
 
-## Milestone Flags
-
-### Early Game
-- [ ] Arrived at ASHWORTH-MANOR-GATE
-- [ ] Entered ASHWORTH-ENTRANCE-HALL
-- [ ] Met MR-HUDSON
-- [ ] Received KEY from MR-HUDSON
-
-### Mid Game
-- [ ] Entered STUDY
-- [ ] Found DEAD-LETTER
-- [ ] Found POISON-BOTTLE
-- [ ] Solved LIBRARY CIPHER
-- [ ] Found SECRET-PASSAGE
-- [ ] Interviewed LADY-ASHWORTH
-- [ ] Interviewed DR-MORIARTY
-
-### Late Game
-- [ ] Found BLOOD-STAINED-KNIFE
-- [ ] Found LOCKED-BOX
-- [ ] Found SECRET-LEDGER
-- [ ] Identified POISON
-- [ ] Found ANTIDOTE
-- [ ] Gathered all 5 evidence items
-- [ ] INSPECTOR-PRESENT = TRUE
-
-### End Game
-- [ ] Accused killer
-- [ ] Presented evidence to Inspector
-- [ ] GAME-WON = TRUE or GAME-LOST = TRUE
-
-## Consequence Mapping
-
-### Wrong Accusation
-```
-ACCUSE LADY-ASHWORTH
-  Result: "Lady Ashworth has an alibi. The evidence doesn't match."
-  Effect: WRONG-ATTEMPTS += 1
-  Can retry: YES
-
-ACCUSE MR-HUDSON
-  Result: "Mr. Hudson was in servants' quarters. The knife isn't his."
-  Effect: WRONG-ATTEMPTS += 1
-  Can retry: YES
-
-ACCUSE DR-MORIARTY (with all evidence)
-  Result: "Dr. Moriarty, you are under arrest for the murder of Lord Ashworth."
-  Effect: GAME-WON = TRUE
-```
+```text
+CASE-ACT 1
+  -- solve library cipher --> CASE-ACT 2
 
-### Dangerous Actions
-```
-TASTE POISON
-  Result: "You feel dizzy. Perhaps that wasn't wise."
-  Effect: PLAYER-HEALTH -= 1
-  Can continue: YES (if health > 0)
-
-CONFRONT KILLER UNARMED
-  Result: "The killer attacks you. Everything goes dark."
-  Effect: GAME-LOST = TRUE
-  Can continue: NO
+CASE-ACT 2
+  -- EVIDENCE-FOUND > 2 and SUSPECTS-INTERVIEWED = 3 --> CASE-ACT 3
+                                                           INSPECTOR-PRESENT = true
+                                                           MOVE INSPECTOR to hall
 ```
 
-### Missed Evidence
-```
-END GAME WITH EVIDENCE-FOUND < 5
-  Result: "The case goes cold. Insufficient evidence."
-  Effect: GAME-LOST = TRUE
-  Can continue: NO
-```
+Act transitions are monotonic and must alter visible world text in at least two places.
 
-## Save/Restore Points
+## Investigation State
 
-The game does not implement save/restore. All state is held in memory during play.
+| Variable | Initial | Guarded trigger |
+|---|---:|---|
+| `EVIDENCE-FOUND` | 0 | Increment once per counted discovery flag |
+| `SUSPECTS-INTERVIEWED` | 0 | Increment once for Hudson alibi, Lady alibi, and Moriarty poison interview |
+| `DEAD-LETTER-FOUND` | false | First meaningful read/examine/discovery of letter |
+| `KNIFE-FOUND` | false | First take/examine discovery of knife |
+| `POISON-BOTTLE-FOUND` | false | First meaningful read/examine of vial |
+| `SECRET-LEDGER-FOUND` | false | First meaningful read/examine of ledger |
+| `BANK-STATEMENT-FOUND` | false | First meaningful read/examine of statement |
 
-## Testing State Assertions
+The physical box is not itself counted evidence. Its statement is the corroborating discovery.
 
-### Golden Path Assertions
-```
-ASSERT STUDY-UNLOCKED = TRUE
-ASSERT CIPHER-SOLVED = TRUE
-ASSERT EVIDENCE-FOUND = 5
-ASSERT SUSPECTS-INTERVIEWED = 3
-ASSERT GAME-WON = TRUE
-```
+## Route and Puzzle State
 
-### Failure Path Assertions
-```
-ASSERT GAME-LOST = TRUE (wrong accusation)
-ASSERT GAME-LOST = TRUE (death)
-ASSERT EVIDENCE-FOUND < 5 (missed evidence)
+| Variable/object state | Initial | Transition |
+|---|---:|---|
+| `STUDY-UNLOCKED` | false | Interior bolt, keyring, or lockpick unlocks door |
+| `STUDY-DOOR OPENBIT` | clear | `OPEN STUDY DOOR` after unlock, or opening from Study |
+| `CIPHER-STAGE` | 0 | Correct book advances 0→1→2→3; wrong book resets |
+| `CIPHER-SOLVED` | false | Blue book after red-yellow-green sequence |
+| `SECRET-PASSAGE-FOUND` | false | Set with cipher success |
+| `SECRET-PASSAGE-OPEN` | false | Set with cipher success |
+| `POISON-IDENTIFIED` | false | `USE VIAL ON PLANTS` in Greenhouse |
+| `BOX-CLUE-SEEN` | false | Examine name-dial box |
+| `FOOTPRINT-DETAIL-FOUND` | false | Use magnifying glass on footprint cast |
+| `CABINET-CLUE-SEEN` | false | Examine/open wine cabinet |
+| `LOCKED-BOX-OPENED` | false | Turn dial to Moriarty after three prerequisite facts |
+| `LOCKED-BOX OPENBIT` | clear | Set with successful dial solution |
+
+## NPC State Matrices
+
+Each principal NPC must expose three discoverable behavior states: initial, changed by direct player action, and changed by story progress elsewhere.
+
+### Hudson
+
+| State | Trigger | Observable behavior |
+|---|---|---|
+| Initial | Act I/II, not confronted | Re-polishes one spoon; cloth squeaks as his hand tightens |
+| Confronted | Show dead letter before Act III | Stops polishing and admits carrying the letter to the study |
+| Late case | `CASE-ACT = 3` | Packed carpetbag and wrongly buttoned coat reveal fear/relief |
+
+Flags: `HUDSON-INTERVIEWED`, `HUDSON-KEY-GIVEN`, `HUDSON-CONFRONTED`.
+
+### Lady Ashworth
+
+| State | Trigger | Observable behavior |
+|---|---|---|
+| Initial | Act I/II, not confronted | Untouched filmed soup and precisely aligned knife |
+| Confronted | Show dead letter before Act III | Ring/paper tremor; admits burning an earlier draft |
+| Late case | `CASE-ACT = 3` | Removes mourning ribbon and listens for Lestrade |
+
+Flags: `LADY-INTERVIEWED`, `LADY-ALIBI-CLAIMED`, `LADY-CONFRONTED`.
+
+### Moriarty
+
+| State | Trigger | Observable behavior |
+|---|---|---|
+| Initial | Act I/II, not confronted | Controlled four-beat tapping by scientific folios |
+| Confronted | Show letter or ask about poison before Act III | Sweat, pocketed gloved hand, counting exits |
+| Late case | `CASE-ACT = 3` | Moves to hall; muddy heel matches footprint cast |
+
+Flags: `MORIARTY-INTERVIEWED`, `MORIARTY-POISON-KNOWN`, `MORIARTY-CONFRONTED`.
+
+### Lestrade
+
+| State | Trigger | Observable behavior |
+|---|---|---|
+| Offstage | Acts I–II | Cannot be examined or addressed |
+| Receiving case | Act III | Blank notebook page; asks for threat/method/motive |
+| Case complete | Three presentation flags | Notebook explicitly labels the three links |
+
+## Final Argument State
+
+| Variable | Trigger | Meaning |
+|---|---|---|
+| `LETTER-PRESENTED` | Show letter to Lestrade | Threat/intent link accepted |
+| `POISON-PRESENTED` | Show bottle to Lestrade | Method/access link accepted |
+| `MOTIVE-PRESENTED` | Show statement to Lestrade | Debt/blackmail link accepted |
+| `KILLER-ACCUSED` | Successful chosen-proof accusation | Accusation made |
+| `CORRECT-ACCUSATION` | Moriarty + complete chain + valid lead proof | Correct culprit established |
+| `GAME-WON` | Successful ending | Win state |
+| `GAME-ENDED` | Successful ending or lethal poison outcome | Session terminates |
+
+Final choice:
+
+```text
+complete case + ACCUSE MORIARTY
+  -> prompt for lead proof
+     -> WITH LETTER: testimony-led resolution
+     -> WITH POISON: physical-evidence/confession resolution
+```
+
+Both branches converge on arrest but contain distinct player-authored emphasis.
+
+## Safety and Counter Invariants
+
+- Repeating `READ`, `EXAMINE`, or `TAKE` never increments a discovery twice.
+- Asking one NPC about Moriarty never marks Moriarty himself interviewed.
+- Topicless `ASK/TELL` checks `PRSI` before `IN?` or `EQUAL?`.
+- Inspector arrival can fire only once.
+- Cipher and box solutions remain solved after revisit/save replay.
+- Wrong accusations increase `WRONG-ATTEMPTS` where supported but do not force a loss.
+- `TASTE POISON` decrements `PLAYER-HEALTH`; only zero health ends the game.
+- `USE CHARCOAL` after tasting poison restores one health point and never exceeds the initial value.
+
+## Golden-Path Assertions
+
+```text
+CASE-ACT = 2 after cipher
+CIPHER-SOLVED = true
+SECRET-PASSAGE-OPEN = true
+POISON-IDENTIFIED = true
+LOCKED-BOX-OPENED = true
+EVIDENCE-FOUND = 5
+SUSPECTS-INTERVIEWED = 3
+CASE-ACT = 3
+INSPECTOR-PRESENT = true
+LETTER-PRESENTED = true
+POISON-PRESENTED = true
+MOTIVE-PRESENTED = true
+KILLER-ACCUSED = true
+CORRECT-ACCUSATION = true
+GAME-WON = true
 ```
+
+## Save/Replay Requirement
+
+`llm.lua` persists state by replaying action history across processes. Every transition above must therefore be deterministic under a fresh load plus replay, including runtime vocabulary registration for `SET`, `CAST`, and `INSPECTOR`.
diff --git a/books/limehouse-killings/work/TRANSCRIPT_TESTS.md b/books/limehouse-killings/work/TRANSCRIPT_TESTS.md
index 1ae1bde..332e637 100644
--- a/books/limehouse-killings/work/TRANSCRIPT_TESTS.md
+++ b/books/limehouse-killings/work/TRANSCRIPT_TESTS.md
@@ -1,420 +1,316 @@
-# The Limehouse Killings - Transcript Tests
+# The Limehouse Killings - Canonical Transcript Plan
 
-## Golden Path Transcript
+Literal parser coverage lives in `tests/test_limehouse_walkthrough.lua`. This document records the human-readable intent of those commands and is the source for future `.zil` refactor transcripts.
 
-### Test 1: Full Investigation and Correct Accusation
+## Golden Path
 
-```
-> GO TO ASHWORTH-MANOR-GATE
-You stand before the iron gates of Ashworth Manor. The gravel path leads north to the entrance. Fog swirls around your feet.
-
-> SOUTH
-You pass through the gates and approach the manor. The front door is slightly ajar.
-
-> ENTER
-You step into the entrance hall. A grand chandelier hangs from the ceiling, its crystals dull with dust. Portraits line the walls. A Persian rug covers the floor.
-
-> LOOK
-Entrance Hall
-A grand foyer with cracked chandelier and dusty portraits. A Persian rug covers the floor. Exits: NORTH (to gate), SOUTH (to study), EAST (to library), WEST (to dining room), DOWN (to kitchen).
-
-> EXAMINE RUG
-A fine Persian rug, now faded and worn. Something dark stains the corner near the south door.
-
-> SOUTH
-The door to the study is locked. You'll need a key or tool to enter.
-
-> EAST
-Library
-Floor-to-ceiling bookshelves line the walls. A reading desk stands near the fireplace. Colored markers dot the shelves. Exits: WEST (to entrance hall).
-
-> EXAMINE BOOKSHELF
-The bookshelf is arranged by color. Red, blue, green, and yellow markers are visible on different shelves. Some books have colored spines.
-
-> EXAMINE READING-DESK
-A reading desk with a torn page lying on it.
-
-> TAKE TORN-PAGE
-You take the torn page.
-
-> READ TORN-PAGE
-The page reads: "Follow the rainbow order. Red, orange, yellow, green, blue, violet. Only then will the way open."
-
-> EXAMINE COLORED-MARKERS
-The markers are: RED on shelf 1, BLUE on shelf 3, GREEN on shelf 4, YELLOW on shelf 2.
-
-> PUSH RED BOOK
-You push a book with a red spine on shelf 1. It clicks into place.
-
-> PUSH BLUE BOOK
-You push a book with a blue spine on shelf 3. It clicks into place.
-
-> PUSH GREEN BOOK
-You push a book with a green spine on shelf 4. It clicks into place.
-
-> PUSH YELLOW BOOK
-You push a book with a yellow spine on shelf 2. It clicks into place.
-
-A section of the bookshelf slides open, revealing a narrow stone passage.
-
-> ENTER SECRET-PASSAGE
-You step into the secret passage. Dust and cobwebs fill the air. The passage leads west to the library and east to the study.
-
-> EAST
-Study
-The study is a crime scene. A body outline marks the floor near the desk. A mahogany desk stands against the wall. A fireplace contains a locked box. A window looks out to the garden. Exits: NORTH (to entrance hall).
-
-> EXAMINE BODY-OUTLINE
-A chalk outline marks where the body was found. The victim was struck from behind, then poisoned.
-
-> EXAMINE DESK
-The mahogany desk has three drawers. An unsent letter and a poison bottle lie on top.
-
-> TAKE DEAD-LETTER
-You take the unsent letter.
-
-> READ DEAD-LETTER
-The letter reads: "My dear Dr. Moriarty, I know what you did. If you do not confess by Friday, I will expose you to Scotland Yard. - Lord Ashworth"
+### Opening and blocker
 
-> TAKE POISON-BOTTLE
-You take the poison bottle.
-
-> EXAMINE POISON-BOTTLE
-The bottle is labeled: "Aconitum - Wolfsbane. Highly poisonous."
-
-> EXAMINE FIREPLACE
-The fireplace contains cold ashes and a locked box.
-
-> EXAMINE LOCKED-BOX
-The locked box is small and ornate. It has a keyhole.
-
-> EXAMINE WINDOW
-The window is old, with a rusty latch. It looks out to the garden.
-
-> NORTH
-Entrance Hall
-
-> WEST
-Dining Room
-A long dining table dominates the room. A wine cabinet stands against the wall. Portraits of the family hang above. Exits: EAST (to entrance hall), NORTH (to pantry).
-
-> EXAMINE TABLE
-The dining table is set for two, but only one place was used. A wax seal lies near the empty plate.
-
-> TAKE WAX-SEAL
-You take the wax seal.
-
-> EXAMINE WAX-SEAL
-The wax seal bears the initial "M" - Moriarty.
-
-> EXAMINE WINE-CABINET
-The wine cabinet is locked. It contains fine wines and spirits.
-
-> NORTH
-Pantry
-A small pantry with shelves of food and wine. Exits: SOUTH (to dining room).
-
-> EXAMINE SHELVES
-The shelves hold canned goods, spices, and a bottle of antidote ingredients.
-
-> TAKE FOXGLOVE
-You take the foxglove.
-
-> TAKE CHARCOAL
-You take the charcoal.
-
-> SOUTH
-Dining Room
-
-> EAST
-Entrance Hall
-
-> DOWN
-Kitchen
-A kitchen with copper pots, a cold hearth, and a servant bell. A drawer in the counter is slightly open. Exits: UP (to entrance hall), WEST (to garden).
+```text
+READ TELEGRAM
+GO NORTH
+GO SOUTH
+OPEN STUDY DOOR
+```
 
-> EXAMINE POTS
-Copper pots hang from the ceiling, tarnished with age.
+Expected signals:
+
+- Telegram is visible at game start and rewards immediate interaction.
+- Entrance Hall is north of the gate.
+- South movement is blocked while the study door is closed.
+- Opening the locked door suggests key/lockpick without claiming they are the only route.
+- `EXAMINE INSPECTOR` here reports that no inspector is present.
+
+### Act I threshold: library sequence
+
+```text
+GO EAST
+EXAMINE READING DESK
+TAKE TORN PAGE
+READ TORN PAGE
+EXAMINE COLORED MARKERS
+PUSH RED BOOK
+PUSH YELLOW BOOK
+PUSH GREEN BOOK
+PUSH BLUE BOOK
+```
 
-> EXAMINE HEARTH
-The hearth is cold, with ashes from yesterday's fire.
+Expected signals:
 
-> OPEN DRAWER
-You open the drawer. Inside is a lockpick set.
+- Each correct push clicks.
+- Blue completes the sequence and opens the concealed wall.
+- `CASE-ACT` becomes 2.
+- Library exposes a passage route and Entrance Hall gains bell-wire aftermath.
 
-> TAKE LOCKPICK-SET
-You take the lockpick set.
+### Locked-room reconstruction
 
-> EXAMINE BELL
-A servant bell hangs from the wall. A rope leads up to the servant's quarters.
+```text
+GO SOUTH
+GO EAST
+EXAMINE CHALK OUTLINE
+EXAMINE DESK
+TAKE DEAD LETTER
+READ DEAD LETTER
+TAKE POISON BOTTLE
+EXAMINE POISON BOTTLE
+OPEN STUDY DOOR
+```
 
-> PULL BELL
-You pull the bell rope. A distant bell rings upstairs.
+Expected signals:
 
-> WEST
-Garden
-An overgrown garden with a fountain at the center. Hedge mazes line the paths. A blood-stained knife lies in the hedge near the fountain. Exits: EAST (to kitchen), NORTH (to greenhouse), SOUTH (to servants' quarters).
+- Passage leads into Study without key or lockpick.
+- Letter records threat once; vial records method clue once.
+- Opening door from inside releases the interior bolt and opens the physical door.
 
-> EXAMINE FOUNTAIN
-The fountain is dry, with coins at the bottom. A footprint cast lies nearby.
+### Environmental evidence and optional tools
 
-> TAKE FOOTPRINT-CAST
-You take the footprint cast.
+```text
+GO NORTH
+GO WEST
+EXAMINE TABLE
+TAKE WAX SEAL
+GO NORTH
+EXAMINE SHELVES
+TAKE FOXGLOVE
+TAKE CHARCOAL
+GO SOUTH
+GO EAST
+GO DOWN
+EXAMINE DRAWER
+OPEN DRAWER
+EXAMINE DRAWER
+EXAMINE LEATHER ROLL
+OPEN LEATHER ROLL
+TAKE LOCKPICK SET
+GO WEST
+EXAMINE HEDGES
+TAKE BLOOD-STAINED KNIFE
+TAKE FOOTPRINT CAST
+```
 
-> EXAMINE FOOTPRINT-CAST
-The cast shows a boot print size 10 - too large for Lady Ashworth.
+Expected signals:
 
-> EXAMINE HEDGE
-The hedge is thick and overgrown. Something glints in the branches.
+- Container state is physical and persistent.
+- Spaced compound nouns parse.
+- Knife increments evidence once; footprint is corroboration rather than a required counter item.
+- Foxglove, charcoal, and lockpick remain optional; they do not solve the central deductions.
 
-> TAKE BLOOD-STAINED-KNIFE
-You take the blood-stained knife.
+### Poison comparison
 
-> EXAMINE BLOOD-STAINED-KNIFE
-The knife is stained with dried blood. It matches the surgical tools in Dr. Moriarty's office.
+```text
+GO NORTH
+EXAMINE PLANTS
+EXAMINE LABELS
+USE VIAL ON PLANTS
+```
 
-> NORTH
-Greenhouse
-A glass greenhouse with exotic plants. Labels mark the pots. A potting bench stands near the door. Exits: SOUTH (to garden).
+Expected signal: `POISON-IDENTIFIED` becomes true and output explicitly matches Aconitum/wolfsbane between vial and greenhouse.
 
-> EXAMINE PLANTS
-Exotic plants fill the greenhouse. One plant has distinctive purple flowers - wolfsbane.
+### Interviews and visible behavior
 
-> EXAMINE LABELS
-The labels read: "Aconitum - Wolfsbane" on the purple plant. "Digitalis - Foxglove" on another.
+```text
+GO SOUTH
+GO SOUTH
+ASK HUDSON
+ASK HUDSON ABOUT MASTER
+ASK HUDSON ABOUT ALIBI
+ASK HUDSON ABOUT KEY
+ASK HUDSON ABOUT MORIARTY
 
-> MATCH POISON-BOTTLE TO LABEL
-You match the poison bottle label to the wolfsbane plant. The poison came from this greenhouse.
+GO NORTH
+GO EAST
+GO UP
+GO WEST
+ASK LADY
+ASK LADY ABOUT MARRIAGE
+ASK LADY ABOUT ALIBI
 
-> SOUTH
-Garden
+GO EAST
+GO EAST
+ASK MORIARTY
+ASK MORIARTY ABOUT EXPERIMENTS
+ASK MORIARTY ABOUT POISON
+```
 
-> SOUTH
-Servants' Quarters
-Sparse rooms with servant beds and a trunk. Mr. Hudson, the butler, is here. Exits: NORTH (to garden).
+Expected signals:
 
-> EXAMINE BEDS
-Simple beds for the household staff. They are empty.
+- Each topicless `ASK` asks what topic the player intends and never crashes.
+- Only each suspect's designated interview topic increments `SUSPECTS-INTERVIEWED`.
+- Moriarty admits poison access, changes behavior, and moves toward the hall.
+- With at least three discoveries and all interviews, `CASE-ACT` becomes 3 and Lestrade arrives.
 
-> EXAMINE TRUNK
-A large trunk contains servant uniforms and a letter.
+Intermediate-state coverage:
 
-> TAKE LETTER
-You take the letter.
+```text
+SHOW LETTER TO HUDSON
+SHOW LETTER TO LADY
+SHOW LETTER TO MORIARTY
+EXAMINE <NPC>
+```
 
-> READ LETTER
-The letter is from Dr. Moriarty to Mr. Hudson: "Keep your mouth shut about the poison, or you'll join your master."
+Run each on a branch before Act III and assert the player-changed description/dialogue.
 
-> ASK HUDSON ABOUT MASTER
-"Lord Ashworth was a difficult man. He fired me last week."
+The automated golden path also magnifies the footprint cast, checks the wine-cabinet delivery clue, tastes and recovers from the vial with charcoal, and shows the detailed cast to Lestrade.
 
-> ASK HUDSON ABOUT ALIBI
-"I was here in the servants' quarters all evening. You can check with the other servants."
+### Name-dial deduction
 
-> ASK HUDSON ABOUT KEY
-"I suppose you'll need this." He hands you a key. "The study key. I kept it for safekeeping."
+```text
+TAKE SECRET LEDGER
+READ SECRET LEDGER
+GO WEST
+GO SOUTH
+GO EAST
+EXAMINE LOCKED BOX
+TURN LOCKED BOX TO MORIARTY
+TAKE BANK STATEMENT
+READ BANK STATEMENT
+```
 
-> TAKE KEY
-You take the key.
+Expected signals:
+
+- Box examine states that there is no keyhole and names three engravings.
+- Keyring/lockpick are irrelevant to this box.
+- Successful dial output explicitly connects letter, flower, and debt.
+- Statement becomes reachable only after `OPENBIT` is set.
+- Score reaches five counted discoveries.
+
+### Case assembly and chosen-proof ending
+
+```text
+GO NORTH
+ASK INSPECTOR
+ASK INSPECTOR ABOUT CASE
+SHOW LETTER TO INSPECTOR
+SHOW BOTTLE TO INSPECTOR
+SHOW STATEMENT TO INSPECTOR
+ACCUSE MORIARTY
+ACCUSE MORIARTY WITH LETTER
+```
 
-> ASK HUDSON ABOUT MORIARTY
-"Dr. Moriarty? He visited often. He and the master had... disagreements."
+Expected signals:
 
-> NORTH
-Garden
+- Topicless Inspector conversation is safe.
+- Lestrade describes threat, method, and motive rather than “five items.”
+- Each accepted link changes a specific presentation flag.
+- Bare accusation asks the player to choose letter or poison.
+- Letter-led ending references witness confirmation, greenhouse/vial, ledger/statement/name dial, footprint/knife, dawn, tea, and a future case.
 
-> EAST
-Kitchen
+Alternate ending branch:
 
-> UP
-Entrance Hall
+```text
+ACCUSE MORIARTY WITH POISON
+```
 
-> SOUTH
-Study
-You unlock the door with the key. The study is a crime scene.
+Expected difference: Moriarty exposes guilty specialized knowledge of the vial before the common arrest/consequence sequence.
 
-> EXAMINE DESK (again)
-The desk drawers are empty except for one. You find a secret ledger.
+## Required Failure and Recovery Transcripts
 
-> TAKE SECRET-LEDGER
-You take the secret ledger.
+### Topicless conversation
 
-> READ SECRET-LEDGER
-The ledger shows Dr. Moriarty owed Lord Ashworth £500. The debt was due this week.
+Run against Hudson, Lady Ashworth, Moriarty, and Lestrade when present:
 
-> USE LOCKPICK ON LOCKED-BOX
-You use the lockpick set on the locked box. It clicks open.
+```text
+ASK <NPC>
+TELL <NPC>
+```
 
-> TAKE BANK-STATEMENT
-You take the bank statement.
+Expected: prompt for a topic; no runtime error, nil text, or generic manual response.
 
-> READ BANK-STATEMENT
-The statement shows Dr. Moriarty's account is overdrawn. He recently withdrew a large sum for "experimental supplies."
+### Compound nouns
 
-> LOOK
-You have gathered all the evidence:
-1. Dead letter threatening Dr. Moriarty
-2. Blood-stained knife matching Moriarty's tools
-3. Bank statement showing Moriarty's debt
-4. Poison bottle from Moriarty's greenhouse
-5. Secret ledger showing financial motive
+```text
+TAKE LOCKPICK SET
+TAKE FOOTPRINT CAST
+```
 
-> GO TO ENTRANCE-HALL
-You return to the entrance hall. Inspector Lestrade has arrived.
+Expected: both resolve despite `SET` and `CAST` having verb senses.
 
-> ASK INSPECTOR ABOUT CASE
-"Ah, the detective. What have you found?"
+### Inspector timing
 
-> ACCUSE DR-MORIARTY
-"Dr. Moriarty, you are under arrest for the murder of Lord Ashworth."
+```text
+[Act I] EXAMINE INSPECTOR
+```
 
-> SHOW DEAD-LETTER TO INSPECTOR
-The inspector reads the letter. "This is damning evidence."
+Expected: not in scope.
 
-> SHOW BLOOD-STAINED-KNIFE TO INSPECTOR
-"The knife matches the wound. And it's from Moriarty's collection."
+After Act III threshold:
 
-> SHOW BANK-STATEMENT TO INSPECTOR
-"Moriarty owed the victim money. Motive established."
+```text
+LOOK
+EXAMINE INSPECTOR
+ASK INSPECTOR ABOUT CASE
+```
 
-> SHOW POISON-BOTTLE TO INSPECTOR
-"Wolfsbane. Rare poison. Only Moriarty had access."
+Expected: room lists Lestrade, examine works, case topic works.
 
-> SHOW SECRET-LEDGER TO INSPECTOR
-"And the ledger shows he was being blackmailed. Case closed."
+### Cipher recovery
 
-> GAME OVER
-Congratulations! You have solved the murder of Lord Ashworth.
-Dr. Moriarty has been arrested for the crime.
-Your reputation as a detective is secured.
+```text
+PUSH RED BOOK
+PUSH BLUE BOOK
 ```
 
-## Failure Path Transcripts
+Expected: reset, then the complete correct sequence remains available.
 
-### Test 2: Wrong Accusation
+### Name dial recovery
 
+```text
+OPEN LOCKED BOX
+TURN LOCKED BOX TO HUDSON
+TURN LOCKED BOX TO MORIARTY    [before prerequisites]
 ```
-> [After gathering evidence]
-> ACCUSE LADY-ASHWORTH
-"Lady Ashworth has an alibi. The evidence doesn't match. Try again."
-
-> ACCUSE MR-HUDSON
-"Mr. Hudson was in servants' quarters. The knife isn't his. Try again."
 
-> ACCUSE DR-MORIARTY
-"Dr. Moriarty, you are under arrest for the murder of Lord Ashworth."
-[Game continues with evidence presentation]
-```
+Expected: teach dial syntax; reject wrong name; identify unresolved clue categories. None consumes evidence or blocks retry.
 
-### Test 3: Missing Evidence
+### Early/weak accusation
 
-```
-> [Without all 5 evidence items]
-> ACCUSE DR-MORIARTY
-"You don't have enough evidence. Gather more clues before making an accusation."
+```text
+ACCUSE MORIARTY                [before Lestrade]
+ACCUSE MORIARTY                [before presentations]
+ACCUSE MORIARTY WITH KNIFE     [after presentations]
 ```
 
-### Test 4: Dangerous Action
+Expected: absent-authority response; missing-chain response; irrelevant-lead-proof response. All allow recovery.
 
-```
-> TASTE POISON
-You feel dizzy. Perhaps that wasn't wise.
-[Health reduced]
+### Dangerous action
 
-> TASTE POISON (again)
-You collapse. Everything goes dark.
-GAME OVER - You have died.
+```text
+TASTE VIAL
 ```
 
-### Test 5: Wrong Cipher Order
+Expected: clear warning/consequence, `PLAYER-HEALTH` decremented, game continues until health reaches zero.
 
-```
-> PUSH BLUE BOOK
-Nothing happens. Perhaps there's an order to follow.
-
-> PUSH GREEN BOOK
-Nothing happens.
+## Room and NPC State Checks
 
-> PUSH RED BOOK
-You push a book with a red spine. It clicks into place.
-```
+| Milestone | Revisit | Required changed observation |
+|---|---|---|
+| Cipher solved | Library | Passage visibly open |
+| Cipher solved | Entrance Hall | Bell wire quivers |
+| Act III reached | Entrance Hall | Lestrade and Moriarty visible |
+| Act III reached | Servants' Quarters | Hudson's packed bag/coat |
+| Act III reached | Dining Room | Lady's removed ribbon/listening behavior |
+| Act III reached | Moriarty examine | Muddy heel/doorward behavior |
+| Box solved | Study | Box lies open |
 
-## Room/Object Checklist Commands
+## Automation Commands
 
-### Room Visits
-```
-GO TO ASHWORTH-MANOR-GATE
-GO TO ASHWORTH-ENTRANCE-HALL
-GO TO STUDY
-GO TO LIBRARY
-GO TO DINING-ROOM
-GO TO KITCHEN
-GO TO GARDEN
-GO TO GREENHOUSE
-GO TO SERVANTS-QUARTERS
-GO TO SECRET-PASSAGE
+```text
+make test-limehouse-walkthrough
+lua5.4 scripts/check-vocab.lua books/limehouse-killings/dungeon.zil
+make test-pure-zil
 ```
 
-### Object Interactions
-```
-EXAMINE BODY-OUTLINE
-EXAMINE DESK
-EXAMINE FIREPLACE
-EXAMINE WINDOW
-EXAMINE BOOKSHELF
-EXAMINE READING-DESK
-EXAMINE TABLE
-EXAMINE WINE-CABINET
-EXAMINE POTS
-EXAMINE HEARTH
-EXAMINE FOUNTAIN
-EXAMINE HEDGE
-EXAMINE PLANTS
-EXAMINE BENCH
-EXAMINE BEDS
-EXAMINE TRUNK
-```
+Current baseline at the time of this document update: 531/531 Limehouse parser assertions passing, vocabulary audit clean, and full pure-ZIL suite passing.
 
-### Evidence Collection
-```
-TAKE DEAD-LETTER
-TAKE BLOOD-STAINED-KNIFE
-TAKE POISON-BOTTLE
-TAKE SECRET-LEDGER
-USE LOCKPICK ON LOCKED-BOX
-TAKE BANK-STATEMENT
-```
+## Documentation Drift Guard
 
-### NPC Conversations
-```
-ASK HUDSON ABOUT MASTER
-ASK HUDSON ABOUT ALIBI
-ASK HUDSON ABOUT KEY
-ASK HUDSON ABOUT MORIARTY
-ASK LADY ABOUT MARRIAGE
-ASK LADY ABOUT ALIBI
-ASK LADY ABOUT ENEMIES
-ASK MORIARTY ABOUT EXPERIMENTS
-ASK MORIARTY ABOUT POISON
-ASK MORIARTY ABOUT RELATIONSHIP
-```
+Reject future transcript edits that use:
+
+- `MATCH POISON-BOTTLE TO LABEL`
+- `FIND WOLFSBANE`
+- `USE LOCKPICK ON LOCKED-BOX`
+- accusation before evidence presentation
+- Inspector present from game start
+- “gather five held items to win”
 
-## Bug Ledger
-
-| Bug ID | Category | Description | Reproduction | Status |
-|--------|----------|-------------|--------------|--------|
-| BUG-001 | Parser | "TAKE LETTER" fails in servants' quarters | TAKE LETTER in SERVANTS-QUARTERS | Open |
-| BUG-002 | State | LOCKED-BOX can be opened without key | USE LOCKPICK ON LOCKED-BOX without finding key | Open |
-| BUG-003 | Content | INSPECTOR doesn't appear after evidence | Gather all evidence, return to entrance hall | Open |
-| BUG-004 | Parser | "ACCUSE KILLER" doesn't work | ACCUSE KILLER (without naming suspect) | Open |
-| BUG-005 | Softlock | Can enter study without evidence | Enter study via secret passage, skip evidence | Open |
-
-## Fix Changelog
-
-| Fix ID | Bug ID | Description | Files Affected | Date |
-|--------|--------|-------------|----------------|------|
-| FIX-001 | BUG-001 | Add LETTER to servants' quarters objects | dungeon.zil | - |
-| FIX-002 | BUG-002 | Require key OR lockpick for locked box | actions.zil | - |
-| FIX-003 | BUG-003 | Trigger inspector after 5 evidence | actions.zil | - |
-| FIX-004 | BUG-004 | Add "ACCUSE KILLER" parser response | actions.zil | - |
-| FIX-005 | BUG-005 | Block secret passage until study unlocked | dungeon.zil | - |
+Those phrases describe the superseded item-gate design, not the current story model.
diff --git a/books/wondertown/wondertown-premise.md b/books/wondertown/wondertown-premise.md
new file mode 100644
index 0000000..95cb29c
--- /dev/null
+++ b/books/wondertown/wondertown-premise.md
@@ -0,0 +1,64 @@
+# THE LAST TOYMAKER'S APPRENTICE
+### A Game Design Premise
+
+**Genre:** Text/parser adventure (interactive fiction), all-ages
+**Tone reference:** *Toy Story* meets *Up* meets *Planetfall* — whimsical opening, bittersweet middle, earned joy at the end
+**Structural reference:** Infocom's mature 3-act formula (as seen in *Deadline*, *Suspended*, and especially *Planetfall*), where Act 1 teaches through comedy, Act 2 raises the emotional and mechanical stakes, and Act 3 pays off everything you learned
+
+---
+
+## PREMISE
+
+You are **Pip**, a wind-up apprentice — no taller than a teacup — who works for Grandfather Tolliver, the last toymaker in the town of **Wrenfold**. Every night after the shop closes, the toys wake up. Pip's job is small and simple: oil the joints, sweep the sawdust, keep the workshop running before dawn.
+
+Tonight, Grandfather Tolliver doesn't come down to lock up. His workshop key — the only thing that keeps the shop's magic wound — has stopped ticking on its hook. Without it, the toys will fall silent by sunrise, one by one, forever.
+
+Pip has one night to find out what happened to the toymaker and rewind the town's heart before the clock runs out.
+
+---
+
+## ACT 1 — "The Nightly Rounds" (comedic, low-stakes, teaches the verbs)
+
+Structurally, this act mirrors *Zork*'s house or *Planetfall*'s Kalamontee — a contained, richly-described space where every room is a joke and a tutorial at once. The player learns to **WIND**, **OIL**, **LISTEN**, and **EXAMINE**, and meets the shop's cast:
+
+- **Bertrand**, a pompous nutcracker who insists he outranks Pip and refuses to help unless addressed "properly" (a light social puzzle — flattery as a mechanic, à la *Hitchhiker's Guide*'s Babel fish sequence).
+- **Old Tick**, a cuckoo clock who only speaks in riddles on the hour, forcing the player to manage real-time waiting the way *Deadline* forces attention to a ticking schedule.
+- **Marzipan**, a one-eyed rag doll who is secretly the smartest character in the shop and drops the real plot information, disguised as nonsense songs.
+
+By the act's end, a comic red herring (a "haunted" music box) resolves into the actual inciting incident: Grandfather Tolliver's key is missing, and muddy little footprints — not toy-sized — lead out the workshop door into the snow.
+
+---
+
+## ACT 2 — "Wrenfold By Night" (the Pixar turn: stakes, sadness, a real NPC)
+
+This is where the game earns the comparison to Infocom's *later* work rather than its earlier one — the moment the story stops being cute and starts being *about* something.
+
+Pip leaves the shop and discovers the whole town is toys — every streetlamp, mailbox, and shopfront was once a child's plaything, discarded and left to wind down slowly for decades. **Grandfather Tolliver was the last person who still repaired them.** The footprints belong to **Nutmeg**, a fox-shaped toy who has been alone in the cold so long she no longer believes she was ever loved by anyone, and who took the key out of jealousy — she wanted just one more night of being *fixed*, of mattering to somebody.
+
+Nutmeg is this game's **Floyd** — the emotionally complex companion (drawing directly on *Planetfall*'s design): she is funny, then heartbreaking, has her own agenda, can be genuinely helped or genuinely alienated depending on how the player treats her, and her arc — not the plot mechanics — is the emotional spine of the game. Critically, like Floyd, **she is not simply a walking hint dispenser**: she refuses to help at several points, tests the player's patience, and the "correct" solution to more than one puzzle is *kindness with no immediate reward*, which the game must not signal mechanically — the player has to choose it without being told it's the right choice.
+
+Puzzles in this act use Infocom's mid-game staples:
+- A **locked door only Nutmeg's small fox-shape can enter**, requiring the player to have earned her trust in Act 1's echo (a callback puzzle).
+- A **weight/inventory puzzle**: Pip can only carry a few tools across the frozen square before winding down himself, forcing hard choices about what matters.
+- A **misdirection puzzle**: the obvious villain (a scrap-metal junk-collector cart that's been "eating" broken toys all along) turns out to be trying to *save* them, salvaging parts to keep others running — recontextualizing an earlier "threat" the same way *Suspended* recontextualizes its own robots.
+
+Act 2 ends at the town's frozen fountain, where Nutmeg finally admits why she took the key, and Pip realizes: it isn't the key that's magic. It's Grandfather Tolliver's habit of noticing which toy needs fixing next. That's not a thing you can rewind. It's a thing you have to *choose to keep doing*.
+
+---
+
+## ACT 3 — "What the Clockwork Remembers" (resolution, real-time climax, earned ending)
+
+A ticking climax in the Infocom mold (*Deadline*'s countdown, *Starcross*'s escape sequence): dawn is coming in real, counted turns. The key alone can't restart the town — Pip must decide, with limited time, which toys to personally rewind by hand (echoing the weight-limit choices from Act 2), knowing not everyone can be saved before sunrise.
+
+The final puzzle isn't combat or a lock — it's a **choice with no single correct object-flag solution**, evaluated on what the player has done throughout the game: whether they were patient with Bertrand, whether they let Old Tick finish his riddles, whether they treated Nutmeg with care when it cost them nothing in-game to be cruel instead. This produces branching but thematically consistent endings — Grandfather Tolliver returns and finds a shop kept alive not by magic, but by an apprentice who learned to notice.
+
+---
+
+## DESIGN NOTES
+
+- **Complex NPC done right:** Nutmeg needs her own internal clock/schedule (like Floyd), independent of player input, so the world feels inhabited rather than staged.
+- **Puzzles as character, not just as locks:** every mechanical puzzle should double as an emotional beat, the way *Planetfall*'s survival puzzles are inseparable from Floyd's companionship.
+- **Fair-but-hard, never cruel:** in the Infocom tradition, red herrings are allowed, but no puzzle should be solvable only by trial-and-death; children need to feel clever, not punished.
+- **Feelies-equivalent:** a small paper "workshop repair manual" as physical/PDF packaging, styled like a child's picture book, seeding vocabulary and lore without in-game exposition dumps.
+
+Given your existing ZIL-to-Lua VM work, this could realistically be prototyped in ZIL directly and run through your own transpiler — which would be a fitting way to build a children's Infocom homage.
diff --git a/infocom/lurkinghorror/h1.zil b/infocom/lurkinghorror/h1.zil
index aa63641..ecaacb5 100644
--- a/infocom/lurkinghorror/h1.zil
+++ b/infocom/lurkinghorror/h1.zil
@@ -3,6 +3,7 @@
 	(c) Copyright 1986 Infocom, Inc. All Rights Reserved."
 
 <SNAME "H1">
+<SET-HEADER 15 "870918">
 
 <PRINC "
 *** The Lurking Horror: Interactive Horror ***
diff --git a/infocom/lurkinghorror/misc.zil b/infocom/lurkinghorror/misc.zil
index b66bd36..704da09 100644
--- a/infocom/lurkinghorror/misc.zil
+++ b/infocom/lurkinghorror/misc.zil
@@ -841,7 +841,7 @@ be included when the crunch comes."
 			<SETG WINNER .OWINNER>
 			<RETURN .FLG>)
 		       (<NOT <ZERO? <GET ,CLOCK-HAND ,C-RTN>>>
-			<SET TICK <GET ,CLOCK-HAND ,C-TICK>>
+			<SET TICK <SIGNED-WORD <GET ,CLOCK-HAND ,C-TICK>>>
 			<COND (<L? .TICK -1>
 			       <PUT ,CLOCK-HAND ,C-TICK <- <- .TICK> 3>>
 			       <SET Q? ,CLOCK-HAND>)
diff --git a/infocom/lurkinghorror/report.md b/infocom/lurkinghorror/report.md
new file mode 100644
index 0000000..52455b2
--- /dev/null
+++ b/infocom/lurkinghorror/report.md
@@ -0,0 +1,371 @@
+# The Lurking Horror — Playability Assessment Report
+
+**Test Date:** July 15, 2026
+**Tested By:** Game Tester Agent
+**Game Version:** Release 15 / Serial number 870918
+**Platform:** AdventureArena ZIL runtime (llm.lua)
+**Session Count:** Multiple sessions, 80+ total game turns
+**Save files:** `/tmp/lh-*.sav`
+
+---
+
+## Executive Summary
+
+| Category | Count |
+|----------|-------|
+| Critical Bugs | 1 |
+| High Severity | 1 |
+| Medium Severity | 3 |
+| Low Severity | 0 |
+| **Fixes Confirmed Since Previous Report** | **13 of 16 previous bugs resolved** |
+| **New Bugs Found** | **2** |
+| **Overall Verdict** | **Largely playable** — The game engine has made enormous progress. All previous crash/hang/parser-blocking bugs are fixed. Full login sequence works. Movement works in all directions including `w`/`west`. NPC interaction is robust. Basic object manipulation works. Two issues remain: inventory display is blank (`i` shows empty-handed), and the dream sequence creature daemon doesn't fire (soft-lock in dream). |
+
+---
+
+## What's Fixed Since the Previous Report
+
+### Round 1 Bugs (from initial report):
+| # | Bug | Previous Status | Current Status | Evidence |
+|---|---|-----------------|----------------|----------|
+| 1 | CLOCKER crash after ~8 turns | Critical | ✅ **FIXED** | Played 50+ turns across multiple sessions; no crash |
+| 2 | PUTP crash when moving south | Critical | ✅ **FIXED** | `south` works reliably from all locations |
+| 3 | "examine outlet" memory dump | Critical | ✅ **FIXED** | `examine call button` works correctly (same class); no memory dump |
+| 4 | Nil in screen display | High | ✅ **FIXED** | Screen display shows correctly with no "nil" strings |
+| 5 | Save/restore state corruption | Game-blocking | ✅ **FIXED** | Most objects and state persist correctly. Hacker interaction works across save/restore |
+| 6 | Number token parsing failure | Game-blocking | ✅ **FIXED** | `type 872325412` accepted, login sequence works |
+| 7 | NPC dialogue output not captured | High | ✅ **FIXED** | `ask hacker about master` → `"Who said anything about any master keys?"` Works correctly |
+| 8 | Verb coverage gaps (west/w misparsed) | Medium | ✅ **FIXED** | `west` and `w` now work correctly as movement commands |
+| 9 | "You already are" for examine chair | Medium | ✅ **FIXED** | `examine chair` shows `It's a molded plastic chair...` |
+| 10 | Missing serial number | Low | ✅ **FIXED** | Serial number now shows `870918` |
+| 11 | Blank output for score/time | Low | ✅ **FIXED** | `score` → "Your score is 0 of a possible 100, in X moves." `time` → "It seems like three o'clock..." |
+| 12 | Missing sound support | Low | ✅ **SAFE NO-OP** | Sound handling is a safe no-op |
+
+### Round 2 Bugs (from previous playability report):
+| # | Bug | Previous Status | Current Status | Evidence |
+|---|---|-----------------|----------------|----------|
+| C1 | `look` hangs on 2nd/3rd floor | Critical | ✅ **FIXED** | `look` works on Second Floor, Third Floor, Kitchen, Computer Center, Roof, and all other rooms |
+| C2 | `examine call button` memory dump | Critical | ✅ **FIXED** | `examine call button` → "Which call button do you mean, the up-arrow or the down-arrow?" |
+| H1 | `west`/`w` misparsed as `tell` | High | ✅ **FIXED** | `west` from Second Floor → Kitchen. `w` from Second Floor → Kitchen |
+| H2 | Dream "It sounds like supplication" | High | ✅ **FIXED** | `examine stone` in dream → `It's a smooth, shiny piece of what might be obsidian...` (P? macro fix works) |
+| H3 | "You can't see any hacker here" | High | ✅ **FIXED** | `ask hacker about master` returns dialogue. `ask hacker about pc` returns documentation advice. Hacker stays visible across commands |
+| H4 | `talk to hacker` not recognized | High | ✅ **FIXED** | `talk to hacker` → "Hmmm ... the hacker waits for you to say something." |
+| M1 | `x` abbreviation not recognized | Medium | ❌ **STILL BROKEN** | `x pc` → "I don't know the word 'x.'" |
+| M2 | `inventory` not recognized | Medium | ❌ **STILL BROKEN** | `inventory` → "I don't know the word 'inventory.'" |
+| M3 | QUIT prompt blocks further commands | Medium | ⚠️ **PARTIALLY FIXED** | QUIT now shows the prompt correctly (was impossible before), but Y/N response handling is incomplete |
+| M5 | `help` returns "Those things aren't here!" | Low | ✅ **FIXED** | `help` → "Well, nothing happens. Perhaps you should turn on the computer?" |
+| L1 | Hacker triple description | Low | ✅ **FIXED** | Hacker description appears exactly once, not 3 times |
+| L2 | `help`/`hello` produce unexpected | Low | ✅ **FIXED** | `hello` → "Cheery, aren't you?" `help` → contextual help text |
+
+---
+
+## Critical Bugs (Remaining)
+
+### Bug C1: Dream sequence creature daemon doesn't fire
+- **Description:** After `take stone` in the dream's "At Platform" room, the game queues `I-LURKER-APPEARS` (via `QUEUE -1`) and `I-COOL` to advance the dream sequence. These daemons do not fire. The creature never appears, and the player is permanently trapped in the dream (cannot go back up, cannot wake up). The smooth stone is "taken" (score +5) but not in inventory (correct dream behavior), but the dream never resolves.
+- **Commands:**
+  ```
+  > take stone
+  Taken.
+  > wait
+  Time passes...
+  > wait
+  Time passes...
+  > look
+  At Platform
+  You stand before a low rock platform...
+  > examine creature
+  You can't see any creature here.
+  ```
+- **Expected:** After `take stone`, the CLOCKER should fire `I-LURKER-APPEARS` which prints "Suddenly, the dimness becomes darkness..." and moves the LURKER to the room. After 2 more CLOCKER ticks, the creature description appears. After 3 more, the creature grabs you and you wake up in Terminal Room.
+- **Walkthrough reference (lurkinghorror.txt lines 94-103):**
+  ```
+  > take stone
+  Taken.
+  Suddenly, the dimness becomes darkness, and the crowd around you explodes with excitement...
+  > eat stone
+  The darkness before you, now visible, is a creature...
+  > show stone to creature
+  The thing is uninterested...
+  ```
+- **Root cause:** The `QUEUE` mechanism in `SMOOTH-STONE-F` stores daemon entries at memory offsets 48-51 (and 44-47 for the second) of the `C-TABLE` ITABLE, which is only 13 bytes. These entries overflow beyond the allocated table into adjacent memory. While the Z-machine flat-memory model allows this, the entries may be overwritten by other memory operations during the save/restore cycle between commands. Additionally, the `_CHILD_TBL`/`_SIBLING_TBL` address mismatch after save/restore may disrupt the memory region where queue entries are stored.
+- **Severity:** Critical — prevents completion of the dream sequence, which is REQUIRED to obtain the smooth stone for later puzzles (Lovecraftian altar). Permanently soft-locks the player.
+- **Reproduction:** 100%. Start new game, login, read paper, page through 4 MORE pages, enter dream, go down, examine platform, take stone → daemon doesn't fire.
+
+---
+
+## High Severity Bugs
+
+### Bug H1: Inventory display (`i`) shows "You are empty-handed"
+- **Description:** The `i` command consistently shows "You are empty-handed" even when items are being carried. Items can be `taken` (says "Taken."), `dropped` (says "Dropped."), and `drop all` finds and drops all carried items. But `i` never lists them.
+- **Commands:**
+  ```
+  > take chair
+  Taken.
+  > i
+  You are empty-handed.       (BUG - should show "You are carrying a chair")
+  > take pc
+  You take it.
+  > i
+  You are empty-handed.       (BUG - should show both items)
+  > drop all
+  the pc: Dropped.
+  the chair: Dropped.         (items ARE tracked correctly)
+  ```
+- **Expected:** Should list all items in inventory, e.g., "You are carrying a chair, a pc, and an assignment."
+- **Root cause:** The `DESCRIBE-CONTENTS` function (used by `V-INVENTORY`) iterates through the player's children using `FIRST?`/`NEXT?` macros, which call `FIRSTQ`/`NEXTQ` in the bootstrap. These read from `_CHILD_TBL` and `_SIBLING_TBL` — byte tables stored in the mem buffer at addresses determined during module loading. However, the SAVE/RESTORE cycle saves and restores these global address variables, which become **stale** across processes because the memory layout differs between the save-origin process and the restore-target process. After RESTORE, `_CHILD_TBL` points to the old process's memory location, while the actual child table data is at a different address. Thus `mem:byte(_CHILD_TBL + player_id)` reads from the wrong location, returning 0 (no children).
+  
+  This issue does NOT affect room descriptions, the parser's object-finding (HELD/HAVE), `take all`/`drop all`, or individual `take`/`drop` commands, because those use the `PQLOC` property (stored per-object, not in a tree structure) to find items.
+  
+  The fix: either:
+  1. Exclude `_CHILD_TBL` and `_SIBLING_TBL` from the save file (they're accidentally saved as numeric globals), OR
+  2. On restore, recalculate `_CHILD_TBL` and `_SIBLING_TBL` from the restored mem data by knowing their fixed offsets.
+- **Severity:** High — inventory management is essential for gameplay. Player cannot see what they're carrying.
+
+---
+
+## Medium Severity Bugs
+
+### Bug M1: `x` abbreviation not recognized
+- **Description:** The classic Infocom abbreviation `x` for "examine" is not in the parser vocabulary.
+- **Command:** `x pc` → "I don't know the word 'x.'"
+- **Expected:** Should be equivalent to `examine pc`.
+- **Severity:** Medium — usability issue.
+
+### Bug M2: `inventory` full word not recognized
+- **Description:** The full word `inventory` returns "I don't know the word 'inventory.'" Only the abbreviation `i` works.
+- **Command:** `inventory` → "I don't know the word 'inventory.'"
+- **Expected:** Should be equivalent to `i`.
+- **Severity:** Medium — usability issue.
+
+### Bug M3: QUIT Y/N prompt not handled cleanly
+- **Description:** After `quit`, the game shows "Do you wish to leave the game? (Y is affirmative): >". The llm.lua confirmation handler attempts to replay the quit command and deliver "y", but the output after answering is empty, and the game continues as if the quit was declined.
+- **Commands:**
+  ```
+  > quit
+  Your score is 0 of a possible 100, in 36 moves...
+  Do you wish to leave the game?
+  (Y is affirmative): >
+  > y
+  (empty output)
+  > look
+  (still in the game)
+  ```
+- **Expected:** Should either quit the game cleanly or cleanly answer "No".
+- **Severity:** Medium — prevents clean exit.
+
+---
+
+## Additional Observations
+
+### Feature Testing Summary
+
+#### Opening & First Impression
+**Status: ✅ Good**
+- Atmospheric opening paragraph
+- Game banner displays correctly with serial number 870918
+- Rich room descriptions
+- Initial inventory: assignment
+
+#### Movement
+| Command | Result |
+|---------|--------|
+| `north`/`n` | ✅ Works correctly |
+| `south`/`s` | ✅ Works correctly |
+| `east`/`e` | ✅ Works correctly |
+| `west`/`w` | ✅ **FIXED —** Now works! Goes to Kitchen from Second Floor |
+| `up`/`u` | ✅ Works correctly |
+| `down`/`d` | ✅ Works correctly |
+| `go <dir>` | ✅ Works (e.g., go west) |
+
+#### Look Command
+| Room | Result |
+|------|--------|
+| Terminal Room | ✅ Works |
+| Second Floor | ✅ **FIXED** |
+| Third Floor | ✅ **FIXED** |
+| Kitchen | ✅ Works |
+| Computer Center | ✅ Works |
+| Roof | ✅ Works |
+| Smith Street | ✅ Works |
+| Dream (Place/Basalt/Platform) | ✅ Works |
+
+#### Computer & Login Puzzle
+| Command | Result |
+|---------|--------|
+| `turn on pc` | ✅ Boots computer |
+| `type 872325412` | ✅ Accepted |
+| `type uhlersoth` | ✅ Login successful |
+| `edit classics paper` | ✅ Opens editor |
+| `touch paper` | ✅ Opens corrupted paper |
+| `read paper` | ✅ Shows Lovecraftian text |
+| `touch more` (×4) | ✅ Triggers dream sequence |
+
+#### NPC Interaction
+| Command | Result |
+|---------|--------|
+| `ask hacker about master` | ✅ `"Who said anything about any master keys?"` |
+| `ask hacker about pc` | ✅ `"You should consult the documentation."` |
+| `ask hacker about key` | ✅ Asks which key (correct disambiguation) |
+| `tell hacker about pc` | ✅ Responds with disinterest |
+| `show assignment to hacker` | ✅ Grunts, shows little interest |
+| `give assignment to hacker` | ✅ "No thanks, keep it for now." |
+| `talk to hacker` | ✅ **FIXED —** "Hmmm ... the hacker waits for you to say something." |
+| `attack hacker` | ✅ "The hacker retreats. 'I know karate!'" |
+
+#### Inventory & Object Manipulation
+| Command | Result |
+|---------|--------|
+| `i` | ✅ Works (but shows empty-handed — Bug H1) |
+| `inventory` | ❌ Not recognized (Bug M2) |
+| `take all` | ✅ Works (lists each item) |
+| `drop all` | ✅ Works (lists each item) |
+| `take chair` | ✅ "Taken." (exists in inventory despite `i` showing empty) |
+| `examine pc` | ✅ Works |
+| `examine computer` | ✅ Works (synonym) |
+| `examine chair` | ✅ Works (no "You already are") |
+| `examine it` | ✅ Pronoun reference works |
+| `examine hacker` | ✅ Full description |
+
+#### OOPS Command
+| Command | Result |
+|---------|--------|
+| `take char` → `oops chair` | ✅ "I don't know the word 'char.'" → "Taken." |
+| `oops` (without prior error) | ✅ "I can't help your clumsiness." |
+
+#### Parser Responsiveness
+| Command | Result |
+|---------|--------|
+| `hello` | ✅ "Cheery, aren't you?" |
+| `help` | ✅ "Well, nothing happens. Perhaps you should turn on the computer?" |
+| `listen` | ✅ "You hear nothing unsettling." |
+| `wait` | ✅ "Time passes..." |
+| `time` | ✅ "It seems like three o'clock in the morning." |
+| `score` | ✅ Shows correct score and move count |
+| `quit` | ⚠️ Shows prompt but Y/N handling incomplete |
+
+#### Ambient/Death Systems
+| Feature | Result |
+|---------|--------|
+| Cold on roof | ✅ Progressive cold warnings: "You can feel the cold worming through..." → "Your eyes are icing up." → "Each breath is like swallowing knives" |
+| Attacking NPCs | ✅ Handled gracefully ("I know karate!") |
+| CLOCKER events | ✅ Moves increment correctly (score tracker works) |
+| I-URCHIN daemon | ✅ Registered at startup (fired every 10 moves) |
+
+#### Elevator & Kitchen
+| Feature | Result |
+|---------|--------|
+| `examine call button` | ✅ "Which call button do you mean, the up-arrow or the down-arrow?" (no memory dump) |
+| `examine up-arrow` | ✅ "You see nothing special about the up-arrow." |
+| Kitchen (west of 2nd Floor) | ✅ Accessible, describes refrigerator and microwave |
+| `open refrigerator` | ❌ "You can't see any refrigerator here." (may be expected — described in room text but not individually interactable) |
+
+#### Verbal Synonyms
+| Verb | Status |
+|------|--------|
+| `examine` | ✅ Works |
+| `examine it` | ✅ Works |
+| `x` (abbreviation) | ❌ Not recognized (Bug M1) |
+| `look` | ✅ Works |
+| `listen` | ✅ Works |
+| `wait` | ✅ Works |
+| `take` | ✅ Works |
+| `drop` | ✅ Works |
+| `ask` | ✅ Works |
+| `tell` | ✅ Works |
+| `show` | ✅ Works |
+| `give` | ✅ Works |
+| `talk` | ✅ **FIXED** (was "I don't know the word 'talk.'") |
+| `help` | ✅ **FIXED** |
+| `hello` | ✅ **FIXED** |
+| `inventory` | ❌ Not recognized (Bug M2) |
+| `score` | ✅ Works |
+| `time` | ✅ Works |
+| `quit` | ⚠️ Partial (confirmation prompt works but Y/N handling incomplete) |
+| `oops` | ✅ Works |
+| `type` | ✅ Works |
+| `edit` | ✅ Works |
+| `touch` | ✅ Works (for MORE box) |
+| `read` | ✅ Works |
+| `plug` | ✅ Works ("You plug in the computer.") |
+
+---
+
+## Playability Assessment
+
+### Can the game be won?
+**Not yet.** Two issues block completion:
+
+1. **Dream sequence daemon (Critical Bug C1):** After reading the computer paper and entering the dream, the `I-LURKER-APPEARS` daemon does not fire after taking the smooth stone. The creature never appears, and the player is permanently trapped in the "At Platform" room in the dream sequence. This prevents obtaining the smooth stone in the real world and blocks the entire later puzzle chain (Lovecraftian altar).
+
+2. **Inventory display (High Bug H1):** The `i` command shows "You are empty-handed" regardless of what the player carries. This makes inventory management practically impossible (the player can't see what they have).
+
+### Can the game be played meaningfully?
+**Yes, with caveats.** A player can:
+- ✅ Start the game with full atmospheric introduction
+- ✅ Explore all rooms: Terminal Room, Second Floor, Third Floor, Kitchen, Computer Center, Roof, Smith Street
+- ✅ Log into the computer (login/read paper/edit sequence works perfectly)
+- ✅ Interact with the hacker (ask, tell, show, give, talk all work)
+- ✅ Navigate between all floors and rooms (all direction abbreviations work)
+- ✅ Examine most objects without crashes
+- ❌ **Cannot** see inventory (`i` shows empty-handed)
+- ❌ **Cannot** complete the dream sequence (soft-locked after taking the stone)
+- ❌ **Cannot** use `x` abbreviation or `inventory` full word
+
+### How many commands before hitting a blocker?
+**About 20-25 commands** before hitting the dream sequence (login + page through). The dream can be entered and explored, but taking the smooth stone soft-locks the game. 
+
+A player who avoids the dream can explore endlessly — movement, NPC interaction, and object manipulation all work stably across many turns (50+ tested).
+
+### How stable is the runtime?
+- **CLOCKER:** Fully functional — survives 50+ turns, score/moves increment correctly
+- **Save/restore:** Mostly stable. Most object state persists. The `_CHILD_TBL`/`_SIBLING_TBL` address mismatch is the main remaining state issue, affecting inventory display and daemon queue entries
+- **Memory:** No more memory dumps or crashes from object examination
+- **Parser:** Reliable — no hangs or crashes across dozens of varied commands
+- **Runtime crashes:** Zero crashes observed in 80+ turns across multiple sessions
+
+---
+
+## Comparison with Previous Report
+
+| Metric | Previous Report | Current Report | Change |
+|--------|----------------|----------------|--------|
+| Critical Bugs | 2 | 1 | ⬇️ |
+| High Severity | 4 | 1 | ⬇️ |
+| Medium Severity | 5 | 3 | ⬇️ |
+| Low Severity | 2 | 0 | ⬇️ |
+| Overall Verdict | Playable but unstable | Largely playable | ✅ |
+
+---
+
+## Recommendations (Priority Order)
+
+### Must Fix:
+1. **Fix `_CHILD_TBL`/`_SIBLING_TBL` address persistence across save/restore** — This is the root cause of the inventory display bug (Bug H1) and likely contributes to the dream daemon issue (Bug C1). The simplest fix: exclude these variables from the save file (they overwrite correct values set during module loading). Alternatively, recalculate their addresses after restore, or use pointer-relative addressing instead of absolute addresses.
+2. **Fix QUEUE/CLOCKER daemon persistence in the dream sequence** — The `I-LURKER-APPEARS` daemon queued by `SMOOTH-STONE-F` doesn't fire. This may be related to the `_CHILD_TBL`/`_SIBLING_TBL` address issue (the QUEUE table may be overwritten by adjacent memory operations). Ensure C-TABLE entries survive save/restore, or use an alternative mechanism (like incremental states in a global counter) to advance the dream.
+
+### Important:
+3. **Add `x` as abbreviation for `examine`** — Standard Infocom shortcut.
+4. **Add `inventory` as synonym for `i`** — Standard Infocom full-word command.
+
+### Polish:
+5. **Fix QUIT confirmation prompt** — Ensure Y/N answer is correctly delivered to the YES? function.
+6. **Test the elevator** — Verify elevator doors work and can be used to access different floors (this was not tested in this session).
+
+---
+
+## Testing Environment
+
+```
+Platform: macOS (Darwin)
+Lua: lua5.4
+Runtime: AdventureArena ZIL runtime (zilscript/)
+Game: The Lurking Horror (Release 15, Serial 870918)
+Interface: llm.lua (process-per-command save/restore model)
+Saves: /tmp/lh-*.sav
+Session count: 5 sessions, 80+ total game turns
+```
+
+---
+
+*Report generated by game tester agent after comprehensive playthrough*
diff --git a/infocom/zork1/globals.zil b/infocom/zork1/globals.zil
index a13f1dc..03a8b52 100644
--- a/infocom/zork1/globals.zil
+++ b/infocom/zork1/globals.zil
@@ -247,7 +247,8 @@ you!" CR>)
 		<TELL "How romantic!" CR>)
 	       (<VERB? EXAMINE>
 		<COND %<COND (<==? ,ZORK-NUMBER 1>
-			      '(<EQUAL? ,HERE <LOC ,MIRROR-1> <LOC ,MIRROR-2>>
+			      '(<AND ,MIRROR-1 ,MIRROR-2
+			             <EQUAL? ,HERE <LOC ,MIRROR-1> <LOC ,MIRROR-2>>>
 		                <TELL
 "Your image in the mirror looks tired." CR>))
 			     (<==? ,ZORK-NUMBER 3>
@@ -306,4 +307,4 @@ you!" CR>)
 	(SYNONYM PAIR HANDS HAND)
 	(ADJECTIVE BARE)
 	(DESC "pair of hands")
-	(FLAGS NDESCBIT TOOLBIT)>
\ No newline at end of file
+	(FLAGS NDESCBIT TOOLBIT)>
diff --git a/infocom/zork1/syntax.zil b/infocom/zork1/syntax.zil
index d5681ab..ffecdea 100644
--- a/infocom/zork1/syntax.zil
+++ b/infocom/zork1/syntax.zil
@@ -201,7 +201,7 @@
 	= V-LOOK-INSIDE>
 <SYNTAX EXAMINE ON OBJECT (HELD CARRIED IN-ROOM ON-GROUND MANY)
 	= V-LOOK-INSIDE>
-<SYNONYM EXAMINE DESCRIBE WHAT WHATS>
+<SYNONYM EXAMINE DESCRIBE INSPECT X WHAT WHATS>
 
 <SYNTAX EXORCISE OBJECT = V-EXORCISE>
 <SYNTAX EXORCISE OUT OBJECT (FIND ACTORBIT) = V-EXORCISE>
@@ -559,4 +559,4 @@
 <SYNTAX YELL = V-YELL>
 <SYNONYM YELL SCREAM SHOUT>
 
-<SYNTAX ZORK = V-ZORK>
\ No newline at end of file
+<SYNTAX ZORK = V-ZORK>
diff --git a/infocom/zork1/test/test-assertions.zil b/infocom/zork1/test/test-assertions.zil
index f5de842..b37b328 100644
--- a/infocom/zork1/test/test-assertions.zil
+++ b/infocom/zork1/test/test-assertions.zil
@@ -1,11 +1,4 @@
-<INSERT-FILE "infocom/zork1/globals">
-<INSERT-FILE "infocom/zork1/clock">
-<INSERT-FILE "books/blackwood-horror/dungeon">
-<INSERT-FILE "books/blackwood-horror/actions">
-<INSERT-FILE "infocom/zork1/parser">
-<INSERT-FILE "infocom/zork1/verbs">
-<INSERT-FILE "infocom/zork1/syntax">
-<INSERT-FILE "infocom/zork1/main">
+<INSERT-FILE "books/blackwood-horror/blackwood-horror">
 
 <CONSTANT RELEASEID 1>
 
@@ -20,11 +13,9 @@
     ;"Test assert-inventory with false expectation (should pass - plaque not in inventory yet)"
     <ASSERT "Brass plaque NOT in inventory initially" <N==? <LOC ,BRASS-PLAQUE> ,ADVENTURER>>
     
-    ;"Take the plaque"
-    <ASSERT "Take brass plaque" <CO-RESUME ,CO "take plaque" T> <==? <LOC ,BRASS-PLAQUE> ,ADVENTURER>>
-    
-    ;"Test assert-inventory with true expectation (should pass - plaque now in inventory)"
-    <ASSERT "Brass plaque IS in inventory after taking" <==? <LOC ,BRASS-PLAQUE> ,ADVENTURER>>
+    ;"The fixed plaque refuses removal"
+    <ASSERT-TEXT "bolted firmly" <CO-RESUME ,CO "take plaque">>
+    <ASSERT "Brass plaque remains outside inventory" <N==? <LOC ,BRASS-PLAQUE> ,ADVENTURER>>
     
     ;"Move to reception room"
     <ASSERT "Enter sanitarium" <CO-RESUME ,CO "north" T> <==? ,HERE ,SANITARIUM-ENTRANCE>>
diff --git a/infocom/zork1/test/test-check-commands.zil b/infocom/zork1/test/test-check-commands.zil
index fa2346e..c25344a 100644
--- a/infocom/zork1/test/test-check-commands.zil
+++ b/infocom/zork1/test/test-check-commands.zil
@@ -1,11 +1,4 @@
-<INSERT-FILE "infocom/zork1/globals">
-<INSERT-FILE "infocom/zork1/clock">
-<INSERT-FILE "books/blackwood-horror/dungeon">
-<INSERT-FILE "books/blackwood-horror/actions">
-<INSERT-FILE "infocom/zork1/parser">
-<INSERT-FILE "infocom/zork1/verbs">
-<INSERT-FILE "infocom/zork1/syntax">
-<INSERT-FILE "infocom/zork1/main">
+<INSERT-FILE "books/blackwood-horror/blackwood-horror">
 
 <CONSTANT RELEASEID 1>
 
@@ -20,11 +13,9 @@
     ;"Test check-inventory when object is NOT in inventory (plaque not taken yet)"
     <ASSERT "Plaque NOT in inventory initially" <N==? <LOC ,BRASS-PLAQUE> ,ADVENTURER>>
     
-    ;"Take the plaque"
-    <ASSERT "Take brass plaque" <CO-RESUME ,CO "take plaque" T> <==? <LOC ,BRASS-PLAQUE> ,ADVENTURER>>
-    
-    ;"Test check-inventory when object IS in inventory"
-    <ASSERT "Plaque IS in inventory after taking" <==? <LOC ,BRASS-PLAQUE> ,ADVENTURER>>
+    ;"The fixed plaque refuses removal and remains outside inventory"
+    <ASSERT-TEXT "bolted firmly" <CO-RESUME ,CO "take plaque">>
+    <ASSERT "Plaque remains outside inventory" <N==? <LOC ,BRASS-PLAQUE> ,ADVENTURER>>
     
     ;"Move to reception room to test flags"
     <ASSERT "Enter sanitarium" <CO-RESUME ,CO "north" T> <==? ,HERE ,SANITARIUM-ENTRANCE>>
diff --git a/limehouse.sav.actions b/limehouse.sav.actions
new file mode 100644
index 0000000..691bd30
--- /dev/null
+++ b/limehouse.sav.actions
@@ -0,0 +1,29 @@
+{"time":1784024404,"game":"limehouse-killings","action":"go north"}
+{"time":1784024409,"game":"limehouse-killings","action":"take magnifying glass"}
+{"time":1784024414,"game":"limehouse-killings","action":"go east"}
+{"time":1784024419,"game":"limehouse-killings","action":"examine ledger"}
+{"time":1784024425,"game":"limehouse-killings","action":"examine torn page"}
+{"time":1784024430,"game":"limehouse-killings","action":"take torn page"}
+{"time":1784024435,"game":"limehouse-killings","action":"go west"}
+{"time":1784024445,"game":"limehouse-killings","action":"go west"}
+{"time":1784024450,"game":"limehouse-killings","action":"examine seal"}
+{"time":1784024455,"game":"limehouse-killings","action":"take seal"}
+{"time":1784024459,"game":"limehouse-killings","action":"go north"}
+{"time":1784024465,"game":"limehouse-killings","action":"take foxglove"}
+{"time":1784024469,"game":"limehouse-killings","action":"take charcoal"}
+{"time":1784024474,"game":"limehouse-killings","action":"go south"}
+{"time":1784024482,"game":"limehouse-killings","action":"go east"}
+{"time":1784024488,"game":"limehouse-killings","action":"go down"}
+{"time":1784024493,"game":"limehouse-killings","action":"open drawer"}
+{"time":1784024498,"game":"limehouse-killings","action":"take leather roll"}
+{"time":1784024503,"game":"limehouse-killings","action":"go west"}
+{"time":1784024508,"game":"limehouse-killings","action":"take knife"}
+{"time":1784024515,"game":"limehouse-killings","action":"examine footprint"}
+{"time":1784024520,"game":"limehouse-killings","action":"go south"}
+{"time":1784024526,"game":"limehouse-killings","action":"take lantern"}
+{"time":1784024532,"game":"limehouse-killings","action":"examine trunk"}
+{"time":1784024541,"game":"limehouse-killings","action":"examine letter"}
+{"time":1784024547,"game":"limehouse-killings","action":"open trunk"}
+{"time":1784024552,"game":"limehouse-killings","action":"take letter"}
+{"time":1784024559,"game":"limehouse-killings","action":"search trunk"}
+{"time":1784024565,"game":"limehouse-killings","action":"read letter"}
diff --git a/llm.lua b/llm.lua
index 8193247..0ff5c4e 100755
--- a/llm.lua
+++ b/llm.lua
@@ -84,14 +84,22 @@ local GAMES = {
     },
     spellbreaker = {
         modules = {"infocom.spellbreaker.z6"}
+    },
+    ["limehouse-killings"] = {
+        modules = {"books.limehouse-killings.limehouse-killings"}
+    },
+    ["blackwood-horror"] = {
+        modules = {"books.blackwood-horror.blackwood-horror"}
     }
 }
 
 local game_name = args.game or "zork1"
 local game_config = GAMES[game_name]
 if not game_config then
+    local available = {}
+    for k in pairs(GAMES or {}) do table.insert(available, k) end
     io.write(string.format('{"ok":false,"error":"Unknown game: %s. Available: %s"}\n',
-        game_name, table.concat(table.keys(GAMES or {}), ", ")))
+        game_name, table.concat(available, ", ")))
     os.exit(1)
 end
 
@@ -213,7 +221,7 @@ local restore
 local function write_error_and_exit(message)
     restore()
     message = tostring(message):gsub('\27%[[0-9;]*m', '')
-    io.write(string.format('{"ok":false,"error":%s}\n', json_escape(message)))
+    io.write("ERROR: " .. message .. "\n")
     os.exit(1)
 end
 
@@ -378,9 +386,26 @@ local function execute_action(action)
     return resume_action(action)
 end
 
+-- A memory dump cannot serialize a coroutine suspended inside YES?.  If the
+-- preceding one-command invocation stopped at a confirmation prompt, recreate
+-- that prompt in the fresh coroutine before delivering the answer.
+local function execute_action_with_confirmation(action)
+    local answer = action:lower():match("^%s*(.-)%s*$")
+    if answer == "y" or answer == "yes" or answer == "n" or answer == "no" then
+        local history = read_action_history(historyfile)
+        local previous = history[#history]
+        local prompt_action = previous and previous.action:lower():match("^%s*(.-)%s*$")
+        if prompt_action == "quit" or prompt_action == "q"
+                or prompt_action == "restart" or prompt_action == "restar" then
+            execute_action(previous.action)
+        end
+    end
+    return execute_action(action)
+end
+
 -- If we have an action, execute it
 if args.action then
-    local ok, output = pcall(execute_action, args.action)
+    local ok, output = pcall(execute_action_with_confirmation, args.action)
     
     if not ok then
         write_error_and_exit(output)
@@ -405,37 +430,9 @@ if args.action then
     
     restore()
     
-    -- Output JSON
-    local response = {
-        ok = true,
-        output = output,
-        room = room,
-        savefile = savefile,
-        historyfile = historyfile,
-        restored = resumed_from_dump or resumed_from_history,
-    }
-    if save_err then
-        response.save_error = save_err
-    end
-    if history_err then
-        response.history_error = history_err
-    end
-    
-    -- Simple JSON serialization
-    io.write("{")
-    io.write('"ok":' .. tostring(response.ok) .. ',')
-    io.write('"output":' .. json_escape(response.output) .. ',')
-    io.write('"room":' .. json_escape(response.room) .. ',')
-    io.write('"savefile":' .. json_escape(response.savefile) .. ',')
-    io.write('"historyfile":' .. json_escape(response.historyfile) .. ',')
-    io.write('"restored":' .. tostring(response.restored))
-    if response.save_error then
-        io.write(',"save_error":' .. json_escape(response.save_error))
-    end
-    if response.history_error then
-        io.write(',"history_error":' .. json_escape(response.history_error))
-    end
-    io.write("}\n")
+    -- Output plain text (exit 0 = success)
+    io.write(output)
+    os.exit(0)
     
 elseif args.new_game then
     -- Start a new game and get initial output
@@ -469,20 +466,9 @@ elseif args.new_game then
     
     restore()
     
-    io.write("{")
-    io.write('"ok":true,')
-    io.write('"output":' .. json_escape(output) .. ',')
-    io.write('"room":' .. json_escape(room) .. ',')
-    io.write('"savefile":' .. json_escape(savefile) .. ',')
-    io.write('"historyfile":' .. json_escape(historyfile) .. ',')
-    io.write('"new_game":true')
-    if save_err then
-        io.write(',"save_error":' .. json_escape(save_err))
-    end
-    if history_err then
-        io.write(',"history_error":' .. json_escape(history_err))
-    end
-    io.write("}\n")
+    -- Output plain text (exit 0 = success)
+    io.write(output)
+    os.exit(0)
     
 else
     write_error_and_exit("No action specified. Use --action or --new-game")
diff --git a/savefile.sav.actions b/savefile.sav.actions
new file mode 100644
index 0000000..a7ca4af
--- /dev/null
+++ b/savefile.sav.actions
@@ -0,0 +1,12 @@
+{"time":1784021417,"game":"limehouse-killings","action":"go down"}
+{"time":1784021421,"game":"limehouse-killings","action":"look"}
+{"time":1784021426,"game":"limehouse-killings","action":"go north"}
+{"time":1784021431,"game":"limehouse-killings","action":"go down"}
+{"time":1784021435,"game":"limehouse-killings","action":"examine roll"}
+{"time":1784021442,"game":"limehouse-killings","action":"examine leather roll"}
+{"time":1784021443,"game":"limehouse-killings","action":"take roll"}
+{"time":1784022627,"game":"limehouse-killings","action":"go north"}
+{"time":1784022634,"game":"limehouse-killings","action":"go north"}
+{"time":1784022648,"game":"limehouse-killings","action":"look"}
+{"time":1784022653,"game":"limehouse-killings","action":"look"}
+{"time":1784022662,"game":"limehouse-killings","action":"look"}
diff --git a/scripts/check-vocab.lua b/scripts/check-vocab.lua
new file mode 100644
index 0000000..e890802
--- /dev/null
+++ b/scripts/check-vocab.lua
@@ -0,0 +1,221 @@
+#!/usr/bin/env lua
+-- check-vocab.lua: Validate objective parser-vocabulary invariants.
+--
+-- Usage:
+--   lua scripts/check-vocab.lua <file.zil> [file2.zil ...]
+--   lua scripts/check-vocab.lua books/limehouse-killings/dungeon.zil
+--
+-- What it checks:
+--   CRITICAL: Player-addressable objects have a DESC.
+--   CRITICAL: At least one noun from DESC appears in SYNONYM.
+--
+-- Determining whether every prose word in FDESC/LDESC is an interactive noun
+-- requires language and world-model context. This script deliberately does not
+-- guess: the previous heuristic treated verbs, adverbs, and compounds as nouns
+-- and made the repository's own lint target unusable.
+
+-- ============================================================
+-- Parse ZIL OBJECT definitions
+-- ============================================================
+local function parse_zil_objects(content)
+    local objects = {}
+    local pos = 1
+    local len = #content
+    local safety = 0
+
+    while pos <= len do
+        safety = safety + 1
+        if safety > 10000 then break end
+
+        local obj_start = content:find("<OBJECT%s+(%S+)", pos)
+        if not obj_start then break end
+
+        local obj_name = content:match("<OBJECT%s+(%S+)", obj_start)
+        if not obj_name then
+            pos = obj_start + 8
+        else
+            local depth = 1
+            local search_from = obj_start
+            local obj_end = nil
+
+            while search_from <= len do
+                local next_open = content:find("<", search_from + 1)
+                local next_close = content:find(">", search_from + 1)
+                if not next_close then break end
+                if next_open and next_open < next_close then
+                    depth = depth + 1
+                    search_from = next_open
+                else
+                    depth = depth - 1
+                    search_from = next_close
+                    if depth == 0 then
+                        obj_end = next_close
+                        break
+                    end
+                end
+            end
+
+            if not obj_end then
+                pos = obj_start + 8
+            else
+                local obj_block = content:sub(obj_start, obj_end)
+
+                local function extract_property(prop_name)
+                    local pattern1 = "%(" .. prop_name .. '%s+"([^"]*)"'
+                    local val = obj_block:match(pattern1)
+                    if val then return val end
+                    local pattern2 = "%(" .. prop_name .. "%s+([^)]+)%)"
+                    local words_str = obj_block:match(pattern2)
+                    if words_str then
+                        local words = {}
+                        for w in words_str:gmatch("(%S+)") do
+                            table.insert(words, w:lower())
+                        end
+                        return words
+                    end
+                    return nil
+                end
+
+                local synonyms = extract_property("SYNONYM") or {}
+                local desc = extract_property("DESC")
+
+                local syn_set = {}
+                if type(synonyms) == "table" then
+                    for _, w in ipairs(synonyms) do syn_set[w] = true end
+                end
+
+                table.insert(objects, {
+                    name = obj_name,
+                    synonyms = syn_set,
+                    has_synonyms = next(syn_set) ~= nil,
+                    desc = desc,
+                })
+
+                pos = obj_end + 1
+            end
+        end
+    end
+
+    return objects
+end
+
+-- ============================================================
+-- Tokenize description text
+-- ============================================================
+local function tokenize_desc(text)
+    if not text then return {} end
+    local words = {}
+    local cleaned = text:gsub("<[^>]+>", " ")
+    cleaned = cleaned:gsub("[<>]", " ")
+    cleaned = cleaned:gsub('"', " ")
+    cleaned = cleaned:gsub("%-%-", " ")
+    cleaned = cleaned:gsub("^%s+", ""):gsub("%s+$", "")
+    for w in cleaned:gmatch("%S+") do
+        local clean = w:match("^[%p]*(.-)[%p]*$")
+        if clean and #clean > 0 then
+            table.insert(words, clean:lower())
+        end
+    end
+    return words
+end
+
+-- ============================================================
+-- Check a single object
+-- ============================================================
+local function check_object(obj)
+    local issues = {}
+
+    -- An object with vocabulary is player-addressable. Without DESC, generic
+    -- responses print nil or an unrelated inherited default name.
+    if obj.has_synonyms and not obj.desc then
+        table.insert(issues, {
+            level = "CRITICAL",
+            field = "DESC",
+            msg = "player-addressable object has SYNONYM but no DESC",
+        })
+    end
+
+    -- DESC is the name printed by the engine. At least one of its words must be
+    -- an accepted noun. We intentionally do not assume the final word is the
+    -- head noun because descriptions such as "door to the garden" are common.
+    if obj.desc then
+        local desc_words = tokenize_desc(obj.desc)
+        local matched_noun = false
+        for _, word in ipairs(desc_words) do
+            if obj.synonyms[word] then
+                matched_noun = true
+                break
+            end
+        end
+        if #desc_words > 0 and not matched_noun then
+            table.insert(issues, {
+                level = "CRITICAL",
+                field = "DESC",
+                msg = "no DESC word appears in SYNONYM — parser won't match the printed name",
+            })
+        end
+    end
+
+    return issues
+end
+
+-- ============================================================
+-- Main
+-- ============================================================
+local function main()
+    local files = {}
+    for i = 1, #arg do
+        table.insert(files, arg[i])
+    end
+
+    if #files == 0 then
+        io.write("Usage: lua scripts/check-vocab.lua <file.zil> [file2.zil ...]\n")
+        io.write("\nValidates that player-addressable objects have DESC and that\n")
+        io.write("each DESC contains a noun registered as a SYNONYM.\n")
+        os.exit(1)
+    end
+
+    local total_critical = 0
+
+    for _, filepath in ipairs(files) do
+        local f = io.open(filepath, "r")
+        if not f then
+            io.write("Error: cannot open " .. filepath .. "\n")
+            os.exit(1)
+        end
+        local content = f:read("*a")
+        f:close()
+
+        local objects = parse_zil_objects(content)
+        local file_issues = {}
+
+        for _, obj in ipairs(objects) do
+            local issues = check_object(obj)
+            if #issues > 0 then
+                file_issues[obj.name] = issues
+            end
+        end
+
+        if next(file_issues) then
+            io.write(filepath .. ":\n")
+            for obj_name, issues in pairs(file_issues) do
+                for _, issue in ipairs(issues) do
+                    io.write(string.format("  [%s] %s: %s\n", issue.level, obj_name, issue.msg))
+                    if issue.level == "CRITICAL" then
+                        total_critical = total_critical + 1
+                    end
+                end
+            end
+            io.write("\n")
+        end
+    end
+
+    io.write(string.format("%d critical across %d file(s)\n",
+        total_critical, #files))
+
+    if total_critical > 0 then
+        os.exit(1)
+    end
+end
+
+main()
diff --git a/skills/02_working_materials_and_design_docs.md b/skills/02_working_materials_and_design_docs.md
index 50f939f..8cbe770 100644
--- a/skills/02_working_materials_and_design_docs.md
+++ b/skills/02_working_materials_and_design_docs.md
@@ -20,6 +20,14 @@ Create the design artifacts that externalize world structure and puzzle logic.
 11. Add explicit unwinnable-state prevention notes to puzzle and state docs.
 12. Define progress structure (score/chapter/rank/objective milestones) in `STORY_STATE.md`.
 13. Add co-play and discussion surfaces (shared vocabulary, parent hints, printable notes/log prompts).
+14. Treat `TRANSCRIPT_TESTS.md` as an exact command contract, not pseudocode. For every critical step record:
+    - exact typed command, including spaces or hyphens;
+    - expected room/object output;
+    - required noun synonyms and adjectives;
+    - state change and inventory/location change;
+    - a likely alternate wording and wrong-order attempt.
+15. Keep `OBJECTS.md` parser-facing: list the canonical head noun, exact compound spelling, adjectives, ambiguity risks, containment flags, and discovery command for every object.
+16. Populate `OBJECTS.md` from every concrete noun promised by room prose, blocked exits, and puzzle responses. Do not list a door, window, drawer, switch, rope, vehicle, gate, or container only in `STORY_STATE.md` as a Boolean; give the physical entity its own object row and reserve globals for supplementary or abstract state.
 
 ## Outputs
 - `MAP.md`
@@ -35,6 +43,8 @@ Create the design artifacts that externalize world structure and puzzle logic.
 - Geography is mostly mappable and room naming is consistent enough for player notes.
 - Opening setup is concrete and testable in under one minute of play.
 - Object and puzzle docs support both mastery play and hint-assisted completion.
+- Every golden-path command is valid player input rather than an internal object ID or direct `PERFORM` shorthand.
+- Every noun in the opening slice has an explicit parser-vocabulary plan before ZIL implementation begins.
 
 ## Primary Source Coverage
 - `ZIL_TEXT_ADVENTURE_AGENTS.md`: section 1, sections 2.3-2.4, section 5.3
diff --git a/skills/03_world_model_and_puzzle_architecture.md b/skills/03_world_model_and_puzzle_architecture.md
index a7fbd27..5470eda 100644
--- a/skills/03_world_model_and_puzzle_architecture.md
+++ b/skills/03_world_model_and_puzzle_architecture.md
@@ -18,12 +18,22 @@ Translate design docs into a coherent simulation plan before full implementation
    - guessable command vocabulary
 4. Validate dependency graph and prevent softlocks.
 5. Define default response strategy and custom overrides for likely wrong attempts.
+6. Audit every planned noun phrase before implementation:
+   - object identifiers and `DESC` do not automatically make words parseable;
+   - the head noun belongs in `SYNONYM`;
+   - modifiers belong in `ADJECTIVE`;
+   - exact hyphenated transcript spellings belong in `SYNONYM` when supported;
+   - two in-scope objects sharing a noun need distinguishing adjectives.
+7. Define container visibility transitions: where contents begin, which action sets `OPENBIT`, and which flags let the parser search inside.
+8. Define each one-time counter as `event flag -> guarded increment`, including which verbs can discover the same clue.
+9. Audit physical nouns against the object registry. Every described fixture or obstacle that affords player actions must be a real object with vocabulary, scope, flags, and behavior; do not substitute a global Boolean for a door, window, container, switch, vehicle, or similar world entity.
 
 ## Infocom-Quality Simulation Checks
 - Build a command matrix for each major puzzle with at least ten likely player attempts; implement useful responses for the top attempts.
 - Ensure common parser verbs and synonyms are covered (`look`, `examine`, `open`, `close`, `take/get`, `drop`, `read`, `put`, `unlock`, `attack`, `listen`, `smell`, `wait`, `again`, inventory shortcuts).
 - Keep the puzzle challenge in idea-space, not wording-space; avoid single exact-verb bottlenecks.
 - Ensure world state is physical and persistent (object movement, room state changes, blocked/unblocked routes, timed hazards).
+- Prefer object state (`OPENBIT`, containment, location, visibility) over parallel global state. Use globals for abstract facts and milestones, or to supplement a real object when the substrate lacks a specific state such as `LOCKEDBIT`.
 - Preserve challenge while reducing accidental cruelty (telegraphed danger, recoverable mistakes, explicit unwinnable-risk handling).
 - Prefer meaningful mazes over filler mazes; if maze-like areas exist, provide landmarks or distinct mechanics.
 - Support optional mastery with alternate/risky/clever solutions where feasible.
@@ -33,12 +43,115 @@ Translate design docs into a coherent simulation plan before full implementation
 - Object/verb response matrix
 - Softlock mitigation list
 
+## Puzzle Artistry: Good vs. Bad Patterns
+
+These patterns are drawn from a direct comparison between Zork III (infocom/zork3/) and Blackwood Horror (books/blackwood-horror/). Each section contrasts key-and-lock mechanics with narrative-integrated puzzle design.
+
+### 1. Puzzles Should Be the Story, Not Reskinned Item Gates
+
+**BAD (Blackwood — key daisy chain):**
+```
+brass-key → desk-drawer → patient-file (lore only, no gate)
+scalpel → chains → morgue access
+valve → steam-door → hydrotherapy access
+safe-key (in hollow book) → wall-safe → chapel-key → chapel access
+scalpel → wooden-box → relic
+serum + syringe + relic → held during HELLO → win
+```
+
+Every step is "find key → unlock next area → find next key." You could reskin this exact chain as a space station, pirate ship, or wizard's tower by renaming the keys and rooms. The horror setting is wallpaper.
+
+**GOOD (Zork III — `3actions.zil:1429-1436`):**
+The Dungeon door requires becoming the Dungeon Master — wearing cloak, hood, amulet, staff, ring, and carrying the lore book and key. This is the culmination of collecting identity-granting items across all three Zork games. The puzzle *is* the story: you must literally become what you seek to understand.
+
+**GOOD (Zork III — `3actions.zil:1112-1175`):**
+The mirror box is a navigational puzzle that requires rotating a magical structure via colored panels. Completely novel mechanics that feel like operating a mysterious device. No keys, no locks — just spatial reasoning within the fiction.
+
+**Rule:** At least 2 of your major gates must be solved by understanding the fiction rather than finding a key. Replace "find key → unlock door" with: performing a ritual, understanding a character's history, arranging objects in a pattern, choosing the right moment, or demonstrating a quality the story values. A key should have *identity* — "the chapel key" is generic; "the key Patient-189 carved from his restraints" is a story.
+
+### 2. Narrative Arc: Three Escalating Acts
+
+**BAD (Blackwood):**
+Linear room-by-room exploration. The player moves from entrance → basement → admin wing → garden → chapel with no structural breaks, no points of no return, and no escalation in challenge type. The same clock routines fire at fixed intervals regardless of progress. Nothing in earlier rooms changes as the player advances.
+
+**GOOD (Zork III):**
+- **Act 1 (Arrival):** Dream sequence, museum, Royal Puzzle. Establishes the quest.
+- **Act 2 (Dungeon Gates):** Mirror maze, beam room, Guardians. Tests spatial reasoning and stealth.
+- **Act 3 (The Dungeon Master):** Flaming pit, prison cells, Treasury. Tests cleverness, compassion, and identity.
+
+Each act is gated by a different *type* of challenge, not just a different key. The dungeon physically changes (earthquake opens the cleft, doors unlock after tests). The Dungeon Master appears, disappears, and reappears in escalating forms.
+
+**Rule:** Structure your game in three acts with clear threshold moments. Each act should have a different dominant challenge type (exploration → deduction → confrontation). At each act boundary, the world should visibly change. Earlier rooms should show different descriptions after the player passes through major story beats.
+
+### 3. Room Cohesion: A Real Place, Not a Trope Checklist
+
+**BAD (Blackwood — 20 rooms):**
+entrance hall → reception → operating theater → patient ward → morgue → basement stairs → boiler room → storage room → flooded chamber → hydrotherapy room → isolation ward → electroshock theater → padded cell → observation deck → administrative wing → director's office → staff quarters → cafeteria → garden → chapel
+
+This reads like a Wikipedia article on "rooms in a mental hospital." Each room is exactly what its name promises. The operating theater has an operating table. The morgue has refrigerated drawers. There are no surprises. The chapel ("beyond the garden") has no institutional relationship to a sanitarium — why would a 1950s mental hospital have an ancient stone chapel?
+
+**GOOD (Zork III):**
+The Royal Museum feeds into the Royal Puzzle (a museum exhibit), which feeds into dungeon corridors. The Land of Shadow is a completely different biome but shares compass-rose and channel features with the mirror maze. The flaming pit is visible from multiple rooms (cells, parapet, north corridor), creating spatial grounding. The Engravings Room's runes foreshadow the guardians, flames, and old man. Every location belongs to a single fictional geography with internal logic.
+
+**Rule:** Every room must either (a) subvert its apparent function, or (b) be visible/audible from at least one other room. No room should exist just because the setting "should have one." The fictional geography must answer: why is this room HERE, in relationship to its neighbors? If the answer is only "it's a spooky hospital and hospitals have those," delete it or give it a specific institutional reason to exist.
+
+### 4. World State Must Change After Thresholds
+
+**BAD (Blackwood):**
+After the player discovers the identity twist, earlier rooms show the same descriptions. After cutting chains, the door object's LDESC still says "sealed with chains." After opening the steam door, the sealed door's LDESC still says "sealed shut." After the game is won, the chapel still lists burning green candles. The world is static.
+
+**GOOD (Zork III — `3actions.zil:2451-2477`):**
+The earthquake (I-CLEFT) dynamically alters the dungeon, opening new passages and changing room descriptions. The dungeon door panels change their message after tests are completed. The time machine sequence changes museum exhibits based on player actions in the past.
+
+**Rule:** Every major story event must change at least 2 existing rooms — either through updated dynamic descriptions (ACTION + M-LOOK), changed object states (FCLEAR flags), or new objects appearing. Use the pattern from Zork I's `EAST-HOUSE` and the skill 04 rule 7: never freeze mutable state into LDESC. Rooms with state changes should omit LDESC and use ACTION routines with M-LOOK.
+
+### 5. NPC Autonomy: Characters That Move Through the World
+
+**BAD (Blackwood — `actions.zil:568-598`):**
+Patient-189 handles five verbs and is permanently static. It never moves, never approaches, never wanders. It is a puzzle object with ACTORBIT.
+
+**GOOD (The Lurking Horror — `frob.zil:346-435`):**
+The urchin uses a true pathfinding routine (`I-URCHIN`) that evaluates all available exits from its current room and moves to a valid adjacent room not occupied by another NPC. It has states (scared, armed, fleeing), responds differently based on what the player holds, and operates on an independent clock schedule.
+
+**GOOD (The Lurking Horror — `hacker.zil`):**
+The hacker has a full 12-topic dialogue tree, a multi-stage help sequence (takes over terminal → mumbles → fixes file system → wanders away), food preferences (will only accept properly heated Chinese food), and a corruption arc (if player reaches inner lair, the hacker follows, gets absorbed, and emerges transformed).
+
+**Rule:** An ACTORBIT object must have at least one autonomous behavior (movement, approach, state change) driven by a clock daemon. It must change state based on player actions AND on purely internal triggers (time passing, other puzzles solved). The weakest NPC in a commercial Infocom game has more autonomy than Blackwood's only NPC.
+
+### 6. Object Interaction Depth: Tool Chains and System Combinations
+
+**BAD (Blackwood):**
+Every puzzle is a single verb on a single object: USE SCALPEL ON CHAINS, UNLOCK DOOR WITH KEY, OPEN BOX WITH SCALPEL. No puzzle requires chaining two objects together or considering object state (temperature, power, saturation) as a puzzle variable.
+
+**GOOD (The Lurking Horror):**
+- The liquid nitrogen puzzle: find nitrogen flask → pour on slime curtain → nitrogen freezes slime → shatter frozen slime → open ancient door. Four steps, two objects, one state change (temperature).
+- The Chinese food puzzle: find Chinese food carton (frozen) → heat in microwave at specific setting (2 minutes, HIGH) → give to hacker → receive master key. Objects have temperature states that affect NPC behavior.
+- The power line puzzle: find axe → cross water while wearing rubber boots + gloves → cut high-voltage line → plug into repeater box → electrocute boss. Requires tool, protective equipment, environmental navigation, and correct ordering.
+
+**Rule:** At least 2 major puzzles must require chaining 3+ objects or considering an object's state (hot/cold, charged/drained, wet/dry) as a puzzle variable. Every object that can hold state should have visible EXAMINE feedback showing its current state. A game where no object has plural states and every puzzle is single-step is a fetch quest, not an adventure.
+
+### 7. Clock-Driven Mechanical Depth: Systems That Simulate, Not Just Decorate
+
+**BAD (Blackwood — `actions.zil:854`):**
+Clock routines (I-WHISPER, I-CREAKING, I-FOOTSTEPS, I-FLICKERING, I-COLD-DRAFT) fire atmospheric flavor text on timers. None of them interact with game state. None create mechanical consequences. They are wallpaper that the player tunes out after the third repetition.
+
+**GOOD (The Lurking Horror):**
+- **Flashlight battery drain** (`cs.zil:1407-1434`): I-FLASHLIGHT daemon dims the flashlight through 5 stages (FRESH → DIM → VERY-DIM → ALMOST-GONE → OUT). Each stage has unique descriptive text and affects whether the player can see in dark rooms. Running out of light at the wrong moment is a real danger.
+- **Freeze-to-death clock** (`cs.zil:60-80`): I-FREEZE-TO-DEATH tracks cumulative exposure to cold. First warning at 3 ticks, then 6, then 9, then death at 12. The player must find shelter or warm clothing before the timer expires.
+- **NPC AI scheduling** (`frob.zil:346-435`): The urchin moves on a clock daemon, not on player triggers. It enters rooms, steals objects, and flees independently, creating a dynamic world where NPCs have agendas.
+- **Temperature decay** (`cs.zil:130-148`): I-COOL tracks object temperature. The Chinese food cools over time, becoming less appealing to the hacker. The nitrogen flask warms, affecting how much slime it can freeze.
+
+**Rule:** Every clock daemon must do at least one of: (a) advance a numerical state that has gameplay consequences, (b) cause autonomous NPC behavior, or (c) modify object state that another system reads. Atmosphere-only daemons may exist but should be outnumbered 2:1 by mechanical daemons. The player should be able to observe clock effects through EXAMINE and gameplay consequences, not just read flavor text.
+
 ## Acceptance Checks
 - No puzzle depends on inaccessible prerequisites.
 - Reasonable command attempts have authored responses.
 - Defaults are overridden where narrative/puzzle intent requires.
 - Navigation model supports player mapping and repeat travel without confusion.
 - At least one long-loop puzzle requires carrying knowledge or objects between distant locations.
+- The first vertical slice can be played with the exact planned commands before the next slice is implemented.
+- Repeating TAKE/READ/EXAMINE or opening an already-open object cannot duplicate progress or strand contents.
+- Every physical noun named in room prose or a blocked-exit message resolves to an object in scope and supports the obvious generic verbs.
 
 ## Primary Source Coverage
 - `ZIL_TEXT_ADVENTURE_AGENTS.md`: sections 3, 4, 5
diff --git a/skills/04_content_writing_and_npc_layer.md b/skills/04_content_writing_and_npc_layer.md
index 1468526..b457d13 100644
--- a/skills/04_content_writing_and_npc_layer.md
+++ b/skills/04_content_writing_and_npc_layer.md
@@ -8,7 +8,7 @@ Write player-facing text and interactions that teach play and maintain tone.
 
 ## Required Actions
 1. Write first-visit and revisit room text with actionable nouns.
-2. Ensure every mentioned noun is handled (object, pseudo object, or scenery response).
+2. **Ensure every mentioned noun is handled** — every object, person, or feature mentioned in room or object text must be reachable through the parser. If a room description says "a heavy door to the north," there must be an object with `SYNONYM DOOR` so `OPEN DOOR` works. Use objects for interactive items (doors, containers, NPCs), PSEUDO for scenery that players might EXAMINE (paintings, fireplaces, rubble), and NDESCBIT for background atmosphere. Never promise the player an interactable noun that isn't there — it breaks trust in the parser.
 3. Author object text to support puzzle affordances.
 4. Author NPC behavior scope and conversation patterns (ASK/TELL/GIVE/SHOW).
 5. Author layered hints (attention, direction, action, command).
@@ -19,18 +19,271 @@ Write player-facing text and interactions that teach play and maintain tone.
 10. Ensure major objects act as more than props (tool, clue, world detail, joke, risk, trophy, or memory marker).
 11. Give key NPCs behavior loops (move, block, steal, help, react, change state), not only static dialogue.
 12. **Player identity belongs in SYNOPSIS.md/DESIGN.md, not in PLAYER object LDESC** — Infocom never explicitly states who the player is in game text.
+13. For every actionable compound noun used in prose, choose and record a canonical command plus natural variants (for example `reading desk`, `reading-desk`, `desk`). Make the ZIL vocabulary support what the prose teaches.
+14. Write NPC topic rows as executable commands (`ASK HUDSON ABOUT KEY`), with listener, topic noun, response, state change, repeat response, and where the listener is accessible.
 
 ## Outputs
 - Draft room and object prose set
 - NPC topic/reaction matrix
 - Hint tiers per puzzle
 
+## Artistic Quality: Good vs. Bad Patterns
+
+These patterns are drawn from a direct comparison between Zork III (infocom/zork3/) and Blackwood Horror (books/blackwood-horror/). Each section shows a concrete weakness found in Blackwood, the Zork III counterexample, and the rule to follow.
+
+### 1. Prose: Show, Don't Tell the Mood
+
+**BAD (Blackwood — `dungeon.zil:54`):**
+> "The air here is thick with an oppressive dread."
+
+Telling the player what to feel. The word "dread" is a conclusion, not a sensation. Repeated across multiple rooms ("reeks of decay," "feels wrong," "oppressive dread"), this numbs the player — if every room "feels wrong," no room truly does.
+
+**BAD (Blackwood — `dungeon.zil:33`):**
+> "The entrance hall reeks of mildew and decay."
+
+Formulaic gothic-horror signifiers reappear across rooms: "reek of mildew," "hollow eye sockets," "gaping mouths," "rotting." The vocabulary narrows to a grim checklist instead of building a specific place.
+
+**GOOD (Zork III — `3actions.zil:2104-2108`):**
+> "Mighty stalagmites form crystalline-encrusted rock formations. Phosphorescent mosses, fed by a trickle of water from above, make the crystals glow and sparkle with every color of the rainbow."
+
+Concrete sensory details (phosphorescent moss, trickling water, sparkling crystals). The wonder is earned through observation, not stated. The player *feels* awe because the description paints it — it never says "this room is beautiful."
+
+**GOOD (Zork III — `3dungeon.zil:550-563`):**
+> "A wide stone channel steeply descends into the room from the south. It is covered with slippery moss and lichen."
+
+Spatially precise, texturally rich. "Slippery moss and lichen" implies danger, age, and dampness without ever saying "this place is creepy."
+
+**Rule:** Every room description must contain at least one concrete sensory detail (sight, sound, smell, texture, temperature). Never use emotion-label adjectives ("dread," "ominous," "creepy," "wrong") as a substitute for description. If you need to remove the mood word and the room still evokes it, you wrote well.
+
+### 2. Atmosphere: Systems, Not Backdrops
+
+**BAD (Blackwood — `actions.zil:854`):**
+> "Distant footsteps echo from somewhere above you."
+
+Clock-driven flavor text that fires on a timer. It plays regardless of game state, never changes content, and the player cannot investigate, interact with, or do anything about it. After the third repetition it becomes wallpaper.
+
+**BAD (Blackwood — `dungeon.zil:13-18`):**
+A whisper table with four fixed entries selected by PICK-ONE. None change based on game progress — the whispers are identical before and after discovering Patient-189's file, opening the chapel, or confronting the truth.
+
+**GOOD (Zork III — `3actions.zil:9-38`):**
+The SWORD glows faint blue near danger, more brightly near enemies. This is a *mechanical system* — not text telling you to feel threatened, but a game object whose state reflects actual danger. The player learns to read the sword's glow as a risk indicator. Atmosphere emerges from gameplay.
+
+**GOOD (Zork III — `3actions.zil:80-87`):**
+The lantern has a fuel system with multiple warning states: "flickering," "growing dim," "about to go out." The threat of darkness is mechanical, not atmospheric — the player can run out of light, and the fear is real because the consequence is real.
+
+**Rule:** Atmosphere must be interactive. Before writing flavor text, ask: can the player do something about this? Does it change based on game state? If the answer to both is no, either: (a) make it interactive, or (b) fire it once as FDESC discovery text and then retire it.
+
+### 3. NPCs: Characters, Not Props
+
+**BAD (Blackwood — `actions.zil:568-598`):**
+Patient-189 handles five verbs (EXAMINE, ATTACK, HELLO, RUB, GIVE). It has no dialogue, no movement, no intermediate states. It never speaks until the final text-dump win. All lore about it comes from reading files elsewhere. It is a puzzle object with ACTORBIT, not a character.
+
+**GOOD (Zork III — `3actions.zil:1380`):**
+> "I'm willing to accompany you, but not ride in your pocket!"
+
+The Dungeon Master has personality, humor, and clear behavioral rules (follows, refuses containers, won't enter the cell). He speaks, reacts to specific verbs, and his dialogue changes based on what the player has done (`3actions.zil:1446-1482` — DMISH counts collected items and selects from DM-REASONS table).
+
+**GOOD (Zork III — `3actions.zil:1789-1863`):**
+The old man in the Engravings Room is the Dungeon Master's earlier form. He starts asleep, wakes when fed waybread, reveals a secret door, and when attacked says "Not yet" before vanishing in smoke. He is one NPC with *multiple behavioral states* — sleeping, grateful, threatened, transcendent.
+
+**Rule:** Every NPC must have at least three behavioral states that the player can discover and affect. At minimum: (1) initial encounter, (2) a state changed by player action, (3) a state triggered by story progress elsewhere. Dialogue must change based on game state. An NPC with ACTORBIT that only handles EXAMINE and the win-condition verb is a prop wearing a character mask.
+
+### 4. Emotional Range: Contrast Makes Horror Hit Harder
+
+**BAD (Blackwood):**
+Every description filters through horror. The garden is "dead," the walls "reek of decay," the chapel "makes everything look like a corpse," the wallpaper is "grotesquely warped by moisture and black mold." There is not a single moment of humor, beauty, warmth, or relief in 890 lines of source.
+
+**GOOD (Zork III — `3actions.zil:73`):**
+> "Who do you think you are? Arthur?" — when you try to pull the sword from the stone.
+
+**GOOD (Zork III — `3actions.zil:2104`):**
+The Crystal Grotto's "breathtaking beauty" — a room that exists purely for wonder, amid a game of deadly puzzles and flaming pits.
+
+**GOOD (Zork III — `3dungeon.zil:690-698`):**
+The Treasury of Zork: "chests containing precious jewels, mountains of zorkmids, rare paintings, ancient statuary" — a moment of pure triumph and awe after hours of challenge.
+
+**Rule:** A horror game must have moments of beauty, humor, or warmth. Without contrast, the player desensitizes and every room feels the same. Aim for at least 3 moments outside the primary tone. The darkest room should come after the player has seen something worth protecting.
+
+### 5. Environmental Storytelling: Clues in the World, Not Files in a Drawer
+
+**BAD (Blackwood):**
+Lore is delivered through NINE text-dump objects: patient file (`actions.zil:74-77`), ledger (`629-631`), Mordecai's journal (`129-135`), observation logbook (`643-644`), medical records (`498-499`), soggy notebook (`536-537`), scattered papers (`324-326`), Mordecai's notes (`725-726`), staff photograph (`413-414`). The player learns the story by finding and reading flat text, not by observing the environment.
+
+**GOOD (Zork III — `3actions.zil:1864-1868`):**
+The runes on the Engravings Room wall show "flames, stone statues, and an old man" — a visual clue that foreshadows three upcoming challenges (the flaming pit, the Guardians, the Dungeon Master). The player decodes meaning from symbols, not from reading a document. This rewards attention without requiring a ledger.
+
+**GOOD (Zork III — `3actions.zil:1719-1724`):**
+The Dungeon Master's speech at the end references the player's actions: "You have shown kindness to the old man, and compassion toward the hooded one. You displayed patience in the puzzle and trust at the cliff." The story *recounts* what the player *did*, making them the author, not just the reader.
+
+**Rule:** Cut text-dump objects by half. Move their information into room descriptions, object examines, environmental details, and NPC dialogue. Information discovered through observation ("the straps on the operating table are worn thin at the wrists") is always stronger than information discovered through reading ("the file says the patient struggled"). The player should feel like an archaeologist, not a file clerk.
+
+### 6. Twist Delivery: Earn It, Don't Telegraph It
+
+**BAD (Blackwood):**
+The "you are Patient-189" twist is revealed explicitly at least THREE times before the chapel:
+1. Straitjacket tag (`dungeon.zil:616`): "Your name. Dated 1947."
+2. Wall scratches (`actions.zil:252`): "YOU ARE 189. YOU ALWAYS WERE."
+3. Observation logbook (`dungeon.zil:643-644`): "Memory loss total. Subject claims to be 'someone else' now."
+
+By the time the player reaches Patient-189, there is nothing left to discover. The twist is a checklist item, not a revelation.
+
+**GOOD (Zork III):**
+The Dungeon Master's identity twist is revealed gradually across three separate encounters:
+1. The old man in the Engravings Room — a seemingly helpless NPC.
+2. The dungeon door panels: "we have met before, although I may not appear as I did then" (`3actions.zil:1463-1464`).
+3. The final transformation in the Treasury — the player *becomes* the new Dungeon Master.
+
+Each encounter deepens the mystery rather than resolving it. The player pieces together the identity over hours, not paragraphs. The reveal is earned.
+
+**Rule:** A twist should be discoverable, not stated. Replace explicit reveals with clues the player must synthesize: dates that match, physical descriptions that align, behaviors that echo. The chapel confrontation should be the *first* moment the player truly understands — not the third confirmation.
+
+### 7. Endings: Interactive Resolution, Not Held-Item Check
+
+**BAD (Blackwood — `actions.zil:587-592`):**
+> "You hold out the relic. Patient 189 stills completely. You draw the serum into the syringe and step forward... inject it. The green light gutters... 'I remember... who I was.' It crumbles to ash... You're free."
+
+The player must hold 3 items and type HELLO. The relic and serum have no thematic purpose — they're *required held items* for a verb gate. Patient-189 says one line. "You're free" is the narrative equivalent of "YOU WIN." No callback to discoveries made. No choice.
+
+**GOOD (Zork III — `3actions.zil:1719-1724`):**
+> "Now that you have solved all the mysteries of the Dungeon, it is time for you to assume your rightly earned place in the scheme of things... For a moment there are two identical mages standing among the treasure, then your counterpart dissolves into a mist and disappears, a sardonic grin on his face. You begin to feel the vast powers and lore at your command and thirst for an opportunity to use them."
+
+Multi-stage climax. The Dungeon Master references specific player actions. The player is *transformed* — not just told they won. The ending opens a new future rather than closing the story.
+
+**Rule:** An ending must: (1) reference at least two specific discoveries the player made, (2) give the player a choice (even a small one), and (3) imply what comes next rather than stopping at "you win." The items required for victory should have thematic purpose — the relic should *do* something in the fiction, not just be a held-object flag check.
+
+### 8. Discovery Text: FDESC on Everything Worth Finding
+
+**BAD (Blackwood):**
+Only 4 objects have FDESC: iron boiler, shock chair, straitjacket, ancient relic. The chapel has no LDESC at all (only a dynamic action routine). The padded cell, observation deck, and most other rooms lack first-visit discovery text.
+
+**GOOD (Zork III — `3dungeon.zil:192-193`):**
+> "Nestled inside the niche is an old and dusty book."
+
+**GOOD (Zork III — `3dungeon.zil:99`):**
+> "Your old friend, the brass lantern, is at your feet."
+
+Nearly every object has a FIRST?/FDESC discovery moment. Revisiting a room after solving a puzzle often reveals new text. The player is constantly rewarded for looking.
+
+**Rule:** Every major room (15+) and every important object should have FDESC discovery text. Discovery text should only appear *once* — it creates a moment. After that, revisit text should be concise and state-aware.
+
+### 9. Parser Depth: Pronoun Resolution, GWIM, OOPS, Disambiguation
+
+**BAD (Blackwood):**
+The substrate parser is used as-is. `TAKE ALL` may not work reliably. `DROP IT` after EXAMINEing a key produces "You can't see any such thing." Mistyped words (`EXAMIN`) produce generic failure. Two objects sharing a synonym (`KEY` for both iron key and safe key) in the same room produce an unhandled error.
+
+**GOOD (The Lurking Horror — `parser.zil`):**
+- **Pronoun resolution** (`misc.zil:469`): `OBJECT-SUBSTITUTE` replaces `IT` and `HIM` with the last referenced object, tracked via `P-IT-OBJECT` and `P-HIM-OBJECT`. The `THIS-IS-IT` routine updates these references after any TELL mentioning an object.
+- **GWIM (Get What I Mean)** (`parser.zil:1089`): When the player types a verb with no object that needs one, the GWIM routine supplies a default object from context. Typing `OPEN` near a closed door auto-fills the door object.
+- **OOPS correction** (`parser.zil`): Full OOPS system with `OOPS-TABLE`, `OOPS-INBUF`, and `AGAIN-LEXV` machinery. Player can type `OOPS DOOR` to retry with the corrected word.
+- **Disambiguation** (`parser.zil:1458`): `WHICH-PRINT` handles ambiguous references with "Which X do you mean, the Y or the Z?" and `P-ACLAUSE` for follow-up clarification.
+- **Orphan merging** (`parser.zil:656`): When the player types `EXAMINE` alone, the parser prompts for a noun (`WHAT?`). On the next input, `ORPHAN-MERGE` combines the two inputs into a full command.
+- **ALL/EXCEPT** (`parser.zil`): `SNARF-OBJECTS`, `MANY-CHECK`, and 80-byte `P-PRSO`/`P-PRSI` tables support `TAKE ALL`, `DROP ALL EXCEPT THE KEY`.
+
+**Rule:** At minimum, implement pronoun resolution (`THIS-IS-IT`) and GWIM defaults for your game. These are the lowest-effort, highest-impact parser improvements. Add disambiguation when two objects in the same scope share a head noun. OOPS is aspirational but transforms how forgiving the game feels.
+
+**Implementation pattern (pronouns):**
+```zil
+<ROUTINE YOUR-OBJECT-F ()
+    <COND (<VERB? EXAMINE>
+           <TELL "Description text here." CR>
+           <THIS-IS-IT ,YOUR-OBJECT>
+           <RTRUE>)>>
+```
+
+**Implementation pattern (GWIM for TAKE):**
+```zil
+<ROUTINE V-TAKE ()
+    <COND (<NOT ,PRSO>
+           ; player typed TAKE with no object
+           <COND (<SET ,PRSO <GWIM-DEFAULT ,HERE>>
+                  <TELL "(the " D ,PRSO ")" CR>
+                  <MOVE ,PRSO ,WINNER>)
+                 (T
+                  <TELL "What do you want to take?" CR>)>
+           <RTRUE>)>>
+```
+
+### 10. NPC Dialogue Trees: Back-and-Forth Conversation
+
+**BAD (Blackwood — `actions.zil:522-726`):**
+Patient-189 handles five verbs with single-shot responses. `ASK PATIENT ABOUT SERUM` produces the same text regardless of what the player already knows or has done. There is no follow-up, no branching dialogue, no way to drill into a topic. The NPC has exactly one line per verb per game state.
+
+**GOOD (The Lurking Horror — `hacker.zil`):**
+The hacker has a full dialogue tree supporting `TELL HACKER ABOUT` on 12+ topics (KEYS, STUDENTS, THE PROGRAM, LOVECRAFT, CHINESE FOOD, THE MASTER KEY, YOURSELF, etc.). Each topic has first-visit text, revisit text, and text that changes based on whether the player has already done related actions (e.g., the Chinese food topic changes after the player heats the food).
+
+**GOOD (Limehouse Killings — `actions.zil`):**
+NPCs have topic objects indexed by `PRSI`. Each topic checks whether it's been discussed before, whether prerequisite evidence has been found, and whether the NPC is in the right state. The response matrix is testable via parser commands.
+
+**Rule:** Each NPC must have at least 3 topics that change based on game state. Responses should be: (1) first time asked, (2) asked again without progress, (3) asked again after related progress elsewhere. Use GLOBAL flags per topic to track whether it's been broached. The player should feel like they're having a conversation, not triggering a vending machine.
+
+**Implementation pattern:**
+```zil
+<GLOBAL DISCUSSED-SERUM <>>
+<GLOBAL DISCUSSED-MORDECAI <>>
+
+<ROUTINE PATIENT-189-F ()
+    <COND (<VERB? TELL>
+           <COND (<EQUAL? ,PRSI ,SERUM-TOPIC>
+                  <COND (,DISCUSSED-SERUM
+                         <TELL "Patient 189 turns away. It has nothing more to say about the serum." CR>)
+                        (,SERUM-FOUND
+                         <TELL "Its eyes fix on the serum vial in your hand. A sound escapes its throat — almost a word." CR>
+                         <SETG DISCUSSED-SERUM T>)
+                        (T
+                         <TELL "Patient 189 tilts its head. It does not understand the word 'serum.'" CR>)>)
+                 (<EQUAL? ,PRSI ,MORDECAI-TOPIC>
+                  <COND (,DISCUSSED-MORDECAI
+                         <TELL "It only stares." CR>)
+                        (T
+                         <TELL "At the name 'Mordecai,' Patient 189 flinches. Something green flickers deep in its eyes." CR>
+                         <SETG DISCUSSED-MORDECAI T>)>)>
+           <RTRUE>)>>
+```
+
+### 11. Unique Death Text: Every Death a Discovery Moment
+
+**BAD (Blackwood):**
+There is no death system. The game has exactly one ending (victory). No environmental hazard can kill the player. The cold, the dark, the Patient — none are dangerous. This removes all tension from exploration.
+
+**GOOD (The Lurking Horror):**
+Every death has unique, characterful text:
+- Freezing: "You are suffused with a warm, blissful numbness. It is marred only by the knowledge that before you wake again, you will die."
+- Electrocution: "Four thousand volts of electricity course through your body! The result is shocking."
+- Slime: "The slime engulfs your nose! You cough, choke, and begin to suffocate!"
+- The FROB: "The creature leaps, a mountain falling on you, and the darkness swallows you, never to brighten again."
+- The flier: "Something gnawing on your <random body part> thinks it's pretty wonderful, or at least fairly tasty."
+- Generic: Unique text when eaten, dissolved, crushed, or absorbed.
+
+**Rule:** Every distinct death type must have unique text that reveals something about the world or the monster. Generic "You have died" is never acceptable. Death text is a writing opportunity — it's the last thing the player reads before restoring, and it should be memorable. Aim for: (1) a sensory detail the player hasn't seen before, (2) a hint about what killed them, (3) tonal consistency with the game. Add at least 3 death states to any horror game.
+
+### 12. Tonal Range: Contrast Makes Every Mood Hit Harder
+
+**EXPANDED FROM SECTION 4:**
+
+A horror game without contrast desensitizes the player. The Lurking Horror proves this by shifting between four distinct tones:
+
+- **Academic comedy**: "You miss. (Now you know why few technical schools make it to the Rose Bowl.)"
+- **Wonder**: The Yuggoth sequence — alien, beautiful, cosmic.
+- **Body horror**: The slime, the mass, the hand in the tub.
+- **Dark humor**: The hacker's "Mumble. Frotz." dialogue, the dark flier's taste for your body parts.
+
+Blackwood has exactly one tone (grim gothic) across 890 lines of source. No jokes, no beauty, no warmth.
+
+**Rule:** Divide your game into thirds. In the first third, the player should encounter at least ONE thing that is beautiful, ONE thing that is funny, and ONE thing that is warm (even if hollow). The horror that follows will hit harder because the player has something to contrast it against. Use this checklist:
+- [ ] One beautiful room or object description
+- [ ] One moment of humor (dark comedy counts)
+- [ ] One moment of warmth or humanity (a letter, a photograph, a memory)
+- [ ] No more than 2 uses of "dread," "ominous," or "feels wrong" in the entire game
+- [ ] At least 3 concrete sensory details per room (sight, sound, smell, texture, temperature) that replace emotion-label adjectives
+
 ## Acceptance Checks
 - Tone remains consistent.
 - Room prose implies meaningful actions.
 - Wrong-but-reasonable attempts are informative.
 - Revisited text is concise and state-aware.
 - NPC interactions produce observable world or puzzle consequences.
+- Every emphasized clue noun and every noun used in a hint resolves through the parser exactly as written.
+- Conversation topics are testable parser objects/words, not documentation-only labels.
 
 ## Primary Source Coverage
 - `ZIL_TEXT_ADVENTURE_AGENTS.md`: sections 6, 7, 11, 14
diff --git a/skills/05_zil_implementation_reference.md b/skills/05_zil_implementation_reference.md
index 773a0da..0d253cd 100644
--- a/skills/05_zil_implementation_reference.md
+++ b/skills/05_zil_implementation_reference.md
@@ -9,19 +9,24 @@ Implement game logic in ZIL with clean split between world data and routines.
 ## Required Actions
 1. Implement `dungeon.zil` for rooms, objects, and declarative world data.
 2. Implement `actions.zil` for routines, daemon/clock behavior, and `GO`.
-3. Implement `walkthrough.zil` as executable test entry file.
+3. Implement an executable walkthrough entry. If using `walkthrough.zil` with `run-zil-test.lua`, it must load prerequisites and expose `RUN_TEST`; also maintain a parser-driven cross-process walkthrough for release confidence.
 4. Use the engine include chain consistently.
 5. Apply advanced ZIL patterns where needed (GLOBAL objects, PSEUDO, FDESC/LDESC, PER exits, dynamic descriptions, transformations, daemons).
+6. Implement one playable vertical slice at a time. After each room, object, puzzle, or NPC interaction, play its exact transcript through `llm.lua` before adding the next slice.
+7. Grow a parser-driven walkthrough test alongside implementation; do not rely only on routines invoked directly with `PERFORM`.
 
 ## Outputs
 - `dungeon.zil`
 - `actions.zil`
 - `walkthrough.zil`
+- Parser-driven walkthrough test under `tests/` when the adventure is playable through `llm.lua`
 
 ## Acceptance Checks
 - Parser/object/room routines compile and run.
 - Puzzle state changes are explicit and traceable.
 - Dynamic text and clock events are deterministic enough to test.
+- Exact transcript noun phrases parse before and after a save/reload boundary.
+- Each completed slice is reachable from a fresh game and remains covered by the growing walkthrough.
 
 ## Design-Critical Implementation Reminders
 
@@ -41,9 +46,9 @@ These are implementation-level constraints that protect the intended Infocom-sty
 
 These rules are derived from real bugs found when running book content through the zilscript engine. Violating them will cause parse errors, broken compilation, or broken gameplay.
 
-### 0. NEVER redefine V-LOOK or SYNTAX — they come from the substrate
+### 0. Never redefine V-LOOK or standard SYNTAX
 
-The substrate (`infocom/zork1/`) provides V-LOOK and all SYNTAX definitions. **Do not add your own.**
+The substrate (`infocom/zork1/`) provides V-LOOK and the standard SYNTAX definitions. **Do not redefine those.**
 
 **V-LOOK is provided by the substrate.** It reads `P?LDESC` from the current room and prints exits. Your `GO` routine calls it automatically. If you redefine V-LOOK (as Limehouse Killings did), you will break room descriptions.
 
@@ -67,7 +72,15 @@ The substrate (`infocom/zork1/`) provides V-LOOK and all SYNTAX definitions. **D
     <MAIN-LOOP>>
 ```
 
-**SYNTAX is provided by the substrate.** All standard verbs (LOOK, EXAMINE, TAKE, DROP, OPEN, etc.) are already defined in `infocom/zork1/syntax.zil`. Your `dungeon.zil` should NOT contain any `<SYNTAX ...>` forms.
+**Standard SYNTAX is provided by the substrate.** LOOK, EXAMINE, TAKE, DROP, OPEN, and other standard verbs already exist in `infocom/zork1/syntax.zil`. Your `dungeon.zil` must not contain `<SYNTAX ...>` forms and `actions.zil` must not redefine standard entries.
+
+A genuinely new verb still needs one narrow syntax declaration in `actions.zil`, after its action routine is available:
+
+```zil
+<SYNTAX ACCUSE OBJECT (FIND ACTORBIT) (IN-ROOM) = V-ACCUSE>
+```
+
+After adding custom syntax, test the typed command through the parser. Calling `<PERFORM ,V?ACCUSE ...>` proves the routine, not the vocabulary or syntax.
 
 **Wrong** (Limehouse Killings bug — adds SYNTAX that conflicts):
 ```zil
@@ -85,7 +98,170 @@ The substrate (`infocom/zork1/`) provides V-LOOK and all SYNTAX definitions. **D
 <OBJECT ...>
 ```
 
-**Detection:** If your `dungeon.zil` contains `<SYNTAX` anywhere, remove it. If your `actions.zil` contains `<ROUTINE V-LOOK`, remove it.
+**Detection:** If `dungeon.zil` contains `<SYNTAX`, remove it. If `actions.zil` contains `<ROUTINE V-LOOK`, remove it. Review every `actions.zil` SYNTAX entry and keep only custom verbs absent from the substrate.
+
+### 0a. Make parser vocabulary explicit
+
+Object IDs and `DESC` strings are not automatically usable nouns. Every player-reachable object needs explicit vocabulary matching the transcript:
+
+```zil
+<OBJECT TORN-PAGE
+      (IN LIBRARY)
+      (DESC "torn page")
+      (SYNONYM PAGE FRAGMENT TORN-PAGE)
+      (ADJECTIVE TORN)
+      (FLAGS TAKEBIT READBIT)>
+```
+
+Rules:
+
+- Put head nouns and alternate nouns in `SYNONYM`.
+- Put modifiers in `ADJECTIVE`.
+- If a transcript types a hyphenated compound, include that exact spelling as a synonym.
+- Add canonical nouns even when they match the object ID (`FOXGLOVE` still needs `(SYNONYM FOXGLOVE ...)`).
+- Test both the documented form and a natural spaced variant.
+- Resolve same-room noun collisions with adjectives or different nouns.
+- If FDESC or LDESC mentions a concrete noun a player might type (e.g., "leather roll", "brass lantern"), that word must resolve to the described object or another object in scope. The text the player reads IS the parser vocabulary contract. `scripts/check-vocab.lua` verifies the objective subset—that each printed `DESC` contains a registered synonym—but prose nouns still require transcript playtesting and human review.
+- When FDESC describes an object inside a container (e.g., "A leather roll lies in the open drawer, its contents glinting steel"), create a separate container object for the described item. Don't put the description noun as a synonym on the contained object — that breaks the containment hierarchy.
+- Every concrete noun printed by an ACTION routine's TELL must correspond to an actual in-game object. If `TRUNK-F` EXAMINE says "contains a letter", a `LETTER` object must exist inside the `TRUNK` with matching SYNONYM. Players type exactly what they read — broken promises destroy parser trust.
+- Don't write manual EXAMINE handlers for containers — the Zork engine handles it automatically via `V-EXAMINE` → `V-LOOK-INSIDE` → `PRINT-CONT`. It prints "The X contains: Y, Z" when open, "The X is closed" when closed, and "The X is empty" when empty. Use `(TEXT ...)` for custom description only when you need flavor text that replaces the default listing. Place contained objects inside the container with `(IN CONTAINER)` so they appear in the automatic listing.
+
+### 0b. Make containers reveal reachable contents
+
+A printed “open” response is not enough. The world model must change:
+
+```zil
+<OBJECT LOCKED-BOX
+      (IN STUDY)
+      (SYNONYM BOX)
+      (ADJECTIVE LOCKED)
+      (FLAGS CONTBIT SEARCHBIT)
+      (ACTION LOCKED-BOX-F)>
+
+; in successful OPEN/UNLOCK branch
+<FSET ,LOCKED-BOX ,OPENBIT>
+<MOVE ,BANK-STATEMENT ,LOCKED-BOX>
+```
+
+Immediately test `OPEN BOX`, then `TAKE STATEMENT` in the next `llm.lua` process. This catches both scope and save-state errors.
+
+### 0c. Guard one-time story progress
+
+If TAKE, READ, and EXAMINE can all reveal a clue, route them through one guarded transition:
+
+```zil
+<COND (<NOT ,LETTER-FOUND>
+       <SETG LETTER-FOUND T>
+       <SETG EVIDENCE-FOUND <+ ,EVIDENCE-FOUND 1>>)>
+```
+
+Test the verbs repeatedly and in different orders. Progress must increment once.
+
+### 0d. Implement ASK/TELL topics for this substrate
+
+The zork1 substrate treats `ASK` as a parser synonym of the `TELL` action; it does not create a separate `V?ASK` action. `ASK ACTOR ABOUT TOPIC` and `TELL ACTOR ABOUT TOPIC` both reach the actor with `PRSA = V?TELL`, the actor in `PRSO`, and the topic in `PRSI`. Actor routines must therefore test `TELL` and inspect `PRSI`:
+
+```zil
+<COND (<VERB? TELL>
+       <COND (<EQUAL? ,PRSI ,KEY-TOPIC>
+              ... )>)>
+```
+
+Do not write `<VERB? ASK TELL>` here: `V?ASK` may be undefined, and placing it first can prevent the valid `TELL` comparison from being reached. Do not inspect `PRSO` for the topic; that is the actor. Define reusable topic objects in `GLOBAL-OBJECTS` so topic words resolve when the referenced clue/person is elsewhere. Guard interview counters, and ensure an NPC needed for a later command is physically or globally accessible at that point.
+
+### 0e. Never redispatch the same action from its default verb routine
+
+`PERFORM` already dispatches an action to the indirect object, direct object, and then the verb default. A default routine must produce the fallback; it must not call `PERFORM` with its own action again:
+
+```zil
+; Wrong: recurses when no object routine handles TELL.
+<ROUTINE V-TELL ()
+    <PERFORM ,V?TELL ,PRSO ,PRSI>>
+
+; Right: normally inherit the substrate's V-TELL. For a new verb, provide
+; a terminal fallback instead of redispatching it.
+<ROUTINE V-SHOW ()
+    <TELL "The " D ,PRSI " doesn't seem interested." CR>>
+```
+
+Before defining any `V-*` routine, search the substrate's `verbs.zil`. Override only when the game genuinely needs a different default, and add a command-level test where no object handler accepts the action.
+
+### 0f. Audit parser registration separately from action routines
+
+A `V-USE`, `V-SHOW`, or `V-HINTS` routine does not make the typed verb parse. Search `infocom/zork1/syntax.zil`; if the verb is absent, add one narrow book-specific `SYNTAX` declaration and exercise the literal command through `llm.lua`.
+
+The substrate may intentionally map a surface verb to a canonical action. In Zork I syntax, `PULL` maps to `V-MOVE`, so a pullable object's action routine handles `<VERB? MOVE>`; duplicating the global `PULL` syntax in a book is unnecessary and can create ambiguous grammar. Record these mappings in the verb × object matrix.
+
+### 0g. Keep puzzle instructions, implementation, and tests executable and identical
+
+For every ordered puzzle, maintain one canonical sequence and copy it exactly into the clue text, hints, design notes, and parser-driven walkthrough. Every named step must exist as an object or action. A clue that says “rainbow order” cannot mention colors for which no interactive books exist, and the walkthrough must not encode a different order merely because it passes.
+
+### 0h. Treat titles as modifiers in multiword NPC names
+
+Put the stable head noun in `SYNONYM` and titles in `ADJECTIVE`:
+
+```zil
+(SYNONYM HUDSON BUTLER MR-HUDSON)
+(ADJECTIVE MR MISTER)
+```
+
+This intentionally supports both `HUDSON` and `MISTER HUDSON`. Test the full natural form; do not move `MISTER` into `SYNONYM`, where it becomes a competing head noun.
+
+### 0i. Represent physical world state with objects, not flag-only scenery
+
+If the prose names a physical thing the player could reasonably manipulate, that thing must exist in the object tree. Doors, windows, drawers, switches, ropes, vehicles, gates, and containers are not merely conditions on room exits.
+
+**Wrong — the prose promises a door, but only a Boolean exists:**
+
+```zil
+<GLOBAL STUDY-UNLOCKED <>>
+
+<ROOM ENTRANCE-HALL
+      (LDESC "A door to the south stands locked.")
+      (SOUTH TO STUDY IF STUDY-UNLOCKED)>
+
+; Somewhere else:
+<SETG STUDY-UNLOCKED T>
+```
+
+This shortcut lets movement change, but there is no door for `EXAMINE DOOR`, `OPEN DOOR`, `UNLOCK DOOR WITH KEY`, `CLOSE DOOR`, or pronoun resolution. Prose, parser scope, generic verbs, and navigation can contradict one another.
+
+**Right — create the door and let its object state control the exit:**
+
+```zil
+<GLOBAL STUDY-UNLOCKED <>> ; supplements the object: locked vs merely closed
+
+<OBJECT STUDY-DOOR
+      (IN LOCAL-GLOBALS)
+      (DESC "study door")
+      (SYNONYM DOOR)
+      (ADJECTIVE STUDY OAK)
+      (FLAGS DOORBIT NDESCBIT)
+      (ACTION STUDY-DOOR-F)>
+
+<ROOM ENTRANCE-HALL
+      (SOUTH TO STUDY IF STUDY-DOOR IS OPEN
+             ELSE "The study door is closed.")
+      (GLOBAL STUDY-DOOR)>
+
+<ROOM STUDY
+      (NORTH TO ENTRANCE-HALL IF STUDY-DOOR IS OPEN
+             ELSE "The study door is closed.")
+      (GLOBAL STUDY-DOOR)>
+```
+
+The door routine should handle `EXAMINE`, `OPEN`, and `UNLOCK`, validate the key or lockpick, set `STUDY-UNLOCKED` when the lock is released, and set/clear `OPENBIT` when the door opens or closes. The exit reads `OPENBIT`; the supplementary global answers the separate question "is it locked?"
+
+Use globals without objects for genuinely abstract facts such as `RIDDLE-SOLVED`, `NPC-TRUSTS-PLAYER`, or a one-time scoring guard. Do not use them to erase physical entities from the simulated world.
+
+Do not leave mutable door state in a static room `LDESC`:
+
+```zil
+; Wrong: this remains "locked" after the door opens.
+(LDESC "A door to the south stands locked.")
+```
+
+Follow Zork I's `EAST-HOUSE` pattern instead: give the room an ACTION routine, handle `M-LOOK`, and compose the complete room description inline from `OPENBIT` and any supplementary lock state. Keep the door's own `EXAMINE`, `OPEN`, `CLOSE`, and `UNLOCK` behavior in its object ACTION routine, just as Zork I keeps `EAST-HOUSE` separate from `KITCHEN-WINDOW-F`.
 
 ### 1. Don't embed item descriptions in room descriptions — let items describe themselves
 
@@ -121,9 +297,11 @@ hangs heavy with the memory of violence.")
     (FLAGS NDESCBIT)>
 ```
 
-**Why**: When items describe themselves, their descriptions can change with game state. A locked box can say "locked" or "open" depending on a flag. A window can say "slightly ajar" or "open" depending on whether the player opened it. If the room description hardcodes the state, you need an ACTION routine just to vary one sentence.
+**Why**: When items describe themselves, their descriptions can change with game state. A locked box can say "locked" or "open" depending on a flag. A window can say "slightly ajar" or "open" depending on whether the player opened it. If the room description hardcodes the state, you need an ACTION routine just to vary one sentence. Most critically: if the room LDESC mentions a "door" but no door object exists, the player will type `OPEN DOOR` and get "There's no door here" — a broken promise that undermines trust in the parser.
+
+**The door rule**: Every "door" noun in room text must correspond to an object with `SYNONYM DOOR` and an ACTION handler (even if it's always open). If you don't want a door object, say "doorway", "passage", or "opening" instead. Never use the word "door" in a room description without providing a door object.
 
-**Detection**: Search your `LDESC` strings for object names that appear as objects elsewhere. If a room says "a desk" and there's an OBJECT DESK, the desk should describe itself.
+**Detection**: Search your `LDESC` strings for object names that appear as objects elsewhere. If a room says "a desk" and there's an OBJECT DESK, the desk should describe itself. Search for the word "door" — every occurrence must have a corresponding door object. Search for any concrete noun (chair, table, bed, window) that a player might `EXAMINE`; if it exists, ensure the parser can find it.
 
 ### 2. Every `<TELL>` must close with `>` before the next form
 
@@ -177,26 +355,15 @@ GO must set up initial state:
 
 **Detection**: Game loads without errors but prints "Failed to start game: GO() not defined or failed."
 
-### 4. Simplified SYNTAX uses `= ACTION`, not `ACTION` keyword
+### 4. Custom SYNTAX uses `= V-ROUTINE`
 
-The limehouse/blackwood books use a simplified SYNTAX format. Note the differences:
+Only add syntax for verbs absent from the substrate. Use `= V-ROUTINE` at the end and include scope constraints when appropriate:
 
-**Simplified format** (books):
 ```zil
-<SYNTAX EXAMINE OBJECT = V-EXAMINE>
-<SYNTAX ASK OBJECT ABOUT TEXT = V-ASK>
+<SYNTAX ACCUSE OBJECT (FIND ACTORBIT) (IN-ROOM) = V-ACCUSE>
 ```
 
-**Infocom format** (zork1/2/3):
-```zil
-<SYNTAX EXAMINE OBJECT (MANY) = V-EXAMINE>
-<SYNTAX ATTACK OBJECT (FIND ACTORBIT) (ON-GROUND IN-ROOM) = V-ATTACK>
-```
-
-Key rules for the simplified format:
-- `= V-ROUTINE` at the end (not `ACTION V?ROUTINE`)
-- Modifier keywords like `TEXT` before `=` are supported
-- Use hyphenated names: `V-GO-NORTH` (not `V?GO-NORTH`)
+Do not copy standard LOOK/EXAMINE/TAKE/ASK entries into book content. Before adding a verb, search `infocom/zork1/syntax.zil`; after adding it, test the typed command rather than only calling its routine.
 
 ### 5. Bracket balance: every `<` needs a matching `>`
 
@@ -238,3 +405,226 @@ Each book needs its own entry `.zil` file (like `blackwood-horror.zil`). Use loc
 ### 7. zork2/zork3 use different file naming conventions
 
 When referencing substrate files for zork2/zork3, note that they prefix files with `g` (globals → gglobals.zil, main → gmain.zil, clock → gclock.zil, etc.). The `try_open` function handles case-insensitive matching (`GMACROS` → `gmacros.zil`).
+
+### 8. Custom V-GO direction handlers must mirror every conditional exit
+
+If you define custom `V-GO-NORTH`, `V-GO-SOUTH`, `V-GO-EAST`, etc. routines in `actions.zil`, those routines completely replace the room's exit-table walk for that direction. Every conditional exit declared on a room (`IF CIPHER-SOLVED`, `IF DOOR IS OPEN`) **must** be replicated inside the matching V-GO routine, or the condition will be silently bypassed.
+
+**Wrong** (library south exit ignores cipher):
+```zil
+<ROUTINE V-GO-SOUTH ()
+    <COND ...
+          (<==? ,HERE ,LIBRARY>
+           <SETG HERE ,SECRET-PASSAGE>       ; no CIPHER-SOLVED check!
+           <TELL "You enter the secret passage." CR>)>>
+```
+
+**Right** (mirrors the room's conditional exit):
+```zil
+<ROUTINE V-GO-SOUTH ()
+    <COND ...
+          (<==? ,HERE ,LIBRARY>
+           <COND (,CIPHER-SOLVED
+                  <SETG HERE ,SECRET-PASSAGE>
+                  <TELL "You enter the secret passage." CR>)
+                 (T
+                  <TELL "You can't go that way." CR>)>)>>
+```
+
+Also ensure every room that HAS an exit for a given direction appears in the V-GO routine. Missing a room entirely means the direction silently fails there, even when the exit should be valid.
+
+**Prevention**: For every conditional room exit, search `actions.zil` for the corresponding direction routine and verify the condition is checked. If no V-GO routine exists for that direction, the substrate's `V-WALK` handles exit-table conditions correctly — only define V-GO routines for directions that genuinely need custom behavior beyond what the room's (TO ... IF ...) declarations already provide.
+
+### 9. NPCs and named objects need generous, overlap-tested vocabulary
+
+Players will try many forms of a name. Give every NPC:
+- Surname and title as `SYNONYM`: `(SYNONYM HUDSON BUTLER MR-HUDSON)`
+- Role-based nouns: `(SYNONYM DOCTOR)` for Dr. Moriarty, `(SYNONYM INSPECTOR LESTRADE OFFICER DETECTIVE POLICE)` for Inspector Lestrade
+- Role nouns as `ADJECTIVE` for common title forms: `(ADJECTIVE DR DOCTOR)` so both "doctor moriarty" and "dr moriarty" parse
+- `ARTICLEBIT` on characters where "the X" is natural English: inspector, doctor, butler — not for proper names alone (Mr. Hudson)
+
+For hyphenated object names (wine-cabinet, blood-stained-knife), add the hyphenated form as a `SYNONYM` **and** ensure the individual words exist as adjective+noun:
+```zil
+<OBJECT WINE-CABINET
+      (SYNONYM CABINET WINE-CABINET)
+      (ADJECTIVE WINE)>
+```
+
+Test every transcript noun phrase in the parser before accepting the slice. Don't assume the substrate inherits every needed verb — search `infocom/zork1/syntax.zil` and if a promised verb (ASK, SEARCH, LOOK AT) is missing, add one narrow `SYNTAX` entry in `actions.zil`.
+
+### 10. No two objects in overlapping scope may share a DESC
+
+When the parser encounters `TAKE LETTER` and two objects have `DESC "letter"`, it enters disambiguation. With identical synonyms and no distinguishing adjectives, this can loop. Give every object a **unique** `DESC` text, or ensure they are never in scope together, or use distinct `ADJECTIVE` so the parser can tell them apart:
+
+```zil
+; Study letter
+<OBJECT DEAD-LETTER
+      (DESC "unsent letter")        ; unique DESC
+      (SYNONYM LETTER)>
+
+; Trunk letter — never in scope at the same time as DEAD-LETTER,
+; but still distinct so "letter" alone doesn't trip disambiguation
+<OBJECT TRUNK-LETTER
+      (DESC "folded note")          ; different DESC
+      (SYNONYM NOTE)
+      (ADJECTIVE FOLDED)>
+```
+
+**Detection**: Grep for duplicate `(DESC "..."` strings across objects and for overlapping `SYNONYM` sets. Also check room `GLOBAL` lists — an object placed in a room's `GLOBAL` appears there as a pseudo-object even if its physical `(IN ...)` is elsewhere. Don't add kitchen `POTS` to the greenhouse's `GLOBAL` list.
+
+### 11. Dynamic room descriptions must faithfully reflect object state
+
+Room ACTION routines that compose a live description from object state must check the correct flags and use accurate language:
+
+```zil
+<ROUTINE KITCHEN-FCN (RARG)
+    <COND (<EQUAL? .RARG ,M-LOOK>
+           ...
+           <COND (<FSET? ,DRAWER ,OPENBIT>
+                  <TELL " The drawer stands open, a leather roll inside.">)
+                 (T
+                  <TELL " A drawer in the counter is closed.">)>)>>
+```
+
+Don't say "slightly ajar" for a closed drawer, "stands open" for a closed door, or "now unlocked" for a door that was unlocked three turns ago. Every state-dependent phrase must be paired with the exact flag check that produces it. When in doubt, the player's `EXAMINE` of the object tells the truth — make sure the room description doesn't contradict it.
+
+### 12. NPC-given items must not be freely TAKE-able before the NPC offers them
+
+When an NPC carries an item meant to be given in conversation, guard the item's `TAKE` handler against early acquisition:
+
+```zil
+<ROUTINE KEYRING-F ()
+    <COND (<VERB? TAKE>
+           <COND (,HUDSON-KEY-GIVEN
+                  <TELL "You take the keyring." CR>
+                  <MOVE ,KEYRING ,WINNER>)
+                 (<IN? ,KEYRING ,WINNER>
+                  <TELL "You already have the keyring." CR>)
+                 (T
+                  <TELL "That's not yours. Ask Mr. Hudson for it." CR>)>)>>
+```
+
+Otherwise the player can `TAKE KEYRING` directly from the NPC's inventory and skip the conversation gate. The item's initial `(IN MR-HUDSON)` places it inside the NPC object, but `TAKEBIT` on the item allows the parser to retrieve it from containers whose `SEARCHBIT` or `OPENBIT` grant access.
+
+### 13. Pronoun resolution with THIS-IS-IT
+
+The substrate's `THIS-IS-IT` macro binds `IT` to an object for subsequent commands. After any TELL that names an object, call `THIS-IS-IT` so the player can refer to it by pronoun:
+
+```zil
+<ROUTINE LENS-F ()
+    <COND (<VERB? EXAMINE>
+           <TELL "The Fresnel lens is magnificent but dark." CR>
+           <THIS-IS-IT ,FRESNEL-LENS>   ; now "EXAMINE IT" or "TAKE IT" works
+           <RTRUE>)>>
+```
+
+Apply this to every object with an ACTION routine that produces text naming the object. The most important objects to bind are: the current room's most visible feature, the last NPC spoken to, the last object examined, the last object taken or dropped.
+
+**Implementation notes:**
+- `THIS-IS-IT` sets the substrate's internal `P-IT-OBJECT` variable.
+- The substrate also supports `P-HIM-OBJECT` for ACTORBIT NPCs. After TELL about an NPC, call `THIS-IS-IT` with the NPC object and it will also set `P-HIM-OBJECT`.
+- Pronoun binding survives across turns but not across save/restore cycles in the current substrate.
+
+### 14. Autonomous NPC movement with clock daemons
+
+An NPC that moves independently creates a living world. The pattern: define a clock daemon that evaluates the NPC's current location and picks a valid adjacent room.
+
+```zil
+<GLOBAL GUARD-DIRECTION <>>  ; which way the guard is currently patrolling
+
+<ROUTINE I-GUARD-PATROL ()
+    <COND (<EQUAL? <LOC ,GUARD> ,ENTRANCE-HALL>
+           <MOVE ,GUARD ,CORRIDOR>
+           <SETG GUARD-DIRECTION 'FURTHER>)
+          (<EQUAL? <LOC ,GUARD> ,CORRIDOR>
+           <COND (<==? ,GUARD-DIRECTION 'FURTHER>
+                  <MOVE ,GUARD ,GUARD-ROOM>
+                  <SETG GUARD-DIRECTION 'RETURN>)
+                 (T
+                  <MOVE ,GUARD ,ENTRANCE-HALL>
+                  <SETG GUARD-DIRECTION 'OUT>)>)
+          (<EQUAL? <LOC ,GUARD> ,GUARD-ROOM>
+           <MOVE ,GUARD ,CORRIDOR>
+           <SETG GUARD-DIRECTION 'RETURN>)>
+    <RTRUE>>
+```
+
+Queue at interval 3-5 in GO. The guard moves every few turns, changing which rooms are occupied or dangerous.
+
+**Key considerations:**
+- An NPC's action routine must handle the case where the player is in the same room when the NPC arrives. Use M-ENTER for room entry handlers.
+- Guard NPC movement against the `GAME-WON` flag so patrols stop after the game ends.
+- If multiple NPCs patrol, ensure they don't occupy the same room simultaneously, or handle the overlap case.
+- Test: the player waits in a room and the NPC eventually arrives or passes through.
+
+### 15. Mechanical stateful clock daemons
+
+Atmosphere-only clock daemons (whispers, creaks) become wallpaper. Mechanical daemons that track numerical state create real gameplay decisions.
+
+**Pattern 1 — Battery drain (resource management):**
+
+```zil
+<GLOBAL FLASHLIGHT-CHARGE 100>  ; starts full
+
+<ROUTINE I-FLASHLIGHT ()
+    <COND (<AND <FSET? ,FLASHLIGHT ,ONBIT>
+                <IN? ,FLASHLIGHT ,WINNER>>
+           <SETG FLASHLIGHT-CHARGE <- ,FLASHLIGHT-CHARGE 1>>
+           <COND (<EQUAL? ,FLASHLIGHT-CHARGE 75>
+                  <TELL "Your flashlight flickers slightly." CR>)
+                 (<EQUAL? ,FLASHLIGHT-CHARGE 50>
+                  <TELL "The flashlight beam grows noticeably dimmer." CR>)
+                 (<EQUAL? ,FLASHLIGHT-CHARGE 25>
+                  <TELL "The flashlight casts only a faint yellow glow." CR>)
+                 (<EQUAL? ,FLASHLIGHT-CHARGE 0>
+                  <TELL "Your flashlight sputters and dies." CR>
+                  <FCLEAR ,FLASHLIGHT ,ONBIT>)>)>
+    <RTRUE>>
+```
+
+**Pattern 2 — Environmental exposure (cumulative hazard):**
+
+```zil
+<GLOBAL COLD-EXPOSURE 0>
+
+<ROUTINE I-FREEZE-CHECK ()
+    <COND (<EQUAL? ,HERE ,COLD-ROOM ,FREEZER ,ICE-CAVE>
+           <SETG COLD-EXPOSURE <+ ,COLD-EXPOSURE 1>>
+           <COND (<EQUAL? ,COLD-EXPOSURE 3>
+                  <TELL "You shiver. The cold is seeping through your clothes." CR>)
+                 (<EQUAL? ,COLD-EXPOSURE 6>
+                  <TELL "Your fingers are numb. Movement is getting harder." CR>
+                  <SETG PLAYER-STRENGTH <- ,PLAYER-STRENGTH 10>>)
+                 (<EQUAL? ,COLD-EXPOSURE 9>
+                  <TELL "The cold crushes the warmth from your chest. Your vision narrows." CR>)
+                 (<EQUAL? ,COLD-EXPOSURE 12>
+                  <TELL "You collapse. The cold takes you." CR>
+                  ; trigger death
+                  )>)>
+    <RTRUE>>
+```
+
+**Pattern 3 — Object state decay (temperature, freshness):**
+
+```zil
+<GLOBAL CHINESE-FOOD-TEMP 5>  ; 5 = frozen, 10 = perfect, 15 = burnt
+
+<ROUTINE I-FOOD-TEMP ()
+    <COND (<AND ,CHINESE-FOOD-HEATING
+                <EQUAL? ,HERE ,KITCHEN>>
+           <SETG CHINESE-FOOD-TEMP <+ ,CHINESE-FOOD-TEMP 1>>
+           <COND (<EQUAL? ,CHINESE-FOOD-TEMP 8>
+                  <TELL "The microwave beeps. The food is now hot." CR>
+                  <SETG CHINESE-FOOD-HEATING <>>
+                  ; tell the hacker it's ready
+                  )>)>
+    <COND (<AND <NOT ,CHINESE-FOOD-HEATING>
+                <IN? ,CHINESE-FOOD ,WINNER>
+                <G? ,CHINESE-FOOD-TEMP 0>>
+           <SETG CHINESE-FOOD-TEMP <- ,CHINESE-FOOD-TEMP 1>>
+           <COND (<EQUAL? ,CHINESE-FOOD-TEMP 2>
+                  <TELL "The Chinese food is getting cold again." CR>)>)>
+    <RTRUE>>
+```
+
+**Rule:** Every mechanical clock daemon must: (1) have visible feedback at each stage threshold, (2) stage notifications at intervals the player can notice and react to, (3) either interact with or be readable through EXAMINE on relevant objects. The player should never die or lose progress without warning. Telegraph, then escalate, then execute.
diff --git a/skills/06_testing_transcripts_and_debugging.md b/skills/06_testing_transcripts_and_debugging.md
index 1b88cd9..b6ec3cf 100644
--- a/skills/06_testing_transcripts_and_debugging.md
+++ b/skills/06_testing_transcripts_and_debugging.md
@@ -8,6 +8,7 @@ Prove completion path, catch regressions, and close parser/content gaps.
 - `TRANSCRIPT_TESTS.md`
 
 ## Required Actions
+0. Begin this loop during Stage 5 after the first playable room; Stage 6 expands and hardens it rather than starting it.
 1. Execute golden-path transcript.
 2. Execute wrong-attempt transcripts and confirm quality responses.
 3. Run room checklist commands and object checklist commands.
@@ -19,9 +20,44 @@ Prove completion path, catch regressions, and close parser/content gaps.
 9. Verify danger telegraphing appears before lethal or high-cost consequences.
 10. Add transcript cases for playful/silly inputs to validate tone-preserving parser feedback.
 11. Verify hint escalation triggers only after repeated failure, and that each tier preserves player dignity.
+12. Run the game through `llm.lua` one command per process using the same save file. This is mandatory coverage for persistence, parser vocabulary, object location, flags, counters, and NPC movement.
+13. For every new room or puzzle, run a fresh-game micro-playthrough before implementing the next slice.
+14. Promote each passing slice into an automated parser-driven walkthrough; keep exact commands synchronized with `TRANSCRIPT_TESTS.md`.
+15. Test one-time events with TAKE/READ/EXAMINE repeated and reordered; assert counters and rewards change once.
+16. Test every opened container by taking its contents in the next process invocation.
+
+## Play-As-You-Build Loop
+
+Use this cadence for each vertical slice:
+
+```bash
+SAVE=/tmp/adventure-slice.sav
+lua5.4 llm.lua --new-game --save "$SAVE" --game adventure-name
+lua5.4 llm.lua --action "go north" --save "$SAVE" --game adventure-name
+lua5.4 llm.lua --action "examine reading-desk" --save "$SAVE" --game adventure-name
+lua5.4 llm.lua --action "take torn-page" --save "$SAVE" --game adventure-name
+lua5.4 llm.lua --action "inventory" --save "$SAVE" --game adventure-name
+```
+
+Each line must succeed on its own. Check output for generic parser failures (`used the word`, `can't see`, `can't go`, unrecognized sentence), then try natural spaced/hyphenated variants and wrong order.
+
+Testing has three complementary layers:
+
+1. Direct ZIL assertions prove routines and state transitions.
+2. Focused `llm.lua` sequences prove parser and cross-process persistence.
+3. A full automated golden path proves the shipped game from fresh start to win.
+
+Do not treat direct `<PERFORM ...>` calls as a substitute for typed-command coverage.
+
+## Executable Walkthrough Contract
+
+- A module run by `run-zil-test.lua` must load its prerequisites and expose `RUN_TEST`; defining only `GO` is not a runnable test for that harness.
+- Prefer a parser-driven `tests/test_<adventure>_walkthrough.lua` for the release golden path. It should invoke `llm.lua` separately for each command, reject generic parser/scope/navigation failures, assert progress totals, and assert the win text.
+- Add a `make test-<adventure>-walkthrough` target and include it in integration testing.
 
 ## Outputs
 - Updated transcripts
+- Parser-driven automated walkthrough and Make target
 - Bug ledger by category
 - Fix changelog
 
@@ -31,6 +67,8 @@ Prove completion path, catch regressions, and close parser/content gaps.
 - Reasonable commands no longer fail silently or generically.
 - Repeated confusion points are captured and mapped to parser/content/hint fixes.
 - Transcript suite covers both mastery path and assisted path.
+- Golden path passes from a fresh game with every action crossing a save/reload boundary.
+- The exact documented compound nouns, conversation topics, custom verbs, and final accusation parse successfully.
 
 ## Primary Source Coverage
 - `ZIL_TEXT_ADVENTURE_AGENTS.md`: section 8
diff --git a/skills/07_workflow_subagents_and_hints_ui.md b/skills/07_workflow_subagents_and_hints_ui.md
index 72921d7..e75caab 100644
--- a/skills/07_workflow_subagents_and_hints_ui.md
+++ b/skills/07_workflow_subagents_and_hints_ui.md
@@ -26,6 +26,8 @@ Operationalize iterative development with specialized passes and parent-child hi
    - progressive command hint (only after repeated failure)
 5. Preserve mystery while reducing stall-outs; hints should extend play, not skip play.
 6. Design for social solving: puzzle prompts and room/object naming should be easy to discuss out loud.
+7. Use a vertical-slice gate: design exact commands, implement one slice, play it through `llm.lua`, add it to the automated walkthrough, then proceed.
+8. After any vocabulary, containment, counter, route, NPC, or save-system change, replay both the focused slice and the golden path.
 
 ## Outputs
 - Review findings per specialist pass
@@ -38,6 +40,7 @@ Operationalize iterative development with specialized passes and parent-child hi
 - Workflow remains slice-based, not big-bang rewrites.
 - Hint UI avoids replacing parser agency with exhaustive action lists.
 - Co-play flow supports parent guidance without immediate spoilers.
+- No iteration batch contains multiple unplayed puzzles; each completed slice has parser-driven coverage before the next begins.
 
 ## Primary Source Coverage
 - `ZIL_TEXT_ADVENTURE_AGENTS.md`: sections 9, 11, 13
diff --git a/skills/08_packaging_checklists_and_release.md b/skills/08_packaging_checklists_and_release.md
index 51bea10..dc0e1dc 100644
--- a/skills/08_packaging_checklists_and_release.md
+++ b/skills/08_packaging_checklists_and_release.md
@@ -21,6 +21,8 @@ Prepare final adventure package and verify definition-of-done criteria.
 6. Verify progress communication is legible (score/rank/chapter/objective summaries).
 7. If producing episodic content, design ending/start transition for narrative continuity even without save import.
 8. Confirm optional accessibility supports for modern play (transcript visibility, note surfaces, hint controls).
+9. Run the dedicated parser-driven walkthrough target from a fresh save and confirm final progress counters and win output.
+10. Run unit, LLM persistence, and broad pure-ZIL regressions after the final content change.
 
 ## Outputs
 - Release-ready adventure folder
@@ -31,6 +33,7 @@ Prepare final adventure package and verify definition-of-done criteria.
 - Packaging files present and coherent with game content.
 - Supplemental artifacts support immersion and optional hinting, not just decoration.
 - Episode hooks and transition text preserve emotional continuity.
+- The release walkthrough uses the exact commands published in testing/hint materials and passes across separate saved invocations.
 
 ## Primary Source Coverage
 - `ZIL_TEXT_ADVENTURE_AGENTS.md`: section 12
diff --git a/skills/README.md b/skills/README.md
index d2ab8c3..3db1907 100644
--- a/skills/README.md
+++ b/skills/README.md
@@ -96,17 +96,46 @@ adventure-name/
 - Full source mirrors remain available for exact wording and complete reference.
 - The `work/`, `test/`, and `package/` subfolders keep adventures organized as they grow.
 
+## Non-Negotiable: Play As You Build
+
+Do not write the whole adventure and wait for Stage 6 to play it. Build vertical slices:
+
+1. Write the exact player commands for one room or puzzle in `TRANSCRIPT_TESTS.md`.
+2. Implement only that slice.
+3. Start a fresh game and execute those commands through `llm.lua`, one saved invocation per command.
+4. Test the obvious noun variants, wrong order, repeated action, inventory, and save/reload boundary.
+5. Add the successful commands to the automated parser-driven walkthrough.
+6. Continue only when the slice passes.
+
+The walkthrough grows with the game. At every commit-sized milestone, all implemented slices must still be playable from a fresh game.
+
 ## Critical Rules (from Real Bugs)
 
 **These caused broken games. Read before implementing.**
 
-1. **No `<SYNTAX ...>` in dungeon.zil** — SYNTAX comes from substrate (`infocom/zork1/syntax.zil`). Adding your own breaks commands.
+1. **No `<SYNTAX ...>` in dungeon.zil and no redefinition of standard syntax** — standard SYNTAX comes from substrate (`infocom/zork1/syntax.zil`). A genuinely new verb may add one narrow declaration in `actions.zil`.
 2. **No `<ROUTINE V-LOOK ...>` in actions.zil** — V-LOOK comes from substrate. Redefining it breaks room descriptions.
 3. **Room descriptions use `P?LDESC` not `P?DESC`** — `P?DESC` is the room name, `P?LDESC` is the full description.
 4. **Every `<TELL>` must close with `>`** — unclosed TELL swallows subsequent code.
 5. **GO must exist in actions.zil** — entry point for the game.
 6. **Room descriptions don't embed item descriptions** — items describe themselves via `FDESC`/`LDESC`/`DESCFCN`. This keeps content modular and lets items adapt to state changes.
-7. **Use dynamic descriptions for state-changing rooms** — rooms with open/closed, lit/unlit, or locked/unlocked elements should use an ACTION routine with `M-LOOK` to vary the description based on flags.
+7. **Never freeze mutable state into `LDESC`** — follow Zork I's `EAST-HOUSE` pattern: rooms with open/closed, lit/unlit, locked/unlocked, moved, revealed, or depleted elements should omit the duplicated static `LDESC` and use an ACTION routine with `M-LOOK` to compose the full live description from object state. The object's ACTION routine separately handles `EXAMINE` and manipulation.
+8. **Object IDs and DESC text are not parser vocabulary** — every reachable object needs explicit `SYNONYM` nouns and `ADJECTIVE` modifiers matching the exact transcript commands, including hyphenated forms when used.
+9. **Opening a container must make contents reachable** — use container/search flags, set `OPENBIT`, and verify contents can be taken after a separate save/reload invocation.
+10. **Evidence and milestone counters must be idempotent** — guard one-time increments with per-clue flags so repeated EXAMINE/READ/TAKE cannot inflate progress.
+11. **Default verb routines never redispatch themselves** — `PERFORM` already visits object actions before the default; calling the same action again creates recursion.
+12. **Parser syntax and action routines are separate deliverables** — a `V-*` routine does not register a typed verb. Test `USE`, `SHOW`, `HINTS`, custom verbs, and substrate aliases through `llm.lua`.
+13. **ASK uses the TELL action and `PRSI` topic** — NPC routines test `<VERB? TELL>` and compare the topic in `PRSI`; do not depend on a separate `V?ASK`.
+14. **Puzzle clues and executable sequences must agree** — reconcile prose, hints, object availability, implementation order, and the parser-driven walkthrough before shipping.
+11. **FDESC/LDESC text is the parser vocabulary contract** — every concrete noun in description text that a player might reasonably type must resolve to that object or another object in scope. When FDESC describes an item inside a container (e.g., "A leather roll lies in the open drawer"), create a container object for the described item rather than adding the description noun as a synonym on the contained object. `scripts/check-vocab.lua` checks that printed `DESC` names contain a registered synonym; transcript playtesting must cover the broader prose contract.
+12. **ACTION routine text must match game objects** — when a TELL inside an ACTION routine mentions an object by name ("contains a letter", "sits on the table"), that object must exist in the game world with the right parent and matching SYNONYM. Players will immediately type the noun they just read.
+13. **Don't override EXAMINE on containers** — the Zork engine automatically lists contents via `V-LOOK-INSIDE` → `PRINT-CONT`. Containers with `CONTBIT` print "The X contains: Y, Z" when open, "closed" when closed. Place objects inside containers with `(IN CONTAINER)` rather than printing their names manually.
+14. **Physical nouns are objects, not Boolean shortcuts** — if prose says there is a door, window, switch, drawer, rope, vehicle, or other thing the player could reasonably EXAMINE, OPEN, CLOSE, UNLOCK, TAKE, or refer to as IT, create an `OBJECT` for it. Put shared fixtures in `LOCAL-GLOBALS`, list them in each relevant room's `GLOBAL`, and use object flags such as `OPENBIT` in exits and descriptions. A global may supplement the object for state the object model does not represent (for example, locked versus closed), but must not replace the object itself. Never print a physical obstacle while implementing only `(SOUTH TO ROOM IF SOME-FLAG)`; that produces scenery the parser cannot interact with.
+15. **Custom V-GO routines must mirror every conditional exit** — if you write `V-GO-NORTH`/`V-GO-SOUTH`/etc., every conditional exit (`IF CIPHER-SOLVED`, `IF DOOR IS OPEN`) declared on rooms must be replicated inside the matching V-GO routine. Missing the check silently bypasses the puzzle. Also ensure every room with an exit for that direction appears in the routine.
+16. **NPCs and key objects need generous, overlap-tested vocabulary** — give every NPC role-based synonyms, title adjectives, and `ARTICLEBIT` where "the X" is natural. Add hyphenated compound forms as `SYNONYM`. Pre-register every verb the DESIGN.md promises (ASK, SEARCH, LOOK AT) with explicit `SYNTAX` entries. Test all transcript noun phrases through the parser.
+17. **No two objects in overlapping scope may share DESC or SYNONYM sets** — identical `DESC` strings on objects that can be in scope together cause disambiguation loops. Give unique DESCs, use distinct adjectives, and audit room `GLOBAL` lists so objects don't pseudo-appear in rooms where they don't belong.
+18. **Dynamic room text must faithfully reflect object state** — every state-dependent phrase in a room ACTION routine must be paired with the exact flag check that produces it. Don't say "slightly ajar" for a closed drawer or contradict what the object's own EXAMINE reports.
+19. **NPC-given items must guard against early TAKE** — if an NPC carries an item meant to be given during conversation, the item's TAKE handler must check the relevant global (e.g., `HUDSON-KEY-GIVEN`) before allowing the player to take it.
 
 See `05_zil_implementation_reference.md` for details.
 
@@ -151,7 +180,6 @@ For rooms that can be entered only via vehicle (boats, etc.):
 | `READBIT` | Can be READ | For readable items |
 | `CONTBIT` | Is a container | For boxes, bags, etc. |
 | `OPENBIT` | Container is open | For open containers/doors |
-| `OPENABLEBIT` | Can be opened/closed | For containers that open |
 | `LIGHTBIT` | Can provide light | For lanterns, torches |
 | `ONBIT` | Light source is on | For active light sources |
 | `ACTORBIT` | Is an NPC | For talkable characters |
@@ -178,5 +206,5 @@ After setting flags, test:
 1. Can player enter the room?
 2. Is the room lit (if ONBIT) or dark (if no ONBIT)?
 3. Can player take objects (if TAKEBIT)?
-4. Can player open containers (if CONTBIT + OPENABLEBIT)?
+4. Can player open and close containers (if `CONTBIT`)?
 5. Can player talk to NPCs (if ACTORBIT)?
diff --git a/skills/source_writing_adventures.md b/skills/source_writing_adventures.md
index a3f0245..4a93ded 100644
--- a/skills/source_writing_adventures.md
+++ b/skills/source_writing_adventures.md
@@ -142,7 +142,7 @@ Keep it as a table:
 
 | Room | N | S | E | W | U | D | Special |
 |------|---|---|---|---|---|---|---------|
-| LIGHTHOUSE-BASE | LIGHTHOUSE-INTERIOR* | — | COASTAL-PATH | — | — | — | *N only if TOWER-UNLOCKED |
+| LIGHTHOUSE-BASE | LIGHTHOUSE-INTERIOR* | — | COASTAL-PATH | — | — | — | *N only if IRON-DOOR is open |
 | COASTAL-PATH | OLD-BRIDGE | — | — | LIGHTHOUSE-BASE | — | — | |
 
 …and as a diagram so the shape is visible at a glance:
@@ -153,7 +153,7 @@ graph LR
   PATH -- W --> BASE
   PATH -- N --> BRIDGE[Old Bridge]
   BRIDGE -- S --> PATH
-  BASE -. "N if TOWER-UNLOCKED" .-> INT[Lighthouse Interior]
+  BASE -. "N if IRON-DOOR is open" .-> INT[Lighthouse Interior]
 ```
 
 **Rule enforced by this artifact:** every exit is bidirectional unless the design says otherwise, and every "otherwise" is written in the Special column with its reason.
@@ -165,7 +165,7 @@ Every object on one line. This is what keeps synonyms unique, flags correct, and
 | Object | Starts in | Flags | Synonyms / Adjectives | Size | Action |
 |--------|-----------|-------|-----------------------|------|--------|
 | IRON-KEY | KEEPERS-COTTAGE | TAKEBIT | KEY / IRON HEAVY | 4 | — |
-| IRON-DOOR | LIGHTHOUSE-BASE | — | DOOR / IRON RUSTED TOWER | — | IRON-DOOR-F |
+| IRON-DOOR | LOCAL-GLOBALS | DOORBIT NDESCBIT | DOOR / IRON RUSTED TOWER | — | IRON-DOOR-F |
 | OIL-CAN | LIGHTHOUSE-INTERIOR | TAKEBIT | CAN OIL / OIL | 5 | — |
 
 **Rules enforced:** takeable things have `TAKEBIT`; containers have `CONTBIT`; no two objects reachable in the same room share an ambiguous synonym without a distinguishing adjective; every object with custom behavior has an `ACTION` routine that exists.
@@ -176,7 +176,7 @@ Every `GLOBAL` flag: what it means, who sets it, who reads it. This is the artif
 
 | Flag | Meaning | Set by | Read by |
 |------|---------|--------|---------|
-| TOWER-UNLOCKED | Iron door open | IRON-DOOR-F | LIGHTHOUSE-BASE exit (N) |
+| TOWER-UNLOCKED | Iron door lock has been released | IRON-DOOR-F | IRON-DOOR-F descriptions/actions |
 | LAMP-LIT | Fresnel lens burning | LENS-F | LENS-F examine, ending check |
 
 ### 4. Puzzle dependency graph (the puzzle chart)
@@ -187,7 +187,7 @@ The spine of the game: which puzzle gates which. Shows dead-ends and unreachable
 graph TD
   MATCHES[Find matchbook<br/>on bridge] --> LAMP
   OILCAN[Find oil can<br/>in interior] --> LAMP
-  KEY[Find iron key<br/>in cottage] --> DOOR[Unlock iron door<br/>sets TOWER-UNLOCKED]
+  KEY[Find iron key<br/>in cottage] --> DOOR[Unlock/open iron door<br/>sets TOWER-UNLOCKED + OPENBIT]
   DOOR --> INTERIOR[Reach interior]
   INTERIOR --> OILCAN
   INTERIOR --> LAMP[Light the lens<br/>sets LAMP-LIT = win]
@@ -215,6 +215,10 @@ A grid of which objects deliberately respond to which non-default verbs. Blank c
 | FRESNEL-LENS | ✓ | — | ✓ | — |
 | FIREPLACE | ✓ | — | — | ✓ |
 
+The grid must use the substrate's action names, not just the surface words. For example, Zork I parses `PULL` as the `MOVE` action, so a pullable object's row records `PULL → MOVE`. A `V-*` routine alone does not register vocabulary: every desired typed verb absent from `infocom/zork1/syntax.zil` also needs a narrow game-specific `SYNTAX` declaration and a literal parser test.
+
+For conversation, `ASK` is a parser synonym for the `TELL` action. NPC routines test `<VERB? TELL>`, keep the actor in `PRSO`, and read the topic from `PRSI`. Default verb routines must end in a response; they must never call `PERFORM` with their own action, because `PERFORM` has already tried the object handlers and will recurse back to the same default.
+
 ### 6. Daemon / clock schedule
 
 Every `QUEUE`d routine, its interval, and — critically — every global flag it reads. This is the checklist for the systems-interaction pass in §4: cross every daemon against every flag in the state ledger and ask "what happens when this fires while that flag is set?"
@@ -291,7 +295,7 @@ The walkthrough (`walkthrough.zil`) also serves as the entry point that wires th
 <CONSTANT RELEASEID 1>
 
 ; Global flags (state tracking)
-<GLOBAL DOOR-UNLOCKED <>>
+<GLOBAL RIDDLE-SOLVED <>>
 <GLOBAL LAMP-LIT <>>
 
 ; Rooms
@@ -360,9 +364,12 @@ Rooms are the locations the player moves between.
 
 **Direction connections:**
 - `(NORTH TO ROOM-NAME)` — unconditional exit
-- `(NORTH TO ROOM-NAME IF FLAG-NAME)` — conditional exit (only if global flag is true)
+- `(NORTH TO ROOM-NAME IF FLAG-NAME)` — conditional exit for an abstract condition or milestone
+- `(NORTH TO ROOM-NAME IF DOOR-NAME IS OPEN)` — conditional exit through a physical door or window object
 - `(NORTH PER ROUTINE-NAME)` — exit handled by a routine
 
+Do not use the flag-only form as a substitute for a physical object named in the prose. If the room says "a locked door blocks the north passage," create a `DOORBIT` object, put it in scope, and use `IF DOOR-NAME IS OPEN`. A supplementary global may track locked versus unlocked if needed, but the door itself must exist.
+
 **Flags:**
 - `RLANDBIT` — this is a land-based room (standard)
 - `ONBIT` — room is lit (no light source needed). Omit for dark rooms.
@@ -400,31 +407,125 @@ Objects are anything the player can see, examine, or interact with.
 
 **Object flags:**
 
-| Flag | Meaning |
-|------|---------|
-| `TAKEBIT` | Player can pick this up |
-| `READBIT` | Can be READ (shows TEXT property) |
-| `CONTBIT` | Is a container (things can be put IN it) |
-| `OPENBIT` | Container/door is currently open |
-| `OPENABLEBIT` | Can be opened/closed |
-| `SURFACEBIT` | Things can be put ON it (like a table) |
-| `DOORBIT` | Is a door (can be opened/closed) |
-| `LIGHTBIT` | Can provide light (lantern, torch) |
-| `ONBIT` | Light source is currently on |
-| `ACTORBIT` | Is an NPC (can be talked to) |
-| `WEAPONBIT` | Can be used as a weapon |
-| `TOOLBIT` | Can be used as a tool (keys, shovels) |
-| `TURNBIT` | Can be turned (valves, dials) |
-| `TRANSBIT` | Container is transparent (contents visible when closed) |
-| `NDESCBIT` | Don't auto-describe in room |
-| `SEARCHBIT` | Can be searched |
-| `DRINKBIT` | Can be drunk |
-| `FOODBIT` | Can be eaten |
-| `BURNBIT` | Can be burned |
-| `FLAMEBIT` | Produces flame |
-| `CLIMBBIT` | Can be climbed |
-| `VEHBIT` | Is a vehicle |
-| `WEARBIT` | Can be worn |
+Organized by use case. Most adventure objects need only a few — see the "Common combinations" below.
+
+#### Container & Visibility
+
+| Flag | Meaning | Example | Notes |
+|------|---------|---------|-------|
+| `CONTBIT` | Is a container — things can be put IN it | Trunk, box, bag | Engine auto-lists contents when open via `V-LOOK-INSIDE` |
+| `OPENBIT` | Container/door is currently open | Open drawer | Set/cleared by OPEN/CLOSE verb. Toggled at runtime with `<FSET ,OBJ ,OPENBIT>` |
+| `SURFACEBIT` | Things can be put ON it (not IN) | Table, desk, altar | Parser understands "PUT X ON Y" vs "PUT X IN Y" |
+| `TRANSBIT` | Container is transparent — contents visible when closed | Glass bottle, cage | Engine lists contents even when container is closed |
+| `SEARCHBIT` | Can be searched — LOOK IN / SEARCH reveals contents | Trunk, desk | Used by parser to allow SEARCH verb |
+
+**Common container combinations:**
+```zil
+(FLAGS CONTBIT OPENBIT SEARCHBIT)      ; open box you can search
+(FLAGS CONTBIT SEARCHBIT)              ; closed box you can open and search
+(FLAGS SURFACEBIT CONTBIT OPENBIT)     ; open table/surface
+(FLAGS CONTBIT TRANSBIT)               ; glass jar — always see inside
+```
+
+#### Light
+
+| Flag | Meaning | Example | Notes |
+|------|---------|---------|-------|
+| `LIGHTBIT` | Can provide light — is a light source | Lantern, torch, candles | Capability to emit light. Use with `ONBIT` for active state |
+| `ONBIT` | Light source is currently on / room is lit | Lit lantern | On a light source: it's emitting light. On a room: room is lit (no dark room) |
+
+**Common light combinations:**
+```zil
+(FLAGS LIGHTBIT ONBIT)       ; lantern that starts lit
+(FLAGS LIGHTBIT)             ; lantern that starts off
+(FLAGS RLANDBIT ONBIT)       ; lit room (always visible)
+(FLAGS RLANDBIT)             ; dark room (needs light source)
+```
+
+#### Player Interaction
+
+| Flag | Meaning | Example | Notes |
+|------|---------|---------|-------|
+| `TAKEBIT` | Can be picked up and carried | Key, coin, letter | Without this, "TAKE X" fails. Most inventory objects need it |
+| `READBIT` | Can be READ — shows TEXT property | Letter, book, map | READ verb shows the `(TEXT ...)` property |
+| `WEARBIT` | Can be worn/unworn | Hat, coat, armor | Allows WEAR/UNWEAR verbs |
+| `FOODBIT` | Can be eaten | Lunch, garlic, fruit | Allows EAT verb |
+| `DRINKBIT` | Can be drunk | Water, potion | Allows DRINK verb |
+| `BURNBIT` | Can be burned/destroyed | Paper, rope, book | Allows BURN verb. Object is flammable |
+| `CLIMBBIT` | Can be climbed | Tree, stairs, ladder | Allows CLIMB verb |
+
+#### Tool & Weapon
+
+| Flag | Meaning | Example | Notes |
+|------|---------|---------|-------|
+| `TOOLBIT` | Can be used as a tool (instrument) | Key, screwdriver, shovel | Parser uses this for "OPEN X WITH Y", "UNLOCK X WITH Y", etc. |
+| `WEAPONBIT` | Can be used as a weapon | Sword, axe, knife | Parser uses this for "ATTACK X WITH Y", "KILL X WITH Y" |
+| `TURNBIT` | Can be turned/twisted | Valve, dial, bolt | Allows TURN verb. For "TURN X TO Y" or "TURN X WITH Y" |
+| `FLAMEBIT` | Produces flame (fire source) | Match, torch, candles | Combined with `ONBIT` = actively flaming. Used by FLAMING? macro |
+
+**Common tool/weapon combinations:**
+```zil
+(FLAGS TAKEBIT TOOLBIT)              ; key, lockpick set
+(FLAGS TAKEBIT WEAPONBIT)            ; sword, knife
+(FLAGS TAKEBIT TOOLBIT WEAPONBIT)    ; axe — both tool and weapon
+(FLAGS TAKEBIT FLAMEBIT ONBIT)       ; lit torch
+```
+
+#### NPC & Combat
+
+| Flag | Meaning | Example | Notes |
+|------|---------|---------|-------|
+| `ACTORBIT` | Is an NPC — can be talked to, commanded, attacked | Troll, thief, ghost | Parser uses this for TELL, COMMAND, ATTACK, KISS, WAKE verbs |
+| `TRYTAKEBIT` | Can't be taken, but TAKE triggers ACTION routine | Troll, basket | ACTION routine handles the attempt (combat, custom message, etc.) |
+| `FIGHTBIT` | Currently in combat | Troll during fight | Set/cleared by combat system. Indicates active engagement |
+| `STAGGERED` | Stunned in combat — can't attack next turn | Staggered combatant | Set/cleared by combat system during fight resolution |
+
+**Common NPC combinations:**
+```zil
+(FLAGS ACTORBIT TRYTAKEBIT)          ; NPC that can't be taken
+(FLAGS ACTORBIT TRYTAKEBIT OPENBIT)  ; NPC in open container (cyclops in room)
+```
+
+#### Room Flags
+
+| Flag | Meaning | Example | Notes |
+|------|---------|---------|-------|
+| `RLANDBIT` | Is solid ground — safe, standard room | Most rooms | Every normal room needs this. Affects movement, combat, thief behavior |
+| `ONBIT` | Room is lit (on rooms, not light sources) | Lit room | Every room that's always lit needs this. Omit for dark rooms |
+| `NONLANDBIT` | Not land — water/air | Flooded reservoir | Prevents land-based actions. Used for boat/water rooms |
+| `MAZEBIT` | Is a maze room | Maze areas | Affects thief behavior and movement pathfinding |
+| `SACREDBIT` | Cannot be touched/destroyed by thief | Treasure rooms | Thief won't steal from or enter these rooms |
+
+**Common room combinations:**
+```zil
+(FLAGS RLANDBIT ONBIT)       ; standard lit room
+(FLAGS RLANDBIT)             ; dark room (needs light source)
+(FLAGS NONLANDBIT)           ; water/air room
+(FLAGS RLANDBIT MAZEBIT ONBIT)  ; lit maze room
+```
+
+#### Visibility & State
+
+| Flag | Meaning | Example | Notes |
+|------|---------|---------|-------|
+| `INVISIBLE` | Not visible — hidden from parser and player | Trap-door (before rug moved) | Set/cleared at runtime to show/hide objects |
+| `NDESCBIT` | Don't auto-describe in room text | Scenery, scenery-in-room | Object's description is handled by room LDESC or ACTION routine. Scenery objects use this |
+| `TOUCHBIT` | Has been visited/interacted with | Room (after first visit) | Controls FDESC (first time) vs LDESC (subsequent). Set by engine on first room visit |
+
+**Common visibility combinations:**
+```zil
+(FLAGS NDESCBIT)                      ; scenery — described in room text, not auto-listed
+(FLAGS NDESCBIT CONTBIT OPENBIT)      ; open container described in room text
+(FLAGS INVISIBLE)                     ; hidden object — revealed later with FSET
+(FLAGS TAKEBIT)                       ; normal takeable object (visible by default)
+```
+
+**Other flags** (defined in engine but rarely needed in adventure writing):
+
+| Flag | Meaning | When to use |
+|------|---------|-------------|
+| `NWALLBIT` | No wall interaction | Inherited from Zork engine, rarely used |
+| `RMUNGBIT` | Can be munged/destroyed | For destructible objects. Also used as catch-all in syntax matching |
 
 ### Routines (Action Handlers)
 
@@ -472,12 +573,12 @@ Routines are functions that handle player interactions with objects.
 
 ### Global Variables (Flags)
 
-Global flags track puzzle state across the game:
+Global flags track abstract puzzle facts, milestones, and one-time guards across the game:
 
 ```zil
-<GLOBAL DOOR-UNLOCKED <>>
+<GLOBAL RITUAL-COMPLETE <>>
 <GLOBAL MONSTER-DEFEATED <>>
-<GLOBAL LANTERN-LIT <>>
+<GLOBAL LETTER-DISCOVERED <>>
 ```
 
 `<>` means false/nil. `T` means true.
@@ -485,28 +586,50 @@ Global flags track puzzle state across the game:
 **Using globals:**
 ```zil
 ; Test a global
-<COND (,DOOR-UNLOCKED <TELL "The door is open." CR>)>
+<COND (,RITUAL-COMPLETE <TELL "The ritual is complete." CR>)>
 
 ; Set a global to true
-<SETG DOOR-UNLOCKED T>
+<SETG RITUAL-COMPLETE T>
 
 ; Set a global to false
-<SETG DOOR-UNLOCKED <>>
+<SETG RITUAL-COMPLETE <>>
 ```
 
 ### Conditional Exit with Flag
 
+Use this form when the condition is abstract, such as completing a ritual, surviving a timed event, or reaching a story milestone. Do not use it to fake a door, window, gate, or other physical obstacle.
+
 ```zil
 <ROOM HALLWAY
       (IN ROOMS)
       (DESC "Hallway")
-      (LDESC "A long hallway. A door to the north is secured with a padlock.")
-      (NORTH TO SECRET-ROOM IF DOOR-UNLOCKED)
+      (LDESC "A long hallway ends at the chalk circle where the ritual must be completed.")
+      (NORTH TO SECRET-ROOM IF RITUAL-COMPLETE
+             ELSE "The unfinished ritual still bars your way.")
       (SOUTH TO LOBBY)
       (FLAGS RLANDBIT ONBIT)>
 ```
 
-The player can only go NORTH once `DOOR-UNLOCKED` is set to `T`.
+The player can only go NORTH once the abstract milestone `RITUAL-COMPLETE` is true.
+
+For an actual door, use an object-driven exit instead:
+
+```zil
+<OBJECT STUDY-DOOR
+      (IN LOCAL-GLOBALS)
+      (SYNONYM DOOR)
+      (ADJECTIVE STUDY OAK)
+      (DESC "study door")
+      (FLAGS DOORBIT NDESCBIT)
+      (ACTION STUDY-DOOR-F)>
+
+<ROOM HALLWAY
+      (NORTH TO SECRET-ROOM IF STUDY-DOOR IS OPEN
+             ELSE "The study door is closed.")
+      (GLOBAL STUDY-DOOR)>
+```
+
+`OPENBIT` controls traversal. If the game distinguishes locked from closed, keep a supplementary `STUDY-UNLOCKED` global and update it in `STUDY-DOOR-F`; never let that global replace the door object.
 
 ### Control Flow
 
@@ -1276,9 +1399,11 @@ Here's a minimal but complete adventure demonstrating all major features:
       (IN ROOMS)
       (DESC "Lighthouse Base")
       (LDESC "You stand at the base of an old lighthouse. The paint is peeling and salt encrusts the windows. A rusted iron door leads north into the tower. The coastal path continues east toward the village.")
-      (NORTH TO LIGHTHOUSE-INTERIOR IF TOWER-UNLOCKED)
+      (NORTH TO LIGHTHOUSE-INTERIOR IF IRON-DOOR IS OPEN
+             ELSE "The iron door is closed.")
       (EAST TO COASTAL-PATH)
-      (FLAGS RLANDBIT ONBIT)>
+      (FLAGS RLANDBIT ONBIT)
+      (GLOBAL IRON-DOOR)>
 
 <ROOM COASTAL-PATH
       (IN ROOMS)
@@ -1307,9 +1432,11 @@ Here's a minimal but complete adventure demonstrating all major features:
       (IN ROOMS)
       (DESC "Lighthouse Interior")
       (LDESC "The ground floor of the lighthouse. A spiral staircase leads up. Machinery and supplies are scattered about. The door south leads outside.")
-      (SOUTH TO LIGHTHOUSE-BASE)
+      (SOUTH TO LIGHTHOUSE-BASE IF IRON-DOOR IS OPEN
+             ELSE "The iron door is closed.")
       (UP TO LAMP-ROOM)
-      (FLAGS RLANDBIT ONBIT)>
+      (FLAGS RLANDBIT ONBIT)
+      (GLOBAL IRON-DOOR)>
 
 <ROOM LAMP-ROOM
       (IN ROOMS)
@@ -1321,11 +1448,12 @@ Here's a minimal but complete adventure demonstrating all major features:
 ; === OBJECTS ===
 
 <OBJECT IRON-DOOR
-        (IN LIGHTHOUSE-BASE)
+        (IN LOCAL-GLOBALS)
         (SYNONYM DOOR)
         (ADJECTIVE IRON RUSTED TOWER)
         (DESC "iron door")
         (LDESC "A rusted iron door blocks entry to the lighthouse tower.")
+        (FLAGS DOORBIT NDESCBIT)
         (ACTION IRON-DOOR-F)>
 
 <OBJECT IRON-KEY
@@ -1378,11 +1506,12 @@ Here's a minimal but complete adventure demonstrating all major features:
 
 <ROUTINE IRON-DOOR-F ()
          <COND (<AND <VERB? EXAMINE>
+                     <NOT <FSET? ,IRON-DOOR ,OPENBIT>>
                      <NOT ,TOWER-UNLOCKED>>
                 <TELL "The iron door is rusted shut but has a large keyhole. It might open with the right key." CR>
                 <RTRUE>)
                (<AND <VERB? EXAMINE>
-                     ,TOWER-UNLOCKED>
+                     <FSET? ,IRON-DOOR ,OPENBIT>>
                 <TELL "The iron door stands open." CR>
                 <RTRUE>)
                (<AND <VERB? OPEN UNLOCK>
@@ -1395,6 +1524,7 @@ Here's a minimal but complete adventure demonstrating all major features:
                      <IN? ,IRON-KEY ,WINNER>>
                 <TELL "You fit the iron key into the lock. With effort, the rusted mechanism turns and the door swings open, revealing a spiral staircase within." CR>
                 <SETG TOWER-UNLOCKED T>
+                <FSET ,IRON-DOOR ,OPENBIT>
                 <RTRUE>)>>
 
 <ROUTINE FIREPLACE-F ()
@@ -1535,7 +1665,8 @@ A walkthrough test is itself a ZIL file. It includes the standard engine files a
     <ASSERT "Take the iron key" <CO-RESUME ,CO "take key" T> <==? <LOC ,IRON-KEY> ,ADVENTURER>>
 
     ; === Puzzle solution ===
-    <ASSERT "Unlock the door" <CO-RESUME ,CO "unlock door with key" T> ,DOOR-UNLOCKED>
+    <ASSERT "Unlock the door" <CO-RESUME ,CO "unlock door with key" T>
+            <AND ,TOWER-UNLOCKED <FSET? ,IRON-DOOR ,OPENBIT>>>
     <ASSERT "Enter the next area" <CO-RESUME ,CO "walk north" T> <==? ,HERE ,NEXT-ROOM>>
 
     ; === Winning condition ===
@@ -1562,7 +1693,7 @@ A good walkthrough test should:
 4. **Verify text output** — key descriptions use `ASSERT-TEXT` to catch broken output
 5. **Test the ending** — confirm the final victory condition triggers
 
-You don't need to test every verb on every object — focus on the path that wins the game. Optional puzzles and flavor interactions are nice to include but not required.
+You do not need a Cartesian test of every verb on every object. You do need literal parser-driven coverage for the critical path, every custom or newly registered verb, every verb × object cell promised by the design, global scenery names, NPC conversation forms, blocked exits, and natural aliases such as `INSPECT`, `ME`, and titled NPC names. Optional flavor can be sampled rather than exhaustive.
 
 ### Checklist Item
 
@@ -1702,7 +1833,8 @@ Use this checklist before submitting your adventure:
 - [ ] Every locked gate has a solution reachable before it
 - [ ] At least one clue exists for every puzzle
 - [ ] No dead ends where the player is stuck with no recourse
-- [ ] Global flags track state for conditional exits and multi-step puzzles
+- [ ] Physical obstacles are real objects; object flags control their physical state
+- [ ] Global flags track abstract milestones, scoring guards, and state not represented by object flags
 
 ### Verbs
 - [ ] **CRITICAL: No `<SYNTAX ...>` forms in dungeon.zil** — all SYNTAX comes from the substrate (`infocom/zork1/syntax.zil`). Adding your own will cause conflicts and broken commands.
diff --git a/skills/source_zil_text_adventure_agents.md b/skills/source_zil_text_adventure_agents.md
index c562b2a..d633fb8 100644
--- a/skills/source_zil_text_adventure_agents.md
+++ b/skills/source_zil_text_adventure_agents.md
@@ -418,7 +418,9 @@ But override defaults often. Good IF feels hand-authored.
 
 ## 5. Keeping Track of Story and State
 
-### 5.1 Use explicit flags
+### 5.1 Use explicit flags for abstract state
+
+Flags should represent abstract facts, milestones, and state that the object model cannot express. They must not replace physical objects named in the prose. If the game says there is a door, window, chest, switch, rope, or vehicle, create that object and let its location and object flags drive ordinary interaction.
 
 Bad:
 
@@ -429,13 +431,15 @@ The code infers progress from object location only.
 Better:
 
 ```text
-bridge-built = true
 riddle-solved = true
 goblin-trusts-player = true
+chapter-two-begun = true
 ```
 
 Object location can still matter, but major story states deserve named flags.
 
+Likewise, object state should still matter. Prefer `OPENBIT`, containment, location, and visibility for physical state. A supplementary flag such as `door-unlocked` is appropriate when the substrate has no `LOCKEDBIT`, but only alongside a real door object. A flag-only conditional exit describing an imaginary door is not a world model.
+
 ### 5.2 State should affect descriptions
 
 After a puzzle changes the world, update:
diff --git a/tests/run_all.lua b/tests/run_all.lua
index eadfcba..37ef050 100644
--- a/tests/run_all.lua
+++ b/tests/run_all.lua
@@ -6,6 +6,7 @@ require 'zilscript'
 
 local test_files = {
 	"tests/test_compiler.lua",
+	"tests/test_check_vocab.lua",
 	"tests/test_comprehensive_accuracy.lua",
 	"tests/test_defmac.lua",
 	"tests/test_framework.lua",
diff --git a/tests/test_check_vocab.lua b/tests/test_check_vocab.lua
new file mode 100644
index 0000000..0120cef
--- /dev/null
+++ b/tests/test_check_vocab.lua
@@ -0,0 +1,68 @@
+#!/usr/bin/env lua5.4
+
+local test = require 'tests.test_framework'
+
+local function shell_quote(value)
+	return "'" .. value:gsub("'", "'\\''") .. "'"
+end
+
+local function write_fixture(name, content)
+	local path = "/tmp/zilscript-check-vocab-" .. name .. ".zil"
+	local file = assert(io.open(path, "w"))
+	file:write(content)
+	file:close()
+	return path
+end
+
+local function run_checker(path)
+	local command = "lua5.4 scripts/check-vocab.lua " .. shell_quote(path) .. " 2>&1"
+	local pipe = assert(io.popen(command, "r"))
+	local output = pipe:read("*a")
+	local ok, _, code = pipe:close()
+	return ok == true and 0 or code or 1, output
+end
+
+test.describe("Vocabulary checker", function(t)
+	t.it("accepts adjectives and prepositional DESC text", function(assert)
+		local path = write_fixture("valid", [[
+<OBJECT KNIFE
+      (DESC "blood-stained knife")
+      (SYNONYM KNIFE BLADE)
+      (ADJECTIVE BLOOD STAINED)>
+<OBJECT DOOR
+      (DESC "door to the garden")
+      (SYNONYM DOOR GATE)>
+]])
+		local code, output = run_checker(path)
+		assert.assert_equal(code, 0)
+		assert.assert_match(output, "0 critical")
+		os.remove(path)
+	end)
+
+	t.it("rejects a printed name with no matching synonym", function(assert)
+		local path = write_fixture("invalid", [[
+<OBJECT RELIQUARY
+      (DESC "ornate reliquary")
+      (SYNONYM BOX CASE)>
+]])
+		local code, output = run_checker(path)
+		assert.assert_not_equal(code, 0)
+		assert.assert_match(output, "no DESC word appears in SYNONYM")
+		os.remove(path)
+	end)
+
+	t.it("rejects player-addressable scenery with no printed name", function(assert)
+		local path = write_fixture("missing-desc", [[
+<OBJECT FOG
+      (SYNONYM FOG MIST HAZE)
+      (FLAGS NDESCBIT)>
+]])
+		local code, output = run_checker(path)
+		assert.assert_not_equal(code, 0)
+		assert.assert_match(output, "object has SYNONYM but no DESC")
+		os.remove(path)
+	end)
+end)
+
+local success = test.summary()
+os.exit(success and 0 or 1)
diff --git a/tests/test_compiler.lua b/tests/test_compiler.lua
index d21ccfb..59924e6 100644
--- a/tests/test_compiler.lua
+++ b/tests/test_compiler.lua
@@ -37,6 +37,40 @@ test.describe("Compiler - Basic Compilation", function(t)
 	end)
 end)
 
+test.describe("Compiler - game-specific TELL and description contexts", function(t)
+	t.it("should lower Infocom verb and preposition synonym directives", function(assert)
+		local ast = parser.parse([[
+			<VERB-SYNONYM EXAMINE X>
+			<PREP-SYNONYM THROUGH THRU>
+		]])
+		local result = compiler.compile(ast)
+
+		assert.assert_match(result.body, 'DEFER_SYNONYM%("EXAMINE", "X"%)')
+		assert.assert_match(result.body, 'DEFER_SYNONYM%("THROUGH", "THRU"%)')
+	end)
+
+	t.it("should lower OBJDESC? to the M-OBJDESC? context", function(assert)
+		local ast = parser.parse([[<ROUTINE DESC (RARG) <RARG? OBJDESC?>>]])
+		local result = compiler.compile(ast)
+
+		assert.assert_match(result.declarations, "EQUALQ%(m_RARG, M_OBJDESCQ%)")
+	end)
+
+	t.it("should preserve article token identity in TELL", function(assert)
+		local ast = parser.parse([[<ROUTINE SAY (OBJ) <TELL A .OBJ " / " THE .OBJ " / " CTHE .OBJ>>]])
+		local result = compiler.compile(ast)
+
+		assert.assert_match(result.declarations, "TELL%(TELL_A, m_OBJ, \" / \", TELL_THE, m_OBJ, \" / \", TELL_CTHE, m_OBJ%)")
+	end)
+
+	t.it("should lower P? verb atoms and object alternatives", function(assert)
+		local ast = parser.parse([[<ROUTINE MATCH () <P? LISTEN (<> NOISE)>>]])
+		local result = compiler.compile(ast)
+
+		assert.assert_match(result.declarations, "PASS%(VERBQ%(VQLISTEN%) and PRSOQ%(nil, NOISE%)%)")
+	end)
+end)
+
 test.describe("Compiler - Object Compilation", function(t)
 	t.it("should compile simple object", function(assert)
 		local code = [[<OBJECT MAILBOX (DESC "mailbox")>]]
@@ -66,9 +100,28 @@ test.describe("Compiler - Object Compilation", function(t)
 		assert.assert_match(result.body, 'DESCFCN = ROUTINE_REF%("HOUSE_D"%)')
 		assert.assert_match(result.body, 'per = ROUTINE_REF%("NORTH_F"%)')
 	end)
+
+	t.it("should preserve hyphens in player-facing vocabulary", function(assert)
+		local code = [[<OBJECT TORN-PAGE
+			(SYNONYM PAGE TORN-PAGE)
+			(ADJECTIVE HAND-WRITTEN)
+			(FLAGS TAKEBIT)>]]
+		local result = compiler.compile(parser.parse(code))
+
+		assert.assert_match(result.body, 'SYNONYM = {"PAGE", "TORN%-PAGE"}')
+		assert.assert_match(result.body, 'ADJECTIVE = {"HAND%-WRITTEN"}')
+		assert.assert_match(result.body, 'FLAGS = {"TAKEBIT"}')
+	end)
 end)
 
 test.describe("Compiler - Constants and Globals", function(t)
+	t.it("should preserve STRING and LENGTH table storage", function(assert)
+		local code = [[<CONSTANT LOGIN-ID <TABLE (PURE LENGTH STRING) "872325412">>]]
+		local result = compiler.compile(parser.parse(code))
+
+		assert.assert_match(result.combined, 'STRING_TABLE%("872325412", true%)')
+	end)
+
 	t.it("should compile CONSTANT", function(assert)
 		local code = [[<CONSTANT MAX-SCORE 100>]]
 		local ast = parser.parse(code)
@@ -89,6 +142,27 @@ test.describe("Compiler - Constants and Globals", function(t)
 	end)
 end)
 
+test.describe("Compiler - Mapping Forms", function(t)
+	t.it("should lower MAP-DIRECTIONS with local bindings", function(assert)
+		local code = [[<ROUTINE WALK-EXITS (ROOM "AUX" COUNT)
+			<MAP-DIRECTIONS (D P .ROOM) <SET COUNT <PTSIZE .P>>>
+		>]]
+		local result = compiler.compile(parser.parse(code))
+
+		assert.assert_match(result.declarations, "MAP_DIRECTIONS%(m_ROOM, function%(m_D, m_P%)")
+		assert.assert_match(result.declarations, "PTSIZE%(m_P%)")
+	end)
+
+	t.it("should lower MAP-CONTENTS with current and next bindings", function(assert)
+		local code = [[<ROUTINE WALK-CONTENTS (BOX)
+			<MAP-CONTENTS (ITEM NEXT .BOX) <SET ITEM .NEXT>>
+		>]]
+		local result = compiler.compile(parser.parse(code))
+
+		assert.assert_match(result.declarations, "MAP_CONTENTS%(m_BOX, function%(m_ITEM, m_NEXT%)")
+	end)
+end)
+
 test.describe("Compiler - Control Flow", function(t)
 	t.it("should compile COND statement", function(assert)
 		local code = [[<ROUTINE TEST (X)
diff --git a/tests/test_limehouse_walkthrough.lua b/tests/test_limehouse_walkthrough.lua
new file mode 100644
index 0000000..7baa442
--- /dev/null
+++ b/tests/test_limehouse_walkthrough.lua
@@ -0,0 +1,196 @@
+#!/usr/bin/env lua5.4
+
+local test = require 'tests.test_framework'
+
+local function shell_quote(value)
+	return "'" .. value:gsub("'", "'\\''") .. "'"
+end
+
+local function run_command(command)
+	local pipe = assert(io.popen("zsh -lc " .. shell_quote(command) .. " 2>&1", "r"))
+	local output = pipe:read("*a")
+	local ok, _, code = pipe:close()
+	return ok == true and 0 or code or 1, output
+end
+
+local function cleanup(savefile)
+	os.remove(savefile)
+	os.remove(savefile .. ".actions")
+end
+
+test.describe("Limehouse Killings walkthrough", function(t)
+	t.it("should complete the documented golden path across LLM processes", function(assert)
+		local savefile = "/tmp/test-limehouse-golden-path.sav"
+		cleanup(savefile)
+		local suffix = " --save " .. shell_quote(savefile) .. " --game limehouse-killings"
+		local code = run_command("lua5.4 llm.lua --new-game" .. suffix)
+		assert.assert_equal(code, 0)
+
+		local actions = {
+			"go north", "take magnifying glass", {"go south", "The study door is closed."},
+			{"open study door", "need the study key or a lockpick"},
+			"go east", "examine reading-desk", "take torn-page", "read torn-page",
+			"examine colored-markers", "push red book", "push yellow book", "push green book",
+			"push blue book", "go south", "go east", "examine chalk-outline", "examine desk", "take dead-letter",
+			"read dead-letter", "take poison-bottle", "examine poison-bottle",
+			{"open study door", "interior bolt"}, "go north", "go west",
+			"examine table", {"examine wine cabinet", "missing squat bottle"},
+			{"open wine cabinet", "opens freely"}, "take wax-seal", "go north", "examine shelves", "take foxglove",
+			"take charcoal", {"taste vial", "vision swims"},
+			{"use charcoal", "dizziness recedes"}, "go south", "go east", "go down",
+			{"examine drawer", "The drawer is closed"},
+			{"open drawer", "Inside is a leather roll"},
+			{"examine drawer", "A leather roll lies in the open drawer"},
+			{"examine leather roll", "The leather roll is closed"},
+			{"open leather roll", "The leather roll contains:"},
+			{"close leather roll", "You close the leather roll"},
+			{"examine leather roll", "The leather roll is closed"},
+			{"open leather roll", "The leather roll contains:"},
+			"take lockpick set", "go west", "examine hedges", "take blood-stained-knife",
+			"take footprint cast", {"use magnifying glass on footprint cast", "outside edge of the right heel"},
+			"go north", "examine plants", "examine labels",
+			{"use vial on plants", "match the poison bottle label"}, "go south",
+			"go south", {"examine trunk", "The trunk contains:"},
+			{"close trunk", "You close the trunk"},
+			{"examine trunk", "The trunk is closed"},
+			{"open trunk", "The trunk contains:"},
+			{"examine trunk", "The trunk contains:"},
+			"ask hudson", "tell hudson", "ask hudson about master", "ask hudson about alibi",
+			"ask hudson about key", "take keyring", "ask hudson about moriarty",
+			{"show letter to hudson", "polishing cloth goes still"},
+			{"show letter to hudson", "Nine twenty"},
+			{"examine hudson", "stopped polishing"}, "go north", "go east",
+			"go up", "go west", "ask lady", "tell lady", "ask lady about marriage", "ask lady about alibi",
+			{"show letter to lady", "paper rattles"},
+			{"show letter to lady", "first draft named the laboratory account"},
+			{"examine lady", "wedding ring"}, "go east", "go east",
+			"ask moriarty", "tell moriarty", "ask moriarty about experiments",
+			{"show letter to moriarty", "Blackmail"}, {"examine moriarty", "sweat darkens"},
+			{"show letter to moriarty", "already performed that trick"},
+			"ask moriarty about poison", "take secret-ledger",
+			"read secret-ledger", "go west", "go south", "examine locked-box",
+			"turn locked box to moriarty", "take bank-statement", "read bank-statement", "go north",
+			"ask inspector", "tell inspector", "ask inspector about case", "show letter to inspector",
+			"show bottle to inspector", "show statement to inspector",
+			{"show footprint cast to inspector", "crescent nicks meet"},
+		}
+
+		for _, entry in ipairs(actions) do
+			local action = type(entry) == "table" and entry[1] or entry
+			local expected = type(entry) == "table" and entry[2] or nil
+			local action_code, output = run_command(
+				"lua5.4 llm.lua --action " .. shell_quote(action) .. suffix)
+			assert.assert_equal(action_code, 0, "Command failed: " .. action)
+			assert.assert_false(output:find("used the word", 1, true) ~= nil, "Parser rejected: " .. action)
+			assert.assert_false(output:find("can't see", 1, true) ~= nil, "Object missing: " .. action)
+			assert.assert_false(output:find("can't go", 1, true) ~= nil, "Route failed: " .. action)
+			if expected then
+				assert.assert_match(output, expected, "Unexpected output for: " .. action)
+			end
+		end
+
+		local score_code, score = run_command("lua5.4 llm.lua --action score" .. suffix)
+		assert.assert_equal(score_code, 0)
+		assert.assert_match(score, "Evidence found: 5 of 5")
+		assert.assert_match(score, "Suspects interviewed: 3 of 3")
+
+		local accuse_code, ending = run_command(
+			"lua5.4 llm.lua --action " .. shell_quote("accuse moriarty with letter") .. suffix)
+		assert.assert_equal(accuse_code, 0)
+		assert.assert_match(ending, "THE LIMEHOUSE KILLINGS %-%- SOLVED")
+
+		cleanup(savefile)
+	end)
+
+	t.it("should support the reported parser and interaction commands", function(assert)
+		local savefile = "/tmp/test-limehouse-command-regressions.sav"
+		cleanup(savefile)
+		local suffix = " --save " .. shell_quote(savefile) .. " --game limehouse-killings"
+		assert.assert_equal(run_command("lua5.4 llm.lua --new-game" .. suffix), 0)
+
+		local actions = {
+			{"examine me", "eyes are prehensile"},
+			{"examine myself", "eyes are prehensile"},
+			{"inspect path", "gravel path leads north"},
+			{"hints", "Hint:"},
+			{"examine fog", "fog swirls"},
+			{"examine gates", "iron gates"},
+			{"examine path", "gravel path"},
+			{"go north", "Entrance Hall"},
+			{"examine chandelier", "chandelier hangs"},
+			{"examine portraits", "Portraits of the Ashworth family"},
+			{"examine rug", "Persian rug"},
+			{"go down", "Kitchen"},
+			{"pull servant bell", "distant bell rings"},
+			{"use servant bell", "distant bell rings"},
+			{"go west", "Garden"},
+			{"take footprint cast", "take the footprint cast"},
+			{"go south", "Servants' Quarters"},
+			{"examine mister hudson", "Mr. Hudson"},
+			{"ask hudson", "What do you want to ask Mr. Hudson about"},
+			{"tell hudson about footprint-cast", "don't know anything about that"},
+			{"show footprint-cast to hudson", "doctor's right heel"},
+		}
+
+		for _, entry in ipairs(actions) do
+			local code, output = run_command(
+				"lua5.4 llm.lua --action " .. shell_quote(entry[1]) .. suffix)
+			assert.assert_equal(code, 0, "Command failed: " .. entry[1])
+			assert.assert_false(output:find("Runtime error", 1, true) ~= nil, "Runtime failed: " .. entry[1])
+			assert.assert_false(output:find("used the word", 1, true) ~= nil, "Parser rejected: " .. entry[1])
+			assert.assert_false(output:find("There was no verb", 1, true) ~= nil, "Verb missing: " .. entry[1])
+			assert.assert_false(output:find("nil", 1, true) ~= nil, "Nil leaked into output: " .. entry[1])
+			assert.assert_match(output, entry[2], "Unexpected output for: " .. entry[1])
+		end
+
+		cleanup(savefile)
+	end)
+
+	t.it("should keep Lestrade offstage until the case reaches act three", function(assert)
+		local savefile = "/tmp/test-limehouse-inspector-arrival.sav"
+		cleanup(savefile)
+		local suffix = " --save " .. shell_quote(savefile) .. " --game limehouse-killings"
+		assert.assert_equal(run_command("lua5.4 llm.lua --new-game" .. suffix), 0)
+		assert.assert_equal(run_command("lua5.4 llm.lua --action 'go north'" .. suffix), 0)
+		local code, output = run_command("lua5.4 llm.lua --action 'examine inspector'" .. suffix)
+		assert.assert_equal(code, 0)
+		assert.assert_match(output, "can't see any inspector here")
+		cleanup(savefile)
+	end)
+
+	t.it("should unlock and open the study door with Hudson's key", function(assert)
+		local savefile = "/tmp/test-limehouse-study-door.sav"
+		cleanup(savefile)
+		local suffix = " --save " .. shell_quote(savefile) .. " --game limehouse-killings"
+		assert.assert_equal(run_command("lua5.4 llm.lua --new-game" .. suffix), 0)
+
+		local actions = {
+			{"go north", "Entrance Hall"},
+			{"go down", "Kitchen"},
+			{"go west", "Garden"},
+			{"go south", "Servants' Quarters"},
+			{"ask hudson about key", "hands you the keyring"},
+			{"go north", "Garden"},
+			{"go east", "Kitchen"},
+			{"go up", "Entrance Hall"},
+			{"look", "closed and locked"},
+			{"unlock study door with keyring", "study door is now unlocked"},
+			{"look", "closed but unlocked"},
+			{"open study door", "You open the study door"},
+			{"look", "stands open, revealing the study beyond"},
+			{"go south", "Study"},
+		}
+
+		for _, entry in ipairs(actions) do
+			local code, output = run_command(
+				"lua5.4 llm.lua --action " .. shell_quote(entry[1]) .. suffix)
+			assert.assert_equal(code, 0, "Command failed: " .. entry[1])
+			assert.assert_match(output, entry[2], "Unexpected output for: " .. entry[1])
+		end
+
+		cleanup(savefile)
+	end)
+end)
+
+local success = test.summary()
+os.exit(success and 0 or 1)
diff --git a/tests/test_llm.lua b/tests/test_llm.lua
index d0fc38d..4f44a30 100644
--- a/tests/test_llm.lua
+++ b/tests/test_llm.lua
@@ -4,8 +4,7 @@ local test = require 'tests.test_framework'
 local runtime = require 'zilscript.runtime'
 
 local function run_command(command)
-	local quoted = "'" .. command:gsub("'", "'\\''") .. "'"
-	local pipe = assert(io.popen("zsh -lc " .. quoted .. " 2>&1", "r"))
+	local pipe = assert(io.popen(command .. " 2>&1", "r"))
 	local output = pipe:read("*a")
 	local ok, why, code = pipe:close()
 	local exit_code
@@ -19,24 +18,6 @@ local function run_command(command)
 	return exit_code, output
 end
 
-local function extract_json_line(output)
-	local json_line = nil
-	for line in output:gmatch("[^\r\n]+") do
-		if line:match("^%b{}$") then
-			json_line = line
-		end
-	end
-	return json_line
-end
-
-local function json_string_field(json, key)
-	return json:match('"' .. key .. '":"(.-)"')
-end
-
-local function json_bool_field(json, key)
-	return json:match('"' .. key .. '":([%a]+)')
-end
-
 local function read_file(path)
 	local file = io.open(path, "r")
 	if not file then
@@ -83,17 +64,8 @@ test.describe("LLM Mode", function(t)
 		cleanup(savefile)
 
 		local exit_code, output = run_command("lua5.4 llm.lua --new-game --save " .. shell_quote(savefile))
-		local json = extract_json_line(output)
-
 		assert.assert_equal(exit_code, 0)
-		assert.assert_not_nil(json)
-		if not json then
-			cleanup(savefile)
-			return
-		end
-		assert.assert_equal(json_string_field(json, "savefile"), savefile)
-		assert.assert_equal(json_string_field(json, "historyfile"), savefile .. ".actions")
-		assert.assert_equal(json_bool_field(json, "new_game"), "true")
+		assert.assert_match(output, "West of House")
 		assert.assert_equal(read_file(savefile .. ".actions"), "")
 
 		cleanup(savefile)
@@ -105,16 +77,10 @@ test.describe("LLM Mode", function(t)
 		run_command("lua5.4 llm.lua --new-game --save " .. shell_quote(savefile))
 
 		local exit_code, output = run_command("lua5.4 llm.lua --action \"open mailbox\" --save " .. shell_quote(savefile))
-		local json = extract_json_line(output)
 		local history = read_file(savefile .. ".actions") or ""
 
 		assert.assert_equal(exit_code, 0)
-		assert.assert_not_nil(json)
-		if not json then
-			cleanup(savefile)
-			return
-		end
-		assert.assert_equal(json_string_field(json, "historyfile"), savefile .. ".actions")
+		assert.assert_match(output, "mailbox")
 		assert.assert_match(history, '"game":"zork1"')
 		assert.assert_match(history, '"action":"open mailbox"')
 
@@ -131,16 +97,8 @@ test.describe("LLM Mode", function(t)
 			" && rm -f " .. shell_quote(savefile) ..
 			" && lua5.4 llm.lua --action \"take leaflet\" --save " .. shell_quote(savefile)
 		)
-		local json = extract_json_line(output)
-
 		assert.assert_equal(exit_code, 0)
-		assert.assert_not_nil(json)
-		if not json then
-			cleanup(savefile)
-			return
-		end
-		assert.assert_equal(json_string_field(json, "historyfile"), savefile .. ".actions")
-		assert.assert_match(json_string_field(json, "output") or "", "Taken")
+		assert.assert_match(output, "Taken")
 
 		cleanup(savefile)
 	end)
@@ -198,6 +156,30 @@ test.describe("LLM Mode", function(t)
 		cleanup(savefile)
 	end)
 
+	t.it("should preserve Limehouse noun lookup after taking all across processes", function(assert)
+		local savefile = "/tmp/test-llm-limehouse-vocabulary.sav"
+		cleanup(savefile)
+		local game = " --game limehouse-killings"
+		local save = " --save " .. shell_quote(savefile)
+
+		local new_code = run_command("lua5.4 llm.lua --new-game" .. save .. game)
+		local north_code = run_command("lua5.4 llm.lua --action \"go north\"" .. save .. game)
+		local take_code, take_output = run_command("lua5.4 llm.lua --action \"take all\"" .. save .. game)
+		local inventory_code, inventory_output = run_command("lua5.4 llm.lua --action \"inventory\"" .. save .. game)
+		local examine_code, examine_output = run_command("lua5.4 llm.lua --action \"examine glass\"" .. save .. game)
+
+		assert.assert_equal(new_code, 0)
+		assert.assert_equal(north_code, 0)
+		assert.assert_equal(take_code, 0)
+		assert.assert_match(take_output, "take the magnifying glass")
+		assert.assert_equal(inventory_code, 0)
+		assert.assert_match(inventory_output, "magnifying glass")
+		assert.assert_equal(examine_code, 0)
+		assert.assert_match(examine_output, "lens clear and strong")
+
+		cleanup(savefile)
+	end)
+
 	t.it("should replay legacy raw-line history", function(assert)
 		local savefile = "/tmp/test-llm-legacy.sav"
 		cleanup(savefile)
@@ -206,15 +188,8 @@ test.describe("LLM Mode", function(t)
 		file:close()
 
 		local exit_code, output = run_command("lua5.4 llm.lua --action \"take leaflet\" --save " .. shell_quote(savefile))
-		local json = extract_json_line(output)
-
 		assert.assert_equal(exit_code, 0)
-		assert.assert_not_nil(json)
-		if not json then
-			cleanup(savefile)
-			return
-		end
-		assert.assert_match(json_string_field(json, "output") or "", "Taken")
+		assert.assert_match(output, "Taken")
 
 		cleanup(savefile)
 	end)
@@ -227,16 +202,144 @@ test.describe("LLM Mode", function(t)
 		file:close()
 
 		local exit_code, output = run_command("lua5.4 llm.lua --action \"look\" --save " .. shell_quote(savefile))
-		local json = extract_json_line(output)
-
 		assert.assert_not_equal(exit_code, 0)
-		assert.assert_not_nil(json)
-		if not json then
-			cleanup(savefile)
-			return
+		assert.assert_match(output, "History file belongs to game")
+
+		cleanup(savefile)
+	end)
+
+	t.it("should preserve Lurking Horror clocks and function exits across processes", function(assert)
+		local savefile = "/tmp/test-llm-lurking-horror.sav"
+		cleanup(savefile)
+		local suffix = " --game lurkinghorror --save " .. shell_quote(savefile)
+
+		local code, opening = run_command("lua5.4 llm.lua --new-game" .. suffix)
+		assert.assert_equal(code, 0)
+		assert.assert_match(opening, "Release 15 / Serial number 870918")
+		local _, hacker_descriptions = opening:gsub(
+			"Sitting at a terminal is a hacker whom you recognize%.", "")
+		assert.assert_equal(hacker_descriptions, 1)
+		local x_code, x_output = run_command(
+			"lua5.4 llm.lua --action " .. shell_quote("x pc") .. suffix)
+		assert.assert_equal(x_code, 0)
+		assert.assert_match(x_output, "HELP key")
+		local inventory_code, inventory_output = run_command(
+			"lua5.4 llm.lua --action inventory" .. suffix)
+		assert.assert_equal(inventory_code, 0)
+		assert.assert_match(inventory_output, "assignment")
+		local talk_code, talk_output = run_command(
+			"lua5.4 llm.lua --action " .. shell_quote("talk to hacker") .. suffix)
+		assert.assert_equal(talk_code, 0)
+		assert.assert_true(not talk_output:match("I don't know the word"))
+		local help_code, help_output = run_command(
+			"lua5.4 llm.lua --action help" .. suffix)
+		assert.assert_equal(help_code, 0)
+		assert.assert_match(help_output, "Perhaps you should turn on the computer")
+		local outlet_code, outlet_output = run_command(
+			"lua5.4 llm.lua --action " .. shell_quote("examine outlet") .. suffix)
+		assert.assert_equal(outlet_code, 0)
+		assert.assert_match(outlet_output, "nothing special")
+		local ask_code = run_command(
+			"lua5.4 llm.lua --action " .. shell_quote("ask hacker") .. suffix)
+		assert.assert_equal(ask_code, 0)
+		local master_code, master_output = run_command(
+			"lua5.4 llm.lua --action " .. shell_quote("ask hacker about master") .. suffix)
+		assert.assert_equal(master_code, 0)
+		assert.assert_match(master_output, "master keys")
+		local power_code = run_command(
+			"lua5.4 llm.lua --action " .. shell_quote("turn on pc") .. suffix)
+		assert.assert_equal(power_code, 0)
+		local examine_code, examine_output = run_command(
+			"lua5.4 llm.lua --action " .. shell_quote("examine pc") .. suffix)
+		assert.assert_equal(examine_code, 0)
+		assert.assert_match(examine_output, "On the screen you see a HELP key%.")
+		local login_code, login_output = run_command(
+			"lua5.4 llm.lua --action " .. shell_quote("type 872325412") .. suffix)
+		assert.assert_equal(login_code, 0)
+		assert.assert_match(login_output, "PASSWORD PLEASE")
+		local password_code = run_command(
+			"lua5.4 llm.lua --action " .. shell_quote("type uhlersoth") .. suffix)
+		assert.assert_equal(password_code, 0)
+		local menu_code, menu_output = run_command(
+			"lua5.4 llm.lua --action " .. shell_quote("examine pc") .. suffix)
+		assert.assert_equal(menu_code, 0)
+		assert.assert_match(menu_output, "On the screen you see a menu box%.")
+		for _ = 1, 12 do
+			local wait_code, wait_output = run_command("lua5.4 llm.lua --action wait" .. suffix)
+			assert.assert_equal(wait_code, 0)
+			assert.assert_true(not wait_output:match("ERROR:"))
 		end
-		assert.assert_equal(json_bool_field(json, "ok"), "false")
-		assert.assert_match(json_string_field(json, "error") or "", "History file belongs to game")
+		local south_code, south_output = run_command("lua5.4 llm.lua --action south" .. suffix)
+		assert.assert_equal(south_code, 0)
+		assert.assert_match(south_output, "second floor of the Computer Center")
+		local look_code, look_output = run_command("lua5.4 llm.lua --action look" .. suffix)
+		assert.assert_equal(look_code, 0)
+		assert.assert_match(look_output, "Second Floor")
+		local button_code, button_output = run_command(
+			"lua5.4 llm.lua --action " .. shell_quote("examine call button") .. suffix)
+		assert.assert_equal(button_code, 0)
+		assert.assert_match(button_output, "up%-arrow or the down%-arrow")
+		local west_code, west_output = run_command("lua5.4 llm.lua --action west" .. suffix)
+		assert.assert_equal(west_code, 0)
+		assert.assert_match(west_output, "Kitchen")
+
+		cleanup(savefile)
+	end)
+
+	t.it("should continue Lurking Horror quit confirmation across processes", function(assert)
+		local savefile = "/tmp/test-llm-lurking-horror-quit.sav"
+		cleanup(savefile)
+		local suffix = " --game lurkinghorror --save " .. shell_quote(savefile)
+
+		local new_code = run_command("lua5.4 llm.lua --new-game" .. suffix)
+		assert.assert_equal(new_code, 0)
+		local quit_code, quit_output = run_command("lua5.4 llm.lua --action quit" .. suffix)
+		assert.assert_equal(quit_code, 0)
+		assert.assert_match(quit_output, "Do you wish to leave the game")
+		local yes_code, yes_output = run_command("lua5.4 llm.lua --action y" .. suffix)
+		assert.assert_equal(yes_code, 0)
+		assert.assert_true(not yes_output:match("I don't know the word"))
+
+		cleanup(savefile)
+	end)
+
+	t.it("should keep the Lurking Horror dream sequence interactive", function(assert)
+		local savefile = "/tmp/test-llm-lurking-horror-dream.sav"
+		cleanup(savefile)
+		local suffix = " --game lurkinghorror --save " .. shell_quote(savefile)
+		local commands = {
+			"turn on pc", "type 872325412", "type uhlersoth",
+			"edit classics paper", "touch paper", "read paper",
+			"touch more", "touch more", "touch more", "touch more",
+			"wait", "wait", "wait", "wait",
+		}
+
+		local new_code = run_command("lua5.4 llm.lua --new-game" .. suffix)
+		assert.assert_equal(new_code, 0)
+		for _, command in ipairs(commands) do
+			local code, output = run_command(
+				"lua5.4 llm.lua --action " .. shell_quote(command) .. suffix)
+			assert.assert_equal(code, 0)
+			assert.assert_true(not output:match("It sounds like supplication"))
+		end
+		local examine_code, examine_output = run_command(
+			"lua5.4 llm.lua --action " .. shell_quote("examine stone") .. suffix)
+		assert.assert_equal(examine_code, 0)
+		assert.assert_match(examine_output, "smooth, shiny piece")
+		local take_code, take_output = run_command(
+			"lua5.4 llm.lua --action " .. shell_quote("take stone") .. suffix)
+		assert.assert_equal(take_code, 0)
+		assert.assert_match(take_output, "Taken")
+		assert.assert_match(take_output, "dimness becomes darkness")
+		local first_wait_code, first_wait_output = run_command(
+			"lua5.4 llm.lua --action wait" .. suffix)
+		assert.assert_equal(first_wait_code, 0)
+		assert.assert_match(first_wait_output, "darkness before you, now visible, is a creature")
+		local second_wait_code, second_wait_output = run_command(
+			"lua5.4 llm.lua --action wait" .. suffix)
+		assert.assert_equal(second_wait_code, 0)
+		assert.assert_match(second_wait_output, "you fall unconscious")
+		assert.assert_match(second_wait_output, "Terminal Room")
 
 		cleanup(savefile)
 	end)
diff --git a/tests/test_runtime.lua b/tests/test_runtime.lua
index 3f103a0..8859345 100644
--- a/tests/test_runtime.lua
+++ b/tests/test_runtime.lua
@@ -107,6 +107,17 @@ test.describe("Runtime - Bootstrap Loading", function(t)
 		assert.assert_type(env.VERIFY, "function")
 	end)
 
+	t.it("should preserve signed Z-machine word arithmetic", function(assert)
+		local env = runtime.create_game_env()
+		runtime.init(env, true)
+
+		assert.assert_equal(env.SUB(4), -4)
+		assert.assert_equal(env.SUB(10, 3, 2), 5)
+		assert.assert_equal(env.SIGNED_WORD(0xffff), -1)
+		assert.assert_equal(env.SIGNED_WORD(0x8000), -32768)
+		assert.assert_equal(env.SIGNED_WORD(0x7fff), 32767)
+	end)
+
 	t.it("should link routine-valued properties defined later", function(assert)
 		local env = runtime.create_game_env()
 		assert.assert_true(runtime.init(env, true))
@@ -139,6 +150,30 @@ test.describe("Runtime - Bootstrap Loading", function(t)
 		assert.assert_equal(env.APPLY(env.GET(exit_ptr, 0)), 33)
 	end)
 
+	t.it("should evaluate conditional exit globals when the exit is used", function(assert)
+		local env = runtime.create_game_env()
+		assert.assert_true(runtime.init(env, true))
+
+		local code = compiler.compile(parser.parse([[
+			<GLOBAL DOOR-UNLOCKED <>>
+			<DIRECTIONS SOUTH>
+			<ROOM STUDY (DESC "study")>
+			<ROOM HALL
+				(DESC "hall")
+				(SOUTH TO STUDY IF DOOR-UNLOCKED ELSE "The door is locked.")>
+		]])).combined
+		assert.assert_true(runtime.execute(code, "conditional-exit", env, true))
+
+		local exit_ptr = env.GETPT(env.HALL, env.PQSOUTH)
+		assert.assert_equal(env.PTSIZE(exit_ptr), 4)
+		assert.assert_nil(env.VALUE(env.GETB(exit_ptr, 1)))
+		assert.assert_not_equal(env.GET(exit_ptr, 1), 0)
+
+		env.DOOR_UNLOCKED = true
+		assert.assert_true(env.VALUE(env.GETB(exit_ptr, 1)))
+		assert.assert_equal(env.GETB(exit_ptr, 0), env.STUDY)
+	end)
+
 	t.it("should restore captured scalar state on restart", function(assert)
 		local env = runtime.create_game_env()
 		runtime.init(env, true)
diff --git a/zilscript/bootstrap.lua b/zilscript/bootstrap.lua
index fcd6304..13a5e7e 100644
--- a/zilscript/bootstrap.lua
+++ b/zilscript/bootstrap.lua
@@ -13,6 +13,10 @@ ZIL_ObjectFlags = {
 }
 
 D = 0xBAADF00D
+N = 0xBAADF00E
+TELL_A = 0xBAADF00F
+TELL_THE = 0xBAADF010
+TELL_CTHE = 0xBAADF011
 
 OQANY=1
 
@@ -29,6 +33,22 @@ P1QVERB=1
 P1QADJECTIVE=2
 P1QDIRECTION=3
 
+-- Standard room-exit property layouts.  Some Infocom sources (including
+-- The Lurking Horror) treat these as substrate-provided constants and leave
+-- their local declarations commented out.
+REXIT=0
+UEXIT=1
+NEXIT=2
+FEXIT=3
+CEXIT=4
+DEXIT=5
+NEXITSTR=0
+FEXITFCN=0
+CEXITFLAG=1
+CEXITSTR=1
+DEXITOBJ=1
+DEXITSTR=1
+
 SH=128
 SC=64
 SIR=32
@@ -66,11 +86,17 @@ FLAGS = {}
 FUNCTIONS = {}
 _DIRECTIONS = {}
 
+_GLOBAL_FLAG_SLOTS = {}    -- global name → Z-machine variable number
+_GLOBAL_FLAG_NAMES = {}    -- Z-machine variable number → global name
+_next_global_flag_slot = 15 -- 0 is the stack; 1..15 are local variables
+
 DESCS = {}
 DIRS = {}
 
 _VTBL = {}
 _OTBL = 0  -- mem address of 256×2-byte object pointer table; set on first DECL_OBJECT
+_CHILD_TBL = 0 -- parent object id -> first child object id
+_SIBLING_TBL = 0 -- object id -> next sibling object id
 
 T = true
 CR = "\n"
@@ -93,12 +119,15 @@ M_ENTER = 2
 M_LOOK = 3
 M_FLASH = 4
 M_OBJDESC = 5
+M_LEAVE = M_END
+M_CONTAINER = M_OBJECT
 
 local mem
 local _obj_count = 0  -- number of declared objects; object IDs are 1.._obj_count
 local _act_count = 0  -- number of registered actions; action IDs are 1.._act_count
 local _act_fn_to_id = {}  -- build-time reverse-lookup: fn_idx -> action_id
 local _pending_syntax = {}  -- SYNTAX entries deferred until action functions are defined
+local _pending_synonyms = {} -- vocabulary aliases applied after all object words exist
 local restart_snapshot
 local suggestions = {
 	READBIT = "READ",
@@ -270,6 +299,26 @@ mem = setmetatable({size=0},{__index={
 	end
 }})
 
+-- The Z-machine header occupies address zero in a story file, while this
+-- runtime keeps its compact object/table heap separately.  Model the handful
+-- of writable header bytes used by Infocom ZIL without reserving or aliasing
+-- heap memory.
+local z_header = {}
+
+function SET_HEADER(release, serial)
+	release = tonumber(release) or 0
+	z_header[2] = release & 0xff
+	z_header[3] = (release >> 8) & 0xff
+	serial = tostring(serial or "000000")
+	serial = (serial .. "000000"):sub(1, 6)
+	for i = 1, 6 do
+		z_header[17 + i] = serial:byte(i)
+	end
+	return true
+end
+
+SET_HEADER(0, "000000")
+
 local cache = {
 	verbs = {},
 	words = {},
@@ -294,6 +343,29 @@ end
 
 local learn
 
+local function merge_dictionary_word(target, source)
+	local old = mem:read(7, target)
+	local new = mem:read(7, source)
+	local old_flags = old:byte(5) or 0
+	local new_flags = new:byte(5) or 0
+	if old_flags == 0 then
+		mem:write(new, target)
+		return
+	end
+	local old_primary = old_flags & 3
+	local new_primary = new_flags & 3
+	local secondary = old:byte(7) or 0
+	if new_primary ~= old_primary then
+		secondary = new:byte(6) or secondary
+	end
+	mem:write(string.char(
+		old:byte(1), old:byte(2), old:byte(3), old:byte(4),
+		((old_flags | new_flags) & ~3) | old_primary,
+		old:byte(6) or 0,
+		secondary
+	), target)
+end
+
 local function register(tbl, value)
 	local n = 0
 	if type(value) == "string" then value = value:lower() end
@@ -523,10 +595,38 @@ end
 
 function TELL(...)
 	local object = false
+	local number = false
 	for i = 1, select("#", ...) do
 		local v = select(i, ...)
-		if v == D then object = true
-		elseif object then object = false io_write(GETP(v, _G["PQDESC"]))
+		if v == D then object = "D"
+		elseif v == TELL_A then object = "A"
+		elseif v == TELL_THE then object = "THE"
+		elseif v == TELL_CTHE then object = "CTHE"
+		elseif v == N then number = true
+		elseif object then
+			local token = object
+			object = false
+			if v then
+				local printer = token == "A" and rawget(_G, "PRINTA")
+					or token == "THE" and rawget(_G, "THE_PRINT")
+					or token == "CTHE" and rawget(_G, "CTHE_PRINT")
+					or token == "D" and rawget(_G, "DPRINT")
+				if printer then
+					APPLY(printer, v)
+				else
+					local desc = GETP(v, _G["PQDESC"]) or ""
+					if token == "A" then
+						io_write(desc:match("^[AEIOUaeiou]") and "an " or "a ")
+					elseif token == "THE" then
+						io_write("the ")
+					elseif token == "CTHE" then
+						io_write("The ")
+					end
+					io_write(desc)
+				end
+			end
+		elseif number then number = false io_write(tostring(v))
+		elseif v == nil or v == false then -- FALSE expressions print nothing
 		elseif type(v) == "number" then io_write(mem:string(v))
 		elseif v == '>' then -- skip
 		else io_write(tostring(v)) end
@@ -615,6 +715,7 @@ end
 
 -- Logic / bitwise
 function NOT(a) return not a or a == 0 end
+function ZIL_TRUE(value) return value ~= nil and value ~= false and value ~= 0 end
 function PASS(a) return a end
 function BAND(a, b) return (a or 0) & (b or 0) end
 function BOR(a, b) return (a or 0) | (b or 0) end
@@ -635,6 +736,13 @@ function EQUALQ(a, ...)
 end
 function GASSIGNEDQ(name) return rawget(_G, tostring(name)) ~= nil end
 function NEQUALQ(a, b) return not EQUALQ(a, b) end
+function SIGNED_WORD(value)
+	value = value or 0
+	if type(value) == "number" and value >= 0x8000 and value <= 0xffff then
+		return value - 0x10000
+	end
+	return value
+end
 function GQ(a, b) return (a or 0) > (b or 0) end
 function LQ(a, b) return (a or 0) < (b or 0) end
 function GEQ(a, b) return (a or 0) >= (b or 0) end
@@ -642,9 +750,21 @@ function LEQ(a, b) return (a or 0) <= (b or 0) end
 function ZEROQ(a) return (a or 0) == 0 end
 function ONEQ(a) return a == 1 end
 function ADD(a, b) return (a or 0) + (b or 0) end
-function SUB(a, b) return (a or 0) - (b or 0) end
+function SUB(a, ...)
+	if select("#", ...) == 0 then return -(a or 0) end
+	local result = a or 0
+	for i = 1, select("#", ...) do
+		result = result - (select(i, ...) or 0)
+	end
+	return result
+end
 function DIV(a, b) return (a or 0) // (b or 0) end
 function MUL(a, b) return (a or 0) * (b or 0) end
+function MOD(a, b) return (a or 0) % (b or 0) end
+
+-- Audio is optional in the current text-only host.  Preserve the opcode's
+-- successful control-flow behavior even when no sound backend is attached.
+function SOUND(...) return true end
 
 -- function GQ(a, b) return a > b end
 -- IGRTRQ = GQ
@@ -654,32 +774,101 @@ MULL = MUL
 -- Object / room ops
 -- Returns the mem address of object num's property table block.
 -- _OTBL is the base of a 256×2-byte array allocated in mem by the first DECL_OBJECT call.
-local function getobj(num) return mem:word(_OTBL + (num-1)*2) end
-
--- VALUE function: identity function for ZIL's <VALUE var> form
--- In ZIL, <VALUE var> gets the runtime value of a variable
-function VALUE(x) return x end
+local function getobj(num)
+	if type(num) ~= "number" or num <= 0 then return nil end
+	local pointer = mem:word(_OTBL + (num-1)*2)
+	return pointer ~= 0 and pointer or nil
+end
+
+-- In ZIL, <VALUE var> gets the runtime value of a variable. Conditional exits
+-- store a variable number in their property bytes, so resolve those numbers
+-- back to the live Lua global; other values retain the legacy identity behavior.
+function VALUE(x)
+	if type(x) == "number" then
+		local gname = _GLOBAL_FLAG_NAMES[x]
+		if gname then
+			return rawget(_G, gname)
+		end
+	end
+	return x
+end
 
 function LOC(obj) return GETP(obj, PQLOC) end
 function INQ(obj, room) return GETP(obj, PQLOC) == room end
-function MOVE(obj, dest) PUTP(obj, PQLOC, dest) end
-function REMOVE(obj) PUTP(obj, PQLOC, 0) end
 
-function FIRSTQ(obj)
-	for n = 1, _obj_count do
-		if GETP(n, PQLOC) == obj then return n end
+local function unlink_object(obj)
+	local parent = LOC(obj)
+	if not parent or parent == 0 then return end
+	local child = mem:byte(_CHILD_TBL + parent)
+	local previous = 0
+	while child ~= 0 do
+		if child == obj then
+			local next_sibling = mem:byte(_SIBLING_TBL + child)
+			if previous == 0 then
+				mem:write(makebyte(next_sibling), _CHILD_TBL + parent)
+			else
+				mem:write(makebyte(next_sibling), _SIBLING_TBL + previous)
+			end
+			mem:write(makebyte(0), _SIBLING_TBL + child)
+			return
+		end
+		previous = child
+		child = mem:byte(_SIBLING_TBL + child)
 	end
 end
 
+function MOVE(obj, dest)
+	unlink_object(obj)
+	PUTP(obj, PQLOC, dest)
+	if dest and dest ~= 0 then
+		local first = mem:byte(_CHILD_TBL + dest)
+		mem:write(makebyte(first), _SIBLING_TBL + obj)
+		mem:write(makebyte(obj), _CHILD_TBL + dest)
+	end
+end
+
+function REMOVE(obj)
+	unlink_object(obj)
+	PUTP(obj, PQLOC, 0)
+end
+
+function FIRSTQ(obj)
+	local child = mem:byte(_CHILD_TBL + obj)
+	return child ~= 0 and child or nil
+end
+
 function NEXTQ(obj)
-	local parent = GETP(obj, PQLOC)
-	local found = false
-	for n = 1, _obj_count do
-		if GETP(n, PQLOC) == parent then
-			if found then return n end
-			if n == obj then found = true end
+	local sibling = mem:byte(_SIBLING_TBL + obj)
+	return sibling ~= 0 and sibling or nil
+end
+
+function MAP_CONTENTS(container, callback, end_callback)
+	local object = FIRSTQ(container)
+	local result
+	while object do
+		local next_object = NEXTQ(object)
+		result = callback(object, next_object)
+		object = next_object
+	end
+	if end_callback then return end_callback() end
+	return result
+end
+
+function MAP_DIRECTIONS(room, callback, end_callback)
+	local directions = {}
+	for _, property in pairs(_DIRECTIONS) do
+		directions[#directions + 1] = property
+	end
+	table.sort(directions)
+	local result
+	for _, property in ipairs(directions) do
+		local property_table = GETPT(room, property)
+		if property_table then
+			result = callback(property, property_table)
 		end
 	end
+	if end_callback then return end_callback() end
+	return result
 end
 
 learn = function(word, atom, value)
@@ -718,7 +907,7 @@ learn = function(word, atom, value)
 	for _, syn in ipairs(cache.synonyms[word_key] or {}) do
 		local syn_key = syn:lower():sub(1, 6)
 		if cache.words[syn_key] then
-			mem:write(mem:read(8, cache.words[word_key]), cache.words[syn_key])
+			merge_dictionary_word(cache.words[syn_key], cache.words[word_key])
 		end
 	end
 	
@@ -752,6 +941,7 @@ function FSETQ(obj, flag)
 end
 function GETPT(obj, prop)
 	local tbl = getobj(obj)
+	if not tbl then return nil end
 	local l = mem:byte(tbl)+tbl+1
 	local pname, psize = mem:byte(l), mem:byte(l+1)
 	local header = 2
@@ -762,6 +952,7 @@ function GETPT(obj, prop)
 	end
 end
 function PTSIZE(ptr)
+	if not ptr then return 0 end
 	return mem:byte(ptr-1)
 end
 function PUTP(obj, prop, val)
@@ -789,7 +980,11 @@ function GETP(obj, prop)
 	local ptr = GETPT(obj, prop)
 	local ptsize = PTSIZE(ptr)
 	if ptsize == 1 then return mem:byte(ptr) end
-	if ptsize == 2 then return mem:word(ptr) ~= 0 and mem:string(mem:word(ptr)) or nil end
+	if ptsize == 2 then
+		local value = mem:word(ptr)
+		if prop == rawget(_G, "PQTHINGS") then return value ~= 0 and value or nil end
+		return value ~= 0 and mem:string(value) or nil
+	end
 	if ptsize == 4 then return mem:dword(ptr) end
 	if ptsize == 8 then return mem:qword(ptr) end
 	assert(false, "Unsupported property to get")
@@ -831,9 +1026,21 @@ function DECL_OBJECT(name)
 	if not _OTBL or _OTBL == 0 then
 		-- Allocate the 256×2-byte object pointer table on first use
 		_OTBL = mem:write(string.rep('\0\0', 256))
-	end
-	_obj_count = _obj_count + 1
-	assert(_obj_count <= 255, "Too many objects (max 255)")
+		_CHILD_TBL = mem:write(string.rep('\0', 256))
+		_SIBLING_TBL = mem:write(string.rep('\0', 256))
+	end
+	-- Direction properties are passed through PRSO for WALK. Several Infocom
+	-- parsers also use numeric pseudo-objects such as IT, so assigning an object
+	-- the same number as a direction makes a walk look like pronoun substitution.
+	-- Leave holes for direction-property numbers when allocating object IDs.
+	repeat
+		_obj_count = _obj_count + 1
+		local is_direction = false
+		for _, property in pairs(_DIRECTIONS) do
+			if property == _obj_count then is_direction = true break end
+		end
+	until not is_direction
+	assert(_obj_count <= 255, "Too many objects (max 255) while declaring " .. tostring(name))
 	if name then declared_objects[name] = _obj_count end
 	return _obj_count
 end
@@ -852,6 +1059,10 @@ function GLOBAL_REF(name)
 	return {__global_ref = name}
 end
 
+function GLOBAL_FLAG_REF(name)
+	return {__global_ref = name}
+end
+
 local pending_routine_refs = {}
 
 function ROUTINE_REF(name)
@@ -875,10 +1086,13 @@ end
 
 function DEFINE_ROUTINE(name, routine)
 	assert(type(routine) == "function", "DEFINE_ROUTINE expected function for "..tostring(name))
+	-- Register every named routine when it is defined.  A routine can otherwise
+	-- receive its first numeric pointer only when GO queues it; restored llm.lua
+	-- sessions skip GO, leaving that saved pointer beyond the rebuilt table.
+	local routine_index = fn(routine)
 	local pending = pending_routine_refs[name]
 	if not pending then return routine end
 
-	local routine_index = fn(routine)
 	for _, ref in ipairs(pending) do
 		if ref.kind == "exit" then
 			local ptr = GETPT(ref.object, ref.property)
@@ -892,6 +1106,17 @@ function DEFINE_ROUTINE(name, routine)
 	return routine
 end
 
+local function sorted_keys(tbl)
+	local keys = {}
+	for key in pairs(tbl) do
+		keys[#keys + 1] = key
+	end
+	table.sort(keys, function(a, b)
+		return tostring(a) < tostring(b)
+	end)
+	return keys
+end
+
 function OBJECT(object)
 	local function resolve_global(value)
 		if type(value) == "string" then
@@ -920,7 +1145,12 @@ function OBJECT(object)
 	local n = _G[object_name]
 	local t = {string.char(#object_name), object_name}
 	assert(n, "DECL_OBJECT not called for "..tostring(object_name))
-	for k, v in pairs(object) do
+	-- Object declarations are Lua tables, whose hash iteration order varies from
+	-- process to process.  Property numbers and function-pointer slots are both
+	-- assigned while walking these fields, so an unstable order makes a memory
+	-- dump written by one llm.lua process incompatible with the next one.
+	for _, k in ipairs(sorted_keys(object)) do
+		local v = object[k]
 		if k == "ZIL_NAME" then
 		elseif k == "SYNONYM" then
 			local body = table.concat2(v, function(syn)
@@ -951,6 +1181,8 @@ function OBJECT(object)
 		-- using PQACTION for ACTION property, commented out original function support
 		elseif k == "ACTION" or k == "DESCFCN" then 
 			table.insert(t, makeprop(function_prop(v, k, n), k))
+		elseif k == "THINGS" and type(v) == "number" then
+			table.insert(t, makeprop(makeword(v), k))
 		elseif type(v) == 'string' then table.insert(t, makeprop(mem:stringprop(v), k))
 		elseif type(v) == 'number' then table.insert(t, makeprop(makebyte(v), k))
 		elseif type(v) == 'function' then table.insert(t, makeprop(mem:stringprop(fn(v)), k))
@@ -979,13 +1211,26 @@ function OBJECT(object)
 					error(string.format("Unresolved exit target for %s.%s", tostring(object_name), tostring(k)))
 				end
 				str = string.char(v[1]) -- UEXIT = 1
-				local say = v.say and mem:write(v.say.."\0") or 0
+				local say = v.say and mem:writestring2(v.say) or 0
 				if v.door ~= nil then
 					local door = type(v.door) == "boolean" and (v.door and 1 or 0) or v.door
 					str = str..string.char(door)..makeword(say)..string.char(0) -- DEXIT = 5
 				elseif v.flag ~= nil then
-					local flag = type(v.flag) == "boolean" and (v.flag and 1 or 0) or v.flag
-					str = str..string.char(flag)..makeword(say) -- CEXIT = 4
+					local flag_val = v.flag
+					if type(flag_val) == "table" and flag_val.__global_ref then
+						local gname = flag_val.__global_ref
+						if not _GLOBAL_FLAG_SLOTS[gname] then
+							_next_global_flag_slot = _next_global_flag_slot + 1
+							_GLOBAL_FLAG_SLOTS[gname] = _next_global_flag_slot
+							_GLOBAL_FLAG_NAMES[_next_global_flag_slot] = gname
+						end
+						local variable = _GLOBAL_FLAG_SLOTS[gname]
+						assert(variable <= 255, "Too many global variables for conditional exits (max 240)")
+						str = str..string.char(variable)..makeword(say) -- CEXIT = 4
+					else
+						flag_val = type(flag_val) == "boolean" and (flag_val and 1 or 0) or flag_val
+						str = str..string.char(flag_val)..makeword(say) -- CEXIT = 4
+					end
 				end
 			end
 			table.insert(t, makeprop(str, k))
@@ -1004,6 +1249,21 @@ function OBJECT(object)
 	end
 	local tbl_addr = mem:write(table.concat(t) .. "\0\0")
 	mem:write(makeword(tbl_addr), _OTBL + (n-1)*2)
+	-- Initial object trees retain declaration order. Runtime MOVE uses the
+	-- Z-machine rule of inserting the object at the head of its new parent.
+	local parent = LOC(n)
+	if parent and parent ~= 0 then
+		local first = mem:byte(_CHILD_TBL + parent)
+		if first == 0 then
+			mem:write(makebyte(n), _CHILD_TBL + parent)
+		else
+			local sibling = first
+			while mem:byte(_SIBLING_TBL + sibling) ~= 0 do
+				sibling = mem:byte(_SIBLING_TBL + sibling)
+			end
+			mem:write(makebyte(n), _SIBLING_TBL + sibling)
+		end
+	end
 end
 
 function REST(s, i)
@@ -1014,6 +1274,13 @@ function REST(s, i)
 	return s:sub((i or 1) + 1)
 end
 
+function BACK(s, i)
+	if type(s) == 'number' then
+		return s-(i or 1)
+	end
+	error("BACK: unsupported type " .. type(s))
+end
+
 function EMPTYQ(s)
 	if s == nil then return true end
 	if type(s) == 'table' then
@@ -1099,11 +1366,21 @@ end
 
 function PUT(obj, i, val)
 	assert(type(obj) == 'number', "PUT: Only number types, not "..type(obj))
+	if obj == 0 then
+		val = type(val) == 'function' and fn(val) or val or 0
+		z_header[i * 2] = val & 0xff
+		z_header[i * 2 + 1] = (val >> 8) & 0xff
+		return
+	end
 	mem:write(makeword(type(val) == 'function' and fn(val) or val or 0), obj+i*2)
 end
 
 function PUTB(s, i, val) 
 	assert(type(s) == 'number', "PUTB: Only number types, not "..type(s))
+	if s == 0 then
+		z_header[i] = val & 0xff
+		return
+	end
 	mem:write(makebyte(val), s+i)
 end
 -- function GET(t, i) return type(t) == 'table' and t[i * 2] or 0 end
@@ -1111,7 +1388,7 @@ end
 
 function GETB(s, i)
 	assert(type(s) == 'number', "GETB: Only number types")
-	if s == 0 then return GET(s) end
+	if s == 0 then return z_header[i or 0] or 0 end
 	return mem:byte(s+i)
 	-- if s == 0 then return GET(s)
 	-- elseif type(s) == 'string' then return i==0 and #i or s:byte(i)
@@ -1123,14 +1400,6 @@ function GETB(s, i)
 end
 
 function GET(s, i)
-	if s == 0 then
-		-- Z-machine header mockup
-		s = {
-			[0] = 3,       -- version (not actually used)
-			[1] = 15,      -- release number (Release 15)
-			[8] = 0,       -- Flags 2 (transcript bit is bit 0)
-		}
-	end
 	if not i then return 0 end
 	if type(s) == 'number' then
 		return (GETB(s,i*2) or 0)|((GETB(s,i*2+1) or 0)<<8)
@@ -1143,6 +1412,27 @@ end
 
 function DIRECTIONS(...)
 	for _, dir in ipairs {...} do
+		-- Top-level object declarations are emitted before directive bodies. If
+		-- the next direction-property number aliases the numeric pseudo-object
+		-- IT, swap that still-forward declaration with the final object declared
+		-- in this module. Otherwise WALK WEST can look like pronoun substitution.
+		local next_property = 1
+		for _ in pairs(PROPERTIES) do next_property = next_property + 1 end
+		for object_name, object_id in pairs(declared_objects) do
+			if object_name == "IT" and object_id == next_property
+					and not getobj(object_id) then
+				for swap_name, swap_id in pairs(declared_objects) do
+					if swap_id == _obj_count and not getobj(swap_id) then
+						declared_objects[swap_name] = object_id
+						_G[swap_name] = object_id
+						break
+					end
+				end
+				declared_objects[object_name] = _obj_count
+				_G[object_name] = _obj_count
+				break
+			end
+		end
 		_DIRECTIONS[dir] = learn(dir, PSQDIRECTION, PROPERTIES)
 		if type(DIRS) == "table" and dir ~= "IN" and dir ~= "OUT" then
 			table.insert(DIRS, dir:lower())
@@ -1182,7 +1472,7 @@ function SYNTAX(syn)
 		error(string.format("SYNTAX for verb '%s' is missing ACTION", syn.VERB))
 	end
 	-- Defer if the action function isn't defined yet (e.g., syntax.zil loaded before verbs.zil)
-	if _G[syn.ACTION] == nil then
+	if _G[syn.ACTION] == nil or (syn.PREACTION and _G[syn.PREACTION] == nil) then
 		table.insert(_pending_syntax, syn)
 		return
 	end
@@ -1218,12 +1508,16 @@ function SYNTAX(syn)
 end
 
 function FINALIZE_SYNTAX()
-	if #_pending_syntax == 0 then return end
 	local pending = _pending_syntax
 	_pending_syntax = {}
 	for _, syn in ipairs(pending) do
 		SYNTAX(syn)
 	end
+	local synonyms = _pending_synonyms
+	_pending_synonyms = {}
+	for _, args in ipairs(synonyms) do
+		SYNONYM(table.unpack(args))
+	end
 end
 
 function BUZZ(...)
@@ -1233,6 +1527,11 @@ function BUZZ(...)
 	end
 end
 
+function DEFER_SYNONYM(...)
+	_pending_synonyms[#_pending_synonyms + 1] = {...}
+	return true
+end
+
 function SYNONYM(verb, ...)
 	verb = verb:lower():sub(1, 6)
 	cache.synonyms[verb] = {...}
@@ -1240,9 +1539,14 @@ function SYNONYM(verb, ...)
 		-- Truncate to 6 chars (Z-machine dictionary convention)
 		local syn_key = syn:lower():sub(1, 6)
 		if cache.words[verb] then
-			cache.words[syn_key] = mem:write(mem:read(8, cache.words[verb]))
+			if cache.words[syn_key] then
+				merge_dictionary_word(cache.words[syn_key], cache.words[verb])
+			else
+				cache.words[syn_key] = mem:write(mem:read(7, cache.words[verb]))
+			end
 		else
-			cache.words[syn_key] = mem:write(string.rep('\0', 8))
+			cache.words[syn_key] = cache.words[syn_key]
+				or mem:write(string.rep('\0', 7))
 		end
 		_G['WQ'..syn:upper()] = cache.words[syn_key]
   end
@@ -1259,6 +1563,32 @@ function ITABLE(size, maybe_size)
 	return address
 end
 
+function ITABLE_WORDS(count, pattern_width)
+	count = count or 0
+	pattern_width = pattern_width or 1
+	return mem:write(string.rep("\0\0", count * pattern_width))
+end
+
+function STRING_TABLE(value, with_length)
+	value = tostring(value or "")
+	if with_length then
+		assert(#value <= 255, "Length-prefixed STRING table exceeds 255 bytes")
+		return mem:write(string.char(#value) .. value)
+	end
+	return mem:write(value)
+end
+
+function PSEUDO_TABLE(...)
+	local entries = {...}
+	local words = {}
+	for _, entry in ipairs(entries) do
+		local adjective = entry[1] and VOC(entry[1], ADJECTIVE) or 0
+		local noun = entry[2] and VOC(entry[2], NOUN) or 0
+		words[#words + 1] = makeword(adjective) .. makeword(noun)
+	end
+	return mem:write(makeword(#entries * 2) .. table.concat(words))
+end
+
 local pending_table_refs = {}
 
 local function table_word(value, pending, offset)
@@ -1646,6 +1976,39 @@ function RESTORE(filename)
 		end
 	end
 
+	-- Version 2 saves append the vocabulary address map after the scalar globals.
+	-- Dictionary storage is rebuilt whenever a game process starts, and its
+	-- addresses are not guaranteed to match those in the process that wrote the
+	-- save.  Restore the saved map so READ and parser word lookups point into the
+	-- memory image we just loaded.
+	if magic == SAVE_MAGIC_V2 then
+		local section_type = file:read(1)
+		if section_type and section_type:byte() == 4 then
+			local count_bytes = file:read(2)
+			if not count_bytes or #count_bytes < 2 then
+				file:close()
+				return false
+			end
+			local cw_count = count_bytes:byte(1) | (count_bytes:byte(2) << 8)
+			local restored_words = {}
+			for _ = 1, cw_count do
+				local nl = file:read(1)
+				if not nl then
+					file:close()
+					return false
+				end
+				local word = file:read(nl:byte())
+				local addr_bytes = file:read(8)
+				if not word or not addr_bytes or #addr_bytes < 8 then
+					file:close()
+					return false
+				end
+				restored_words[word] = read_int64(addr_bytes)
+			end
+			cache.words = restored_words
+		end
+	end
+
 	-- Clean up state globals in the game environment (env) that weren't in the save file.
 	-- _G inside the bootstrap IS the env table (env._G = env).
 	local game_env = _G
@@ -1664,4 +2027,3 @@ end
 _LLM_RESTORED = false
 
 -- === Done ===
-print("ZIL runtime initialized.")
diff --git a/zilscript/compiler/fields.lua b/zilscript/compiler/fields.lua
index 3ab91c6..c2be76b 100644
--- a/zilscript/compiler/fields.lua
+++ b/zilscript/compiler/fields.lua
@@ -30,6 +30,14 @@ local function writeListString(buf, node, compiler)
   end, compiler)
 end
 
+-- Vocabulary is player-facing text, not a Lua identifier. Preserve ZIL word
+-- spelling (notably hyphens) so commands such as "take torn-page" resolve.
+local function writeWordList(buf, node, compiler)
+  writeFormattedList(buf, node, function(child)
+    return string.format("%q", tostring(child.value))
+  end, compiler)
+end
+
 -- Write plain list
 local function writeList(buf, node, compiler)
   writeFormattedList(buf, node, nil, compiler)
@@ -86,8 +94,8 @@ end
 -- Field writer dispatch table
 Fields.FIELD_WRITERS = {
   FLAGS = writeListString,
-  SYNONYM = writeListString,
-  ADJECTIVE = writeListString,
+  SYNONYM = writeWordList,
+  ADJECTIVE = writeWordList,
   DESC = writeStringField,
   LDESC = writeStringField,
   FDESC = writeStringField,
@@ -124,7 +132,11 @@ function Fields.writeNav(buf, node, compiler)
     if utils.safeget(parts[5], 'value') == "IS" and parts[6] then
       cond = "door = "..cond
     else
-      cond = "flag = "..cond
+      if parts[4].type == "ident" or parts[4].type == "symbol" then
+        cond = "flag = GLOBAL_FLAG_REF(\"" .. cond .. "\")"
+      else
+        cond = "flag = "..cond
+      end
     end
     
     local room = compiler.value(parts[2])
@@ -151,6 +163,18 @@ end
 
 -- Write field using appropriate writer or default
 function Fields.writeField(buf, node, field_name, compiler)
+  if field_name == "THINGS" and node[2] and node[2].type == "expr"
+      and node[2].name == "PSEUDO" then
+    buf.write("PSEUDO_TABLE(")
+    for i, tuple in ipairs(node[2]) do
+      if i > 1 then buf.write(", ") end
+      local adjective = tuple[1] and tuple[1].value
+      local noun = tuple[2] and tuple[2].value
+      buf.write("{%s, %q}", adjective and string.format("%q", adjective) or "nil", noun)
+    end
+    buf.write(")")
+    return
+  end
   local writer = Fields.FIELD_WRITERS[field_name] or writeValueField
   writer(buf, node, compiler)
 end
diff --git a/zilscript/compiler/forms.lua b/zilscript/compiler/forms.lua
index 94e268f..090d913 100644
--- a/zilscript/compiler/forms.lua
+++ b/zilscript/compiler/forms.lua
@@ -30,6 +30,19 @@ end
 -- Helper: Generate a table constructor call (LTABLE, TABLE share same pattern)
 local function writeTableCall(buf, name, node, printNode)
   local first_is_storage_spec = utils.safeget(node[1], 'type') == "list"
+  if first_is_storage_spec then
+    local has_string, has_length = false, false
+    for _, spec in ipairs(node[1]) do
+      has_string = has_string or spec.value == "STRING"
+      has_length = has_length or spec.value == "LENGTH"
+    end
+    if has_string and node[2] and node[2].type == "string" and #node == 2 then
+      buf.write("STRING_TABLE(")
+      printNode(buf, node[2], 0)
+      buf.write(", %s)", has_length and "true" or "false")
+      return
+    end
+  end
   local start = first_is_storage_spec and 2 or 1
   buf.write("%s(", name)
   for i = start, #node do
@@ -117,6 +130,117 @@ end
 function Forms.createHandlers(compiler, printNode)
   local form = {}
 
+  local function writeMap(buf, node, indent, runtime_name, binder_count)
+    local bindings = node[1]
+    if not bindings or bindings.type ~= "list" or #bindings < binder_count + 1 then
+      error(runtime_name .. " requires a binding list")
+    end
+
+    local saved_local_vars = {}
+    for k, v in pairs(compiler.local_vars) do saved_local_vars[k] = v end
+    local binders = {}
+    for i = 1, binder_count do
+      compiler.registerLocalVar(bindings[i])
+      binders[i] = compiler.localVarName(bindings[i])
+    end
+
+    local end_clause
+    local body_start = 2
+    if node[2] and node[2].type == "list"
+        and utils.safeget(node[2][1], "value") == "END" then
+      end_clause = node[2]
+      body_start = 3
+    end
+
+    buf.write("%s(", runtime_name)
+    printNode(buf, bindings[#bindings], indent + 1)
+    buf.write(", function(%s) local __tmp", table.concat(binders, ", "))
+    for i = body_start, #node do
+      buf.write("; ")
+      if utils.needReturn(node[i]) then buf.write("__tmp = ") end
+      printNode(buf, node[i], indent + 1)
+    end
+    buf.write("; return __tmp end, ")
+    if end_clause then
+      buf.write("function() local __tmp")
+      for i = 2, #end_clause do
+        buf.write("; ")
+        if utils.needReturn(end_clause[i]) then buf.write("__tmp = ") end
+        printNode(buf, end_clause[i], indent + 1)
+      end
+      buf.write("; return __tmp end")
+    else
+      buf.write("nil")
+    end
+    buf.write(")")
+    compiler.local_vars = saved_local_vars
+  end
+
+  form["MAP-DIRECTIONS"] = function(buf, node, indent)
+    writeMap(buf, node, indent, "MAP_DIRECTIONS", 2)
+  end
+
+  form["MAP-CONTENTS"] = function(buf, node, indent)
+    local bindings = node[1]
+    local binder_count = bindings and (#bindings - 1) or 1
+    writeMap(buf, node, indent, "MAP_CONTENTS", binder_count)
+  end
+
+  form["RARG?"] = function(buf, node, indent)
+    local target = compiler.local_vars.RARG and "m_RARG" or "RARG"
+    buf.write("EQUALQ(%s", target)
+    for i = 1, #node do
+      buf.write(", ")
+      local context = node[i].value
+      if context == "OBJDESC?" then
+        buf.write("M_OBJDESCQ")
+      elseif context and ({BEG=true, CONTAINER=true, END=true, ENTER=true,
+          LEAVE=true, LOOK=true, OBJDESC=true})[context] then
+        buf.write("M_%s", context)
+      else
+        printNode(buf, node[i], indent + 1)
+      end
+    end
+    buf.write(")")
+  end
+
+  -- P? is the compact Infocom predicate for matching the current verb,
+  -- direct object, indirect object, and actor. Its macro normally adds the
+  -- V? prefix to verb atoms; emitting a plain atom makes it nil at runtime,
+  -- which turns the verb slot into a wildcard and matches every command.
+  form["P?"] = function(buf, node, indent)
+    local dimensions = {
+      {predicate = "VERBQ", node = node[1], verb = true},
+      {predicate = "PRSOQ", node = node[2]},
+      {predicate = "PRSIQ", node = node[3]},
+      {predicate = "WINNERQ", node = node[4]},
+    }
+    local wrote = false
+    buf.write("PASS(")
+    for _, dimension in ipairs(dimensions) do
+      local argument = dimension.node
+      if argument and argument.value ~= "*" then
+        if wrote then buf.write(" and ") end
+        wrote = true
+        buf.write("%s(", dimension.predicate)
+        local values = argument.type == "list" and argument or {argument}
+        for i, value in ipairs(values) do
+          if dimension.verb and value.type == "ident" then
+            local verb = value.value == "THROUGH" and "ENTER" or value.value
+            compiler.current_verbs[#compiler.current_verbs + 1] = verb
+            buf.write("VQ%s", utils.normalizeIdentifier(verb))
+          else
+            printNode(buf, value, indent + 1)
+          end
+          if i < #values then buf.write(", ") end
+        end
+        buf.write(")")
+      end
+    end
+    if not wrote then buf.write("true") end
+    buf.write(")")
+  end
+
   -- COND (if-elseif-else)
   form.COND = function(buf, node, indent)
     if node[1] and utils.safeget(node[1][1], 'value') == "ELSE" then
@@ -140,9 +264,9 @@ function Forms.createHandlers(compiler, printNode)
         if i > 1 then buf.write("else ") end
       else
         buf.write(i == 1 and "if " or "elseif ")
-        buf.write("APPLY(function() __tmp = ")
+        buf.write("ZIL_TRUE(APPLY(function() __tmp = ")
         printNode(buf, clause[1], indent + 1)
-        buf.write(" return __tmp end)")
+        buf.write(" return __tmp end))")
         buf.write(" then ")
       end
       
@@ -176,11 +300,22 @@ function Forms.createHandlers(compiler, printNode)
   end
 
   form.TELL = function(buf, node, indent)
+    -- TELL-TOKENS gives these identifiers formatting semantics distinct from
+    -- their ordinary globals (THE is also commonly an object flag).
+    local tokens = {
+      A = "TELL_A",
+      AN = "TELL_A",
+      THE = "TELL_THE",
+      CTHE = "TELL_CTHE",
+    }
     buf.write("TELL(")
     for i = 1, #node do
       local cond_node = utils.isCond(node[i]) and node[i]
         or (node[i].type == "placeholder" and utils.isCond(node[i][1]) and node[i][1])
-      if node[i].type == "placeholder" and node[i][1] and not cond_node then
+      local token = node[i].type == "ident" and tokens[node[i].value]
+      if token then
+        buf.write(token)
+      elseif node[i].type == "placeholder" and node[i][1] and not cond_node then
         buf.write("D, ")
         printNode(buf, node[i][1], indent + 1)
       elseif cond_node then
@@ -348,6 +483,18 @@ function Forms.createHandlers(compiler, printNode)
     writeStringCall(buf, "SYNONYM", node)
   end
 
+  -- Infocom vocabulary sources distinguish verb/preposition aliases from the
+  -- generic SYNONYM directive.  They share the same dictionary representation
+  -- at runtime, so preserve the source spelling while lowering both forms to
+  -- the existing synonym implementation.
+  form["VERB-SYNONYM"] = function(buf, node, indent)
+    writeStringCall(buf, "DEFER_SYNONYM", node)
+  end
+
+  form["PREP-SYNONYM"] = function(buf, node, indent)
+    writeStringCall(buf, "DEFER_SYNONYM", node)
+  end
+
   -- GLOBAL and CONSTANT
   form.GLOBAL = function(buf, node, indent)
     local name = compiler.value(node[1])
@@ -425,13 +572,17 @@ function Forms.createHandlers(compiler, printNode)
   end
 
   form.ITABLE = function(buf, node)
-    buf.write("ITABLE(")
-    if utils.safeget(node[1], "value") == "NONE" and node[2] then
-      printNode(buf, node[2], 0)
+    if node[1] and node[1].type == "number"
+        and not (node[2] and node[2].type == "list") then
+      buf.write("ITABLE_WORDS(%s, %d)", compiler.value(node[1]), math.max(1, #node - 1))
+    elseif utils.safeget(node[1], "value") == "NONE" and node[2] then
+      buf.write("ITABLE_WORDS(%s, 1)", compiler.value(node[2]))
     else
+      -- Preserve the established byte/LEXV buffer layout for flagged tables.
+      buf.write("ITABLE(")
       printNode(buf, node[1], 0)
+      buf.write(")")
     end
-    buf.write(")")
   end
 
   -- AND/OR
diff --git a/zilscript/compiler/toplevel.lua b/zilscript/compiler/toplevel.lua
index 6b5936d..c830271 100644
--- a/zilscript/compiler/toplevel.lua
+++ b/zilscript/compiler/toplevel.lua
@@ -217,7 +217,10 @@ TopLevel.DIRECT_STATEMENTS = {
   COND = true,
   BUZZ = true,
   SYNONYM = true,
+  ["VERB-SYNONYM"] = true,
+  ["PREP-SYNONYM"] = true,
   SYNTAX = true,
+  ["SET-HEADER"] = true,
   GLOBAL = true,
   CONSTANT = true,
   SETG = true,