Repository navigation
0.36
Croftweaver 0.36 — a smoother first launch, and checks that tell you what to fix 🚀
As always: your favorite AI assistant takes you by the hand. Just ask it, in your own words, and it does the work.
What's new:
- 🚀 Your first launch on Cloudflare goes the right way round. Your assistant walks you through Cloudflare's import, has you choose your live branch where Cloudflare actually keeps it, and connects your domain only after that. Prefer Cloudflare Pages? Say so, and your assistant sets up a Pages project for you.
- 🩺 When a check fails, it tells you what to fix. When your tab icon's size is set wrong, the icon test names the exact line to change. The legal-pages test lists the three answers you can give. The analytics and deploy checks name the lines your settings are missing. One message, and you know your next step.
- 🎨 Your own icons stay yours. The icon maker replaces only the starter's placeholder icons and leaves the ones you made alone until you say yes. The icon test opens your SVG tab icon the way a browser does, so you catch a damaged file before your visitors do, and it checks the logo search engines show for your business.
- 🛡️ Cloudflare setup touches only what it needs to. It writes only the bot settings it changes, so a setting you just changed in the dashboard should stay as you set it. If one moved anyway, setup names it and asks you to check it.
- 🧪 Fewer checks that pass by mistake. When the link check can't make its working files, it stops and tells you instead of reporting a clean site. The email test now works on sites that count their visitors too. The icon test no longer lets an icon on another site stand in for your own. The analytics check now also catches an email link written without extras (
/go/emailon its own), and it now checks Workers builds too. - 🔒 Built on fresh versions. New sites start on Astro 7.4.13, Playwright 1.65.1 and Wrangler 4.164.0. They ask for a Node.js with November's security fixes, and npm tells you if yours is older.
- 🔄 Publishing offers to try again. If your live site still shows the old version about 3 minutes after you publish,
npm run shipasks you once in the terminal: "Ship again?" Only on your yes does it send one small extra commit, to give Cloudflare a fresh reason to build, and then it keeps watching. Answer anything else, and it simply keeps waiting. If the site still shows the old version after 6 minutes, it tells you where to retry in Cloudflare. This is new, and no one has seen it on a live site yet. If you set build watch paths in Cloudflare, includeSHIP-AGAIN.txtin them. - 🖼️ No more Astro logo in your browser tab. The build now checks your
favicon.svgandfavicon.icofor Astro's known default icons, and when it finds one, it stops and tells you how to replace it. Your launch check now also looks at the icons on your live site. - 📝 (0.35) Every new page gets judged before it's built. Your assistant writes the page out first, a fresh reviewer reads it as your visitor would, and you approve the exact sentences before anything is built.
- ☁️ (0.35) New sites start on Cloudflare Workers. You can publish straight from your computer, with no GitHub connection needed.
- 🔎 (0.35) Your launch check reads your Cloudflare settings. Your assistant walks you through five places in the dashboard and warns you when a setting would keep Google, Bing or Apple out.
- ⚖️ (0.35) Legal pages say when they're still drafts. Your imprint and privacy pages show a visible draft notice until you say how they were checked.
- 🧹 Behind the scenes. Your assistant's second opinion on its own work is steadier: it refuses a prompt with broken characters and says where, turns off add-on servers it doesn't need, and asks you whether to keep fixing when the same kind of problem comes back.
New here? How to start: download croftweaver.zip below, unzip it, and paste the starter prompt from the README into your AI assistant. It takes you by the hand from there. Works on macOS, Linux, WSL, and Git Bash on Windows. To check the download, put SHA256SUMS beside it and follow the README's two-line check.
Updating, upgrading or moving a site:
- 🔒 Update Node.js on your computer. Node.js released security fixes on 10 and 11 November 2026. Run
node --version: if it's older than 22.23.5, 24.22.3 or 26.13.1 (for your line), update it. Your site'spackage.jsonkeeps its own minimum. - 🚚 Moving a site to Workers is easier to prepare. The move guide lists what to have ready, walks you through making the move's token click by click (as Cloudflare's page looked on 17 November), and has it end after 7 days. Before it moves anything, the move script shows how each of your addresses answers today, warns you when your sitemap sets its date to the build time with
lastmod: new Date()(a date that changes on every build), and asks its go question in plain words. The firstrecordruns stop while your site builds, and that is expected: run it again. Andrecordno longer reports a failed build when it checks at the moment the build finishes. The move now also works when your main branch is protected: your assistant sends the change as a pull request, you merge it, and the move carries on from there. If your folder is behind, your assistant tells you the one command that brings it up to date. One limit: if you use "Squash and merge" for it and later merge other changes, the script can't undo the move on its own; ask for help. Read the move guide again before you start. - 🔁 The update helper keeps your choices. When you keep an older copy of a skill on purpose, the report keeps listing what changed upstream. When you leave a test file out, you write down why, and every report shows it. A site with no update record learns how to pick its starting point, and a refresh stops if it can't remove an old folder.
- 🖼️ Check your tab icon first. Open
https://<your address>/favicon.svgandhttps://<your address>/favicon.icoonce. If either shows the Astro logo, replace it before your next build, or the build will stop: a site without icons of its own runsnode scripts/make-icons.mjs --setup(if it says the icons are not ones it made, run it with--replace); any other site asks its assistant to use the brand-kit skill. Google may keep showing the old icon for some weeks. - 🧰 Take the new parts into your site. Nothing changes on its own. Ask your assistant: "take make-icons.mjs and the icons test from the latest Croftweaver starter" (the icons test needs your home page's search-engine data to name
/images/logo.pngon your own site, so a site whose only logo sits on another host now fails it). "Take check_internal_links.sh and tests/email.spec.ts from the latest Croftweaver starter." "Take the analytics gate, check_deploy.sh and verify script from the latest Croftweaver starter"; on a site withscripts/deploy.sh,npm run verifythen needs"deploy:preview": "bash scripts/deploy.sh preview"and"deploy:live": "bash scripts/deploy.sh live"inpackage.json. "Update tests/check_ship_push.sh and scripts/ship.sh from the latest Croftweaver starter, together." For the publish retry and the tab-icon guard (after the check above): "take build-marker.mjs, ship.sh with check_ship_push.sh, and deploy.sh with check_deploy.sh from the latest Croftweaver starter"; if you set build watch paths in Cloudflare, addSHIP-AGAIN.txtto them. On Workers: "take deploy.sh, ship.sh, the Workers config test and playwright.config.ts from the latest Croftweaver starter." Got the toolkit straight from GitHub rather than as the download? Ask: "check if my site needs any updates from the latest Croftweaver version".
For the technically curious, 0.36:
- Starter Node floor:
engines^22.23.5 || ^24.22.3 || >=26.13.1(Node's security releases of 10 and 11 November 2026; the advisory rates the highest on each line High, most in HTTP/2 and TLS);SETUP.md,UPGRADING.md, the starterREADMEandnew-websitesay so. @astrojs/sitemap'ssitemaplibrary 9 → 10 (the sitemap tests pass), Playwright 1.65.1 — PR #565. Starter packages: Astro 7.4.13, @astrojs/sitemap 3.7.6, Wrangler 4.164.0 (exact); a second rolldown (1.3.3) nests under Astro, whose range differs from Vite's;sisteransi1.0.5 → 2.0.0 for@clack/prompts— PR #597. - Move to Workers: a "ready before the freeze" list (
docs/MOVE-TO-WORKERS.mdafter §6);checkwarns on the literallastmod: new Date()in the Astro config (other forms are left torecord; exit code unchanged) and prints each host's status,/build.txtcommit and likely platform; the token gets a 7-day end date; the go question in plain words with a 10-minute line — PR #579. The token's click-by-click steps (two policies, four permissions), as seen on 2026-11-17, inMOVE-TO-WORKERS.md§6 andCLOUDFLARE_MOVE.md— PR #584.check_analytics_gate.shreads/go/email,/go/email#…and/go/email/as go links, and its Workers live (analytics off), Workers preview and empty-CF_PAGES_BRANCHbuilds expect none; the move guide andCLOUDFLARE_MOVE.mdsayrecord's first run for a commit starts the build and exits 4 — PR #596.move-to-workers.mjs: an emptyexit.txt(the build writes it with onewriteFileSync, which creates it before filling it) is judged by the builder's pid, as a missing one is, not read as a failed build — PR #599. For a protectedmain, the push steps print one ref per line:mainfirst, then (two-stage)git fetch originandgit push origin origin/main:production;afteraccepts amaintip that is the route commit, or a squash or merge commit of it (its files and its parent), and uses that commit from then on;moveandundocheck the folder's HEAD and print the one line that brings itsmainthere. After a "Squash and merge" of the move and later merges,undoandmoverefuse and going back needs help (a BUGLOG follow-up) — PR #600. - First deploy on Workers: the production branch is set in the Worker's Settings → Builds after the import, the domain attached after that (
CLOUDFLARE_FIRST_DEPLOY.mdpath B,CLOUDFLARE-CHECKLIST.md§1,new-website) — PR #566. - Pages by command:
wrangler pages project createends in--force, only on the owner's word that the site stays on Pages, since Wrangler 4.162.0 run by an assistant made a Worker without it;wrangler pages deployis unchanged. A Worker made by mistake: checkgit status, restore what Wrangler changed, the owner deletes the Worker, create again with--force— PR #587. scripts/build-marker.mjsstops the build (message on stderr,dist/removed, exit 1) whendist/favicon.svgordist/favicon.icois create-astro's icon: the SVG by Astro's outline path (comments ignored), the ICO by SHA-256; an icon redrawn or re-encoded from Astro's can pass (BUGLOG follow-up).--check <file>...checks downloaded copies; the launch check's live re-check (website-launch-check§8) uses it on both files from the live host — PR #595.scripts/build-marker.mjsalso reads Workers Builds'WORKERS_CI_COMMIT_SHA(only a full commit id), and the starter README,deploy.shandPUBLISHING.mdspeak Workers too, not only Pages.scripts/ship.sh(template-version 0.34) andtests/check_ship_push.sh: about 3 minutes, in a terminal, after the push, if the live site still serves the old build, it asks "Ship again?" once; yes makes one commit onmainthat changes one line ofSHIP-AGAIN.txt, pushes it tomainandproduction, and waits again; no keeps waiting. After 6 minutes the warning names theproductionrow to retry in Cloudflare, never amainrow. Amainthat refuses direct pushes refuses the retry, and ship gives the dashboard steps. Build watch paths must includeSHIP-AGAIN.txt. The cause of the missing build on 2026-11-17 is unproven, and the retry has not yet been seen to start a build on a real site (tested against stubs and a local git server) — PR #594.scripts/check_internal_links.shexits 1 with a message whenmktempfails (whats-newoffers the new copy to a site whose baseline is older);cloudflare-setup.mjssends only the Bot Management fields it changes (a left-out top-level field that differs from the zone's start is not yet shown kept on a live zone; a moved one reads back "by hand");tests/email.spec.tsremoveswindow.plausibleafter load, so the no-tracker test passes with analytics on — PR #589.make-icons.mjs --setupreplacesfavicon.svgandfavicon.icoonly when each is create-astro's Astro logo (by SHA-256); other favicons need--replace.tests/icons.spec.tskeeps a link on another host as its whole address, so it fails.whats-newwith template-test copies and no stamp says how to pick a baseline;--refreshstops, naming the folder, if it cannot delete the brand kit's left-behind test folder — PR #590.scripts/ship.sh,scripts/deploy.sh,tests/workers-config.spec.ts,tests/check_deploy.sh,tests/check_ship_push.shandplaywright.config.ts: trailing commas inwrangler.jsoncread;deploy.shreadssite:asship.shdoes (a commented address gives "cannot check"); the Playwright fallback looks for the headless shell — PR #588.tests/check_ship_push.shandscripts/ship.shtemplate-version 0.32 (this release ends at 0.34): a failing setup step names its case as[<case> (setup)]and adds "Stopped at line N: " (on macOS's bash 3.2 the line number is wrong and the message says so; a failure inside a( … )subshell is not named there) — PR #564.tests/icons.spec.ts: reads the logo from the home page's structured data, notCOMPANY.logo, and needs/images/logo.pngon the site's own origin; loadsfavicon.svgin the browser — PR #577; the sizes failure names theBase.astroline — PR #581.tests/placeholders.spec.ts: the message names the three answers;AGENTS.md§5 for sites made before 0.35 — PR #576.- The analytics gate and
tests/check_deploy.shname the missingsrc/config.tslines;whats-newsays both read that file; withscripts/deploy.sh,npm run verifyneeds the starter'sdeploy:previewanddeploy:livelines — PR #575. whats-new --refreshwrites apinned:line inSUITE-VERSIONfor a pinned skill the suite still has, so the report keeps its upstream changes (delete the line once taken);--stamp-testskeepsleft_out: <path> — <why>andkept:lines intests/TESTS-VERSION, and every report lists them — PR #574.independent-review: the Codex seat refuses a prompt that is not UTF-8 and names where — PR #568; no fewer-than-2 warning on a one-seat Light round — PR #570; round 2 of a Normal or High gate refuses when the log shows its fresh-eyes seat was never logged — PR #582; ask the manager at a kind's second return after a cut — PR #585, plan PR #580; Codex runs turn off the MCP servers they can name — PR #586, plan PR #583; a READ of a web page quotes the page itself, not a summary of it — PR #593.make checktakes a lock, so one run goes at a time for each user on a machine — PR #562;scripts/check_next.sh set <session> | show | clearnames whose run is next, and the lock refuses everyone else until that session runs or 10 minutes pass after the later of the entry and the last run's end — PR #592, plan PR #591. The maintainer's Antigravity release test reads Google's 503s and stray files correctly — PR #560.- Maintenance: BUGLOG rows — PR #561, PR #563, PR #567, PR #569, PR #571, PR #572, PR #573, PR #578.