Plan, 2026-09-28

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.

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.