Your directive: You are a fork with the whole design conversation in context. Write the ISSUE FILES for PHASE 4 of Double Diaper Dungeon (401 through 414), plus issues/phase-4-progress.md. Project root: /mnt/cmdo/ritz/games/tq/ai-stuff/double-diaper-dungeon. Read docs/019-roadmap.md for the exact issue list and titles, docs/001 for vocabulary, docs/009 and 015 for the mechanisms (and 004, 006, 012 where they touch), docs/018 for house style, docs/020 for open question ids, assets/023-balance-table.lua for entry names, and notes/decisions-in-her-own-words.md for the developer's verbatim lore (the crybabies left behind; monsters carried away into secret tunnels). Do not touch any file outside issues/. Do not run git. Do not run new-source-file.

File naming: issues/{PHASE}{ID}-{dashed-lowercase-title}.md, e.g. issues/403-the-dodge-rule.md. One file per roadmap row, exact titles.

Format of every issue (the hero-less-moba shape you read):

NNN — Title

Phase	4 — Combat in a Room
Blocked by	issue numbers, or —
Blocks	issue numbers
Reads	links to the documents it builds from, ../docs/NNN-name.md
Open questions	ids from docs/020-open-questions.md (e.g. D2, D6, D8), or none

Current behavior

What exists now: nothing runs; phases 1 to 3 are assumed built (name what this issue needs from them). The dodge rule was Monte Carlo'd during design: roughly five whiffs per side open every fight, attacker dexterity is the strong lever, constitution the weak one; say so in 403.

Intended behavior

The blueprint: what it is, how it works mechanically, the data with datatypes, every branch and where it leads, what it refuses (errors, never fallbacks, nothing nil), the actual log lines in the emoji-first style with English connective tissue (names colored by slider share is the viewer's job; the log line carries the hero id and the words), and the scenario that tests it. Plain English and fixed vocabulary; list files, functions and structures by descriptive name rather than code. Numbers by balance-table entry name, never values.

Suggested implementation steps

Numbered. Files to create (dashed names for ./new-source-file, no indices claimed), what each holds, the scenario in tests/, the order.

Related documents and tools

Still open

Facts that must be right: one melee pool per room, no positioning; cadence from speed; physical damage from strength, magical from intellect times imagination; the dangerous state multiplies damage dealt and taken and crybaby chance; threat stored raw per attacker-defender pair, like-targets-like halving applied only at target selection, healer inherits a fraction of the healed target's incoming threat; the dodge rule with one avoid value per defender (start, additive decay per dodge widened by attacker dexterity, floor at zero, on a hit recover a fraction of the missing value toward the cap raised asymptotically by defender constitution, rounded); stunned means auto-hit and an auto-hit counts as a hit for recovery; crybaby sits in the corner until the room's battle ends or someone holds them, monsters do not attack a crier while fighters remain; Encourage ends crying from across the room at a threat cost, then the encouraged hero is stunned until they take one hit, then gets a shield that blocks exactly one hit; death is health below zero, every teammate loses confidence dampened by maturity and low maturity rolls to cry, every enemy gains confidence, a won battle after a death sobers survivors on all sanity attributes once; monsters flee below the flee line (dropping nothing; only wetting in pants drops valuables), can cry, stop when bullied or cared for, a caregiver's care sends a naughty monster running; if every monster is crying, heroes carry them to another room where they cry until they stop and sneak away into the secret tunnels in the walls; if every fighter leaves and only a crier remains, the screen fades to black and the hero is gone (quote her lore verbatim); reinforcements from connected infested rooms at battle start and over time; the ghost of the level themes in-battle intellect puzzles answered by a stat roll that can overrule the right answer, right answers earn praise and a journal line, wrong answers deal regression; the battle ends when the room holds no monsters or no fighting heroes and the crybaby, toilet-retry, between-battle-change and caregiver-stun systems read that boundary; issue 414 defines the first monsters as data in assets/ (goblin, feral cat, and the haunted toilet, with fallen seraph and cave troll stubbed), pants or diaper per kind, one fixed color each, the periodic reminder line about their maturity. Issue 413 is the battle-boundary issue; issue 414 is the phase capstone and creates issues/completed/demos/phase-4-demo (house-convention bash) that runs a party against a room of goblins and feral cats a thousand times headless and prints hit rate per swing over the first thirty swings, targeting and why, every cry and hold, every death and its confidence ripples, and one run ending in the fade to black. Also write issues/phase-4-progress.md in the hero-less-moba shape: goal, ends with, a table of issues with status "not started", Blocking, "Demo: not yet built".

Length: 500 to 1200 words per issue. When done, reply with the list of files written and their word counts, and any NEW open questions you noticed (topic plus one sentence). Nothing else.