Plan, 2026-10-17

01:07: Derelict opens on a title card with the painted cover

• Jam raters judge the first five seconds. Right now the game opens straight onto a map and a message card. A title card makes it read as a game.
• The card: the cover painting, DERELICT, today's ship name, one line on the rules and par, and a "Board the ship" button. It shows on the first visit of the day and on practice ships, and never over a run that's already finished.
• The painting is a ~40 KB webp bundled through Vite, so the itch zip carries it too.
• Check on desktop and phone, run the tests, deploy, verify it live.

01:17: Read the jam page before it opens for the theme and rules

• Submissions open 03:00Z. Read https://itch.io/jam/ai-jam-5 now for anything new (theme, rules on AI art, screenshots, the HTML embed size, and whether the jam needs the game made during the jam), and check /press/derelict against it so the boss's steps still hold.
• If the page asks for something /press/derelict doesn't cover, fix the press page and deploy. If the theme isn't out, write when to read it again.

01:18: Draft a how-it-was-made devlog for the jam's AI Usage vote

• The jam votes on AI Usage and says sharing tools, prompts, pipeline and lessons is "encouraged". Write a short devlog the boss can post on the Derelict itch page after submitting. It covers how the agent works, what code does and what the image model did (with the real prompts and cost), and three lessons, every fact checked against the repo.
• Host it on /press/derelict as a step 5 with a copy button. Don't post anything myself.

03:03: Read the jam theme now that submissions are open

• Read the theme from the jam page and decide whether Derelict can take it with a small, true change (copy or one game element). Note it in FACTS-free form in actual; it's a public fact from the page, not from the boss.

03:07: Jam half 1, a ship that hums: a generative ambient score for Derelict

• The jam needs at least half of Derelict made from 17 Oct on, and Audio is one of the six votes. Today the game has only short synthesised effects. Add a generative ambient score made in Web Audio: a low drone, a slow pad that gets tense as the air drops, and distant hull groans. It's seeded per ship, follows the sound toggle, and starts only after "Board the ship".
• Start a dated list of what's new in the jam window, at app/store/DERELICT-JAM-NEW.md, so the devlog and the boss can see the new half.
• Check it in the browser (no errors, the audio graph starts and stops), run the tests, deploy, verify it live.

04:04: Read the jam theme, now that the page has changed

• The "Theme: ???" line is gone from the jam page. Read the theme, write it into the actual, and decide how Derelict's new half takes it.

04:04: Jam half 2, the cutting torch in the engine

• Read the engine's step, cost, replay and SEALED code. Add a torch with limited fuel: cut through a wall into the next room, or cut a sealed door with no SEALED charge. Use a new move letter so replay() reproduces it exactly, and give it tests. Use the bot to size the fuel and air cost so a cut is a choice. UI comes in the next entry.

04:13: Jam half 3, the torch in your hands: controls, light and sound

• A Torch button and the T key arm the torch, and the next direction (arrow, pad, or a tap on the square next to you) cuts. While it's armed, the walls you can cut glow on the map. The HUD shows the charges left, the cut has a sound and a message, and a warm torchlight circle is drawn around you.
• Check on desktop and phone with Playwright, run the tests, deploy, verify live, then let the bot measure whether par still means something.

04:24: Does par still mean something with the torch

The bot that set par plays without the torch. Teach it to cut where a cut saves air, run it over a spread of days with and without the torch, and compare the scores to par. If the torch beats par by a lot, raise par or make the torch cost more. Write down the numbers either way.

04:26: Jam half 4, a survivor sealed in

Some ships carry one survivor, shut in a room the logs point to. Reach them and they follow you, and each step costs 1 more air while they do. Get them out the airlock for a big bonus and a line in the story. The torch is often the quickest way in. Engine and replay first, with tests, then the screen and the story. Deterministic from the ship seed so everyone gets the same survivor.

05:07: Survivor in the engine, with tests

Build the rules half of the survivor: one ship in some carries a survivor in a room away from the airlock, placed from the ship seed. Walking onto them starts them following; while they follow every move costs 1 more air; leaving with them adds a bonus. Moves stay replayable. Tests for placement, the follow cost, the bonus and replay. No screen work yet.

07:07: Survivor on the screen, then switch it on

Draw the survivor in their room once you have seen it, and one step behind you once they follow. When you reach them, show their name and first line. The HUD says who is with you, the share text and end story say whether you got them out, and dying with them says so. Then take out Game.survivors = false, check on desktop and phone with Playwright, run the tests, deploy, and verify live.

08:21: A daily leaderboard for Derelict

The boss wants one ("no leaderboard? I think that makes it competitive"). A run sends its moves, not its score. The worker replays the moves on the day's ship with the same engine and keeps the score it gets itself, so a forged score can't get on the board. One entry per player per day. Names are callsigns the game makes up, so there's no free text to moderate. The end screen shows today's top 10 and your place. Record the quote in FACTS.md.

09:07: Jam half 6, fire: the ship fights back with flame

A new way the dying ship fights back, on the theme: a fire breaks out in a room near you. Every step in a burning room costs 2 more air, and each time the ship decays again the fire can spread through a door into the next room. Draw the flames, tag the cost, give it a sound and a line, and teach airOut and the route costs about it. Engine and tests first. It goes live with the 11:07 daily deploy, at the ship change, so nobody's run changes rules halfway through.

10:11: Jam half 7, new ways to die: what killed you, and the fire can reach the survivor

The boss said "do more of #2 right now". Two new kinds of death. First, the run records what killed you: the air ran out in a burning room, in smoke, in a room with its own hazard, out in a hull breach, or in a plain corridor. Each one gets its own end-screen title, story line and share line. Second, a survivor you haven't reached yet can be lost if the fire gets to their room first. The engine records it, and the screen, story and share all say so. Engine and tests first, then the screen and a Playwright check, then commit. It goes live with the 11:07 daily, along with fire.

10:21: Jam half 8: new screenshots for the press page

Shoot in-game screenshots at 1100x800 that show the new half: the torch lit with walls glowing, a fire spreading, the distress signal and the survivor following, and the end screen with the board. Put them under app/public/press/derelict/ and add them to the press page, so the boss can use them on the itch page when they submit. No paid art. Deploy only after the 11:07 daily, and never while it is running.

10:24: Measure the jam half: how much of Derelict was made since 17 Oct 03:00Z

Count the Derelict game code lines added since the jam opened against what existed before it: the files in app/src/game, app/worker, app/derelict, the generator's derelict parts and the tests. Write the figure into DERELICT-JAM-NEW.md so the call on when to submit rests on a number.

10:57: The boss asked "ok what now": check the 11:07 daily, then the next jam piece

If it's past 11:07Z, check today's daily log and npm run status, and run the day if it is missing. Then confirm that fire, the deaths and the press shots are live, and that the board answers for today. If it's before 11:07, start the next jam piece and keep it switched off until the daily has gone out.

11:07: Run the 11:07 daily, check it, then start Blackout days

Once it's past 11:07Z and today's derelict is missing, run daily-host.sh in the background, then npm run status, the Bluesky URL check, and checks that fire, the press shots and the board are live. After that, start the daily conditions with Blackout, engine first.

11:44: Next jam piece: one new mechanic in rules, page and tests

• Boss said "ok do something". Pick the next piece of new game for the jam's 50% rule, build it in the engine with tests, draw it, keep it off until a daily ship change if it changes scoring.
• Read engine.ts first to choose something that fits (likely air canisters or a new hazard), not a rewrite.

Next

• JAM THEME IS TORCH (17 Oct). Item 1 of the new half is a cutting torch: limited fuel, cut a sealed door or cut through a wall into the next room as a shortcut, a new move letter so replay stays exact, and a lit circle drawn around you. Size the fuel with the bot. Then a survivor and the rest below, fitted to torches where it's true to the game.
• JAM NEW HALF (from 17 Oct 03:00Z; the host wants 50% new content made during the jam, LEARNED 17 Oct). Don't let the boss submit until app/store/DERELICT-JAM-NEW.md clearly outweighs the pre-jam game, aiming for about 24 Oct so there is a week of votes. Candidates, theme permitting, biggest first: (1) a survivor aboard: some ships hold one crew member you can find and walk out (slower, uses air), worth more than any cache, and the logs say where they hid; (2) new ways the ship fights back: power cuts that hide the plan, venting rooms that push you, a door that only opens from one side; (3) four new causes of death, each with logs and room changes; (4) the leaderboard, only if the boss says yes. Fit it to the theme once it's out. Rewrite the step 5 devlog from the JAM-NEW list.
• Jam (17 to 31 Oct, submissions open 03:00Z today): the boss makes the itch page and submits, using /press/derelict. When the theme is announced, read it and work it into Derelict. Competition check on 25 Oct, target top 20.
• Leaderboard: asked the boss 16 Oct. It needs the Cloudflare token confirmed as rotated, or a KV namespace the boss creates. Build nothing until they answer.
• Daily run after 11:07Z if today's derelict is missing.
• AI Browser Game Jam 5 (17 to 31 Oct, https://itch.io/jam/ai-jam-5): a reason to start Derelict on 17 Oct instead of waiting for the 22 Oct decision. Bulkhead is shipped and for sale, so RULES allow app two. Put it to the boss; the boss would join the jam and submit the page.
• Fourteen Ships itch page: handed to the boss 15 Oct. Once it is live: check the page, add it to Bulkhead's page and the site, IndexNow. Compare its views against the free packs (16/11) on 22 Oct.
• 22 Oct, decision point (set 15 Oct): when the sale ends, read itch views, downloads and purchases. If Bulkhead still has 0 sales after the kits bundle and the Owlbear listing have had their chance, stop pushing it as the main work: keep the daily running, and pick app two. Pick it for a market where an AI-made tool is welcome (check each store's and community's AI rule before building), and with a channel that reaches buyers on day one.
• ROLL20 AND DRIVETHRU CLOSED (15 Oct): DriveThru Partners wrote that no standalone artwork "generated in whole or in part by AI" is accepted on any Roll20 or DriveThru marketplace, and that AI-touched titles must carry the Contains AI-Generated Content filter. The packs are made by AI-written code, so they do not go there in any form. Do not resubmit, do not change the Creation Method, do not send the drafted question. The seven drafts can stay in Drafts. The pack kits and store/roll20/ stay as they are (a possible itch bundle, see below).
• Re-plan the paid bet (16 Oct): itch (Bulkhead $9 on sale to 22 Oct, then $12) and the Owlbear store. Facts first: itch views and buys since the sale began, which pages bring the visits that become itch views (events by referrer, sittings). One candidate to weigh: put the ten ready ship kits on itch as a paid map bundle beside Bulkhead, stated plainly as procedurally generated by AI-written code (itch allows that when tagged; check itch's current AI disclosure rule first). No new free packs.
• r/starfinder_rpg is closed: the 15 Oct post was removed under Rule 4 (low effort). Do not ask the boss to message the mods or repost. The next Reddit ask is still not before 22 Oct, and it must read as a post for that sub's readers first (a question, a how-to, a free map), not as a product gallery.
• 22 Oct, after the itch sale ends: node scripts/set-price.mjs 9 12 --write, run the tests, deploy, and check status shows itch $12, site $12. Compare itch views and purchases for 15 to 22 Oct against the baseline (36 views, 3 downloads, 0 purchases).
• When the boss says pack 2 is submitted: take its press/r20 folder down (back it up to the scratchpad first), deploy, and check for 404. Then pack 3 (RSV Umber) the same way, one at a time, to stay under any weekly cap. The page generator is scratchpad/r20page.py; copy it to app/scripts/roll20-page.py if it gets used again.
• The itch page is fixed as of 15 Oct (no video, 3 screenshots, new sample, see-through line, devlog 1.19). From 16 Oct, watch itch views and purchases daily against the 15 Oct baseline (36 views, 3 downloads, 0 purchases), and look at the itch.io/devlogs feed and the referrers in itch analytics if the API shows them.
• When the boss says "devlog": check /bulkhead/devlog lists it, and that it shows on itch.io/devlogs or the tag pages. With each future release, write the devlog in the same turn and put it next to the upload task, so it doesn't get lost again.
• When the boss says "pictures": load the itch page at phone width with Playwright. Check there is no video, there are 3 screenshots with the ship first, there are 10 tags, and the see-through line is in. Then re-run the itch searches ("deck plan", "starship", "map editor") to see whether the new tags show us.
• After the boss posts task 12: read the thread logged out about 2 h and 24 h later, names masked. Draft answers only, nothing goes out without them. Log points and comments in LEARNED.
• Decided 15 Oct (boss asked how anyone pays): no new free packs or free giveaways. The daily derelict stays as the one free hook. Roll20 packs are the main paid bet (buyers already pay $4.99 there and never see our free things). The $12 editor stays, sold on what the free versions don't do: fleet, adventure PDF, print PDF, .dd2vtt, no watermark. The Owlbear extension stays free, as promised in its own text and to the store reviewer.
• itch is indexed (15 Oct). After the boss uploads 1.19: re-read the itch tags and the description's first lines for itch search, and add the see-through line.
• Check PR 174 in a few days: has the label come off, and has a review been requested?
• Next Owlbear panel change: bump manifest version (1.17.2) so the Rogue Store re-reads store.md.
• Ask the boss to post the reply on PR #174 (needs response label). Text is in the chat at 17:07. Put it first in the batch.
• Next lever is reach for the editor, not more Roll20 products: put this week's Reddit slot in the next batched ask (not stacked), after the GitHub token.
• Ask the boss for a new GitHub token (fine-grained, contents read/write on walkertbrown/bulkhead only), to go into .git-credentials. Then push the local commits.
• bulkhead-1.19.zip is built, passes paid-check and pack-check, and is deployed in the rel folder. Batch ask for the boss: on itch, upload 1.19 and delete 1.18 (or I give them the link). Once the uploads API shows 1.19, add the see-through line to itch-description.html for the boss to paste.
• Roll20 one-ship products: add a theme loop (#style: blueprint, dungeon/parchment, print) to roll20-pack.mjs. That's a scripts-only change, no src. 3 themes x GM/player x grid/gridless = 12 images per deck. A space or transparent background would need a src change: render.ts paints t.bg into the void and also uses it to erase hull edges, so it can't just be skipped. Do that after the daily, with tests.
• Roll20: pack 2 onward should be one ship per product ($4.99), with more variants: a space background, a transparent background, emergency lighting. Before building, check whether roll20-pack.mjs can get those from the editor. Give the boss a paste list of image names and tags in upload order. Ask the boss (batched): can image names and tags on a submitted product still be edited in Item Management?
• (done 13 Oct, pack 1 built) Roll20 first product: ships that aren't free anywhere, as good as the application samples. Render each deck at 140 px per square as JPG: GM labeled and player unlabeled, each gridded and gridless. Check that grid lines bisect walls. List each deck's size in squares for the uploader. Write the listing text with the code-drawn and AI-agent disclosure, and price it at least $4.99. Verify it in a real Roll20 page if the boss can (one ask, once it's finished). Then give the boss one link and paste-ready fields.
• The Roll20 batched ask (ticket #491430) is answered: approved. Drop it from the batch.
• 27 Oct: re-read sittings.sh since 2026-10-04T20:00:00Z for saves per web Generate sitting (13 Oct: 3 of 9), intro-pic sittings (13 Oct: 0) and desktop one-press exits (13 Oct: 2 of 6). Act only once there are 20 or more web sittings.
• Late October (Halloween, 31 Oct): a derelict one-shot angle for a Reddit slot after this week's, once the last post went okay (at most one a week). A GM on r/Starfinder2e wanted a ship for a Halloween one-shot. Draft it from the free adventure pages, facts checked, and give it to the boss as a choice. Landing page: /derelict-one-shot/ (RSV Greyling, horror tone, free 8-page PDF, 5 ft squares), checked live 12 Oct. Earliest slot: about 26 Oct, if a post goes out this week and went okay.
• r/starfinder_rpg DRAFT v2 (12 Oct, after Tech Core). Waiting on the boss to pick it over task 8. Not on /press/. Flair: Ad. Images: upper deck, then lower deck, from public/maps/icv-halcyon-drift/. - Title: "[free] ICV Halcyon Drift, a two deck ship map for tech core starship combat, 5 ft squares, png and foundry walls" - Line 1: "an ai agent built the tool that drew this ship, and it wrote this post. i'm the human who posts it." - Line 2: "tech core says every crew should make a starship map showing where each battle station is (p. 167), so here is a free one." - Line 3: "upper deck has the bridge, crew quarters, galley, medbay, cargo, armoury, engineering and the drive. lower deck is a hold where something has been nesting in the crates, a machine shop, life support with pump 2 failing, and four escape pods, two showing green." - Line 4: "one way to place the stations: pilot's console and scanners on the bridge, generator in engineering, gunnery in the armoury and the cargo hold, drone console in the machine shop downstairs. https://bulkhead.bananafest-destiny.com/starfinder-deck-plans/"; - Line 5: "free and cc0: a png and a .dd2vtt per deck with walls, doors and lights, a print pdf and the room key. https://bulkhead.bananafest-destiny.com/maps/icv-halcyon-drift/"; - Line 6: "no image generator. the decks come from dice tables in code that runs in your browser. the editor has a free demo and a $12 full version, which is why it's flaired ad." - Facts checked 12 Oct: the p. 167 quote and the station names are from AoN (LEARNED, 12 Oct); the stations layout is word for word from the live /starfinder-deck-plans/; the files (2 png, 2 dd2vtt, pdf, key .md) are linked on the live map page; the rooms are from the key; sizes and lights are as checked on 6 Oct. Dropped the Foundry importer and sf2e detail to keep it short.
• 19 Oct: views of /starfinder-deck-plans/ and Starfinder queries in Search Console. If any appear, consider a battle station marker (pilot's console, gunnery, generator) in the editor (src, with full tests).
• About 10 Oct: once Tech Core is out, find whether its starship combat sets a scale or size for the ship battle map, or ships sample maps (reviews, Archives of Nethys). If it does, match /starfinder-deck-plans/ to it. 19 Oct: Search Console queries containing starfinder.
• This week's one Reddit slot, waiting on the boss: task 8 (r/FoundryVTT, already on /press/) or r/starfinder_rpg for Tech Core week (draft in plan/2026-10-05.md Next, verified 6 Oct 01:07). If they pick r/starfinder_rpg, put it on /press/ with one URL and copy-paste text, then read the thread back logged out 24 h later.
• 8 Oct: RUM against the pings again (visits.sh vs events.sh since 5 Oct). If RUM is still 0 while the pings have 10+ views, put one line in the batch: does the Web Analytics dashboard show visits after 4 Oct? Until then, count visits with events.sh.
• 6 Oct after the 11:07 daily: the first daily built by the lights-count script. Read its page's "carries …" line against its .dd2vtt light count.
• Batch ask candidate, after task 3 and task 1 (LEARNED, 5 Oct): FoundryMods. Ask the boss to sign in to foundrymods.com and say whether a module that isn't on foundryvtt.com can be added. If yes, list Bulkhead Deck Plans by its manifest URL. Facts only; it is an alpha site.
• 19 Oct: /foundry/ in Search Console (query,page filtered to foundry, --fresh). Its title changed on 5 Oct to lead with "Free sci-fi starship maps for Foundry VTT v14". It had no rows before the change. Re-inspect it too, so we know Google has crawled it since 5 Oct.
• From the texttotabletop read (LEARNED, 5 Oct): one search, one page, tied to a moment. Candidate for Tech Core week: put "Starfinder 2e" in /starfinder-deck-plans/'s title and h1, which is true (5 ft squares per the 2e Player Core, and the sf2e system was checked on 29 Sep), and say nothing about what Tech Core contains. First, at the 9 Oct inspect, see whether Google has the page at all. If it's still "Discovered", a title change won't matter yet. Don't write a blog-style page per topic until one page shows clicks.
• After r/starfinder_rpg (so the week of 12 Oct at the earliest), and only if task 8 didn't go bad on the AI line: an r/Star_Wars_Maps post (LEARNED, 5 Oct). [DECK PLAN] flair, or [Self Promotion] if it links the $12 page. One derelict's decks as PNGs with the size in the title ([WxH]), like the makers there do. AI line first; the creator's one rule is to say when AI is used. Second line: the maps come from dice tables in the page. Link a free map page, not the store. Not a Star Wars ship, and no Star Wars names. Before writing it, check the sub's sidebar again and look at the last 2 weeks of [DECK PLAN] posts.
• Foundry validation ran on 14.365 because foundry-validate.mjs runs on demo.foundryvtt.com, which is on that build. Stable is 14.368. That isn't ours to move: the demo will catch up. Each Sunday run's log line names the core it used. If it ever goes back to 13.x, the v14 claim on /foundry/ needs a look.
• Owlbear page, from 4 Oct: 7 views of /owlbear-rodeo-dd2vtt/ since 1 Oct 12:10, and 0 obr-copy, 0 obr-rogue. At 20+ views with still 0 copies, make the store link the page's first button above the manifest URL (one press, nothing to paste), then count obr-rogue again.
• r/starfinder_rpg, the week of Tech Core (out 7 Oct). Write it on Tue 6 Oct, after task 8's first day shows how r/FoundryVTT took it, and give it to the boss for Wed 7 or Thu 8. Shape: a gallery post with the Ad flair (the page links the $12 version), three to four deck PNGs at 5 ft squares from one ship, and the first line saying an AI agent made the maps and the post. Second paragraph, from the 30 Sep lessons: the maps come from dice tables in code that run in your browser, with no image model and no server. Never call Generate optional. A free .dd2vtt per deck for Foundry's sf2e system, and a link to /starfinder-deck-plans/. Don't claim Tech Core has starship rules: neither source says so. No staged replies. If task 8 goes negative on the AI line, hold this one and say why. - The ship is chosen (4 Oct): ICV Halcyon Drift. Images: the upper deck (3600x1700, 233 kB) and the lower deck (2700x1700, 151 kB), both from public/maps/icv-halcyon-drift/. The link is /maps/icv-halcyon-drift/, so the post also tests a map page's opens and downloads directly. Tuesday adds only the text. - DRAFT (5 Oct, from the key on disk; Tuesday adjusts it, then re-check every fact against the live page before /press/). Flair: Ad. Images: upper deck, then lower deck. - Title: "[free] ICV Halcyon Drift, a two deck starship on 5 ft squares, png and foundry walls (36x17 and 27x17)" - Body, line 1: "an ai agent built the tool that drew this ship, and it wrote this post. i'm the human who posts it." - Body, line 2: "no image generator here. the decks come from dice tables in code that runs in your browser, laid out room by room on a 5 ft grid." - Body, line 3: "upper deck has the bridge, crew quarters, galley, medbay, cargo, armoury, engineering and the drive. lower deck is a hold where something has been nesting in the crates, a machine shop, life support with pump 2 failing, and four escape pods, two showing green." - Body, line 4: "free and cc0: a png and a .dd2vtt per deck (walls, doors and lights, imports into foundry with the universal battlemap importer, works under the sf2e system), a print pdf and the room key. https://bulkhead.bananafest-destiny.com/maps/icv-halcyon-drift/"; - Body, line 5: "the editor that made it has a free demo and a $12 full version, which is why it's flaired ad." - Facts used: sizes from the page (36x17 upper, 27x17 lower, 100 px per 5 ft square). Rooms are word for word from icv-halcyon-drift-key.md. sf2e is from the 29 Sep check (sf2e 1.5.1, verified on v14). Checked 5 Oct: the PNGs are 3600x1700 and 2700x1700, and the .dd2vtt files say 36x17 and 27x17 at 100 px, with 19 and 8 portals and 6 and 3 lights.
• Batched asks, after task 1 (facts only): did [email removed] ever answer ticket #491430 (Roll20 Marketplace application, 15 Sep)? If it answered, what did it say? If it is silent past 13 Oct (4 weeks), the boss can reply on the ticket. Roll20's forum says that helps. If it was approved, rebuild store/roll20/halcyon-drift-pack.zip from the 1.18 build before uploading, because the current pack was rendered from 1.12.2. Better: build it from a ship that isn't free on /maps/, because Halcyon Drift is CC0 there and is the r/starfinder_rpg ship.
• 11 Oct: /maps/ opens again (events.sh since 1 Oct 12:10, 'view /maps/<slug>/'). It was 0 of 12 on 4 Oct, and the screenshots showed no fault. At 20+ views with 0 opens, try a direct download link on each card.
• 16 Oct, when The Last TTRPG Jam opens (theme on its page): re-read the rules, then make a one-sheet derelict boarding game on A4. The press is app/scripts/one-sheet.mjs (ship json, side-two HTML, out PDF); generate a fresh one-deck derelict on the day. Write all game text on or after 16 Oct; the jam says no pre-released content. Side one is a Bulkhead-generated derelict GM map with its trail. Side two is rules, a d6 of what goes wrong, a clock and the theme. The first line says an AI agent made it, and the map line credits Bulkhead. CC0, free. Only when the PDF is finished and checked, give the boss one /press/ step: a new free itch project and the jam submit. Next jam re-check is 17 Oct.
• When the boss says "pictures" or task 1 is done: fetch the itch page, check the screenshot order, that the video is gone and the tags, and that the demo file is the 816 kB examples zip (by size; never print md5s).
• 9 Oct inspect, also: /derelict-one-shot/ (unknown on 3 Oct; sitemap resubmitted and Bing-submitted 09:2x) and the four still-Discovered landing pages. On 3 Oct /deck-plan-generator/ had moved to indexed (crawled 1 Oct).
• 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.
• 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.
  • (Dropped 5 Oct, 08:2x: Scene Importer's own parser, run in node on our zip, imports 0 scenes because v11+ packs keep walls as separate keys. See LEARNED. Not a room test.)
• 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.
• /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 funnel, 4 Oct: bash scripts/installs.sh 2026-09-20T00:00:00Z against 34 listing / 25 manifest / 10 icon / 6 panel (3 Oct). If the panel count rises while the listing count holds, more people who add Bulkhead are finding it.
• 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, run release.mjs 1.18 (it runs pack-check), --fix stale pack PDFs, re-make the Greyling by hand if it is flagged, bump ?v= on /press/ and itch-description, deploy, read every changed file back. Since 19:2x on 3 Oct: 1.18 zip ?v=1004b (since 21:2x on 4 Oct, with the short-phone card fix and the Global Illumination README lines), pack ?v=1018 (since 20:2x), examples zip and Greyling ?v=1004. 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 now the file swap (the switch went live on 3 Oct). When status shows "itch sells the current" ok for both files, take the paid zips off /press/, drop the pack from the zip check, and paste the 1.18 devlog (store/DEVLOG-1.18.md) as the next ask.

01:07: Derelict opens on a title card with the painted cover

• Derelict now opens on a title card: the painted cover, the ship's name, one paragraph of rules, par, and a "Board the ship" button. Enter or Space also boards. Arrow keys do nothing while the card is up, so no air is spent before you start. Resumed runs and finished days skip the card.
• Checked with Playwright on desktop (1280x800) and Pixel 7. The card fits both, and Enter hides it.
• tsc clean. vitest 101/101.
• Rebuilt the itch zip (141441 bytes, was 127158; the cover is now bundled) and deployed. The live /derelict/ page has "Board the ship", the live bundle has the title code, the cover webp returns 200, and the live zip size matches the local one.
• Finished 01:17

01:17: Read the jam page before it opens for the theme and rules

• Jam page read at about 01:20Z: the theme is still "???" and will be announced when submissions open (03:00Z). It is "a suggestion, not a hard requirement." Nothing has changed from the 16 Oct read: free, playable in the browser, heavily AI-assisted, and a continued project is allowed if most of it is new. 228 joined so far (AI Jam 4 had 248 joined and 126 entries).
• Fixed two stale lines on /press/derelict: the zip is about 140 KB (it said 40 KB), and step 3 now says the game opens on the painting with a "Board the ship" button. Deployed. Live page checked, and the live zip is still 141441 bytes.
• The title card fits itch's 820x760 embed: the box runs from 25 to 735 px and the button ends at 713 px.
• Next: read the theme after 03:00Z.
• Finished 01:18

01:18: Draft a how-it-was-made devlog for the jam's AI Usage vote

• Added step 5 to /press/derelict: a devlog title and text with copy buttons, for the boss to post on the Derelict itch page once it's public.
• What it covers: - It says in its first lines that an AI agent wrote it. - The build: 15 to 16 Oct, about 1,100 lines of game TypeScript (wc: 1120), ships from Bulkhead's generator, deterministic daily seed, 24 game tests. - The bot playtest and the agent's own "the loop is thin" verdict, quoted from actual/2026-10-16 18:22. - The five design changes made before any art. - The images: 10 gpt-image-1 images including the unused test sheet, about $0.61 (0.04 + 0.57), written as "about 60 cents". The real style line and one real room prompt, both recovered word for word from this session's commands. - The sound: Web Audio, about 90 lines (sound.ts is 86). - Three lessons.
• Kept off the page: itch's exact devlog menu names and a post type, which I couldn't check.
• No em-dashes. Deployed, and the live page has the text.
• Finished 01:19

03:03: Read the jam theme now that submissions are open

• At 03:03Z the theme was still "???" on the jam page. There were 3 entries in entries.json.
• Found a host ruling in the community tab (in LEARNED, 17 Oct): a game started before the jam needs "50% new content during the jam". Derelict was built 15 to 16 Oct, so it doesn't qualify as it is.
• Checked: Derelict isn't entered (not in entries.json) and bananafestdestiny.itch.io/derelict is a 404, so nothing was submitted.
• /press/derelict step 4 now says HOLD, with the host's quote. Steps 1 to 3 (making the itch page) are still fine. Step 5 (the devlog) is marked for a rewrite, because it says the game was built on 15 and 16 Oct. Deployed and checked live.
• Finished 03:03

03:07: Jam half 1, a ship that hums: a generative ambient score for Derelict

• Added a generative score to Derelict, at the end of src/game/sound.ts: - It's seeded from the ship's name, which picks the key (D2 to G#2), the mode (aeolian, phrygian or dorian), a four-chord walk and the echo time. So today's ship sounds the same for everyone. - The pad is detuned saws through a lowpass that opens as the air drops; hud() sends 1 - air/maxAir. - High pings go through a long echo, hull groans come every 14 to 30 s and more often under stress, and a heartbeat starts below a quarter of the air. - It fades in over 5 s, stops with the sound button and comes back with it, and stops at the end of the run along with the hull drone. - New sfx.board: a hiss and thud on "Board the ship". That click is the browser gesture that starts the audio.
• Checked in Chromium: not playing before boarding, playing after, off and on with the button, no page or console errors over 12 s at high tension. I can't listen to it myself, so the mix levels are only reasoned from the existing gains (hum 0.05, pad bus 0.03).
• Tests 101/101, tsc clean.
• Itch zip rebuilt (142432 bytes) and deployed. The live bundle has the score code, and the live zip size matches.
• New app/store/DERELICT-JAM-NEW.md: a dated list of what's made in the jam window, for the devlog and the boss. This score is item 1.
• Finished 03:17

04:04: Read the jam theme, now that the page has changed

• The theme is up on the jam page (read at about 04:05Z): "Theme: 🔥TORCH🔥". The page still says it's "a suggestion, not a hard requirement."
• My watcher missed it because it matched "theme: " and the text after it starts with an emoji. It printed an empty line, which is why I read the page by hand.
• How Derelict takes it, as the main new mechanic for the jam's new half: a salvager's cutting torch. - With limited fuel, you can cut a sealed door open (free of the SEALED cost) or cut straight through a wall into the next room, making your own shortcut at an air cost. - The torch is also your light: the score's tension and the drawing get a lit circle around you. - Engine change, with replay kept deterministic: a new move letter for a cut. - Design it next with numbers from the bot, so the torch is a real choice (fuel for maybe 2 or 3 cuts), not a free pass.
• Finished 04:04

04:04: Jam half 2, the cutting torch in the engine

• engine.ts: a cutting torch, with TORCH = 3 charges and CUT = 2 air. - canCut(side) is true for a wall, or a jammed door, with ship's floor behind it; never out into space. - cut(side) spends a charge, opens the edge for good (it then costs a plain step in both directions), steps through for 1 + CUT air, and records "T<side>" in moves. - A sealed room entered through a cut isn't charged SEALED, and its message says so. - New event { t: 'cut', left }. stepAt counts the cuts, so tap routes, airOut and airOf all use the gaps. - replay() reads T<side>. record.ts now accepts T<side> in saved moves; without that, a reload would have dropped a run that had a cut.
• Par is unchanged and doesn't use the torch. Whether the torch makes par too easy is for the bot to measure once the UI is in.
• 3 new tests: cut cost, charge, gap and an exact replay on over 10 ships; no cut into space and charges run out; a sealed room cut into charges no seal. All 104 pass, tsc clean.
• Not deployed: there's no UI for it yet.
• Finished 04:13

04:13: Jam half 3, the torch in your hands: controls, light and sound

• The torch UI shipped: T or the Torch button lights it, and the next arrow, pad press or tap cuts. Cuttable walls glow, the gaps stay drawn, a torchlight circle follows you, and there are sounds for ignite, cut and boarding.
• Playwright on desktop and Pixel 7 with no page errors. Desktop: a cut into a sealed crew quarters cost 3 air and no seal. Phone: a pad cut cost 3 air and left torch at 2/3. The screenshots read fine.
• 104/104 tests pass and tsc is clean. Deployed; the live bundle has "Cut which way", and the live itch zip matches the local one at 143961 bytes.
• Added to DERELICT-JAM-NEW.md. Not done yet: the bot check on whether par still means something with the torch. That's next.
• Finished 04:24

04:24: Does par still mean something with the torch

• I didn't teach the play bot to cut. Instead I bounded the torch from above: a throwaway test re-ran par's greedy tour with unlimited cuts at 3 air each, over 48 ships (12 each of shuttle, corvette, freighter and station, derelict).
• Par rises on 14 of 48 ships, and the mean goes from 370 to 391 (+6%). Item distance from the airlock barely moves (median 0, p90 1, max 13), so the gain is shorter legs between rooms. Stations never change. A few ships jump: shuttle 10 from 245 to 400, shuttle 12 from 255 to 425, corvette 6 from 265 to 380, freighter 12 from 270 to 385.
• The player gets 3 cuts, not unlimited, so the real gain is below this.
• Decision: par stays as it is. On about 70% of ships the torch doesn't move it. On the rest, cutting well is how you beat par, which is what a theme mechanic should do. Changing parFor would also move par on days already posted and recorded.
• If players start beating par by miles, revisit it with a cut-aware par.
• Test file deleted; nothing in the game changed.
• Finished 04:25

05:07: Survivor in the engine, with tests

• The engine has a survivor: placeSurvivor() picks one for about two ships in three from a hash of the ship's name. They go in a sealed room if the ship has one, else in the farther half of the rooms. Never the boarding room, never on an item, always reachable.
• Walking onto them sets with=true and raises a 'survivor' event. While they follow, every move costs FOLLOW (1) more, and airOut and airOf count it too, so the "to get out" figure stays honest. Getting out together adds RESCUE (75) to worth and score.
• 2 new tests: placement over 60 ships (rate between 45% and 90%, at least one in a sealed room, deterministic), and a full rescue with the follow cost, the bonus and an exact replay. 106/106 pass, tsc clean.
• The daily at 11:07 deploys whatever is in the tree. So the page sets Game.survivors = false until the screen draws the survivor and says their line; otherwise a survivor would be invisible and cost air. Not deployed by hand; the page is unchanged.
• Next: the screen half. Draw them in their room and one step behind you, give them their line, show them in the HUD, put a rescue line in the share text and the story, and only then switch them on.
• Finished 05:24

07:07: Survivor on the screen, then switch it on

• The survivor is on screen and switched on. - The intro names the distress signal's room, and a ♥ DISTRESS SIGNAL tag sits over the room until you've seen inside. - Then there's a glowing figure tagged SURVIVOR +75. Once they follow, they're drawn one step behind you. - Meeting them plays a knock-knock sound and shows their name and line. The HUD shows "<name> with you". - The end screen title, the score breakdown, the share line ("1 rescued") and the story all cover it.
• Playwright on desktop and Pixel 7, two different practice ships each run: found, followed, brought out, no page errors. A step with them cost one more air.
• Two fixes from that run: - A smoke event on the meeting step had replaced the meeting text; the survivor now counts as news, so decay is added after it. - The story missed a comma ("Lev Petrov, the comms officer came out").
• 106/106 tests pass and tsc is clean. Deployed; the live bundle has "DISTRESS SIGNAL", and the live itch zip matches the local one at 145534 bytes.
• Edge case: someone mid-run on today's ship who reloads gets a survivor placed. If their saved walk crosses that square, the replayed air will differ. That's rare and only lasts until 11:07.
• Finished 07:17

08:21: A daily leaderboard for Derelict

• The boss asked for it. Their words and the plan answer (Workers Paid) are in FACTS.md.
• Built: POST /api/board/<day> takes {player, moves}. The worker fetches /daily/<day>/ship.bulkhead.json from the static assets, replays the moves (judge() in src/game/board.ts), and stores what the replay scores. - Storage is a Durable Object per day with SQLite. - Only the current daily ship counts (today or yesterday UTC). - The first scoring run per player id counts, and the same walk under another id is refused. - Runs that score 0 aren't kept, so "step out of the airlock" can't pad the board. - Callsigns come from the id; nobody types a name. - The worker sends CORS headers so the itch build can use it too.
• D1 was blocked for the deploy token (error 10000), so I used a Durable Object; that went into LEARNED.
• Tested locally with wrangler dev and Playwright on desktop and Pixel 7: two real daily runs. The server scored them 40 and 15, the same as the page, ranked them 1st and 2nd, and the board came back after a reload. No page errors.
• Live: the deploy shows the BOARD Durable Object; the GETs answer {"top":[],"count":0}; a junk run "N" stays off; OPTIONS gives 204 with allow-origin *; video Range still gives 206; the itch zip matches at 146297 bytes. 109/109 tests pass, tsc is clean.
• Finished 08:34

09:07: Jam half 6, fire: the ship fights back with flame

• Fire is in. One decay in five, where smoke had two, is now a fire in a room near you, costing 2 more air a step there. Each later decay spreads a fire on your deck into a room beside it, never yours.
• First I tried spreading only through doors, but rooms mostly open onto corridors, so it spread just 5 times in 144 decays. Spreading to any room sharing a wall or a door gives 20+.
• The route search, airOut and airOf all use one new extra() cost: fire 2, thick or smoke 1.
• On screen: a patchy orange glow with flames, a FIRE +2 A STEP tag, a whoomph-and-crackle sound, and "Fire." / "The fire spreads into ..." lines. The intro now says fires break out. A Playwright check with a fire set beside the airlock showed it and threw no page errors.
• Tests are 110/110 across 6 files, and tsc is clean.
• Not deployed. The 11:07 daily builds the working tree and goes live with the new ship, so nobody's run changes rules halfway. The board also accepts yesterday's day, so a 16 Oct run submitted after 11:07 is replayed under the new rules and may be turned away. Few players, so I accept that.
• Finished 09:22

10:11: Jam half 7, new ways to die: what killed you, and the fire can reach the survivor

• The engine has a new death getter that says what killed you from where your air ran out: fire, smoke, a hazard, vacuum (a breach square) or plain air. A fire or spread that lands on the room of a survivor you haven't reached sets lost on them, and the decay event carries them so the page can say it. A lost survivor can't be picked up.
• The page gives each cause its own end title, story line and share mark (🔥 💨 ☣ 🕳). A lost survivor gets the line "The distress signal stops. X was in there.", a grey ♡ SIGNAL LOST tag, and a story line saying the fire got there first.
• Playwright: I set a room on fire, walked in on 1 air and died there. The page showed "The fire took you. The ship keeps you.", the share showed "lost aboard 🔥", and the story had both lines. No page errors.
• Tests are 112/112 across 6 files, and tsc is clean.
• Not deployed. It goes live with fire in the 11:07 daily.
• Finished 10:21

10:21: Jam half 8: new screenshots for the press page

• Three new screenshots, all genuine play on practice ships with the jam rules: - desk-torch.png: a real cut into a sealed cargo hold that holds the survivor, a log and salvage, with "You cut through" and "the seal cost you nothing" in the card. - desk-fire.png: a fire that broke out on its own during a scripted walk, with the "Fire." line and the FIRE +2 A STEP tag. - desk-survivor.png: the moment Hana Ito joins you, with another genuine fire burning in the next room.
• They are in app/public/press/derelict/ and store/itch-derelict/. The press page lists them first, numbered 1 to 7.
• The itch description, on both the press page and in ITCH-DERELICT.md, now covers the torch, fire, the survivor, the daily board and "the end tells you what got you".
• Two torch spots were weak (one small glowing wall) before I made the shot a real cut.
• Not deployed. The 11:07 daily deploys the working tree, which includes the press page. I'll check the live files after.
• Finished 10:23

10:24: Measure the jam half: how much of Derelict was made since 17 Oct 03:00Z

• Base: the last commit before 17 Oct 03:00Z, the devlog commit from 16 Oct. The game code had 2053 lines then and has 2742 now: 738 added and 49 removed, about 27% new. Written into DERELICT-JAM-NEW.md.
• Old still outweighs new about 2.8 to 1 by lines. The about-24-Oct target needs roughly another 1300 lines of new game, or a case that the features list itself is the content. I'd rather earn it in code.
• Finished 10:24

11:07: Run the 11:07 daily, check it, then start Blackout days

• Crons are paused, so I ran daily-host.sh by hand at 11:07. It exited 0. Today's ship is the ICV Ironbark, and meta.json has a Bluesky URL for today.
• The first npm run status failed 2 of 31: "itch $?" on the price checks, a read of the itch page that came back without the price. A re-run straight after was all 31 clear, so it was transient.
• Live checks: - The /derelict/ bundle has "The fire took you", "SIGNAL LOST" and "fire spreads". - desk-torch, desk-fire and desk-survivor all return 200 at the same sizes as local. - /press/derelict has the new description. - /api/board/2026-10-17 answers an empty board, and today's ship.bulkhead.json returns 200.
• The itch zip was still the pre-fire game, so I rebuilt it (147400 bytes, its JS has the fire death) and deployed. The live size matches.
• Finished 11:13
• Then I started Blackout days, as "ship conditions" in the engine: - The condition comes from the ship's name, one ship in six each for blackout, reactor and stress. - Blackout reveal stops at 3 squares and no longer lights whole rooms. - Reactor uses a decay table that is 3 parts in 5 fire. Stress decays every 7 steps. - Game.conditions is off by default in the engine itself, so the page and the board's replay can't disagree. The tests switch it on.
• Tests are 114/114. Next: draw the conditions in the page, then switch them on with a daily ship change.
• Finished 11:23
• Conditions drawn in the page (uncommitted until now): HUD ship name gets " · BLACKOUT" / " · REACTOR FIRE" / " · HULL STRESS", the title card and the boarding message explain it in one line, the share line names it, and a blackout darkens everything beyond LIGHT squares from you. Checked on three practice ships with a dev-only ?cond=1 switch (no page errors, screenshots looked right).
• tsc clean, 114/114 tests pass. Game.conditions stays false in the engine; it goes true with the 18 Oct daily so the page and the board's replay change on the same ship.
• Finished 11:33

11:44: Next jam piece: one new mechanic in rules, page and tests

• Built oxygen canisters: engine (placeCanisters, Canister, a 'canister' event, fire blows one), page (cyan cylinder, O₂ +15 tag, O₂ BLOWN, hiss sound, legend, intro line, pickup message saying how much was wasted), 2 new tests.
• First placement (middle half by distance) put them 4 to 6 steps from the airlock on 3 of 5 practice ships, which is no choice at all; moved to the farther half (9 to 25 steps on the next run).
• Found and fixed: a decay on the same step replaced the canister message. A test walk met a fire that blew the canister on the way, so the test skips that case (it shows the blow-up works in real play).
• tsc clean, 116/116 tests. Game.canisters stays false; switch it on with Game.conditions at the 18 Oct daily.
• Finished 12:03