@maka/maka-cli 5.122.1 → 5.123.1

package/bundle/typescript/src/commands/game/sideQuest/factories/scene-chunks.js

@@ -63,8 +63,8 @@ export function isFixerName(name) {
 export function wardBrief(player) {
     return partyCanDispel(player)
         ? `- WARDS: this runner can dispel, so a "ward" device is fair game.`
-        : `- WARDS: NOBODY at this table can dispel. Do NOT write a "ward" device -- there is no
-  findable answer to a ward, so a mundane team simply cannot pass one. Use a "lock" or a
+        : `- WARDS: NOBODY at this table can dispel. Do NOT write a "ward" device -- there is no
+  findable answer to a ward, so a mundane team simply cannot pass one. Use a "lock" or a
   "panel"; both have a way through that anyone can find.`;
 }
 export function buildPlayerDossier(player) {
@@ -139,34 +139,34 @@ export function buildPlayerDossier(player) {
     const armor = a.getArmorValue();
     if (armor > 0)
         gearBits.push(`armor +${armor} soak`);
-    return `
-THE RUNNER (build this job FOR this specific character):
-- Name: ${a.name}${a.archetypeName ? ` -- archetype: ${a.archetypeName}` : ''}${a.gender ? ` -- ${a.gender === 'male' ? 'a man (he/him)' : 'a woman (she/her)'}` : ' -- gender unstated (use they/them, never guess)'}
-- Attributes: ${attrs}
-${topSkills ? `- Top skills: ${topSkills}` : ''}
-- Combat calibration: attack pool ~${attack}d6, defense pool ~${defense}d6${gearBits.length > 0 ? ` (${gearBits.join(', ')})` : ''}
-${caps.map(c => `- ${c}`).join('\n')}
-
-Tailoring rules:
-- Include at least one route, subplot, or payoff that rewards THIS runner's toolkit (matrix
-  content and hasNode rooms for a decker/technomancer; astral angles or Awakened opposition
-  for a mage; melee-shaped trouble for an adept; social leverage and people worth talking round
-  for a talker; recon value for a drone owner). Pick what fits this character and this
-  story -- don't bolt on every plane at once.
-- Never gate FINISHING the run behind a capability they lack: no matrix-plane winCondition
-  item unless they can already jack in (deck or resonance) or a findable Cyberdeck is placed
-  in a reachable room; no ward/"spell"-bypass-only route for someone who can't cast.
-- Don't hand them loot they can't use as a puzzle rewardItem or the winCondition rewardItem
-  (spellcasting gear for an adept, a second cyberdeck or drone for someone who already has
-  one). Useless-to-them gear may still exist as ordinary world dressing or valuables.
-- The runner ALREADY OWNS everything the dossier lists -- never duplicate any of it (their
-  deck, drone, weapon, focus, commlink) in the "starting"-role items. Round those out with
-  complementary basics instead: ammunition, a medkit, armor, tools -- or fewer items.
-- Scale opposition to the calibration pools above: rank-and-file threats should roll a few
-  dice below the runner's pools, and a centerpiece enforcer can match or slightly exceed
-  them. Don't send soft civilians at a combat monster, or elite security at a runner built
-  for talking their way through.
-${wardBrief(player)}
+    return `
+THE RUNNER (build this job FOR this specific character):
+- Name: ${a.name}${a.archetypeName ? ` -- archetype: ${a.archetypeName}` : ''}${a.gender ? ` -- ${a.gender === 'male' ? 'a man (he/him)' : 'a woman (she/her)'}` : ' -- gender unstated (use they/them, never guess)'}
+- Attributes: ${attrs}
+${topSkills ? `- Top skills: ${topSkills}` : ''}
+- Combat calibration: attack pool ~${attack}d6, defense pool ~${defense}d6${gearBits.length > 0 ? ` (${gearBits.join(', ')})` : ''}
+${caps.map(c => `- ${c}`).join('\n')}
+
+Tailoring rules:
+- Include at least one route, subplot, or payoff that rewards THIS runner's toolkit (matrix
+  content and hasNode rooms for a decker/technomancer; astral angles or Awakened opposition
+  for a mage; melee-shaped trouble for an adept; social leverage and people worth talking round
+  for a talker; recon value for a drone owner). Pick what fits this character and this
+  story -- don't bolt on every plane at once.
+- Never gate FINISHING the run behind a capability they lack: no matrix-plane winCondition
+  item unless they can already jack in (deck or resonance) or a findable Cyberdeck is placed
+  in a reachable room; no ward/"spell"-bypass-only route for someone who can't cast.
+- Don't hand them loot they can't use as a puzzle rewardItem or the winCondition rewardItem
+  (spellcasting gear for an adept, a second cyberdeck or drone for someone who already has
+  one). Useless-to-them gear may still exist as ordinary world dressing or valuables.
+- The runner ALREADY OWNS everything the dossier lists -- never duplicate any of it (their
+  deck, drone, weapon, focus, commlink) in the "starting"-role items. Round those out with
+  complementary basics instead: ammunition, a medkit, armor, tools -- or fewer items.
+- Scale opposition to the calibration pools above: rank-and-file threats should roll a few
+  dice below the runner's pools, and a centerpiece enforcer can match or slightly exceed
+  them. Don't send soft civilians at a combat monster, or elite security at a runner built
+  for talking their way through.
+${wardBrief(player)}
 `.trim();
 }
 // ============================ Prompt builders ============================
@@ -200,11 +200,11 @@ function buildTeamBlock(crew) {
             .map(([s, r]) => `${s} ${r}`).join(', ');
         return `- ${m.name} (${m.archetypeName ?? 'street contact'}): body ${c.body ?? 3}, agility ${c.agility ?? 3}, logic ${c.logic ?? 3}${(c.magic ?? 0) > 0 ? `, magic ${c.magic}` : ''}${topSkills ? ` -- ${topSkills}` : ''}`;
     }).join('\n');
-    return `
-THE TEAM: the runner does NOT work alone -- their crew rides along on this job:
-${rows}
-The opposition must credibly threaten a team of ${crew.length + 1} runners: scale guard
-counts and quality up accordingly (one extra capable defender per crew member is a good
+    return `
+THE TEAM: the runner does NOT work alone -- their crew rides along on this job:
+${rows}
+The opposition must credibly threaten a team of ${crew.length + 1} runners: scale guard
+counts and quality up accordingly (one extra capable defender per crew member is a good
 baseline), and let the fiction acknowledge a crew, not a loner.`;
 }
 export function buildSkeletonPrompt(tier, player, previousError, rumor, crew, canonBlock, runType = 'standard') {
@@ -254,409 +254,409 @@ export function buildSkeletonPrompt(tier, player, previousError, rumor, crew, ca
     // fixer" possible at all and why the objective below can be a `give`.
     // The two halves have to agree about WHERE the file is, so this block
     // says host-or-offline-server in the same vocabulary room.ts uses.
-    const dataRunBlock = runType !== 'data' ? '' : `
-THIS JOB IS A DATA RUN -- a quiet one. The runner is being paid to STEAL A FILE, not to
-take ground. Build it accordingly:
-- The winCondition item is PAYDATA: a "matrix"-plane item, category Document, sitting
-  either INSIDE a hasNode host, or on an OFFLINE SERVER device in a room (a box with no
-  Matrix presence, whose files open only to a runner whose BODY is in that room). Pick one
-  and commit to it -- the offline server is the harder, more interesting shape when the
-  fiction wants a vault you must walk into.
-- THE OPPOSITION IS ICE, not muscle. Every NPC besides the client is "matrix"-plane and
-  stationed in the host. No guards patrolling meat corridors, no gunfight in the lobby: a
-  data run that ends in a firefight is a smash-and-grab wearing the wrong name. A site can
-  still be WATCHED (cameras) -- surveillance is pressure without being a gun.
-- Keep it SHORT and tight. One site, one host, one file.
-- It pays LESS than a full run of the same tier -- roughly half. The runner is trading pay
-  for a job that never puts a gun in their face, and the fixer prices it that way. Say so
-  in the client's own terms if it comes up at the meet.
-- The delivery still matters: the file comes out of the vault written to a chip, and the
-  chip is a physical object the runner carries and hands over. A "give" objective is the
-  natural shape.
+    const dataRunBlock = runType !== 'data' ? '' : `
+THIS JOB IS A DATA RUN -- a quiet one. The runner is being paid to STEAL A FILE, not to
+take ground. Build it accordingly:
+- The winCondition item is PAYDATA: a "matrix"-plane item, category Document, sitting
+  either INSIDE a hasNode host, or on an OFFLINE SERVER device in a room (a box with no
+  Matrix presence, whose files open only to a runner whose BODY is in that room). Pick one
+  and commit to it -- the offline server is the harder, more interesting shape when the
+  fiction wants a vault you must walk into.
+- THE OPPOSITION IS ICE, not muscle. Every NPC besides the client is "matrix"-plane and
+  stationed in the host. No guards patrolling meat corridors, no gunfight in the lobby: a
+  data run that ends in a firefight is a smash-and-grab wearing the wrong name. A site can
+  still be WATCHED (cameras) -- surveillance is pressure without being a gun.
+- Keep it SHORT and tight. One site, one host, one file.
+- It pays LESS than a full run of the same tier -- roughly half. The runner is trading pay
+  for a job that never puts a gun in their face, and the fixer prices it that way. Say so
+  in the client's own terms if it comes up at the meet.
+- The delivery still matters: the file comes out of the vault written to a chip, and the
+  chip is a physical object the runner carries and hands over. A "give" objective is the
+  natural shape.
 `;
     // The hub's active street rumor becomes the job's backdrop -- gossip
     // the runner heard at the noodle stand pays off as foreshadowing when
     // the next job turns out to be tangled in exactly that (see
     // Game.advanceRumor).
     const rumorBlock = rumor
-        ? `\nSTREET RUMOR the runner has been hearing around their home district: "${rumor}"
-Let this job CONNECT to the rumor -- as its cause, its consequence, or the truth behind it.
-The connection should be discoverable in play (the client's briefing, an NPC's talk, a
+        ? `\nSTREET RUMOR the runner has been hearing around their home district: "${rumor}"
+Let this job CONNECT to the rumor -- as its cause, its consequence, or the truth behind it.
+The connection should be discoverable in play (the client's briefing, an NPC's talk, a
 document), not just implied by the title.`
         : '';
-    return `
-You are generating the STRUCTURE (skeleton) of a self-contained Shadowrun-flavored text
-adventure "run". This is job #${tier} in an ongoing campaign -- scale stakes accordingly.
-Prose comes later in separate passes: here, every "concept" is ONE tight sentence of intent,
-and everything else is structure. Get the STRUCTURE exactly right -- every name is a
-cross-reference other passes and the game engine will rely on verbatim.
-${rumorBlock}
-${dataRunBlock}
-${canonBlock ? `\n${canonBlock}\n` : ''}
-${dossier ? `\n${dossier}\n` : ''}
-${JSON_ONLY}
-
-{
-  "name": string, // the run's title
-  "story": string, // 1-2 SHORT teaser sentences shown before play -- name the shape of the
-                    // trouble, never the objective, target names, locations, or passphrases
-                    // (those are learned at the meet with the client).
-  "completionMessage": string, // 1-2 sentences shown when the job completes
-  "rooms": [{
-    "name": string, "concept": string, "roomType"?: string,
-    "outdoors": boolean, // TRUE only if OPEN TO THE SKY. A courtyard, a street, a
-                         // rooftop, a dock: true. Anything with a roof -- a market
-                         // HALL, a parking garage, a docking bay, a courtROOM -- is
-                         // false, however outdoor its name sounds. Say it for every
-                         // room; the engine cannot tell from the name and a wrong
-                         // guess sends a taxi inside a building.
-    "isStartRoom"?: boolean, // EXACTLY ONE room
-    "reachable"?: boolean, // false ONLY for a remote contact's room (rare -- a voice on the
-                            // other end of a call, never anyone the player must meet)
-    "owner"?: string, // an NPC's name, if it's their room. USE THIS for any territorial or
-                       // guarded space (a gang cache, a fixer's office, a shop): the room's
-                       // goods become THEIRS, and the engine makes them contest theft --
-                       // an unowned prize in a guarded vault walks out unchallenged.
-    "hasNode"?: boolean, // a live Matrix host standing over this room: its own virtual space,
-                          // ENTERED by a persona that holds a mark on it. Hacking it releases
-                          // the room's maglocks AND unseals its matrix-plane files, which live
-                          // INSIDE the host -- from the outside grid it is one sealed icon.
-                          // A HOST IS ORDINARY, NOT CORPORATE. "Your local Stuffer Shack has
-                          // a host icon" (p.219), and the core book publishes that convenience
-                          // store as a worked sample host (p.245-246) -- so a pawnshop, a bar,
-                          // a clinic or a corner store plausibly has one, rated 3-4 as "low-end
-                          // commercial, private business" (p.247). Withholding hosts from
-                          // everything but corp/tech sites is what made an ordinary storefront
-                          // read "thin grid" on the map when canon says otherwise.
-                          // SET IT ON PREMISES, NOT ON EVERY ROOM: the businesses and secure
-                          // sites a scene contains, not each corridor, alley, stairwell or
-                          // room inside one building -- a site is covered by its host, and
-                          // interior rooms of the same premises share it rather than each
-                          // sprouting their own. Give every host a hostRating chosen for the
-                          // place it actually is; a scene where every rating is 3 is as wrong
-                          // as one where nothing is a host.
-                          // Ice NPCs and matrix-plane items belong ONLY in hasNode rooms, and
-                          // any hasNode room holding matrix items MUST have an ice NPC
-                          // stationed in it -- so a corner-store host with no paydata in it
-                          // carries no ice, and costs the scene nothing.
-    "nodeAccess"?: "wireless", // Hosts are always reachable from the Matrix -- that is what
-                          // makes them hosts. There is no air-gapped host: for a vault that
-                          // must be entered in the flesh, put an OFFLINE SERVER device in the
-                          // room's items instead and leave the host off. Legacy "wired" values
-                          // are migrated automatically; do not author them.
-    "hostGrid"?: "public" | "local" | "global:<corp>", // OPTIONAL. Which grid the host sits on (SR5 p.233 cross-grid -2). Leave it out unless the fiction says -- hosts are reachable from every grid.
-    "hostRating"?: number, // 1-12, SR5 p.247. What KIND of host this is, and the only thing
-                          // that tells a pawnshop apart from an arcology on the grid map.
-                          // 1-2 personal sites, pirate archives. 3-4 low-end commercial,
-                          // private business. 5-6 social media, local police. 7-8 local
-                          // corporate, low-level government. 9-10 regional corporate, secure
-                          // sites. 11-12 megacorporate HQ, military command. Rate it for the
-                          // place it actually is; omit it and the host is treated as a 3.
-    "warded"?: boolean, // astral barrier: projecting mages can't enter. Use sparingly.
-    "watched"?: boolean, // security cameras cover this room (feeds ride the site's hosts;
-                          // hasNode rooms are always watched implicitly). Use for lobbies,
-                          // corridors, and secure floors in corp/guarded locations -- loud
-                          // acts on camera cost runners dearly, and deckers loop the feeds.
-    "exits": [{ "direction": "north"|"east"|"south"|"west"|"up"|"down", "targetRoom": string,
-                "keyRequired"?: string, // an items[].name with role "key"
-                "device"?: string, // a devices[].name that holds this door shut. That
-                                    // device's own "room" MUST be the room declaring this
-                                    // exit -- you have to stand where the mechanism is.
-                "guard"?: string }] // an npcs[].name who STANDS in this doorway and will
-                                     // not move. A person, not a mechanism: the way past
-                                     // is talking them round or putting them down.
-                                     // NEVER set "device" and "guard" on one exit -- a
-                                     // door is gated by a thing OR a person, never both.
-    // Doors are TWO-WAY automatically: declare each connection from ONE
-    // side only (with its keyRequired/puzzle on that one declaration) --
-    // never declare the reverse direction too.
-  }],
-  // STAFF YOUR COMMERCE. Any room that sells, serves, or treats -- a
-  // market, shop, bar, restaurant, clinic, pawnshop -- MUST have an
-  // npcs[] entry stationed in it. A shop with nobody behind the counter
-  // is a room the runner walks into and finds blank, no matter how good
-  // its description reads.
-  "npcs": [{
-    "name": string, "concept": string, "startLocation": string,
-    "plane"?: "meat"|"matrix"|"astral", // "matrix" = ICE guarding a hasNode room;
-                                        // "astral" = a spirit. Default meat.
-    "hostile"?: boolean // OPPOSITION: this one KNOWS the runner does not belong and will
-                        // act on it -- a posted guard, a patrolling enforcer, a gang
-                        // holding the room. Default false, and LEAVE IT FALSE unless the
-                        // concept is genuinely someone's security. NOT for staff who
-                        // merely work for the wrong people: a bartender, a clerk, a
-                        // ripperdoc and a fixer are all NEUTRAL even inside an enemy
-                        // building, and marking them turns an ordinary scene into a
-                        // brawl. If in doubt, leave it out -- a guard who stays calm is
-                        // a missed beat, a hostile bartender is a broken scene.
-                        // ICE NEEDS NO FLAG: a "matrix" NPC is intrusion countermeasures
-                        // and is treated as opposition automatically. Write it only to
-                        // say FALSE, for the rare tame construct.
-  }],
-  "devices": [{
-    "name": string, "concept": string, // what it physically IS (a maglock, a keypad, a
-                                        // scanner, a ward) -- a THING, never a person
-    "room": string, // REQUIRED. A device always stands in ONE room -- the one you must be
-                     // in to reach it. If it holds a door, declare that exit FROM THIS
-                     // SAME ROOM with "device": "<this name>".
-    "kind": "lock"|"panel"|"ward", // lock = a mechanism: picked, breached, or opened by its
-                          // key. panel = an interface: a code, or hacked. ward = a working:
-                          // cast at or dispelled. EXACTLY these lowercase strings.
-                          // A device is always a THING. A doorman or a checkpoint guard is
-                          // NOT a device -- write them into npcs[] and name them in that
-                          // exit's "guard"; people are got past socially, not picked.
-    "grantsItem"?: string // an items[].name with role "reward" -- what opening it hands
-                           // over. Omit for a device that holds a door: the open way IS
-                           // the reward.
-  }],
-  "items": [{
-    "name": string,
-    "role": "winCondition"|"reward"|"key"|"clue"|"loot"|"starting",
-    "category": string, // one of: Weapon, MeleeWeapon, RangedWeapon, Armor, BodyArmor,
-                         // ArmorClothing, Helmet, Hat, LegArmor, ArmArmor, Gloves, Commlink,
-                         // Cyberdeck, Drone, Credstick, CurrencyContainer, Key, Trinket,
-                         // Document, Datachip, Vice, Book, Tool, Clothing, Glasses, Boots,
-                         // Medical, StimPatch, SpellFormula, Grimoire, Focus, Ammunition,
-                         // Food, Drink (consumables -- hot food heals stun, drink is liquid
-                         // courage; fine as dressing in bars/kitchens, never as prizes),
-                         // Cyberware (RARE prize loot -- an uninstalled augmentation part.
-                         // Its name must be one of: ${AUGMENTATIONS.map(a => a.name).join(', ')};
-                         // never one the runner already has installed, never role "starting")
-    "room"?: string, "heldBy"?: string, // exactly one of these for roles winCondition/key/
-                                         // clue/loot; NEITHER for roles reward/starting
-    "plane"?: "meat"|"matrix", // "matrix" = paydata: only in a hasNode room, category
-                                // Datachip/Document. A matrix-plane winCondition item makes
-                                // the job a datarun (its room MUST have ice).
-    "forPuzzle"?: string // role "clue" only: which puzzle's passphrase this clue reveals.
-                          // EVERY puzzle needs exactly one clue item, category "Book",
-                          // placed in a DIFFERENT room than that puzzle (door puzzles: any
-                          // room). The clue's text is written in a later pass.
-                          // ${isContinuation ? 'Role "starting" is FORBIDDEN in this scene -- the runner arrives fully equipped (see dossier).' : 'Role "starting" items are the fresh runner\'s basic kit.'}
-  }],
-  "winCondition": {
-    "item": string, // the items[].name with role "winCondition" -- MUST have room or heldBy
-                     // set (never heldBy "toNpc" -- the player has to find it), and it is
-                     // the central plot object of "story"
-    "toNpc": string, // an npcs[].name -- who wants it delivered
-    "payout": number, // the job's pay in nuyen; the engine actually transfers it -- half at
-                       // the meet, the rest on delivery. ~2000-6000 for job #1, roughly half
-                       // again more per job after that
-    "rewardItem"?: string // optional bonus: an items[].name with role "reward"
-  },
-  "client": string // the npcs[].name of the run's CLIENT -- see CLIENT below
-}
-
-CLIENT: every run has a CLIENT -- "a Mr. Johnson", the employer's deniable face, the person
-who holds THE MEET (briefs the runner in person, negotiates the rate, pays the whole fee as
-one lump sum on delivery). Invent a COVER NAME with corporate anonymity to it -- "Mr. Osprey",
-"Ms. Veil", "Señora Marrow" -- never literally "Mr. Johnson" and never "${FIXER_NAME}" (that's
-the runner's own fixer back home, who brokered this meet and is NOT in this scene). Station
-the client in a REACHABLE room that makes a characterful meet spot -- a bar booth, a noodle
-stall, the back seat of a parked limo, a chapel pew -- reachable from the start room WITHOUT
-passing any puzzle, key, or hostile ground: the meet opens the job, it is never gated behind
-it. The client MUST hold a Commlink-category item (role "loot", heldBy them) so the runner
-can also call them, and the player must have a commlink available (${isContinuation ? 'the runner already carries their own -- see the dossier' : '"starting" role, or findable in a reachable room'}).
-The client usually has no combat block -- they hired OUT the violence. They do NOT have to
-be winCondition.toNpc (delivering to the client at the meet spot is one good shape; a
-dead-drop to a different contact is another); any toNpc in an unreachable room needs a
-commlink of their own too.
-
-Hard structural rules (validated mechanically -- a violation is rejected):
-- Every exits[].targetRoom, npcs[].startLocation, items[].room name a real rooms[].name;
-  every items[].heldBy names a real npcs[].name; every exits[].device names a real
-  puzzles[].name; every keyRequired names a real items[].name with role "key".
-- "client" names a real npcs[].name, stationed in a REACHABLE room, holding a
-  Commlink-category item.
-- Exactly one room has isStartRoom true, and it must be OUTDOOR street-level ground -- a
-  street, alley, plaza, lot, dock, yard -- with "outdoors": true AND a name/roomType that
-  says so. The runner
-  arrives by cab at that curb and hails the ride home from the same spot; an indoor start
-  room breaks the transport fiction. Never lock the start room's only exits behind keys
-  placed beyond them: every key must be reachable WITHOUT passing through the door it opens.
-- A "reachable": false room never connects to a reachable one, and nothing the player must
-  retrieve (winCondition item, keys, clues) is ever placed in one.
-- EVERY device names its own "room". If it holds a door, that door's exit is declared
-  from THAT SAME room with "device": "<its name>".
-- EVERY WAY THROUGH IS FINDABLE -- no exceptions, and no dependence on who is playing:
-    * every "panel" gets a code AND exactly one "clue"-role Book item (forDevice set) in a
-      DIFFERENT room, reachable without passing the panel itself;
-    * every "lock" gets a "key"-role item placed in the world, reachable without passing
-      the lock itself.
-  Write the clue or the key in the same breath as the device. A runner with the matching
-  skill can still take the shortcut -- pick the lock, hack the panel -- but the found way
-  must exist for a runner who has neither.
-- The winCondition item must not be heldBy winCondition.toNpc. If a matrix-plane item is the
-  winCondition item, its room has hasNode true AND a "matrix"-plane NPC stationed there.
+    return `
+You are generating the STRUCTURE (skeleton) of a self-contained Shadowrun-flavored text
+adventure "run". This is job #${tier} in an ongoing campaign -- scale stakes accordingly.
+Prose comes later in separate passes: here, every "concept" is ONE tight sentence of intent,
+and everything else is structure. Get the STRUCTURE exactly right -- every name is a
+cross-reference other passes and the game engine will rely on verbatim.
+${rumorBlock}
+${dataRunBlock}
+${canonBlock ? `\n${canonBlock}\n` : ''}
+${dossier ? `\n${dossier}\n` : ''}
+${JSON_ONLY}
+
+{
+  "name": string, // the run's title
+  "story": string, // 1-2 SHORT teaser sentences shown before play -- name the shape of the
+                    // trouble, never the objective, target names, locations, or passphrases
+                    // (those are learned at the meet with the client).
+  "completionMessage": string, // 1-2 sentences shown when the job completes
+  "rooms": [{
+    "name": string, "concept": string, "roomType"?: string,
+    "outdoors": boolean, // TRUE only if OPEN TO THE SKY. A courtyard, a street, a
+                         // rooftop, a dock: true. Anything with a roof -- a market
+                         // HALL, a parking garage, a docking bay, a courtROOM -- is
+                         // false, however outdoor its name sounds. Say it for every
+                         // room; the engine cannot tell from the name and a wrong
+                         // guess sends a taxi inside a building.
+    "isStartRoom"?: boolean, // EXACTLY ONE room
+    "reachable"?: boolean, // false ONLY for a remote contact's room (rare -- a voice on the
+                            // other end of a call, never anyone the player must meet)
+    "owner"?: string, // an NPC's name, if it's their room. USE THIS for any territorial or
+                       // guarded space (a gang cache, a fixer's office, a shop): the room's
+                       // goods become THEIRS, and the engine makes them contest theft --
+                       // an unowned prize in a guarded vault walks out unchallenged.
+    "hasNode"?: boolean, // a live Matrix host standing over this room: its own virtual space,
+                          // ENTERED by a persona that holds a mark on it. Hacking it releases
+                          // the room's maglocks AND unseals its matrix-plane files, which live
+                          // INSIDE the host -- from the outside grid it is one sealed icon.
+                          // A HOST IS ORDINARY, NOT CORPORATE. "Your local Stuffer Shack has
+                          // a host icon" (p.219), and the core book publishes that convenience
+                          // store as a worked sample host (p.245-246) -- so a pawnshop, a bar,
+                          // a clinic or a corner store plausibly has one, rated 3-4 as "low-end
+                          // commercial, private business" (p.247). Withholding hosts from
+                          // everything but corp/tech sites is what made an ordinary storefront
+                          // read "thin grid" on the map when canon says otherwise.
+                          // SET IT ON PREMISES, NOT ON EVERY ROOM: the businesses and secure
+                          // sites a scene contains, not each corridor, alley, stairwell or
+                          // room inside one building -- a site is covered by its host, and
+                          // interior rooms of the same premises share it rather than each
+                          // sprouting their own. Give every host a hostRating chosen for the
+                          // place it actually is; a scene where every rating is 3 is as wrong
+                          // as one where nothing is a host.
+                          // Ice NPCs and matrix-plane items belong ONLY in hasNode rooms, and
+                          // any hasNode room holding matrix items MUST have an ice NPC
+                          // stationed in it -- so a corner-store host with no paydata in it
+                          // carries no ice, and costs the scene nothing.
+    "nodeAccess"?: "wireless", // Hosts are always reachable from the Matrix -- that is what
+                          // makes them hosts. There is no air-gapped host: for a vault that
+                          // must be entered in the flesh, put an OFFLINE SERVER device in the
+                          // room's items instead and leave the host off. Legacy "wired" values
+                          // are migrated automatically; do not author them.
+    "hostGrid"?: "public" | "local" | "global:<corp>", // OPTIONAL. Which grid the host sits on (SR5 p.233 cross-grid -2). Leave it out unless the fiction says -- hosts are reachable from every grid.
+    "hostRating"?: number, // 1-12, SR5 p.247. What KIND of host this is, and the only thing
+                          // that tells a pawnshop apart from an arcology on the grid map.
+                          // 1-2 personal sites, pirate archives. 3-4 low-end commercial,
+                          // private business. 5-6 social media, local police. 7-8 local
+                          // corporate, low-level government. 9-10 regional corporate, secure
+                          // sites. 11-12 megacorporate HQ, military command. Rate it for the
+                          // place it actually is; omit it and the host is treated as a 3.
+    "warded"?: boolean, // astral barrier: projecting mages can't enter. Use sparingly.
+    "watched"?: boolean, // security cameras cover this room (feeds ride the site's hosts;
+                          // hasNode rooms are always watched implicitly). Use for lobbies,
+                          // corridors, and secure floors in corp/guarded locations -- loud
+                          // acts on camera cost runners dearly, and deckers loop the feeds.
+    "exits": [{ "direction": "north"|"east"|"south"|"west"|"up"|"down", "targetRoom": string,
+                "keyRequired"?: string, // an items[].name with role "key"
+                "device"?: string, // a devices[].name that holds this door shut. That
+                                    // device's own "room" MUST be the room declaring this
+                                    // exit -- you have to stand where the mechanism is.
+                "guard"?: string }] // an npcs[].name who STANDS in this doorway and will
+                                     // not move. A person, not a mechanism: the way past
+                                     // is talking them round or putting them down.
+                                     // NEVER set "device" and "guard" on one exit -- a
+                                     // door is gated by a thing OR a person, never both.
+    // Doors are TWO-WAY automatically: declare each connection from ONE
+    // side only (with its keyRequired/puzzle on that one declaration) --
+    // never declare the reverse direction too.
+  }],
+  // STAFF YOUR COMMERCE. Any room that sells, serves, or treats -- a
+  // market, shop, bar, restaurant, clinic, pawnshop -- MUST have an
+  // npcs[] entry stationed in it. A shop with nobody behind the counter
+  // is a room the runner walks into and finds blank, no matter how good
+  // its description reads.
+  "npcs": [{
+    "name": string, "concept": string, "startLocation": string,
+    "plane"?: "meat"|"matrix"|"astral", // "matrix" = ICE guarding a hasNode room;
+                                        // "astral" = a spirit. Default meat.
+    "hostile"?: boolean // OPPOSITION: this one KNOWS the runner does not belong and will
+                        // act on it -- a posted guard, a patrolling enforcer, a gang
+                        // holding the room. Default false, and LEAVE IT FALSE unless the
+                        // concept is genuinely someone's security. NOT for staff who
+                        // merely work for the wrong people: a bartender, a clerk, a
+                        // ripperdoc and a fixer are all NEUTRAL even inside an enemy
+                        // building, and marking them turns an ordinary scene into a
+                        // brawl. If in doubt, leave it out -- a guard who stays calm is
+                        // a missed beat, a hostile bartender is a broken scene.
+                        // ICE NEEDS NO FLAG: a "matrix" NPC is intrusion countermeasures
+                        // and is treated as opposition automatically. Write it only to
+                        // say FALSE, for the rare tame construct.
+  }],
+  "devices": [{
+    "name": string, "concept": string, // what it physically IS (a maglock, a keypad, a
+                                        // scanner, a ward) -- a THING, never a person
+    "room": string, // REQUIRED. A device always stands in ONE room -- the one you must be
+                     // in to reach it. If it holds a door, declare that exit FROM THIS
+                     // SAME ROOM with "device": "<this name>".
+    "kind": "lock"|"panel"|"ward", // lock = a mechanism: picked, breached, or opened by its
+                          // key. panel = an interface: a code, or hacked. ward = a working:
+                          // cast at or dispelled. EXACTLY these lowercase strings.
+                          // A device is always a THING. A doorman or a checkpoint guard is
+                          // NOT a device -- write them into npcs[] and name them in that
+                          // exit's "guard"; people are got past socially, not picked.
+    "grantsItem"?: string // an items[].name with role "reward" -- what opening it hands
+                           // over. Omit for a device that holds a door: the open way IS
+                           // the reward.
+  }],
+  "items": [{
+    "name": string,
+    "role": "winCondition"|"reward"|"key"|"clue"|"loot"|"starting",
+    "category": string, // one of: Weapon, MeleeWeapon, RangedWeapon, Armor, BodyArmor,
+                         // ArmorClothing, Helmet, Hat, LegArmor, ArmArmor, Gloves, Commlink,
+                         // Cyberdeck, Drone, Credstick, CurrencyContainer, Key, Trinket,
+                         // Document, Datachip, Vice, Book, Tool, Clothing, Glasses, Boots,
+                         // Medical, StimPatch, SpellFormula, Grimoire, Focus, Ammunition,
+                         // Food, Drink (consumables -- hot food heals stun, drink is liquid
+                         // courage; fine as dressing in bars/kitchens, never as prizes),
+                         // Cyberware (RARE prize loot -- an uninstalled augmentation part.
+                         // Its name must be one of: ${AUGMENTATIONS.map(a => a.name).join(', ')};
+                         // never one the runner already has installed, never role "starting")
+    "room"?: string, "heldBy"?: string, // exactly one of these for roles winCondition/key/
+                                         // clue/loot; NEITHER for roles reward/starting
+    "plane"?: "meat"|"matrix", // "matrix" = paydata: only in a hasNode room, category
+                                // Datachip/Document. A matrix-plane winCondition item makes
+                                // the job a datarun (its room MUST have ice).
+    "forPuzzle"?: string // role "clue" only: which puzzle's passphrase this clue reveals.
+                          // EVERY puzzle needs exactly one clue item, category "Book",
+                          // placed in a DIFFERENT room than that puzzle (door puzzles: any
+                          // room). The clue's text is written in a later pass.
+                          // ${isContinuation ? 'Role "starting" is FORBIDDEN in this scene -- the runner arrives fully equipped (see dossier).' : 'Role "starting" items are the fresh runner\'s basic kit.'}
+  }],
+  "winCondition": {
+    "item": string, // the items[].name with role "winCondition" -- MUST have room or heldBy
+                     // set (never heldBy "toNpc" -- the player has to find it), and it is
+                     // the central plot object of "story"
+    "toNpc": string, // an npcs[].name -- who wants it delivered
+    "payout": number, // the job's pay in nuyen; the engine actually transfers it -- half at
+                       // the meet, the rest on delivery. ~2000-6000 for job #1, roughly half
+                       // again more per job after that
+    "rewardItem"?: string // optional bonus: an items[].name with role "reward"
+  },
+  "client": string // the npcs[].name of the run's CLIENT -- see CLIENT below
+}
+
+CLIENT: every run has a CLIENT -- "a Mr. Johnson", the employer's deniable face, the person
+who holds THE MEET (briefs the runner in person, negotiates the rate, pays the whole fee as
+one lump sum on delivery). Invent a COVER NAME with corporate anonymity to it -- "Mr. Osprey",
+"Ms. Veil", "Señora Marrow" -- never literally "Mr. Johnson" and never "${FIXER_NAME}" (that's
+the runner's own fixer back home, who brokered this meet and is NOT in this scene). Station
+the client in a REACHABLE room that makes a characterful meet spot -- a bar booth, a noodle
+stall, the back seat of a parked limo, a chapel pew -- reachable from the start room WITHOUT
+passing any puzzle, key, or hostile ground: the meet opens the job, it is never gated behind
+it. The client MUST hold a Commlink-category item (role "loot", heldBy them) so the runner
+can also call them, and the player must have a commlink available (${isContinuation ? 'the runner already carries their own -- see the dossier' : '"starting" role, or findable in a reachable room'}).
+The client usually has no combat block -- they hired OUT the violence. They do NOT have to
+be winCondition.toNpc (delivering to the client at the meet spot is one good shape; a
+dead-drop to a different contact is another); any toNpc in an unreachable room needs a
+commlink of their own too.
+
+Hard structural rules (validated mechanically -- a violation is rejected):
+- Every exits[].targetRoom, npcs[].startLocation, items[].room name a real rooms[].name;
+  every items[].heldBy names a real npcs[].name; every exits[].device names a real
+  puzzles[].name; every keyRequired names a real items[].name with role "key".
+- "client" names a real npcs[].name, stationed in a REACHABLE room, holding a
+  Commlink-category item.
+- Exactly one room has isStartRoom true, and it must be OUTDOOR street-level ground -- a
+  street, alley, plaza, lot, dock, yard -- with "outdoors": true AND a name/roomType that
+  says so. The runner
+  arrives by cab at that curb and hails the ride home from the same spot; an indoor start
+  room breaks the transport fiction. Never lock the start room's only exits behind keys
+  placed beyond them: every key must be reachable WITHOUT passing through the door it opens.
+- A "reachable": false room never connects to a reachable one, and nothing the player must
+  retrieve (winCondition item, keys, clues) is ever placed in one.
+- EVERY device names its own "room". If it holds a door, that door's exit is declared
+  from THAT SAME room with "device": "<its name>".
+- EVERY WAY THROUGH IS FINDABLE -- no exceptions, and no dependence on who is playing:
+    * every "panel" gets a code AND exactly one "clue"-role Book item (forDevice set) in a
+      DIFFERENT room, reachable without passing the panel itself;
+    * every "lock" gets a "key"-role item placed in the world, reachable without passing
+      the lock itself.
+  Write the clue or the key in the same breath as the device. A runner with the matching
+  skill can still take the shortcut -- pick the lock, hack the panel -- but the found way
+  must exist for a runner who has neither.
+- The winCondition item must not be heldBy winCondition.toNpc. If a matrix-plane item is the
+  winCondition item, its room has hasNode true AND a "matrix"-plane NPC stationed there.
 - ${isContinuation
         ? 'ZERO "starting"-role items -- the runner arrives with everything they own. 4-6'
-        : '3-5 "starting"-role items (basics the runner doesn\'t already own -- see the dossier), 4-6'}
-  "loot"-role world items, one "clue" per panel and one "key" per lock.
-
-Scope: ${scope}. Gritty noir Shadowrun tone: a client, a job, a debt, a betrayal -- and a
-fresh premise, not a generic "corp blackmail vault" rerun.${repairNote(previousError)}
+        : '3-5 "starting"-role items (basics the runner doesn\'t already own -- see the dossier), 4-6'}
+  "loot"-role world items, one "clue" per panel and one "key" per lock.
+
+Scope: ${scope}. Gritty noir Shadowrun tone: a client, a job, a debt, a betrayal -- and a
+fresh premise, not a generic "corp blackmail vault" rerun.${repairNote(previousError)}
 `.trim();
 }
 /** Shared context header for the detail passes: the fixed skeleton. */
 function skeletonContext(skeleton) {
-    return `The scene's FIXED skeleton (all names are final -- reference them EXACTLY, never invent new ones):
+    return `The scene's FIXED skeleton (all names are final -- reference them EXACTLY, never invent new ones):
 ${JSON.stringify(skeleton, null, 1)}`;
 }
 export function buildRoomsPrompt(skeleton, previousError) {
-    return `
-You are writing the room descriptions for a Shadowrun text adventure.
-
-${skeletonContext(skeleton)}
-
-For EVERY room in the skeleton, write evocative 2-3 sentence prose expanding its "concept" --
-gritty cyberpunk noir, concrete sensory detail, no mechanics talk and no spoilers (never
-reveal passphrases, hidden items, or plot twists in a room description).
-Never write a CODE-SHAPED string into room prose -- no door numbers, unit numbers, serials,
-or stencilled digits on a wall. The barriers' answers are the only codes in this world, and
-a number in scenery is a number a player will carry to the nearest lock and type.
-
-"At" SPOTS -- named places WITHIN a room the player can "move to":
-- Give 2-4 "spots" ONLY where positioning matters (bars, markets, offices, warehouses --
-  social or large spaces). SKIP them for corridors, transit streets, and small
-  single-purpose rooms; most rooms should have none.
-- Spot names are short concrete nouns ("bar", "booths", "loading dock", "desk") -- and
-  WEAVE each spot's name into that room's prose so the player can see it.
-- Every room WITH spots must include one doorway spot (a name containing
-  door/entrance/entry/threshold/gate).
-- At most ONE spot per spotted room may carry "tags": ["cover-partial"] (chest-high
-  cover) or ["cover-good"] (near-total concealment). Most need neither.
-- "size": "tiny" | "small" | "medium" | "large" | "huge" -- how far apart the spots
-  stand and how far a shot travels: tiny is a closet or cubicle (a few meters across),
-  small a cramped room, medium a normal room, large a proper hall or bar floor, huge
-  a warehouse or atrium. Pick the smallest size that fits the room's concept.
-- Optional "place" per spot -- where it stands: "north" | "south" | "east" | "west"
-  (that wall), "northeast corner" | "northwest corner" | "southeast corner" |
-  "southwest corner", or "center". Say this ONLY when the prose
-  actually puts it there ("the bar runs along the east wall"); leave it off otherwise
-  and the engine spreads the spot out on its own.
-- Optional "levels" -- ONLY for a genuinely multi-level space the prose describes
-  (a catwalk over a warehouse floor, a mezzanine above a club, a balcony over an
-  atrium): [{ "name": "catwalk", "side": "north"|"south"|"east"|"west",
-  "kind": "catwalk"|"balcony"|"mezzanine" }], at most 2. A spot standing on one
-  carries "level": 1 (or 2 for the second). Most rooms have none.
-- "npcSpots": station each npc whose startLocation is THIS room at the spot they'd
-  work from ({ "<npc name>": "<spot name>" }). Leave wanderers unstationed.
-  GIVE EACH ONE A DIFFERENT SPOT unless they genuinely share a post -- two people
-  on one tile read as standing shoulder to shoulder for no reason (a real report).
-- Describe the SPACE ONLY -- never write PEOPLE or takeable goods into the prose.
-  People move, flee, fight, and die, and loot gets pocketed, but the description is
-  forever: a sentry written "blocking the way, arms crossed" reads absurd after he
-  ran (a real session). Presence is the engine's job -- "look" reports who stands
-  where live. The fixed stage (the spots, the architecture, the weather) is what
-  belongs in the prose.
-- "itemSpots": anchor each item placed in THIS room to the spot it sits at
-  ({ "<item name>": "<spot name>" }) -- a prize belongs at the guarded spot, not
-  floating in the doorway; loose scatter can stay unanchored.
-- "exitSpots": which spot each exit leaves from ({ "<direction>": "<spot name>" }).
-  Give one to EVERY exit of a spotted room, and copy the spot name EXACTLY as you wrote
-  it in "spots" -- this is the only thing that tells the engine which way out a doorway
-  leads. Leave one off and the engine has to GUESS from the spot's name, which is how a
-  spot called "the back door" ended up bound to the stairs DOWN and stranded in the middle
-  of the floor. A vertical way out (stairs, a ladder, a floor hatch) needs a spot that
-  reads vertical, and a door needs one that reads like a door.
-  An exit blocked by a barrier deserves its
-  OWN named spot -- a back gate is not the entrance; two gates are two spots -- so the
-  player always knows which gate is which.
-- ONE STORY: the prose and the spot data must agree. When the prose mentions a
-  stationed NPC, place them AT their npcSpots spot and use that spot's exact name
-  ("under the awning" only if stationed at "awning") -- never "near the entrance" for
-  someone stationed elsewhere. An NPC whose job is watching a barrier stands AT that
-  barrier's exit spot.
-
-${JSON_ONLY}
-[ { "name": string, "description": string, "roomType": string,
-    "size"?: string, "spots"?: [ { "name": string, "tags"?: string[], "place"?: string, "level"?: number } ],
-    "npcSpots"?: { }, "itemSpots"?: { }, "exitSpots"?: { },
-    "levels"?: [ { "name": string, "side": string, "kind": string } ] } ]
-One entry per skeleton room, "name" copied exactly.${repairNote(previousError)}
+    return `
+You are writing the room descriptions for a Shadowrun text adventure.
+
+${skeletonContext(skeleton)}
+
+For EVERY room in the skeleton, write evocative 2-3 sentence prose expanding its "concept" --
+gritty cyberpunk noir, concrete sensory detail, no mechanics talk and no spoilers (never
+reveal passphrases, hidden items, or plot twists in a room description).
+Never write a CODE-SHAPED string into room prose -- no door numbers, unit numbers, serials,
+or stencilled digits on a wall. The barriers' answers are the only codes in this world, and
+a number in scenery is a number a player will carry to the nearest lock and type.
+
+"At" SPOTS -- named places WITHIN a room the player can "move to":
+- Give 2-4 "spots" ONLY where positioning matters (bars, markets, offices, warehouses --
+  social or large spaces). SKIP them for corridors, transit streets, and small
+  single-purpose rooms; most rooms should have none.
+- Spot names are short concrete nouns ("bar", "booths", "loading dock", "desk") -- and
+  WEAVE each spot's name into that room's prose so the player can see it.
+- Every room WITH spots must include one doorway spot (a name containing
+  door/entrance/entry/threshold/gate).
+- At most ONE spot per spotted room may carry "tags": ["cover-partial"] (chest-high
+  cover) or ["cover-good"] (near-total concealment). Most need neither.
+- "size": "tiny" | "small" | "medium" | "large" | "huge" -- how far apart the spots
+  stand and how far a shot travels: tiny is a closet or cubicle (a few meters across),
+  small a cramped room, medium a normal room, large a proper hall or bar floor, huge
+  a warehouse or atrium. Pick the smallest size that fits the room's concept.
+- Optional "place" per spot -- where it stands: "north" | "south" | "east" | "west"
+  (that wall), "northeast corner" | "northwest corner" | "southeast corner" |
+  "southwest corner", or "center". Say this ONLY when the prose
+  actually puts it there ("the bar runs along the east wall"); leave it off otherwise
+  and the engine spreads the spot out on its own.
+- Optional "levels" -- ONLY for a genuinely multi-level space the prose describes
+  (a catwalk over a warehouse floor, a mezzanine above a club, a balcony over an
+  atrium): [{ "name": "catwalk", "side": "north"|"south"|"east"|"west",
+  "kind": "catwalk"|"balcony"|"mezzanine" }], at most 2. A spot standing on one
+  carries "level": 1 (or 2 for the second). Most rooms have none.
+- "npcSpots": station each npc whose startLocation is THIS room at the spot they'd
+  work from ({ "<npc name>": "<spot name>" }). Leave wanderers unstationed.
+  GIVE EACH ONE A DIFFERENT SPOT unless they genuinely share a post -- two people
+  on one tile read as standing shoulder to shoulder for no reason (a real report).
+- Describe the SPACE ONLY -- never write PEOPLE or takeable goods into the prose.
+  People move, flee, fight, and die, and loot gets pocketed, but the description is
+  forever: a sentry written "blocking the way, arms crossed" reads absurd after he
+  ran (a real session). Presence is the engine's job -- "look" reports who stands
+  where live. The fixed stage (the spots, the architecture, the weather) is what
+  belongs in the prose.
+- "itemSpots": anchor each item placed in THIS room to the spot it sits at
+  ({ "<item name>": "<spot name>" }) -- a prize belongs at the guarded spot, not
+  floating in the doorway; loose scatter can stay unanchored.
+- "exitSpots": which spot each exit leaves from ({ "<direction>": "<spot name>" }).
+  Give one to EVERY exit of a spotted room, and copy the spot name EXACTLY as you wrote
+  it in "spots" -- this is the only thing that tells the engine which way out a doorway
+  leads. Leave one off and the engine has to GUESS from the spot's name, which is how a
+  spot called "the back door" ended up bound to the stairs DOWN and stranded in the middle
+  of the floor. A vertical way out (stairs, a ladder, a floor hatch) needs a spot that
+  reads vertical, and a door needs one that reads like a door.
+  An exit blocked by a barrier deserves its
+  OWN named spot -- a back gate is not the entrance; two gates are two spots -- so the
+  player always knows which gate is which.
+- ONE STORY: the prose and the spot data must agree. When the prose mentions a
+  stationed NPC, place them AT their npcSpots spot and use that spot's exact name
+  ("under the awning" only if stationed at "awning") -- never "near the entrance" for
+  someone stationed elsewhere. An NPC whose job is watching a barrier stands AT that
+  barrier's exit spot.
+
+${JSON_ONLY}
+[ { "name": string, "description": string, "roomType": string,
+    "size"?: string, "spots"?: [ { "name": string, "tags"?: string[], "place"?: string, "level"?: number } ],
+    "npcSpots"?: { }, "itemSpots"?: { }, "exitSpots"?: { },
+    "levels"?: [ { "name": string, "side": string, "kind": string } ] } ]
+One entry per skeleton room, "name" copied exactly.${repairNote(previousError)}
 `.trim();
 }
 export function buildNpcsPrompt(skeleton, previousError) {
-    return `
-You are writing the characters for a Shadowrun text adventure.
-
-${skeletonContext(skeleton)}
-
-For EVERY npc in the skeleton, expand its "concept":
-- "description": private GM notes on personality/motives (never shown verbatim to the player).
-- "dialogue": 2-4 short in-character lines. For "${skeleton.client}" (the CLIENT -- the
-  Johnson holding the meet) this is the REAL briefing -- the objective (the winCondition
-  item), where to start looking, the stakes, and the exact payout figure from the skeleton
-  (the engine pays exactly that number, as one lump sum on delivery). Their private
-  "description" should read like a client rep's dossier -- the employer's deniable face, a
-  Johnson buying deniability. When referring to places, use EXACT room names from the
-  skeleton -- never invent locations.
-  NEVER write a CREDENTIAL into "dialogue" or "description" -- no door code, safe
-  combination, passphrase, or key-word, not even a hint at the digits. This stage runs in
-  PARALLEL with the stage that writes the pass each barrier actually accepts, so you
-  cannot see those passes, and any credential you write here is one you invented: the lock
-  will refuse it and the player will burn a run trusting it. An NPC may say that a code
-  EXISTS, who holds it, or where it's written down -- never what it is. The engine hands
-  the real pass to whoever genuinely holds it, at runtime (see npc.ts).
-- "combat": OPTIONAL attribute block -- omit for anyone who'd never fight. Each attribute
-  1-8 (soft civilian 1-2, street-level 3-4, hardened enforcer 5-6, elite 7-8):
-  { "body", "agility", "reaction", "combatSkill", "strength"?, "willpower"?, "logic"?,
-    "intuition"?, "charisma"?, "magic"?, "resonance"?, "adept"?,
-    "skills"?: { "firearms"?, "blades"?, "clubs"?, "unarmed"?, "sneaking"?, "perception"?, "palming"?,
-                 "hacking"?, "cybercombat"?, "electronic-warfare"?, "hardware"?, "locksmith"?, "computer"?,
-                 "negotiation"?, "con"?, "intimidation"?, "etiquette"?, "leadership"?, "performance"?, "disguise"?,
-                 "medicine"?, "assensing"?, "counterspelling"?, "conjuring"?, "gunnery"? } }
-  "magic" 3-6 ONLY for a genuinely Awakened concept; "plane":"matrix" ice fights with
-  logic 4-7; give combat blocks to anyone the story expects in a firefight. "skills" is
-  optional flavor for defined concepts (a sharpshooter's "firearms": 6).
-
-${JSON_ONLY}
-[ { "name": string, "description": string, "dialogue": string[], "combat"?: { ... } } ]
-One entry per skeleton npc, "name" copied exactly.${repairNote(previousError)}
+    return `
+You are writing the characters for a Shadowrun text adventure.
+
+${skeletonContext(skeleton)}
+
+For EVERY npc in the skeleton, expand its "concept":
+- "description": private GM notes on personality/motives (never shown verbatim to the player).
+- "dialogue": 2-4 short in-character lines. For "${skeleton.client}" (the CLIENT -- the
+  Johnson holding the meet) this is the REAL briefing -- the objective (the winCondition
+  item), where to start looking, the stakes, and the exact payout figure from the skeleton
+  (the engine pays exactly that number, as one lump sum on delivery). Their private
+  "description" should read like a client rep's dossier -- the employer's deniable face, a
+  Johnson buying deniability. When referring to places, use EXACT room names from the
+  skeleton -- never invent locations.
+  NEVER write a CREDENTIAL into "dialogue" or "description" -- no door code, safe
+  combination, passphrase, or key-word, not even a hint at the digits. This stage runs in
+  PARALLEL with the stage that writes the pass each barrier actually accepts, so you
+  cannot see those passes, and any credential you write here is one you invented: the lock
+  will refuse it and the player will burn a run trusting it. An NPC may say that a code
+  EXISTS, who holds it, or where it's written down -- never what it is. The engine hands
+  the real pass to whoever genuinely holds it, at runtime (see npc.ts).
+- "combat": OPTIONAL attribute block -- omit for anyone who'd never fight. Each attribute
+  1-8 (soft civilian 1-2, street-level 3-4, hardened enforcer 5-6, elite 7-8):
+  { "body", "agility", "reaction", "combatSkill", "strength"?, "willpower"?, "logic"?,
+    "intuition"?, "charisma"?, "magic"?, "resonance"?, "adept"?,
+    "skills"?: { "firearms"?, "blades"?, "clubs"?, "unarmed"?, "sneaking"?, "perception"?, "palming"?,
+                 "hacking"?, "cybercombat"?, "electronic-warfare"?, "hardware"?, "locksmith"?, "computer"?,
+                 "negotiation"?, "con"?, "intimidation"?, "etiquette"?, "leadership"?, "performance"?, "disguise"?,
+                 "medicine"?, "assensing"?, "counterspelling"?, "conjuring"?, "gunnery"? } }
+  "magic" 3-6 ONLY for a genuinely Awakened concept; "plane":"matrix" ice fights with
+  logic 4-7; give combat blocks to anyone the story expects in a firefight. "skills" is
+  optional flavor for defined concepts (a sharpshooter's "firearms": 6).
+
+${JSON_ONLY}
+[ { "name": string, "description": string, "dialogue": string[], "combat"?: { ... } } ]
+One entry per skeleton npc, "name" copied exactly.${repairNote(previousError)}
 `.trim();
 }
 export function buildDevicesPrompt(skeleton, previousError) {
     if (skeleton.devices.length === 0)
         return '';
-    return `
-You are writing the DEVICES for a Shadowrun text adventure. A device is a THING that is
-shut and can be opened -- a lock, a panel, a ward. Never a person.
-
-${skeletonContext(skeleton)}
-
-For EVERY device in the skeleton, expand its "concept" (what it physically is -- that's
-fixed, as is its "kind"):
-- "description": what the player sees on approaching it, shown verbatim -- PLAIN and
-  concrete, never a cryptic riddle-poem. Describe it as a THING: what it is, how it's
-  secured, and what it visibly expects. Write NO people into it -- no guards, no dialogue,
-  no "they demand": anyone standing watch does their own demanding in play, in their own
-  voice. Never state the credential itself, and never write ANY OTHER number into it -- no
-  unit number, no model number, no serial, no floor number. Every code-shaped string a
-  player reads is one they will go and type.
-- "code": ONLY for kind "panel", and REQUIRED for one. The exact credential it accepts, and
-  it MUST BE THE SAME KIND OF THING your "description" says the panel wants. This is the
-  single most confusing thing in the game when it drifts: a player who reads "a keypad with
-  worn digits" and then finds "double or nothing" written in a notebook does not believe
-  they have the code, and goes looking for a number that does not exist.
-    * If the description shows a NUMERIC pad, dial, or counter -- digits only, 3-6 of them,
-      no spaces ("470912"). Then it really does take a number.
-    * Otherwise (an intercom, a voice-gate, a spoken passphrase, a name, a sign reading
-      "password") -- ALL LOWERCASE, 2-5 plain words, no punctuation.
-  Either way a concrete literal thing, never wordplay.
-  OMIT "code" for a "lock" or a "ward". You cannot talk at a mechanical lock, and a ward
-  answers to the Art -- neither has anything to hear a phrase with, so a code on one is a
-  promise the game cannot keep.
-- "openMessage" / "refuseMessage": one sentence each, in-fiction.
-- "guardsExit": ONLY when the concept is physically TERRAIN blocking a passage -- rubble, a
-  collapsed rack, a security shutter across a walkway -- name the exact "direction" of one
-  of its own room's exits that it seals. A device on a container, safe, or item pickup
-  guards nothing physical: leave it unset.
-- "footprint": "small" | "medium" | "large" -- how much of the room the blockage occupies.
-  Only meaningful alongside "guardsExit".
-
-${JSON_ONLY}
-[ { "name": string, "description": string, "code"?: string, "openMessage": string,
-    "refuseMessage": string, "guardsExit"?: string, "footprint"?: string } ]
-One entry per skeleton device, "name" copied exactly.${repairNote(previousError)}
+    return `
+You are writing the DEVICES for a Shadowrun text adventure. A device is a THING that is
+shut and can be opened -- a lock, a panel, a ward. Never a person.
+
+${skeletonContext(skeleton)}
+
+For EVERY device in the skeleton, expand its "concept" (what it physically is -- that's
+fixed, as is its "kind"):
+- "description": what the player sees on approaching it, shown verbatim -- PLAIN and
+  concrete, never a cryptic riddle-poem. Describe it as a THING: what it is, how it's
+  secured, and what it visibly expects. Write NO people into it -- no guards, no dialogue,
+  no "they demand": anyone standing watch does their own demanding in play, in their own
+  voice. Never state the credential itself, and never write ANY OTHER number into it -- no
+  unit number, no model number, no serial, no floor number. Every code-shaped string a
+  player reads is one they will go and type.
+- "code": ONLY for kind "panel", and REQUIRED for one. The exact credential it accepts, and
+  it MUST BE THE SAME KIND OF THING your "description" says the panel wants. This is the
+  single most confusing thing in the game when it drifts: a player who reads "a keypad with
+  worn digits" and then finds "double or nothing" written in a notebook does not believe
+  they have the code, and goes looking for a number that does not exist.
+    * If the description shows a NUMERIC pad, dial, or counter -- digits only, 3-6 of them,
+      no spaces ("470912"). Then it really does take a number.
+    * Otherwise (an intercom, a voice-gate, a spoken passphrase, a name, a sign reading
+      "password") -- ALL LOWERCASE, 2-5 plain words, no punctuation.
+  Either way a concrete literal thing, never wordplay.
+  OMIT "code" for a "lock" or a "ward". You cannot talk at a mechanical lock, and a ward
+  answers to the Art -- neither has anything to hear a phrase with, so a code on one is a
+  promise the game cannot keep.
+- "openMessage" / "refuseMessage": one sentence each, in-fiction.
+- "guardsExit": ONLY when the concept is physically TERRAIN blocking a passage -- rubble, a
+  collapsed rack, a security shutter across a walkway -- name the exact "direction" of one
+  of its own room's exits that it seals. A device on a container, safe, or item pickup
+  guards nothing physical: leave it unset.
+- "footprint": "small" | "medium" | "large" -- how much of the room the blockage occupies.
+  Only meaningful alongside "guardsExit".
+
+${JSON_ONLY}
+[ { "name": string, "description": string, "code"?: string, "openMessage": string,
+    "refuseMessage": string, "guardsExit"?: string, "footprint"?: string } ]
+One entry per skeleton device, "name" copied exactly.${repairNote(previousError)}
 `.trim();
 }
 export function buildItemsPrompt(skeleton, devices, previousError) {
@@ -667,36 +667,36 @@ export function buildItemsPrompt(skeleton, devices, previousError) {
         return `- "${i.name}" is the clue for device "${i.forDevice}": its "details" text MUST contain the exact code "${code ?? 'UNKNOWN'}" verbatim (a diary entry, scrawled note, or manual that gives it away once read).`;
     })
         .join('\n');
-    return `
-You are writing the items for a Shadowrun text adventure.
-
-${skeletonContext(skeleton)}
-
-For EVERY item in the skeleton, expand it into a full item ("name" and "category" are fixed):
-- "description": one sentence of always-visible flavor.
-- "details": deeper text shown on close examination or reading. CLUE ITEMS (below) put
-  their puzzle's credential HERE -- never in "description".
-- "size": "Tiny"|"Small"|"Medium"|"Large"|"VeryLarge"; "rating": "Common"|"Standard"|"Rare"|
-  "Legendary"|"MilitaryGrade" (rating scales combat/heal/deck power -- reserve Rare+ for
-  earned rewards); "shape"/"color"/"texture": short literals; "weight": realistic kilograms
-  (0.05 chip, ~2 pistol, ~4 armor); "currencyAmount" only for Credstick/CurrencyContainer.
-
-Clue requirements (mechanically validated -- the exact phrase must appear in "details"):
-${clueSpecs || '- (no clue items in this scene)'}
-
-THE ONLY CODES IN THIS WORLD are the clue phrases listed just above. No other item may
-carry a code-shaped string -- no serial numbers, no model numbers, no unit or locker or
-apartment numbers, no "access code" on a scrap of paper that isn't a listed clue. A player
-who reads a number writes it down and takes it to the nearest lock; a second plausible
-number is indistinguishable from the real one and it costs them the run. Quantities and
-prices are fine (a clip "holds 10 rounds", a stick "carries 2000 nuyen") -- those read as
-amounts, not credentials.
-
-${JSON_ONLY}
-[ { "name": string, "description": string, "size": string, "category": string,
-    "shape": string, "color": string, "texture": string, "rating": string, "weight": number,
-    "currencyAmount"?: number, "details"?: string, "transferable"?: boolean } ]
-One entry per skeleton item, "name" and "category" copied exactly.${repairNote(previousError)}
+    return `
+You are writing the items for a Shadowrun text adventure.
+
+${skeletonContext(skeleton)}
+
+For EVERY item in the skeleton, expand it into a full item ("name" and "category" are fixed):
+- "description": one sentence of always-visible flavor.
+- "details": deeper text shown on close examination or reading. CLUE ITEMS (below) put
+  their puzzle's credential HERE -- never in "description".
+- "size": "Tiny"|"Small"|"Medium"|"Large"|"VeryLarge"; "rating": "Common"|"Standard"|"Rare"|
+  "Legendary"|"MilitaryGrade" (rating scales combat/heal/deck power -- reserve Rare+ for
+  earned rewards); "shape"/"color"/"texture": short literals; "weight": realistic kilograms
+  (0.05 chip, ~2 pistol, ~4 armor); "currencyAmount" only for Credstick/CurrencyContainer.
+
+Clue requirements (mechanically validated -- the exact phrase must appear in "details"):
+${clueSpecs || '- (no clue items in this scene)'}
+
+THE ONLY CODES IN THIS WORLD are the clue phrases listed just above. No other item may
+carry a code-shaped string -- no serial numbers, no model numbers, no unit or locker or
+apartment numbers, no "access code" on a scrap of paper that isn't a listed clue. A player
+who reads a number writes it down and takes it to the nearest lock; a second plausible
+number is indistinguishable from the real one and it costs them the run. Quantities and
+prices are fine (a clip "holds 10 rounds", a stick "carries 2000 nuyen") -- those read as
+amounts, not credentials.
+
+${JSON_ONLY}
+[ { "name": string, "description": string, "size": string, "category": string,
+    "shape": string, "color": string, "texture": string, "rating": string, "weight": number,
+    "currencyAmount"?: number, "details"?: string, "transferable"?: boolean } ]
+One entry per skeleton item, "name" and "category" copied exactly.${repairNote(previousError)}
 `.trim();
 }
 // ========================= Parse / validate / assemble ====================