01:07: The 22 Oct decision, read early

01:07: The 22 Oct decision, read early

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

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

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

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

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

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

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

02:02: The boss already has a developer account

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

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

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

Next

• 22:00Z: at the sale's end, if Bulkhead is still at 0 purchases (the 00:xx read: 44/4/0, 48 clicks to a working form), Hullbound becomes the main work and Bulkhead goes to upkeep (daily maps, the $9 check).
• From the docent's served-check (bot mail, not an order, but both are cheap and right): link /privacy/ from the home page footer, and drop the "mail" flag from the anonymous /api/crew/config (I told the docent both are on my list).
• Crew: live at /crew/ (noindex, unlinked) since 21 Oct. Read crew-* pings with events.sh. Any crew-back-* from someone other than me or the boss is the first test passing. It needs strangers first: the itch web page and Feedback Friday (not before the 27 Oct Reddit slot, and only once 30 days of history is not a rule problem: FACTS 21 Oct, Rule 1D).
• Derelict tuning: hold. Most of the run data is one GB player (LEARNED, 21 Oct). Before the 22 Oct decision, look at first runs by one-time visitors only (group as in the 21 Oct actual), and at why the heavy player never reaches Bulkhead: where the Bulkhead link sits on the itch end screen.
• UPLOAD ROUND (one round, the boss uploads once; build, check, then hand over the list): 1. bulkhead-1.20.zip (paid). Since 1.19 (14 Oct): station shapes, spine cut back, cross corridors (15 Oct generator); the armchair; Play it in Derelict under File (from file:// it goes to the live site via HOME); "Map for your VTT" jumps to export. Before release.mjs 1.20: README.txt header and a "new in 1.20" line; the buyer intro lead (main.ts ~1390) says 1.20 (the 14 Oct miss). Then open it from file:// with the network blocked, as a buyer would. 2. bulkhead-examples.zip (free): the Greyling PDF is already re-made (21 Oct); re-export both Greyling .dd2vtt and put them in. pack-check compares text only, so check the pictures by eye. 3. derelict-itch.zip: the chair and the board line on the daily only. Build with build-itch.sh last, after everything else is in. 4. Eight Derelicts pack: the chairs in its PDFs/PNGs/VTT files are old. No one has bought it. Re-render only if a script can redo the drawings from the saved ships without changing them; otherwise leave it and say so. The bulkhead-1.20 devlog goes in the same round.
• Done on the site: the board line shows on the daily only. The itch zip still has it, and it goes in the next batch with the chair.
• BUILT and live 20 Oct (see the entry above). From 21 Oct, read play-derelict (the editor button), -yours pings and card-bhDraw with events.sh. The zip rebuilt 20 Oct 17:59 has the new card and the hand-drawn mode; drawn ships open on the website, not in itch. Sizing as it was:
• Sized 20 Oct: "play a ship you drew in Derelict". Verdict: yes, on the website first. About 2 hours. The itch zip waits for the next real batch. - The game already plays any Bulkhead ship. It does new Game(deserialize(json)). - Boarding: boardingPoint boards at the first airlock door on the hull, or else at a hull breach. With neither it throws 'no way aboard', so show "add an airlock in Bulkhead" instead. - Items: placeItems reads the room key. Note lines starting "Log fragment" become logs and "Salvage:" lines become salvage. Lockers and crates add loose salvage, at most 6. - Hazards come from "Hazard:" notes. Par, air, survivor, drone and so on are worked out from the ship itself. - A ship drawn with no notes still plays, but with only loose salvage and no logs. - The hand-off already exists in the editor (src/main.ts ~1070): share links put the whole ship, deflated, after #s= (a daily-sized ship is about 3.7 KB of URL). The paid file:// edition already sends share links to the hosted site. - To build: 1. Move b64url/inflate into a shared module. 2. Game: loadShip reads #s= as a fourth mode, "yours". It isn't counted, has no board and no vs link, and uses every live rule (rulesFor(null)). Pings: -yours. 3. Editor: a "Play it in Derelict" button next to Share, opening /derelict/#s=.... 4. Derelict end card: the offer becomes "Draw your own derelict in Bulkhead and play it here, or dare a friend with the link". It opens the editor on the day's ship, as the picture does now. 5. Result share: carries the #s= link, so a friend plays the same hand-made ship. 6. Test: a hand-drawn deck with one airlock and two notes plays and scores; no airlock gives the message. - Why yes: on the first itch day 0 of 6 card clicks; jam players don't want a VTT map, but they might want to make a level. It gives them a reason to open the editor, where the $9 upsell is. It is also a jam feature before rating opens on 31 Oct. Not a direct sale: GMs are still the buyers, and the paid files (VTT, PDF) don't change. - Check after: the end card's clicks (go/ pings) and -yours plays in events.sh.
• Itch batch sent 20 Oct (one zip, the last for now): practice card fallback, card picture opens the editor, and the run analytics (run-<how>-s<steps band>-r<rooms entered>of<rooms>-l<logs read>of<logs>, run-left for a quit mid-run, share and share-vs). From 21 Oct read them with events.sh; until the boss uploads, itch plays still send only the old pings.
• From 21 Oct: read the Derelict funnel in events.sh, on the site and in the itch frame (-itch): view, board (a run started), out/dead, card-* (bhOpen, bulkhead, mapLink, buy, how). Since the Derelict links went live (19 Oct 09:00Z to 20 Oct 03:00Z) there was no human /derelict/ view at all, so the jam entry is the first real test. Which card link gets clicked decides what to change on the end screen.
• When a daily ship switches on welding or one-way doors, add them to /derelict/how/ in the same commit.
• After the 20 Oct daily deploy: check a challenge link live. GET /api/board/<day>?vs=<callsign> answers, the title-card line shows; no test run posted to the live board.
• Done 19 Oct: Chronicles card and share tags are live; docent mailed.
• Venting is switched on in the working tree (committed 19 Oct). Do not deploy Bulkhead before the 20 Oct 11:07Z daily, which ships it with the new ship; after it, check a live practice run and the board.
• Jam share 19 Oct: about 53.5% by the JAM-NEW measure, too thin. Next game block: a venting room. A hull-breach room drags you one square toward the breach as you enter or cross it, costs air, and makes a cut or a sealed door matter. Put it behind static venting = false like the 18 Oct switches, so today's board replays don't change. Build it with a test and a bot fairness check, draw it, then switch it on with a daily ship (deploy between 11:07Z runs, never during). Add it to DERELICT-JAM-NEW.md with a fresh measure. Aim for at least 60% before the boss submits (target 24 Oct).
• Derelict links went live 19 Oct 09:17Z (home, nav, /daily/, every day page; noindex dropped). Read real derelict-board and derelict-out pings on 21 Oct against 0 before.
• 18 OCT DAILY (11:07Z): set engine.ts lines 422, 425, 430 and 435 to true (dry-run again 18 Oct 09:xx with the drone fix: 134/134 on and off). Run tests and commit, then the daily. Verify live, rebuild and redeploy the itch zip, then tell the boss they can submit. Then node scripts/media-daily.mjs 2026-10-18 for the docent.
• From 18 Oct: read brief-vtt against generate-* in events.sh (LEARNED 17 Oct, where the editor loses people).
• JAM THEME IS TORCH (17 Oct). Item 1 of the new half is a cutting torch: limited fuel, cut a sealed door or cut through a wall into the next room as a shortcut, a new move letter so replay stays exact, and a lit circle drawn around you. Size the fuel with the bot. Then a survivor and the rest below, fitted to torches where it's true to the game.
• JAM NEW HALF (from 17 Oct 03:00Z; the host wants 50% new content made during the jam, LEARNED 17 Oct). Don't let the boss submit until app/store/DERELICT-JAM-NEW.md clearly outweighs the pre-jam game, aiming for about 24 Oct so there is a week of votes. Candidates, theme permitting, biggest first: (1) a survivor aboard: some ships hold one crew member you can find and walk out (slower, uses air), worth more than any cache, and the logs say where they hid; (2) new ways the ship fights back: power cuts that hide the plan, venting rooms that push you, a door that only opens from one side; (3) four new causes of death, each with logs and room changes; (4) the leaderboard, only if the boss says yes. Fit it to the theme once it's out. Rewrite the step 5 devlog from the JAM-NEW list.
• Jam (17 to 31 Oct, submissions open 03:00Z today): the boss makes the itch page and submits, using /press/derelict. When the theme is announced, read it and work it into Derelict. Competition check on 25 Oct, target top 20.
• Leaderboard: asked the boss 16 Oct. It needs the Cloudflare token confirmed as rotated, or a KV namespace the boss creates. Build nothing until they answer.
• Daily run after 11:07Z if today's derelict is missing.
• AI Browser Game Jam 5 (17 to 31 Oct, https://itch.io/jam/ai-jam-5): a reason to start Derelict on 17 Oct instead of waiting for the 22 Oct decision. Bulkhead is shipped and for sale, so RULES allow app two. Put it to the boss; the boss would join the jam and submit the page.
• Fourteen Ships itch page: handed to the boss 15 Oct. Once it is live: check the page, add it to Bulkhead's page and the site, IndexNow. Compare its views against the free packs (16/11) on 22 Oct.
• Chair fix (20 Oct, live on the site): still old in the itch zip (next real batch), the paid 1.18 file (next release.mjs run, with the rest of the next src batch), bulkhead-examples.zip (Greyling PDF and .dd2vtt maps; the site's Greyling PDF, map image and press picture were re-made 21 Oct), and the free packs. Don't send a zip for it alone.
• GREYLING POST UP 20 Oct 22:11Z (r/Star_Wars_Maps, FACTS). Read it at 24 h, about 22:00Z 21 Oct: score, comments (masked), events.sh for /derelict-one-shot/, the PDF and ?open=/adventure/ editor opens. The next Reddit ask is a week on, not before 27 Oct.
• 22 Oct Reddit slot: draft ready in app/store/REDDIT-STAR-WARS-MAPS.md (r/Star_Wars_Maps, DECK PLAN, RSV Greyling as a Halloween one-shot). Pictures hosted 20 Oct (links in the draft). On 22 Oct: check the one-shot page live, then ask once, on 22 Oct, for 14:00 to 17:00 UTC.
• 22 Oct baseline, read 20 Oct 19:1x with scripts/itch-stats.sh (my-games counts): bulkhead views 44, downloads 4, purchases 0; pack 2 views 12, downloads 1; free pack views 18, downloads 3; derelict views 18. Bluesky 9 followers. Fourteen Ships is still not on the itch profile (handed over 15 Oct).
• 22 Oct, decision point (set 15 Oct): when the sale ends, read itch views, downloads and purchases. If Bulkhead still has 0 sales after the kits bundle and the Owlbear listing have had their chance, stop pushing it as the main work: keep the daily running, and pick app two. Pick it for a market where an AI-made tool is welcome (check each store's and community's AI rule before building), and with a channel that reaches buyers on day one.
• ROLL20 AND DRIVETHRU CLOSED (15 Oct): DriveThru Partners wrote that no standalone artwork "generated in whole or in part by AI" is accepted on any Roll20 or DriveThru marketplace, and that AI-touched titles must carry the Contains AI-Generated Content filter. The packs are made by AI-written code, so they do not go there in any form. Do not resubmit, do not change the Creation Method, do not send the drafted question. The seven drafts can stay in Drafts. The pack kits and store/roll20/ stay as they are (a possible itch bundle, see below).
• Re-plan the paid bet (16 Oct): itch (Bulkhead $9 on sale to 22 Oct, then $12) and the Owlbear store. Facts first: itch views and buys since the sale began, which pages bring the visits that become itch views (events by referrer, sittings). One candidate to weigh: put the ten ready ship kits on itch as a paid map bundle beside Bulkhead, stated plainly as procedurally generated by AI-written code (itch allows that when tagged; check itch's current AI disclosure rule first). No new free packs.
• r/starfinder_rpg is closed: the 15 Oct post was removed under Rule 4 (low effort). Do not ask the boss to message the mods or repost. The next Reddit ask is still not before 22 Oct, and it must read as a post for that sub's readers first (a question, a how-to, a free map), not as a product gallery.
• 22 Oct, after 22:00Z (DECIDED 19 Oct, see LEARNED): Bulkhead stays $9 and does not go back to $12. The boss changes the itch base price from $12 to $9 once the sale has ended; the site already says $9 everywhere, so no set-price run. Then check status (itch $9, site $9) and that the buy button lands on $9.
• When the boss says pack 2 is submitted: take its press/r20 folder down (back it up to the scratchpad first), deploy, and check for 404. Then pack 3 (RSV Umber) the same way, one at a time, to stay under any weekly cap. The page generator is scratchpad/r20page.py; copy it to app/scripts/roll20-page.py if it gets used again.
• The itch page is fixed as of 15 Oct (no video, 3 screenshots, new sample, see-through line, devlog 1.19). From 16 Oct, watch itch views and purchases daily against the 15 Oct baseline (36 views, 3 downloads, 0 purchases), and look at the itch.io/devlogs feed and the referrers in itch analytics if the API shows them.
• When the boss says "devlog": check /bulkhead/devlog lists it, and that it shows on itch.io/devlogs or the tag pages. With each future release, write the devlog in the same turn and put it next to the upload task, so it doesn't get lost again.
• When the boss says "pictures": load the itch page at phone width with Playwright. Check there is no video, there are 3 screenshots with the ship first, there are 10 tags, and the see-through line is in. Then re-run the itch searches ("deck plan", "starship", "map editor") to see whether the new tags show us.
• After the boss posts task 12: read the thread logged out about 2 h and 24 h later, names masked. Draft answers only, nothing goes out without them. Log points and comments in LEARNED.
• Decided 15 Oct (boss asked how anyone pays): no new free packs or free giveaways. The daily derelict stays as the one free hook. Roll20 packs are the main paid bet (buyers already pay $4.99 there and never see our free things). The $12 editor stays, sold on what the free versions don't do: fleet, adventure PDF, print PDF, .dd2vtt, no watermark. The Owlbear extension stays free, as promised in its own text and to the store reviewer.
• itch is indexed (15 Oct). After the boss uploads 1.19: re-read the itch tags and the description's first lines for itch search, and add the see-through line.
• Check PR 174 in a few days: has the label come off, and has a review been requested?
• Next Owlbear panel change: bump manifest version (1.17.2) so the Rogue Store re-reads store.md.
• Ask the boss to post the reply on PR #174 (needs response label). Text is in the chat at 17:07. Put it first in the batch.
• Next lever is reach for the editor, not more Roll20 products: put this week's Reddit slot in the next batched ask (not stacked), after the GitHub token.
• Ask the boss for a new GitHub token (fine-grained, contents read/write on walkertbrown/bulkhead only), to go into .git-credentials. Then push the local commits.
• bulkhead-1.19.zip is built, passes paid-check and pack-check, and is deployed in the rel folder. Batch ask for the boss: on itch, upload 1.19 and delete 1.18 (or I give them the link). Once the uploads API shows 1.19, add the see-through line to itch-description.html for the boss to paste.
• Roll20 one-ship products: add a theme loop (#style: blueprint, dungeon/parchment, print) to roll20-pack.mjs. That's a scripts-only change, no src. 3 themes x GM/player x grid/gridless = 12 images per deck. A space or transparent background would need a src change: render.ts paints t.bg into the void and also uses it to erase hull edges, so it can't just be skipped. Do that after the daily, with tests.
• Roll20: pack 2 onward should be one ship per product ($4.99), with more variants: a space background, a transparent background, emergency lighting. Before building, check whether roll20-pack.mjs can get those from the editor. Give the boss a paste list of image names and tags in upload order. Ask the boss (batched): can image names and tags on a submitted product still be edited in Item Management?
• (done 13 Oct, pack 1 built) Roll20 first product: ships that aren't free anywhere, as good as the application samples. Render each deck at 140 px per square as JPG: GM labeled and player unlabeled, each gridded and gridless. Check that grid lines bisect walls. List each deck's size in squares for the uploader. Write the listing text with the code-drawn and AI-agent disclosure, and price it at least $4.99. Verify it in a real Roll20 page if the boss can (one ask, once it's finished). Then give the boss one link and paste-ready fields.
• The Roll20 batched ask (ticket #491430) is answered: approved. Drop it from the batch.
• 27 Oct: re-read sittings.sh since 2026-10-04T20:00:00Z for saves per web Generate sitting (13 Oct: 3 of 9), intro-pic sittings (13 Oct: 0) and desktop one-press exits (13 Oct: 2 of 6). Act only once there are 20 or more web sittings.
• Late October (Halloween, 31 Oct): a derelict one-shot angle for a Reddit slot after this week's, once the last post went okay (at most one a week). A GM on r/Starfinder2e wanted a ship for a Halloween one-shot. Draft it from the free adventure pages, facts checked, and give it to the boss as a choice. Landing page: /derelict-one-shot/ (RSV Greyling, horror tone, free 8-page PDF, 5 ft squares), checked live 12 Oct. Earliest slot: about 26 Oct, if a post goes out this week and went okay.
• r/starfinder_rpg DRAFT v2 (12 Oct, after Tech Core). Waiting on the boss to pick it over task 8. Not on /press/. Flair: Ad. Images: upper deck, then lower deck, from public/maps/icv-halcyon-drift/. - Title: "[free] ICV Halcyon Drift, a two deck ship map for tech core starship combat, 5 ft squares, png and foundry walls" - Line 1: "an ai agent built the tool that drew this ship, and it wrote this post. i'm the human who posts it." - Line 2: "tech core says every crew should make a starship map showing where each battle station is (p. 167), so here is a free one." - Line 3: "upper deck has the bridge, crew quarters, galley, medbay, cargo, armoury, engineering and the drive. lower deck is a hold where something has been nesting in the crates, a machine shop, life support with pump 2 failing, and four escape pods, two showing green." - Line 4: "one way to place the stations: pilot's console and scanners on the bridge, generator in engineering, gunnery in the armoury and the cargo hold, drone console in the machine shop downstairs. https://bulkhead.bananafest-destiny.com/starfinder-deck-plans/"; - Line 5: "free and cc0: a png and a .dd2vtt per deck with walls, doors and lights, a print pdf and the room key. https://bulkhead.bananafest-destiny.com/maps/icv-halcyon-drift/"; - Line 6: "no image generator. the decks come from dice tables in code that runs in your browser. the editor has a free demo and a $12 full version, which is why it's flaired ad." - Facts checked 12 Oct: the p. 167 quote and the station names are from AoN (LEARNED, 12 Oct); the stations layout is word for word from the live /starfinder-deck-plans/; the files (2 png, 2 dd2vtt, pdf, key .md) are linked on the live map page; the rooms are from the key; sizes and lights are as checked on 6 Oct. Dropped the Foundry importer and sf2e detail to keep it short.
• 19 Oct: views of /starfinder-deck-plans/ and Starfinder queries in Search Console. If any appear, consider a battle station marker (pilot's console, gunnery, generator) in the editor (src, with full tests).
• About 10 Oct: once Tech Core is out, find whether its starship combat sets a scale or size for the ship battle map, or ships sample maps (reviews, Archives of Nethys). If it does, match /starfinder-deck-plans/ to it. 19 Oct: Search Console queries containing starfinder.
• This week's one Reddit slot, waiting on the boss: task 8 (r/FoundryVTT, already on /press/) or r/starfinder_rpg for Tech Core week (draft in plan/2026-10-05.md Next, verified 6 Oct 01:07). If they pick r/starfinder_rpg, put it on /press/ with one URL and copy-paste text, then read the thread back logged out 24 h later.
• 8 Oct: RUM against the pings again (visits.sh vs events.sh since 5 Oct). If RUM is still 0 while the pings have 10+ views, put one line in the batch: does the Web Analytics dashboard show visits after 4 Oct? Until then, count visits with events.sh.
• 6 Oct after the 11:07 daily: the first daily built by the lights-count script. Read its page's "carries …" line against its .dd2vtt light count.
• Batch ask candidate, after task 3 and task 1 (LEARNED, 5 Oct): FoundryMods. Ask the boss to sign in to foundrymods.com and say whether a module that isn't on foundryvtt.com can be added. If yes, list Bulkhead Deck Plans by its manifest URL. Facts only; it is an alpha site.
• 19 Oct: /foundry/ in Search Console (query,page filtered to foundry, --fresh). Its title changed on 5 Oct to lead with "Free sci-fi starship maps for Foundry VTT v14". It had no rows before the change. Re-inspect it too, so we know Google has crawled it since 5 Oct.
• From the texttotabletop read (LEARNED, 5 Oct): one search, one page, tied to a moment. Candidate for Tech Core week: put "Starfinder 2e" in /starfinder-deck-plans/'s title and h1, which is true (5 ft squares per the 2e Player Core, and the sf2e system was checked on 29 Sep), and say nothing about what Tech Core contains. First, at the 9 Oct inspect, see whether Google has the page at all. If it's still "Discovered", a title change won't matter yet. Don't write a blog-style page per topic until one page shows clicks.
• After r/starfinder_rpg (so the week of 12 Oct at the earliest), and only if task 8 didn't go bad on the AI line: an r/Star_Wars_Maps post (LEARNED, 5 Oct). [DECK PLAN] flair, or [Self Promotion] if it links the $12 page. One derelict's decks as PNGs with the size in the title ([WxH]), like the makers there do. AI line first; the creator's one rule is to say when AI is used. Second line: the maps come from dice tables in the page. Link a free map page, not the store. Not a Star Wars ship, and no Star Wars names. Before writing it, check the sub's sidebar again and look at the last 2 weeks of [DECK PLAN] posts.
• Foundry validation ran on 14.365 because foundry-validate.mjs runs on demo.foundryvtt.com, which is on that build. Stable is 14.368. That isn't ours to move: the demo will catch up. Each Sunday run's log line names the core it used. If it ever goes back to 13.x, the v14 claim on /foundry/ needs a look.
• Owlbear page, from 4 Oct: 7 views of /owlbear-rodeo-dd2vtt/ since 1 Oct 12:10, and 0 obr-copy, 0 obr-rogue. At 20+ views with still 0 copies, make the store link the page's first button above the manifest URL (one press, nothing to paste), then count obr-rogue again.
• r/starfinder_rpg, the week of Tech Core (out 7 Oct). Write it on Tue 6 Oct, after task 8's first day shows how r/FoundryVTT took it, and give it to the boss for Wed 7 or Thu 8. Shape: a gallery post with the Ad flair (the page links the $12 version), three to four deck PNGs at 5 ft squares from one ship, and the first line saying an AI agent made the maps and the post. Second paragraph, from the 30 Sep lessons: the maps come from dice tables in code that run in your browser, with no image model and no server. Never call Generate optional. A free .dd2vtt per deck for Foundry's sf2e system, and a link to /starfinder-deck-plans/. Don't claim Tech Core has starship rules: neither source says so. No staged replies. If task 8 goes negative on the AI line, hold this one and say why. - The ship is chosen (4 Oct): ICV Halcyon Drift. Images: the upper deck (3600x1700, 233 kB) and the lower deck (2700x1700, 151 kB), both from public/maps/icv-halcyon-drift/. The link is /maps/icv-halcyon-drift/, so the post also tests a map page's opens and downloads directly. Tuesday adds only the text. - DRAFT (5 Oct, from the key on disk; Tuesday adjusts it, then re-check every fact against the live page before /press/). Flair: Ad. Images: upper deck, then lower deck. - Title: "[free] ICV Halcyon Drift, a two deck starship on 5 ft squares, png and foundry walls (36x17 and 27x17)" - Body, line 1: "an ai agent built the tool that drew this ship, and it wrote this post. i'm the human who posts it." - Body, line 2: "no image generator here. the decks come from dice tables in code that runs in your browser, laid out room by room on a 5 ft grid." - Body, line 3: "upper deck has the bridge, crew quarters, galley, medbay, cargo, armoury, engineering and the drive. lower deck is a hold where something has been nesting in the crates, a machine shop, life support with pump 2 failing, and four escape pods, two showing green." - Body, line 4: "free and cc0: a png and a .dd2vtt per deck (walls, doors and lights, imports into foundry with the universal battlemap importer, works under the sf2e system), a print pdf and the room key. https://bulkhead.bananafest-destiny.com/maps/icv-halcyon-drift/"; - Body, line 5: "the editor that made it has a free demo and a $12 full version, which is why it's flaired ad." - Facts used: sizes from the page (36x17 upper, 27x17 lower, 100 px per 5 ft square). Rooms are word for word from icv-halcyon-drift-key.md. sf2e is from the 29 Sep check (sf2e 1.5.1, verified on v14). Checked 5 Oct: the PNGs are 3600x1700 and 2700x1700, and the .dd2vtt files say 36x17 and 27x17 at 100 px, with 19 and 8 portals and 6 and 3 lights.
• Batched asks, after task 1 (facts only): did [email removed] ever answer ticket #491430 (Roll20 Marketplace application, 15 Sep)? If it answered, what did it say? If it is silent past 13 Oct (4 weeks), the boss can reply on the ticket. Roll20's forum says that helps. If it was approved, rebuild store/roll20/halcyon-drift-pack.zip from the 1.18 build before uploading, because the current pack was rendered from 1.12.2. Better: build it from a ship that isn't free on /maps/, because Halcyon Drift is CC0 there and is the r/starfinder_rpg ship.
• 11 Oct: /maps/ opens again (events.sh since 1 Oct 12:10, 'view /maps/<slug>/'). It was 0 of 12 on 4 Oct, and the screenshots showed no fault. At 20+ views with 0 opens, try a direct download link on each card.
• 16 Oct, when The Last TTRPG Jam opens (theme on its page): re-read the rules, then make a one-sheet derelict boarding game on A4. The press is app/scripts/one-sheet.mjs (ship json, side-two HTML, out PDF); generate a fresh one-deck derelict on the day. Write all game text on or after 16 Oct; the jam says no pre-released content. Side one is a Bulkhead-generated derelict GM map with its trail. Side two is rules, a d6 of what goes wrong, a clock and the theme. The first line says an AI agent made it, and the map line credits Bulkhead. CC0, free. Only when the PDF is finished and checked, give the boss one /press/ step: a new free itch project and the jam submit. Next jam re-check is 17 Oct.
• When the boss says "pictures" or task 1 is done: fetch the itch page, check the screenshot order, that the video is gone and the tags, and that the demo file is the 816 kB examples zip (by size; never print md5s).
• 9 Oct inspect, also: /derelict-one-shot/ (unknown on 3 Oct; sitemap resubmitted and Bing-submitted 09:2x) and the four still-Discovered landing pages. On 3 Oct /deck-plan-generator/ had moved to indexed (crawled 1 Oct).
• 9 Oct, with the Google re-inspect: count bingbot hits since 2 Oct 07:16 on the 20 paths sent with bing-submit (/, the 7 keyword pages, /maps/ and the 11 map pages), against the 26 Sep week, when IndexNow alone left bingbot reading one page. If Bing still hasn't read them, bing-submit is as empty as IndexNow, so stop spending turns on it.
• Real-room batch, after task 1: in Owlbear with Dynamic Fog, check that a bridge "Window" (now sent closed) stops a token and that the GM can open it with the door tool. The source says yes. This is just to see it.
  • (Dropped 5 Oct, 08:2x: Scene Importer's own parser, run in node on our zip, imports 0 scenes because v11+ packs keep walls as separate keys. See LEARNED. Not a room test.)
• If a GM ever reports a room with no way in on a derelict: it opens on a hole (the 13:09 guard test proves it). Check how a breach draws at small sizes and in the PNG before touching the generator.
• itch support follow-up: it's task 3 on /press/ (a reply in the 18 Sep thread). After task 1, a 1.18 devlog replaces the unpublished 1.17 draft. Devlogs get indexed even while the page isn't. Once indexed: add the ttrpg tag and re-run itch-indexed.mjs.
• /maps/ from 4 Oct: Free maps is the intro's second visible button now. Count sittings that go / → /maps/, and whether they open a map page or come back and press Generate (before: 8 of 9 /maps/ sittings came from /, and none opened a map page). If it only pulls people away from the derelict, move it under More.
• Owlbear funnel, 4 Oct: bash scripts/installs.sh 2026-09-20T00:00:00Z against 34 listing / 25 manifest / 10 icon / 6 panel (3 Oct). If the panel count rises while the listing count holds, more people who add Bulkhead are finding it.
• Owlbear path, from 4 Oct: views of /owlbear-rodeo-dd2vtt/, then obr-copy and obr-rogue (counted since 1 Oct, 12:10), then obr-view, then obr-send, in events.sh. If people view the page but nobody copies, the page is what to fix. If they copy but nothing opens the panel, look at the install step in Owlbear. After each daily, run the switch check on a worktree.
• Phone Generate sittings after the room key fix (deployed by 07:17): per sitting, do phones now press Another one, Save or Link? Also per sitting: intact or derelict, and where it started (intro-derelict / intro-intact are counted from 2 Oct, about 05:12; the demo intro has led with the derelict since 05:00). Before, by app/scripts/sittings.sh 2026-09-28T00:00:00Z 2026-10-02T00:00:00Z: 5 of 29 web sittings saw a derelict, 1 saved or linked, 9 pressed more than once (the 04:54 count of 3 of 22 was off; see the 08:08 actual). Run the same script from 2026-10-02T05:12:00Z for after. 25 Sep to 1 Oct counted 103 intact presses against 13 derelict, but one phone made 58 presses on 1 Oct. If real sittings mostly stay on intact (the select's default) and never see a story, try derelict as the first press, then measure saves. Group by hour, country and device as on 1 Oct (a temporary script in app/scripts/, removed after). Read from/ alongside it.
• Batch question after task 1, on the same Android phone: download bulkhead-1.18.zip from /press/, unzip it, and open bulkhead.html. Does the editor run, and does Generate work? Then the same on an iPhone if there's one to hand. The file itself runs from disk in WebKit and in Chromium as a phone, even with storage blocked (the 2 Oct 18:07 actual); what's unknown is whether the phone opens it in a browser at all. If it doesn't, the itch page and the demo's upsell must say "for a computer" before anyone pays.
• Batch questions after task 1, all in one real Owlbear room. First, the .dd2vtt export from the panel on an Android phone: does a "downloaded" notice show, what is the file called in Downloads (it should end .dd2vtt), and does a two-deck ship bring up a "download multiple files?" prompt? (BR, 30 Sep: three presses, then a desktop save 25 min later. No sandbox on the frame and ~1 s to the download, checked 09:07.) Then a hex send and dragging in a -WxH PNG.
• Before task 1: after any src fix a buyer would get, run release.mjs 1.18 (it runs pack-check), --fix stale pack PDFs, re-make the Greyling by hand if it is flagged, bump ?v= on /press/ and itch-description, deploy, read every changed file back. Since 19:2x on 3 Oct: 1.18 zip ?v=1004b (since 21:2x on 4 Oct, with the short-phone card fix and the Global Illumination README lines), pack ?v=1018 (since 20:2x), examples zip and Greyling ?v=1004. From the upload on, pack ships don't change.
• Old .dd2vtt walls: done on 1 Oct (the daily archive, the weekly zip, Foundry 1.4.0). The /maps/ pages and both free packs (store/ = public/packs/; store/ is what I prepared for itch, but I can't see itch's uploaded files, so this is an assumption) already had the right walls, so the itch free packs need no re-upload. Drop that from the after-task-1 batch.
• Task 1 is now the file swap (the switch went live on 3 Oct). When status shows "itch sells the current" ok for both files, take the paid zips off /press/, drop the pack from the zip check, and paste the 1.18 devlog (store/DEVLOG-1.18.md) as the next ask.

01:07: The 22 Oct decision, read early

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

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

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

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

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

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

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

02:02: The boss already has a developer account

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