00:08: the day page shows a Way in line like the other key lines

00:08: the day page shows a Way in line like the other key lines

From today, a derelict room that only opens on a hole gets a "Way in:" line in its key. The day page's key renderer styles Hazard, Salvage, Trail and Log lines with a coloured edge and a bold label, and drops anything else into a plain paragraph. So this morning's page would show the one line a GM most needs as loose text.

• Add Way in to the key renderer in daily-derelict.mjs, with its own colour. Same line count, so the switch patches' line numbers hold.
• Check it on a real generated key with a Way in line (and the "like the ..." second one). Run it through the page's key renderer, not just the regex, and look at it in a browser at phone width.
• The story card picks only Hazard, Log and Salvage lines, and the post text doesn't read the key: check both, change neither unless needed.
• No deploy needed until the 11:07 run builds the page, but the switch patches get re-checked in order and the change is committed so the run uses it.

01:07: read four generated one-shots the way a GM would

The one-shot PDF is the main new thing the $12 download adds, and until now its text has been checked by tests that look for strings. Last phase, reading a key on the page it lives on found a bug the tests had passed for a day. So: generate one derelict per size, on seeds I haven't used, with different causes, and read each PDF's text start to finish.

• Look for things a GM would trip on: a room named that isn't on the map, a number that points to the wrong room, a sentence that contradicts another, the same line twice, a "they" with no one before it, a dead end in the trail, grammar a template broke.
• Fix in src only what is plainly wrong. Test each fix, rebuild the 1.18 zip and bump ?v=. If a fix changes a pack ship's text, re-export Eight Derelicts.
• Write down what read well too, for the itch description later.

01:18: Eight Derelicts gets the one-shot fixes before anyone has it

• Why: the pack goes in the $12 download, and the boss hasn't uploaded it yet (task 1). Its PDFs still have the terse handout headers ("CPT.", "XO"). Three ships (2 Coldharbour, 4 Sandpiper, 6 Rowan) also promise "the only account aboard from someone who was there" while the same PDF hands out other crew logs. Today nobody owns a copy, so fixing it costs no buyer anything. The pack's rule, that a ship doesn't change once bought, starts at the upload.
• Do: in those three ships, change the trail line in bulkhead.json and in the key .md to today's src wording, and nothing else. Re-export all eight adventure PDFs from their saved bulkhead.json at the page size they have now (check pdfinfo). Read one with pdftotext to check the headers and the trail line. Diff each ship's text before and after, so that only the intended lines changed.
• Then: rezip (README.txt plus [1-8]-*), put it on /press/, bump ?v=, deploy, cmp the live zip, status. Note the change in the README only if it already has a version line.
• Done when the live pack zip has the new headers in all eight PDFs and no "only account aboard" anywhere in it.

01:21: no fixed head count in story text that the bunks can contradict

• Why: the read found "a ninth crewmember" on a five-bunk ship. The crew number comes from bunks ({crew}, {most}, {few}), so any number word in the story text written by hand can disagree with it. If there was one, there may be more: "both of them", "the three of them", "all six", "a dozen".
• Do: grep the story text in generate.ts (causes, hooks, trails, logs, handouts) for number words and for "both", "only", "every", "all". For each hit, decide whether the bunks can contradict it, then reword or swap in a crew token. Add a test: over seeds 1-40 at every size, no generated brief or key states a head count that differs from the ship's crew. Rebuild the 1.18 zip only if src changed. Don't touch the pack: its ships are already read and fixed.
• Done when the grep is reviewed line by line, every real contradiction is fixed, and the test is in and passes.

01:39: story text never sends players to a room the ship doesn't have

• Why: the pods are already guarded (a podless ship never mentions pods), and every log or salvage line goes to a room that exists (at). The text itself is not checked, though: a hook like "the two locked in the galley", or a log that says "check the lab", can land on a ship with no galley or lab. A GM reading it out sends the players to a room that isn't on the map. That is the same class of fault as the pod counts, one level up.
• Do: measure first. Over seeds 1-60 at every size, derelict, find each room word in the brief and key (galley, lab, medbay, armoury, hangar, cargo hold, life support, engineering, crew quarters, bridge, drive) and check the ship has that room. Fix what's real: extend sayable to rooms, the way it works for pods, so a line naming a missing room is dropped when there is an alternative, and ships that have the room roll exactly as before. Add a test. Don't touch the pack or the posted days.
• Done when the measurement is written down, the real cases are fixed and tested, and the full suite passes with pipefail before any deploy.

01:51: do our own pages rank yet for what a GM types

• Why: the itch pages are noindex until itch reviews them, so only bulkhead.bananafest-destiny.com can be found by web search. The last check (LEARNED, day 19) found no rank for the generic searches. That's the gap between the 26 itch views and any buyer.
• Do: run WebSearch on five searches: "starship deck plan generator", "random derelict ship map generator", "spaceship deck plan maker", "sci-fi ship battle map generator free", "deck plan editor browser". For each, note whether any bulkhead.bananafest-destiny.com page appears and what holds the top spots. Read the top competitor page for the closest miss and compare it with our matching page (title, h1, what the first screen says). Use WebSearch only, with no scripted SERP scrapes.
• Done when: a table of five searches → our position (or absent) → top three results is in the actual, and one concrete change to our page is either made and deployed (with tests and status green) or named with the reason it waits.
• Not doing: posting anywhere, or asking the boss for anything.

02:01: every deploy dates the sitemap itself

• Why: a hand deploy left the sitemap's dates stale on 4 pages until the next daily run. Search engines use that field to decide what to recrawl, and we are being crawled slowly (14 of 40 pages).
• Do: make the npm deploy script run sitemap-lastmod.mjs before the build. Running it twice in the daily run is harmless, since it rewrites nothing when the dates match. Check: --check is clean, a deploy with no content change leaves the git tree clean, and the daily script still works because it calls npm run deploy.
• Done when: package.json is changed, a deploy runs clean, status is 29/29, and it's committed. Tests aren't needed because no src changes.

02:03: the rest of the place words: bridge, reactor, core, airlock, pods, cryo

• Why: the 01:39 test only knows ten room words. The story also names the bridge (35 times in the source), the reactor or core, the airlock, the escape pods or pod bay, and cryo. Any of those can be missing from a generated ship's map. The one-shot text isn't checked at all, and it's what a buyer prints.
• Do: in a temp test, walk seeds 1-60 at every size and both moods. Collect the brief, the room notes and the one-shot text, then list each place word that appears with no matching room or fixture on the map. Map each word to what has to exist: a room name, or for the airlock and pods a door kind or stamp. Fix with {Room?yes|no} the way 01:39 did, or with sayable(). Add the words to the permanent test and prove it fails against the old code.
• Done when: the counts before and after are in the actual. If anything changed: tests pass with pipefail, the 1.18 zip is rebuilt, ?v= bumped, deployed and checked live. The 8 pack ships get the same check; they get fixed only if one fails.

02:20: the four Eight Derelicts ships without an airlock get one, before upload

• Why: Gossamer, Sandpiper, Quillon and Rowan send players "through the airlock" or "the forward lock", and their maps have none. A buyer who prints the map and reads the one-shot finds a door that isn't there. Quillon is the boarding plot, where the whole story is a cut airlock. The pack isn't uploaded yet, so it can still change.
• Do: back up the 4 folders to the scratchpad. Add one airlock door per ship file with the generator's rule: a hull edge, corridor first, not the bridge, not on furniture, not facing a hull hole, and in a fore position if the one-shot says "forward". Re-export the PNG, .dd2vtt, key and A4 adventure for those ships the way 21:07 on 1 Oct did, on a paid dev server with a temp script in app/scripts that is deleted afterwards. Diff old against new: only the new door should differ in the ship file, the .dd2vtt should gain only a portal, the key should be the same, and the PDF should show the airlock on its map. Re-zip with the same file list, then unzip -t.
• Done when: all 8 ships pass the airlock check, the zip is rebuilt, press ?v= bumped, deployed, and the live cmp is same.

02:28: the boarding story's cut airlock goes in the room the airlock opens into

• Why: the boarding cause has a hazard, "cut airlock; the frame is scored and the inner door will not seal. This room is vacuum." It has no room tag, so it lands in a random room. On Quillon it sat in the cargo hold, and I had to put the door there by hand to make the story true. Every boarding derelict the generator or the daily makes has the same mismatch: the key says the airlock is in a room that has none.
• Do: - give that hazard a lock tag: it goes only in a room an airlock door opens into, on any deck; - if the airlock opens onto a corridor, or a hole took it, drop the hazard, as notes for rooms a ship lacks are already dropped; - measure first, on 60 seeds of each size, how often each case happens; - add a test: whenever a key says "cut airlock", that room touches an airlock door; - run the full suite with pipefail, then deploy if clean. The daily builds from the working tree, so nothing unverified stays in src.
• Done when: the test passes, it fails on the old code (backup under a unique name, in its own step), the suite is green, and it's deployed and live.

02:40: a boarded ship keeps at least three hazards

• Why: the 02:28 actual says the other hazards still give a boarding ship 3 to 5. I measured it afterwards, on 60 seeds of each size: 1 corvette in 31 boarding ships now has 2, because without the cut airlock the pool is the bridge charge, the last stand, and two notes that need a cargo hold or life support. The old code gave 3 to 5.
• Earlier, on a worktree: the four app/switch patches apply on HEAD and the switched tree passes tsc. So task 1's switch is ready.
• Do: add one untagged hazard that fits a boarding, so every boarded ship's pool has at least 3 without a room tag. Re-measure, run the tests, deploy, rebuild the 1.18 zip and bump press ?v=. Correct the 02:28 line in the actual.
• Done when: the minimum is 3 on every size, the suite is green, and it's deployed and live.

02:48: does every cause fill its hazards, logs and loot on every size

• Why: storify asks for 3 to 5 hazards, 3 logs and 2 to 3 loot, but drops any note tagged for a room the ship lacks. The boarding cause fell short today. The other causes have never been counted the same way, and a shuttle has few rooms.
• Do: on 60 derelict seeds of each size, count Hazard:, Log fragment and salvage lines per ship, by cause; list every cause and size that comes in under its floor. Fix whatever falls short with untagged notes that suit the cause, and leave the rest alone.
• Done when: the counts are written down, and either nothing is short or the short ones are fixed, tested, deployed and the 1.18 zip rebuilt.

03:10: the three Eight Derelicts ships under the note floors get their missing notes, by hand

• Why: the generator now promises at least 3 hazards, 3 logs and 2 salvage. Three pack ships were made before that: Gossamer has 2 logs, Quillon has 2 logs and 1 salvage, and Lodestar Station has 1 salvage. Their one-shots have thinner Salvage and Logs sections than the free daily will from now on. The pack isn't uploaded, so it can still change.
• Do: - back up the three folders; - write each missing note by hand for that ship's own story (cause, crew names, rooms), into a room with no note of that kind; - re-export the key and A4 adventure, plus the PNG and .dd2vtt so the folders stay one export; - diff: the key and PDF gain only the new lines, and the PNG and .dd2vtt are unchanged; - re-zip, unzip -t, press ?v= bump, deploy, live cmp.
• Done when: all 8 meet the floors, and the zip is live and the same as local.

03:16: a derelict with no airlock left is never the one taken at the airlock

• Why: the 02:20 test only reads the Getting aboard section. Over the whole one-shot and brief, 6 of 1200 derelicts have no airlock left after their holes. One of them (shuttle 139) is the boarding cause, and its brief, clock and a log all talk about the cut airlock. The other five only mention the armoury's door lock, which is fine.
• Do: when the ship has no airlock, leave out any cause whose brief mentions an airlock, the way a podless ship already drops pod lines. pick() makes one r() call either way, so only the lockless ships can change. Prove it with a hash compare, and widen the test to the whole PDF and the brief. Then suite, deploy, rebuild the 1.18 zip, and bump press.
• Done when: no lockless derelict's text mentions an airlock, the other ships are byte-same, and it's live.

03:30: read the next three daily derelicts' one-shots as a GM before they post

• Why: the daily post is public and the one-shot is what the $12 file sells. Each read-through so far found a real fault: the cut airlock, the note floors, the lockless boarding. Today's ship (2 Oct) posts at 11:07, after today's fixes.
• Do: build the 2, 3 and 4 Oct ships the same way the daily does: same date seed, same size, from the working tree. Dump each one-shot's text, plus the key and the brief. Read them for anything a GM would trip on: a room or person the map lacks, a contradiction between brief, clock and notes, a count that doesn't match, an unclear instruction. Fix a fault in the generator only if it's general; prove it on the 1200 and the suite before deploying.
• Done when: all three are read, and every fault is either fixed and live, or written up with why it was left.

03:55: read one one-shot for each of the five causes not yet read today

• Why: the 03:30 read of three causes found four faults (235, 37, 37 of 1200, plus a "deck 2"). Five causes are still unread: 0, 1, 2, 5 and 7 (debris, reactor, Lot 14, the drive field, the thing in the ducts).
• Do: take the first seed from 1004 up that gives each cause, spreading the sizes across shuttle, corvette, freighter and station. Dump the brief, key and PDF text, and read them as a GM. A fault gets fixed in the generator only if it's general: measure it on the 1200, check that the other ships are byte-same, add a test that bites, check the pack's 8 ships, run the suite, rebuild the zips and deploy.
• Done when: all five are read, and every fault is either live and tested, or written up with why it was left.

04:26: read today's and tomorrow's daily one-shots before they post

• Today's 11:07 corvette and tomorrow's freighter come from the date seed and today's working tree. Once they post, the PDFs are public, archived and in the weekly zip. Reading them now means a fault gets fixed before it goes out, not after.
• Generate both the way the script does: the same size and seed, through daily-derelict.mjs's own path. Read each as a GM, end to end: the brief, the ways in against the drawn doors, every room note against the brief, the trail, the d6 and the endings. Check it against everything fixed today (ways in, cold, reactor, weld, misjump) and anything new.
• Fix in src with a word-only change and a biting test, as before. Don't run the daily by hand, and don't touch an already-posted day.
• Search follow-up, nothing to do today: re-run the 40 inspects on 9 Oct and compare against FACTS 2 Oct. Don't resubmit the sitemap unless it changes.
• Done when both days read clean, or are fixed, tested and deployed, before 11:00.

04:51: read an indexed daily page as a visitor from search, and see where it leads

• Search Console (FACTS, 2 Oct): of the 15 indexed pages, 7 are daily pages. They are what Google holds. A visitor who lands on /daily/2026-09-20/ from search: what do they see, what can they do, and how many steps is it to the $12 itch page or the Eight Derelicts mention?
• Read the live page on a phone-width viewport. Playwright blocks cloudflareinsights, /e/ and /go/. Check the order: the map, the story, the download, the editor link, the paid link. Count the words before the first action.
• Compare with what events.sh and visits.sh show for daily pages: views against clicks out, so far.
• Change only what the numbers or the read clearly point to. A wording or order change in daily-derelict.mjs's page template, rebuilt for all days (no regeneration of ships, no --force). Measure before and after.
• Done when the read is written down, with any change deployed and checked, or with a reason to leave it.

04:54: per sitting, do web visitors who press Generate ever see a derelict?

• 25 Sep to 1 Oct: 103 intact presses against 13 derelict. Intact is the select's default; the story, the key and the one-shot only come with a derelict. One phone made 58 presses on 1 Oct, so raw counts mislead.
• Group generate-intact and generate-derelict events into sittings (same visitor hash or country+device, presses under 30 min apart), skipping my own headless runs and the daily's. Per sitting: intact only, derelict only, or both, and whether a sitting that saw a derelict did anything after (save, key, link, .dd2vtt).
• If most real sittings are intact-only: make derelict the default in the select (the daily sets the mood itself, so it's unaffected), with a test, then deploy and add a before/after line to the 4 Oct check. If sittings do switch to derelict on their own, leave it.
• Done when the table is written in actual, and the default is either changed and live or left with the reason.

05:02: rebuild the 1.18 zip with the new intro, so task 1 uploads what the demo runs

• The intro change reaches the paid file too: its first-open intro now hides the intact button instead of relabelling it. The result should look the same to a buyer, but the zip on /press/ (?v=1016) was built before it. The standing rule is to rebuild after any src change a buyer gets.
• Run node scripts/release.mjs 1.18 (it must end "the paid file is sound"), and open the paid file's first-open intro in a fresh browser: one visible button, "Generate a derelict", and pressing it gives a derelict with its One-shot button. Bump ?v= to 1017 on /press/ and itch-description.html, deploy, and cmp the live zip.
• Done when the live zip matches the local build and the intro reads right.

05:04: count which button a sitting starts from, intro or toolbar

• The 4 Oct read will judge the new intro by sittings that see a derelict. But /e/generate-derelict is the same event from the intro button, the toolbar and the card's Another one. So a toolbar press by a returning visitor and a first-time intro press look alike.
• Add one bare event on each intro button (intro-derelict, intro-intact) beside the generate count, the same as intro-pic. No other change. The entry-pages test checks both handlers send it, and fails without them. Run the suite, deploy, and check on the live site with /e/ fulfilled that one press sends both events. events.sh lists them with no change, since it prints any /e/ path.
• Not the paid file: count() is a no-op outside the demo (check this first). If it isn't, leave the zip alone and note it.
• Done when it is live and seen firing.

05:12: read Search Console with --fresh: any query or page since the 2 Oct baseline?

• The baseline (FACTS 2 Oct) was 6 impressions in a month, with data about 2 days behind. --fresh adds the days still changing. Read query, page and date for 25 Sep to today. No inspects: those are for 9 Oct.
• If a query shows up, note which page it hit and whether that page leads to the editor or itch. If there's nothing, write the line and move on. Search is slow by nature, and the 9 Oct re-inspect is the real check.
• Done when the numbers are in actual, and any new fact is in FACTS.

06:07: look at what a first-time phone visitor sees after pressing the new intro button

• Since 05:00 the intro's one button makes a derelict. That screen is now the first thing most visitors see, and 16 of 22 sittings never pressed a second time. So it has to land on the first press.
• On the live site at phone width (390x844) and desktop (1280x800), in a fresh browser with /e/, /go/ and insights blocked: press the button and screenshot the screen at once, then after scrolling down through the story. Do it 3 times per size. Check the map is readable and not hidden under the card, the story is whole and in view, and the next step (Save, Room key, Another one, the $12 line) is obvious without scrolling past settings.
• Fix only what is clearly wrong: a hidden map, a cut-off story, or a buy line that doesn't show. Test the fix, deploy and screenshot again. If it reads well, write that down and leave it.
• Done when the screenshots are read and any fix is live.

07:08: before 11:07, run today's code through the daily's own path and the Owlbear harness

• main.ts changed three times since the last daily (the intro, the intro counts, the fit and the note boxes). At 11:07 the daily rebuilds store/bulkhead.html from this tree and drives it in Playwright, and a failure costs a public day.
• Owlbear: obr-harness ok, exports and player against the live site. (Run just before this entry was written; noted in actual.)
• The daily: npm run build:paid, then copy to store/ as the .sh does, then daily-derelict.mjs for 2099-01-07 (a Wednesday, so no weekly pack). It writes a day folder and rebuilds /daily/ and its feed, but doesn't deploy or post. Read its output and the files it made. Then delete the 2099 folder and git checkout every file it touched, and check git status is clean apart from store/.
• Done when the dry run has made a full day with no error and the tree is back, or a fault is found and fixed before 11:07.

07:10: check the intro-derelict and intro-intact counts reach the event log

• Why: the 4 Oct read splits sittings by where they started, using /e/intro-derelict and /e/intro-intact (deployed about 05:12). If those requests never reach Cloudflare's log (blocked, wrong path, dropped by the UA filter), the read finds nothing, and I'd learn that two days late.
• How: run events.sh since 05:00 and look for intro-* lines. If real visitors have come and there are none, press the live intro once in a real (non-headless) UA pattern isn't possible here, so instead check main.ts's count() path and a curl of /e/intro-derelict for its status. Fix any gap before 11:07.
• Done when: intro-* shows in the log, or I've shown why it can't yet (no visitors since 05:12) and that the path answers.

07:13: what a visitor to /owlbear-rodeo-dd2vtt/ sees first

• Why: it's the third most viewed page since 28 Sep (16 views, after / at 83 and /maps/ at 22). Owlbear is the one channel where a store listing is coming. Copy and Rogue clicks have only been counted since 1 Oct, so the 4 Oct read can't say yet whether the page works. I can check now whether its first screen gives the install link and what the extension does.
• How: screenshot it on desktop (1280x800) and phone (390x844) with Playwright, blocking /e/, /go/ and the beacon. Is the manifest URL with a Copy button, or the Rogue link, above the fold? Does Copy put the exact manifest URL on the clipboard? Does the manifest URL answer 200 with 1.17.2?
• Done when: either both screens show the install step without scrolling and Copy works, or I've fixed what doesn't, with a test or a smoke check and a deploy.

07:14: what /maps/ visitors see, and why so few go on

• Why: /maps/ is the second most viewed page since 28 Sep (22 views), but only 4 map-page views followed, and no editor visit came from /maps/ (from/self/maps/ is 0). Something on its first screen isn't pulling people on, or they just wanted a picture.
• How: screenshot /maps/ on desktop and phone with Playwright (block /e/, /go/ and the beacon). What's above the fold: a thumbnail grid they can click, or text? Where's the editor link? Check where those 22 views came from (by country, device and referrer), as far as the request log says.
• Done when: I can say what the first screen offers and have fixed anything plainly broken or hidden (a test or smoke check, a deploy). Otherwise I write down what to judge on 4 Oct.

07:16: send the pages Bing hasn't read through the broker's bing-submit

• Why: 18 pages are "Discovered - currently not indexed" in Google, and that includes every keyword landing page and /maps/. Google has no API for that, and the README says resubmitting the sitemap is a hint, not a fix. Bing does have one: bing-submit, 20 URLs a day, which I haven't used yet. LEARNED (26 Sep) says IndexNow's "200 accepted" left Bing reading one page in a week, so this is the other door. It needs nothing from the boss.
• How: pick 20, landing pages and /maps/ first: /derelict-ship-map-generator/, /free-sci-fi-battlemaps/, /owlbear-rodeo-dd2vtt/, /starfinder-deck-plans/, /maps/, then the map pages and the /deck-plan-generator/ pair. One bing-submit call, then record the answer verbatim. On 9 Oct, look for bingbot hits on those paths in the request log.
• Done when: the call has answered and its result is in FACTS, with the 9 Oct check in Next.

08:08: a kept sittings script for the 4 Oct read

• Why: every read of sittings (1 Oct, this morning's 22 sittings, the /maps/ read at 07:15) used a temp script I wrote again and then deleted. The groupings drifted (by minute, by hour, with a UA hash or without), so the 4 Oct numbers wouldn't compare cleanly with the "3 of 22" baseline. Before that, at 08:07, I re-checked PR #174 (the one review from 24 Sep, already fixed that day; still waiting on task 2) and /go/ buy counts (brief leads, 30; /go/ isn't backed by itch views, so not a signal).
• How: app/scripts/sittings.sh [since] [until]. It pulls /e/ events with datetimeMinute, country and UA, drops my runs and bots the way events.sh does, and calls one UA+country within a 30-min gap a sitting. It prints one line per sitting (start, country, phone or desktop, the events in order), then totals: sittings, sittings that saw a derelict, intro-derelict and intro-intact starts, and saves (brief-png, export-*, brief-link).
• Done when: run over 28 Sep to 1 Oct, it gives the same 22 web sittings and 3 that saw a derelict as this morning's count, or I can explain the difference. Then it's committed, and Next points at it.

09:07: is /press/ task 4 (Bing import) still needed, and is task 9 stale?

• Why: the boss's phone task page should only ask for things that still matter. Task 4 says Bing has none of our pages and asks the boss to import the site into Bing Webmaster Tools. But the broker's bing-submit took 20 URLs at 07:16, and Bing's submission API only works for a site verified in the account. Task 9 is dated "Wednesday the 30th", which has passed. (I started reading these at 09:07, before writing this entry.)
• How: bingbot hits in the request log since 25 Sep (done: it crawls about daily). Check Bing's index with WebSearch. Read what FACTS says about the broker's Bing access and about task 9's thread. If task 4 is done in effect, take it off /press/ (or mark it) and say why. If task 9's date has passed, check it off or re-date it from the facts.
• Done when: /press/ asks only for what's still open and true, deployed and checked live, with no boss-voice text changed beyond that.

09:09: the desktop first press at 1366x768 and 1920x1080

• Why: the first real start from the new intro was a GB desktop that pressed once and left. I only checked desktop at 1280x800, where the ship now fits beside or below the story card at about half its old size. The two most common desktop screens are 1920x1080 and 1366x768. A short 768 screen could leave the ship tiny under a tall card.
• How: on the live site, with /e/, /go/ and the beacon blocked, press Generate a derelict at both sizes, five seeds each. Take screenshots and measure the ship's drawn width and height in CSS px, and whether the card covers it. I'll judge by looking: a ship under about 300 px across, or rooms too small to read their numbers, is a fault.
• Done when: both sizes look right, or I've found a fault and fixed it with a test, the smoke check and a deploy. Don't change it on taste alone (see the Next note).

10:07: how often a room's name is drawn over a stamp

• Why: at 09:10, on 1920x1080, ENGINEERING ran over a console stamp. Labels go on a room's bottom row (generate.ts), and the generator puts stamps against walls, so they can meet. The PNG and PDF a buyer exports draw the same way. A name you can't read on a printed map is a fault in what the $12 file sells, not just something on screen. (Before this I checked at 10:07 that every unindexed landing page is linked from pages Google has indexed: it is.)
• How: a temp vitest (written to a scratch file, removed after) generates 200 ships (4 sizes, both moods, 25 seeds). For each label it estimates the text box in squares (about 0.6 x size per character wide, size tall) and counts the ones that cross a stamp's footprint. If it's common, move the label to whichever row of the room (bottom or top) is clear, or skip the stamp under it, with a test that fails on today's code.
• Done when: I have the rate. If it's above a few per cent of labels, the fix is in, tested, deployed, the 1.18 zip rebuilt and /press/ ?v= bumped. If it's rare, it's written down and left.

11:07: daily check, and the store copy after the halo

• npm run status. If today's derelict is missing or the feed is stale, run the day by hand as the daily instructions say.
• The daily rebuilds store/bulkhead.html from the tree. Check that the only change is the label halo (diff size, strokeText present), and that the paid build is still sound.
• Note itch views (baseline 26 on 1 Oct) and today's Bluesky likes.
• Done when status is all clear (or fixed) and the store copy is accounted for.

11:12: today's daily image with the label halo

• RSV Kestrel is the first public image drawn since the halo went in. Open its PNG and look at every room name: readable, no thick dark ring on blueprint, nothing over a stamp left unreadable.
• Done when it is looked at; if a name looks worse than before, the stroke width comes down and the change is redeployed.

12:07: why the 2 Oct daily didn't start on its own

• The daily was missing at 11:07 and nothing was running. Find what is supposed to start it (the session cron a41fca10, or anything else), when it last fired, and whether it will fire tomorrow.
• Done when I know the cause and either it's fixed or tomorrow's fallback is written down. No new schedulers outside what's already allowed (system crontab is denied).

12:32: a real daily timer on OptiServer

• The boss: "You're on optiserver". My shell is a bwrap sandbox on that host, so I can't install anything into the host's systemd myself, and ~/.config is outside where I may write.
• Write app/scripts/daily-host.sh (nvm's node on PATH, credentials loaded in the subshell form, a lock so two runs can't overlap, then npm run status, a log under app/ that git ignores) and a user service and timer at 11:07 UTC with Persistent=true, so a day missed while the machine was off runs at the next boot.
• Test the wrapper here with env -i (no inherited PATH or variables) against a day that is already posted: it must skip, and status must come out all clear.
• Move my session cron to 11:37Z as a watcher only, so it never races the timer.
• Then give the boss one paste: copy the two units, daemon-reload, enable --now, and enable linger (needs sudo). Only after the test passes.

13:07: the pages Google already shows, and what they show

• itch views were flat at 26 all day; LEARNED says the gap is arrivals. Read Search Console (broker, --fresh, last 28 days) by page and by query: impressions, position, clicks.
• For the page with the most impressions near the first page of results, read the title and description Google would show. If they don't say what the page gives (a free generator, free maps), rewrite them so a searcher would click.
• Done when the numbers are written down and either one page's snippet is changed, deployed and live-checked, or the read shows there's nothing to act on yet.

13:08: Owlbear store PR #174, anything new

• Read the PR's state, comments and reviews from GitHub's public API (no token). Done when written down.

14:07: does Google have our current sitemap

• 6 pages were "URL is unknown to Google" on 1 Oct. Read the broker's sitemaps answer: when Google last downloaded sitemap.xml, how many URLs it counted, any errors. Compare with the live sitemap's URL count.
• If Google's copy is older than the newest pages, submit it once (5 a day cap) and inspect one unknown page. If it's current, the unknown pages just wait for the 9 Oct re-inspect.
• Done when written down.

14:08: is the daily Bluesky post itself the problem

• 0 likes was noted at 11:12 for today and yesterday. Read the last six posts' text and counts from the public API before changing anything about the post.

15:07: where today's visitors came from and went

• Today's daily got a repost. Run scripts/events.sh from 2 Oct 00:00 for today's views, from/ sources and editor actions, and scripts/visits.sh for page visits. Look for one specific leak I can fix without the boss, for example a day page that gets visits but sends nobody to the editor.
• Done when the numbers are written down and either one fix is made, tested and deployed, or the leak is named for a later read.

16:07: the after-export dialog offers the save it asks for

• After a first export the demo shows the upsell, whose hint says to save the ship as .bulkhead.json first, but the "Save this ship first" button is hidden there (keep=false). Show it: right after an export, the ship on screen is the one they made.
• Also: showUpsell() with no title keeps the last title. After a locked .dd2vtt or PDF click, the after-export dialog would carry that title. Pass the watermark title and lede explicitly.
• A test in entry-pages.test.ts, tsc, full suite (pipefail), deploy, check the live bundle. The paid build doesn't show the upsell, so the 1.18 zip needn't change; confirm by building it and comparing md5.

17:07: the upsell dialog on a phone

• Most visitors are on phones. At 390x844 and 360x640 (a small Android), open the after-export dialog and the locked .dd2vtt one. Check that the title, the $12 line, and all three buttons are on screen or reachable by scrolling, and that nothing is cut off. Screenshot both.
• If something is cut off, fix the CSS, test, deploy and re-shoot. Otherwise write it down.

17:08: does the $12 file work on a phone

• Most visitors are on phones. Look for any record (LEARNED, FACTS, the itch page) of the paid HTML file being opened on Android or iOS. Done when written down, with a test for the batch if nothing is known.

18:07: the paid file from disk in WebKit and with storage blocked

• Open store/bulkhead.html as file:// in Playwright WebKit (Safari's engine) as a phone at 390x844, and in Chromium as a phone with localStorage throwing. Press Generate in each and watch for page errors.
• This doesn't replace the real-phone question (iOS Files preview, Android file managers), but a crash here would answer it early.
• If something breaks, fix it in src, test, rebuild the paid file and the 1.18 zip, and bump ?v=. Otherwise write down what passed.

22:07: the live demo in Safari's engine

• smoke.mjs checks every page and the first press in Chromium only; 7 of the visits since 25 Sep were MobileSafari. Run the live site in Playwright WebKit as an iPhone (390x844, touch): every sitemap page for page errors, then the first press (intro derelict, room notes not cut off), a PNG export, and the after-export dialog.
• If WebKit finds a fault, fix it in src, test, deploy, and check again in WebKit. If it finds none, add a WebKit first press to smoke.mjs so it stays checked.
• Block cloudflareinsights, /e/ and /go/ as smoke does.

23:07: read four more one-shots as a GM, multi-deck first

• Every read-through today has found a fault in the paid text, and 1.18 is not on itch yet, so a fix still reaches every buyer. Generate one-shot PDFs at new seeds (2201-2204: freighter, station, two corvettes), pdftotext them, and read each end to end as a GM preparing a session. Watch most closely for what crosses decks: the trail, Way in lines, logs naming rooms.
• Fix what's plainly wrong in src with a test, then rebuild 1.18 (release.mjs, press ?v= bump, cmp the live zip) and deploy. If nothing is wrong, say so and note what read well.

00:07: sweep every station's text for ship-only words

• Two of the last read's five faults were hull words on a station ("left port", "aft section"), and each read sees only one station. Generate stations at seeds 1-300, intact and derelict, and collect the brief, every key note and the one-shot's own sections (the say() text in adventure.ts). Grep them for words a station can't have: aft, fore/forward, port (as harbour), jump, drive, hull frame, voyage, "the ship", "this ship", helm, heading home, under way.
• Read each hit in context. Fix the wrong ones in STATION_WORDS or the station alternative, and add the sweep as a test, so a new story line can't bring a hull word back. Then the 1.18 rebuild, deploy and cmp, as last time.

Next

• 3 Oct: if the boss installed bulkhead-daily.timer, app/.daily-log/2026-10-03.log should start near 11:07Z with "daily-host start". The watcher (406fff8d, 11:37Z) reads it. If there's no log, the timer isn't installed or didn't fire: run daily-host.sh by hand and ask once. The watcher expires around 9 Oct; once the timer has run two days on its own, let it expire.
• 9 Oct, with the Google re-inspect: count bingbot hits since 2 Oct 07:16 on the 20 paths sent with bing-submit (/, the 7 keyword pages, /maps/ and the 11 map pages), against the 26 Sep week, when IndexNow alone left bingbot reading one page. If Bing still hasn't read them, bing-submit is as empty as IndexNow, so stop spending turns on it.
• First press, desktop: the ship now fits below the card, about half the size it was. If the 4 Oct sittings show desktop visitors leaving after the first press more than phones do, try letting a long ship run under the card's lower edge (fit to the stage minus the card's height only on its right part). Don't change it on looks alone. The switch patches applied 4 of 4 at 06:19.
• Real-room batch, after task 1: in Owlbear with Dynamic Fog, check that a bridge "Window" (now sent closed) stops a token and that the GM can open it with the door tool. The source says yes. This is just to see it.
• If a GM ever reports a room with no way in on a derelict: it opens on a hole (the 13:09 guard test proves it). Check how a breach draws at small sizes and in the PNG before touching the generator.
• itch support follow-up: it's task 3 on /press/ (a reply in the 18 Sep thread). After task 1, a 1.18 devlog replaces the unpublished 1.17 draft. Devlogs get indexed even while the page isn't. Once indexed: add the ttrpg tag and re-run itch-indexed.mjs.
• Today 11:07: the daily check. If the ship has a cut-off room, check that the day page shows the Way in line with its violet edge, the full one first. Bulkhead's itch views were 26 on 1 Oct; note the change. Today's (2 Oct) Bluesky post: 0 likes at 11:12, 2 likes and 1 repost by 14:09. A three-hour read is too early.
• /maps/ from 4 Oct: Free maps is the intro's second visible button now. Count sittings that go / → /maps/, and whether they open a map page or come back and press Generate (before: 8 of 9 /maps/ sittings came from /, and none opened a map page). If it only pulls people away from the derelict, move it under More.
• Owlbear path, from 4 Oct: views of /owlbear-rodeo-dd2vtt/, then obr-copy and obr-rogue (counted since 1 Oct, 12:10), then obr-view, then obr-send, in events.sh. If people view the page but nobody copies, the page is what to fix. If they copy but nothing opens the panel, look at the install step in Owlbear. After each daily, run the switch check on a worktree.
• Phone Generate sittings after the room key fix (deployed by 07:17): per sitting, do phones now press Another one, Save or Link? Also per sitting: intact or derelict, and where it started (intro-derelict / intro-intact are counted from 2 Oct, about 05:12; the demo intro has led with the derelict since 05:00). Before, by app/scripts/sittings.sh 2026-09-28T00:00:00Z 2026-10-02T00:00:00Z: 5 of 29 web sittings saw a derelict, 1 saved or linked, 9 pressed more than once (the 04:54 count of 3 of 22 was off; see the 08:08 actual). Run the same script from 2026-10-02T05:12:00Z for after. 25 Sep to 1 Oct counted 103 intact presses against 13 derelict, but one phone made 58 presses on 1 Oct. If real sittings mostly stay on intact (the select's default) and never see a story, try derelict as the first press, then measure saves. Group by hour, country and device as on 1 Oct (a temporary script in app/scripts/, removed after). Read from/ alongside it.
• Batch question after task 1, on the same Android phone: download bulkhead-1.18.zip from /press/, unzip it, and open bulkhead.html. Does the editor run, and does Generate work? Then the same on an iPhone if there's one to hand. The file itself runs from disk in WebKit and in Chromium as a phone, even with storage blocked (the 2 Oct 18:07 actual); what's unknown is whether the phone opens it in a browser at all. If it doesn't, the itch page and the demo's upsell must say "for a computer" before anyone pays.
• Batch questions after task 1, all in one real Owlbear room. First, the .dd2vtt export from the panel on an Android phone: does a "downloaded" notice show, what is the file called in Downloads (it should end .dd2vtt), and does a two-deck ship bring up a "download multiple files?" prompt? (BR, 30 Sep: three presses, then a desktop save 25 min later. No sandbox on the frame and ~1 s to the download, checked 09:07.) Then a hex send and dragging in a -WxH PNG.
• Before task 1: after any src fix a buyer would get, rebuild bulkhead-1.18.zip (release.mjs), bump ?v= on /press/, cmp the live zip. Rebuilt 01:17 with the one-shot wording fixes. The Eight Derelicts zip was rebuilt by 01:20 with the same fixes; the 1.18 zip is on ?v=1019 (rebuilt after the reactor, weld, misjump, seal and twist wording fixes, and the 2 Oct intro change); the Eight Derelicts zip is on ?v=1019 (unchanged since 1016) (all 8 PDFs re-made 2 Oct for the twist line; Sandpiper and Willet notes fixed by hand), rebuilt with airlocks and note floors on all 8 ships. From the upload on, pack ships don't change.
• Old .dd2vtt walls: done on 1 Oct (the daily archive, the weekly zip, Foundry 1.4.0). The /maps/ pages and both free packs (store/ = public/packs/; store/ is what I prepared for itch, but I can't see itch's uploaded files, so this is an assumption) already had the right walls, so the itch free packs need no re-upload. Drop that from the after-task-1 batch.
• Task 1 is still with the boss. On "done", follow app/switch/README.md: four patches in order, then map-pages.mjs, deploy and the checks.

00:08: the day page shows a Way in line like the other key lines

• daily-derelict.mjs's key renderer now gives "Way in:" lines the same tag treatment as Hazard, Salvage, Trail and Log, with a violet edge. It changes two lines in place, so the switch patches' line numbers hold.
• I ran a real key through the page's own renderer and style at 390 px (corvette 18, three cut-off rooms) and found a bug from yesterday. The chain ran in grid-scan order, not key order, so the Bridge (1) said "like the Crew quarters (3)" and the full sentence sat two rooms further down. generate.ts now chains the rooms in key order: the first by number gets the full line and the rest point back up. No dice, so every ship still rolls the same. A new test ("the first Way in line in key order is the full one") passes with the fix and fails without it on corvette 18. The full suite was 50/50 before the test was added; the new test alone passes.
• Neither the story card (it picks only Hazard, Log and Salvage) nor the post text (built from the brief) reads Way in lines. Unchanged.
• Eight Derelicts: each ship has at most one cut-off room (Coldharbour, Willet), so the pack's text is unchanged. No re-export.
• 1.18 zip rebuilt (paid-check: "the paid file is sound"). The new build has one more room-number sort than the old one. /press/ links bumped to ?v=1002. The live zip and the itch description match by cmp.
• Deployed. Status: all 29 clear. Smoke: 42/42 pages and 42/42 links. Switch patches 1 to 4 applied in order to this tree: all OK.
• The first day page that can show it is the 11:07 run's, if today's ship has a cut-off room.
• Finished 00:16

01:07: read four generated one-shots the way a GM would

• Generated the one-shot PDF for seed 501 at each size (shuttle, corvette, freighter, station) and read each one the way a GM would before a session.
• Three things were plainly wrong, and all three are fixed in src: - The log handouts were headed "CPT.", "XO", "ENG." and so on. Across the table that reads like a typo. They now read "THE CAPTAIN'S LOG", "THE XO'S LOG" and so on (LOG_OF in adventure.ts). Any other speaker falls back to the old header. - The trail promised "the only account aboard from someone who was there", but the same PDF hands out other crew logs. Two trail endings and the summary line now say "a recording of the last day, from someone who was there". The third trail said "the first account aboard"; it now says "start to finish". - A mutiny hook said "a ninth crewmember on neither list", but crew counts come from bunks, so a five-bunk ship said ninth. It now says "one more crewmember, on neither list".
• What read well: the station's trail (galley, lab, life support across two decks), the getting-aboard choices, the dangers tied to rooms, and the doctor line in salvage.
• Noted, not fixed: room names repeat across decks (station seed 501 has Lab 4 on the hub deck and Lab 2 on the ring deck; the freighter has two Engineering rooms). The number and deck tell them apart, so it isn't wrong, only a little flat.
• Old wording stays where it was already published: four posted daily pages (24, 26, 27 and 30 Sep), because a posted day is a record. Three pack ships (2 Coldharbour, 4 Sandpiper, 6 Rowan) keep it in their bulkhead.json, so re-exporting those PDFs would not change it. That is the next phase.
• Checks: tsc clean, 51 tests pass. 1.18 zip rebuilt (the paid file is sound), press links now ?v=1003. Deployed; live zip, /press/ and itch-description match local. status: all 29 clear. smoke clean. All four switch patches still apply in order.
• Finished 01:17

01:18: Eight Derelicts gets the one-shot fixes before anyone has it

• Four ships carried the old trail wording, not three: Fieldfare (8) had "the first account aboard" as well. In 2 Coldharbour, 4 Sandpiper, 6 Rowan and 8 Fieldfare, the trail line in bulkhead.json and in the key .md now uses today's src wording. A word diff against a backup showed one line changed per file and nothing else.
• Re-exported all eight adventure PDFs from their saved ships at A4, the size they had. A pdftotext diff of old against new showed only the intended changes: the summary line, the trail lines, and the handout headers ("NAV" is now "THE NAVIGATOR'S LOG"; there are 2 or 3 per ship). Page counts are unchanged (6 or 8 each). Rowan's other changes are reflow only. I rendered Fieldfare's handout page and looked at it: the longer headers fit, and nothing overlaps.
• Rezipped (README.txt plus [1-8]-*). Still 57 files, the same layout. Every PDF in the zip has the new headers, and none of its PDFs, keys or ship files has the old wording. The README has no version line, so I left it alone. Press links now ?v=1004. The 1.18 zip doesn't carry the pack, so it didn't change.
• Left as published: the four posted daily days and their GM keys in the Foundry module (gm-keys) keep the old line. A posted day is a record.
• Deployed. The live pack zip, /press/ and itch-description match local. status: all 29 clear.
• Finished 01:20

01:21: no fixed head count in story text that the bunks can contradict

• Grepped every number word, plus "both" and "half", in generate.ts and reviewed each hit. Days, rounds, rifles, crates and light-years can't disagree with anything drawn, so they stay.
• Head counts: none can go over the crew. Crew is at least 2 (crewTokens), and the only fixed people counts are "Two crew are missing" and "the two locked in the galley", so both fit every ship. The plan's suspicion was wrong here.
• The real contradictions were between room notes and the furniture drawn on the map. A temporary count over seeds 1-60 at each size and mood found: - Escape pods said "Four pods" or "Six pods", but a pod bay draws one pod per cell of width (3-6), and more where rooms merge. The note matched about 1 time in 5. - The bridge said "Three stations" over 4 or 5 consoles most of the time. - The new test then caught the medbay's "two beds" over a shuttle medbay that drew one. - All three are intact-ship notes, which are what the web demo's Generate shows. Derelicts use the separate dead notes, so no posted day and no pack ship has them.
• Reworded so no count is stated: "Consoles forward; one chair is bolted at a strange angle.", "Pods along one wall. Not all of them show green.", "Every pod green. Last drill logged nine days ago.", "Autodoc and beds. Supplies: half."
• The bad-plot derelict also said the pods went "in four different directions" and "four pods launched, four headings", over a bay that POD_STATE reports as "All pods gone" with any number of cradles. It now says "each in a different direction" and "pods launched one by one, every heading different". "pods went" and "pods launched" are kept, so POD_STATE still matches. The unreachable fallback "Two more pods, both green." is now "More pods, all green."
• New test, 'a count the key gives for pods, beds or consoles is what the room draws': over seeds 1-40 at every size and both moods, any count of 2 or more next to pod, bed, station or console must equal the stamps drawn in that room. Against the committed generator it fails on shuttle intact 1 (Bridge: Three stations, drawn 4).
• Hand-finished ships, checked the same way: the example ship and Halcyon draw 4 pods, Anvil draws 6 pods, and the example's medbay draws 2 beds, so all match. Tamarind says "Three stations" over 5 consoles. It's a published free map in both packs, and a "station" isn't strictly a console, so I left it and noted it here.
• Mistake: I chained the 1.18 rebuild and deploy after a test run whose exit code came from tail, and one test had failed. My python edit to the new test replaced let said = 0 in the Cut off test as well, so that test hit an undefined variable. The bug was only in the test file, so the deployed generator was the tested code. I fixed it and reran everything with pipefail: 52 tests pass. From now on, a deploy waits on a test run that can fail.
• Checks: tsc clean, 52 tests pass. 1.18 zip rebuilt (the paid file is sound), press ?v=1005. The live zip, /press/ and itch-description match local. status: all 29 clear. smoke 42/42 pages and 42/42 links. All four switch patches still apply in order.
• Finished 01:38

01:39: story text never sends players to a room the ship doesn't have

• 64 of 240 generated derelicts (seeds 1-60, every size) had story text that named a room the ship didn't have. It was mostly medbay, galley, engineering, the cargo hold and the lab, for example "shuttle 2 has no Medbay" while the brief sent players there.
• The fix: storify now takes the same {Room?if aboard|if not} form the one-shot already used. Sixteen lines now pick an alternative when the room is missing: the drive section, the crew quarters, the ration stores, the cook's log, the corridors, torn-open crates, and the nav plates on the bridge. The quarantine account in adventure.ts does the same for Medbay.
• New test, 'the story never names a room the ship does not have': no { or } is left over, and every room named in the text is in the key. It fails against the old code at "shuttle 2 has no Medbay".
• Intact ships were already clean. The eight Eight Derelicts ships were checked the same way and name no missing room, so the pack zip didn't need rebuilding.
• Checks: tsc clean, 53 tests pass (run with pipefail before the deploy). 1.18 zip rebuilt (the paid file is sound), press ?v=1006. The first live cmp showed DIFF on the zip and /press/ while the edge caught up; a second fetch matched all three. status: all 29 clear. smoke: 42/42 pages and 42/42 links. All four switch patches still apply in order.
• Finished 01:50

01:51: do our own pages rank yet for what a GM types

• WebSearch, five searches. Ours is absent from all five; the top results are: - "starship deck plan generator": neural.love art, travellerrpgblog (Geomorph Shipyard), Wikipedia Enterprise plans - "random derelict ship map generator": itch event pages (pankodl, TresilloEffect), Scribd, DriveThru (Ideagonk, DwarfMine), delacannon's itch page - "spaceship deck plan maker": Arkenforge, a Royal Road forum thread, swrpgcommunity - "sci-fi ship battle map generator free": World Anvil's 2021 roundup, Miska's Maps, Arkenforge - "deck plan editor browser": all house decks (TimberTech, Trex, Cedreo), so it's the wrong search for us
• site:bulkhead.bananafest-destiny.com gives the root only, under an old title ("starship deck plans for tabletop RPGs").
• Our own logs (crawlers.sh, since 25 Sep): Googlebot fetched 14 of 40 sitemap pages and Bingbot 10 of 40. Googlebot has never fetched /maps/, /derelict-ship-map-generator/, /space-station-map-maker/ or /free-sci-fi-battlemaps/. robots.txt, noindex, canonicals and the sitemap are all clean. The exception is /derelict-one-shot/, which is noindex by the boss's choice and stays.
• The change: / linked /about/, which linked the three generic landing pages, so they were two hops out. The home page's link row now links /deck-plan-generator/ ("How the generator works"), /derelict-ship-map-generator/ ("Derelict ships") and /space-station-map-maker/ ("Space stations") directly. link-graph: 40/40 reachable, all three at 1 hop.
• The sitemap lastmod was stale on 5 pages. /guide/, /free-sci-fi-battlemaps/, /foundry/ and /owlbear-rodeo-dd2vtt/ changed in the Foundry 1.4.0 commit without a ledger update, and / is today's edit. sitemap-lastmod.mjs rewrote them; --check is now clean.
• Roundups: frostbytebooks "Free Starship Resources" has no date, author or way to suggest additions. World Anvil's 2021 post asks for suggestions only in its comments. A comment would be a boss-voice post for a probably-nofollow link, so I'm not asking for it.
• Checks: tsc clean, 53 tests pass (pipefail) before the deploy. Live / has all three links, and the live sitemap matches local. status: all 29 clear. smoke: 42/42 pages and 42/42 links.
• Finished 02:00

02:01: every deploy dates the sitemap itself

• The npm deploy script is now: run sitemap-lastmod.mjs, then build, then wrangler deploy. So a hand deploy can't ship a page with an old date any more.
• Correction to the last phase: the daily run already calls sitemap-lastmod, so those 4 dates would have been fixed at 11:07 today. The gap only ran from a hand deploy to the next daily run, about 12 hours, not a full day.
• Checked: a deploy with no content change printed "every lastmod already matches", deployed, and left only package.json modified. The daily script calls npm run deploy after its own lastmod run, and the second run rewrites nothing. status: all 29 clear.
• Finished 02:02

02:03: the rest of the place words: bridge, reactor, core, airlock, pods, cryo

• Survey over 480 ships (seeds 1-60, every size, both moods), covering brief, room notes, fixture notes and one-shot text. Bridge, reactor, core, escape pods, cryo and hangar are never named on a ship that lacks them. "Airlock" is.
• The real fault was in the map, not the words. 233 of 480 ships had no airlock door at all: intact shuttles 51/60, corvettes 43/60, freighters 23/60, stations 0. The spine got one random try, and it missed whenever rooms lined both sides of the spine at that spot. The one-shot still offered "Through the airlock" or "the main lock" as a way aboard.
• Fix (generate.ts): when that try misses, take the hull edge nearest mid-spine, preferring corridor over rooms. It never uses the bridge, and it avoids squares with furniture, which clearDoorways would otherwise have deleted. It draws no random numbers. Hash check, old against new over all 480: 187 identical, and the other 293 differ only by the airlock(s) added. That includes 61 two-deck freighters whose lower deck gained one. Rooms, notes, briefs, stamps and holes are unchanged, so old card links show the same ship plus an airlock.
• One derelict (corvette 25) still has none, because a hull hole took it. For that case adventure.ts swaps any aboard line that names a lock for "Through the breach. The way in that was built went with the hull..." or "Across the hull to another breach...".
• New test, 'every ship has an airlock, and a one-shot only sends players through one the map draws'. It fails against the old generator at "shuttle 1".
• Mistake on the way: a compare run restored an old backup over my first edit (LEARNED). I caught it when "nothing changed" made no sense, grepped, found the edit missing, and reapplied it.
• Eight Derelicts: 4 of 8 ships have no airlock on the map but send players through one (Gossamer B, Sandpiper A, Quillon A, Rowan A and B). Not fixed here; it's the next phase.
• Checks: tsc clean, 54 tests pass (pipefail). The 1.18 zip was rebuilt (the paid file is sound), press is on ?v=1007, deployed, and the live zip, /press/ and itch-description match. status: all 29 clear. smoke: 42/42 pages and 42/42 links. All four switch patches still apply.
• Finished 02:20

02:20: the four Eight Derelicts ships without an airlock get one, before upload

• Backed up the four folders and the old zip to the scratchpad first.
• Added the airlocks to the ship files. Gossamer and Sandpiper got one each, at the fore end of the corridor beside the bridge (Sandpiper's text says "the forward airlock"). Quillon's is on the cargo hold's hull edge, because its one-shot says "the cut airlock... the lock and the room behind it are vacuum", and the cargo hold's hazard already reads "cut airlock, this room is vacuum". Rowan got two: "the forward lock" by the bridge, and "the service lock" into Engineering, because its B line is "the engineering side, through the service lock".
• Every pick is a hull edge: not the bridge, not on furniture, and not facing a hole.
• Re-exported the PNG, .dd2vtt, key and A4 adventure for each ship from the paid dev server with a temp script, which is now deleted.
• Old vs new: - Keys are byte-same. - Each .dd2vtt gained only the new portal(s); the wall lines split around them. - The PNG and VTT image change only in a door-sized box at that spot. - The PDF text is the same: those lines already said airlock, and now the map has one.
• A slip: my first PNG compare said "no change" because it took the bounding box of an RGBA difference, which only looks at alpha. The checksums differed, so I looked at a crop and redid the compare in RGB.
• The new PNGs came out named -WxH. I renamed them to the pack's old names so all eight folders match the README.
• Airlocks per ship: 1, 1, 1, 1, 1, 2, 2, 1. All eight pass.
• Zip rebuilt with the same 57 entries; unzip -t found no errors.
• Press ?v=1008, deployed. Live cmp: same for the zip, /press/ and itch-description. Status: all 29 clear. Smoke: 42/42 pages and 42/42 links.
• Finished 02:28

02:28: the boarding story's cut airlock goes in the room the airlock opens into

• Measured on the new code, 60 derelict seeds per size: - Boarding ships: shuttle 6, corvette 6, freighter 13. The cut-airlock hazard was placed on none of them, because every ship airlock opens onto the corridor. - Stations: 6 boarding, placed on all 6, because their docking locks open into rooms. - Before this, the hazard went in whichever room came up, for example shuttle 12's Escape pods.
• Change: the hazard has a lock tag. It goes only in a room an airlock door opens into, on any deck; with no such room it is dropped, like a note for a room the ship lacks. I wrote here that the other hazards still give a boarding ship 3 to 5. That was not measured, and it was wrong: 1 corvette in 31 boarding ships got 2. Fixed in the next phase.
• Test: 'a key that says "cut airlock" is on a room an airlock opens into'. - It fails on the old code, from the unique backup: "shuttle 12 Escape pods". It passes on the new. - Full suite: 55 passed. tsc clean.
• Deployed; the live main bundle matches dist.
• The paid 1.18 zip carries the generator, so I rebuilt it ("the paid file is sound"), put press on ?v=1009, and deployed again.
• Live cmp: same for the zip, /press/ and itch-description. Status: all 29 clear. Smoke: 42/42 pages and 42/42 links.
• Finished 02:37

02:40: a boarded ship keeps at least three hazards

• Measured after the 02:28 deploy, hazards per boarding derelict over 60 seeds of each size: - new code: shuttle 3 to 3, corvette 2 to 3, freighter 3 to 4, station 3 to 5; - old code: shuttle 3 to 4, corvette 3 to 4, freighter 3 to 5, station 3 to 5.
• Added one untagged boarding hazard: "the boarders cut the door controls on their way through. Every door out of here opens by hand, slowly and loudly: roll for an encounter each time one is forced." Now: shuttle 3 to 4, corvette 3 to 4, freighter 3 to 5, station 3 to 5, the same spread as before 02:28.
• Corrected the 02:28 line above, which claimed this without measuring it.
• Earlier this phase, on a worktree: all four app/switch patches apply on HEAD and the switched tree passes tsc.
• Full suite 55 passed; tsc clean.
• Rebuilt the 1.18 zip ("the paid file is sound"), press ?v=1010, deployed.
• Live cmp: same for the main bundle, the zip, /press/ and itch-description. Status: all 29 clear. Smoke: 42/42 pages and 42/42 links.
• Finished 02:48

02:48: does every cause fill its hazards, logs and loot on every size

• Counted on 600 derelicts (150 seeds of each size). Storify asks for 3 to 5 hazards, 3 logs and 2 to 3 salvage. What came out: - 12 had no salvage at all, all corvettes; - 186 had one salvage; - 33 had two hazards; - 60 had two logs. - Every shortfall is the cause's pool running dry, because most notes are tagged to rooms a small ship lacks.
• The plan said "untagged notes that suit the cause". I did one shared spare list instead: 2 hazards, 1 log and 2 salvage, written to fit any cause, any room, and stations. They are drawn only after the pool is empty and only up to the floor (3, 3, 2).
• Old vs new hashes on all 600: the 388 ships that were never short are byte-identical, and only the 212 short ones changed.
• Test: 'every derelict gets at least three hazards, three log fragments and two salvage notes'. It fails on the old code (shuttle 1 salvage: 1) and passes on the new.
• The first full suite failed on the house test that every hazard says what it does: my grating hazard ended "a hard landing". I reworded it to "a fall into it: a hard hit". After that: 56 passed, tsc clean.
• Rebuilt the 1.18 zip ("the paid file is sound"), press ?v=1011, deployed.
• Live cmp: same for the main bundle, the zip, /press/ and itch-description. Status: all 29 clear. Smoke: 42/42 pages and 42/42 links.
• Finished 03:10

03:10: the three Eight Derelicts ships under the note floors get their missing notes, by hand

• Backed up the three folders and the zip first.
• Wrote four notes by hand, each into a room with no note of its kind: - Gossamer, a Dr. log in the Lab: the crew falling back ahead of the air loss, and Moreau, the trail's owner, promising the seals will hold. - Quillon, a Cook's log in the Galley, which ties to its "table set for five". - Quillon, salvage in Crew quarters: Petrov's locked locker with the crate's real manifest and a buyer's name. This ties to the brief (Petrov moved the crate) and the hook. - Lodestar Station, salvage at the Central hub, which has the customs desk: Lot 14's customs file with the shipper's address. This ties to the hook about the second consignment.
• Checks: - A python re-dump of the backup files is byte-identical, so nothing but the notes changed in the ship files. - Re-exported from the paid dev server; the temp script is deleted and the server stopped. - Old vs new: the keys and PDF text gain only the new lines (Gossamer's and Quillon's logs also print as player handouts). Page counts are the same (6, 6, 8). The PNG and .dd2vtt files are identical, so I kept the old ones.
• All 8 pack ships now meet the floors (hazards, logs, salvage): - Gossamer 4,3,2; Coldharbour 3,3,2; Willet 3,3,2; Sandpiper 3,3,2; - Quillon 3,3,2; Rowan 3,3,2; Lodestar 3,3,2; Fieldfare 5,3,2.
• Zip rebuilt with the same list; unzip -t found no errors.
• Press ?v=1012, deployed. Live cmp: same for the zip, /press/ and itch-description. Status: all 29 clear. Smoke: 42/42 pages and 42/42 links.
• Finished 03:14

03:16: a derelict with no airlock left is never the one taken at the airlock

• Measured over the whole one-shot and brief: 6 of 1200 derelicts (300 seeds of each size) end with no airlock. - Shuttle 139 was a boarding story: "taken at the airlock", "docks at the cut airlock", "cut the lock". - The other five only say "the lock was cut from the inside", which is the armoury's door lock.
• Change: when the ship has no airlock at the moment the cause is picked, any cause whose brief mentions an airlock is left out.
• Hash compare over the same 1200: 5 changed, the other 1195 are byte-same. That is more than the one boarding ship. Filtering the list moves where the same r() value lands, so every ship lacking a lock at pick time can draw a different cause. Some of those get their airlock back later, when the new cause mends its holes (shuttle 242 lost its airlock and 194 kept its, both with causes that don't mention one).
• Widened test: the airlock test now covers the whole PDF text and the brief, over 150 seeds. It fails on the old code at "shuttle 139 anywhere" and passes on the new.
• Full suite 56 passed; tsc clean.
• Rebuilt the 1.18 zip ("the paid file is sound"), press ?v=1013, deployed.
• Live cmp: same for the main bundle, the zip, /press/ and itch-description. Status: all 29 clear. Smoke: 42/42 pages and 42/42 links.
• Finished 03:28

03:30: read the next three daily derelicts' one-shots as a GM before they post

• Changed course: the daily draws a random seed in the browser, so the next ships can't be built ahead of time. Instead I read fresh one-shots in the order the daily will use the sizes (2 Oct corvette, 3 Oct freighter, 4 Oct station), at seeds 1001 to 1003.
• Corvette (ISV Cinder Reach, mutiny): way B was "the drive side, through the service lock". Measured: shuttles and corvettes draw exactly one airlock (297 of 300 each; the other 3 none). Checking every cause's two ways in turned up four lines that name a door the map may lack: the mutiny's service lock, the boarding story's "dead docking port on the other side", and the "cargo doors" of the Lot 14 and frozen stories on ships with no cargo hold. Together that was 235 of 1200 derelicts.
• Fix (adventure.ts): with fewer than two airlocks, way B cuts in through the hull. With no cargo hold, the Lot 14 way cuts in, and the frozen way goes through "a hull seam split by the cold". Old against new over 1200: 0 now name a missing door (235 before); the other 965 are byte-same; nothing outside "Getting aboard" changed. New test; it fails on the old code at shuttle 12.
• Eight Derelicts: a direct call reproduces all 8 frozen pack PDFs byte for byte. Only Quillon (one lock, the docking port) and Lodestar (no hold, the cargo doors) change. I swapped in their two new PDFs (4 and 2 lines of text differ). The zip has the same 57 entries and tests clean.
• Freighter (MSV Mistral, boarding): the crate, the survivor in the coolant trunk and Petrov's moved crate all agree. One fault: the Tech's log "Vented deck 2... my people were on deck 2" can land on one-deck ships. It now says "the aft section". Words only; it's in no posted daily and not in the pack.
• Station (Fieldfare Station, cold): two faults in the cold story. - The medbay said "The patient is not in it." beside a salvage note about the patient in the autodoc, a d6 line about the patient's vitals and an ending that wakes them. - The blankets hazard was in the crew quarters, while the brief and the captain's log put the crew in the galley. - Fixes: the cold story drops that one sentence (words only, no r()). A new "first" flag places the blankets hazard in the first room of its list that the ship has. - Over 1200: both faults went from 37 to 0. 65 ships changed, all of them the cold story; 1135 are byte-same. New test; it fails on the old code at shuttle 28. - Coldharbour (the pack's cold ship) has no medbay and no blankets hazard, so it's unaffected.
• Full suite 58 passed, tsc clean. Rebuilt the 1.18 zip ("the paid file is sound"), press ?v=1014, deployed. Live cmp: same for the main bundle, both zips, /press/ and itch-description. Status: all 29 clear. Smoke: 42/42 and 42/42.
• Finished 03:55

03:55: read one one-shot for each of the five causes not yet read today

• I read one fresh one-shot for each of the five causes not yet read today (swarm, reactor, plague, misjump, specimen), as a GM would. Three causes contradicted themselves: - Reactor: 95 of 1200 ships had a brief saying the ship is "still warm aft" while engineering read "Reactor cold." or the drive section read "Cold. Frost on every surface." A new per-cause unsay list removes those words in this story only. The drive now reads "The torch has not fired in weeks, and the deck is still warm underfoot." - Plague: 99 briefs say someone "welded the medbay (or crew quarters) shut", and the key never mentioned it. A new kept note adds a welded-door hazard to the room the brief names. 99 of 99 land there. - Misjump: 53 drive sections said "The log says they were not" about the fuel, beside a core with one more jump in it. The line now reads "Fuel gauges at zero. The charge gauge is not." The PDF threat line said "the drive is live"; it now says "cold but still charged".
• The swarm and specimen one-shots read clean.
• All three fixes change words only, with no r() draws. Against the pre-phase generator, 938 of 1200 ships are byte-identical. The rest changed: 110 reactor, 99 plague, 53 misjump, and nothing else.
• New test: "a dead room says what its story says". It failed on the committed source ("shuttle 2: expected undefined to be 'crew quarters'"), and the backups were restored after md5 checks.
• Full suite: 59 passed. tsc is clean.
• Eight Derelicts: Willet (misjump) had the fuel line in its JSON and key. I fixed both by hand and re-made its PDF with the direct call. The PDF text diff is exactly those two lines. - Sandpiper (reactor) opens engineering with "Panels off" and has no cold or frost, so no change. - Lodestar's plague brief has no weld, so no change. - The zip was rebuilt with the same entry list and passes unzip -t.
• 1.18 was rebuilt, and release.mjs ended "the paid file is sound". First it had to re-download Playwright's Chromium, because ~/.cache had been emptied across the restart.
• Press links are now ?v=1015. Deployed. Live cmp is the same for both zips, /press/, the itch description and the main bundle. Status 29/29, smoke 42/42.
• Mid-phase, the boss gave me Search Console and Bing access (.search/). I read it in place of a screenshot. - 6 impressions and 0 clicks in a month. - 15 of 40 sitemap pages are indexed. 18 are "Discovered", 1 is "Crawled - not indexed" and 6 are unknown. - Not one keyword landing page is indexed, though the home page links to them. - The full table is in FACTS. My reading of it is in LEARNED.
• Finished 04:25

04:26: read today's and tomorrow's daily one-shots before they post

• The plan's premise was wrong. The daily isn't seeded from the date. daily-derelict.mjs clicks Generate in the rebuilt paid file with a random seed, until the cause and the name are both new. So today's ship can't be read in advance. What I can know is the set of causes it may pick. - The last five days used causes 7, 0, 6, 2 and 3. - Today's corvette will be reactor, boarding or misjump (1, 4 or 5). - Tomorrow's freighter will be from 1, 4, 5 or 7. - I read a fresh one-shot of each from current src: corvettes for 1, 4 and 5, and a freighter for 7. - The script rebuilds store/bulkhead.html before every run (daily-derelict.sh, line 10), so today's fixes do reach the 11:07 ship.
• Boarding (RSV Harrow) and specimen (ISV Cassandra) read clean. Today's reactor and misjump fixes read right in context: the aft deck is "still warm underfoot", and the charge gauge agrees with the threat.
• Found and fixed: - Reactor: both briefs seal a room: "{Engineering?engineering|the drive section}", or the alt's drive section with the engineer inside. The key never said so. A kept note now adds "the door is sealed, and the seal is still good…" to that room. On stations, "the reactor ring" falls back to Engineering. Against the pre-change generator: 1053 of 1200 ships are identical, and only reactor ships changed. On the first run, 147 of 164 reactor ships got the note in the right room; the 17 misses were all stations, fixed by the fallback. - Misjump tally hazard: "lose your own count: anyone who reads it through loses the time: an hour is gone" became "lose your own count. Anyone who reads it through loses an hour." - Every one-shot's twist: it said "Keep it from the players until they find it", but the key places the twist only sometimes; Cassandra's was in a doctor's file no room held. It now reads "Hold it back until late in the session, then let it surface in a log, a body or a survivor's word, wherever it fits this ship best." It goes through say(), so a station says "this station".
• Tests: the "dead room says" test now covers the seal, the tally sentence and the twist, including the station wording. It failed on the committed generate.ts ("shuttle 3 … an hour"). It failed on the committed adventure.ts too, once it joined the PDF's wrapped lines; the first version passed on the old code because the phrase wraps. Sources were restored from md5-checked backups. Full suite: 59 passed, twice. tsc is clean.
• Eight Derelicts: - Sandpiper's drive section (the alt brief: "sealed the drive section with herself inside it") got the seal note by hand, in its JSON and key. - Willet got the tally fix by hand. - All 8 PDFs were re-made with the direct call. The text diffs are only the twist line, those two notes and page reflow. Lodestar reads "this station". - The zip has the same entries and passes unzip -t.
• 1.18 was rebuilt ("the paid file is sound"). Press links are now ?v=1016. Deployed. Live cmp is the same for both zips, /press/, the itch description and the bundle. Status 29/29, smoke 42/42.
• Finished 04:51

04:51: read an indexed daily page as a visitor from search, and see where it leads

• I read /daily/2026-09-20/, one of the 7 indexed daily pages. The page order is: 1. The nav, with "Full version $12" last. 2. The date, the title and the AI line. 3. The map. 4. The brief. 5. "Open it in the free editor". 6. The downloads. 7. The CC0 line. 8. The GM key, room by room. 9. "The full version" with a buy button.
• The $12 link is one tap from the top (the nav) and one at the bottom. The pitch lists editor features. It doesn't mention the one-shot adventure PDF. It can't yet: the itch store still serves 1.17 (FACTS), and 1.17 has no Export adventure (counted 0 in the 1.17.1 zip's html). Pitching the one-shot waits for task 1.
• The numbers decide this one. events.sh since 25 Sep: the daily day pages had 1 view in total (/daily/2026-09-30/), and /daily/ had 8. Over the same span, / had 84 views and the editor had 116 Generate presses (103 intact, 13 derelict). Search sent 1 editor visit (duckduckgo) and Reddit sent 2.
• Being indexed hasn't brought anyone to the day pages, so a template change there would reach nobody. No change. The place a visitor turns into a buyer is the editor, and its next reading is the phone-sittings count already planned for 4 Oct.
• Finished 04:52

04:54: per sitting, do web visitors who press Generate ever see a derelict?

• The web Generate presses from 28 Sep to 1 Oct, grouped into sittings (the same visitor, with presses under 30 min apart; my runs and bots dropped). The request log reached back only to 28 Sep at this grain: 22 sittings. - 17 pressed intact only. 16 of those pressed once and left; one NL phone pressed 53 times. One ES desktop pressed 3 and clicked the locked fleet. - 3 pressed derelict only: CA 1, BE 7, CZ 1. - 2 opened the intro picture only. - None switched from intact to derelict, and none saved anything.
• Why: the demo intro had one visible button, "Generate a ship" (intact). "Generate a derelict" was folded under More. The story, the room key and the one-shot only come with a derelict, so most first-time visitors never saw them.
• Changed (index.html, main.ts): the intro's visible button is now "Generate a derelict"; "Generate an intact ship" moves under More and sets the mood to intact itself. The full version's first-open intro hides the intact button, as before it hid the derelict one. obr.html keeps both side by side. The toolbar select still defaults to Intact, and the daily sets its own mood.
• Test: entry-pages checks that the only primary button before More is introDerelict, and that its handler sets derelict. It failed on the old index.html. Suite 60/60, tsc clean. Deployed. Live check (fresh browser, phone 390 and desktop 1280, /e/ fulfilled): visible buttons "×" and "Generate a derelict", pressing it sent /e/generate-derelict, and the card showed a story.
• Measure from 4 Oct: sittings that see a derelict, and saves per sitting, against 3 of 22 before.
• Finished 05:02

05:02: rebuild the 1.18 zip with the new intro, so task 1 uploads what the demo runs

• release.mjs 1.18 ended "the paid file is sound". The paid file's first open (a fresh browser, network blocked): the visible buttons are "×" and "Generate a derelict", and the lead is the 1.18 one-shot line. Pressing the button set the mood to derelict, made RSV Pelican, and showed the One-shot button on the card.
• ?v=1016 → 1017 on /press/ and itch-description.html. Deployed. Live cmp shows these identical to the local files: bulkhead-1.18.zip, bulkhead-eight-derelicts.zip (not rebuilt), itch-description.html and /press/.
• Finished 05:03
• Correction (after the above, finished 05:04): I wrote that intact ships have "no story". That's wrong. An intact ship has a situation, a hook and room notes. What it lacks is hazards, the trail, logs and salvage, and so the one-shot. The intact button's title said "no story: just the rooms"; it now says "with a situation and a hook: no hazards, trail or one-shot". The code comment is fixed the same way. The count above (16 of 22 sittings were one intact press) stands. The 1.18 zip was rebuilt again ("the paid file is sound") and ?v= went to 1018. Live cmp shows the zip, itch-description.html and /press/ identical to local, and the live / carries the new title.

05:04: count which button a sitting starts from, intro or toolbar

• main.ts: introDerelict sends /e/intro-derelict and introGenerate sends /e/intro-intact, each just before its generate count. count() returns early outside the demo host, so the paid file sends nothing. I left the 1.18 zip alone (no change a buyer sees); the daily's store/ rebuild picks up the source anyway.
• The entry-pages test checks both handlers, and it failed on the old main.ts. Suite 60/60, tsc clean. Deployed. Live (phone 390, /e/ fulfilled): the derelict button sent intro-derelict then generate-derelict, and the intact one, under More, sent intro-intact then generate-intact.
• Side read, Bluesky logged out: 4 followers. The 1 Oct daily has 0 likes after 18 h, and every daily since 21 Sep has had 0 to 2. That matches LEARNED (29 Sep): the daily is not a channel. Nothing new to do.
• Also read: the site's links into the editor. 38 go to ?gen=derelict and 15 to ?gen=ship. The ?gen=ship links sit where a working ship is what the page promises: /deck-plan-generator/, /space-station-map-maker/ (station), /starfinder-deck-plans/, /traveller-deck-plans/, and every /maps/ page as the second choice after "generate a derelict". Left as they are.
• Finished 05:12

05:12: read Search Console with --fresh: any query or page since the 2 Oct baseline?

• Search Console, 1 Sep to 2 Oct, read with --fresh: by date, 24 Sep 1, 29 Sep 1, 30 Sep 4, 1 Oct 0, and no rows for 2 Oct yet. By page, the same four as the baseline: /guide/ 3, /daily/2026-09-20/ 1, /maps/derelict-msv-cassandra/ 1, /space-station-map-maker/ 1. No clicks. No query rows (rare queries are hidden). Nothing has moved since the baseline, and FACTS needs nothing new. The 9 Oct re-inspect stands.
• After the intro edits to index.html and main.ts: the four app/switch patches still apply in order on a fresh worktree at HEAD (15 files, through obr.ts in patch 4). Checked singly with --check against the base, 2 and 3 fail, because they build on 1. That's expected, not drift. The worktree was removed.
• Finished 05:13

06:07: look at what a first-time phone visitor sees after pressing the new intro button

• Live, in a fresh browser, 3 presses each at phone (390x844) and desktop (1280x800): - Phone, good: the ship above the card, its story and hook in full in the Room key under it, the card's Save, Link, Another one and the $12 line in view. - Two faults. Each room's note box showed two lines, so the hazard (always the note's last part) was cut off. On a phone that list is the only room key, because the card hides the Room key button there. And on desktop the story card sat over the ship's far end (rooms 6 and 7 of a corvette).
• Fixed: - renderKey grows each note box to its text, and keeps growing it on input. A hidden panel measures 0 and is skipped. - On a wide screen showBrief fits the ship into the strip left of the card or the one below it, whichever draws it bigger: fitBesideCard in the new src/fit.ts. Closing the card refits to the whole stage at every size.
• Tests: - test/fit.test.ts: a long, a tall and a square ship each fit clear of a 1280x800 card, where the whole-stage fit would overlap it; and the bigger strip wins. All 4 failed with the fit made whole-stage again. - smoke.mjs has a new "first press" check at phone and desktop: the intro button makes a derelict, and no room note is cut. Run against the old live site it failed on both (7 room notes cut off each); after the deploy both pass. 42/42 pages, 42/42 outbound links.
• Suite 64/64, tsc clean. Deployed. Live desktop: the ship sits whole below the card, at 57% against about 105% before. It's smaller, but all of it shows. Room notes are whole in the sidebar.
• Buyers get this too, so release.mjs 1.18 was re-run ("the paid file is sound") and ?v= went 1018 → 1019. The first live cmp of the zip differed; a minute later three fetches were byte-same (an edge cache HIT at first). itch-description.html, the Eight Derelicts zip and /press/ are also the same.
• Finished 06:19

07:08: before 11:07, run today's code through the daily's own path and the Owlbear harness

• Order: I ran the Owlbear harness before writing this entry; the plan was written straight after it.
• Owlbear harness against the live site: - ok: a scene sent, with 35 walls, 6 doors and windows and 2 lights, and the send button came back. - exports: the .dd2vtt and PDF are free and marked, with no upsell and nothing paid-only shown. - player: send is disabled ("Only the GM can add scenes").
• Daily dry run: build:paid, copied to store/, then daily-derelict.mjs 2099-01-07. Exit 0. It made a whole day: a shuttle, ISV Dunmore Verge (boarding), with the PNG, .dd2vtt, key, story PNG, card, pin and day page. - Read as a GM: the trail runs Drive section (4) → Crew quarters (2) → Cargo hold (3). Every hazard is whole. Nothing to fix. - The 2099 folder was deleted, and the files it touched (/daily/ pages, feed, latest.png, _redirects, press/daily.html, sitemap) were restored with git checkout. grep finds no 2099 anywhere. - store/bulkhead.html stays rebuilt from this tree, as the 11:07 run would do, and is committed here.
• Also seen: the daily's editor.png isn't linked from any page (the site uses /img/editor.png), so its card covering the ship doesn't matter.
• Finished 07:08

07:10: check the intro-derelict and intro-intact counts reach the event log

• The plan's "How" line came out garbled. What I actually did: check the live bundle, press the live intro once headless with /e/ let through, then read Cloudflare's log with my headless filter off.
• The live bundle (main-*.js) has the introDerelict handler sending count('intro-derelict'), and the live page leads with "Generate a derelict".
• The headless press sent /e/from/none, /e/view/, /e/intro-derelict and /e/generate-derelict, all 200. It made "Derelict — ICV Vantage".
• In Cloudflare's log: nothing straight away. About 2.5 min later, a copy of events.sh with the Headless filter off (a temp file in app/scripts, removed) showed intro-derelict 1 and generate-derelict 1. So the counts the 4 Oct read needs do arrive. The normal events.sh still drops my run.
• Real traffic since 04:00: one view of / with intro-pic, one view of /owlbear-rodeo-dd2vtt/, and nobody pressed Generate yet. Too few to read anything.
• Lesson already in LEARNED (measure before stating). Nothing new to add.
• Finished 07:13

07:13: what a visitor to /owlbear-rodeo-dd2vtt/ sees first

• Desktop 1280x800: the manifest URL and Copy sit at about 440 px and the Rogue Store link at 546, all above the fold. The Owlbear screenshot pair starts just below.
• Phone 390x844: the manifest URL at 701 and Copy at 750, both above the fold. The Rogue link is at 931, just below. The URL wraps at "bananafest-" on a phone, but Copy sits right under it, so nobody has to select it by hand.
• Copy on both: the clipboard holds exactly https://bulkhead.bananafest-destiny.com/obr/manifest.json, the button says "Copied", and /e/obr-copy is sent (stubbed here, so not counted).
• The manifest answers 200 with version 1.17.2.
• Nothing to fix. If the 4 Oct read shows views and no copies, the page's first screen isn't why: the install step is visible and works. The words, or who lands there, would be next.
• Finished 07:14

07:14: what /maps/ visitors see, and why so few go on

• First screen: on desktop (1280x800), the first six maps show as clickable cards above the fold, under a short CC0 line and links to the zips, the Foundry module and the daily. On a phone (390x844), the first card (Anvil) starts at 506 px. Nothing broken or hidden.
• Where the 22 views came from (view pings grouped by hour, country and a UA hash; Cloudflare doesn't give this plan the referrer field): 9 sittings. - 8 of 9 also viewed / in the same hour, so /maps/ is mostly a click from the editor's nav or intro, not a landing page. - One DE desktop on 1 Oct made 10 of the 22. IT made 4. - None of the 9 sittings sent a map-page view afterwards. They looked at the grid and left, or went back to the editor (NZ, BR and DE pressed Generate).
• File requests since 28 Sep (.dd2vtt, .pdf, .zip, with obvious bot UAs dropped): SG fetched nearly every file every day with a browser UA and no view pings. That's a crawler, not a GM. Most of the scattered single .dd2vtt fetches from other countries also come without a view ping, so this log can't count real map downloads. I'm not drawing anything from it.
• No change. Nine sittings are too few, and the cards work. In the 4 Oct read, now that the intro's second visible button is "Free maps": count sittings that go / → /maps/ and whether any open a map page or come back and press Generate. If /maps/ only pulls people away from the derelict, move Free maps back under More.
• Finished 07:15

07:16: send the pages Bing hasn't read through the broker's bing-submit

• Sent 20 URLs with bing-submit: /, every keyword landing page (deck-plan-generator, space-station-map-maker, derelict-ship-map-generator, free-sci-fi-battlemaps, owlbear-rodeo-dd2vtt, starfinder-deck-plans, traveller-deck-plans), /maps/ and all 11 map pages. Left out: /about/, /guide/, /foundry/, /daily/ and the day pages (20 a day).
• The answer was JSON with a "submitted" list matching what I sent, as far as I saw it. My mistake: I piped it through head -20, so I didn't see the end (an error or quota field, if there was one). I'm not resending, since that would spend the day's cap again. Next time, read the whole answer.
• Whether Bing reads them is the real question. On 9 Oct, count bingbot hits on these 20 paths in the request log, next to the Google re-inspect.
• Finished 07:16

08:08: a kept sittings script for the 4 Oct read

• Before the plan (08:07): PR #174 has one review (24 Sep). Its two points, a description under 128 characters and a transparent icon, were fixed that day. It still waits on task 2. /go/ buy requests since 15 Sep: brief 30, map 18, daily 17. Not a signal, since itch views don't back them.
• New: app/scripts/sittings.sh [since] [until]. It reads /e/ events at minute grain. A sitting is one IP + user agent with events under 30 min apart (the IP is only a key; it's never printed). It drops what events.sh drops, lists each sitting that did something in the editor, then prints totals.
• Over 28 Sep to 2 Oct 00:00: 78 sittings, 48 of them page views only. 29 web sittings did something in the editor, plus 1 in Owlbear (BR phone: send, export x3). - 26 pressed Generate, 5 saw a derelict, 1 saved or linked, 9 pressed more than once. - Keying on UA + country instead of IP gives the same 29 and 5.
• Correction to the 04:54 baseline ("22 sittings, 3 saw a derelict, none switched, none saved"). Over the same window, the kept script finds: - 5 that saw a derelict: the same CA, BE and CZ, plus a US phone on 29 Sep 08:04 (derelict only) and a US desktop on 1 Oct 03:33 (5 intact, then 2 derelict, so one did switch). - 1 that saved: a BR desktop on 30 Sep 23:31 pressed intact, then took the PNG with story (brief-png) and copied the link (brief-link). events.sh had shown brief-png 1 and brief-link 1 all along. - The 04:54 script was deleted, so I can't say exactly where it went wrong. It counted generate presses only, and it missed the saves. The change it led to still stands: 21 of 26 Generate sittings saw only intact.
• The 4 Oct comparison now uses this script on both sides: before = 5 of 29 web sittings saw a derelict, 1 saved.
• Finished 08:09

09:07: is /press/ task 4 (Bing import) still needed, and is task 9 stale?

• Bing: - .search/search.mjs exits with "search: <status> <error>" on any non-OK broker answer. At 07:16 it printed the JSON "submitted" list, so the broker reported success. - Bing's URL Submission API only takes URLs for a site verified in the submitting account. So the import task 4 asked for is done in effect, through the boss's search setup of 1 Oct. That's an inference from how the API works, not something I saw in Bing's dashboard. - Bingbot in the request log since 25 Sep: hits in about 40 hours, on /, the sitemap, robots, /owlbear-rodeo-dd2vtt/ (6 times), /derelict-ship-map-generator/, /free-sci-fi-battlemaps/, /foundry/, a day page, and the Owlbear manifest. After the 07:16 submit: /daily/ and /free-sci-fi-battlemaps/ at 07, and / with its assets at 08. - WebSearch for site:bulkhead.bananafest-destiny.com lists our homepage. I can't tell which index that tool draws on, so it doesn't prove Bing has us.
• Task 9 was posted on 30 Sep, and it was the #1 post on r/OwlbearRodeo that day (FACTS, 30 Sep). /press/ still showed it as open, with its copy-paste replies.
• /press/ changes: - Task 4: marked done ("not needed any more: skip it"), with one line on why, and the import steps removed. - Task 9: marked done ("done on the 30th"), with its post and reply drafts removed. That fits "no more replies in that thread". - Still 20 task blocks, and the other tasks are unchanged. Deployed. The live /press/ is byte-identical to the file, after the edge cache cleared on the fourth fetch.
• LEARNED (26 Sep, "bingbot had read one page") is out of date: bingbot now reads the site most days. Added a line.
• Finished 09:09
• Also, after this phase (09:09): - sittings.sh since 05:12 found the first real start from the new intro: a GB desktop at 08:08 pressed "Generate a derelict" once and left. One sitting, so nothing to read from it. - Fixed the "16 of 22" in main.ts's intro comment to the kept script's count. tsc is clean, and the paid build is byte-identical to store/bulkhead.html (comments are stripped), so no zip rebuild is needed.

09:09: the desktop first press at 1366x768 and 1920x1080

• Live site, two presses at each size (/e/, /go/ and the beacon blocked). I ran 2 seeds per size, not the 5 the plan said: all four were 1-deck derelicts, and the fit didn't differ between them.
• 1366x768 (MSV Osprey, MSV Whimbrel Drift): the stage is 1030x700 and the card sits at x 706, 380x377. The ship draws at 65%, about 550 px across, left of the card, with no overlap. Room numbers and labels are readable.
• 1920x1080 (FTV Palisade, MSV Palisade Drift): the stage is 1584x1012 and the card is at x 1260. The ship draws at 129%, about 980 px across, clear of the card.
• No fault, so nothing to change. A cosmetic blemish at 129%: the ENGINEERING label runs over a console stamp, and the CREW label touches its room marker. Not first-press specific, so not worth a generator change today.
• The GB sitting at 08:08 that left after one press wasn't caused by a small or covered ship at common desktop sizes. One sitting can't say what was.
• Finished 09:10

10:07: how often a room's name is drawn over a stamp

• Measured with a temp test (200 generated ships: 4 sizes, intact and derelict, 25 seeds each): 53 of 1918 room names cross a stamp's footprint. ARMOURY 23, GALLEY 7, LIFE SUPPORT 6, ENGINEERING 5, CREW QUARTERS 5, the rest 1 or 2. About 1 ship in 4 has one.
• First fix: choose the label row at push time. No change (53 → 52, then 53 with a bottom-up row scan). clearLabels (commit 7fa34ac) already walks rows and nudges sideways after every stamp is placed. What is left are rooms with no bare spot, e.g. an armoury with lockers in three corners and a table in the middle. generate.ts restored from the backup copy; md5 matches HEAD.
• Real fix, render only: every room name gets a floor-coloured stroke under its fill (src/render.ts). No ship changes, the RNG is untouched, and the Eight Derelicts pack and switch patches are unaffected. Rendered the shuttle intact 15838 armoury in print and blueprint: ARMOURY reads cleanly beside its locker, other names look the same apart from a faint edge.
• tsc clean, full suite 64 passed (pipefail). Deployed; the live main bundle has strokeText. release.mjs 1.18: "the paid file is sound"; the live 1.18 zip is byte-identical. /press/ and itch-description ?v= 1019 → 1020, live byte-identical at /press/ and /press/itch-description (the .html URLs 307).
• Temp test removed.
• Finished 10:18

11:07: daily check, and the store copy after the halo

• 11:07 npm run status: 5 of 26 failing, all today's daily (no page, feed on 1 Oct, no Bluesky URL, no preview). No daily process was running, so I ran scripts/daily-derelict.sh by hand at 11:07. It finished 11:11, exit 0: Derelict — RSV Kestrel (a corvette, misjump story; two names were regenerated as used lately), posted to Bluesky, mastodon skipped (no credentials), committed as "Daily derelict 2026-10-02".
• Re-ran status: all 29 clear.
• Store copy: store/bulkhead.html went from 203266 to 203380 bytes (+114). strokeText appears once in the new copy and never in the old: the label halo and nothing else of size.
• itch: bulkhead views 26 (same as 1 Oct), 1 download, 0 purchases; deck-plan-pack-free 6 views, pack-2 2. Bluesky: 5 followers; today's and yesterday's posts 0 likes, 30 Sep 1.
• Finished 11:11

11:12: today's daily image with the label halo

• Opened daily/2026-10-02 derelict-rsv-kestrel-main-deck-38x17.png (blueprint). All nine names read: BRIDGE, HANGAR, GALLEY, CREW, CARGO HOLD, ARMOURY, MEDBAY, ENGINEERING, DRIVE. ARMOURY sits right against its bottom-left locker and stays legible; the edge is a thin dark rim, not a ring. No change needed.
• ARMOURY's last letter runs up to the wall it shares with MEDBAY. Readable, and there's nothing to fix without changing the room.
• Finished 11:12

12:07: why the 2 Oct daily didn't start on its own

• Cause: CronList showed no jobs at all. The session cron a41fca10 that ran the daily check is gone; session crons die on a restart and expire after 7 days. Nothing else starts the daily on this machine (no cron daemon, no user systemd: LEARNED, 21 Sep).
• Fix for now: re-created it as 7aa3f2d0, "12 6 *" local. The machine is on CDT, so that's 11:12Z, just after the daily is due. The prompt is the boss's daily instructions word for word, with the credential load in the subshell form. It's session-only and expires after 7 days (around 9 Oct). It only fires while the session is idle.
• The real fix is still the 21 Sep question (is there a machine that stays on?). It was folded into "Old asks" on /press/ on 25 Sep and never answered; FACTS has no answer. Since then the boss's .search/README says the search broker runs as search-broker.service on OptiServer, so such a machine exists. Added to the after-task-1 question batch instead of asking now.
• Finished 12:08

12:32: a real daily timer on OptiServer

• Wrote app/scripts/host/: daily-host.sh, bulkhead-daily.service (oneshot, 40 min limit, after network-online) and bulkhead-daily.timer (11:07 UTC daily, Persistent=true). The wrapper puts nvm's newest node on PATH, takes a flock on app/.daily-log/lock, runs daily-derelict.sh then npm run status, and logs to app/.daily-log/DATE.log (git-ignored). It loads no credentials itself.
• Test, env -i with only HOME, from /: node v22.23.1 found, "already generated 2026-10-02", "bluesky: already posted", status all 29 clear, exit 0. Nothing new to commit. Lock test: with the lock held, a second run printed "another run holds the lock" and exited 0.
• systemd-analyze calendar: next elapse Sat 3 Oct 11:07 UTC (06:07 CDT). verify needs the host's bus, which the sandbox can't reach.
• Session cron 7aa3f2d0 deleted; watcher 406fff8d at 06:37 CDT (11:37Z). It reads the log first and runs daily-host.sh (lock-safe) only if the day is missing.
• Install needs the host (outside my sandbox, and ~/.config is outside where I may write), so it goes to the boss as one paste.
• Finished 12:36

13:07: the pages Google already shows, and what they show

• Broker query, 4 Sep to 2 Oct, --fresh, by page: /guide/ 3 impressions (position 7.3), /daily/2026-09-20/ 1 (1.0), /maps/derelict-msv-cassandra/ 1 (4.0), /space-station-map-maker/ 1 (2.0). 0 clicks. By query: no rows (all hidden as rare).
• The same four pages and counts as the 1 Oct read (FACTS). Nothing new has shown in Google since.
• Nothing to act on: with 6 impressions in 28 days, a rewritten title or description would have no measurable effect. The gap is pages being indexed and shown at all, which the 9 Oct re-inspect measures. No snippet changed.
• Finished 13:07

13:08: Owlbear store PR #174, anything new

• Open, not merged, last updated 24 Sep 13:36Z. One comment (24 Sep: description over 128 characters, icon transparency), no reviews. Both were fixed on 24 Sep; status shows the description at 126 characters and the action icon with no background fill. The reply on the PR is task 2 on /press/, still with the boss.
• Nothing new to act on. LEARNED (merges come in batches) puts a merge around February.
• Finished 13:08

14:07: does Google have our current sitemap

• Broker sitemaps: last submitted 15 Sep, last downloaded 2 Oct 08:39Z (the 1 Oct read was 1 Oct 09:31Z, so Google reads it daily). 40 web URLs and 43 images, 0 warnings, 0 errors. The live sitemap has 41, the extra one being today's daily, added after 08:39. Google's copy is current, so no resubmit.
• Inspected two of the six pages that were "URL is unknown to Google" on 1 Oct: /traveller-deck-plans/ is now "Discovered - currently not indexed" (it moved in a day). /maps/orbital-station-vesper/ is still unknown, though it's in the sitemap (lastmod 29 Sep), answers 200, and 8 pages link to it, /maps/ among them. Nothing to fix; it waits for the 9 Oct re-inspect with the rest.
• Finished 14:07

14:08: is the daily Bluesky post itself the problem

• Last six posts (27 Sep to 2 Oct), likes/reposts: 2/1, 1/0, 1/0, 1/0, 0/0 (1 Oct), and today 2/1 by 14:09 (it was 0 at 11:12). Every post is the same shape: a one-line story hook, "Free map, CC0: PNG, .dd2vtt with walls, GM key.", the day link, five tags, the map image.
• Not the post: about one like a day is the steady level for a 5-follower account, and today's is one of the better two. Nothing changed. Read likes the next day, not at the daily check.
• Finished 14:08

15:07: where today's visitors came from and went

• events.sh since 2 Oct 00:00: 8 page views (5 /, 2 /owlbear-rodeo-dd2vtt/, 1 /daily/2026-09-25/). Editor visits came from /owlbear-rodeo-dd2vtt/ (3), bananafest-destiny.com (2) and none (2). One sitting started from intro-derelict, generated a derelict and saved a PNG (export-png): the first save since the derelict became the intro's button.
• visits.sh since 25 Sep: 67 page loads; / 36, /owlbear-rodeo-dd2vtt/ 12, /obr 6, /maps/ 4. Referers: direct 31, bananafest-destiny.com 13, our own host 13, www.owlbear.rodeo 6, the Reddit app 4.
• visits.sh since 15 Sep: 210 loads, none with a Bluesky referer, and today's day page not loaded once despite its repost. The Bluesky app may send no referer, so some could sit under direct, but the day pages the posts link to almost never load either way.
• No fix to make today. The leak, named: the daily post costs nothing to run but brings no visits I can see. It isn't a channel; the Owlbear landing page and the boss's own site are.
• Finished 15:08

16:07: the after-export dialog offers the save it asks for

• afterExport now calls showUpsell with the watermark title and lede and keep=true, so "Save this ship first" shows under the hint that asks for it. New test in entry-pages.test.ts; it fails on the old main.ts (1 failed | 5 passed) and passes on the new.
• Browser check, local dev, 1280x800: intro-derelict, locked .dd2vtt click (title "Walls, doors and lights are in the full version"), closed, then the first PNG export: the dialog opens titled "That's the demo watermark" with the save button showing. Before the fix it would have kept the .dd2vtt title and hidden the button. Pressing save opened Chrome's file picker path (no download in headless), the same code the .dd2vtt and PDF dialogs already use.
• tsc clean, full suite 65 passed (pipefail). The paid build is byte-identical to store/bulkhead.html (the upsell is demo-only), so the 1.18 zip and ?v= stay as they are. Deployed; the live main bundle has the new call.
• Finished 16:15

17:07: the upsell dialog on a phone

• Live site, Playwright as a phone (isMobile, touch), after intro-derelict. Dialog top/bottom and the bottom of its last button, in px: - 390x844: locked .dd2vtt 210-634, last button 615; first PNG export 228-616, last button 597. - 360x640: locked .dd2vtt 89-551, last button 532; first PNG export 117-523, last button 504. - No scrolling inside the dialog in any case, full width.
• Screenshot at 360x640, after export: the title "That's the demo watermark", the lede, the 2 paragraph, the save hint, then Get the full version and Save this ship first side by side, with Keep using the demo below. Nothing cut off. No change.
• Open question, not for today: on a phone, "save, then open the file in the full version" means opening a downloaded HTML file on the phone. Whether that works on Android and iOS is unchecked.
• Finished 17:07

17:08: does the $12 file work on a phone

• No record anywhere: nothing in LEARNED or FACTS on opening the paid HTML file on Android or iOS. The live itch page names no platform and doesn't mention phones. It only says the demo runs "in your browser".
• Why it matters: most visitors are phones (visits.sh since 25 Sep: BR mobile 6, US mobile 5, and so on). A phone buyer gets a zip holding an HTML file. iOS's Files preview may not run scripts; on Android it depends on the file manager. I can't test a real phone from here, and a desktop emulation wouldn't answer it.
• Added to the after-task-1 batch, next to the Android .dd2vtt question already there: open the 1.18 zip's bulkhead.html on the phone and press Generate. If it fails, the itch page and the upsell say "for a computer" before anyone pays.
• Finished 17:08

18:07: the paid file from disk in WebKit and with storage blocked

• Installed Playwright WebKit 26.6 into its cache (it wasn't there). Copied store/bulkhead.html (the paid 1.18 build) to scratch and opened it as file://. Every http(s) request was aborted and counted; none were made.
• At 390x844, touch: tapped "Generate a derelict" on the 1.18 intro, read the ship name, then pressed the .dd2vtt export. - WebKit (Safari's engine): ISV Example became Derelict — FTV Sextant, and derelict-ftv-sextant-main-deck.dd2vtt downloaded. No errors. - WebKit with localStorage throwing: Derelict — FTV Candlemas, .dd2vtt downloaded, no errors. - Chromium as a phone with localStorage throwing: Derelict — FTV Petrel, .dd2vtt downloaded, no errors.
• So the file itself runs in Safari's engine and survives a context with no storage. The first try read #briefName, which stays empty, and pressed btnGenerate, which opens the options; it showed nothing either way, so I re-ran with the intro button and #shipName.
• What remains is the phone's own step: whether iOS Files or an Android file manager opens bulkhead.html in a real browser rather than a preview. That's the batch question as written, now narrowed to that step.
• Finished 18:08

22:07: the live demo in Safari's engine

• Ran the live site in Playwright WebKit as an iPhone 13. All 41 sitemap pages were clean. The first press made "Derelict — MSV Wren Verge" with no room notes cut off. The PNG export downloaded, and the after-export dialog opened with "That's the demo watermark" and the save button. Screenshots show the same layout as in Chromium. There was no site fault to fix.
• The first run failed every page, but my own stub caused it. WebKit rejects the beacon stand-in: a 204 with no type isn't a valid module, and an empty script fails the beacon's integrity hash. Fixed by aborting the beacon request and ignoring its load errors.
• smoke.mjs now runs a third first press, iPhone in WebKit, inside the daily check. If WebKit won't start on the machine, it prints a skip line instead of failing the day. Smoke run twice: 43/43 pages, 3 first presses ok, 40/40 links, exit 0.
• Finished 22:17

23:07: read four more one-shots as a GM, multi-deck first

• Read fresh one-shots end to end as a GM: freighter 2201 (ISV Greyling, two decks), station 2202 (Willet Station, boarded), corvettes 2203 (FTV Corvid, plague) and 2204 (MSV Calloway, mutiny). Five faults, all fixed in src: - Willet's last recording said the crate "had been moved before we left port". A station never left port. It now reads "the day it came aboard" (a STATION_WORDS swap). - Willet's tech "vented the aft section". A station has no aft. It now reads "the outer ring". - Willet's medbay note said "The patient is not in it." Beside it were the salvage and the twist, where the autodoc's patient is a boarder, alive and willing to talk. Only the cold story removed that line; the boarding story now removes it too. - Calloway's recorder salvage said "It settles the argument. Nobody left to hear it." The same one-shot has a survivor from each side, and Haddad's recording says it "will not tell you who was right". It now reads "It shows who fired first, and whoever is left on either side will want it." - The summary said "Their trail runs through three rooms, below". On a two-deck ship whose trail starts on the lower deck, that reads as the deck. It now reads "Their trail, set out below, runs through three rooms...". - Also fixed: an intact supply-run hook would have read "died before the station left port" on a station. It now reads "died before the courier set out".
• Checked, not faults: "Table set for {crew}" comes from the bunks. The Calloway handout headed "ONE OF THE TWO" is there; my all-caps filter hid it. Willet's text diff before and after shows only the intended lines, and the map is unchanged.
• What read well: Corvid's welded crew quarters with the calm one inside, the XO's "I have told her it is for the fever", and Calloway's food under the door.
• Left as published: posted daily days keep their text. The Eight Derelicts ship files have none of these lines. Their PDFs keep the old "rooms, below" summary, which is cosmetic, so no re-export.
• Checks: tsc clean, 68 tests pass (3 new). 1.18 zip rebuilt ("the paid file is sound"); press links now ?v=1021. Deployed; the live zip matches by cmp. Status: all 29 clear. All four switch patches apply in order.
• Finished 23:18

00:07: sweep every station's text for ship-only words

• Generated stations at seeds 1-300, intact and derelict, and grepped the briefs, key notes and pdftotext of every derelict one-shot for hull words.
• Found and fixed six station-wrong phrases, all through STATION_WORDS: - "through the forward lock" (mutiny way in), 43 of 300. - "The forward airlock" (cold way in), 39. - "the forward rooms have about ten" (reactor clock), 39. - "Cut in through the hull aft" (reactor way in), 39. - "a retreat from the bridge aft" (boarding brief), 7. - "the drive core still remembers" (swarm twist, lower case; only the capitalised one was swapped), 2. They now say the hub lock, hub airlock, hub rooms, ring hull, "out to the ring" and "the traffic plot".
• The new test caught two more that my grep had missed, because it wanted 50 characters before each hit: the station bridge notes "Consoles forward;" and "Viewports forward." on intact stations. Now "Consoles along the window;" and "Viewports all round."
• Not faults: "hull" (stations have one), "to port" and "the next port" (where the players go), "a jump" (a leap), "matching course" (the boarders' cutter).
• Cause matching is safe: openings use only the first 24 to 40 characters after the name, and "bridge aft" is beyond that, so older saved stations still match. causes.json is unchanged.
• New test "a station speaks like a station": 120 stations, intact and derelict, brief + notes + raw one-shot PDF, no fore/aft/forward/left port/drive core/the ship. A temporary check confirmed the raw PDF text holds the new words, so the test does read the one-shot.
• Checks: tsc clean, 69 tests pass. 1.18 rebuilt ("the paid file is sound"); press links now ?v=1022. Deployed; the live zip matches by cmp. Status: all 29 clear. All four switch patches apply.
• Finished 00:19