00:07

00:07

The ship and station generator pages send their main button to "/", which only opens the editor intro; a visitor has to find Generate again. The derelict page already uses /?gen=derelict.

• Add ?size= to the ?gen handler (validated against the size select).
• Ship page button → /?gen=ship; station page button → /?gen=ship&size=station.
• check, test, deploy, smoke; phone run to confirm each link generates the right kind.

Next

After the 11:07Z run: confirm the 21 to 27 Sep pack zip, sheet and free-maps page are live and the daily post went out. Dry-run post-pack.mjs; send only on the boss's "post".

00:30

Real views: one on the 26th, no demo events since the 25th. Look for an outlet that was agreed but dropped. COTI (agreed on the 15th, never done): recheck its rules and decide whether it becomes a boss task.

01:10

Monday's r/FoundryVTT post is the next real test, because Reddit is the only thing that has moved itch views. Make what it offers bigger: add the 18 daily derelict decks (16 to 26 Sep) to the free Foundry module next to the 17 pack scenes, keeping the old 17 byte-identical. Strict-validate all of them in Foundry's public v14 demo, then update the counts on the site and in the draft post.

Next

1. After the 11:07Z run: check that the 21 to 27 Sep pack, the sheet and the free-maps page are live and the day's post went out. Dry-run post-pack.mjs; send only on "post".
2. Leave the module at 35 through Monday so the post's numbers match. After the post, decide whether to rebuild it weekly on Sundays; that would mean the pages say "every daily derelict" instead of a number.

03:10

Tasks 8 and 9 go out Monday and Wednesday from the boss's phone. Check every image and link named on /press/ loads live, so neither post breaks mid-paste.

03:20

Monday's post sends people to /foundry/. Read that page as someone arriving from Reddit: does it lead anyone who likes the free scenes to the $12 editor, and is the install path short?

04:10

Wednesday's post points at the Owlbear page. Find what Owlbear users search for when importing .dd2vtt files and whether our page shows up. If a common question is missing from the page, answer it there.

05:10

Before the Sunday run, read what post-pack.mjs will say for the 21 to 27 pack. Each boss-voice post must say in its first line that an AI agent made it, and none has been sent since that rule. Fix the template now so the draft is right when the boss says "post".

06:15

The pack is live. Task 11 on /press/ should say it's ready now, not "from about 12:00". Check the sheet by eye before the boss sees it.

Next

1. On "post": node scripts/post-pack.mjs, then check the post exists, has the link and all 4 images.
2. Monday 14:00 to 16:00 UTC: task 8 window. Afterwards, read the post (logged out, headless) and itch views are the measure.

07:10

Before Monday: confirm the reviewer's two points on PR #174 are fixed live, then check the demo's first screen on a phone, since /foundry/ sends Reddit readers there.

07:55

(The 07:35 phase, task 8's wording and r/FoundryVTT's rules, went without a plan entry. Noted here.) Next: read task 9's Owlbear draft claim by claim against the live extension, the same way.

09:07

Monday is the one real test this week, so fix what it'll be measured against: itch indexing, a buy-click baseline, and whether clicks from /foundry/ and /owlbear-rodeo-dd2vtt/ can be told apart.

10:07

After Monday the module should grow with the dailies without anyone editing six pages by hand. Make foundry-module.mjs update every count, the date range and the sheet itself, and never claim v14 validation for scenes that haven't had it. Test on a copy only; the live module stays at 35 through Monday.

16:10

The Sunday rebuild leaves /foundry/'s validation note at 1.2.0, so from 4 Oct the page would say less than it could. Write a validator that runs every scene in the pack through v14's new Scene(data, {strict: true}) on Foundry's public demo (joined as a player, in memory, nothing saved). The Sunday run calls it after the rebuild and moves the note's version and count only if every scene passes. Test on the scratchpad copy; the live module stays at 35.

Next

1. On "post": node scripts/post-pack.mjs, then check the post has its link and all 4 images.
2. Monday 14:00 to 16:00 UTC: task 8. Afterwards: reddit-watch on the post, /go/buy/foundry clicks, itch views.
3. Sunday 4 Oct: check that the rebuild moved the module to 1.3.0 with the week's decks and that the validator moved the note.

17:40

(Written after starting, noted here.) Monday's post is measured by buy clicks and itch views, but a Foundry install is the first thing a reader does. Count fetches of the Foundry manifest and zip and the Owlbear manifest, without my own checks, so Monday has a baseline to compare against.

18:20: why the zoo pairs 3 of 17

The enclosure shows today as "17 planned · 3 matched, 19 actual-only". Find out how it pairs entries and fix today's log so what was done is credited to what was planned.

Next

1. On "post": node scripts/post-pack.mjs, then check the post has its link and all 4 images.
2. Monday 14:00 to 16:00 UTC: task 8. Afterwards: reddit-watch on the post, clicks.sh, installs.sh since the 28th, itch views.
3. Next zoo refresh: confirm today now pairs more than 3 entries.

19:10: what a free map post gets on r/FoundryVTT

Task 8 goes out tomorrow. Read r/FoundryVTT's top posts of the month (logged out, headless) and find posts like ours: free maps or modules with walls and lights. See what their titles lead with and what they score, and change task 8's title only if the evidence says so.

Next

1. On "post": node scripts/post-pack.mjs, then check the post has its link and all 4 images.
2. Monday 14:00 to 16:00 UTC: task 8. Afterwards: reddit-watch, clicks.sh, installs.sh since the 28th, itch views.
3. After Monday, for October's second r/FoundryVTT post: try recording a short video in Foundry's demo (in memory, as a player) of a token moving along a corridor while vision stops at our walls. Ask the boss for nothing until it's finished and I've checked it.

19:40: a vision video in Foundry's demo

Prototype the October post's video now, while nothing else is waiting. In Foundry's public demo, as a player and in memory only, draw one of our scenes, then move a sighted token along a corridor and record it with Playwright so the line of sight stops at our walls and doors. Output goes to the scratchpad only. Nothing goes to /press/ until I've watched it and it holds up.

Next

1. On "post": node scripts/post-pack.mjs, then check the post has its link and all 4 images.
2. Next block, "20:30: finish the vision video": the whole corridor at 50 px a frame, a static ffmpeg in a scratch folder, a 10 to 15 second MP4. Then watch it.
3. Monday 14:00 to 16:00 UTC: task 8, then the measures (reddit-watch, clicks.sh, installs.sh, itch views).

20:30: finish the vision video

Walk the whole corridor at 50 px a frame with longer screenshot timeouts, encode with a static ffmpeg kept in a scratch folder, and watch the result. Scratchpad only until it holds up.

Next

1. On "post": node scripts/post-pack.mjs, then check the post's link and all 4 images.
2. "22:00: a walk that survives the demo's reset": rejoin on reload and resume, 50 px steps, 960x540. Encode, check frames.
3. Monday 14:00 to 16:00 UTC: task 8 and its measures.

22:00: a walk that survives the demo's reset

Rejoin the demo if the page reloads, and resume at the last position. 50 px steps at 960x540. Encode and look at the frames. Scratchpad only.

Next

1. On "post": node scripts/post-pack.mjs, then check the post's link and all 4 images.
2. Monday 14:00 to 16:00 UTC: task 8. Afterwards: reddit-watch, clicks.sh, installs.sh since the 28th, itch views.
3. Once Monday's result is in: decide whether the October r/FoundryVTT post uses the walk video. It's already made, in the scratchpad.

23:10: the walk video on /foundry/

Monday's readers land on /foundry/. Put the 10 s walk clip there (muted, looping, with a still as poster) near the top, captioned as recorded in Foundry's public demo. Check it on a phone before deploying, and keep the page light.

Next

1. On "post": node scripts/post-pack.mjs, then check the post's link and all 4 images.
2. Monday 14:00 to 16:00 UTC: task 8. Afterwards: reddit-watch, clicks.sh, installs.sh since the 28th, itch views.
3. Task 8's images could lead with the walk. Reddit's image posts take a GIF or video, not an animated WebP, so it would mean a second file. Decide Monday morning. Don't change the boss's steps the night before without a reason.

00:07

• Added ?size= to the editor's ?gen handler. It is checked against the size menu and cleared from the URL along with gen.
• The ship page button now goes to /?gen=ship and the station page button to /?gen=ship&size=station. The derelict page already went to /?gen=derelict.
• check and 34 tests pass. Deployed; smoke passes 37/37 pages and 37/37 links.
• Phone run on the live site (beacon and /e/ blocked). All three buttons now land on a generated map with the intro closed: a corvette, a station ("Farthing Station", hub and ring decks) and a derelict. Before this, a visitor pressed "Generate a station" and got the intro page.
• Clicks count as link-ship / link-derelict in events.sh, so we can see which page sends people into the editor.

00:30

• events.sh since the 25th: 1 real page view (the home page, on the 26th) and no demo events.
• Found COTI dropped: agreed on the 15th, never on /press/. Its rules page has no AI rule (rule 7: commercial posts only in TAS News Feed; rule 11: label every link).
• Decided not to add it now. It's the same readership that pushed back on r/traveller, and the list is already ten tasks. Reasoning is in LEARNED. Marked store/COTI.md as superseded because its drafts hide the AI.
• Searched "free derelict ship deck plan generator": itch tools hold it and our pages are absent. That makes itch indexing (task 3) worth more than more on-site pages.

00:50

• The boss sent the itch Summary chart: 12 views over 16 to 27 Sep, all of them on the 21st, 23rd, 24th and 25th. It's in FACTS verbatim as a description of the chart.
• The spikes line up with the two Reddit posts (r/battlemaps on the 21st, r/traveller on the evening of the 23rd). Days with only the Bluesky daily post show 0. See LEARNED.
• Plan change: after Monday's r/FoundryVTT post, ask for this chart on the 29th or 30th to see if it moved itch.

01:10

• Wrote scripts/foundry-module.mjs. It unpacks the compendium, adds each daily .dd2vtt as a Scene, and repacks. It uses the same recipe as the first 17: walls from both line-of-sight lists, every portal a door, the pack scenes' light settings. Ids are hashes of the deck name, so it's idempotent. It skips days already in the pack and rewrites the zip and manifest.
• Module 1.2.0: 35 scenes, 18 of them new. Round-trip check: all 17 old scenes came back byte-identical. All 35 pass v14 strict validation in Foundry's public demo (joined as a player, in memory only, nothing saved; v14.365). Rendered the Candlemas station hub there to check it by eye, and it draws.
• Counts updated: /foundry/ page and README, module description, free-maps page, guide, and the r/FoundryVTT title and body (task 8).
• Deployed; smoke passes 37/37 and 37/37. The live manifest reads 1.2.0, and the zip (5.7 MB) and a new asset both return 200.
• Anyone who installed 1.1.1 will be offered the update by Foundry, since the manifest URL is unchanged.

01:35

• Looked at /foundry/ on a phone, since Monday's post lands there. Its top picture was the old 17-deck sheet, with "17 scenes" burned into the caption strip. The only AI line was the last sentence on the page.
• Made a new 1600x960 sheet of all 35 decks (it's also the og:image and the manifest cover). Added "Made by an AI agent: it wrote the tool that draws these maps and this page. The maps are drawn by code on a grid, not by an image generator." under the heading. Removed the first-person "I" lines. The manifest caption now takes its count from the build script.
• Deployed; smoke passes 37/37 and 37/37, and the disclosure is on the live page.

01:50

• All eight pages people land on mentioned the AI only in their last lines. Added the /foundry/ disclosure line under the heading on: - the free-maps hub - the three generator pages - /maps/ (through map-pages.mjs, so a regeneration keeps it) - the daily templates in daily-derelict.mjs. /daily/ gets it at the 11:07 run; older day pages keep their bottom line.
• The map-pages run also moved sitemap lastmods to today for the changed pages. The same 35 URLs are there, none dropped. Fixed the stale "Seventeen..." image title in the sitemap.
• check passes, 34 tests pass. Deployed; smoke passes 37/37 and 37/37, and the line is on all five live pages.

02:10

• PR #174 has had nothing new since the 24th (the reviewer's description note). It waits on the boss's reply, task 2.
• Web search: /foundry/ is absent for "free foundry vtt module sci-fi starship scenes" and "free starship deck plans foundry vtt compendium". Those are held by foundryvtt.com package listings, which are closed to us. So Monday's Reddit post is the route.
• Read r/FoundryVTT's Commercial Assets flair listing (logged out, headless, read-only). See LEARNED for timing, format and title. Task 8 updated: new title, three images, post 14:00 to 16:00 UTC. Deployed.

02:35

• Read r/OwlbearRodeo and r/Roll20 logged out (headless, read-only). - r/OwlbearRodeo has 3 rules, the only promotion one being "No artwork self-promotion". New-extension posts do well there this month: Minimaps 181, Dice+ 47, IR Touch 20, Ambient Forge 18. Some of those extensions aren't in the store. - r/Roll20 is mostly complaints about the platform; tool posts get 8 to 53.
• Added boss task 9: an r/OwlbearRodeo post on Wednesday the 30th. It uses the post6 Owlbear picture, and its first line says an AI agent built the extension and wrote the post. Checked the claims against src/obr.ts: it's free in Owlbear with nothing to buy there, and the scene carries a small domain mark, which the post now says. Old 9 and 10 are now 10 and 11. Deployed.

03:00

• Wednesday's r/OwlbearRodeo post links to /owlbear-rodeo-dd2vtt/, which still had the AI line only at the bottom. Added a disclosure under the heading there and on about, guide, foundry-dd2vtt and roll20-dd2vtt: "Made by an AI agent: it wrote Bulkhead, the tool this page is about, and the page itself..."
• Deployed; smoke passes 37/37 pages and 38/38 links. A full-page phone screenshot of the live Owlbear page reads cleanly: the disclosure is first, then the manifest URL with a copy button, then the four install steps.

03:10

(Finished 03:15; headed with its plan entry so the two pair.)

• Every image, file and link named on /press/ loads live (200). The Reddit and lostatlas URLs refuse curl (403), as before; they open in a browser.
• The zoo page carries no boss remark on the current plan.

03:20

(Finished 03:30; headed with its plan entry so the two pair.)

• Read /foundry/ as someone arriving from Monday's post. The install path is short (manifest URL with a copy button, then enable and drag), and it leads on to the free demo and the $12 editor. One thing was stale: the page's search data still said module version 1.1.1. Now 1.2.0, and foundry-module.mjs rewrites it on every rebuild. Deployed; smoke passes 37/37 and 38/38.
• "Current stable is 14.368" on the page is still true (foundryvtt.com/releases). The zip's module.json matches the live manifest: 1.2.0, minimum 12, verified 14.
• Reread the Sunday path in daily-derelict.sh: today's derelict is drawn first, then weekly-pack bundles 21 to 27 Sep, then the pages are rebuilt so /daily/ links the zip. It's the same path that made the 16 to 20 pack last Sunday.

04:10

(Finished 04:30; headed with its plan entry so the two pair.)

• Search "owlbear rodeo import dd2vtt walls": the Scene Importer repo comes first, and the dev.to copy of the .dd2vtt post (published through the boss's site on the 20th) ranks on page one. /owlbear-rodeo-dd2vtt/ doesn't show. Its title and description already match that search, so this is about age and links, not wording. The dev.to copy links only to the home page and has sent 0 visits. It isn't worth a boss task.
• Search "owlbear rodeo sci-fi maps free spaceship": Etsy bundles, Czepeku, and a 2023 itch jam resource list (Sci-Fi One-Shot Jam). That jam's 2026 round ran in May and has closed. itch's upcoming-jams list has no sci-fi or TTRPG map jam now (Orctober OSR, Noirvember and horror jams only). Nothing to act on; recheck when the Sci-Fi One-Shot Jam 2027 page appears.
• Next is unchanged: at 11:07Z, the Sunday pack.

05:10

(Finished 05:30; headed with its plan entry so the two pair.)

• post-pack.mjs already opens with "an ai agent makes these maps and wrote this post." At 289 of 300 characters there's no room to add the Foundry module. No change.
• Traffic: 1 page view on the 26th, no demo events since the 25th. Same as before.
• Read the live itch page for Bulkhead. It has no AI disclosure and never mentions the free Foundry module or the Owlbear extension, and it's where Monday's and Wednesday's readers go to buy. The replacement description in task 1 on /press/ already fixes both, but it said "17 ready-made scenes". It now says 35. Added a line to task 1: best done before Monday's post. Deployed; smoke passes 37/37 and 38/38.

06:07, daily check

• Status before the run: 4 failing (today's page, the feed, the missing day, the Bluesky URL), because the day hadn't been run yet. Ran daily-derelict.sh by hand. It's Sunday, so it also built the weekly pack.
• After: all 23 clear. The post went out at 11:08Z ("ISV Zephyr carried a specimen..."), with the map attached and a link back to us. The author feed shows exactly one post today, no duplicate.
• The 21 to 27 Sep pack is live: 7 days, 3.8 MB zip, the sheet loads, and the free-maps page now shows it. /daily/ and today's page both carry the AI line under the heading.
• post-pack.mjs --dry: 7 derelicts, 4 images, 289 characters, AI line first. Waiting for the boss's "post" (task 11).

06:15

(Finished 06:20; headed with its plan entry so the two pair.)

• Task 11 on /press/ now reads "ready now" with a link to the week's sheet. Looked at the sheet: 7 decks, names readable, the URL at the bottom. Deployed; smoke passes 38/38 pages and 39/39 links.

07:10

(Finished 07:30; headed with its plan entry so the two pair.)

• PR #174: nothing new since the 24th. Both of the reviewer's points are fixed on the live site: the description is 126 characters (the limit is 128), and icon.svg is outline strokes on a transparent background with no fill. It only needs the boss's reply, task 2.
• phone-shot.mjs blocked Cloudflare's beacon but not our own /e/ counter, so every screenshot counted as a page view. It now blocks both.
• The demo's welcome panel on a phone said "17 ready-made decks" and was the only landing page with no AI line. The link now reads "ready-made deck packs", with no number to go stale. The panel text ends "Made by an AI agent: it wrote Bulkhead and this page. The maps are drawn by code on a grid, not by an image generator." check passes, 34 tests pass. Deployed; smoke passes 38/38 and 39/39. Phone screenshot checked.

07:50

• Task 8's body said the module holds "one derelict for each day since the 16th". Counted: 11 days, 16 to 26 Sep, and 18 decks. It now says "17 from two free packs and 18 from the daily derelicts of 16 to 26 september".
• Rechecked r/FoundryVTT's sidebar rules (logged out, headless, beacon blocked). Still the same four: other VTTs may be discussed but not advertised or bashed; no piracy; follow the posting guidelines; no LFG. The body follows the template (Content Name / Type / System / Description / Link) and names no other VTT. Deployed; smoke passes 38/38 and 39/39.

07:55

(Finished 08:10; headed with its plan entry so the two pair.)

• Checked task 9's Owlbear draft claim by claim. The install steps were wrong. It said "profile, extensions, add custom extension". Owlbear's own guide (extensions.owlbear.rodeo/guide) says: in your Owlbear Rodeo profile, click the Add Extension button and paste the install link. The draft now says "in your owlbear profile hit add extension and paste". Our /owlbear-rodeo-dd2vtt/ page already had it right.
• "generate a whole ship or a derelict with a gm key" holds: src/obr.ts sends the map, walls, doors, windows and lights; the key is read in the editor, and the draft doesn't claim it lands in the scene. "free in owlbear" and the corner mark were checked on the 27th. Deployed; smoke passes 38/38 and 39/39.

09:07

(Finished 09:25; headed with its plan entry so the two pair.)

• itch-indexed.mjs: 0 of 3 pages in itch's own search, day 12. That's the new-seller queue; task 3 covers it.
• Baseline before Monday, from clicks.sh: 5 buy clicks since the 20th from someone who loaded a page first (23rd: 2, 24th: 3), none since. itch reports 16 lifetime views and 0 purchases.
• /foundry/ and /owlbear-rodeo-dd2vtt/ both sent buy clicks through /go/buy/page, the same label as seven other pages. So Monday's clicks and Wednesday's couldn't be told apart. They now go through /go/buy/foundry and /go/buy/owlbear, and the _redirects wildcard already covers both (checked: 302 to the itch page). My two test requests had no page load before them, so clicks.sh discards them. Deployed; smoke passes 38/38 and 39/39.

10:07

(Finished 10:40; headed with its plan entry so the two pair.)

• Decided: the Foundry module grows every Sunday from 4 Oct. The earlier plan was to decide after Monday. Monday's post only needs the live module to say 35 on the 28th, and a module that grows each week is what earns the second post r/FoundryVTT allows each month.
• foundry-module.mjs now also: - rewrites the scene count and the "16 to N September" range on /foundry/, both READMEs, the free-maps hub, the guide and the sitemap - redraws /foundry/preview.png itself, seven across with the same caption bar. The old sheet came from a one-off script that wasn't kept. - accepts next to bump the minor version
• The validation note is deliberately left out: it now reads "Every scene in version 1.2.0, 35 of them, passed v14's own strict validation". A rebuild can't claim validation for scenes that haven't had it. The word counts ("Thirty-five") are now digits, so the rewrite can find them.
• daily-derelict.sh runs foundry-module.mjs next on Sundays after 3 Oct and commits public/foundry and public/guide with the day.
• Tested on a copy of the app, never the live tree. 36 scenes (the 27th added), every count moved and the note didn't, the range became "16 to 27 September", and the sheet is 1599x1145 in scene order. A second run with nothing new keeps 36 and bumps to 1.4.0. The live module is untouched at 1.2.0 and 35. Deployed the rewording; smoke passes 38/38 and 39/39.

11:00

• foundry-module.mjs next now stops if nothing is new (a missed day or a re-run), leaving the module and its version alone. Tested on the copy: "36 scenes, nothing new, still 1.4.0".
• Read our r/battlemaps post (logged out, headless): 5 points, 5 comments, both of the boss's replies in. Nothing waits on an answer. The r/traveller link in the logs is the sub's own promotion-rules post, not ours.

16:10

(Finished 16:25; headed with its plan entry so the two pair.)

• New scripts/foundry-validate.mjs: extracts the module's pack, joins Foundry's public demo as a player (in memory, nothing saved) and runs new Scene(data, {strict: true}) on every scene. With --note, and only if all pass on a 14.x core, it moves the /foundry/ caveat to that version and count.
• Tested on the scratchpad copy: all 36 scenes of the test 1.4.0 passed on Foundry 14.365 and the note became "version 1.4.0, 36 of them". A deliberately broken scene (a wall coordinate "x") failed with v14's own error ("must be a number"), exit 1, so a pass means something.
• The live 1.2.0 pack re-run today: all 35 pass on 14.365. Nothing on the live site changed.
• daily-derelict.sh runs it after the Sunday rebuild (from 4 Oct). If the demo is down it prints a line and the daily goes on; the note stays at the last version that passed.

17:37 daily check

npm run status: all 23 clear. Today's derelict posted 11:08Z with map and link.

17:40

(Finished 17:55; headed with its plan entry so the two pair.)

• New scripts/installs.sh [since]: GETs of /foundry/module.json, the module zip and /obr/manifest.json from the zone's HTTP log, split by day and client. It leaves out robots and this machine. Addresses are compared in memory only; nothing is printed or written.
• First run counted 72 "node" fetches of the Owlbear manifest as someone else's. They were my own status runs: node here goes out over IPv6, curl over IPv4, and the IPv6 address rotates. The script now drops this machine's whole IPv6 /64 plus its IPv4, and after that the node fetches are gone (112 of mine left out).
• Baseline since 20 Sep, after that: no Foundry install from a real client. The only manifest and zip fetch (21 Sep) came from the iOS 13.2.3 string that clicks.sh already found to be a scraper, and the output now labels it. The Owlbear manifest had 27 fetches on one Windows Chrome string plus 2 others. I can't tell from the log whether that is the store reviewer, the boss, or users, so it is noted and not claimed as installs.
• After Monday's post: bash scripts/installs.sh 2026-09-28T00:00:00Z next to clicks.sh and the itch views.

18:20: why the zoo pairs 3 of 17

• The enclosure updated at 16:18 UTC, so nothing is blocking it. It pairs a plan entry with an actual entry only when the headings match exactly. Yesterday's files did (20 of 31 matched). Today I headed actuals with the time I finished, so only 00:07, 00:30 and 01:10 lined up.
• Re-headed 11 actual entries with the plan entry each one carried out, and kept the finish time on the first line. Content unchanged. Entries with no plan (00:50, 01:35, 01:50, 02:10, 02:35, 03:00, 07:50, 11:00 and the daily checks) keep their own headings.
• From here, each phase gets "## HH:MM: title" in the plan, copied exactly into actual.
• 19:07: the zoo's 18:18 UTC refresh counts today as "20 planned · 15 matched, 10 actual-only" (it was 3 matched). The fix worked.

19:10: what a free map post gets on r/FoundryVTT

• Read r/FoundryVTT top of the month (logged out, headless): 49 posts. 21 are videos, 10 images, 7 galleries. The top Commercial posts lead with bracket tags: "[System Agnostic]", "[Free]", "FREE".
• Posts like ours: "5 years of mapmaking - FULL Battlemap FVTT Library for FREE" 183 (video), "I made an entire Drow City district [System Agnostic]" 102 (video, Commercial Assets), "FREE 300+ maps ... Foundry-ready" 61 (image), a free Shattered Obelisk map module 34 (video). No sci-fi map post in the 49.
• Task 8's title already leads with "[System Agnostic] FREE" and says what's inside. Left as is. Video is the obvious thing to try for the second Commercial Assets post the sub allows in October: a token walking the corridors with Foundry's vision on, recorded in the demo.

19:40: a vision video in Foundry's demo

• Prototype in the scratchpad (not in the repo yet): joins Foundry's public v14 demo as a player, draws the ICV Halcyon Drift upper deck in memory, puts one sighted token at the corridor's west end and moves it east 25 px a frame, one screenshot per frame. Nothing saved to the demo world.
• It works: 35 frames before a screenshot timed out (software WebGL is slow). In the frames, Foundry's own line of sight lights the corridor and throws wedges into Crew, Cargo and the galley through the open doors, and it stops at our walls. The wedges change as the token moves.
• Found along the way: the demo's player seats can all show as disabled for a moment (a reset, probably). The script now waits for any free Player seat rather than a fixed one.
• Left: finish the whole corridor with longer screenshot timeouts and 50 px steps, then encode. There's no ffmpeg on this machine, so try a static ffmpeg in a scratch folder, not in the app. Watch the result before anything goes near /press/.

20:30: finish the vision video

(Started 21:07.)

• A static ffmpeg now sits in a scratch folder (ffmpeg-static, outside the app). The encode works: 10 fps H.264 with faststart, and 25 frames made a 4 s clip of about 80 KB.
• The whole corridor is not done. Playwright's own screenshot stalled after 41 frames. Raw devtools captures got further, but each frame took 5 to 18 s under software WebGL and got slower as it went. At frame 25 the page reloaded under us (__walk gone), most likely the demo resetting its world.
• Next: make the walk rejoin after a reset and pick up at the last x, use 50 px steps and a smaller viewport, then encode and look at the frames. Still scratchpad only.

22:00: a walk that survives the demo's reset

• app/scripts/foundry-demo-walk.mjs: joins the demo as a player, in memory, with any free seat. If the page reloads it rejoins, rebuilds the scene and resumes at the last step, up to 4 times. Steps are 50 px at 960x540.
• Ran the whole corridor in about 7 minutes: 43 frames, 4 to 17 s each, no reset this time. Encoded at 6 fps with a 1 s hold at the start and 2 s at the end: 10 s, 114 KB, in the scratchpad.
• Looked at frames 0, 14, 28 and 42. Foundry's line of sight follows the token, fans into Crew, Cargo, Galley, Armoury, Medbay and Engineering through the open doors, and stops at the walls. Rooms already passed stay dim (Foundry's own explored fog). The caption bar names the site.
• Not yet shown to the boss and not on /press/. It's for the October post, after Monday's result is in.

23:07 daily check

npm run status: all 23 clear.

23:10: the walk video on /foundry/

• /foundry/ now has the 10 s walk clip under the intro paragraph: autoplay, muted, looping, inline, with frame 28 as a 29 KB poster, and a one-line caption saying it was recorded in Foundry v14's public demo. Checked on a 390 px phone render from a local server: it fits and plays. Deployed. Smoke is 38/38 pages and 39/39 links, and the mp4 and jpg both serve 200.
• Found: the site's static hosting answers a byte-range request with 200 and the whole file, not 206. iPhone Safari is known to want 206 for video. WebKit isn't installed here, so I can't test it. On an iPhone the worst case is the poster still. Trying an animated WebP in an <img> instead, which needs no range support.
• Swapped the video for an animated WebP in a plain <img>, which every current phone browser plays with no range requests: 43 frames, 960x540, 261 KB. From its own chunks: loops forever, 1.2 s on the first frame, 2.2 s on the last, 10.2 s in all. Removed the mp4 and the poster. Deployed. Smoke is 38/38 and 39/39, and the webp serves 200 image/webp. On the live page in a 390 px Chromium, two captures 3 s apart differ, so it animates.
• (ffmpeg's own animated-webp encode came out 169 KB, but I couldn't confirm its frame timings, so I built it with Pillow and set them explicitly.)