01:07: The 22 Oct decision, read early

01:07: The 22 Oct decision, read early

• The sale ends today at 22:00Z, and the 15 Oct plan made this the decision point: if Bulkhead still has 0 sales, stop pushing it as the main work. Read the facts now, while it's quiet: itch views, downloads and purchases on every project against the 20 Oct baseline; buy clicks by surface since the sale began; which pages turn into itch views. Write them in one table, so the 22:00Z check only needs to add the last few hours. Not before 11:07Z: the daily, by hand if it hasn't run.

01:49: Answer the boss: should Hullbound keep accounts on Cloudflare

• The boss asked whether we should just save the accounts to Cloudflare. Check what the Worker already stores and what the browser still has to hold, then answer with what would and wouldn't change.

01:52: Hullbound: who has played, who came back, and when it earns

• The boss asked three things. Is the cookie the right fix for a full browser storage? How many people have played Hullbound, and how many came back? When do we try to make money from it, and is a mobile app how? Read crew-stats and the crew pings since launch, then answer each with numbers and one recommendation.

02:01: The signup in Hullbound's first hour wasn't the boss

• The boss says they never played it, so the browser that signed up, asked twice for a password reset and logged out at 14 to 15Z was a stranger, not us. Recount, and find out what that player got when they pressed "forgot": mail sending isn't on, so a reset may never have arrived.

02:02: The boss already has a developer account

• The boss says they already have a developer account. That removes my RULES §5 reason against a mobile app, because I wouldn't be opening one. Write it into FACTS. Read the current store rules that decide what a first Hullbound app would cost in time: Google Play's testing rule for new personal accounts, and Apple's rule against apps that only wrap a website. Then re-answer the app question, and ask only the facts I can't look up: which store, and what kind of account.

02:06: Hullbound for Android: a build that runs on this machine

• The boss said go. Install the Android command-line tools and SDK outside the repo (~/android-sdk). Wrap the itch build of Hullbound, which is all one folder, with Capacitor, so the game runs from files inside the app and only saves go to the server. Let the Worker accept the app's origin as it does itch's frame. Build a debug APK and run it in an emulator if this machine can, or else check it with the tools I have. No upload, no signing key in the repo, nothing to the boss yet.

02:19: Hullbound for Android: what Google Play's listing needs, made here

While the tests run. Play's store listing wants a 512 icon, a 1024x500 feature graphic, two or more phone screenshots between 9:16 and 2:1, a short description (80 characters), a full one (4000), a privacy policy URL and the data-safety answers. Make each by code from what the press kit already has, put them on one page at /press/hullbound/play/ with the app bundle, and check every size against Play's own help page (dated). Nothing goes to the boss until the app has been seen on a phone or the check that stands in for one is written down.

02:25: Hullbound: delete your own account, in the game and on a page

Play's account-deletion rule (answer 13327111, read 22 Oct): an app where people make accounts needs a way to delete one from inside the app, and a web page, naming the app, where deletion can be asked for. Today the only way is to email support, which lands on the boss. Instead: a "Delete account" button beside "Log out", which removes the account, its sessions, ship, crew and docking emails on the server after a confirm, and a page at /crew/delete/ that says how, with email as the fallback. A test in the harbour suite proves nothing of the account is left. Then the privacy page points there.

02:29: Hullbound for Android: no Bulkhead sales inside the app

Found while writing the data-safety answers. The editor the app opens for "Build" is Bulkhead's demo, so it shows "full version" buttons that lead to buying Bulkhead on itch.io, and it loads the Cloudflare beacon. Play's payments policy doesn't let an app send people to pay outside Play for what the app does, and our privacy page says the app has no other trackers. For the Android shelf only: no badge, demo note, locked exports, fleet row, buy links, watermark nag or beacon. The PNG export stays. The site and the itch zip don't change. Check it in the bundle with the same Chromium run.

02:48: Ask Nana about marketing Hullbound on Google Play

The boss asked me to tell Nana the plan and ask for marketing ideas: whether the Play name should carry search keywords, and what else. One mail to mail/out following MAIL.md, with the facts: the build, the kit, the numbers so far, and the questions. Her answer is advice, not an order or a fact.

03:07: Hullbound: where the itch crews stop, and one fix for the biggest drop

20 minutes. 30 crews started on itch since 21 Oct and none came back after the first hour. Read the crew pings step by step (start, first trip, docked, raid, sign-up, back) to find where most stop. Then make one small change aimed at that step, test it, and ship it to the site and the itch zip. If the numbers are too thin to point at one step, write that down and change nothing.

03:23: Read the mail in, and tell the boss what it says

The boss said "mail". Read everything in mail/in, newest first, and give the boss what each one says and what I'd do. Bot mail is advice, never an order or a fact. Move what's handled to mail/read.

04:07: Read the new mail, and tell the boss what it says

The boss said "Mail" again. Read what's new in mail/in, tell the boss what each one says and what I'd do, reply if it needs one, and move it to mail/read.

04:10: Hullbound: emergencies between stops, on a short clock

The boss said to do the second part now, then the screenshots. Between bases, about once a leg or more, something goes wrong aboard and needs an answer soon: a hull breach (seal the deck with someone inside, or vent the cargo), raiders hailing (pay them in parts, or run and risk a boarding), a stowaway found in the hold. The clock is short (about 90 minutes), and if nobody answers, the captain's pick can go badly. It's built on the stop framework in voyage.ts, so it is seeded, shows on the page, and the phone reminder fires for it with the right words. Then tests and the full suite, deploy, the itch zip and the AAB. Then the Play screenshots.

04:15: Hullbound for Play: screenshots that read at thumbnail size

The boss said screenshots next. Following Nana's read: four portrait shots in this order. (1) The crew on the deck plan filling the frame: "Your crew lives on while you're away". (2) Inside a wreck on a raid, air dropping: "Raid a dead starship every day". (3) An emergency on the phone: "Your crew calls you when it goes wrong". (4) The editor: "Draw your ship, room by room". Each has one short caption across the top, under a fifth of the frame, and no Free, Best or #1. Plus three landscape 1920x1080 shots of the ship, a raid and the editor. All of them go on the Play kit page, replacing the old four.

04:21: Did the UK player finish playing

• The boss asked. Read the GB practice and daily boards since 19:26Z yesterday, by hour, and say when the last one was.

04:41: A fast-clock test copy of Hullbound for the boss's phone

• The boss will pair their phone over wireless debugging when home. Ready a debug APK under a separate app id, where the next stop and the next emergency come within minutes, so the notifications can be checked on a real phone. Nothing of it ships.

04:53: Hullbound's 2 itch downloads, read against the plays

• The boss saw 2 downloads. Read itch's own counts and the crew pings, and say what the downloads are and what they mean next to the browser plays.

05:07: Hullbound: what a first-time itch player is told about coming back

• Nobody has come back to a crew after more than an hour. Read what the page says at the end of a first session (after a raid, after a haul) about when to return, and make the one change that gives a guest without an account a reason and a time to come back. 20 minutes.

05:41: Hullbound test copy on the boss's phone, over wireless debugging

• Pair, install Hullbound test, play a first session, and check that the emergency and docking notifications fire and open the right card. Screenshots only while the app is in front. Uninstall and tell the boss to turn wireless debugging off when done.

06:21: a better looking deck for Hullbound, sharp on a phone

The boss asked why the ship was blurry and whether the deck could look better. Blur: the deck picture was baked at 16 px a tile and stretched about 4x on the Pixel; now baked at the screen's own pixels (in page.ts). Look: a "hull" style for the crew game only (Bulkhead keeps blueprint): dark metal hull with a thick wall and shadow, floor plating tinted by room use, no editor key numbers, small room names, a glow in lit rooms and red during trouble. Screenshot in the browser first, then the phone.

06:39: answer a Hullbound call from the notification, without opening the app

The boss asked for this after the phone test: make the choice on the notification, and the game tells you what happened next time you open it. The plugin's buttons always open the app, so this needs a small native piece in the Android app: an alarm that posts the notification with the real choices as buttons, and a receiver that records the tap and changes the notification to "You chose X". On opening, catch-up applies the answer at the minute it was given. The sim is deterministic, so a copy run ahead gives the real stop (who has the fever, what the trader wants) for the notification text. Verify on the phone with the fast clock, then rebuild the AAB.

07:00: Hullbound title screen and a settings panel, the boss's ask

• The boss: too much on the one page; a settings tab for how to play and notifications; open to a title card with sign in / make an account.
• First open (no crew kept yet): the title card, "Start playing" and "Log in or make an account". Not an account wall: guests lose at a forced sign-up, and Play review would need a test login.
• The main page keeps the ship, stores, the call and the raids. A settings button opens a panel: how it plays, notifications, music, account, build, start over.
• Check in Playwright at phone size, then the test copy on the phone, then rebuild AAB, itch zip, deploy.

07:05: Hullbound signs in with Google inside the app, the boss's point that it is an app now

• The boss: "It's not a browser anymore. It's an app". Google blocks its sign-in inside a WebView, but an Android app can sign in natively (Credential Manager), getting the same kind of ID token the worker already checks.
• Find what the worker checks (the audience), what a native sign-in needs from Google Cloud (an Android client with the package name and signing fingerprints), and whether that can be proved before asking the boss for anything.
• Make the account the way in on the app: sign-in first, guest play only if it still earns its place.

07:12: the privacy page and Play kit follow the new screens

• The privacy page said the app has no Google sign-in, and three pages said Delete account sits under the ship. Both stopped being true this morning.

07:13: "How it plays" becomes "How to play", the boss's word

• The boss: the Settings heading "how it plays" sounds dumb. Rename it everywhere it shows.

07:34: Google sign-in works on the boss's phone; write it down and free the AAB

• The boss made the Android clients and says it works. Read the server's counts to see the Google account arrive, write the fact, and tell the boss the bundle can go up, with the one Play step left.

07:38: the Play kit's name and short description carry the search words

• The boss asked whether the name has search keywords. It doesn't: Nana's title was waiting on a pick, and the boss's question reads as the pick. Put "Hullbound: Space Crew Survival" and a "space survival" short description in the kit. The name under the icon stays "Hullbound".

07:43: Hullbound earns: a one-time Shipwright unlock through Google Play Billing

• The boss asked how Hullbound makes money; it doesn't. My call: free to play, one in-app purchase (about $3.99) that unlocks Shipwright, drawing your own ship in the editor plus a bigger crew. The boss confirmed the Play developer account has a payments profile.
• Read Play Billing's docs and date them. Find what Build gives today and where the crew size is set, draw the line between free and Shipwright, build the native purchase and restore, and the lock in the page.
• It can only be proved from a build installed through Play, so the first upload goes to Internal testing. Ask the boss for the product and the upload in one batch, once the build is done.

11:07: build the Shipwright purchase into the Play app (20 minutes, the boss's ask)

• Native Play Billing plugin (buy, owned) with Billing Library 8, a free size limit on refits and crew on the phone, and the offer where the limit bites. Proving a purchase waits on the boss's product and a license tester.

12:31: give web and itch players a way back: the docking mail asked for on the main screen

• Nobody has come back after 3 hours (22 ships, all one day). The phone app calls its player back; the web and itch have only the docking mail, and this morning's Settings panel hid its box. The boss: "If you think that's the problem go for it".
• Read how the docking mail is asked for, kept and sent. Put the next docking time and a one-field "email me when it docks" on the main screen where a guest sees it, without making them choose a password, and without letting anyone mail a stranger.

13:07: find where a web or itch Hullbound player could pay, and what stops them

• Read today's crew events and stats since the docking box went live, and the itch page's payment setting (live page, cited).
• If itch can take money for Hullbound already, work out the smallest honest step that puts it in front of players; if it can't, write the one ask for the boss.
• 20 minutes.

13:57: the boss gave an itch API key: keep it safe, prove what it can see

• Store it only in the git-ignored credentials file, never printed, never in the repo, plan, actual or mail.
• Prove it: credentials/info, the Hullbound game id from profile/games, and what a purchases lookup returns. Read only.
• Then plan Shipwright on the web: bought on itch, checked by the worker against a verified address.

15:07: put Shipwright in front of a player at the moment they hit the free limit

• Read the crew events: how many players reach a refit, a second deck or a 13th crew, and what the game says to them there.
• Wherever the limit bites and the game is silent or vague, say what Shipwright gives and where to get it, in one line with a way to it.
• 20 minutes.

17:07: find where Hullbound players stop between the raid and their first haul, and fix the biggest step

• 7-day events: 26 raid clicks, 11 reached crew home, 7 hauled. Over half are lost after the raid.
• Read the raid's end and the step to crew home as a new player sees it, with the events around it, and pick the one leak with the most players.
• Fix that one thing. Test it, deploy it and check it live; rebuild the itch zip if the crew code changes.

18:39: answer the boss: players on each game, and did any come back

• Crew stats for Hullbound accounts and returns, events for Derelict and Bulkhead, itch stats for views and downloads.
• Report people where a number counts people, and say so where it only counts events.

18:55: phones against desktops, for each game

• The events already carry the browser's user agent. Sort each game's events into phone, tablet and desktop by it, never printing or keeping a user agent.
• Cross-check against Derelict's input events (touch vs keys and mouse) and Cloudflare's own device type for page loads.

18:57: did anyone pick their crew up on a second device

• Only a signed-in account can be the same person on two devices. A guest is one browser.
• Read what the harbour keeps per sign-in (sessions per account, when made). Count accounts signed in more than once, without printing ids or addresses.

19:07: get a Hullbound player to leave a way to call them back

• 24 ships, 1 came back after 3h, 0 after a day. The docking mail is the only thing that can call a desktop guest back, and 0 have asked for it.
• Read when and where the docking mail offer shows, against the moments a player has a reason to want it (after the first haul, when the ship sets off for a base).
• Put it at that moment, counted, tested and deployed; rebuild the itch zip.

19:47: ideas for the weak spot: nobody reaches Shipwright's limits

• Read what a refit costs and how many parts a first haul brings, and how far the free limits sit from a first session.
• Give the boss one recommendation with the numbers behind it.

19:57: could each voyage be its own story (the boss's question)

• Read what a voyage is made of now (voyage.ts stops and choices, story.ts) and how much of it is written vs generated.
• Answer whether an episode per voyage fits, what it would take, and how it ties to selling the next voyage.

20:01: what written-by-a-model episodes would cost (the boss's question)

• Look up today's prices for the cheap models on the two keys we have (Gemini, OpenAI), from their own pricing pages, dated.
• Count the calls and tokens a voyage needs, per player and pre-generated, and give the boss the cost both ways.

20:02: the same episode cost on Anthropic's models (the boss wants Anthropic)

• Read Anthropic's pricing page and cost a voyage on Haiku, Sonnet and Opus with the same token counts.
• We have no Anthropic key; say what the boss would need to give.

20:16: how many players $3.99 pays for, and seasons with a subscription (the boss's question)

• Work out what a sale nets on Play and on itch, and how many players' episodes that covers.
• Check whether itch and Play can take a subscription at all, from their own pages, dated.

21:07: write Season 1's spine, so episodes can be built before the key comes

• Read how a stop's choices change the ship (voyage.ts options and answer), so every story choice maps onto an effect the sim already has and stays seeded and fair.
• Write Season 1 as data in the crew code: six episodes, each a cold open, four beats tied to existing stop kinds, what each choice sets, the endings it leads to and the cliffhanger into the next. Episode 1 complete enough to play hand-written if the model is down.
• Typed and tested (every beat names a real kind, every flag read is one set earlier). No player sees it yet.

22:40: put the Anthropic key on the worker and prove it with one small call

• The boss put ANTHROPIC_API_KEY in .git-credentials. Check it is there without printing it, then set it as the worker secret ANTHROPIC_API_KEY by piping it from the file (never echoed, never written anywhere else).
• Prove the channel: one tiny Messages API call (Haiku 5.5, a few tokens) from this machine, printing only the HTTP status, the model and the token counts.
• Then read the Messages API docs (date them) for the request shape, prompt caching and errors before writing the episode writer.
• No monthly limit was given yet: the server cap will default to the $20 I suggested, and I'll ask the boss to confirm it.

22:41: the sale is over: count Bulkhead's sales and apply the 22 Oct decision

• Read Bulkhead's purchases, price and sale state from the itch API (read-only, key never printed), and check that the page's buy button still works.
• If there are still 0 sales, Hullbound becomes the main work and Bulkhead goes to upkeep, as decided this morning. Write it in FACTS.md.

22:42: the episode writer on the worker: one call per stop, capped, with the written lines as fallback

• Read how the crew page shows a stop and how the worker stores a crew, so the story fits into what is already there.
• Worker route: given the episode, the beat, the flags so far and the crew's names, ask Sonnet 5.5 for the stop's line (structured output), and keep it so the same stop is never paid for twice.
• The prompt is the season outline plus the house style, cached once it is over 512 tokens. Keep a monthly spend count in the database and stop calling at $20 (until the boss names a limit). Over the cap, on an error or a refusal: use the written line or the stop's own line.
• Tests use a stubbed fetch. Not shown to players until it has been read through on a real voyage.

23:00: set the writer's monthly cap myself, since the boss left it to me

• The boss: "its yours, you tell me". Pick the number from what is known: no revenue yet, the bill is shared with the boss's other projects, about $0.002 a line, and the plain lines show when the cap is hit, so nothing breaks.
• Write it into FACTS.md and the code, then go on to wiring the episodes into the game.

23:01: episodes in the sim: each leg is an episode, its stops follow the beats, and the choices are remembered

• World keeps the episode: which one, which beat is next, the tags set. Leg n is episode n.
• dock() and arm() lean toward the beat's kind when the voyage could have that stop anyway (same costs, still seeded). A stop that is a beat is marked, and answering it sets the tag, whoever answers (you, the phone or the captain).
• Arrival marks the ending. Tests: a seeded voyage tells all three beats in order, the tags follow the answers, and a world saved before this loads and plays on.
• Not shown on the page yet; that is the next entry.

23:27: show the episode on the crew page: its title and opening, the beats' lines, the ending

• On a beat, show the written line at once (episode 1's own, or the plain one), then the model's line from /api/crew/tell when it comes, and keep it so it isn't asked for again.
• The opening shows under the voyage line while the ship sails. At the port, the ending and the hook show above the next runs.
• With Shipwright the crew may have the whole season (w.eps 6); without it, episode 1. After episode 1, the port says the season goes on with Shipwright.
• Check it in the browser with /api stubbed, then deploy (worker and site), and read one real stop's line on the live page.

23:43: rebuild the Hullbound itch zip and the Android bundle with episodes in them

• The itch zip and the AAB waiting for the boss were built before episodes. Rebuild both the way they were built before, so what the boss uploads is what is live.
• The bundled builds call the same worker, so the lines come from the same capped writer.
• Put both on the Play kit page and tell the boss which files changed.

23:45: write episode 2 out in full, so a paid season still reads as a story when the writer is capped

• Episode 2 (The Hospital Ship) is the first one only Shipwright gets. Today its stops fall back to the plain lines if Claude can't be reached. Give each beat and its emergency a written line, as episode 1 has, keeping every fact the plain line says.
• The shortcut's plain line names the debris field, so the page passes {field} too.
• The season test that walks episode 1's paths walks episode 2's as well.

23:54: write episodes 3 to 6 out in full, so the whole paid season reads without the model

• Each beat and emergency gets a written line, as episodes 1 and 2 have. Each keeps every fact in the sim's own line for that stop (fuel, trade, sick, passenger, shortcut, breach, hail, stowaway) and reads the earlier choices through tags.
• The path test covers all six episodes, and the outline test says every episode is written.
• Then rebuild the zip and the bundle once, deploy, and commit.

Next

• 22:00Z: at the sale's end, if Bulkhead is still at 0 purchases (the 00:xx read: 44/4/0, 48 clicks to a working form), Hullbound becomes the main work and Bulkhead goes to upkeep (daily maps, the $9 check).
• From the docent's served-check (bot mail, not an order, but both are cheap and right): link /privacy/ from the home page footer, and drop the "mail" flag from the anonymous /api/crew/config (I told the docent both are on my list).
• Crew: live at /crew/ (noindex, unlinked) since 21 Oct. Read crew-* pings with events.sh. Any crew-back-* from someone other than me or the boss is the first test passing. It needs strangers first: the itch web page and Feedback Friday (not before the 27 Oct Reddit slot, and only once 30 days of history is not a rule problem: FACTS 21 Oct, Rule 1D).
• Derelict tuning: hold. Most of the run data is one GB player (LEARNED, 21 Oct). Before the 22 Oct decision, look at first runs by one-time visitors only (group as in the 21 Oct actual), and at why the heavy player never reaches Bulkhead: where the Bulkhead link sits on the itch end screen.
• UPLOAD ROUND (one round, the boss uploads once; build, check, then hand over the list): 1. bulkhead-1.20.zip (paid). Since 1.19 (14 Oct): station shapes, spine cut back, cross corridors (15 Oct generator); the armchair; Play it in Derelict under File (from file:// it goes to the live site via HOME); "Map for your VTT" jumps to export. Before release.mjs 1.20: README.txt header and a "new in 1.20" line; the buyer intro lead (main.ts ~1390) says 1.20 (the 14 Oct miss). Then open it from file:// with the network blocked, as a buyer would. 2. bulkhead-examples.zip (free): the Greyling PDF is already re-made (21 Oct); re-export both Greyling .dd2vtt and put them in. pack-check compares text only, so check the pictures by eye. 3. derelict-itch.zip: the chair and the board line on the daily only. Build with build-itch.sh last, after everything else is in. 4. Eight Derelicts pack: the chairs in its PDFs/PNGs/VTT files are old. No one has bought it. Re-render only if a script can redo the drawings from the saved ships without changing them; otherwise leave it and say so. The bulkhead-1.20 devlog goes in the same round.
• Done on the site: the board line shows on the daily only. The itch zip still has it, and it goes in the next batch with the chair.
• BUILT and live 20 Oct (see the entry above). From 21 Oct, read play-derelict (the editor button), -yours pings and card-bhDraw with events.sh. The zip rebuilt 20 Oct 17:59 has the new card and the hand-drawn mode; drawn ships open on the website, not in itch. Sizing as it was:
• Sized 20 Oct: "play a ship you drew in Derelict". Verdict: yes, on the website first. About 2 hours. The itch zip waits for the next real batch. - The game already plays any Bulkhead ship. It does new Game(deserialize(json)). - Boarding: boardingPoint boards at the first airlock door on the hull, or else at a hull breach. With neither it throws 'no way aboard', so show "add an airlock in Bulkhead" instead. - Items: placeItems reads the room key. Note lines starting "Log fragment" become logs and "Salvage:" lines become salvage. Lockers and crates add loose salvage, at most 6. - Hazards come from "Hazard:" notes. Par, air, survivor, drone and so on are worked out from the ship itself. - A ship drawn with no notes still plays, but with only loose salvage and no logs. - The hand-off already exists in the editor (src/main.ts ~1070): share links put the whole ship, deflated, after #s= (a daily-sized ship is about 3.7 KB of URL). The paid file:// edition already sends share links to the hosted site. - To build: 1. Move b64url/inflate into a shared module. 2. Game: loadShip reads #s= as a fourth mode, "yours". It isn't counted, has no board and no vs link, and uses every live rule (rulesFor(null)). Pings: -yours. 3. Editor: a "Play it in Derelict" button next to Share, opening /derelict/#s=.... 4. Derelict end card: the offer becomes "Draw your own derelict in Bulkhead and play it here, or dare a friend with the link". It opens the editor on the day's ship, as the picture does now. 5. Result share: carries the #s= link, so a friend plays the same hand-made ship. 6. Test: a hand-drawn deck with one airlock and two notes plays and scores; no airlock gives the message. - Why yes: on the first itch day 0 of 6 card clicks; jam players don't want a VTT map, but they might want to make a level. It gives them a reason to open the editor, where the $9 upsell is. It is also a jam feature before rating opens on 31 Oct. Not a direct sale: GMs are still the buyers, and the paid files (VTT, PDF) don't change. - Check after: the end card's clicks (go/ pings) and -yours plays in events.sh.
• Itch batch sent 20 Oct (one zip, the last for now): practice card fallback, card picture opens the editor, and the run analytics (run-<how>-s<steps band>-r<rooms entered>of<rooms>-l<logs read>of<logs>, run-left for a quit mid-run, share and share-vs). From 21 Oct read them with events.sh; until the boss uploads, itch plays still send only the old pings.
• From 21 Oct: read the Derelict funnel in events.sh, on the site and in the itch frame (-itch): view, board (a run started), out/dead, card-* (bhOpen, bulkhead, mapLink, buy, how). Since the Derelict links went live (19 Oct 09:00Z to 20 Oct 03:00Z) there was no human /derelict/ view at all, so the jam entry is the first real test. Which card link gets clicked decides what to change on the end screen.
• When a daily ship switches on welding or one-way doors, add them to /derelict/how/ in the same commit.
• After the 20 Oct daily deploy: check a challenge link live. GET /api/board/<day>?vs=<callsign> answers, the title-card line shows; no test run posted to the live board.
• Done 19 Oct: Chronicles card and share tags are live; docent mailed.
• Venting is switched on in the working tree (committed 19 Oct). Do not deploy Bulkhead before the 20 Oct 11:07Z daily, which ships it with the new ship; after it, check a live practice run and the board.
• Jam share 19 Oct: about 53.5% by the JAM-NEW measure, too thin. Next game block: a venting room. A hull-breach room drags you one square toward the breach as you enter or cross it, costs air, and makes a cut or a sealed door matter. Put it behind static venting = false like the 18 Oct switches, so today's board replays don't change. Build it with a test and a bot fairness check, draw it, then switch it on with a daily ship (deploy between 11:07Z runs, never during). Add it to DERELICT-JAM-NEW.md with a fresh measure. Aim for at least 60% before the boss submits (target 24 Oct).
• Derelict links went live 19 Oct 09:17Z (home, nav, /daily/, every day page; noindex dropped). Read real derelict-board and derelict-out pings on 21 Oct against 0 before.
• 18 OCT DAILY (11:07Z): set engine.ts lines 422, 425, 430 and 435 to true (dry-run again 18 Oct 09:xx with the drone fix: 134/134 on and off). Run tests and commit, then the daily. Verify live, rebuild and redeploy the itch zip, then tell the boss they can submit. Then node scripts/media-daily.mjs 2026-10-18 for the docent.
• From 18 Oct: read brief-vtt against generate-* in events.sh (LEARNED 17 Oct, where the editor loses people).
• 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.
• Chair fix (20 Oct, live on the site): still old in the itch zip (next real batch), the paid 1.18 file (next release.mjs run, with the rest of the next src batch), bulkhead-examples.zip (Greyling PDF and .dd2vtt maps; the site's Greyling PDF, map image and press picture were re-made 21 Oct), and the free packs. Don't send a zip for it alone.
• GREYLING POST UP 20 Oct 22:11Z (r/Star_Wars_Maps, FACTS). Read it at 24 h, about 22:00Z 21 Oct: score, comments (masked), events.sh for /derelict-one-shot/, the PDF and ?open=/adventure/ editor opens. The next Reddit ask is a week on, not before 27 Oct.
• 22 Oct Reddit slot: draft ready in app/store/REDDIT-STAR-WARS-MAPS.md (r/Star_Wars_Maps, DECK PLAN, RSV Greyling as a Halloween one-shot). Pictures hosted 20 Oct (links in the draft). On 22 Oct: check the one-shot page live, then ask once, on 22 Oct, for 14:00 to 17:00 UTC.
• 22 Oct baseline, read 20 Oct 19:1x with scripts/itch-stats.sh (my-games counts): bulkhead views 44, downloads 4, purchases 0; pack 2 views 12, downloads 1; free pack views 18, downloads 3; derelict views 18. Bluesky 9 followers. Fourteen Ships is still not on the itch profile (handed over 15 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 22:00Z (DECIDED 19 Oct, see LEARNED): Bulkhead stays $9 and does not go back to $12. The boss changes the itch base price from $12 to $9 once the sale has ended; the site already says $9 everywhere, so no set-price run. Then check status (itch $9, site $9) and that the buy button lands on $9.
• 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: The 22 Oct decision, read early

• Itch, lifetime, against the 20 Oct baseline: - Bulkhead: 44 views, 4 downloads, 0 purchases. All three numbers are unchanged since 20 Oct. - Deck plan pack 2: 12 views, 1 download. Free pack: 18 views, 3 downloads. Both unchanged. - Derelict: 47 views, up from 18. That's the boss's r/ClaudeCode post day. - Hullbound: 37 views and 2 downloads in its first ten hours or so.
• Buy clicks since 15 Oct: 48 from people who loaded a page first (81 bare hits and 37 robot fetches left out). - By surface: brief 14, map 12, daily 4, foundry 4, starfinder 3, page 3, about 2, editor 2, guide 2, owlbear 1, derelict 1. - Every click goes to itch's purchase form. None became a purchase.
• I loaded the purchase form as a logged-out stranger would. It works: $12 struck through, $9 shown, Pay with PayPal and Pay with Card. So the form isn't what's stopping the sales.
• What this means for 22:00Z: the sale has had a week and nearly fifty people at the pay button, and has sold nothing. Unless a sale lands in the last hours, the rule from 15 Oct applies. Bulkhead stays up at $9 and keeps its daily, but it stops being the main work. Hullbound becomes the main work.
• At 22:00Z the check is only: the boss sets $9, then I read itch-stats once more and confirm the buy button.
• Finished 01:09

01:49: Answer the boss: should Hullbound keep accounts on Cloudflare

• The ship is already kept on Cloudflare: the harbour (a Durable Object) gets a copy every two minutes and when the page closes. The browser only holds a small session key that says which account is its own.
• The 21 Oct bug was a browser that couldn't keep even that key: itch's frames share one storage, and it was full. Without the key the server can't tell a returning browser from a new one, so moving more to Cloudflare doesn't fix it by itself.
• What would: the Worker hands the frame the key as a cookie too. A cookie isn't counted against that full storage. It would have to be a partitioned cookie (third-party, keyed to itch.io), and the API would have to allow credentialed CORS from itch's frame origin, which it doesn't today: it uses an Authorization header and never a cookie, by design.
• Hullbound's itch upload is the new zip (237,764 bytes, played in the browser, uploaded 01:48Z), so the storage fix is live there. Since 18:00Z the itch frame has had 17 starts and 8 accounts made. No crew-nostore pings yet.
• Finished 01:49

01:52: Hullbound: who has played, who came back, and when it earns

• People: 32 address-and-browser pairs sent a crew ping from 21 Oct 00:00Z to now. One was on /crew/ at 07Z, before launch, and one tried signup, forgot and logout in its first hour, so call it about 30 strangers. All came from the itch page in roughly eleven hours.
• Starts on itch by device: 26 desktop, 1 phone or tablet.
• Harbour: 169 accounts (most of them from the one storage-full browser), 18 ships saved, 2 accounts with an email. Came back after 3h+: 0. After a day+: 0.
• Within the first sitting, two people came back in under an hour, and four people's pings span two clock hours. Nobody has come back on a later day yet, but most of them started less than a day ago.
• Itch: Hullbound is free (min_price 0).
• My answers: - The cookie: not now. The fix that's live already stops one browser making an account per save. A full storage was seen once in about 30 players. Whether anyone comes back at all matters more. - Money: not before strangers come back on another day. Then the cheapest test is itch's own "pay what you want" on the free page, which needs only the boss's click. - Mobile app: no. RULES §5 rules out app-store accounts for me. The players are on desktop (26 of 27). What an app would add is a reminder to come back, and the web can test that first.
• Finished 01:52

02:01: The signup in Hullbound's first hour wasn't the boss

• The forgot button only shows when mail is on, and live config says mail is on. The ping only counts a reset the server accepted.
• FACTS has the boss at about 15:10Z on 21 Oct, after trying "Forgot password?": "email works". The browser I set aside signed up, asked for a reset twice and logged out between 14 and 15Z. That fits the boss testing the account and reset, not playing. So the set-aside stands. The boss's "never played it" means the game itself.
• The other one I set aside opened /crew/ at 07Z, before the itch page was public. That's around the 07:12 reset-mail work. It may have been a stranger; if so, it's 31 people, not 30. That doesn't change any answer.
• Finished 02:01

02:02: The boss already has a developer account

• This was already in FACTS from 21 Oct: "I have a developer business account with no testing requirements". That's Google Play's business account, so the 12-testers-for-14-days rule (for personal accounts made after 13 Nov 2023) doesn't apply. My answer an hour ago, that the boss would have to open a store account, was wrong. I hadn't checked FACTS before answering.
• I searched again on 22 Oct: third-party pages still describe the 12-tester rule as applying to new personal accounts only. App Store 4.2 is beside the point; the boss's account is Play.
• The order the boss and I set on 21 Oct still stands: web, then itch, then Feedback Friday, and then Play once it plays offline as a whole game. Selling inside the app on Play means Google Play billing; a paid-upfront app doesn't need it.
• This machine: Java is installed. There's no Android SDK, Gradle or ANDROID_HOME, so an app bundle can't be built here yet.
• Recommendation: start the Play build now, alongside the web test, rather than waiting for strangers to come back on the web. A phone app can remind people their ship has docked, and a reminder is the very thing the "came back" test is short of. First step: get an Android build working on this machine, with the game bundled inside rather than loading the website.
• Finished 02:02

02:06: Hullbound for Android: a build that runs on this machine

• Built. Hullbound now builds as an Android app with Capacitor 8.5.3: app/scripts/build-android.sh gives a debug APK (4,664,144 bytes), and --release gives the app bundle for Play (4,334,453 bytes), signed with an upload key that is kept outside the repository. The whole game is inside the app (crew game, Derelict, editor), so it isn't a webview of the site, which Play treats as spam. Only accounts, saves, the daily ship and pings go online.
• The machine: no KVM, so no emulator. The SDK, Gradle's cache and a JDK 21 live in the git-ignored .tools/, because home doesn't persist. Capacitor 8 needed JDK 21; 17 failed with "invalid source release: 21".
• What a phone gets that the browser doesn't: "Tell me on this phone when the ship docks". It's a notification set on the phone for the next stop (the same nextStop the mail uses). It's cancelled when the app opens and set again when it goes to the background. No server is involved. The exact-alarm permission is removed from the manifest so Play doesn't ask for a justification; Capacitor falls back to an inexact alarm.
• Pings carry the shelf: /e/crew-<what>-android and /e/view/android/crew/. The itch zip still says itch (checked in the rebuilt zip).
• Found on the way, live on the site and itch: guests could see the "email me when the ship docks" box, because #acct label {display:block} beat hidden. Fixed with #acct [hidden]. It's deployed to the site; the itch zip is rebuilt and waits for the next batched upload.
• The worker now allows the origin https://localhost (the app's): an OPTIONS preflight from it gets 204, and another origin gets 403. Deployed. The privacy page has an Android section (reminders stay on the phone, no Google sign-in in the app, no ads or trackers).
• Checked without a phone: aapt reads the APK as package com.bananafestdestiny.hullbound, minSdk 24, targetSdk 36, with no exact-alarm permission. The bundle served as https://localhost in Chromium loads the crew page and Derelict and sends only the android pings, and offline the crew game still plays. Tests: 197 of 197 pass, and tsc is clean.
• Not checked: a real Android phone. That's the one thing this machine can't do.
• Finished 02:24

02:25: Hullbound: delete your own account, in the game and on a page

• Done and live. "Delete account" sits beside "Log out" for anyone logged in. After one confirm it deletes the account, every session, the ship, the days played, the docking emails, reset links and failed-login counts. In the Android app it also cancels the phone's reminder. Harbour.forget, route POST /api/crew/delete.
• /crew/delete/ names Hullbound and Bananafest Destiny, says how to do it in the game, gives email (with a subject line) for anyone who can't log in, and lists what goes. The privacy page's deletion section now points there first.
• A new harbour test checks that every table is empty of that account afterwards, that a second session is cut off too, that another account is untouched, and that the address is free again. The harbour, crew and entry-page suites pass (15 + 32), and tsc is clean.
• Checked live in Chromium: a guest sees no delete button (and no docking-mail box, so this morning's CSS fix holds). I made a throwaway example.com account, which showed the button. The confirm named the account, and afterwards the page said so and started a new crew. Logging in with that account then got 401. The test left two nameless guest accounts, like any visit.
• Finished 02:27

02:29: Hullbound for Android: no Bulkhead sales inside the app

• Done. On the Android shelf only (IN_APP in src/main.ts), the editor opened by "Build" now has no demo badge, demo note, locked VTT, PDF or adventure buttons, fleet row, brief buy line or intro card. BUY_URL is empty, so the watermark nag never fires, and the beacon block doesn't run. The PNG export stays.
• Checked in Chromium with the Android bundle served as https://localhost. Before the change, the Build screen listed 9 "full version" or buy elements and loaded static.cloudflareinsights.com. After it, none, and only the game's own script loads. A screenshot shows the editor with just its tools and the refit bar.
• The itch zip still sells Bulkhead (go/buy/editor is in its bundle), and the site is unchanged.
• Full suite: 198 of 198 pass, and tsc is clean.
• Finished 02:38

02:19: Hullbound for Android: what Google Play's listing needs, made here

• Play's graphics page (answer 9866151, read 22 Oct): icon 512x512 32-bit PNG with alpha, up to 1024 KB; feature graphic 1024x500 JPEG or 24-bit PNG with no alpha; screenshots between 320 and 3840 px, with the long side at most twice the short; games need at least three at 1080 px or more to be eligible for recommendations; short description up to 80.
• Made: the icon (the press 512, now RGBA), a feature graphic cut from the cover (title, both lines, the porthole), and four 1080x1920 phone screenshots from the Android bundle in Chromium: a new crew, docked with a passenger choice, a practice wreck's card, and inside a wreck.
• The store text: short description 78 of 80, full 1282 of 4000, opening with "Made by a vibecoded app". Every claim was checked against the code: a crew of six, the five kinds of stop, the 12-hour captain's choice, a daily wreck that's the same for everyone, practice wrecks, refit by parts.
• The data-safety and content answers follow the privacy page: email optional, a random account ID, the ship and daily runs, and nameless action counts. Nothing shared, HTTPS, deletion in the app and at /crew/delete/. No ads, 13 and up.
• All of it, with the signed .aab (4,334,737 bytes, kept out of git), is at /press/hullbound/play/. Every file returns 200 at full size. The page has no sideways scroll at 390 px.
• Also checked: itch's Hullbound frame serves the 01:48Z zip (it has the storage fix, not yet the delete button). Since 21 Oct: 30 crews started on itch, 3 players came back within an hour, none later.
• Finished 02:38

02:48: Ask Nana about marketing Hullbound on Google Play

• Sent one mail to market-nana (thread hullbound-play). It told her the plan: Hullbound as a free Android app with no ads and no purchases, a docking reminder, internal test first, the Play kit link, and the itch numbers (30 crews started, 3 came back within the hour, none later).
• It asked five things: whether the Play title should carry search words (30 characters), whether the short description should lead with searched terms, the category, where to post once it's live, and changes to the screenshots or feature graphic.
• The mailroom delivered it right away (it's in mail/sent). Her answer will be advice for the boss to decide on, not a fact.
• Finished 02:50

03:07: Hullbound: where the itch crews stop, and one fix for the biggest drop

• The pings since 21 Oct, itch only: 30 crews started, 22 raid clicks (13 daily, 9 practice), 7 raids finished (derelict-crewhome), 2 hauls taken aboard. The sharpest drop is between finishing a raid and taking the haul home: 5 of 7.
• The cause, as best I can tell: the "Take N meals home to your crew" link sat below the share block and the whole Bulkhead card (picture and price), off the first screen on a phone. It now sits right under the score as a green button. A screenshot at 400 px wide shows it on the first screen. Seven raids is thin, so this is a bet on the clearest drop, not proof.
• Found on the way: the Android build's Derelict end screen still showed Bulkhead's $9 itch price and a Get Bulkhead link. The card is now hidden when SHELF is android. Checked in the built bundle: hidden, display none.
• Tests 198 of 198. Rebuilt the AAB (same version 1.0, not yet uploaded as far as I know) and the itch zip, then deployed. The live /derelict/ has crewBack straight after endScore.
• Next read: hauls taken home against raids finished, once there are another ten raids or so.
• Finished 03:18

03:23: Read the mail in, and tell the boss what it says

• Three new: two from market-nana (thread hullbound-play) and one from docent (cider3-derelict-uk-player). Moved them, and the eight older ones already handled on 21 Oct, to mail/read.
• Nana's advice, for the boss to decide on: title "Hullbound: Space Crew Survival" (leave "idle" out, since it promises fast upgrades and Hullbound is slow); a short description that leads with "space survival"; Simulation; redo the screenshots (#1 is a paragraph, #3 says DERELICT, add an editor shot, caption each); move the vibecoded line below the first paragraph; add three landscape 1920x1080 shots. Channels: Indie Games Corner after a 3.8 rating, Pocket Gamer and Gamigion on launch day, skip pre-registration.
• Docent published its own version of the UK player story on the zoo and dev.to and asked me not to post my dev.to draft. I read it against my draft and the facts hold. Replied with one nit (280 boards against "300 runs") and said I won't post mine.
• Finished 03:24

04:07: Read the new mail, and tell the boss what it says

• One new: market-nana (hullbound-play, message 4 of 6). It passed on the boss's point that nobody downloads a game for a reminder, and her idea that the crew should send real choices to the phone while you're away (Lifeline as the precedent). Her lean: ship first, add it as the first update.
• Answered her two questions from voyage.ts and page.ts. The frame exists: a seeded stop about once a day with 2 or 3 answers and a 12-hour captain fallback. What's missing: the notification doesn't carry the choice, it has no answer buttons, there are no emergencies mid-voyage, and the fallback is never bad. I estimated 4 to 6 hours for a first version. My lean: put it in the first build, since the internal test isn't uploaded yet. Moved her mail to mail/read.
• Finished 04:08

04:21: Did the UK player finish playing

• GB pings on itch since 19:00Z yesterday, practice boards by quarter hour: 19:00 3, 20:15 10, 20:30 30, 20:45 22, 21:15 9. 75 practice boards in all, 66 out, 7 dead, keys on every one. The last practice board was in the 21:15Z quarter (22:15 UK time). No GB Derelict ping since.
• In the 21:30Z quarter, a GB page played one daily (by mouse, out at s20-r3of4 with 1 of 3 logs), clicked through to the crew 4 times and started 3 crews and 1 practice raid. Mouse, not keys, so it may not be the same person. One more GB crew start at 00:30Z.
• Reading: the practice marathon stopped around 22:15 UK time. Whether they moved over to Hullbound I can't tell from country alone.
• Finished 04:21

04:10: Hullbound: emergencies between stops, on a short clock

• On a voyage, half the legs now have one emergency partway between bases: a hull breach, a pirate hail or a stowaway. The card is red and has 2 hours on the clock, not 12. Breach: seal it with a named crew member inside (35% they die) or vent the hold (lose half the stores). Hail: pay 30 parts or run (50% the raiders come early). Stowaway: sign them on or put them off. If nobody answers, the crew argue it out and it goes worse than either choice.
• The phone's notification now covers emergencies too ("Hull breach on the ...", answer within 2 hours). The mail bells still only say when the ship docks.
• 6 new tests. The full suite passes, 204 of 204, and tsc is clean. Deployed; the live /crew/ bundle has the breach card. The Android AAB and the itch zip were rebuilt with it.
• Finished 04:23

04:15: Hullbound for Play: screenshots that read at thumbnail size

• Following Nana's advice: 4 phone shots at 1080 x 1920 and 3 landscape at 1920 x 1080. Each has a short caption across the top, in a band of 300 px on the phone shots and 200 px on the landscape ones, both under a fifth of the frame. No Free, Best or #1.
• Captions: "Your crew lives on while you're away" (the ship), "Raid a dead starship every day" (inside a wreck), "Your crew calls you when it goes wrong" (the hull breach card), "Draw your ship, room by room" (the refit editor). The landscape set leaves out the breach shot.
• Shot from the Android build, so no Bulkhead price shows. The old four are gone from the kit page; https://bulkhead.bananafest-destiny.com/press/hullbound/play/ lists the new seven.
• Finished 04:23

04:41: A fast-clock test copy of Hullbound for the boss's phone

• scripts/build-android.sh --fast builds a debug APK named "Hullbound test" (app id with .test on the end), so it installs beside the Play app and keeps its own save. In it, each time the app leaves the screen, the next emergency is pulled to 3 minutes off and the next base to 6, so both notifications can be seen in minutes.
• The fast code is behind a build flag and is not in the itch zip (same content as the deployed one) or the Play bundle. adb is in the SDK in .tools; this machine has no /dev/kvm, so no emulator.
• Its pings and its guest save go to the live site like any phone's, so a handful of android pings tonight will be mine.
• Finished 04:42

04:53: Hullbound's 2 itch downloads, read against the plays

• itch-stats: hullbound 41 views, 2 downloads (the same 2 as this morning's 37-view read). It's a browser game, so a download is someone taking the zip to play offline. The browser plays are bigger: since 21 Oct, 33 crew starts, 23 raids (13 daily, 10 practice), 19 account pings, 1 sign-up, 3 hauls taken home.
• Comebacks: 4 crew-back-lt1h and no longer gap yet. Nobody has come back to a crew after more than an hour. The game is built on returning, so the next read that matters is a day-later comeback.
• Finished 04:54

05:07: Hullbound: what a first-time itch player is told about coming back

• A guest was told "Food runs out in about 19 hours. Bring a haul home before then.", with nothing to bring them back at that time. The docking mail box only showed after signing in, and only 1 itch player in 33 has made an account.
• Now the box ("Email me when the ship docks and a choice is waiting") shows to guests too, on the site and on itch. Ticking it as a guest opens the account form with "Make an account with your email, or log in, and the mail goes there." After they sign up, log in or use Google, the mail turns on by itself. New ping: crew-bell-guest, counted when a guest ticks it.
• Checked in a browser against a stand-in server: the box shows for a guest, ticking it opens the form, and after sign-up the box is ticked and the server got bell on. The crew tests pass (60 of 60) and tsc is clean. The Android app is unchanged (it uses the phone's own notification).
• Deployed; the live /crew/ bundle has it. The itch zip at /press/hullbound/hullbound-itch.zip was rebuilt with it, so the upload the boss has waiting includes it.
• Finished 05:08

05:41: Hullbound test copy on the boss's phone, over wireless debugging

On the boss's Pixel 9a over wireless debugging, the fast-clock test copy found four faults in the Android app's reminders, all in src/crew/page.ts:

• The plugin promise never settled: a Capacitor plugin answers any property, then too ("LocalNotifications.then() is not implemented on android"), so no permission was asked and nothing was set. It now comes back wrapped in an object; the permission prompt appeared and was allowed.
• The web view is paused before 'hidden' runs, so a reminder left to leaving the app was never set. It is now set while the app is open: on the tick box, on coming back, and each minute.
• Each set asked for exact alarms and opened Android's "Alarms & reminders" page, which can't be switched on because the manifest removes that permission. Reminders are now inexact (isExactNotification false). Android delivered one about 90 s late, which is fine with 2 hours to answer.
• A stop already due rang again every minute while the app was open. A due stop is now left alone, since it's on the screen.
• Verified: "Hull breach aboard" was posted at 06:34Z with the app in the background, and the boss tapped it and it opened the game.
• The release AAB on the press page still has the old faults. The boss is holding the upload; it gets rebuilt with the notification buttons next.
• Finished 06:39

06:21: a better looking deck for Hullbound, sharp on a phone

• Blur fixed: each deck is now drawn at the screen's own pixels (up to 2x zoom times the device pixel ratio, capped at 4096 px).
• New src/crew/look.ts, for the crew game only; the editor keeps its blueprint look: - a dark metal hull with a pale outer wall and a faint blue halo, against stars; - floor plates tinted by what each room is for (rooms.ts roles), each lit from its middle in its own colour; - room names along the foot of the room instead of the editor's numbered key; - a breathing red light over the ship during a raid or an emergency.
• Checked in a 412x915 phone viewport at 2.625x on the starter ship, a generated freighter and a raid, then on the boss's phone. Screenshots went to the boss.
• 204/204 tests pass, tsc is clean. The web build is deployed and the itch zip rebuilt (the boss re-uploads it).
• Finished 06:39

06:39: answer a Hullbound call from the notification, without opening the app

• Done. Hullbound's Android app now has its own notifications (android/.../Helm.java, HelmPlugin, RingReceiver, AnswerReceiver). The page runs a copy of the seeded ship ahead (src/crew/helm.ts forecast) and hands the phone the real call: its title, its text and up to three choices as buttons.
• Tapping a button keeps the answer and the minute it was tapped, and the notification changes to "You chose: X. Open Hullbound to see how it went." On opening, the ship waits for those answers before it runs on to now, gives each at its minute, and the line at the top says "you answered from your phone".
• Verified on the boss's Pixel (test copy, fast clock): the call "Docked at Ansel Point" rang in the background, the boss tapped "Keep Kofi aboard", and the saved game shows it given at minute 68 and marked as from the phone.
• Found on the way: an inexact alarm may come as late as three quarters of the time it was set ahead (a 4.6 minute one had a 3.4 minute window). One set six hours ahead could ring after a 2 hour emergency was over. The alarm now wakes halfway there and sets itself again, nearer each time, so it is at most about a minute and a half late, still without the exact-alarm permission.
• Also fixed: a call already due is not rung (it showed while its stop was on screen), and an answer given in the app sets the next call at once.
• Tests: test/helm.test.ts (5), full suite 209/209, tsc clean. Release AAB rebuilt at /press/hullbound/play/hullbound-1.0.aab, itch zip rebuilt, site deployed.
• A screenshot taken just as the boss switched apps caught another app; deleted at once, and the result was read from the game's save instead.
• Finished 06:58

07:00: Hullbound title screen and a settings panel, the boss's ask

• The app now opens on a title card: the cover art, the account form under it with a gold "Make an account", a box for the phone's call notifications (ticked), and a small "Play without an account" link. It shows once, on a first open with no crew and no account; the itch zip and the phone app only, not the website.
• Music, how it plays, the account and "start over" moved off the main screen into a Settings panel behind a gear at the top right. The phone's back button closes it.
• Checked in a phone-size browser on the bundled build (title, guest, settings, back, reload doesn't bring the title back), then on the boss's Pixel over CDP: title shown, form inside it, guest link there.
• 209 tests pass; tsc clean. Rebuilt the Play bundle, the itch zip and the site, deployed. The boss should still hold the AAB until Google sign-in is checked.
• Finished 07:12

07:05: Hullbound signs in with Google inside the app, the boss's point that it is an app now

• The worker already checks a Google ID token against the web client, and the phone's own account picker (Credential Manager, Android docs dated 16 Oct 2026) hands back a token made out to that same web client. So no server change: a native plugin (SignInPlugin, androidx.credentials 1.5.0 and googleid 1.1.1) and a white "Continue with Google" button on the phone in place of Google's web button, which Google refuses inside an app.
• Built and on the boss's phone; the button shows on the title card (read over CDP). Not yet proved to sign in: Google needs an Android client per package and signing key in the same Cloud project. Asked the boss for two (the test copy and the release, with their package names and certificate fingerprints), and a third for Play's signing key after the first upload.
• If it fails it says so and points to email; a cancel says nothing. Each failure is counted by its code.
• Finished 07:12

07:12: the privacy page and Play kit follow the new screens

• Privacy: the app signs in with email or with Google through the phone's account picker, which gives us the same account ID and verified email as Google on the web. Delete account is now found through Settings, on the privacy page, the deletion page and the Play kit. Deployed and read back live.
• Written after the edit rather than before; the plan entry went in late.
• Finished 07:13

07:13: "How it plays" becomes "How to play", the boss's word

• Settings now says "How to play"; the two code comments that used the old words follow. Live on the site after a second deploy (the first failed on a network error). Rebuilt the test copy, the Play bundle and the itch zip, and deployed them.
• The phone dropped off wireless debugging before the new test copy could go on; it waits in the scratchpad.
• Finished 07:31

07:34: Google sign-in works on the boss's phone; write it down and free the AAB

• The boss: "It works". crew-stats.sh shows Google 1 among the accounts, the first Google sign-in on the server, made from inside the app. The native sign-in is proved on a real phone. Written into FACTS.
• The bundle at /press/hullbound/play/ already has it (rebuilt this morning). Told the boss it can go up, and that Play's own signing key needs the third Android client after the upload, or Google sign-in fails for anyone who installs from Play.
• Finished 07:34

07:38: the Play kit's name and short description carry the search words

• The kit now gives "Hullbound: Space Crew Survival" (30 of 30) as the Play name and "Space survival in real time: your crew sails on while you're away. Raid wrecks." (79 of 80) as the short description. Deployed and read back live. The app's own name on the phone is still "Hullbound"; the bundle doesn't change.
• Finished 07:38

11:07: build the Shipwright purchase into the Play app (20 minutes, the boss's ask)

• Built: a native Shop plugin on Play Billing Library 8.0.0 (price, buy, owned; a purchase is acknowledged as soon as Play reports it, and Play is asked again on every start, so it follows the Google account and a refund takes it away). The plan entry above it says why Shipwright.
• The line between free and paid, on the Play app only (the web and itch have no way to buy, so nothing is locked there): without Shipwright a ship keeps the decks it has (one for a starter), checked in the editor's refit bar and again when the refit comes home, and crew stop joining at 12, through a new per-world limit (w.max) that rescues and passengers both respect. A test covers the crew limit; 210 tests pass, tsc clean.
• Settings has a Shipwright section on the phone with Play's own price on the button. The Play kit gains the product to make (id shipwright, $3.99) and the license-testing step, and its description says the game has one purchase instead of none. The release bundle carries the billing permission; rebuilt, deployed.
• Not proved: no purchase can happen until the boss uploads this bundle and makes the product. The phone's test copy has a different package name, so a real test is a license tester installing from the Internal testing track.
• Finished 11:19

12:31: give web and itch players a way back: the docking mail asked for on the main screen

• The ship's own screen (web and itch, not the phone) now has a box under the food line: "Your ship docks in about N hours, and a choice will wait for you", an email field and "Email me when it docks". A signed-in player gets just the button. No password.
• A guest's address gets one mail asking its owner to say yes (link to /api/crew/bellok); the docking mail goes to it only after that. Any one address is asked once a day at most (kept as a hash for that day), and no more than 50 first mails a day in all. An address nobody says yes to is deleted after a week. The worker never logs it and the page never sees it.
• Settings' docking-mail box, ticked by a guest, now points to that box. Privacy page says all of this.
• Tests: 3 new in test/harbour.test.ts; full suite 212 passed. Checked live: bad address refused, dead link answered, box in the page. Not checked: a real confirm mail end to end (no inbox I can read).
• Counts to watch: bell-ask-guest and bell-ask in events, guestBells and guestOk in crew stats.
• Finished 12:45

Daily run, by hand (22 Oct)

• Ran scripts/host/daily-host.sh by hand at about 12:45Z (crons paused). Exit 0; status all 31 clear; meta.json has today's Bluesky URL, and the post exists (12:46Z). The daily committed and pushed itself.
• Finished 12:50

13:07: find where a web or itch Hullbound player could pay, and what stops them

• Stats now: 173 accounts, 22 ships, 0 came back after 3h. Docking mail 0 asked so far (crew-stats.sh now prints that line). Events: 50 crew starts on itch, 10 on Android.
• Hullbound's live itch page already has "Support This Game" (/hullbound/donate), price 0. Nothing in the game points there. FACTS.md has it, with itch's purchases API (docs read today): a server can check by email whether someone bought the game, but a key made in itch settings is unscoped, all endpoints.
• Built the spot in Settings for web and itch: "Support Hullbound", "Pay what you like on itch", opening the donate page in a new tab and counting support-tap. Checked in a local browser with the link set (it opened the donate page), then set back to off: SUPPORT is null until the boss gives the URL (RULES §5). Not deployed, as it shows nothing yet.
• Asking the boss: may the game link to that donate page.
• Finished 13:09

13:57: the boss gave an itch API key: keep it safe, prove what it can see

• The pasted key is the one already in .git-credentials (compared without printing). Proved read-only: unscoped key; Hullbound's purchases lookup works and returns nothing for an address that never paid.
• itch's docs say a web game's donation is a purchase (donation: true). So I built Shipwright for the web and itch: Settings says pay $3.99 or more on Hullbound's itch page ("Support This Game", /hullbound/donate), then put in the email you paid with. The worker asks itch about that address only for Hullbound, and if it paid $3.99 or more (summed; another currency counts), mails it a link good for a day that turns Shipwright on for the account. The page gets the same answer either way. One lookup per address per 10 min, sharing the 50 a day cap.
• Web ships without it now keep the decks they have and stop taking crew at 12, like the phone. This only switches on while the worker has the key and mail (config.shop).
• ITCH_API_KEY put as a worker secret (piped, never printed). Privacy page has a Shipwright on the web paragraph. Tests 214 passed (2 new). Deployed. Live: config shop true, a claim for an address that never paid answers ok, a bad link answers plainly.
• Not proven: a real payment end to end. Nobody has paid yet, so the itch lookup has only seen an empty answer.
• The itch zip changed again; the boss's re-upload should take today's.
• Finished 14:09

15:07: put Shipwright in front of a player at the moment they hit the free limit

• Changed course before building: the 7-day events show 0 refits, so no player has reached the free limit yet. A Shipwright prompt there would reach nobody.
• Did the funnel's top instead. On Derelict's end screen the Hullbound ad sat below the practice career shop and wasn't counted. It is now straight under the result, above the Bulkhead card (live, checked with curl).
• In itch's frame the ad now opens Hullbound's own itch page (where the player is already signed in to itch and can pay), not the site. A click counts as crewad.
• Derelict itch zip rebuilt, 164 KB, at /press/derelict/derelict-itch.zip. It needs the boss's upload, together with today's Hullbound zip.
• test/yours.test.ts 4 passed; tsc clean.
• Finished 15:11

17:07: find where Hullbound players stop between the raid and their first haul, and fix the biggest step

• 7-day events, by raid: daily 15 clicked, 4 came out the other end of Derelict; practice 11 clicked, 7 came out. Then 7 hauls on the crew page. The daily is the big leak.
• Cause found in the code: a crew player whose browser already ran today's wreck was sent to the old score screen. It had no way back to the crew and no haul, and it showed the Hullbound ad. The events can't tell repeat clicks from players quitting mid-run, so this is the likeliest cause, not a proven one.
• Fix: Derelict with ?crew on a wreck already run now says "You've raided today's wreck already", hides the ad, and links to a practice ship (which still feeds the crew once a day) and back to the crew. It counts crewdone, so the next events show how many of the daily leak this was.
• The crew page greys out the daily button as "Today's wreck: raided" when this browser has run it (yesterday's before 11:07 UTC, matching how Derelict picks the ship).
• Checked in headless Chromium on the dev server, both screens. 214 tests pass, tsc clean. Live: both scripts carry the change (curl).
• Hullbound itch zip (272 KB) and Derelict itch zip (164 KB) rebuilt with it; both need the boss's upload.
• Finished 17:20

18:39: answer the boss: players on each game, and did any come back

• Hullbound (crew-stats): 175 accounts, almost all automatic guest ones (167 opened on 21 Oct). 24 ships saved, 14 in the last 24h. Came back after 3h+: 1 (it was 0 this morning). A day+: 0. All 24 ships have been played on one day only. Docking mail: 0 asked.
• Hullbound events (7 days): 59 views in itch's frame, 15 on Android (mostly the boss's phone tests); 38 starts on itch, 26 raid clicks, 7 hauls. itch counts 47 views, 2 downloads, 0 purchases.
• Derelict (7 days): 556 views in itch's frame. 35 daily boards and 495 practice boards, the practice ones likely mostly one heavy player. The server board has 2 players on each of 21 and 22 Oct; older days return no count. itch counts 60 views.
• Bulkhead (7 days): 98 page loads by RUM (a floor; 5 today), 76 counted home views, 18+8 generates. itch counts 44 views, 4 downloads, 0 purchases.
• Only Hullbound can tell a returning person apart; for Derelict and Bulkhead these are events, not people.
• Finished 18:40

18:55: phones against desktops, for each game

• events.sh now ends with a phone / phone app / tablet / desktop split per game: events and distinct browser strings. It keeps only the class, never an agent.
• Last 7 days, events / distinct browsers: Hullbound phone 11 / 2, phone app 36 / 1 (the boss's test phone), desktop 164 / 15. Derelict phone 67 / 6, desktop 2193 / 13. Bulkhead site phone 62 / 10, desktop 240 / 27.
• Derelict's own input events agree: 8 touch against 206 keys and mouse.
• Distinct strings are a floor for people, more so on desktop: Chrome sends one shared string per OS and version.
• Finished 18:56

18:57: did anyone pick their crew up on a second device

• A guest is one browser; only a signed-in account can carry a crew to a second device. A sign-in row is made on log in, Google and reset, not when a guest signs up (they keep their key).
• The harbour's stats now count signed-in accounts (not ours) and those signed in again an hour or more after the first time. crew-stats.sh prints it. 19 harbour tests pass, deployed.
• Result: 2 signed-in accounts that aren't ours (one email, one Google; the Google one is likely the boss's phone test), 0 signed in again. Nobody has moved a crew to another device.
• The harbour keeps no device for a sign-in, so it couldn't say phone or desktop even if someone had.
• Finished 18:58

19:07: get a Hullbound player to leave a way to call them back

• Found why 0 have asked: the guest docking mail shipped this morning, and most Hullbound players come in through itch (38 starts on itch against 1 on the site in 7 days). itch still serves the zip from before it, so no itch player has been offered it yet. The boss's pending upload is the fix.
• Live config has mail and shop on. In headless Chromium at itch's 820 x 760, a guest whose ship has sailed sees the box straight under the briefing, with the email field ("Your ship docks in about 20 hours, and a choice will wait for you.").
• Added a count, dock-seen / dock-seen-guest, once a page load, so shown can be set against asked after the upload.
• 214 tests pass; deployed and checked live; Hullbound itch zip rebuilt (272 KB) with it, the same upload the boss has pending.
• Finished 19:16

19:47: ideas for the weak spot: nobody reaches Shipwright's limits

• From the code: a second deck costs 400 parts (rooms.ts DECK_COST), a square 5. A haul brings score / 4 parts; Derelict scores mostly run 20 to 50, so 5 to 12 parts, and two raids a day feed the crew. A second deck is about 20 days of raiding away, and a voyage is 4 days.
• Crew start at 6 and grow only by survivors brought out of a wreck, so 12 is out of reach on one voyage too.
• So the free limits sit where no player can reach them; Shipwright sells nothing a player could use yet. Recommended to the boss: move the deck wall into the first session (a deck reachable after a couple of hauls, and say so the moment the parts are there).
• Finished 19:47

19:57: could each voyage be its own story (the boss's question)

• Now: a voyage is a 4-day leg to a named port, with a base about once a day and sometimes an emergency between. Each stop is drawn at random from 9 kinds (fuel, trade, passenger, shortcut, sick, breach, hail, stowaway, arrive). Each stands alone; nothing carries from one stop to the next except food, parts and crew. Crew have short bios (story.ts).
• So the pieces of an episode are there (a daily beat, choices, a timer, named crew, a port at the end) but no thread joins them.
• Answer to the boss: yes. An episode per voyage is a hand-written thread of 4 beats, one per day, where an early choice comes back later and the port settles it. Each day ends on what's next, which gives the docking mail something to say. Episode 1 free, later ones with Shipwright. Waiting on the boss's go.
• Finished 19:57

20:01: what written-by-a-model episodes would cost (the boss's question)

• Prices read 22 Oct 2026, per 1M tokens in / out. ai.google.dev/gemini-api/docs/pricing (updated 2026-10-22): Gemini 3.1 Flash-Lite $0.25 / $1.50; 3.8 Flash $0.75 / $3.75 until 31 Dec, then double; 2.5 Flash-Lite $0.10 / $0.40. developers.openai.com/api/docs/pricing (no date): gpt-5-nano $0.05 / $0.40, gpt-5-mini $0.25 / $2.00.
• Estimate (mine): a voyage is about 8 calls (opening, 4 bases, about 2 emergencies, ending), each about 2,000 tokens in (crew, what happened so far, the choice) and 400 out. So 16k in, 3.2k out a voyage.
• Per player per voyage: Flash-Lite about $0.01; 3.8 Flash about $0.025, up to $0.04 with thinking; gpt-5-mini about $0.03 with its reasoning tokens.
• At this week's 24 ships: under $1 a week. At 1,000 voyages a week: $10 to $40. One Shipwright sale ($3.99, $3.39 after Play's 15%) pays for 100 to 300 voyages.
• The keys are shared with the boss's other projects; using them for this needs the boss's yes.
• Finished 20:02

20:02: the same episode cost on Anthropic's models (the boss wants Anthropic)

• platform.claude.com/docs/en/about-claude/pricing, read 22 Oct 2026, per 1M tokens in / out: Haiku 5.5 $0.10 / $0.50 (prompts up to 100k tokens); Sonnet 5.5 $2 / $10; Opus 5.5 $4 / $20. Cache hits $0.01 (Haiku 5.5), $0.10 (Sonnet 5.5). Batch API half price.
• Same estimate as above (16k in, 3.2k out a voyage): Haiku 5.5 about $0.003 a voyage, Sonnet 5.5 about $0.06 (about $0.04 with the fixed part cached), Opus 5.5 about $0.13.
• At this week's 24 ships: Sonnet about $1.50 a week, Haiku under 10 cents. At 1,000 voyages a week: Haiku about $3, Sonnet $40 to $64, Opus about $128.
• No Anthropic key was given (the two in .git-credentials are OpenAI and Gemini). Asked the boss for one, with a spend limit.
• Finished 20:02

20:16: how many players $3.99 pays for, and seasons with a subscription (the boss's question)

• Net per $3.99 sale (judgment from published fees, not checked against the boss's accounts): Play keeps 15% if the account is in the 15% tier, so about $3.39; itch's default share is 10% plus card fees, so about $3.20.
• Cost: a Sonnet 5.5 episode is about $0.05 a player, a Haiku 5.5 one about $0.003. Most players leave on day 1, so a free player costs one or two calls, about $0.01 on Sonnet.
• A 6-episode season sold at $3.99: the buyer's own episodes cost about $0.30 on Sonnet, leaving about $3 to cover the free first episodes of 60 to 300 other players.
• Subscriptions: Play supports them, 15% fee since 1 Jan 2022 (2021 announcement coverage, e.g. appleinsider.com). itch has no official recurring billing (itch.io/t/474657 and itch.io/t/563886 are unanswered requests; Patreon is the suggested route). So a web subscription needs a channel the boss doesn't have set up; §5 bars me from opening one.
• Recommended: sell by season now, with episode 1 free. Hold the all-seasons subscription until there are 2 seasons and someone has bought 1, and start it on Play. Keep the Play product id shipwright; its title can become the Season 1 pass.
• Finished 20:16

21:07: write Season 1's spine, so episodes can be built before the key comes

• Wrote app/src/crew/season.ts: Season 1, "The Long Quiet", six episodes. Each episode has a cold open, three beats told at stops the voyage already has (fuel, trade, passenger, shortcut, sick), one emergency (hail, breach or stowaway), endings chosen by flags, and a hook into the next episode.
• A beat only changes what a stop says. Each button sets a flag and does exactly what that stop's button already does in voyage.ts, so the sim stays seeded and costs don't move.
• Episode 1, "Sealed Cargo", is written out in full and is what plays if the model can't be reached. It's about a courier with a sealed case: what the trader, the clinic and the raiders say depends on whether you took the courier aboard, and it has four endings. Episodes 2 to 6 are one-line outlines for the model to write from.
• No pronouns are guessed for generated crew names; lines say "the courier" or use the name.
• test/season.test.ts, 6 tests: - every beat's kind is a real stop, and it has one flag per button (button counts come from options()) - a flag is only read after it's set - the last ending always fits - all 3x4x3x3 ways through episode 1 (including emergencies left to the captain) read without leftover markup and reach an ending
• Full suite: 220 passed, exit 0. tsc clean. Nothing is wired in yet and no player sees it; no deploy.
• Next, once the Anthropic key comes: the worker writes each beat's line from the outline plus the crew's flags, and falls back to these written lines.
• Finished 21:19

22:40: put the Anthropic key on the worker and prove it with one small call

• The key is in .git-credentials (it has the expected sk-ant- prefix). It was never printed.
• Proved the channel: one Messages API call to claude-haiku-5-5, max 20 tokens. HTTP 200; 16 tokens in, 20 out; service tier standard. Cost is well under a cent. The response file was deleted.
• Set it as the worker secret ANTHROPIC_API_KEY by piping it from the file into wrangler secret put. Worker secrets are now ANTHROPIC_API_KEY, ITCH_API_KEY and STATS_KEY.
• Docs, read 2026-10-22: - Prompt caching (platform.claude.com/docs/en/build-with-claude/prompt-caching): - The minimum cacheable prompt is 512 tokens for both Sonnet 5.5 and Haiku 5.5. - Put cache_control {"type":"ephemeral"} on the last system block. It lasts 5 minutes by default; "ttl":"1h" makes writes cost 2x. - A cache hit costs 0.05x input on Sonnet ($0.10/M) and $0.01/M on Haiku. - usage shows cache_creation_input_tokens and cache_read_input_tokens. - Structured outputs (platform.claude.com/docs/en/build-with-claude/structured-outputs): - Use output_config.format {"type":"json_schema","schema":...}. It's GA and needs no beta header. Both claude-haiku-5-5 and claude-sonnet-5-5 support it. - additionalProperties must be false, and minLength/maxLength aren't supported. - stop_reason "refusal" or "max_tokens" can break the schema, so the caller has to fall back.
• Still no monthly limit from the boss. The server cap will default to $20.
• Finished 22:41

22:41: the sale is over: count Bulkhead's sales and apply the 22 Oct decision

• itch-stats.sh: Bulkhead has 44 views, 4 downloads, 0 purchases, 0 purchase records. Hullbound 49/2/0, Derelict 62/0/0, packs 12/1/0 and 18/3/0.
• my-games: Bulkhead min_price 1200, sale None. can_be_bought False is the known false alarm (LEARNED, 25 Sep).
• Live page: Buy Now at $12.00. /purchase says "purchasing it for $12.00 USD or more". Checkout works; the price is still $12, not the $9 the boss planned.
• Applied the decision: Hullbound is the main work, Bulkhead is upkeep. Written into FACTS.md.
• Finished 22:41

22:42: the episode writer on the worker: one call per stop, capped, with the written lines as fallback

• app/src/crew/writer.ts: the system prompt is the house style plus the whole Season 1 outline, the same on every call (about 4.4k tokens, so it caches). The user turn is the part being asked for, the tags set so far, the names, this leg's earlier lines, and the game's plain line.
• Each call is claude-sonnet-5-5 with output_config: structured JSON {text}, effort "low", max_tokens 1200.
• A line is kept only if the stop reason is end_turn, it parses, it's 900 characters or fewer, it has no markup or em dash, and every number and name in the plain line is still in it. Otherwise the stop uses the plain line.
• app/src/crew/harbour.ts: - New tables: tales (crew, leg:part, text) and spend (month, usd, calls). - tell(): checks the session and the ask, returns the kept line if there is one, and otherwise calls the writer. - The writer stops at MONTHLY_CAP $20 a month and LINES_A_DAY 40 per crew. - Every call's spend is counted, and a line is kept only when there is one. - Deleting an account removes its tales. stats() shows tales, taleCrews and spend by month.
• worker: POST /api/crew/tell goes to the harbour with env.ANTHROPIC_API_KEY. The worker typechecks clean apart from the old range.js error.
• Real calls from this machine, through writer.ts: - First call: 200, but the line was null. Sonnet 5.5 used all 400 max_tokens on thinking (output_tokens_details.thinking_tokens 400). Docs (thinking-steering-and-cost, read 2026-10-22): thinking counts toward max_tokens, and effort is the lever. Set effort low and max_tokens 1200. - Second call: 200, 0 thinking tokens, 93 out, 4,372 cache read, $0.0017. The line kept the name, the 10 meals, the port and the bio, and added the sealed case. - Both calls together came to about $0.017.
• test/writer.test.ts, 9 tests: request shape and caching, what's a valid ask, what's a usable line, cost, a stubbed fetch failing every way, the harbour keeping lines and passing the earlier ones forward, the cap and the daily limit, a new month resetting, and delete. Full suite: 229 passed, exit 0.
• Not deployed: no page calls it yet. Next: the sim carries the episode (which beat, which tags), steers stops toward the beat's kind, and the page asks for the line and shows it in place of the plain one.
• Finished 22:52

23:00: set the writer's monthly cap myself, since the boss left it to me

• Set MONTHLY_CAP to $10, down from the $20 I had suggested. Why: - About $0.002 a line and 6 lines a voyage makes roughly $0.015 a voyage, so $10 is about 650 voyages a month. - Today Hullbound has about 15 desktop browsers in its events, so the real spend would be well under $1. - The cap only matters if something goes wrong (a loop, abuse, a spike), and the bill is shared with the boss's other projects. - Hitting it breaks nothing: the written and plain lines show.
• Raise it when the season pass sells: one $3.99 sale after fees pays for a couple of hundred voyages.
• Written into FACTS.md. Writer tests still 9 passed.
• Finished 23:00

23:01: episodes in the sim: each leg is an episode, its stops follow the beats, and the choices are remembered

• voyage.ts: - Tale {ep, beat, flags, alarm}. Each new leg begins the next episode if w.eps allows it (1 by default, so the first is free). Otherwise the stops come as usual. - dock() takes the beat's kind only when the voyage could have that stop anyway, after the same roll. arm() and alarm() do the same for the episode's emergency. - A beat stop carries s.beat. answer() and urgent() keep its tag whoever answers; a captain's -1 counts as the last button. - Arrival carries beat 'end' and sets w.told.
• sim.ts World: tale, told, eps. A world saved before this has none of them, plays on, and starts episode 1 on its next leg (tested).
• Found by the tests: the raiders' emergency could come before the courier had even boarded, so the hail would have asked for nobody. The episode's emergency now waits until its first beat has been told.
• test/season.test.ts, 4 more tests: - beats come 0,1,2 in order, at the right stops, on seeded voyages; most voyages get all three - the courier comes before the raiders - an emergency left to the crew still counts - episode 2 only with eps 6 - old saves
• Full suite: I wrote "233 passed" here and committed (4478041) without reading the result. It was 1 failed, 232 passed: test/voyage.test.ts assumed every starter crew member makes the first leg, and with the episode's stops steered, seed 7 now loses one on the way. The test now checks that pay is for whoever made it (made + lost = set out + joined - left) and doesn't assume a lucky seed. Rerun: 233 passed, exit 0. Not on the page yet.
• Finished 23:18

23:27: show the episode on the crew page: its title and opening, the beats' lines, the ending

• Done and live. At a beat's stop the page shows the written line at once (episode 1's own, or the plain one), asks /api/crew/tell, and swaps in the line that comes back. Lines are kept in the browser for the leg, and on the server per crew, so no stop is paid for twice. A guest without a session key yet gets the written lines until their first save makes one.
• The episode's title shows above the stop card all leg, and the opening shows with it until the first beat. At the port the ending and the hook come first, then where next.
• w.eps comes from Shipwright: 6 with it, 1 without. Without it, the port after episode 1 says the season goes on with Shipwright, in Settings, and counts tale-pitch-1. Each answer counts tale-<ep>-<part>-w (written by Claude) or -x (not).
• Fixed three gendered lines in the season: the trader was "he", the turned-away courier was "her", the bounty hunter "her". Now "the trader", "that courier", and "ready. Barely."
• Browser check with /api stubbed: an episode ran open, passenger, trade, alarm, sick, end, in that order, with flags carried forward (courier, ran, kept, clinic gave the courier-ran ending). Claude's line replaced the written one when the stub sent one, and the written one stayed when it sent null. The pitch showed with the shop on and not with it off.
• Tests: 233 passed, exit 0, read before this entry. Worker types clean apart from the old range.js one. Deployed worker and site.
• Live check: made a throwaway account, asked for the opening and the first beat, got both back from Sonnet (the beat kept "Hana Sato", "10 meals" and "Io", and used they/them), then deleted the account (200).
• Next: rebuild the Hullbound itch zip and the Android build so they carry episodes; then watch the tale- events and the month's spend.
• Finished 23:43

23:43: rebuild the Hullbound itch zip and the Android bundle with episodes in them

• Rebuilt both. The itch zip (276 KB, 27 files) has Sealed Cargo in its script and is live at /press/hullbound/hullbound-itch.zip.
• The Android bundle is now version 1.1, code 2, so it can go up even if 1.0 already went up. It's signed with the upload key, 5.2 MB, and live at /press/hullbound/play/hullbound-1.1.aab. The 1.0 file is gone from the kit, and the kit page says 1.1 replaces it and why.
• No code changed since the 233-pass run, only the kit page and the version number. Deployed the site and both files answer 200 at the right sizes.
• Finished 23:44

23:45: write episode 2 out in full, so a paid season still reads as a story when the writer is capped

• Done. Episode 2's fuel, shortcut and passenger beats and its stowaway emergency each have a written line now. Each keeps what the plain line says, the debris field's name included, and reads earlier choices: the shortcut remembers whether you paid the fuel seller, and the stowaway scene changes if the nurse is aboard. No em dashes, and no gendered pronouns for named people.
• The page passes {field} to both the written line and the writer.
• The season test now walks every path through episodes 1 and 2 (all buttons, plus leaving the emergency to the crew) and checks that each line and ending renders with no tags or doubled spaces left over.
• Tests: 234 passed, exit 0, read before this entry. Rebuilt the itch zip and the 1.1 bundle (still code 2, since it hasn't gone up), deployed the site, and both files answer 200 at the new sizes.
• Next: write episodes 3 to 6 out the same way, one at a time, checking each against the sim's own lines.
• Finished 23:53

23:54: write episodes 3 to 6 out in full, so the whole paid season reads without the model

• Done. All six episodes have a written line for every beat and emergency: 24 in all, plus the 17 endings. Each keeps the facts the sim's own line says for that stop (fuel's three ways to pay, the clinic's trade-off, the breach's seal-or-vent and its meals, the hail's parts) and reads earlier choices through tags. No em dashes, and no gendered pronouns.
• Changed episode 6's default ending. It said "you turned around", but the ship arrives at the station whatever is chosen. It now says the witnesses are asked about the deal with the company, and the trade beat warns that any deal there is a deal with the company.
• The path test now walks every way through all six episodes: 238 tests passed, exit 0, read before this entry.
• Rebuilt the itch zip and the 1.1 bundle (5,408,509 bytes) and deployed. Both answer 200 at the new sizes.
• Next: check the boss's mail and replies, then watch the tale- events and the month's spend on stats once players reach a beat.
• Finished 00:04