01:07: Greyling PDF and pictures get the new chair

01:07: Greyling PDF and pictures get the new chair

• People coming from the Greyling post land on /derelict-one-shot/ and download the adventure PDF, and that PDF still draws the bridge chairs the old way (the "toilets"). Rebuild the PDF and the three press pictures with the same script that made them, look at the bridge, bump ?v= wherever the PDF is linked, deploy, and fetch both live.
• Read mail/in first. Not before 11:07Z: the daily, by hand if it hasn't run.

03:07: The next upload round: what goes in and what's changed since 1.18

• Read mail/in. Then list what has changed in src/ since the 1.18 paid file was cut. Read how release.mjs makes a release and what it touches: the paid zip, the pack check, the examples zip and the /press/ links. Decide whether this round is 1.19 or a re-cut of 1.18.
• Build into the git-ignored folders only. Nothing goes to the boss in this entry. Write the round's file list and order on Next, so the next entry can build, check and hand over one round.

03:08: 1.20 words: README and the buyer's first-open line

• Write the 1.20 header and its new lines in release/README.txt, and point the buyer intro lead (main.ts) at 1.20, using only the changes listed on Next. Check each claim in the source before writing it, and keep the lines plain. Run tsc and the intro test if there is one. No release build in this entry.

04:00: Derelict analytics since the new zip went up

• The boss asked how the analytics look. Read the derelict-* pings since 20 Oct 19:00Z, when the new zip's first pings arrived, and split them by itch/site and by mode. Then itch-stats.sh for views, downloads and plays on both pages, plus the Greyling post's site traffic. Report numbers only, with no tuning yet.

04:12: The boss's raid-game idea: facts down, rules read, a first answer

• The boss has an older personal Play account, not a new one, and suggested Bulkhead as a game: build a ship to guard your loot, raid other ships for loot and rank, played like an Android app. Write their words into FACTS.md. Read RULES.md and SELLING.md for whether this counts as the same app or the next one. Then answer with a plan for the smallest loop that tests it.

04:14: Crew of 50 aboard: the boss's addition to the raid idea

• Add the boss's line, a 50-person simulation living on the ship that you protect, to the scratch note. Work out what it changes in the loop and in the smallest test, and how the existing room types map to the crew's needs. Answer the boss. Nothing built.

04:16: Before committing to the crew raid game: Play policy, channel, Chronicles

• The boss: "You can do whatever would make this sellable". RULES §7 comes before any build. Read Google Play's current policy on apps built from web content, and on billing for in-app items, from Google's own pages. Name the places a stranger would come across the game and check each one is open to a nobody. Look at side/chronicles (read only; no server, no live world) to see whether its sim can be borrowed. Write what holds into FACTS/LEARNED, and the commitment if it holds.

04:20: Crew sim core, first slice

• A deterministic tick sim in app/src/crew/: crew with food, sleep and air, rooms read from a Bulkhead ship (galley, quarters, life support), and walking along the ship's corridors. The same seed and ship always give the same day.
• Tests: the same seed gives the same result, a ship with no galley starves, and a long walk to the galley costs more than a short one.
• No page and no deploy yet. Commit if the tests pass.

04:23: Crew page: watch the crew live on a ship

• A dev-only page (app/crew/index.html, not linked or in the sitemap) that loads a generated ship or a #s= share link, draws it with the editor's renderer, and moves the crew around on it with the sim. Fast-forward buttons, a list of who's doing what, and the notes as a log.
• Check it in Playwright on a phone-sized screen. Deploying it waits until the boss has seen a screenshot.

04:43: Raids while you're away, in the sim

• Raiders board at the ship's airlock (Derelict's boardingPoint) on a seeded schedule, walk to the hold and make trips until their time runs out. A hold far from the airlock means fewer trips. Crew in the rooms they pass get hurt. Someone on watch on the bridge raises the alarm, and warned crew shelter in quarters.
• Each raid goes in the log with what was taken and who was hurt. The page shows the raiders.
• Tests: the same seed gives the same raids; a far hold loses less than a near one; a manned bridge means fewer hurt. Commit if they pass.

04:46: Your raid brings food home

• The other half of the loop: you board a ship in Derelict (today's daily, or a generated one) and the salvage you carry out becomes meals in your hold. Your crew keeps living while you're away.
• First in the sim and tests: a function that adds a run's take to the world, with a fixed exchange rate. Then a "Go raiding" button on the crew page that opens Derelict and brings the score back (same origin; local storage for now, the server later).
• Check that a crew fed by one raid a day lives a week while being raided.

05:00: Crew page goes live, noindex, with one practice haul a day

• The food hole: practice ships are unlimited, so their meals are too. Only the first practice haul of a UTC day feeds the crew. The rest come home with nothing, and the log says why. The daily ship always counts (it can be run only once).
• Put /crew/ in the vite build with noindex and no sitemap entry, so the boss can open it on a phone. Not linked from anywhere yet.
• Test: two practice hauls on one day give meals once; a daily and a practice both give meals. Check the live page loads and a ?crew Derelict run comes back to it.

05:07: Crew pings, so the first test can be read

• The boss asked for 20 minutes on something that moves the goal. The crew game's first test passes if a stranger comes back to check on their crew. Nothing measures that yet.
• Add pings to the crew page the way Derelict sends them: crew-view on a fresh ship, crew-back-<how long away> on a return, crew-haul-<meals band> when a haul is taken, and crew-raid when a raid link is clicked. Then teach events.sh to show them if it doesn't already.
• Test: the ping names, and no ping on dev. Ship it with the live crew page in one deploy, after the full suite.

05:24: Raids take a share of the stores, not a fixed count

• The boss asked: should a raid take a percentage set by the size of your stores, is it players raiding players, and how does a raid work.
• Answer them plainly (now: simulated raiders on a timer, not players). Then build the share: a raid takes up to a fixed share of what's in the hold. How much of that share they get out depends on the layout (how far the hold is from the airlock, whether the bridge warns). A full hold loses more meals but never all of them.
• Tests: a bigger hold loses more meals but the same share; a far hold still loses less; the week-long fed test still passes.

05:33: Crew accounts and a ship saved on the server

• First slice toward players raiding players. The boss asked for accounts so a player can move browsers.
• Server: one Durable Object, the harbour, with SQLite. An account is an id plus a hash of a random secret key; no email, no password. The ship and crew world are saved under it.
• API under /api/crew/: POST account (makes one, returns id and key once); PUT ship (auth, size capped); GET ship (auth).
• Crew page: on the first save it makes an account and keeps the key in this browser, then saves to the server every few minutes and on leaving. "Play on another device" shows a link (/crew/#k=...) and a QR code. Opening the link signs that browser in and loads the ship from the server; the key is wiped from the address bar.
• Known hole for now: the client runs the sim, so it could lie about its hold. That matters once ships raid each other, and the fix goes with that slice (the server replays it).
• Tests: the API on the worker test harness, if there is one, else the harbour's logic as plain functions. Then a browser check on dev, and live after deploy: make an account, open the link in a second browser context, see the same ship.

05:48: A real login: email and password, and Google

• The boss, mid-build: "No we need just a regular ass login, and Google, especially if this does end up on the play store". The key-in-a-link account goes; the server save and the version checks under it stay.
• You can still play without logging in. A guest gets an account behind the scenes on the first save. "Make an account" puts an email and password on it, so nothing is lost. "Log in" on another device brings that ship over. Google sign-in does the same through Google.
• Server: accounts (id, email, password hash, Google id), sessions (hash of a random session key, account). Passwords go through PBKDF2-SHA256 with a salt, at the most rounds Workers allow. Failed logins are limited per email. Logging out ends the session.
• Google: Sign in with Google (Google Identity Services) in the page. The worker checks Google's ID token (signature against Google's keys, audience, issuer, expiry). That needs an OAuth client ID from a Google Cloud project on the boss's account, so I read Google's docs first and date them. Everything is built and tested against a fake signer, and the ask comes once.
• Password reset needs a way to send email, and we have none. I read the options and their docs (Cloudflare's own sending first) and put it in the same ask. Until then there is no "forgot password", so the page says to add Google as a second way in.
• Tests: sign-up, log in, wrong password, the lockout, a guest turned into an account keeping the ship, log in on a second browser, logout, and a Google token: good, wrong audience, expired, bad signature.

05:52: Forgot password, by mail from our own domain

The boss says the account should be on Workers Paid, which is what Cloudflare's Email Sending (beta) needs to mail any address. After the login is in: read the send_email docs for setup (sender domain onboarding, DNS), add a reset link that mails a one-time code valid 30 minutes, and test it to an address of ours. If the binding won't deploy or the mail never comes, say so and leave reset out.

06:08: Parts, a hold that fills, and a ship that grows

The boss asked for more resources, upgrades like bigger food stores, and in time a whole second deck. My design: a second resource, parts, that every derelict raid brings home along with food. The cargo hold's size caps how much food the ship can keep, so a bigger hold is the first thing worth parts. Every new room or square costs parts, and a second deck costs about a week of good raids. A survivor you rescue on a derelict joins your crew. Start ships small (one deck, a few rooms, 6 crew) so there is somewhere to grow. Build it after the login is live: sim and haul first, with tests, then the build screen on /crew/.

06:32: The crew's clock runs on real time

Before raiding other players (which needs the server to replay each ship, so stores can't be faked): the first test is whether a stranger comes back to check on their crew, and that only means something if time aboard is real time. Today the page runs the ship 60 times faster while you watch and has a "+1 day" button. Change: a ship's clock is the wall clock since the crew started, so coming back after 8 hours finds 8 hours gone. The speed buttons and +1 day stay only under ?t= for looking at, and older crews carry on from where their clock stands. Tests, a check in the browser, deploy. The server replay comes after, then the itch page. The 21 Oct daily runs by hand after 11:07Z if it's missing.

06:40: A name and a way in for the crew game

The first test is whether a stranger comes back to check on their crew, and today nobody can find the crew page: it is linked from nowhere and is called "CREW". Before the server replay (needed only once ships raid each other): give the game a name that isn't taken on itch or the app stores, a proper title, description and share card, and two ways in. One is from Derelict's end card, so people who already raid derelicts learn their haul can feed a crew. The other is a line on the Bulkhead page. Nothing posted anywhere; the itch page is the step after, and that's an ask for the boss once it's ready.

06:53: Hullbound as an itch web game, ready for the boss to upload

• Find out how the Derelict itch zip is built and whether the same approach works for the crew page. The crew page talks to our worker (login, saves) and sends raids to /derelict/, and inside itch's iframe both are on another origin.
• Build a zip that runs inside the itch frame, try it in a local iframe on a foreign origin, and write the page text. Nothing goes to the boss until the zip is verified; then it's one batched ask.

07:12: Reset mail from [email removed]

• The boss on the from address: "address doesn't matter to me". I'm using [email removed]. Write that in FACTS.
• See whether the domain is onboarded for Email Sending yet (the cf-bounce records in public DNS). If it is, add the send_email binding and MAIL_FROM, deploy, and send one reset to an address that reaches the boss, who confirms it arrived. If not, everything waits for the onboarding; nothing goes live half set up.

07:20: Google sign-in with the boss's client ID

The boss sent the OAuth client ID (Web application). Put it in wrangler.jsonc vars as GOOGLE_CLIENT_ID (a client ID is public: Google's button needs it in the page), check how the worker verifies Google's token against it, run the harbour tests, deploy, and see that /api/crew/config answers with it and the button renders on /crew/. A real sign-in needs a Google account in a browser, which I don't have, so that last step is the boss's: one tap on the button, and say whether it lands on their crew.

07:22: A home page and privacy policy Google will accept for Hullbound

Google won't publish the consent screen without a home page URL and a privacy policy URL. The home page is /crew/. Read public/privacy/index.html: if it doesn't cover crew accounts (email, password hash, Google's id, the saved ship, reset mail), add that section, deploy, and give the boss both URLs.

07:29: Swap in the boss's second Google client ID

The boss sent a different client ID and said to use it. Replace GOOGLE_CLIENT_ID in wrangler.jsonc, harbour tests, deploy, and check config and the button on the live /crew/.

07:41: Does Hullbound get counted like Derelict?

The boss asked whether the crew game is tracked and analysed like Derelict. Compare what the crew page sends (page views, /e/ events, harbour accounts) with what Derelict has (board, events.sh, visits.sh, status), run the numbers that exist for today, and answer with what's missing.

11:07: Count a stranger's return even if their first look was short

The account is made at the page's first two-minute save. Someone who looks for a minute, leaves, and comes back tomorrow gets an account made tomorrow, so the stats would say they never came back: the one number Hullbound's first test rests on. See whether the saved world carries its own real start time; if it does, measure "back" from that on the server (no zip change). If not, the page saves early instead and the zip is rebuilt.

11:09: The 21 Oct daily, by hand

Crons are paused and it's past 11:07Z. If today's derelict isn't out, run scripts/host/daily-host.sh in the background to .daily-log, then npm run status, check meta.json has today's Bluesky URL, no-keys, commit and push. No deploy, nothing else posted.

13:07: A reason to come back at a time

Hullbound passes its first test if a stranger comes back. Look at what the page tells a player about when to come back (the next raid, how long the food lasts) and what it shows on return. If it gives no time to come back to, add one line: food lasts about X, raiders expected around Y, from the sim's own numbers. Test, deploy, rebuild the zip.

13:20: The crew page's intro only until you know it

The boss asked whether all that writing is on screen the whole time. It is: the six-line intro shows on every visit. Show it on a new crew's first visit only, after that fold it behind a small "How it plays" toggle, keep the one-line food forecast. Test on phone, deploy, rebuild the zip.

13:27: Hullbound gets a voyage: a destination, stops, and choices

The boss asked whether the ship is going anywhere and suggested bases to refuel at, with decisions that change things for each ship (their idea, in FACTS). It isn't going anywhere now. Smallest version: a voyage to a named destination some real days away, a stop at a base about once a day where a choice waits for the player, and an arrival that ends the voyage with who made it, then the next leg. Fold in the story pieces (a line per crew member, survivors keep their wreck's story, a report on return). Design first in this entry, then build in steps, each tested and deployed.

14:00: The Hullbound press folder gets a page of its own

• The boss opened /press/hullbound/ and got the 404: I gave a folder, not a page. Add public/press/hullbound/index.html showing the cover, the five screenshots in order with what each shows, the zip and logo as downloads, the settings and the description with a copy button. noindex. Deploy, check it live, commit.

14:02: A Hullbound logo with the name on it, from the image generator

• The boss: "The logo needs the name on it. You should use the image generator. It wouldn't hold up on play store". That is their go-ahead for AI art on Hullbound (until now drawn by code), for the logo.
• Generate the emblem with the image model (a few tries, cents each, inside the art budget), set the name HULLBOUND on it in a real font by code so the letters are exact, export a 512 x 512 store-style icon and a 120 and 315 x 250 for itch. Look at it small. Put it on the press page and the crew page's icon if it reads. AI disclosure on the itch kit then includes Graphics. Record the spend.

14:19: Hullbound is on itch; a jam entrant asks whether walls cost air in Derelict

• The boss made https://bananafestdestiny.itch.io/hullbound (no logo on it; itch has no slot that needs one). Play it there in a phone and a desktop browser: the embed starts, the voyage shows, the raid links work inside itch's frame, no page errors. Add it to the itch stats.
• A jam entrant's post on Derelict's jam topic: a first run made sense from the landing screen alone, but they couldn't tell whether pressing into a wall costs air ("over about 16 presses the air only moved 5"). Check in the code what a bump costs, put one line on the board that says so, test, deploy, and make one new Derelict zip for the boss. Draft a short reply for the boss in their voice. They also asked for a run of their own jam game in return: that is the boss's call, and I don't rate entries.

14:35: Derelict's numbers, then Greyling's

• The boss asked for Derelict's numbers before the Greyling read: runs and players by day from the event pings, the jam and itch views, the board. Then Greyling.

14:50: The boss's Greyling insights, 17 h in

• Write the boss's Reddit insights into FACTS, set them against our own counts for the same window, and write what that says into LEARNED.

15:01: Has anyone come back to their Hullbound crew

• Run crew-stats.sh (the harbour's own counts: accounts, saves by day, back after N hours) and set it against the crew- pings by hour. Leave out my own and the boss's accounts where they can be told apart.

15:03: A Hullbound cover as strong as Derelict's

• The boss: Derelict's cover is much cooler, and Hullbound was only published half an hour ago, so this morning's crew pings were draft-page visits, not strangers. Correct that in actual.
• Try a cover built round the logo's ship art (already made and allowed) with the same layout as Derelict's: dark, one strong picture, the name in yellow. Show it to the boss. A new generated picture needs their say first.

15:07: An email when the ship docks, for players who ask for it

• Opt-in, only for accounts with an email: when the ship docks at a base or reaches port and a choice waits, one email says where and what, with a link back. At most one email for each stop, none if the player is already on the page.
• The page knows from the seeded sim when the next stop is; it sends that time with each save, and the harbour sets an alarm for it. Test it in the sim and against the local worker, then deploy.

15:14: A devlog post, drafted for the boss

The boss: "we need to post in the devlog". Find which devlog we have (itch pages), draft one post in plain words about what changed, host it under press with a page, and give the boss one link to paste from. I don't post it.

15:25: The reply to the Derelict comment, found for the boss

The boss asks what the reply was for the comment on Derelict. Find the draft I wrote at 14:19 and give it back as is.

15:28: The boss says both are done; check the zips, the devlog and the reply on itch

Read from outside what is now on itch: which zip each game serves (size and date from the uploads API, no ids or md5s), whether Hullbound's devlog is up, and whether the reply is on the jam post. Then play each from itch's frame for the new lines.

16:00: Is there sound in the games

The boss asks whether the games have sound. Search the Derelict, Hullbound and editor code for audio and answer from what's there.

16:01: A soundtrack for the crew page, like a Super Nintendo game

The boss: "crew page needs a soundtrack, like a super nintendo game or something". Write it in code with WebAudio like Derelict's, with no files: a looping tune with a pulse lead, warm pad chords, a bass, an arpeggio and light drums, through a SNES-style echo and a muffled top end. It starts on the first tap, stops while the tab is hidden, has a Music on/off button that is remembered, and goes quiet while a raid is open in Derelict. Test it in a browser (no errors, the button works), deploy, rebuild the Hullbound zip and put it in the same upload ask as the tick box.

16:50: The boss on the music: "its perfect"

Write it into FACTS, with what was approved (the tunes as rendered at /press/hullbound/music/), and what I take from it into LEARNED. Then the itch description gets a line about the music for the next paste, batched with the zip.

17:02: Derelict's numbers, since the 14:35 read

The boss asks how Derelict is doing. events.sh since 14:30Z and since 04:00Z, the board for today, itch-stats, and the jam page. Compare with the 14:35 read: 115 boards (113 from one GB browser), 101 practice runs ended, 1 daily run, itch 31 views.

17:03: The one player in GB who boards most of Derelict's ships

The boss asks what's up with them. From the request log only, grouped by hour, never naming anyone or keeping their agent: when they started, how steady the play is, how the scores move, how fast runs end, whether it looks like a person or a script, and whether they ever touch the daily, Hullbound or the editor.

17:06: Why the GB browser plays Derelict like a script

The boss wants to know why. Checks I can do from here: does its first visit line up with Derelict's jam submission or a jam event; does its Chrome version match a Playwright or other automation build; what the jam's pages say about bots or AI playtesting; which daily ships and query strings it opened. What the game could add: a flag in the run ping when the browser says it is automated (navigator.webdriver), and the pace of keys. And what only the boss can see: itch's referrers for Derelict.

17:10: A robot flag on Derelict's board ping

The boss: "Spend the next 20 minutes doing something that will help accomplish your goal." The logs can't settle whether the GB player is a person or a script: it reloads the page between boards, but so does the "again" button. One cheap ping settles it from now on.

• On boarding, Derelict also pings derelict-robot when navigator.webdriver is true, and pings the first input kind (mouse, touch or keys) once per page. No id and nothing new stored; the privacy page already covers bare event pings.
• tsc, the game tests, build, deploy, and a fresh Derelict zip next to the Hullbound one, so the boss uploads both in one go.
• Tell the boss what the timing says now: it looks more like one keen person grinding the practice career than a script.

17:16: Check the Derelict upload with the robot flag

The boss: "Ok derelict is up". Check what itch serves for Derelict (filename, size, date only) and that the served build has the flag in it. Hullbound's zip is still the old one, so check that as well.

17:29: Watch for the UK player's first flagged session

The boss: "let me know when you know what's up with uk player". Their sessions so far were lunch, afternoon and evening UK time, so the next one is likely tonight or tomorrow lunchtime.

• A background watch polls Cloudflare every 5 minutes for Derelict pings since the 17:16Z upload. It matches the player by the same browser hash as before, or by the address that browser used (compared inside the script, never printed).
• It stops when a robot or input ping from them shows up, or after 15 boards with neither (an old tab still open, or a script that clicks through JavaScript). It gives up after 20 hours.
• Then tell the boss what it says, write the actual entry and commit.

17:35: What videos are up for the socials

The boss: "Do you have any videos submitted for the socials". Read the docent media channel memory, list what's under /media/ (live and in the repo), with dates and what each shows, and say what's missing (Hullbound, the soundtrack).

17:50: A Hullbound clip for the docent, and ask whether the first three went out

The boss, on recording a Hullbound clip: "What do you think?" Yes: Hullbound's test needs strangers, and a short clip costs little. But §7 says prove the channel first, and I don't know whether any of the three videos posted. So both:

• Read MAIL.md and the docent's latest mail, then send the docent one letter: did any of the three post, and where. Offer the Hullbound clip.
• Record the clip: real capture of /crew/ on the live site, 1080x1920, 30–50 s, sound off. A raid on screen, then the ship docked with a choice waiting. Publish media/hullbound-raid-and-dock-<date>.mp4 + .json (product Hullbound, a claim backed by public pages, no sales).
• Deploy, check both URLs, write it up, commit.

18:26: The UK player story: tell the docent, draft a dev.to post

The boss: "We need to tell docent about this. This is a brilliant dev.to post". Find what FACTS says about dev.to (account, who posts, rules), then write the post as a draft the boss can paste, hosted under /press/. Mail the docent the story and the link. No visitor details: no address, no full agent string, no country beyond "the UK".

19:07: Practice in front of daily players; the privacy link

The boss: "Spend the next 20 minutes doing something that will help accomplish your goal." Derelict's one devoted player came for practice mode. Most players play the daily once and leave. So:

• Read what the end screen of a daily run offers and how "again" is worded. Check the pings for how many daily players ever board a practice ship.
• If practice is buried, make it the first thing offered after a daily run: say what it is (a fresh ship, as often as you like, credits buy upgrades). Then test, deploy and make a new Derelict zip.
• Small and owed: link /privacy/ from the home page footer (the docent's served-check). The /api/crew/config "mail" flag stays, because the page needs it to show the email tick box and the UI already says mail is sent. Tell the docent that in a later letter, not now.

19:18: Offer practice to a daily player when their run ends

• The one player who kept coming back came for practice mode, but a daily player only finds it under "Practice on another ship" at the end. Read what the end screen says after a daily run, and if practice is only that one button, add one line saying what practice is: endless ships, nothing counted against the day. Then test, deploy, and add it to the same zip round if the boss hasn't uploaded yet.

19:26: Is the UK player still playing

• The boss asked. Read the Derelict pings since 18:00Z (practice-itch boards, input-keys) and say when the last one was.

19:43: The boss's r/ClaudeCode post about the UK player: is anyone coming to Derelict from it

• The boss posted "Update: Business Bots" on r/ClaudeCode at about 18:35Z: 2.7K views in 55 min, 3 upvotes, 3 comments. It names Derelict on itch but has no link. See whether Derelict boards and itch views since 18:30Z went up, outside the UK practice runs.

21:07: Make the most of the r/ClaudeCode readers

• The boss's post is still being seen, and its comments may have questions the boss could answer. Read the thread through Reddit's public JSON (no login). Draft short replies in the boss's voice for any questions, and look at what a reader sees on the Derelict itch page: does it lead anywhere (Bulkhead at $9 until 22 Oct 22:00Z, Hullbound)? Check boards since the link comment.

23:07: Where Derelict and Hullbound players go next, and what to fix in the way

• Read clicks.sh (does anyone use the Bulkhead card under a Derelict run?) and crew-stats.sh (has any Hullbound stranger come back?). Then fix the weakest step I find, if it's small.

Next

• 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: Greyling PDF and pictures get the new chair

• mail/in was empty.
• Built the paid single file from today's source (npm run build:paid, into the git-ignored dist-single) and exported the Greyling one-shot from its own ship file the way pack-check does: File, Open, One-shot. A first try in the dev-server demo got no download, so the demo was not used.
• The text is identical to the live PDF, line for line, still 8 pages. Page 3 (upper deck GM map) side by side: the bridge and galley chairs were the round "toilet" seats and are now armchairs. Nothing else on the map moved apart from compression edges.
• Live now: /adventure/rsv-greyling-adventure.pdf (?v=1005 on all five links on /derelict-one-shot/, and the bare URL also serves the new file), /derelict-one-shot/page-gm-map.webp ?v=1004 (re-cut from page 3 at the same 1287 x 910), and /press/greyling/greyling-upper-deck.png (same 220 dpi and margins; the lower deck and room key came out pixel-identical, so they were left alone). Each one was fetched live and matches the local file in size; the upper-deck PNG matches byte for byte.
• Still old: bulkhead-examples.zip (its PDF and both .dd2vtt maps), the paid 1.18 file, the Eight Derelicts pack, the free packs and the itch zip. Those are files the boss uploads, so they go with the next release, not now.
• Finished 01:11

03:07: The next upload round: what goes in and what's changed since 1.18

• mail/in was empty.
• itch already has 1.19: the 14 Oct build, uploaded by the boss 15 Oct 02:37Z (per the 15 Oct actual). It sits beside the 3 Oct eight-derelicts zip and the examples zip, the latter 816088 bytes, the same as ours. So this round is 1.20, not a re-cut.
• Editor changes since 1.19 (git log, src without game/): three generator commits on 15 Oct (station shapes, spine cut back, cross corridors), the 17 Oct VTT jump, the 20 Oct Play it in Derelict and notes hint, and the 20 Oct chair. The sale-week price commit only touches the site; set-price.mjs is a manual script, so nothing flips the price back to $12 by itself on 22 Oct.
• release.mjs already defaults to 1.19. Its steps: build:paid, stage bulkhead.html with README.txt, zip into the unlisted rel- folder, then paid-check and pack-check. README.txt and the buyer intro (main.ts ~1390) still say 1.19.
• The round's list, with its order and the checks for each file, is now on Next. Nothing was built or sent in this entry.
• Finished 03:07

03:08: 1.20 words: README and the buyer's first-open line

• README.txt now heads Bulkhead 1.20. "It does not send anything anywhere" now says "unless you press Play it in Derelict". GENERATE A FLEET gains a "New in 1.20" paragraph: cross corridors give straight, cross and H outlines, long decks end past their last room, and stations come in more than one shape. New section PLAY IT IN DERELICT: it's under File; Salvage:/Log fragment:/Hazard: notes in numbered rooms; it needs an airlock in the hull or a hole in it.
• Checked against the source before writing. The boarding point is the first hull airlock, else an open breach (engine.ts boardingPoint). With neither, the game page says "This ship has no way aboard" and links back to the editor; my first draft said the button warns, which it doesn't, so I fixed it. Hazard: notes are read by engine.ts. In the paid file, the button opens the live site through HOME.
• The buyer intro lead (main.ts) is now "New in 1.20: press Play it in Derelict, under File, to walk your own ship in the free daily roguelike", followed by the one-shot line as before. release.mjs defaults to 1.20. tsc ok. No release built.
• Finished 03:08

04:00: Derelict analytics since the new zip went up

• Since 20 Oct 19:00Z (events.sh): 33 boards (32 practice, 1 daily), 33 runs ended (32 practice, 1 daily), all from inside the itch frame. No derelict pings from the site itself. No share, no share-vs, no card-bhDraw and no Bulkhead click. The one daily run "left" at once (0 score, 1 room of 11).
• Practice results, counted from the run- pings: 32 runs, 28 out, 3 dead, 1 left. The score bands of the runs that got out were 20, 50 and 100. They entered a median 4 of 8 rooms. 9 of 32 read no log and 4 read all three.
• Grouped by hour, country, device and a 4-character hash of the user agent (a temporary copy of events.sh, now deleted; no IPs or agents written down): one desktop browser in GB made almost all of it. It played 10:00 to 21:59Z on 20 Oct with about 120 boards, including all 32 since 19:00Z. Everyone else on 20 to 21 Oct was 1 or 2 boards each: FR, US twice, BE phone, GB once, and BR at 03Z today.
• itch-stats: derelict 23 views, 0 downloads (browser game). Bulkhead 44 views, 4 downloads, 0 purchases, the same as the 22 Oct baseline.
• Greyling post: since 22:00Z yesterday, 3 views of /derelict-one-shot/, 1 home and 1 /deck-plan-generator/. The one editor visit came from m.facebook.com, not Reddit.
• Finished 04:01

04:12: The boss's raid-game idea: facts down, rules read, a first answer

• mail/in empty. The boss's words are in FACTS (21 Oct): an older personal Play account, the raid-game idea, and a business developer account with no testing requirement.
• Read Google's help page on testing requirements: 12 testers for 14 days applies only to personal accounts created after 13 Nov 2023. Read Chrome's TWA page (last updated 2020): a TWA needs the site to meet the add-to-home-screen bar and Digital Asset Links. That page does not cover Play's current policy on web apps, which still needs reading.
• RULES §1: Bulkhead is ready to sell, so a next app is allowed. §7: the channel has to be proven and written in FACTS before committing. §5: I open no store accounts; the boss already has one.
• Wrote scratch/2026-10-21-raid-game.md: the loop (build, raid, defend, rank), what exists, what's new, open questions, and the smallest web-first test. Nothing built.
• Finished 04:13

04:14: Crew of 50 aboard: the boss's addition to the raid idea

• Added a crew section to scratch/2026-10-21-raid-game.md. It covers: what you protect is people; the existing rooms as needs (galley, quarters, medbay, life support, engineering, cargo, bridge); layout as the game; catch-up while away; logs written from what happened to your crew; a deterministic tick sim, so the server can replay raids; and a smaller first test (12 crew, three needs, two raids while away).
• Finished 04:14

04:16: Before committing to the crew raid game: Play policy, channel, Chronicles

• mail/in empty.
• Google Play, read 21 Oct: the 12-testers-for-14-days rule is for personal accounts made after 13 Nov 2023, so the boss's business account is clear. Minimum functionality: "stable, functional, and provide meaningful content"; Google's 2020 blog calls webview-only traffic apps spam. Digital items sold inside the game need Play billing.
• Reddit blocks this machine entirely (curl, Playwright, WebFetch). Read through WebSearch and a redlib mirror instead: r/incremental_games now allows a developer one post every 30 days, each linking something playable, and sends unfinished games to Feedback Friday. Couldn't read r/AndroidGaming's rule.
• Chronicles looked at read-only: the agent model (drives, illness, bonds) is right for the crew. Its LLM narrator and Firebase aren't, so I'll port the ideas rather than the code.
• Wrote the 21 Oct quotes, the dated findings and the commitment into FACTS.md, plus a LEARNED section. The scratch note now covers "keep the daily" (the daily ship is everyone's shared raid), what to take from Chronicles, and where a stranger meets the game.
• Committed: the crew raid game is the current app's next form. The editor stays on sale at $9.
• Finished 04:19

04:20: Crew sim core, first slice

• app/src/crew/sim.ts: one tick is a minute. Crew have food, sleep and health; air is ship-wide. A room's job comes from its name in the key (galley, quarters, life support, medbay, bridge, engineering, cargo). Walking times come from Derelict's own distances() between room stations, at 2 squares a minute, so layout costs time. Meals come out of the hold's stores. Names, jobs and starting needs come from a seeded RNG, so a run is repeatable.
• Peeking at the numbers found three faults, all fixed. (1) Most generated ships have no room named Life support, so every crew suffocated; engineering now makes the air on those ships, and air workers are capped at one per four squares of the air rooms. (2) With no galley, hungry crew paced between bunk and work: about 10 hours of walking a day on a corvette, down to about 30 minutes now. They only break off for a need the ship can meet. (3) The medbay healed starving crew forever; nobody heals on an empty stomach now.
• After the fixes: an intact freighter with 12 crew lives 3 days and empties its hold at about hour 60. A station with 50 crew does the same around hour 62. A shuttle with no galley loses its crew at about hour 41.
• test/crew.test.ts, 8 tests, all pass: the same seed gives the same world; a good layout keeps 12 alive for 2 days; no galley (even with a medbay) starves everyone in 4 days; no air room suffocates; stores run out; a galley 30 squares further off more than doubles the walking; it runs on a generated freighter. tsc is clean.
• Nothing in the existing app imports it yet; no page, no deploy.
• Finished 04:23

04:23: Crew page: watch the crew live on a ship

• mail/in empty.
• app/crew/index.html and app/src/crew/page.ts: the ship is drawn once per deck with the editor's renderer, and the crew are dots coloured by what they're doing. Walkers follow the real corridor path, worked out downhill on Derelict's distance map, so they go through doors rather than walls. There's a deck switcher, speeds of 1 min, 1 hr and 10 hr a second, Pause, +1 day, a crew size of 12/25/50, New ship, the log, and the crew list with food, sleep and health bars. It reads ?size, ?seed and ?crew, or a #s= share link from the editor.
• The sim now records where each walk started and how long it is (from, trip), for drawing only.
• Playwright at 390x844: a freighter with 12 crew and a station with 50, two days each. No page errors, no sideways scroll, nobody died.
• What it shows: on an intact ship with full stores nothing happens for days ("Nothing has happened yet"). The crew alone isn't a game. Raids and running short of stores are what make the story, so they come next.
• The page isn't in the build, so /crew/ is 404 live. Deployed only the screenshot: https://bulkhead.bananafest-destiny.com/press/crew/crew-first-look.png (200, image/png).
• Finished 04:42

04:43: Raids while you're away, in the sim

• mail/in empty.
• sim.ts: three raiders board at Derelict's boardingPoint, 17 to 31 hours apart, on a schedule drawn from the world's own RNG state, so a replay gives the same raids. They head for the hold nearest the airlock (the galley's stores if there's no hold). Each raid lasts 45 minutes, and they make as many trips as the walk allows: at most 3, so 36 meals, one day's food for 12. Anyone on watch on the bridge sends the crew to shelter in quarters. If nobody is, crew in the rooms the raiders cross lose 45 health and can die. A ship with no way aboard gets cut into at the hold. route() moved from the page into the sim.
• 3 new tests, 11 in all, passing: the same raids on every replay; a hold 12 squares further from the airlock loses less; a bridge means fewer hurt (6 seeds, 4 days each). tsc clean.
• On generated ships the bridge sees most raids coming, and the airlock-to-hold route runs along corridors, so few crew get hurt. Every crew starves by about day 4, because nothing brings food in yet. The player's own raids are meant to fill that gap.
• Page: raiders are red diamonds going back and forth on the route, sheltering crew are pink, the log says what was taken and who was hurt, and ?t=raid jumps to just after the first raid. Playwright at 390x844, freighter and station: no errors. Screenshot: https://bulkhead.bananafest-destiny.com/press/crew/crew-raid.png (200).
• Finished 04:46

04:46: Your raid brings food home

• Built. A Derelict run started from the crew page (/derelict/?crew or ?practice&crew) leaves its score in this browser (crew-haul, src/crew/haul.ts). The end screen says "Take N meals home to your crew", or "Back to your crew, empty-handed" on a death. The crew page takes every waiting haul on load and adds it to the hold, with a log line: "You came home from the Wren with 37 meals."
• One meal per 10 points. Par over 40 generated ships: min 140, median 370, max 585. So a par run is about 37 meals, a day's food for 12.
• Raids cut back to match: 3 raiders, 3 meals each, at most 2 trips, so 18 meals at most a raid (was 36, a whole day's food). With raids every 17 to 31 h, a crew of 12 fed one par run a day lives a week (test, 5+ raids). Unfed, more than half are dead by then (same test).
• The crew page now keeps its ship in the browser (crew-world). Coming back, it runs the minutes you were away, up to 3 days, and says "You were away 5 h 12 min, and the ship lived on without you." This is the first-test loop: come back to check on them.
• Checked in a browser on the dev server: crew page, then Raid a practice ship, board, leave at once, then the empty-handed link. A par haul was added by hand next to it. Back on the crew page: 108 to 144 meals, both log lines, and the haul store emptied. No page errors.
• Picture: https://bulkhead.bananafest-destiny.com/press/crew/crew-haul.png
• Hole: practice runs are unlimited, so food is unlimited. Not fixed in this slice. The fix goes in the next plan.
• Tests: crew 14 (3 new); full suite 158 passed, 444 s; tsc clean. Deployed. /crew/ is still dev only (not in the build), so live ?crew links lead nowhere until it ships.
• Finished 05:00

05:00: Crew page goes live, noindex, with one practice haul a day

• Done. Only the first practice haul of a UTC day feeds the crew. Later ones come home with nothing, and the log says "only one practice ship a day feeds the crew. Raid today's ship, or come back tomorrow." The Derelict end screen says so too, before you go back. A haul from the daily ship always counts. The day is kept in crew-fed (src/crew/haul.ts ration/takeRations).
• /crew/ is in the build and live: https://bulkhead.bananafest-destiny.com/crew/ . It is noindex, not in the sitemap and not linked from anywhere. It got a two-line intro for someone who lands on it cold.
• Checked live on a phone-sized browser with pings blocked: crew page, a practice raid, the "empty-handed" link back, and the log line, with no page errors. On the dev server, two practice hauls in one day: 30 meals, then the once-a-day line.
• Finished 05:17

05:07: Crew pings, so the first test can be read

• Done, in the same deploy. The crew page sends bare GETs, live host only: - crew-start: a first ship in this browser. crew-new: New ship, or the crew count changed. - crew-back-<lt1h|1to8h|8to24h|1to3d|3d+>: came back after 5 minutes or more away. This is the first test's number. - crew-haul-<none|lt20|20to39|40+|over> - crew-raid-<daily|practice> on the raid links.
• Derelict sends derelict-crewhome-<mode> when a run started from the crew page ends, plus a view ping on /crew/. events.sh already lists every /e/ path, so they show with no change.
• Tests: crew 16; full suite 160 passed, 475 s; tsc clean.
• Finished 05:17

05:24: Raids take a share of the stores, not a fixed count

• Answered the boss. Raids are simulated, on a timer, not players. Players raiding players is next, with accounts (the boss asked; see below).
• Built. A raid takes up to 20% of the hold (SHARE in src/crew/sim.ts) if the raiders make both trips, and 10% if a far hold leaves time for only one. The fixed 3 meals each is gone. A full hold loses more meals, and none is ever emptied.
• Measured: 12 crew eat about 43.5 meals a day (14 simulated days, 3 seeds). At 10 points a meal, a par run (37 meals) could not keep up once raids took a share: the hold hit 0 by day 6 and 2 to 4 crew died. Now 6 points a meal, so par is 61 meals. With one par run a day the hold settles at 40 to 60, about a day's food, and nobody dies in two weeks.
• Tests: crew 17 (new: a share of the hold, more from a full one, never all of it); full suite 161 passed, 439 s; tsc clean. Deployed.
• The boss asked about accounts ("what if they want to play on a different browser"). My answer: yes, once the ship is on the server. First an account with no email or password: the server makes it on the first save, and a "play on another device" link or QR carries the key. Later, Google sign-in, which needs an OAuth client on the boss's account. That is one ask, made only once people are playing.
• Finished 05:33

05:33: Crew accounts and a ship saved on the server

• Built the server save: one Durable Object (SQLite) holds every crew's ship under an account, and saves carry the version they were built on, so a tab left open on another device is told no (409) and takes the newer copy instead of overwriting it. Checked locally with two browsers.
• The key-in-a-link way to move devices was replaced the same morning by a real login (next entry), on the boss's word. The save and version checks under it stayed.
• Finished 05:59

05:48: A real login: email and password, and Google

• Live on /crew/. Anyone can still play as a guest. "Log in or make an account" opens email and password: Make an account puts a login on the guest account, ship and crew included, and Log in on another browser brings that ship over. Log out removes the account, ship and crew from that browser.
• Passwords are kept only as salted PBKDF2-SHA256 hashes (100,000 rounds). Ten misses on one email lock it for 15 minutes. Sessions are random keys, stored only as hashes, one per browser.
• Sign in with Google is built: the server checks Google's signature (keys from Google's JWKS, cached for as long as Google says), the issuer, our client ID and the expiry, and stores Google's account id, not the name. The button stays hidden until there is a client ID. The boss said they'll set up the Google client and Email Sending.
• Forgot password is built too: one link at a time, 30 minutes, one mail per address every two minutes, and using it ends every other session. It stays hidden until the site has a send_email binding.
• New /privacy/ page (Google's consent screen needs one): what we keep, Cloudflare as host, and support@ for deleting an account.
• Checks: 10 harbour tests (sign-up, login, wrong password, lockout, guest to account, Google tokens good and bad from a generated RSA key, reset). Full suite 171/171. Two browsers against the local worker: same crew after login, wrong password refused, an open tab takes the newer save, logout leaves nothing. Live: config, cross-site 403, guest account, wrong login, logout 401 after, and the page with no errors.
• Finished 06:13

05:52: Forgot password, by mail from our own domain

• Read Cloudflare's Email Sending pages (send_email binding page updated 25 Jun 2026; pricing updated 9 Jun 2026): the sending domain is onboarded in the dashboard, which adds its own DNS records; mailing any address needs Workers Paid; 3,000 a month are included.
• Built the rest in the login commit: "Forgot your password?" on the crew page asks for the email; the server makes a one-time code good for 30 minutes (only the newest works, one mail per address every 2 minutes), and the worker mails a link. Opening the link sets a new password and signs out every other browser. Tested end to end in the harbour tests, not by real mail.
• Not live: the button stays hidden until the worker has a mail binding and a from address. Turning on Email Sending changes the zone's DNS, so I left that to the boss, who said they will. When they say it's on, I'll add the binding, deploy, and send a reset to an address of ours.
• Finished 06:32

06:08: Parts, a hold that fills, and a ship that grows

• Live. A new crew now starts on a small ship: one deck, crew quarters, galley, life support and a cargo hold on one corridor, and 6 crew. Older crews keep their ship.
• Every raid brings home parts as well as meals: a quarter of the score, so a par run of 370 is 92 parts. Practice ships after the first of the day bring nothing, as with meals.
• The hold has a size: 8 meals per square of cargo hold and 2 per square of galley. The starter keeps 160. Food that doesn't fit is left behind, and the log says so.
• A survivor you bring out of a derelict joins the crew under their own name, up to 50.
• Build: the crew page opens the editor on your ship with a bar showing what the drawing costs (5 parts a new square, 400 a new deck) against the parts you have, and what the ship would be missing (no galley, no quarters, no air). Build it takes the ship back to the crew page, which checks the cost again, moves the crew aboard and keeps their food, sleep and health. In crew mode the editor doesn't save over your own plan.
• "Start over" (with a confirm) replaced the crew-size menu and the random-ship button. A link to someone else's ship no longer starts a crew on it.
• Change found by the tests: with no medbay, a crew member hurt in raids never healed, and the starter lost 2 of 6 in a week. Now rest heals slowly and the medbay heals fast. Across 30 starter ships over two weeks of daily raids, 1 person died; raiding every other day gave the same.
• Tests: 179 of 179 (25 crew tests, 8 of them new). The first full run failed 3 entry-page tests from the new editor bar; fixed and rerun.
• Checked locally: drew a 6-square room, which cost 30 parts; the crew moved aboard; a reload kept it. Phone width: no sideways scroll. Live: a new visitor gets the starter and Build opens the bar, with no errors.
• Finished 06:32

06:32: The crew's clock runs on real time

• Live. The ship's clock now runs a minute a minute from where it stood when the page opened, and the page says so in the intro ("raiders come about once a day"). The speed buttons, Pause and +1 day show only under ?t=. Older crews carry on from their own clock.
• Found while building: a tab in the background draws nothing, but it still saved every 5 seconds, stamping the current time on a stale clock. That would have lost the hours. Every save now brings the ship up to the wall clock first.
• Checked in a browser with a faked clock: 10 s later still 00:00; 65 min later 01:05; a reload keeps 01:05; 8 h later in the same tab 09:05; ?t=0 still runs fast with its buttons. No page errors. Crew and entry-page tests 32 of 32; nothing else changed since the full run of 179.
• Live check: the page carries the new intro line and hides the speed buttons.
• Next: the server replay that raiding other ships needs, then the itch page.
• Finished 06:40

06:40: A name and a way in for the crew game

• Named it Hullbound. Searches found no game by that name; "Holdfast" is an itch tabletop RPG, so not that.
• /crew/ can be indexed now. It has a real title ("Hullbound: keep a crew alive on a ship you draw"), a description, og tags, a canonical URL and a 1200x630 share card (img/hullbound-og.png: the starter ship mid-raid). Also added to the sitemap.
• Two ways in: a link on the home page nav, and a line on Derelict's end card ("Hullbound: keep a crew of your own alive... Start a crew"). The end-card line hides when the run came from a crew (?crew).
• Checked locally: the line shows on the end card at phone width with no errors. I only read the ?crew hide in the code (main.ts:645, the run-end path); I didn't drive a run to the end.
• Full suite: 179/179. Deployed. Live: the title, og:image (200, image/png), the nav link, #crewAd on /derelict/ and /crew/ in the sitemap.
• Nothing posted. The itch web page comes next, as an ask for the boss once it's finished.
• Finished 06:53

06:53: Hullbound as an itch web game, ready for the boss to upload

• Built app/hullbound-itch.zip (224 KB, 23 files) with scripts/build-hullbound.sh and vite.hullbound.config.ts. The crew page is index.html at the root, Derelict is in derelict/, the editor in editor/. A small module, src/bundle.ts, keeps links between those three inside the zip and sends every other link to the real site in a new tab. Account calls and pings go to the live site (pings marked -itch). The Google button is left out, since Google won't sign in from itch's origin. On the site itself, all of this does nothing.
• Worker: /api/crew/ now answers itch's origins (itch.zone, hwcdn.net), with a preflight for the Authorization header and PUT. Every other foreign origin still gets 403. The session key travels in a header, never a cookie, so the opening gives a page nothing it didn't already hold. A local test origin is allowed only through .dev.vars, which deploy never uploads.
• Tested before shipping: the zip served from 127.0.0.1 inside a sandboxed 820 x 760 frame on another origin, with the local worker as the API. Starter crew, a practice raid, the end card (the Hullbound ad hidden, "Back to your crew"), home, Build into the editor with the refit bar, and Cancel back all worked. Sign-up worked, and logging in from a second browser brought back the same ship. No page errors.
• Full suite: 179/179. Deployed. Live: an itch.zone preflight gets 204 with the right headers; a foreign origin and the test origin get 403; the site's own calls get 200.
• Itch page fields in app/store/ITCH-HULLBOUND.md. Cover (630x500) and four screenshots (raid, starter, building, phone) are in store/itch-hullbound/. Those and the zip are live under /press/hullbound/ (all 200; the zip is 229067 bytes, same as the build).
• Not tested: the zip on itch itself. That needs the boss's upload; once it's up I'll check play, sign-up and a raid on the real page.
• Finished 07:10

07:12: Reset mail from [email removed]

• The boss had already onboarded bananafest-destiny.com for Cloudflare Email Sending (cf-bounce MX, SPF and DKIM; one DMARC record kept). I didn't run anything that touches DNS.
• wrangler.jsonc: a send_email binding EMAIL and MAIL_FROM [email removed]. The worker's reset mail now comes from "Hullbound", subject "Reset your Hullbound password", and logs only accepted or failed with the error code, never the address.
• Harbour tests 10/10, dry run clean, deployed. /api/crew/config now answers mail:true, so the "Forgot password?" link shows on /crew/.
• Live test: a harbour account for [email removed], then /forgot. The worker's tail logged "reset mail accepted": Cloudflare took the send. Whether it reached an inbox is not known; that address has no mailbox I can read. Asked the boss to try it with their own address.
• That test account stays on the live harbour; it holds no crew.
• Finished 07:16

07:20: Google sign-in with the boss's client ID

• GOOGLE_CLIENT_ID went into wrangler.jsonc vars next to MAIL_FROM. The worker already checks Google's token against it (the harbour gets it as x-google-client). Harbour tests 10/10.
• Built and deployed. /api/crew/config answers with the client ID and mail:true.
• On the live /crew/, opening "Log in or make an account" loads Google's sign-in button (an accounts.google.com/gsi/button frame), with no origin or client errors in the console.
• Not tested: a real Google sign-in, because I have no Google account in a browser. Asked the boss to tap it once. If their consent screen is still in Testing, only the test users they added can get through.
• The itch zip still leaves Google out (that origin isn't registered), as planned.
• Finished 07:21
• Then the boss asked about the consent screen's logo. It's optional, and uploading one makes Google verify the brand before it shows. I drew a 120 x 120 one from code anyway (the hull outline with three crew; source store/itch-hullbound/logo.html), deployed, and it's live at /press/hullbound/logo-120.png. I told the boss that leaving it blank is quicker. (added 07:22)

07:22: A home page and privacy policy Google will accept for Hullbound

• Google's consent screen won't publish without a home page and a privacy policy URL (the boss's screenshot). /privacy/ already had a crew-game section (accounts, the PBKDF2 hash, Google's id, deleting an account). Its one stale line now also says the address is used for a password reset link when you ask for one. Deployed; /crew/ and /privacy/ both answer 200.
• Gave the boss: home page https://bulkhead.bananafest-destiny.com/crew/, privacy https://bulkhead.bananafest-destiny.com/privacy/, and authorized domain bananafest-destiny.com.
• Finished 07:23

07:29: Swap in the boss's second Google client ID

• Replaced GOOGLE_CLIENT_ID in wrangler.jsonc; harbour 10/10; deployed. /api/crew/config answers with the new ID and mail:true.
• Live /crew/: Google's button frame renders "Continue with Google", with no origin or client error in the console. The only console errors were my test aborting the page's count pings.
• A real sign-in is still the boss's to try.
• Finished 07:30

07:41: Does Hullbound get counted like Derelict?

• Already there: the crew page sends a view ping and crew-* events (new, start, back-<how long away>, raid-today/practice, haul-<size>, refit, account, signup/login/google, forgot, reset, logout). scripts/events.sh already counts them from the zone log, with my headless runs and bots dropped. Since 20 Oct: 1 view of /crew/ and 1 crew-start. The itch zip adds -itch to its events and sends its own view ping.
• Missing: anything from the server. Derelict has its board; the crew game had no count of ships, logins or who came back, and coming back is the test it has to pass.
• Added: a days table in the harbour (each ship's UTC days with a save; the page saves every two minutes while open) and Harbour.stats(), which returns counts only: accounts (email, Google, ours = @bananafest-destiny.com), ships, came back 3h+/1d+/3d+, saved in 24h/7d, ships by days played, and accounts opened per day. It returns no id, email or ship; a test checks that.
• The worker's GET /api/crew/stats answers only to a Worker secret STATS_KEY. Without the key, or with a wrong one, it 404s. The key is also CREW_STATS_KEY in the git-ignored credentials file and was never printed. scripts/crew-stats.sh reads it.
• Harbour 11/11, tsc clean, dry run clean, deployed. First live read: 2 accounts (1 email, 1 ours), 0 ships. Both are likely my own tests. A first visit only makes an account at its first two-minute save, so a short look leaves nothing on the server; events.sh still counts it.
• Finished 07:44

11:07: Count a stranger's return even if their first look was short

• The world's clock doesn't help. w.t runs a minute a minute while the tab is open, so a three-hour open tab and a return look the same.
• Fix on the page: the first save, which also makes the account, now comes 20 seconds in instead of at the two-minute mark. A first look of 20 s or more now has an account dated that day, so a return the next day counts as back. A look under 20 s still leaves nothing on the server; events.sh's crew-new still counts it.
• tsc clean, crew 25/25. Local wrangler dev: account and first save both at 20 s, no page errors. Deployed.
• Rebuilt the itch zip (224 KB, 23 files; its crew script has the 20 s save) and replaced it at /press/hullbound/hullbound-itch.zip. If the boss had already downloaded the earlier copy, the only difference is this timing.
• Finished 11:09

11:09: The 21 Oct daily, by hand

• My first start wrote to .daily-log, which is the log folder, so the shell refused it before the script ran. The second start sent its output to .daily-log/run-manual.out.
• The run (11:09Z start) generated and deployed today's derelict and posted to Bluesky at 11:10Z, with the map attached and a link back to /daily/2026-10-21/. IndexNow accepted 3 URLs. 66/66 pages clean, and the daily committed and pushed itself (Daily derelict 2026-10-21).
• Status, run inside it at 11:14Z: all 31 clear. That covers today's page live, the feed leading with it, no missing days (36), today's Bluesky URL recorded and the post really on Bluesky, and itch at $9 matching the site.
• It exited 1 for one reason: the link graph called /crew/ a link to nothing. Like /derelict/ on 20 Oct, /crew/ is a Vite input, not a file in public/. Fixed in scripts/lib/pages.mjs; the link graph now reaches 64/64 sitemap pages. Nothing on the site was wrong.
• No deploy of my own, nothing else posted.
• Finished 11:14

13:07: A reason to come back at a time

• Before: the page gave no time to come back to. The intro says "come back later", and a return says "you were away X". Nothing said how long the crew can last.
• Now one yellow line above the raid buttons, from the sim itself run ahead on a copy (raids are seeded, so it's the real future): "Food runs out in about 2 days. Bring a haul home before then." Once the hold is empty it says "Someone starves in about N hours unless you bring food home." It looks at most three days ahead, as far as the clock catches up. It's worked out on load and once a minute.
• Checked: with a fixed seed the answer is the same from any start time (a starter's hold empties at about 52 h; the first starves 26 to 38 h later). Three days ahead takes 11 to 16 ms in Node for 6, 20 and 50 crew. Locally: fresh 2 days; t=600, 41 hours; t=2500, 9 hours; an empty hold, 17 hours. My first comparison across ?t= runs looked inconsistent only because each fresh load gets a new random seed.
• tsc clean, crew 25/25. Deployed (/crew/ has the line). Rebuilt the itch zip and replaced it at /press/hullbound/.
• Finished 13:10

13:20: The crew page's intro only until you know it

• The intro is now inside a details element. It's open on a new crew's first visit. On any return (a saved crew for this ship) it folds to a small "How it plays" link, and tapping that opens it again. The food line, the raid buttons and the map move up.
• Local check: first visit shows the intro; a reload after 7 s shows the link only; a tap opens it. No page errors. On a 390 px phone, a return now shows the map in the first screen.
• crew 25/25, tsc clean. Deployed; the zip rebuilt and replaced at /press/hullbound/.
• Finished 13:21

13:27: Hullbound gets a voyage: a destination, stops, and choices

• Built the voyage (the boss's idea, FACTS 21 Oct). src/crew/voyage.ts: a leg is a few real days to a named port; about once a day the ship docks at a base and a seeded choice waits (fuel in meals or parts or coast a day; a trader; a passenger with their own line; a debris shortcut a day shorter where raids come twice as often; a sick crew member left at a clinic or kept). Food is eaten while it waits; after 12 hours the captain takes the safe one. No base twice on a leg, never the same kind twice running. At the port the yard pays 5 parts per survivor per day, the leg goes in a record you can share, and the next leg is the longer pair: one far and paying double, one near.
• src/crew/story.ts: everyone has one line (who they were, a habit) from their name; a survivor from a raid carries their wreck's first line; coming back says what happened by name ("Bram Osei and Gale Haddad were hurt. The ship is docked at Pell's Rest, waiting for your call."). The header says "Day 2 of 4 to Quayle Port".
• If everyone dies the ship drifts, with no arrival and no pay. A sick crew member who dies while you choose clears the choice.
• Balance, 8 seeds x 16 days, captain's choices and one par raid a day: 2 legs each, 0 to 2 deaths (raids with no medbay, the harder second leg, a sick one kept aboard).
• Tests: test/voyage.test.ts 11; the full suite 191 of 191 before the last two fixes (fuel buttons say "for fuel"; no base twice), then voyage and crew 36 of 36 and tsc clean after them.
• Itch kit redone for it: four new screenshots from real sim states stepped faster (desk-stop, desk-arrive, desk-raid, phone-away), desk-build kept; the cover re-shot with a new tagline "Take a crew to a far port on a ship you draw. Raiders board while you're away."; store/ITCH-HULLBOUND.md rewritten (short description, tags with choices-matter, description, screenshot honesty note); zip rebuilt, 232 KB, checked served from another origin with no page errors and the voyage in the header.
• Deployed; live /crew/ loads on a phone with no page errors and "Day 1 of 4 to ..." in the header; all eight files under /press/hullbound/ answer 200; /derelict/ 200.
• Finished 13:59

14:00: The Hullbound press folder gets a page of its own

• Added public/press/hullbound/index.html (noindex): the steps for a new free itch project with every setting, the description in a box with a Copy button (taken from store/ITCH-HULLBOUND.md so the two can't differ), the cover, the five screenshots in order with what each shows, the zip and logo as downloads.
• Deployed. Live at a phone width: 200, all seven images load, no 4xx, no sideways scroll.
• Finished 14:01

14:02: A Hullbound logo with the name on it, from the image generator

• Five gpt-image-1 images at medium, 1024 x 1024: three emblems (each drew a rounded tile inside the square, wrong for a store icon), then two full-bleed. Kept the gold ship with three crew at a lit window (store/itch-hullbound/emblem-gen.png). 5280 output tokens, about $0.21; the image budget now stands at about $0.82 of $1 (FACTS 21 Oct).
• The name is set in Russo One by store/itch-hullbound/icon.html over a fade, so the letters are exact; rendered to icon-1024.png, icon-512.png and icon-120.png. Looked at it at 1024, 512, 120 and 48 and under a store's 20% rounded corners: the name stays inside them and reads at 48. A circle mask would clip it, but that is an Android launcher icon, not ours.
• First try shrank the art and left a border down the sides; put it back full size and made the name smaller instead.
• On the press page: icon-512, icon-1024 and logo-120 (replaced with the new one). The AI disclosure there and in ITCH-HULLBOUND.md now says Graphics too, and which picture came from the model.
• Deployed. The new icons were 404 for a few seconds right after the deploy, then 200 at full size; the page has the new disclosure.
• Finished 14:06

14:19: Hullbound is on itch; a jam entrant asks whether walls cost air in Derelict

• The boss made the Hullbound itch page (https://bananafestdestiny.itch.io/hullbound). They didn't put the logo on it. The game plays from html-classic.itch.zone.
• A jam entrant posted on Derelict's jam page: a first run made sense without How to play, but they couldn't tell whether walking into a wall costs air like a step. Over about 16 presses their air moved 5.
• In the engine a wall costs nothing: move() spends no air and records no move. The airlock costs nothing in the first moments either, and it already says so.
• The board now says so too. On the first wall of a run: "A wall. Walking into one costs no air." The first tip now ends "walking into a wall costs nothing."
• Checked in a browser against the local worker: the line shows on the first bump and the air doesn't change. My first test pressed into the airlock instead of a wall.
• tsc passes; game tests 43/43 (the full suite was 191/191 earlier today, before this change). Deployed, and the live script has the line.
• One new zip of each for the boss, since the Hullbound zip carries Derelict too: /press/derelict/derelict-itch.zip and /press/hullbound/hullbound-itch.zip.
• Wrote a reply to the jam entrant for the boss to post. Playing their game back is the boss's call; I don't rate entries.
• Accounts on itch: nothing to set. The itch build has email sign-in only; the Google button is hidden there because itch's frame origin isn't on the client.
• Finished 14:27

14:35: Derelict's numbers, then Greyling's

• Derelict since 04:00Z (events.sh): 115 boards (113 practice, 2 daily); 101 practice runs ended (89 out, 12 dead), all from inside the itch frame. One daily run ended dead. The board for 21 Oct has no runs; 20 Oct's has 2.
• By who (a temporary copy of events.sh grouped by country, device and a 4-character agent hash, now deleted; nothing written down but the counts): the one desktop browser in GB from yesterday made 113 of the boards, from 10:00Z to 14:00Z. Everyone else: two browsers in DE with 3 boards between them, plus one-view visits from the US and NZ.
• Practice results from the run- pings: most got out, with scores of 20 or 50; a handful scored 100. Few read all three logs.
• Hullbound from itch: 3 crew-start and 2 crew-account pings since 07:00Z (US, DE, AE). The DE and AE pings share one agent hash at 14:00Z, likely one person.
• itch-stats: derelict 31 views (23 at 04:00), hullbound 5, Bulkhead 44 views, 4 downloads, 0 purchases. Bluesky 9 followers.
• Greyling post (r/Star_Wars_Maps, 22:11Z 20 Oct), about 16.5 h in: 5 views of /derelict-one-shot/, 3 fetches of the adventure PDF, 1 editor visit (from m.facebook.com, not Reddit). The post's own score and views: Reddit's .json refused a logged-out read. Only the boss's screenshots show them.
• Finished 14:37

14:50: The boss's Greyling insights, 17 h in

• In FACTS: 1.1K views, #1 in the sub today, 0 points at a 35% upvote ratio, 2 comments, and 65.7% of viewers in the US. Views peaked in the first five hours.
• Against our counts for the same window (5 one-shot page views, 3 PDF fetches, 0 editor visits from Reddit), that is about 0.5% clicking through. In LEARNED: an image post in a map sub gets seen but doesn't reach the editor. The 24 h read is done now; there's no need for another at 22:00Z.
• Finished 14:50

15:01: Has anyone come back to their Hullbound crew

• crew-stats.sh: 5 accounts, all opened today. 1 is ours (my email test), 1 signed up with email, none with Google. 3 ships saved, all with 1 day played. Came back after 3 h or more: 0.
• Crew pings since 20 Oct, all from itch except one: 5 starts, 3 accounts, 2 hauls of 20 to 39, 3 raids sent into Derelict (2 practice, 1 daily) and 3 trips back home from Derelict. 1 "back" ping, under an hour away. 8 views of the itch crew page.
• So the first test hasn't been run yet: nobody has had the chance to come back. The earliest stranger came at about 07:00Z, 8 hours ago, and hasn't been back. Most arrived at 14:00Z. Read again tomorrow: "a day+" is the number that counts.
• The raid loop works for strangers: 3 went from their crew into a Derelict run and came home with the haul.
• Finished 15:01

15:03: A Hullbound cover as strong as Derelict's

• Correction to the 14:58 entry: Hullbound went public at about 14:30Z (the boss), so the crew pings before then, the 07:00Z US one and the 14:00Z DE/AE one included, came from the page while it was a draft. Most likely those were the boss and the itch preview, not strangers. The 5 accounts include those. Strangers who could come back: none yet.
• The boss chose a painted cover with a raised budget, and said email works (the reset mail arrives). Both are in FACTS.
• Two tries from gpt-image-1: three crew in silhouette at a round hatch, with a raider's cutting torch burning blue through its window, amber lamps and dark blue. I took the first (the torch is in the window); the second is kept as cover-gen-2.png.
• cover.html now lays it out like Derelict's cover: HULLBOUND in yellow at the top left, the two lines under it, and a fade over the dark top. New banner.html gives the itch page header, 960x300, with the name on the dark left and the painting on the right.
• Press page: the new cover, the banner with where it goes on itch (Edit theme, Banner), and the disclosure says the cover painting is from the image model too. ITCH-HULLBOUND.md likewise. Deployed; the page, cover and banner are 200.
• Finished 15:06

15:07: An email when the ship docks, for players who ask for it

• Opt-in only, for accounts with an email. A tick box under the account line on /crew/, "Email me when the ship docks and a choice is waiting". It shows only when mail is configured and you're signed in.
• The worker works out the next stop from the saved ship: the next base, or the port if that comes first, up to three days ahead. The Harbour's alarm sends one mail 5 minutes after the stop is due. If the ship was saved after that moment (the player was already there), nothing is sent. One mail per stop, never twice.
• Each mail says where and that the captain takes the safe option after 12 hours, links back to the crew (the itch page for players who play on itch, the site for the rest), and has a link that turns it off.
• Tested: 3 new unit tests (harbour 14/14; harbour, voyage and crew 50/50; tsc clean). Locally end to end: signed up, saved a ship one tick from a base, ticked the box, and at 15:16:26 the alarm sent "Your ship has docked: a choice is waiting" (send_email accepted). The tick box in a browser: ticked, still ticked after a reload.
• Deployed. Live: /crew/ has the box, an anonymous POST /api/crew/bell gets 401, the unbell link answers in plain words.
• The privacy page now says what this mail is and that it can be turned off. It is in the sitemap too, after the docent bot's mail said nothing linked to it apart from /crew/.
• A new Hullbound itch zip with the tick box: /press/hullbound/hullbound-itch.zip (234,713 bytes). The boss uploads it.
• Finished 15:18

15:14: A devlog post, drafted for the boss

• Derelict has one devlog ("Play a ship you drew") and Bulkhead has 1.14 and 1.19. Hullbound has none, so this is its first.
• Drafted it at https://bulkhead.bananafest-destiny.com/press/hullbound/devlog/: upload the new zip first, then Devlog, Create new post, type Update. The page has a title and body with Copy buttons and desk-stop.png as the picture.
• Title: "Hullbound is up, and it can email you when the ship docks". The body is lowercase, opens with "made by a vibecoded app", and says what the game is, the docking choices, the new email and how to play on another device. It asks for comments.
• Every claim is checked against the live build: the tick box, one mail per stop, the off link, Google sign-in on the site only.
• Finished 15:18

15:25: The reply to the Derelict comment, found for the boss

• Found it in my 14:27 message to the boss, not in actual: "thanks for playing from the airlock. walls cost nothing, and now the board says so the first time you bump one". Gave it back as is.
• Noted that the line only shows on itch once the new Derelict zip is uploaded, since itch plays the zip, not the site.
• Finished 15:25

15:28: The boss says both are done; check the zips, the devlog and the reply on itch

• Hullbound's devlog is up: /hullbound/devlog/<n>/hullbound-is-up-and-it-can-email-you-when-the-ship-docks.
• Derelict on itch serves the wall-line zip: 166,457 bytes, uploaded 14:34:59Z, the same size as /press/derelict/derelict-itch.zip.
• Hullbound on itch still serves the 14:34:33Z zip (234,514 bytes), not the one with the email tick box (234,713 bytes, built about 15:25Z). So players on itch don't see the box the devlog talks about. Asked the boss to replace that one file.
• The reply on the jam page: logged out, the rate page doesn't show its comments, so I can't see it. Taken as the boss said.
• Finished 15:29

16:00: Is there sound in the games

• Derelict has sound, all made in code with WebAudio (src/game/sound.ts): a hull drone, a score for each ship (the seed picks the key, so everyone hears the same one for the day, and it tightens as the air goes), beds for fire, smoke and the drone, and effects for hazards, logs, salvage, survivors, air canisters, getting out and dying. It's on by default, starts on the first move, and has a Sound on/off button.
• Hullbound's crew page has no sound. Its raids open in Derelict, so they have Derelict's sound. The Bulkhead editor has none.
• Finished 16:00

16:01: A soundtrack for the crew page, like a Super Nintendo game

• New src/crew/music.ts. All of it is made in code with WebAudio, with no files and no music model: - A pulse-wave lead with vibrato that comes in on held notes, detuned saw string pads, a filtered saw and triangle bass, a 12.5% pulse arpeggio, and noise and sine drums. - It runs through a three-sixteenth echo that gets darker each time round, and a 6.5 kHz low-pass (the SNES's soft top end). 104 bpm.
• Two tunes, written by hand as eighth-note bars: - The voyage: 16 bars in D (D C G D Bm G Em A, G A F#m Bm G A D C). - Raiders aboard: 8 bars in B minor with driving drums. - Docked with a choice waiting: the voyage tune without drums, with the bass held.
• The page sets the mood every frame and the tune changes at the next bar. A raid opens Derelict in the same tab, so the crew music stops and Derelict's sound takes over.
• It starts on the first tap or key (the browser rule), suspends while the tab is hidden, and fades in over 2 s. A "Music on/off" button sits beside Build, is remembered in this browser, and is counted as music-on or music-off.
• Tests: 3 new in test/music.test.ts (note names, bars, every bar fits). Full suite 197/197 in 455 s; tsc clean.
• In a browser against the local worker: no audio context before a tap, running after one, off remembered across a reload, no tap restarts it while off, on again works, no page errors.
• Rendered offline (voyage 16 bars, raid 8, docked 4; 66.6 s at 32 kHz): peaks 0.28, 0.26 and 0.19, and RMS about 0.07 in all three, so no clipping and the moods are equally loud. I can't listen myself, so the file is for the boss: https://bulkhead.bananafest-destiny.com/press/hullbound/music/ (the WAV is git-ignored, 8.5 MB).
• Deployed; /crew/ has the button live. A new Hullbound zip with the music and the email tick box: /press/hullbound/hullbound-itch.zip (237,282 bytes). It replaces the 234,713-byte one the boss hasn't uploaded yet.
• Finished 16:14

16:50: The boss on the music: "its perfect"

• In FACTS. In LEARNED: sound is a strength to show; render it and measure before any change, since I can't hear it.
• The itch description (store/ITCH-HULLBOUND.md and the press page's Copy box) has one new line: "A 16-bit style soundtrack that changes when raiders board or the ship docks, with a Music off button". The press page says to paste it over the old one. Deployed and live.
• Batched for the boss: the 237,282-byte zip and the description paste.
• Finished 16:50

17:02: Derelict's numbers, since the 14:35 read

• Since 14:30Z (events.sh, read about 17:02Z): 75 boards (72 practice, 3 daily) and 76 practice runs out. All from inside the itch frame. 76 Derelict page views on itch.
• By who (a temporary grouped copy of events.sh, deleted; only counts kept): one desktop browser in GB again made 67 of the 75 boards and about 74 run endings. It plays practice ship after practice ship with steady scores of 20 to 100, the way a person plays. The other boards came from 7 browsers (PL phone, DE, GB, FR, US phone and more), most of them arriving through Hullbound's raid buttons.
• Daily: 3 boards today. Two runs left early with 5 points, and none finished, so the 21 Oct board has 0 runs. 20 Oct's has 2 (230, 105).
• Scores: most runs get out with 20 or 50, a few with 100. Logs read: mostly 1 of 3, a few 3 of 3. Deaths: 4 practice.
• itch-stats: derelict 33 views (31 at 14:35), hullbound 15 (5), bulkhead 44 views, 4 downloads, 0 purchases.
• The jam's rate page shows no ratings count logged out.
• Finished 17:02

17:03: The one player in GB who boards most of Derelict's ships

• From the zone's request log (temporary scripts, deleted). Only counts and yes/no answers came out; no agent string and no address was printed or kept.
• One desktop Chrome on Linux, one address, in GB. It is not this machine: its address isn't ours, and our own runs are headless and filtered anyway. It plays Derelict only inside the itch frame.
• First seen 20 Oct 10:43Z. 288 boards in 10 sessions: 20 Oct 10:43, 11:32, 13:49, 18:11, 19:29 and 21:00; 21 Oct 10:35, 12:13, 14:07 and 15:11 (the last ended 15:36). Sessions run 10 to 45 minutes.
• Inside a session it boards about 2 ships a minute, every minute. The gap between boards is 1 minute 153 times, 2 minutes 22 times and longer only 5 times. The 15:xx session went 1, 1, 1, 2, 2, 2... per minute for 26 minutes.
• Almost all practice: 281 practice boards, 4 archive, 3 daily, and it never finished a daily. Most runs get out with 20 or 50 after 2 to 6 rooms; 17 died. It loads the end picture every run, and reads the 20 Oct board a few times.
• Reading: a person can play a 30-second practice run, but not 50 in a row at that beat across ten sessions. It looks like a script or an AI agent playing the itch build: a jam entrant's tool, a tester, or someone's bot. I can't tell which, and there's no way to ask. It costs nothing (static files, and practice runs never reach the board), so it isn't blocked. From now on it is counted apart from people.
• Finished 17:05

17:06: Why the GB browser plays Derelict like a script

• Jam page: nothing on bots, agents or playtesting. Derelict was submitted about 04:30Z on 20 Oct; this browser first showed at 10:43Z.
• Its agent says Chrome 154 on Linux x86_64, not HeadlessChrome. That's the current version, so it says nothing either way.
• Every board is a fresh page load (291 view pings, 288 boards). But the end screen's "again" button reloads the page (location.href to ?practice), so a person does that too. My earlier "plays like a script" leaned on this, and it doesn't hold.
• Seconds-level timing (186 run pings that survived sampling): view to board 1–3 s (median 2), board to end 5–264 s (median 33, wide spread), end to the next view 2–3 s. Steady clicking with uneven play lengths. That fits a person in flow; an LLM agent would take minutes a board.
• Sessions in UK time (BST): 11:43, 12:32, 14:49, 19:11, 20:29, 22:00 on the 20th; 11:35, 13:13, 15:07, 16:11 on the 21st. Lunch, afternoon, evening: a day's shape, not a cron.
• It played the daily once a day, opened two archive days and checked the board for 19, 20 and 21 Oct.
• No improvement across runs (rooms reached about half the ship each day, deaths about 1 in 10). That's the one thing that looks less human.
• Reading: more likely one keen person grinding the practice career than a script. Not proved; the robot flag (next entry) settles it from the next upload.
• Finished 17:13

17:10: A robot flag on Derelict's board ping

• src/game/main.ts: boarding also pings derelict-robot-<mode> when navigator.webdriver is true. The first pointer or key after boarding pings input-mouse / input-touch / input-pen / input-keys once per page, with -robot on the end under automation. Bare GETs, no id.
• tsc ok; game tests 43/43. Deployed. A headless Playwright run on live practice (pings caught and aborted, never sent) saw view, board-practice, robot-practice, input-mouse-robot-practice.
• New derelict-itch.zip (166,539 bytes) at /press/derelict/derelict-itch.zip. The itch embed only gets the flag once the boss uploads it, together with the Hullbound zip (237,282 bytes) still waiting.
• Finished 17:13

17:16: Check the Derelict upload with the robot flag

• itch uploads API: Derelict serves derelict-itch (1).zip, 166,539 bytes, 17:16:14Z, type html. Hullbound serves hullbound-itch (5).zip, 237,282 bytes, 16:48:32Z. Both are the current builds, so the Hullbound ask is done too.
• The bare Derelict page said "Loading game for the first time" until about 17:27Z, but a cache-busted fetch already had the game frame. Itch was serving a cached copy of the page, not still unpacking. By 17:28 the bare URL had the frame too.
• The embed's script contains the flag (input- pings). From now on the itch build sends derelict-robot-* under automation, plus the first input kind.
• Finished 17:27

17:35: What videos are up for the socials

• Three videos are up under /media/, all returning 200: daily-derelict-2026-10-17, daily-derelict-2026-10-18 (both "here's today's free ship", about 12 MB) and deck-plan-to-foundry-2026-10-17 (editor to a Foundry export, about 1.4 MB). Each has its claim JSON with product Bulkhead.
• Nothing since 18 Oct: no Hullbound footage and no Derelict gameplay clip. Nothing in FACTS says whether the docent cut or posted any of the three.
• Offered the boss a Hullbound clip (a raid and a docking choice, real capture, sound off per the docent's spec) and a fresh daily.
• Finished 17:36

17:50: A Hullbound clip for the docent, and ask whether the first three went out

• Mail to the docent (thread cider3-media-status): did any of the three /media/ videos post, and where; the Hullbound clip is coming on the same path. Delivered by the mailroom.
• New scripts/media-hullbound.mjs: the live /crew/ page in its look-ahead mode (?t=0) at 432x768, 2.5x. Pings and /api/ are blocked, the speed buttons are hidden, and a drawn arrow shows the mouse. It finds the raid by the raiders' red on the map, slows to a minute a second for it, runs fast to the next docking and picks a choice with the mouse.
• Three takes. Take 1: 23 s, a bit short. Take 2: the mouse sold 20 meals and the clip ended on an empty hold, so the script no longer sells food. Take 3 kept: 30.46 s, a raid in the corridor, docked at Pell's Rest, "Take the shortcut", the voyage going on, a 2 s still tail.
• Live: /media/hullbound-raid-and-dock-2026-10-21.mp4 (914,040 bytes, video/mp4, 200) and .json (product Hullbound; claim backed by /crew/ and the itch page; no sales; notes say the clock runs fast in the clip).
• Finished 17:58

17:29: Watch for the UK player's first flagged session

• The watch matched them at 18:10Z: the same browser (hash 4e53, Chrome 154), first ping 18:05Z, on the new itch build. That's 19:05 UK time, an evening session like yesterday's.
• 19 boards in the first 15 minutes. The first input on every page was keys (19 input-keys, 1 input-mouse later on one page). Not one robot ping and no -robot suffix, so navigator.webdriver is false.
• Reading: a person playing with the arrow keys, which also explains the pace (Enter boards, arrows walk). Standard Playwright, Puppeteer and Selenium all set webdriver; only a stealth-patched driver or a key macro on a real browser would look like this. Still unexplained: their results don't improve across runs.
• Finished 18:21

18:26: The UK player story: tell the docent, draft a dev.to post

• FACTS has no dev.to entry. LEARNED and older actuals show the boss has their own dev.to posts (a copy of the .dd2vtt post went up there on 20 Sep). So this is a draft for them to paste, the same way as the itch devlog.
• Draft at /press/devto-uk-player/ (noindex; title, tags and body each with a Copy button; post.md beside it). About 870 words, first line "Made by a vibecoded app", no em-dashes. Title: "I thought my game's best player was a bot, so I asked the browser". Tags: gamedev, javascript, webdev, analytics.
• It tells it straight: my first call (script), the boss's question, the "again" button that reloads, the timing to the second, the webdriver and first-input ping (the real code), the 18:05Z answer, and what I got wrong. Nothing identifying: "the UK", time of day, no browser version, OS, address or hash.
• Mail to the docent (thread cider3-derelict-uk-player, needs_reply no): the story in short, the draft link, keep the player unidentified, practice footage on request. It was in mail/out at the time of writing.
• Finished 18:28

19:07: Practice in front of daily players; the privacy link

• Read why the few daily players other than the UK fan end so soon. Since 14 Oct, the itch daily had 19 boards, and most runs ended within 5 steps in the first room. An "out" at 1 to 4 steps means a step back onto the airlock square, and that ended the day's only run. The game already guarded the very first step (full air), but not the second.
• Fixed: an arrow or a tap into the airlock now asks first ("That's the airlock. Leaving ends the run with N air. Step that way again to leave, or any other way to stay aboard."). The same way again, or the Leave button, leaves. Checked on a local build with Playwright: the first press asked, the second ended the run. tsc clean, game tests 43/43.
• The home page sidebar line now links /privacy/ (website only; the paid file strips that line). It was already in the sitemap.
• Deployed. The live derelict bundle has the new line. New Derelict zip (166,625 bytes) at /press/derelict/derelict-itch.zip for the boss to upload.
• Not done: a pitch for practice after the daily. The /api/crew/config mail flag stays, because the page needs it for the tick box. Tell the docent when it replies.
• Finished 19:15

19:18: Offer practice to a daily player when their run ends

• After a daily run, the end screen only offered a button called "Practice on another ship" and never said what practice is. Added one line under the buttons, shown after a daily or archive run but not after practice: "Want another go? Practice is a new ship every time, as many as you like. What you get out with buys air tanks, a harness slot and torch cells for the next one. Tomorrow's daily is a new ship for everyone."
• Checked on a local build with Playwright. On a daily run (step in, step back, asked, leave), the line shows; on a practice run, it's hidden. tsc clean, game tests 43/43.
• Deployed; the live /derelict/ has the line. The zip was rebuilt with both changes (166,743 bytes), same link. The boss uploads it once, covering this round and the airlock prompt.
• Finished 19:22

19:26: Is the UK player still playing

• GB practice boards on itch, by hour: 14Z 49, 15Z 51, nothing 16-17Z, 18Z 91, 19Z 3. The last was at 19:01Z. From 18:00Z: 95 practice boards, 90 out, 5 dead; the runs reach most of the ship (s20 to s100, several r5of5 and 3 of 3 logs). They're still on the itch build without the airlock prompt.
• Finished 19:27

19:43: The boss's r/ClaudeCode post about the UK player: is anyone coming to Derelict from it

• Since 18:30Z, apart from the UK practice runs, there were 3 daily boards on itch. All 3 ended within 5 steps in room 1: 2 left the page, 1 got out. That could be readers of the post, but it's too few to say. There were also 3 Hullbound starts on itch. Itch's all-time Derelict views are 37 (18 on 20 Oct). The post has no link, so a reader has to search itch for the game.
• The new zip, with the airlock prompt and the practice line, isn't on itch yet. Itch is where any readers land.
• Finished 19:44

• The boss added the itch link as a comment (19:59Z or just before). They said they didn't want the post to look like promotion. I'll check boards again later this evening.
• The boss uploaded the new zip (166,743 bytes, 19:58Z), but as a plain download. The browser-played file is still the 17:27 one. The itch frame's script has no "That's the airlock", so players still get the old build. Asked the boss to tick "played in the browser" on the new file and delete the old one.
• 20:02Z: the boss set the new zip to play in the browser and deleted the old one. Itch's API lists one upload (166,743 bytes, html). I loaded the itch page in Playwright: the game frame has the practice line and the airlock prompt. A plain curl of the page still got the cached "Loading game for the first time".

21:07: Make the most of the r/ClaudeCode readers

• Reddit's JSON is closed to scripts (old.reddit 302, api.reddit 403), so I couldn't read the comments. Ask the boss to paste any question worth answering.
• Daily boards on itch since 19:55Z, the new build's first hour: 4 boards and 4 run-sums. One got out at s20-r2of4 with 2 of 3 logs, two died at s20-r2of4 with 2 of 3 logs (or one death sent twice), and one left at s20-r1of4. Every daily run went past 20 steps. Before today's fix, nearly all ended within 5. Four runs is too few to call it the fix, but it's the first evening with no run ending in the first 5 steps. No daily player went on to practice: all 62 practice boards since 19:55Z were keyboard runs, the UK pattern.
• A Reddit reader lands on the Derelict itch page. Its description still says "Made by an AI agent (Claude)", and its only Bulkhead link goes to the website, not the itch page where it sells. Hullbound isn't mentioned. Wrote a new description at /press/derelict/description/ with a copy button: "made by a vibecoded app" first, the practice line saying what practice gives, Bulkhead's itch link, and a last line for Hullbound. Deployed; 200.
• Finished 21:08

23:07: Where Derelict and Hullbound players go next, and what to fix in the way

• Buy clicks since 14 Oct: 62 from people who loaded a page first (most from /daily/ map pages: map 22, brief 15). All go to itch's purchase form. Bulkhead itch: 0 purchases this week. Nothing new to fix there tonight.
• Hullbound: crew-stats shows 167 accounts today but 16 ships saved, and no one back after 3h+ yet. The zone log of POST /api/crew/account, grouped by a hash of address and agent that stays inside the script: one GB Firefox-on-Mac browser made 125 accounts from 17Z to 21Z, about 30 an hour. That's one per 2-minute save. It never sent a PUT /api/crew/ship or a crew-account ping, and sent 4 crew-start pings (4 fresh starts). An Argentine Chrome-on-Windows browser did the same 21 times. So their storage on the itch frame's origin refuses writes: setItem throws, account() catches it and returns null, and the next save makes a new account. Most likely the shared html-classic.itch.zone storage is full; every itch HTML game uses that one origin. Neither player could keep a ship past a reload.
• Fixed in src/crew/page.ts: the key and base are also kept in memory, so an open page saves to one account. When a write fails, the account line says "This browser isn't keeping your crew (its storage for this page is full or blocked), so closing the page starts over. Make an account or log in to keep them." A new crew-nostore ping counts it once per page.
• Tested on the local worker with Playwright and setItem made to throw: 1 account and 2 saves in 2.5 min (both 200), and the line shows. Normal storage: 1 account across a reload, line unchanged. tsc clean; crew, harbour and voyage tests 50/50.
• Deployed, live /crew/ bundle checked. New Hullbound zip (237,764 bytes) at /press/hullbound/hullbound-itch.zip for the boss to upload. That's the build both of those players use.
• Slip: I stopped the local worker with pkill instead of kill PID and fuser. The pattern matched my own shell and ended that command. Then fuser -k 8792/tcp.
• Finished 23:14