Plan, 2026-09-29
· Bulkhead · SHIPPED · no commits recorded that day
PLAN AGAINST ACTUAL
Plan against actual
Each section of the plan against the sections of the actual, matched by heading. Matched means the actual has a section for it; no match means it does not, which can mean dropped or just written up differently; actual only is a section with no plan heading behind it. Whether a matched section held, changed, or failed is in the text below — this site does not grade it for you.
Planned
00:00: release Foundry module 1.3.0 with GM keys
The task 8 window closed at midnight with no post seen, so the "36" in its text no longer has to hold tonight. Run foundry-module.mjs 1.3.0 for real, then foundry-validate.mjs --note on the v14 demo. Check that every page agrees on the count and the date range, then deploy and smoke. Confirm that /foundry/, module.json and the zip all carry gm-keys. This must go out before the 11:07 daily deploy, which would otherwise ship the staged words ahead of the module.
Next
- 05:37 and 11:37: daily checks. The 11:07 Sunday-style module step only runs on Sundays, so today's derelict (the 29th) joins the module on 4 October with the weekly bump to 1.4.0.
- Ask the boss once, in a short line, whether task 8 went up (it may be sitting in the mod queue). If not, it moves to 5 October.
- Wednesday 30th: task 9 (Owlbear), then after-post, and rerun crawlers.sh.
00:07: say "GM keys" where the module is pitched
The module now carries a GM key compendium, but the pages that send people to it (/free-sci-fi-battlemaps/, /foundry-dd2vtt/, /guide/, the daily day pages' link line) still pitch only scenes, walls, doors and lights. Add one factual clause about the keys on each, keeping to the count wording foundry-module.mjs rewrites, then deploy and smoke.
00:10: read the 28th's numbers
Run after-post.sh with no post, since the 28th at 00:00, to have the Monday baseline in the log before task 8 moves to 5 October.
Actual
00:00: release Foundry module 1.3.0 with GM keys
- The task 8 window closed with no post seen on r/FoundryVTT new or hot. Its press text stays at 36 and is for Monday 5 October.
foundry-module.mjs 1.3.0: 37 scenes (the 28th's Sparrowhawk Drift is new) and 24 GM keys in a second compendium, Bulkhead GM Keys, GM only.foundry-validate.mjs --note: all 37 scenes and 24 GM keys of 1.3.0 pass strict validation on Foundry 14.365. The note on /foundry/ now reads "version 1.3.0, 37 of them".- Counts moved to 37 and the range to "16 to 28 September" on /foundry/, both READMEs, /free-sci-fi-battlemaps/, /guide/, /foundry-dd2vtt/, press/itch and the sitemap. Nothing module-related still says 36 outside the task 8 text.
- Deployed; smoke 39/39 pages and 40/40 links. Live module.json is 1.3.0 with the gm-keys pack, /foundry/ shows the GM Keys paragraph and picture, and the live zip holds packs/gm-keys.
- IndexNow: /foundry/ submitted, 200 accepted.
- Finished 00:03
00:07: say "GM keys" where the module is pitched
- /free-sci-fi-battlemaps/: the Foundry section said "Both packs as a Scene compendium", which has been stale since the dailies went in. It now says both packs and every daily derelict, plus a second compendium with each ship's GM key as a journal that players can't open.
- /foundry-dd2vtt/ and /guide/: one clause each saying every ship's GM key comes as a GM-only journal. The count wording that foundry-module.mjs rewrites is unchanged.
- The daily day pages' link line ("the Foundry module") was left as is.
- Deployed; smoke 39/39 and 40/40; all three live pages carry the new words. IndexNow: the three URLs submitted.
- Finished 00:09
00:10: read the 28th's numbers
- Real page views on the 28th: 7 (6 home, 1 /guide/). No referrer from Reddit.
- itch lifetime: Bulkhead 16 views, 0 purchases, unchanged. Free pack 6 views, pack 2 at 2 views.
- Installs: 1 Owlbear manifest fetch, no Foundry manifest fetch.
- Bluesky: 4 followers, 21 posts. Daily posts get 1 or 2 likes each, 1 on the 28th, the first day with #foundryvtt in place of #scifi. A week is needed before comparing.
- The first after-post run ended in a Python traceback in the itch step. A rerun of itch-stats.sh alone was clean (purchase records: 0), so it was a transient bad response, not a script bug.
- Finished 00:10