24 Sep

The moment someone reaches for the export

Since yesterday the hosted demo stops at the .dd2vtt and PDF buttons and shows the buy dialog. That dialog is the one sales surface I control end to end, so it gets read as a visitor would. Two problems. It leads with "no watermark" instead of naming the exports, and it never tells a person who just made a ship they like that the ship stays in this browser and does not follow them into the paid file. Plan: rewrite the copy so it names what $12 exports, and add a "Save this ship first" button when the dialog was raised by a locked export. Test it on a phone-width browser and check the save actually produces a file.

Then, from the schedule

• 5:37: the daily run, the first to post with the hook line and the new label placement. Status clear, card read by eye.
• Count likes on today's post from accounts outside the four regulars.
• 26th: Owlbear card and events.sh (vtt-locked, pdf-locked, upsell-save, export-png). 27th: weekly pack.

5:37 check, added 03:50

• Today's derelict must trace to cause 1, 2, 5 or 7 (0, 3, 4 and 6 were told on the 19th–23rd). Read the card for crew count against bunks, labels clear of furniture, and no repeated room note.

Next: after the phone fix

• 11:37 check: npm run status, then count likes on today's derelict post from anyone outside the four regulars. That is the only sign the daily reaches new people.
• Then look at the phone "Another one" loop: does a second tap keep the room key in view, or does it jump back to the top of the panel? Fix it if it jumps.

Next: after "Another one"

• 11:37 check as planned, plus the like count from anyone outside the four regulars.
• Look at the intact ("working ship") generate on a phone the same way: does its story card read as well as the derelict's, and does its $12 line show?

Next: after the top bar

• 11:37 check and the like count, as planned.
• Phone-shot the three landing pages Reddit and Bluesky links go to (/derelict-ship-map-generator/, /free-sci-fi-battlemaps/, /daily/) and make sure the first screen shows what the link promised.

Next: after /daily/

• 11:37 check and the like count, as planned.
• The 27th's weekly pack will take the spot under today's ship. Check it reads as "last week's five" and not as today's.

Next: after the /daily/ button

• 11:37 check and the like count, as planned.
• 26th: visits.sh, count /daily/ -> / and /daily/ -> /daily/<date>/ to see whether Reddit visitors now go past the index.

Next: one r/battlemaps post a week

• The 27th's weekly pack (21 to 25 Sep, five derelicts) is the next thing worth an r/battlemaps post. The boss offered to post again on the 20th.
• Before the 27th: read r/battlemaps' rules on self-promotion and OC, then draft the post (title, flair and first comment, AI disclosure in the first line) for the boss as one copy-paste block on /press/, sent once the pack exists. Don't ask for r/traveller again.

Draft for the 27th: r/battlemaps post (fill in names once the pack exists)

Flair: Sci-Fi - Vehicle/Ship. Image: the pack's contact sheet, /packs/<slug>.png.

Title: [OC] five free derelict starship maps from this week, CC0, PNG + Universal VTT with walls, doors and lights (drawn by code an AI agent wrote, not an image generator)

First comment, posted by the boss right after: an AI agent built the generator and wrote this text, i just post it. the maps are drawn by plain code on a 5 ft grid, no image model, so the walls and doors come through as real data in the .dd2vtt. this week: <ship 1>, <ship 2>, <ship 3>, <ship 4>, <ship 5>. each one has a GM key with what killed it, the hazards and the salvage. zip, CC0, no email: https://bulkhead.bananafest-destiny.com/free-sci-fi-battlemaps/ how they're made: same page, "How these maps are made".

Checks on the 27th: the post's first line says who wrote it, there are no em-dashes, the $12 version goes unmentioned (rule 4 allows a shop line, but the post doesn't need one), and there's one post, not one a day.

Next: after the itch description fix

• Once the boss has done task 5, phone-shot the store page. Look for paragraphs, whole links and no redactor text.
• The 26th: button use on /daily/ (visits.sh), the Owlbear card, and events/clicks against itch views.
• The 27th: the weekly pack, then the r/battlemaps post goes on /press/ as one block.

Next: after the Owlbear review

• The boss replies on PR #174 (text is in chat). Then read the PR comments through the public API each daily check until it is merged or asked for more.

Plan: make the Owlbear extension survive a functional review

The PR #174 reviewer checked the listing, not the extension. Today /obr loaded once, from owlbear.rogue.pub. Before someone tests it, read src/obr.ts against the OBR SDK and the listing's claims: GM-only, uploadScenes, what happens with no room or a player role. Then load /obr outside Owlbear and check that it fails politely. Fix what's wrong.

Next: after the Owlbear harness

• Add node scripts/obr-harness.mjs ok|player|slow to the pre-deploy checks whenever obr.ts changes.
• Still waiting: the boss's PR reply, then the 26th's reads.

Next: after the listing check

• The rest of the evening: nothing new that needs the boss. At 17:37 the daily check runs. After that, check PR #174 comments via the public API.
• The 26th and 27th as planned above.

Next: after the daily Owlbear check

• Leave itch alone until tomorrow (429). Then one phone-shot of the store page, not a loop.
• PR #174: still one comment and waiting on the boss's reply. Read it again at the 17:37 check.

Next: after the name list

• On the 25th, confirm the daily ship's name isn't one of the old 15 (a 59-in-74 chance it's new).

Draft for Monday the 28th (UTC): r/FoundryVTT, Commercial Assets flair

The boss's call, because the module is untested in Foundry. Offer it on /press/ on the 27th alongside r/battlemaps, not before. Text post, no image.

Title: Bulkhead Deck Plans: 17 sci-fi ship and station scenes with walls, doors and lights, free CC0 compendium module (system-agnostic)

Body:

an AI agent built this module and the tool that drew the maps, and wrote this post. i'm the human who posts it

Content Name: Bulkhead Deck Plans

Content Type: Map

System: None

Description: 17 starship, station and derelict decks as a compendium of scenes. walls, doors and lights are already placed, so vision and fog work when you drag a scene in. free and CC0. the maps are drawn by code on a grid, not an image generator. honest caveat: nobody on our side owns a foundry licence. all 17 scenes pass v14's own strict validation (checked in foundry's public demo as a player), but no one has dragged one onto a real v14 table yet. if a scene comes in wrong, say so here and it gets fixed. the same site sells a $12 editor for drawing your own, which is why this is flaired commercial

Link: https://bulkhead.bananafest-destiny.com/foundry/ (manifest: https://bulkhead.bananafest-destiny.com/foundry/module.json)

Next, after the Foundry file check

• Consider generating scene thumbnails for the compendium (a small image per scene), so the list isn't blank icons when someone opens the pack. Do it only if it fits in one block, and before the 27th.
• Keep to the dated list: the 25th ship name and one itch shot; the 26th usage; the 27th weekly pack plus the /press/ drafts.

Next, after Foundry 1.1.1

• The Monday r/FoundryVTT draft needs one image showing Foundry, and I can't make one without Foundry. Before the 27th, find out whether a free Foundry trial or demo instance exists, from foundryvtt.com only and with no account. If there is none, the boss decides whether the post goes without the image. Ask on /press/ with the draft.
• Otherwise keep to the dated list (the 25th, 26th, 27th).

Block: Foundry image question, then the Foundry page

• Check foundryvtt.com for a free trial or demo. Read only, no account.
• If there is none, write the question for the boss on /press/ with the Monday draft (moved up from the 27th, because only the boss can answer it).

Next, after the v14 check

• Real-table proof remains the one gap. Only someone with a licence can close it; that's not something to ask the boss for (they don't use Foundry, as far as FACTS says). The r/FoundryVTT post invites it instead.
• Back to the dated list: the 25th ship name + one itch shot; the 26th usage; the 27th weekly pack and the /press/ drafts (battlemaps, FoundryVTT).

Block: read today's traffic, then fix the weakest step it shows

• visits.sh and events.sh since 00:00 UTC today. Pick one page or step to improve from that data, not from a guess.

Next, after the Save button

• The 26th: count brief-png and export-png next to the generate events. If people generate and still don't save, the next suspect is the watermark or the PNG itself, not the button's place.
• Don't count iOS 17 iPhone user-agent events as visitors; that is phone-shot. Worth making events.sh drop it the way it drops HeadlessChrome.

Block: look at the PNG a demo visitor actually gets

• Download it from the live demo at the default settings and judge it as a GM would: is it usable at the table, and is the watermark reasonable? Fix whatever makes it not worth saving.

Next, after the PNG and Bluesky read

• The 27th /press/ block: add an optional second #spaceshiptember quote-post draft, in the boss's voice, starting with the AI disclosure, for their go-ahead. #spaceshiptember ends on the 30th, so the 27th is the last sensible slot. The weekly zip post goes out as before.
• Otherwise keep to the dated list.

Block: are search engines crawling us?

• Run crawlers.sh since the 17th, and see which pages Googlebot and Bingbot fetch. Fix whatever keeps the SEO pages from being fetched (sitemap, internal links, IndexNow).

Next, after the internal links

• The 30th crawler read now also checks for Googlebot fetches of /maps/<ship>/.
• Up next is the 25th's daily check: the ship name from the new list, and the day page carrying the five derelict links from the template.

Status at 00:07

4 of 16 failing, all four about today's derelict, which runs at 5:37. The check cron is scheduled (37 5,11,17). Nothing else failing.

The buy dialog now names the exports and keeps the ship

Read the dialog the demo shows on a locked .dd2vtt or PDF click, on a 390px screen. The shared paragraph led with "no watermark" and a fleet, and never named the two exports the person had just asked for. Rewritten: "one HTML file that exports the finished map: the .dd2vtt with walls, doors and lights, the print PDF, and a whole fleet in one zip", then no watermark, offline, $12.

The bigger gap: someone who generated a derelict they like and hits the lock would buy, open the paid file from their disk, and find an empty editor, because the demo's autosave lives in the website's storage. The only warning was a grey hint. The hint now says it plainly, and the dialog has a Save this ship first button when a locked export raised it. It saves the .bulkhead.json and toasts "In the full version, press Open and pick this file". It's counted as upsell-save, so the 26th's read shows whether anyone uses it.

Tested in Chromium at phone width: the button shows, and the fallback download (Safari and Firefox) gives derelict-ftv-tamarind.bulkhead.json. In Chrome it opens the save picker, which is the existing Save path. Also cut a repeated sentence in the VTT lede. Tests 28/28, zip rebuilt (paid-check sound), deployed, smoke 34/34, live page carries the button.

A derelict tells one story

Generated a five-ship derelict freighter fleet, the paid feature, and read its FLEET.md and one full key room by room as a GM. Three faults a reader would catch:

• Repeated notes. Two cargo holds both said "Manifest on the wall, half the lines crossed out", two labs both "The notes stop mid-word", and the condition lines ("Cold. Frost on every surface.") came up twice. Each deck drew its notes alone, from pools of two.
• Contradictions. One pod bay said "All pods gone.", the other "Every pod still docked. Nobody left." Room notes also ignored the story: the swarm brief launches one pod, the boarding story takes them all, two others say they are all here.
• In one fleet, "ISV Wren Reach" and "FTV Wren".

Fixed with a pass over the whole ship before the story is placed. It uses no random numbers, so layouts do not change. A repeated note is swapped for an unused one from the room's pool. Cargo, engineering, lab and life support got a third note each, since they recur across decks. A repeated condition line is dropped. Pod bays take their state from the story (one launched, all gone, all docked), and a second bay agrees with the first. The crew-quarters note no longer assumes pods left. The fleet now keys hulls on the first word of the name.

Across 1,200 derelicts: repeated room notes 262 ships to 0, pod contradictions 155 to 0. Added as a test (29/29). Zip rebuilt (paid-check sound), deployed, smoke 34/34. The 1.17.1 devlog on /press/ mentions it, and now opens by saying an AI agent built Bulkhead and wrote the devlog; it had been missing that disclosure. Today's 5:37 derelict is the first built with this.

Intact ships get the same pass

Read an intact freighter and an intact station room by room. Same faults as the derelicts: two cargo holds with "Ladder down. Crates torn open from inside.", two engineering rooms where "the engineer sleeps here", both pod bays "All pods gone.". Two new ones: "Ladder down." on the lower deck, which has nothing below it, and "Nav plot still shows the last jump" on a station.

The ship-wide pass now runs for intact ships too, before the job's details are placed. It drops "Ladder down." unless that room holds the ladder to a lower deck, compares notes with the ladder stripped, and takes replacements only from the pool that matches the ship: dead notes for a derelict, living ones for an intact ship. My first version pulled "Reactor cold" into a working ship. Station room notes now go through the station wording, and the nav plot shows "the last docking approach". The test covers both moods and fails on a ladder note on the bottom deck. 29/29, zip rebuilt (paid-check sound), deployed, smoke 34/34.

A fleet of five is five deaths (03:00–03:25)

Went to put a real fleet on the pages, since the fleet is the main thing the $12 adds past the exports and no page showed one. The first fleet I generated had two quarantines in five ships. causeOf keyed on the brief's first words, and each cause has two openings, so a quarantine told two ways counted as two stories. Measured over 200 five-corvette fleets: 121 repeated a cause while the about page, the derelict page and every daily page said "five derelicts are five different deaths".

• causeOf now traces a brief back to the cause that wrote it (station wording included). generateSpread weighs a repeated cause 2, a repeated opening 1, a repeated hull 2, and tries up to 30 candidates instead of 12.
• After: 0/200 repeats. Hull (name) repeats: 9 in 1,200 fleets of four shapes with the first version of the fix (e.g. two "Halcyon Station"), 0 in 1,600 after the reweighting. That was also the source of a flaky test.
• Tests: a ten-ship fleet uses all eight causes, none more than twice; twenty ships use all eight, none more than three times, with at least 13 openings; every derelict brief traces to a cause; and the sample fleet quoted on the site is pinned to the generator.
• /about/ and /derelict-ship-map-generator/ now quote a seeded five-freighter fleet, first line of each brief, nothing edited: specimen, misjump, reactor, quarantine, debris.
• The paid zip was rebuilt (release.mjs, paid-check sound) and the site deployed. 34/34 pages, 27/27 links. The task 5 devlog on /press/ gained one sentence about the fix. The listing still serves 1.17 until the boss uploads, so buyers today still get the old spread.

The daily was retelling deaths too (03:30–03:50)

RUM since the 23rd: 35 page loads, 10 from the Reddit app, 7 of them to /daily/. I looked at that page on a phone. At the top is the 23rd's shuttle, whose story has "seven crew wanted to turn back, two wanted to press on" over two bunks. That is the r/traveller complaint, and the fix for it landed that evening, after the card was made. The labels there sit on furniture for the same reason. At 5:37 the 24th goes on top with every fix in it. I am not regenerating old days: the date seed would make a different ship from the one already posted.

The daily's "don't retell a story" check had the same fault as the fleet: it keyed on the brief's opening words. Traced back to causes, the archive has the same death on 16 and 17 Sep (consecutive days, and both in the first free pack) and on 19 and 22 Sep.

• generate.ts now exports causeOpenings() (18 openings, ship and station wording, mapped to 8 causes). causeOf and the fleet use it, and scripts/lib/causes.json is a copy the daily script reads under plain node. A test fails if the copy drifts.
• The window drops from 10 days to 5. With eight causes (seven for a station), a 10-day no-repeat rule cannot hold and the loop would just give up after 24 tries. Dry run for today: causes 0, 3, 4 and 6 are blocked, and it picks from the other four.
• Checked, not a problem: store/bulkhead.html is dated the 23rd, but daily-derelict.sh rebuilds it before every run.
• Tests 32/32; release sound, deployed; 34/34 pages, 27/27 links.

Read three ships as a GM would (04:00–04:25)

Generated a derelict station, a derelict shuttle and an intact freighter, and read every room. I found four things a reader would catch:

• An intact freighter "on schedule" with All pods gone in one bay and "Empty cradles" in the other. The intact pod pool had "All pods gone." in it.
• The same ship had Reactor scrammed on the upper deck and Reactor hums on the lower. The intact line is now "Backup reactor, cold. Manual start: twenty minutes, two people."
• A cold-soaked station (heater, frost, "the cold has lasted longer") with the coffee machine is still warm in the galley. settle() now has a CLASHES table: when the story is cold, a "still warm" note is swapped for another from the room's pool.
• A shuttle has no pod bay, but its story says the pods went, one at a time, in four different directions. On a ship with no Escape pods room, storify now filters out briefs, hooks and notes that mention pods. The list is only filtered when there is something to drop, so ships with pods roll exactly as before, and the pinned sample fleet is unchanged.

Before → after, on the same seeds: shuttles mentioning pods 93/300 → 0; cold stories with a warm room 60/900 → 0; intact ships with pods gone or a scrammed reactor 612/900 → 0. Two test rules and one new test hold these. Tests 33/33; release sound, deployed; 34/34 pages, 27/27 links.

Checked and not a bug: "Table set for 23" on that station. The station has 23 bunk stamps across two crew quarters; I had first counted kinds, not stamps.

Daily check (06:07)

The status check at 06:07 had 4 of 16 failing: today's page, feed, run and Bluesky URL were all missing. The daily run is this check itself; the session cron fired at 06:07 instead of 5:37 because it waits until the session is idle. I ran daily-derelict.sh by hand. Status is now all 19 clear. Post: https://bsky.app/profile/bananafest-destiny.bsky.social/post/3mwb4ibtszg2u, with the map attached and the link back.

Read the card by eye. It is the first one with every fix from the 23rd and 24th.

• RSV Osprey Verge, a corvette. It traces to cause 2 (quarantine); the new picker had 0, 3, 4 and 6 blocked, and it chose outside them.
• Labels sit clear of furniture and breaches. No room note repeats. There is no pod bay, and nothing mentions pods.
• The galley says "Table set for six". Six bunks: five in crew quarters and one in engineering ("the engineer sleeps here"). Right.
• Nit: badge 7 sits on the reactor in engineering. It is legible, and I left it.

Room numbers off the furniture (06:20–06:45)

The one nit on today's card was badge 7 on the reactor. It is not a one-off: engineering puts its reactor at the room's centre, and the number badge went at the centre. Across 3,868 generated rooms, 1,652 numbers sat on furniture.

• New badgeSpots() in model.ts: keep the centre if it is clear, else take the nearest half-cell step (up to three cells) where the badge circle lands on bare floor of its own room, clear of stamps and labels. The canvas renderer, the PDF and the generator's label placement all use it now.
• Saved maps keep their labels where they are, so the badge steps round them. For a first try on today's ship, badge 7 moved off the reactor onto the ENGINEERING label, which is why labels count too. The generator computes spots without labels, then moves labels clear of them. The renderer then agrees with the generator in all but 3 of 3,868 rooms.
• After: 2 of 3,868 on furniture, 0 on a label. New test (under 0.5%). Tests 34/34; release sound, deployed; 35/35 pages, 28/28 links. Checked by eye on RSV Osprey Verge in a local build.
• PNGs already rendered (the daily archive and packs) keep their old badges. Every new render, export and daily gets the fix.

Phone: the story card's buttons and the room key

A phone screenshot after tapping "Generate a derelict" showed the story card taking 45% of the map, with "Read the room key", "Another one" and the $12 line cut off below its fold, and the panel under the map still on Plan settings. Now on narrow screens only the story text scrolls inside the card. The buttons and the $12 line always show, and the panel under the map scrolls to the Room key, where the whole story and every room note can be read. I checked it on a local phone-size screenshot before shipping. Tests 34/34, the paid file is sound, deployed, smoke 35/35 pages and 28/28 links.

Phone: "Another one", and the same death twice

I checked the phone loop on the live site. After a reader scrolls into the room key, "Another one" puts the panel back at the start of the new story. That part was fine.

The same check turned up a real fault. Two taps in a row both "misjumped". The demo drew one of the eight deaths at random, so each tap repeated the ship before one time in eight, and three taps had about a one-in-three chance of a repeat. Now it remembers the last three causes (the same causeOf the fleets use) and rerolls, up to eleven times, to avoid them. Ten taps on a local build gave no death twice within three ships. Tests 34/34, the paid file is sound, deployed, smoke 35/35 pages and 28/28 links.

Phone: the working ship, and the name boxes in the top bar

A working ship (the "Generate a ship" button) reads as well as a derelict on a phone. Its card shows the story, both buttons and the $12 line, and the panel under the map opens on its room key. Nothing to fix there.

Every phone screenshot today showed the same fault in the top bar. The ship-name and deck-name boxes were about 40px wide and showed one letter each ("M", "M"). Under 560px the deck-name box is now hidden, since the deck tabs on the map already name the deck. The Demo line wraps onto two short lines instead of one long one. A 390px phone now reads "MSV Kestrel" in full. At 320px the Demo line takes three lines but stays inside the bar, with no sideways scroll. Tests 34/34, the paid file is sound, deployed, smoke 35/35 pages and 28/28 links.

Phone: the pages links land on

I took phone screenshots of /derelict-ship-map-generator/, /free-sci-fi-battlemaps/, /daily/ and today's day page. Bluesky posts link to the day page. It opens on the ship, its story and "Open in Bulkhead", and ends with the $12 fleet pitch. It was fine. So were the two landing pages: their first screen says what they are and has a clear button.

/daily/ was not. It is what the "Daily derelict" link in every page's menu opens, and its first screen was last week's pack (16 to 20 Sep), with no ship from today. The daily script now puts today's ship first, loaded eagerly, then the pack, the explanation and the older days. Rebuilt for today (the ship files are unchanged, only the index), with sitemap dates restored. Deployed, smoke 35/35 pages and 28/28 links, status all 19 clear.

/daily/ gets a way into the editor

RUM since yesterday: 40 page loads. 10 came from the Reddit app, 7 of them to /daily/. None of the /daily/ visitors went on to the editor or to a day page. On the index, today's ship had download links and nothing else, while the day page has "Open in Bulkhead". Today's entry on /daily/ now has the same button and a link to its GM key. The home page is doing its job: 11 loads and 6 generates. The Owlbear page (6 loads) reads fine on a phone. Deployed, smoke 35/35 pages and 28/28 links, status all clear. On the 26th, count /daily/ -> / and /daily/ -> /daily/<date>/ in visits.sh to see whether the button is used.

11:37 check, run at 11:48

Late because the boss had an off-topic ask (their own app, not Bulkhead), which ended with nothing to do. Status: all 19 clear.

Bluesky likes on the daily posts, from the public API: 18th 1, 19th 1, 20th 2, 21st 1, 22nd 1, 23rd 1, and 0 so far on the 24th. No reposts and no replies on any of them. RUM since yesterday shows no bsky.app referrer at all, while the Reddit app sent 10. The Bluesky post costs nothing, but it is not the channel. /daily/ is worth its keep as a page Reddit sends people to and as a page search can index, and that is where today's fixes went.

Where /daily/'s Reddit visitors come from

Reddit's JSON is still blocked from here, but the logs name one post: the boss's r/battlemaps post from the 20th (Nimbus Station). By reddit-watch.mjs it has 4 points and 5 comments, all friendly ("You're doing a real service here, keep it up!"). Four days on it still sends Reddit app visitors to /daily/, and it is the only Reddit link I know of. The channel that works is one CC0 map post in r/battlemaps, and it pays out for days.

r/battlemaps rules, read from the sidebar

39K members. The rules that bear on a weekly Bulkhead post:

• 4: maps must be usable, not behind a paywall. A post that includes a usable map may mention a shop. Our CC0 PNGs and .dd2vtt files qualify, and the $12 line belongs in a comment, not the title.
• 6: "AI-generated images are not allowed". It names image generators (Midjourney, Stable Diffusion, DALL-E, ChatGPT). Bulkhead's maps are drawn by ordinary code from rooms and stamps; no image model is involved. But my rule is that every boss-voice post says in its first line that an AI agent made the tool and wrote the text. So the post has to say both plainly: an AI agent wrote the code and this text, and the maps are drawn by that code, not an image generator. If that line alone gets the post removed, that is the answer, and we don't argue it.
• 7: one post per day per creator. Weekly is well inside that.

Flair: "Sci-Fi - Vehicle/Ship", as on the 20th.

17:37 check, then "How these maps are made"

Status all 19 clear.

r/battlemaps rule 6 bans AI images, and my posts say an AI agent made the tool. So a reader or a mod needs to be able to check that the maps aren't AI images on the page the post links. The site only said "built by an autonomous agent" in a footer. Now /free-sci-fi-battlemaps/ and /about/ each have a short section saying an AI agent wrote the code and the words, and that no image model is involved. The generator lays rooms, corridors and doors on a grid from a seed, then draws walls and furniture as lines, rectangles and circles. I checked this against src/stamps.ts: every stamp is drawn from rect/circle/line calls, and the only image loader is for pictures a user imports. Deployed, smoke 35/35 pages and 28/28 links. The draft for the 27th's r/battlemaps post is in plan/.

The itch description is one paragraph with a broken link

A phone screenshot of the store page showed the saved description as one block. Every line break had turned into spaces. itch's auto-linker also cut each URL at the first / after the domain, and it left a scrap of its own markup showing as text: /guide/" class="redactor-linkify-object">. The pack pages kept their paragraphs and full links, because they were pasted as formatted text. The description was pasted as plain text.

The replacement queued on /press/ (task 5) would have broken in the same way. So /press/ now has a Copy formatted button that puts HTML on the clipboard: paragraphs, headings and full links, with plain text alongside it. The old button stays as a fallback. Tested in headless Chromium: the clipboard holds both text/html and text/plain, with 6 headings, 10 paragraphs and 4 links whose paths are intact. The description's first line now says an AI agent wrote the code and the text. Deployed; smoke passed with 35 pages and 28 links.

Owlbear PR #174 got a review

The boss forwarded a comment from a reviewer on owlbear-rodeo/extensions#174. The validation script, the image URLs and the learn-more link all pass. Two things block it:

• the description is over 128 characters, so the extension won't install;
• /obr/icon.svg has no transparency, so it may show as a blank rounded square in the action tray.

The PR only holds a URL to our /obr/store.md (read from the public API), so both fixes are on our side and the PR itself doesn't change:

• The description in both manifest.json and store.md now reads "One click makes a whole starship or derelict, or draw your own deck plans. Saves a scene with walls, doors and lights for fog." That's 126 characters.
• icon.svg lost its filled navy rect. It is now a white outline of a hull split into four rooms with doors, on transparent. I rendered it on red to check it.
• status.mjs gained two checks: the description is 128 characters or fewer, and the action icon has no background rect. Status: all 21 clear.

The Cloudflare token can't purge the cache (authentication error). The files revalidated on their own anyway, because they are served with max-age=0, and all three are confirmed live. The boss needs to reply on the PR, since the reviewer asked @walkertbrown.

The Owlbear extension, run against a fake Owlbear

The PR #174 reviewer said "Extension functionality and API usage not checked". Today /obr loaded once from owlbear.rogue.pub, and two visits came from there. The only end-to-end test was the boss's room on the 15th. So I built scripts/obr-harness.mjs. It loads /obr in an iframe on another origin, with the obrref the SDK expects, and answers the SDK's postMessage calls the way Owlbear does.

• GM: the panel shows and Send goes out. The scene arrives as "ISV Example — Deck 1": 150 dpi, 5ft grid, fog filled, a base map and 43 items on the FOG and MAP layers. The note reads "35 walls, 6 doors/windows, 2 lights".
• Player: Send is disabled, and the note says "Only the GM can add scenes."
• Slow: Owlbear doesn't answer uploadScenes in time. The SDK gives that call its default 5 s (sendAsync, AssetsApi.js), and the caller can't change it. If Owlbear answers after the folder dialog closes, a GM who takes more than 5 s to pick a folder, or a four-deck upload, would have seen "Could not send" and an error toast while the scene still saved. src/obr.ts now treats that timeout as "Owlbear is still working on it; pick a folder" and shows no error. The harness confirms the new note and that the buttons come back.

Tests: 34 passed. Deployed; smoke passed with 35 pages and 28 links. The live obr bundle has the new text.

The Owlbear listing, checked claim by claim against the code

The store.md that PR #174 points at is what an Owlbear user reads before installing. I checked each claim that could be tested:

• "Only the GM sees the Bulkhead panel", and step 1's "(GM only)": false. The harness showed a player gets the panel with the send buttons disabled. Both now say players can open it but only the GM can send scenes. The same "(GM only)" on /owlbear-rodeo-dd2vtt/ is fixed too.
• The watermark "bulkhead.bananafest-destiny.com · demo": false for the extension. obr.ts sets it to the bare domain, on purpose, so the scene doesn't claim to be a demo of something. Fixed.
• "Seventeen finished deck plans": accurate, since it's 17 scenes across both packs. Reworded to "Two packs of finished deck plans (17 decks) and a new derelict every day".
• Eight causes, 40 hazards, 48 logs, 24 salvage: true. I evaluated the CAUSES table and got 8 / 40 / 48 / 24, plus 47 hooks.
• The button labels "Generate a ship", "Send this deck to Owlbear" and "Send all decks", and the API uploadScenes: true.

Also tried: Bing site: shows 4 of our URLs, one of them /obr/manifest.json. Generic Bing and DuckDuckGo queries from this machine come back as junk or blocked, so search position can't be read from here. That's still task 7 (Search Console) for the boss.

Deployed. Status: all 21 clear. Smoke passed with 35 pages and 28 links.

The fake Owlbear now runs against the live site every day

• itch answered this machine with 429 Too Many Requests, so I stopped reading the store page for now. Status's own itch check is unaffected.
• The r/battlemaps post from the 20th: 5 points, 5 comments. The boss had already answered everything, and nothing is new.
• Events since the 17th: 14 generate-derelict, 12 link-derelict and 2 generate-intact, 27 of them today. clicks.sh counts 10 buy clicks this week, but itch says 15 lifetime views and 0 purchases, so I'm not reporting those clicks as buyers.

The harness now serves its fake host from https://owlbear.test through Playwright routing and points it at the live /obr by default. It exits 1 unless a GM send saves a scene (or, in player mode, Send is locked). status.mjs runs both modes: all 23 clear. Pointed at a base that doesn't exist, it exits 1, so the check can fail.

Ship names: 15 became 74

The Bluesky posts are already well built: five hashtags, langs: en, alt text on the image. They still get 0 or 1 like each. What stood out was the names. The last nine dailies were Sable Dawn, Halcyon Verge, Nimbus, Vantage, Corvid, Osprey, Vantage Station, Sable Verge and Osprey Verge, so Sable, Vantage and Osprey came up twice each in nine days. They were drawn from a list of 15, and that list is also the names of the free packs' ships and the /maps/ pages. At one ship a day, every name would come round again about every two weeks.

• NAMES in src/generate.ts now has 74 entries: the original 15 plus 59 new ones, with no duplicates. It leaves out Vesper, which /maps/ already uses, and every famous fictional ship. pick() draws one number whatever the list length, so layouts don't change. Deck and room counts for the seeded sample fleet match before and after: 2 decks and 17 keyed rooms each.
• The test that pins the sample fleet quoted on /about/ and /derelict-ship-map-generator/ failed, as it's meant to. The fifth ship changed story as well as name (Threshold's debris field became Solace's power failure), probably because the fleet code re-rolls repeated names less often now. I updated both pages to the generator's current output: Coldharbour, Winnow Verge, Hollis, Sparrowhawk Drift, Solace. The "two decks, seventeen keyed rooms" line is still true.
• store/bulkhead.html looked stale (06:07). But daily-derelict.sh rebuilds the paid file and copies it there before it generates, so tomorrow's derelict uses the new list.

Tests: 34 passed. Deployed; smoke passed with 35 pages and 28 links; status: all 23 clear. The 1.17.1 zip was rebuilt with the new list, under the same name, since the boss hasn't uploaded it yet.

17:xx daily check, and where else on Reddit we can post

The daily check: all 23 clear. Nothing to run.

Reddit is the only channel that has sent visitors, and r/battlemaps allows one post a week. I read the rules of six more subs with headless Chromium (details in LEARNED.md):

• Closed: r/SWN and r/AlienRPG (no AI content, map packs included) and r/Roll20 (no map posts).
• r/OwlbearRodeo: no artwork self-promotion.
• r/VTT: small.
• r/FoundryVTT, the one real opening: a Monday (UTC) Commercial Assets post for the free Foundry module, using the sub's template.

The catch: the module has never been run in Foundry. /foundry/ says so, and the boss won't pay for a licence (FACTS, the 18th). So the draft says so in plain words, and it has no image, because images must show the content inside Foundry and we have none.

Foundry module checked without Foundry

I have no Foundry licence, so I checked the module's files directly. I extracted the compendium with the official foundryvtt-cli and unzipped the release zip.

• The zip has module.json at its root (id bulkhead-deck-plans, 1.1.0). All 17 scenes point at a background image that is in the zip, and each image is exactly the scene's width and height, so nothing is stretched. No wall lies outside its scene.
• I drew two scenes' walls, doors and lights over their images: an intact command deck (167 walls, 21 doors, 9 lights) and a derelict hub (116 walls, 18 doors, 2 lights, as it has lost power). The walls follow the drawn walls and the doors land on the door marks.
• Loose ends that don't break anything: - The pack entry says "system": null, which Foundry treats as no system. - Scenes use the older top-level globalLight, which Foundry migrates when you import. - The scenes have no thumbnails, so the compendium list shows blank icons.
• Still unproven: an actual import in v13 or v14. The Monday draft already says so.

Foundry module 1.1.1: compendium thumbnails

• Each of the 17 scenes now has a 300 px webp thumbnail (68 KB for all 17), so the compendium shows the ship instead of a blank icon. I rebuilt the pack with the official CLI and extracted it again to check: 17 scenes, each with its thumb.
• I removed "system": null from the pack entry, bumped the version to 1.1.1 (both manifests and the page's structured data) and rebuilt the zip. Anyone who installed by manifest URL will see the update offered.
• Live: module.json says 1.1.1, and the zip downloads (200) with its thumbnails. Smoke: 35/35 pages, 28/28 links.

Foundry module checked in real v14, without a licence

• foundryvtt.com links a public web demo, demo.foundryvtt.com, running v14 build 365 on a PF2E world. It only lets visitors join as players, with the password printed on the join page ("foundry"). I could not import anything there, and did not try.
• In that player's browser, the real v14 document code is loaded. For each of our 17 scene JSONs I built the Scene in memory with new Scene(data, {strict: true}). That runs Foundry's own migration and strict validation and saves nothing to the shared world. - Result: 17/17 valid, with zero warnings while building. - Wall, door and light counts match the pack. The command deck, for example, has 167 walls, 21 doors and 9 lights. - Grid is 100 ft, global light is off, and the thumbnails are kept.
• v14 moved scene backgrounds into Levels. I read the demo's public client code (foundry.mjs): when a scene is created, which includes a compendium import, Scene._preCreate finds no levels and builds a default Level from the old background.src. Our old-style background therefore carries over on import. Because thumb is set, Foundry keeps ours instead of generating one.
• Still unproven: a GM actually dragging a scene onto a v14 canvas. The Monday draft's caveat now says exactly that.
• /foundry/ page caveat now says the same thing (v14 strict validation passed, background moves into a Level, no real-table drag yet). Deployed; smoke 35/35 and 28/28, live page carries the new line.

Traffic says people generate and don't save: a Save button on the ship card

• I broke down today's demo events by hour and country. At 16:00 UTC one person in Poland (Firefox on Windows) opened the ?gen=derelict link 12 times and pressed Generate 9 more times: 21 derelicts, and not one export, not even the free PNG. Their page views never reached the beacon, so they probably run an ad blocker; the events come from the request log, which does see them. The iPhone iOS 17 events at 12–14 UTC are my own phone-shot runs (same user agent). The other real events today: Brazil (2), the Netherlands (1, inside Owlbear).
• Why nothing was saved: the card that pops up with a generated ship offered only "Read the room key" and "Another one". Export PNG is a long way down the sidebar, under the whole room key.
• Change: the card now leads with Save the map (PNG), which runs the same export as the sidebar button, plus "Room key" and "Another one". It also counts brief-png, so the next check can see whether anyone uses it. On phones the label shortens to "Save (PNG)", and to "Save" at 360 px or less. At 320, 360, 390 and 1366 px all three buttons sit inside the card. It is in both index.html and obr.html, whose IDs stay in step.
• Tests 34/34, release zip rebuilt ("the paid file is sound"), deployed, smoke 35/35 and 28/28. The live ?gen=derelict page gives a PNG download from the new button. Status: all 23 clear.
• events.sh now drops phone-shot's iOS 17.0 agent. Today, visitors only: 12 link-derelict, 10 generate-derelict, 1 generate-intact, 1 obr-generate-intact, and no exports.

The demo PNG, judged, and what Bluesky gives back

• I downloaded the PNG from the live demo (?gen=derelict, then Save): 3800×1300, a full derelict with numbered rooms and hull breaches. The only mark is a small grey "bulkhead.bananafest-destiny.com · demo" in the bottom-right corner. Labels are tight in places ("CREW" pressed to a wall, "CARGO HOLD" next to marker 5) but readable. The dialog that follows says honestly what the watermark is and what $12 adds. The image is not a reason anyone would skip saving, so I changed nothing. The weak step was only where the button sat.
• Bluesky, read through the public API: 5 followers, 17 posts. The dailies get 0 to 1 like each. The best posts were the weekly five-derelict zip (4 likes) and the boss's #spaceshiptember quote-post on the 20th (2 likes, 2 reposts, the only reposts we have). So the channel is costless but nearly silent; only the weekly zip and the hashtag post reached anyone.

Crawlers: the ten ship pages had no way in from the pages Google revisits

• crawlers.sh since the 17th: Googlebot fetched 16 of 33 sitemap pages and Bingbot 12. Both fetched /maps/ but only one of the ten ship pages under it. Google revisits the daily pages every day (it fetched 16th–21st), and those linked only to the /maps/ index. The favicon 404 in the log is from before it was added on the 21st; it is 200 now. The sitemap dates are honest: the map pages really changed on the 24th (UTC).
• Every day page, the nine live ones and the template for future days, now links the five hand-finished derelict pages by name. /space-station-map-maker/ gained a short "Three finished stations, free" section linking Threshold, Vesper and Corvid; I checked that each has a hub and a ring deck with .dd2vtt.
• Deployed (smoke 35/35 and 28/28, both new blocks live), sitemap lastmod refreshed, and the ten affected URLs sent through IndexNow: 200 accepted.
• To judge on the 30th with the crawler baseline: whether any /maps/<ship>/ page is fetched by Googlebot.