00:10: one report after a post

00:10: one report after a post

Monday is read off five scripts. Put them behind one command that takes the post URL and the time it went up, so the reading after task 8 (and task 9 on Wednesday) is the same every time and nothing gets skipped. Try it on a dry run now.

Next

1. On "post": node scripts/post-pack.mjs, then check the post's link and all 4 images.
2. 06:07 and 11:37 daily checks. The daily runs about 11:07Z.
3. Morning: decide whether task 8 leads with the walk clip (Reddit would need an mp4 or gif, not the webp), then 14:00 to 16:00 UTC is task 8.
4. After it: bash scripts/after-post.sh <url> 2026-09-28T14:00:00Z, then at +24 h.

00:40: videos that play on an iPhone

(Decided first: task 8 stays a gallery on Monday and the walk video waits for October, so the two formats get compared on separate posts.) The site answers byte-range requests with 200 and the whole file, and iPhone Safari wants 206 for video. /press/ tells the boss to open short.mp4 and save it. Add a small Worker that runs only for *.mp4 and answers Range with 206, and leave everything else on static assets. Check after deploy with curl -r and smoke.

01:15: task 8 checked end to end

Task 8 goes up in about 13 hours. Before then, open /press/ the way the boss will on a phone and check every image, link and text box in task 8: each one loads, the first line says an AI agent made the tool and wrote the text, the post text follows the r/FoundryVTT rules as read, and the links it gives go to live pages with the manifest URL that installs. Fix anything wrong now, not at 14:00.

Next

1. On "post": node scripts/post-pack.mjs, then check the post's link and all 4 images.
2. Daily checks at 06:07 and 11:37. The daily runs about 11:07Z.
3. 14:00 to 16:00 UTC: task 8, now 3 in-Foundry images. Then bash scripts/after-post.sh <url> 2026-09-28T14:00:00Z, and again at +24 h.
4. Before Wednesday, give task 9 (r/OwlbearRodeo) the same check against that sub's rules and template.

01:45: task 9 checked against its sub

Task 9 (r/OwlbearRodeo, Wednesday) gets the same check that caught task 8's image: re-read that sub's rules, flairs and any wiki, logged out, and check every image, link and text box in task 9 against them. Also check the Owlbear extension itself still installs from its manifest. Fix anything wrong now.

Next

1. On "post": node scripts/post-pack.mjs, then check the post's link and all 4 images.
2. Daily checks at 06:07 and 11:37. The daily runs about 11:07Z.
3. 14:00 to 16:00 UTC: task 8. Then bash scripts/after-post.sh <url> 2026-09-28T14:00:00Z, and again at +24 h.
4. Wednesday: task 9, then after-post.sh on it the same way.

02:30: /foundry/ ready for Monday's readers

Task 8 sends r/FoundryVTT readers to /foundry/, and many will read it on a phone. Load it at phone width and at desktop width in headless Chromium, blocking the beacon. Check that the install steps come first and read clearly, that the new animated image loads and isn't too heavy on mobile, and that there is one clear next step to the free editor and one to the $12 one. Fix whatever is weak.

Next

1. On "post": node scripts/post-pack.mjs, then check the post's link and all 4 images.
2. Daily checks at 06:07 and 11:37. The daily runs about 11:07Z.
3. 14:00 to 16:00 UTC: task 8. Then bash scripts/after-post.sh <url> 2026-09-28T14:00:00Z, and again at +24 h.
4. 4 Oct: check that the Sunday run made preview.webp and moved its width and height.

03:30: can anyone find us yet

Three ways in that need nothing from the boss: itch search, Bing and Google. Run itch-indexed.mjs and index-status.mjs to see where each stands today. Push the pages that changed tonight (/foundry/, /owlbear-rodeo-dd2vtt/) to IndexNow. Then decide from the numbers whether task 3 (the itch nudge) needs rewording, or whether something on our side is keeping a page out.

Next

1. On "post": node scripts/post-pack.mjs, then check the post's link and all 4 images.
2. Daily checks at 06:07 and 11:37. The daily runs about 11:07Z.
3. 14:00 to 16:00 UTC: task 8. Then bash scripts/after-post.sh <url> 2026-09-28T14:00:00Z, and again at +24 h.
4. 30th: crawlers.sh baseline, to set against the 21st numbers above.

04:45: answers ready for task 8's comments

A Reddit post lives or dies on its first hour of comments, and the boss can't answer Foundry questions without asking me first. Guess the questions r/FoundryVTT will ask from the comments on the top Commercial Assets posts there, check every answer against the module files, and put copy-paste replies under task 8 on /press/. Each reply is lowercase and short, with no em-dashes, and makes clear the answer comes from the agent.

Next

1. On "post": node scripts/post-pack.mjs, then check the post's link and all 4 images.
2. Daily checks at 06:07 and 11:37. The daily runs about 11:07Z.
3. 14:00 to 16:00 UTC: task 8. After it, watch the thread with reddit-watch.mjs and draft replies for any comment the list does not cover. Then bash scripts/after-post.sh <url> 2026-09-28T14:00:00Z, and again at +24 h.

05:50: what a default token sees in our scenes

The one comment I could not answer is the one those threads ask most: "my token only sees the lit bits". Our scenes set no environment, so Foundry uses its defaults: darkness 0 and global light off. On the v14 demo, drop a token with default sight (range 0) into a scene and test with canvas.visibility.testVisibility whether it sees an unlit corridor square and a lit room square. If default tokens see only the lights, the scenes need global light on, which means a module fix before 14:00. Either way, the answer goes under task 8.

Next

Task 8's pictures were taken before 1.2.1. The "one token's vision" shot shows the old behaviour, where the token is dark outside the lights. At 06:25, retake it on the v14 demo from the 1.2.1 pack so the post shows what a reader will get. Check all three images against the module, then check the daily at 11:37. Task 8 goes out at 14:00 UTC.

07:10: retake the token-vision picture from 1.2.1

Task 8 image 2 was made before global light went on. Retake it on the v14 demo using the 1.2.1 Halcyon scene and one token in the corridor, so the post shows what a reader gets. Then check images 1 and 3 still match.

Next

The walk video on /foundry/ was recorded before 1.2.1. Check whether it shows the same lights-only darkness; if so, re-record it from the 1.2.1 scene. Then check the zoo for remarks, the daily at 11:37, and task 8 at 14:00 UTC.

08:07: does the walk video show the old darkness

The walk video on /foundry/ was recorded before 1.2.1. Look at its frames. If a token walking the corridor sees only lit patches, re-record it from the 1.2.1 scene, then swap it on /foundry/.

Next

At about 08:25, open /press/ task 8 at phone width (390 px) the way the boss will see it. Check that the three images, the title, the flair line, the Copy buttons and the reply section read and work in order. Fix anything that is awkward on a phone. Then the daily check at 11:37 and task 8 at 14:00 UTC.

08:08: task 8 on a phone

Open /press/ task 8 at 390 px wide, the way the boss sees it. Check the images, title, flair line, Copy buttons and replies, and fix anything awkward.

Next

Daily check at 11:37: status, and confirm the 28th's derelict posted. Task 8 goes up at 14:00 UTC; after it, run reddit-watch and after-post.sh, and draft replies for any comment not covered. Until then, look over the Owlbear listing PR (#174) for any new review comments, read-only through the public API.

09:07: /foundry/ as a reader from today's post sees it

Task 8's link lands on /foundry/. Open it at phone width and at desktop width. Check that the first screen says what it is and how to install, and that the way on to the editor is visible without hunting. Fix what isn't.

Next

Daily check at 11:37. Task 8 goes up at 14:00 UTC. Then reddit-watch and after-post.sh, and draft replies for any comment the nine don't cover.

10:07: the editor as a Foundry reader meets it

A reader who clicks through from /foundry/ lands on the editor. At desktop width, from first screen to trying an export, check it is clear what the demo does, what Foundry export needs, and where the $12 is. Fix what is unclear.

Next

Daily check at 11:37. Task 8 at 14:00 UTC, then watch it.

11:11: make sure the thread watcher still reads Reddit

Task 8's comments get read with reddit-watch.mjs. Run it now against an older post of ours and check it still returns the score and the comments, so it doesn't fail at 14:00.

Next

Task 8 goes up between 14:00 and 16:00 UTC. When the boss sends the link: run reddit-watch, then after-post.sh, and draft replies for anything uncovered. Until then, check the zoo for remarks.

12:07: do search crawlers know the Foundry pages

Check the zoo for boss remarks. Then run crawlers.sh and see whether Googlebot and Bingbot have fetched /foundry/ and /foundry-dd2vtt/ since the module grew. If not, find why: sitemap lastmod, internal links, IndexNow.

Next

Task 8 goes up between 14:00 and 16:00 UTC; wait for the link. Re-run crawlers.sh on the 30th.

13:07: two more checked replies for task 8

Task 9's text still holds; the daily's tags were already settled on the 25th. Add answers for two questions a Foundry reader is likely to ask that the nine replies don't cover: the package list, and system and metres. Check each against the pack first.

Next

Task 8's window opens at 14:00 UTC. Wait for the link, then run reddit-watch and after-post.sh.

14:07: is task 8 up yet

The window is open. Read r/FoundryVTT/new logged out and look for our post. If it's up, run reddit-watch and after-post.sh and start watching. If not, use the time on something that doesn't touch the boss.

Next

When the Monitor or the boss reports the post: run reddit-watch and after-post.sh on it, then check the /foundry/ traffic and module fetches the hour after. Draft replies for any uncovered comment. Re-arm the watch at 14:37 if nothing has shown up, until 16:30.

14:12: task 8 page at phone width

The boss is doing task 8 on a phone now. Render /press/ at 390px from the top link to #task8, check nothing runs off the side, every Copy button in task 8 copies the right text, and the image downloads work.

14:38: re-arm the task 8 watch

The first watcher ran out at 14:38 with no sighting. Re-arm it and confirm the /new read itself still works.

14:45: is r/FoundryVTT/new stale for us

The watcher has seen no post newer than 10:42Z for four hours. Load /new with a cache-busting query and compare it with the plain read. If the plain read is stale, point the watcher at the fresh URL.

Next

The watcher is re-armed at 15:08 and runs to about 16:30 in 30-minute turns. On a sighting or a link from the boss: reddit-watch, then after-post.sh with a start of 14:00Z. If there is still nothing by 16:30, the window has closed. Ask the boss once whether it went up (it may be in the mod queue) and move task 8 to Monday 12 October, since Commercial posts are allowed at most twice a month. Daily check at 17:37.

15:40: what Bing and DuckDuckGo have indexed

Google is slow, but Bing sent a visit this week. List which pages a site: search on Bing and on DuckDuckGo (which uses Bing) returns, and which key pages are missing. The result decides what the Search Console / Bing Webmaster ask should name.

16:38: task 8 window passed

The watcher is out at 16:38 and nothing has shown on /new. The sub only requires a Monday in UTC, so the post is still allowed until midnight. Change the press page to say so, name 5 October as the fallback, deploy, and ask the boss once.

Next

Ask the boss once whether task 8 went up. Daily check at 17:37, with one read of r/FoundryVTT/new at the same time. If there is no post today: on Sunday 4 October, after the 1.3.0 run, update the task 8 title and body to the new count and dates.

17:07: daily check, and is /new lying

The daily check is all clear, 23 of 23. Then work out why /new has shown nothing after 11:04 for six hours.

17:50: which Bluesky hashtags carry traffic

The daily post ends with #ttrpg #battlemap #osr #scifi #travellerrpg, chosen in the first week. Now that every daily also lands in the Foundry module, measure how busy candidate tags are, and which the daily's past likes came from if that can be seen, then change the tag line only if the numbers say so.

18:50: task 9 page at phone width

Task 9 (Owlbear) is due on Wednesday. Run the same phone check that task 8 got: no sideways scroll, every Copy button copies its own text, every picture loads. Then read its text against the extension as it is now (1.17.1).

19:55: GM keys into the Foundry module

The module claims "ready to play", but the room keys (story, hook, hazards, salvage, trail for every room) are not in it: only on the web pages as .md. Build a Journal compendium, one entry per ship with a page per deck, and point each scene's journal at its ship. This slot: a prototype in the scratchpad, checking the key files map one to one onto the 36 scenes. No deploy until it has validated on the v14 demo.

Next

Wire the journal pack into foundry-module.mjs: build it from the extracted scenes, compile it to packs/gm-keys, and add it to module.json packs as JournalEntry. Then validate the 23 entries on the v14 demo, the same way as the scenes (in memory, as a player). Release it only after that, as 1.3.0 ahead of the Sunday run, or with it. The 5 October post can then say the keys are in. Keep re-arming the r/FoundryVTT watch to midnight.

20:10: wire the GM keys into the module build

foundry-module.mjs builds packs/gm-keys from the scenes it just packed and adds it to both module.json files as a JournalEntry pack. Test the build on a copy, not on public/, so nothing changes before the v14 demo check.

Next

After midnight UTC, once the task 8 window has closed: run foundry-module.mjs 1.3.0 for real, run foundry-validate --note, check the counts across the pages, deploy, and run smoke. Say on /foundry/ that GM keys are included. Then refresh the task 8 text for 5 October (37 or more scenes, GM keys in). Keep re-arming the r/FoundryVTT watch to midnight.

21:08: stage the 1.3.0 words

Write what the GM keys add into the module description (in foundry-module.mjs), the /foundry/ page and both READMEs, so the after-midnight release is one run of the script, validate and deploy. Commit only. Nothing deploys before midnight UTC.

22:07: a picture of a GM key in Foundry

The 1.3.0 page and the 5 October post need to show the keys, not only say so. Shoot the Sable Dawn key clean on the v14 demo (no dice on top, no banner), crop it to the sheet, and stage it for /foundry/. Not deployed before midnight.

23:08: daily check, and the task 8 text for 5 October

The daily check is all clear, 23 of 23. Then draft the 5 October title and body for task 8, with the GM keys in and no number that the Sunday run moves without me. It gets applied after the 1.3.0 release, not before midnight.

00:10: one report after a post

• New app/scripts/after-post.sh <post url|-> <since>: runs reddit-watch on the post (for a Reddit URL), then visits, events, clicks with itch views, installs and itch-stats, in that order.
• Dry run since 27 Sep 00:00: 1 real page view (the home page), no demo events, no Foundry installs, 3 Owlbear manifest fetches (one is the scraper string). itch: Bulkhead 16 views and 0 purchases, pack 1 at 6 views, pack 2 at 2. Bluesky: 4 followers.
• clicks.sh counts 2 buy clicks on the 27th (map and owlbear surfaces) from browsers that loaded a page first. itch views did not move (16 before, 16 now), so they did not reach the store. Treated as not real.
• Monday after task 8: bash scripts/after-post.sh <post url> 2026-09-28T14:00:00Z.

00:40: videos that play on an iPhone

• Task 8 stays a 3-image gallery on Monday. The walk video waits for the October post, so each format gets its own post to compare.
• New app/worker/range.js, wired in wrangler.jsonc with run_worker_first: ["/*.mp4"], so only mp4 requests reach it and everything else is still plain static assets. It answers Range with 206 and the slice asked for, 416 when the range is past the end, and a plain GET or HEAD with 200 as before.
• Checked live: short.mp4 and short2.mp4 give 206 for 0-99 (100 bytes) and for an open-ended range, and 200 for the whole file. A range on a PNG still gets 200 from assets. A missing page and a missing mp4 both give 404. Smoke is 38/38 pages and 39/39 links, and status is all 23 clear.
• Why: iPhone Safari will not play a video from a server that ignores Range, and /press/ post 9 tells the boss to open short.mp4 and save it.

01:15: task 8 checked end to end

• Everything task 8 links to answers 200: images 1 and 2, /foundry/, module.json (1.2.0, the right manifest and download URLs, verified 14) and the zip (35 scene PNGs, the last from 26 September, which matches the body text).
• I re-read the r/FoundryVTT sidebar, the posting-guidelines wiki and the post template, logged out in headless Chromium, because the JSON API is blocked. Commercial Assets posts are still Mondays (UTC) only, at most twice a month, with the Commercial Assets flair and the template. The template also says "Any Images included must be foundry specific. (Content should be displayed inside foundry)". Task 8 image 3 was our all-35 contact sheet, which is not inside Foundry, and that is grounds for removal. The last check missed this.
• Fix: a new scripts/foundry-demo-shot.mjs joins the public v14 demo as a player, in memory only, and draws the derelict Nimbus station ring deck with Foundry's full UI showing: 100 walls, 16 doors, 1 light, core 14.365. That picture is now image 3, and the contact sheet is gone from the task. The body now says the pictures are "two of the scenes ... a ship lit and then with one token's vision, and a station".
• Deployed. The new image is live (39.5 KB) and /press/ carries it. Smoke 38/38 and 39/39. The body has no em-dashes, and its first line still says an AI agent made the module and wrote the post.
• Finished 01:35.

01:45: task 9 checked against its sub

• I re-read the r/OwlbearRodeo sidebar logged out; the wiki is disabled. There are 3 rules. Rule 2 asks posts to start a discussion and not just share a link. Rule 3 removes posts that are mainly artwork or maps, but screenshots that show Owlbear in use are allowed. The sub has an "Extension 🔌" flair, and this week's extension posts use it.
• Fixed on /press/ task 9: added the flair. The post now leads with the extension's own panel (new press/obr-panel.png, a copy of obr/derelict.png) so it reads as a tool post, and the fog picture comes second. The body ends on a question for sci-fi GMs about what they would want generated. There are still no em-dashes, and the first line still says an AI agent made it.
• The fog picture (press/post6-owlbear.png, and the same file at obr/in-owlbear.png, which the store listing and /owlbear-rodeo-dd2vtt/ use) had a line of text cut in half along its bottom edge. I cropped both copies from 1920x700 to 1920x630.
• The extension itself is fine: manifest 1.17.1 with CORS *, the popover /obr gives 200, and the icon gives 200. Store PR #174 is still open, last updated 24 Sep.
• Deployed. Smoke 38/38 and 39/39, status all 23 clear.
• Finished 02:20.

02:30: /foundry/ ready for Monday's readers

• Checked the claims: the page says current stable is 14.368, and foundryvtt.com/releases still lists 14.368 as the newest. The validation note (1.2.0, 35 of them) matches the live module. The install steps, the manifest and the zip are fine.
• Weight: the contact sheet at the top was a 577 KB PNG with no width or height, so a phone downloaded half a megabyte and the page jumped while it loaded. The page now uses preview.webp, the same sheet at 108 KB, with width and height set. The PNG stays for og:image and the manifest.
• foundry-module.mjs writes the WebP next to the PNG every Sunday and rewrites the img width and height to the new sheet size. Tested on the scratch copy: 36 scenes made a 6-row sheet, and the page attributes went to 1599x1145.
• Phone check in headless Chromium at 390 px, beacon blocked: no sideways scroll. The top shows the title, the AI note and the sheet; the Install heading is just below the first screen.
• Deployed. Smoke 38/38 and 39/39.
• Finished 03:25.

03:30: can anyone find us yet

• itch-indexed.mjs: 0 of 3 pages are in itch search or browse. Everything on our side checks out, so they are still in the new-seller review queue; task 3 (the nudge to itch) stays as it is.
• Search engines: index-status.mjs got nothing usable. Google served a CAPTCHA, DuckDuckGo an anomaly page, and Bing returned the same unrelated results for five different queries. LEARNED.md already said scripted rank checks do not work, and I should have read it before running them. The crawler log is the measure that works: since the 21st, Googlebot has fetched 99 times across 26 paths, Bingbot 61 times across 30, and Applebot 14.
• IndexNow accepted /foundry/, /owlbear-rodeo-dd2vtt/ and /press/ (200).
• Fixed: the homepage declared its icon as an inline data URI, and /foundry/ and the 404 page declared none. Search engines fetch a real icon file to show beside a result, and Googlebot-Image had a 404 on /favicon.ico before that file existed on the 21st. All three pages now link /favicon.svg and /favicon.ico, both 200. Checks pass (tests 34/34), deployed, smoke 38/38 and 39/39.
• Finished 04:30.

04:45: answers ready for task 8's comments

• I read the comments on the four top free-map posts on r/FoundryVTT (407 to 749 points), logged out. What people asked: installs that show no maps, background paths on v14, which Foundry version, tokens that only see lit areas, what software made the maps, use in Owlbear or other VTTs, watermarks, and one module versus many. Automod also posts a system-tag reminder on posts with no system tag.
• Under task 8 on /press/ I added 8 copy-paste replies. Each one starts "the agent that built this, answering:", is lowercase and has no em-dashes. The topics: AI, versions, install, grid and scale, what software, other VTTs, licence, and more to come.
• Checked against the files: 100 px, 5 ft squares with no padding. One compendium, with the images inside the same module. Minimum v12, verified 14. Every deck is its own scene. The module PNGs carry no watermark. I left out an answer on lighting and vision because I could not verify how Foundry treats darkness 0 without global light on each version.
• Caught before shipping: /packs/ returns 404 because it has no index page. The reply about other VTTs now points to /free-sci-fi-battlemaps/, which links every zip, and to /daily/. Every URL in the replies gives 200.
• Deployed. Smoke 38/38 and 39/39, and the page has all 8 replies.
• Finished 05:45.

05:50: what a default token sees in our scenes

Finished 06:17. Tested on the Foundry v14 demo (14.365): a token with default sight (enabled, range 0, basic) in our scenes as built saw only the two placed lights through open doors. It could not see its own corridor. With global illumination on, it sees its line of sight, and closed doors still block, at darkness 0 and 0.8. foundry-module.mjs now turns global light on in every scene. Rebuilt as module 1.2.1: 36 scenes (the 27th's derelict came in too), all 36 pass strict validation, and the /foundry/ note moved. Deployed. Live module.json says 1.2.1, the zip returns 200 (5.9 MB), and /foundry/ says 36 scenes and 16 to 27 September, with a line on global illumination. /press/ task 8: counts moved to 36, a note that 1.2.1 fixed this, and a ninth reply for "my token can't see anything". Smoke 38/38 and 39/39. Status 16/20; the 4 failures are today's daily, due about 11:07Z.

07:10: retake the token-vision picture from 1.2.1

Finished 07:16. I retook the vision shot on the Foundry v14 demo (14.365) as a player, in memory only. The scene is the ICV Halcyon Drift upper deck, extracted from the 1.2.1 pack unchanged (global light on), plus one token with default sight (range 0). The token sees the whole corridor, the bridge and drive through their open doors, and slivers of the side rooms. The demo confirms behind a closed door is false and the corridor far end is true. The old picture, from before 1.2.1, showed only lit patches. The player seat's PF2e user-config dialog opened over the scene, so it is now closed before capture. The new picture replaces task 8 image 2 on /press/ and the vision picture on /foundry/, with alt text and the caption updated to say default sight. Deployed; both live files are byte-identical to local, and smoke is 38/38 and 39/39. Images 1 and 3 are lit views without token vision, so global light doesn't change what they show and they stay. The walk video on /foundry/ was made before 1.2.1 and has not been rechecked.

08:07: does the walk video show the old darkness

Finished 08:08. No re-record needed. I pulled four frames from the 43-frame walk video on /foundry/. The token sees down the corridor and into each room through its open door, and explored rooms stay dimmed. The video was recorded with sight range 40, and 1.2.1's global light gives any token at least that much line of sight, so the video matches what a reader gets. No page on the site still shows an old scene count (looked for 30 to 35 next to scenes, decks or starship). I also dry-ran after-post.sh over the last 24 hours as a baseline before task 8: 2 real page loads (both /, direct), no demo editor events, 0 Foundry manifest or zip fetches by anyone else, 2 distinct fetchers of the Owlbear manifest. itch lifetime: Bulkhead 16 views, pack-free 6, pack-2 2, 0 purchases. Bluesky: 4 followers. installs.sh counts /foundry/module.json and the zip, so an install from the post will show up.

08:08: task 8 on a phone

Finished 08:11. I opened /press/ at 390 px on the live site, with the beacon blocked, and paged through task 8. The page has no horizontal scroll. The three images, the title and body boxes with their Copy buttons, and the nine replies all read in order, and the new vision picture shows. Problem: task 8 sits about 11,000 px down the page, and the top line still said "two things, both short" with no word about today. I added a bold first line: today only, 14:00 to 16:00 UTC (9 to 11 Central), with a link that jumps to task 8. Task 11's heading said "Today" from Sunday, so it now says "Whenever you like". The week sheet it links returns 200. Deployed; smoke 38/38 and 39/39.

09:07: /foundry/ as a reader from today's post sees it

Finished 09:10. Task 8's link lands on /foundry/. At 390 px and at 1366x768, the first screen showed the title, the AI line and the contact sheet. The manifest URL, the one thing a Foundry user came for, was below the fold at both widths, and far down on a phone. I added a "Manifest URL" line with its own Copy button and a "how to install" jump, just under the AI line. Both Copy buttons share one handler. Tested live on a phone viewport: each puts the exact manifest URL on the clipboard, no page errors, no horizontal scroll. "the free demo" in the where-these-came-from section is now a link to the editor; it was plain text. Deployed; smoke 38/38 and 39/39.

10:07: the editor as a Foundry reader meets it

Finished 10:10. At 1366x768 on the live editor, the first screen says what it draws, that the demo exports a watermarked PNG, and what the $12 adds (Universal VTT with walls, doors and lights, PDF, fleets). Generate a derelict works. Clicking Export Universal VTT opens a clear dialog: what the file carries, the price, and "Save this ship first" so the work isn't lost. No page errors. Problem found on the way: /foundry-dd2vtt/ (linked as "Foundry import" from the editor) said "Seventeen Bulkhead deck plans are packaged as a Foundry module". The press/itch copy, which the boss will paste in task 1, said "Seventeen finished plans" twice. The module has held 36 since this morning, and "seventeen" as a word was invisible to the build script. Both now say "36 deck plans", which the script's count pattern matches, and foundry-module.mjs now updates both files each Sunday. I also updated the vision picture's alt text on /foundry-dd2vtt/. Deployed and live; smoke 38/38 and 39/39.

Daily check, 11:07

At 11:07 status had 4 failing, all today's derelict not yet out. No daily job was running, so I ran daily-derelict.sh by hand. It generated the 28th's derelict (RSV Sparrowhawk Drift), deployed it, and posted it to Bluesky at 11:08Z with the map and a link back to /daily/2026-09-28/. Re-run status at 11:11: all 23 clear, including the Owlbear manifest, the store listing and the 1.17.1 zip.

11:11: make sure the thread watcher still reads Reddit

Finished 11:13. reddit-watch.mjs still reads Reddit logged out: on our r/battlemaps post it returned the title, 5 points and all 5 comments. I found a bug I made at 08:08: the "today" jump link gave task 8's block id "t8", which an older textarea on /press/ already used, so that textarea's Copy button would have grabbed the wrong element. The anchor is now "task8". There are no duplicate ids on /press/ or /press/itch. Task 8 never asked for the post's link back, which I need to watch the thread, so it now ends with "once it is up, paste the post's link into the chat". Tested live on a phone viewport: the jump lands on task 8, the body and the old Short caption each copy their own text, and the new line shows. Smoke 39/39 and 40/40, with today's daily in the count.

12:07: do search crawlers know the Foundry pages

Finished 12:09. The zoo has no remarks. crawlers.sh, since the 21st: Googlebot 108 fetches over 30 paths (the 21st's baseline was 99 over 26), Bingbot 63 over 30 (was 61 over 30). Both have fetched /foundry/, and Googlebot has fetched /foundry-dd2vtt/. Googlebot has fetched 16 of 37 sitemap pages. Even since the 10th it has never fetched /free-sci-fi-battlemaps/, /derelict-ship-map-generator/, /roll20-dd2vtt/, /owlbear-rodeo-dd2vtt/, 10 of the 11 /maps/ pages, or any daily after the 21st. It isn't a linking fault: / and /maps/ (both crawled) link to all of them in plain static HTML, and no page is noindex. Google is crawling a new site slowly. Googlebot was also fetching our view beacon (/e/view/...), because its renderer runs the page script. The stats scripts already drop bot hits, but robots.txt now disallows /e/ so crawl isn't spent there. Deployed; live robots.txt has the line. Sent 10 pages Bing hasn't seen, or that changed today, to IndexNow (200 accepted). For Google, the only lever faster than waiting is Search Console's Request indexing, a boss ask. I'm holding it until after task 8 so the list stays short.

13:07: two more checked replies for task 8

Finished 13:10. Task 9 (Owlbear, Wednesday) still reads right: it says the store listing is in the queue, and its links are covered by status. The daily's tags were settled on the 25th (LEARNED: #battlemap keeps it in both map feeds), so nothing to change there. Added replies fvr9 (is it on Foundry's package list) and fvr10 (which system, metres) under task 8's "If someone comments". Checked against the extracted 1.2.1 pack: all 36 scenes are a 100 px square grid at 5 ft a square, sizes 23x9 to 40x37 squares. The pack has no system, and module.json has manifest and download URLs, so Foundry's update button works. The package-list reply says only that it isn't listed. Both are lowercase and start "the agent that built this, answering:". No duplicate ids. Deployed; smoke 39/39 and 40/40.

14:07: is task 8 up yet

Finished 14:08. Read r/FoundryVTT/new logged out at 14:08: task 8 isn't up yet, and the newest post is from 10:42Z. One other Commercial post went up today, at 06:46Z: a free PDF asset importer, 39 points and 4 comments by 14:08. So Monday commercial posts are getting upvoted today. A background loop to catch our post was refused by the permission classifier, which is fair: it used an improvised sleep. I didn't route around it. Instead a Monitor task polls /new every 7 minutes for a title with Bulkhead or "36 starship" and reports when it appears. It expires after 30 minutes, so I re-arm it until 16:30.

14:12: task 8 page at phone width

Finished 14:16. Rendered /press/ as an iPhone 13 (390 px), live site, beacon blocked. The page does not scroll sideways and no element in task 8 is wider than the screen. The top "task 8" link lands exactly on the task. All 12 Copy buttons in task 8 (title, body, replies fvr0 to fvr10) put their own textarea's text on the clipboard, with no mismatch. All three Foundry pictures load at 1600 px. Nothing to fix. The /new watcher is still running and found nothing up to now.

14:38: re-arm the task 8 watch

Finished 14:40. Re-armed until 15:08. The read works: /new still shows the 10:42Z post as the newest, the same as at 14:08. Four hours without a single new post on a sub this size is odd. Either Reddit is serving a cached list to logged-out readers, or new posts are waiting for mod approval. If the boss has posted and it sits in the mod queue, the watcher cannot see it, so the link from the boss is the surer signal.

14:45: is r/FoundryVTT/new stale for us

Finished 14:52. It is not stale. Reddit sends the listing as private, no-store. A read with a cache-busting query returns exactly the same posts as the plain /new read. The newest post is from 11:04Z. At 14:38 my title-only print showed the 10:42 post first, which was a DOM-order effect, not stale data. The sub has simply had no new post that a logged-out reader can see since 11:04. So either the boss has not posted yet, or the post is waiting in the mod queue, which a logged-out reader cannot see. The site agrees: since 12:00 there are 2 real page loads, both on / and both from the bananafest-destiny.com landing, with no reddit.com referrer. The watcher stays as it is.

15:40: what Bing and DuckDuckGo have indexed

Finished 15:50. Inconclusive, and it will stay that way from here. Bing loaded headless ignored the site: operator: it returned dictionary and Seattle pages, and for "bulkhead deck plan editor" only the game studio. DuckDuckGo's html endpoint returned 403. The only real evidence is our own logs: one bing.com visit this week, landing on /. Written into LEARNED.md so I do not retry it. No change to the Search Console ask held for after task 8. The watcher (to about 16:08) has seen nothing.

16:38: task 8 window passed

Finished 16:44. The press page top line now says task 8 is still fine today until midnight UTC (7 pm Central), otherwise next Monday, 5 October. The task heading says the same. Deployed; smoke 39/39 and 40/40; the live page carries the new line. Before 5 October the post text needs its numbers refreshed: the Sunday run on the 4th makes the module 1.3.0 with 43 scenes and the dates 16 September to 3 October, and the press textareas are not in the build script's count list. I did not restart the watcher. One read of /new at the evening check will cover a late post.

17:07: daily check, and is /new lying

Finished 17:15. Daily check: all 23 clear, and today's derelict is on Bluesky with its map and link (11:08). Then I found a blind spot in this afternoon's watch. At the same moment, r/AskReddit/new was 9 minutes fresh and r/rpg/new 81 minutes, but r/FoundryVTT/new still ended at 11:04. The sub's hot list shows two later posts, 15:36 and 16:25. So the logged-out /new for this sub is hours behind. The watcher's silence proved nothing, though the 14:45 test (a cache-busting query) could not have caught this. Our post is not on hot either, and the site has no reddit.com referrer, so it is still not up, or it is sitting in a queue. Noted in LEARNED.md: any watch reads /new and hot together.

17:50: which Bluesky hashtags carry traffic

Finished 18:02. The public search API gives, per 100 latest posts, how long they span and their likes. #ttrpg fills in about 3 hours and #scifi in about 5, so a post there sinks fast. #battlemap fills in 12 days (3.7 likes a post), #osr in 5 days (8), #travellerrpg in 37 days (12.9), #foundryvtt in 44 days (3.7). Our own 18 posts get 1 to 4 likes whatever the tags carry, so our data cannot rank the tags. One change on reasoning alone: #scifi out, #foundryvtt in. Every daily now also goes into the Foundry module and ships a .dd2vtt, and #scifi is a firehose outside tabletop. Dry run of today's text: it fits, and the hook is kept. Tomorrow's 11:07 post is the first with it. Compare its likes over the week, not one day.

18:50: task 9 page at phone width

Finished 19:20. I checked the whole /press/ page, not only task 9, as an iPhone 13 with every collapsed section opened. There is no sideways scroll and no duplicate ids. 48 of 49 text boxes have a Copy button that copies exactly their own text. The one without, wk2, is the weekly pack post, which the boss only reads and answers with "post", so no button is needed. All 11 images load, and every link to our own site returns 200. The task 9 text still matches the facts: the store PR is still open, so "add it by link" is right, and the manifest is 1.17.1. If task 8 moves to 5 October, task 9 on the 30th is still fine: no other post from the boss sits next to it. Nothing to change.

19:55: GM keys into the Foundry module

Finished 20:08. New script app/scripts/foundry-journals.mjs turns the -key.md files into JournalEntry sources: one entry per ship, a "The ship" page (story, hook, links to every deck scene), then one page per deck. Each deck page opens with an @UUID link to its scene in the deck-plans pack. Rooms become h3s, and Hazard, Salvage, Trail and Log labels are bold. Against the 1.2.1 scenes: 23 entries and 59 pages. Every one of the 36 scenes has its key, and every deck heading matched a scene by name. Only today's Sparrowhawk key waits, because it is not in the module until Sunday. I fixed one bug before the first run: the slice for the last deck would have come out empty. Not wired into foundry-module.mjs yet, and nothing is deployed.

20:10: wire the GM keys into the module build

Finished 20:14. foundry-module.mjs now rebuilds packs/gm-keys from scratch on every run. It fails if any scene lacks a key, and it adds the pack to both module.json files as "Bulkhead GM Keys" (JournalEntry). The pack is PLAYER NONE and ASSISTANT OWNER, so players cannot open the GM keys. A Sunday with nothing new still builds the keys once if the pack is missing. foundry-validate.mjs now also checks the keys with new JournalEntry(d, {strict: true}). It takes any free player seat, because the fixed "Player 03" seat was taken and timed out. Tested on a copy of app/ in the scratchpad, with nothing written to public/: 1.3.0 would have 37 scenes (today's Sparrowhawk joins) and 24 GM keys. The zip carries the pack. On the v14 demo (14.365), as a player and in memory: all 37 scenes and 24 keys pass strict validation. I rendered the Sable Dawn key in its journal sheet, with a test-only owner override. Its contents list shows every room, the labels are bold, and the scene link sits at the top (it shows broken there only because the module is not installed on the demo). Not released: a 37-scene module tonight would make the "36" in the task 8 text wrong while the post may still go up.

21:08: stage the 1.3.0 words

Finished 21:07. The GM keys are now described on the /foundry/ page (a sentence after the "nothing to trace" line), in both READMEs, and in the module description the script writes. A full dry run of foundry-module.mjs 1.3.0 on a scratchpad copy gives 37 scenes and 24 keys. The page reads "37 starship... from 16 to 28 September", and the new description is right. Committed, not deployed: the live site still says 36 and has no keys, and it stays that way until the release after midnight UTC. If the release slips, these committed words must not deploy on their own. The 11:07 daily deploy would carry them, so the release has to happen before then.

22:07: a picture of a GM key in Foundry

Finished 22:08. Shot the Sable Dawn key on the v14 demo in memory (a test-only owner view, so the page renders for a player seat). The dice overlay and notifications are hidden, and it is cropped to the journal sheet at 1100x900. It shows the contents list with every room, the upper deck page, and bold Hazard, Salvage and Log lines. Saved as app/public/foundry/in-foundry-v14-gm-key.png (94 KB, palette PNG) and placed on /foundry/ after the GM keys sentence. The alt text is written, and a caption says the scene link shows broken only because the module is not installed on the demo. Committed, not deployed: it goes out with 1.3.0 after midnight.

23:08: daily check, and the task 8 text for 5 October

Finished 23:07. Daily check: all 23 clear. The 5 October title and body are drafted in the session scratchpad (not in the repo, since scratch/ is for the next app). The GM keys are in, and the only moving number is the scene count, {N}. The "19 from the daily derelicts of 16 to 27 september" wording is replaced by "the rest from a daily derelict that has come out every day since 16 september", so it never goes stale. The key picture joins as the third image. Of the replies, only fvr0 and fvr1 carry a count ("all 36"). The Sunday run on the 4th goes next, then validates. The count cannot be known now, because some dailies have two decks, so the text is applied on the 4th after that run.