Skip to content

0.35

Choose a tag to compare

@karero karero released this 14 Nov 15:50
Immutable release. Only release title and notes can be modified.
8825573

Croftweaver 0.35 — pages judged before they're built, and a launch that reads your Cloudflare settings 📝

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:

  • 📝 Every new page gets judged before it's built. When you ask for a new page, an article or a rewrite, your assistant first writes it out as one page document. A fresh reviewer reads it as your visitor would, and for search and AI answers. You approve the exact sentences; after the build, a check makes sure the page kept them. The new skill is copied into every new site and never runs unasked.
  • 🚚 Move a page from an old site without losing what worked. Your assistant first saves the old page's headings, downloads, forms and embeds, and the reviewer checks that no section or search that brought visitors is lost. Four weeks after go-live it compares the page's clicks before and after, and tells you if it kept less than half. On a small site it still lists every search that brought a click.
  • 🔎 The launch check reads your Cloudflare settings. At the live re-check, your assistant walks you through five places in the Cloudflare dashboard and writes down what they show. That re-check is no longer optional: for a new domain, it's the only step that looks at these settings. It also reads your README's answer about your legal pages and asks whether it still holds. And after you publish, it checks that your live home page counts visitors the way your settings say, and tells you plainly when it doesn't.
  • 🤖 Search engines and AI assistants can still reach your site. Since 15 September 2026, blocking AI training in Cloudflare also shuts out Google, Bing and Apple. Setup now warns you when it finds that, on launch day too, and the checklist shows how to refuse AI training and stay in search. Cloudflare now also lists personal AI agents (assistants that fetch a page for a person), which the general AI setting left as they were. Setup now sets each to Cloudflare's "disabled" setting, after listing the changes for your yes, and sends you to the dashboard if Cloudflare doesn't confirm. The Cloudflare check now also knocks as Claude-SearchBot, Anthropic's search crawler, and the Search Console steps say where to see which AI crawlers came.
  • ⚖️ Legal pages that say when they're still drafts. A new site's imprint and privacy pages show a visible draft notice until you say how they were checked: by a lawyer, your own texts, or published as drafted. Your assistant asks once and notes your answer in the README; a test keeps the notice until then. English sites now get an English Legal Notice; a German Impressum is offered only if your business is based in Germany.
  • 📜 Croftweaver's licence travels with your site. Every new site has a CROFTWEAVER-LICENSE.md in its top folder, the licence of the Croftweaver files it carries (tests, scripts, hooks). Keep it when you hand your site's source to someone or publish it. Your visitors never see it.
  • 🚀 Publishing shows what goes live, and where (for sites with a preview and a live version). npm run ship now names your site and its GitHub repo first, lists the changes that go live, and in a terminal window asks you to type y before it uploads anything. A run by your assistant isn't asked and says so.
  • 🔤 A tab icon from day one. New sites draw their first letter on your brand colour into every icon file, instead of pointing to icons that weren't there. Once you have a logo, the brand kit replaces them, and it now reads more real logo files it used to turn down.
  • ☁️ For sites on Cloudflare Workers. New sites now start on Workers, and you can publish one straight from your computer, with no GitHub connection. A site already on Workers now counts its visitors (before, analytics there counted nothing), and its publish script and headers work there too. For advanced users, a new script moves a live site from Cloudflare Pages to Workers, checks that nothing visible changed, and moves it back on request. Before it moves anything, it checks that your analytics will still count on Workers. A new guide says what you decide, do and see along the way; you don't have to move, and a Pages site keeps working.
  • 🗺️ Search engines get the sitemap they can read. New sites point search engines straight at the file that lists your pages, and the Search Console steps submit that file. Bing had called the old index file "not accessible" on a live site.
  • 🧭 Search and AI advice you can check. The skills now say Google stopped showing FAQ rich results in May 2026. AI monitoring starts with Google's and Bing's free AI reports and asks each question several times. The content guide quotes Google's own words on trust and adds a short rule for figures on a page: source, date, what it counts. Advice that had no source now has a dated one, or is gone. Advice on being cited by AI now starts with being found: a page whose title and a paragraph answer your customers' questions in their own words. The often-quoted figure that 85% of brand mentions come from other sites is now named for what it is: one vendor's study of business-software searches.
  • 📱 The phone check sees hidden pictures. A picture kept out of sight by a fade or a cut-off frame, such as a carousel's waiting slides, now counts as hidden, so a big one no longer passes.
  • 🧪 Tests you can trust. Your site's tests now notice when a second build in the same folder replaced the pages under test, and they run in Claude Code's cloud sessions too.
  • 🔐 Your assistant asks before it commits. A commit, a new working branch and its first push now ask first.
  • 🧹 Behind the scenes. Setup copies your .gitignore back in a way every assistant may run, the Antigravity guide says to install the suite one way only, and the AI check says it runs weekly and what that costs. The update helper names any file a changed test needs that your site lacks. And your assistant's second opinion on its own work checks sweeping claims before every review and keeps real reviews it used to throw away. Skills no longer send your assistant to skills Croftweaver doesn't have, and the brand kit's messages say plainly what to do. The AI SEO, Search Console and team-setup guides no longer show a garbled price when you start them with extra words. On a computer with none of its fonts, the share-card maker now stops and says which font to install, instead of drawing ä, ö, ü and ß as empty boxes. New sites start on Node 26, the current long-term version; a site on Node 22 or 24 keeps working.

🔁 Already have a site? Nothing changes on its own. For page reviews, ask: "copy the website-new-page skill from the latest Croftweaver into my site"; for the Cloudflare reading at launch: "update my website-launch-check skill from the latest Croftweaver". For the draft notice, ask: "take the new legal-page test from the latest Croftweaver starter and ask me the legal-pages question"; the test stays red until your answer is recorded. Ask: "copy CROFTWEAVER-LICENSE.md from the latest Croftweaver starter into my site". If your site publishes in two stages: "update my publish script to the latest Croftweaver version". For the letter icon: "add the icon maker and icon test from the latest Croftweaver starter" (brand-kit icons need nothing more). For the sitemap: "point my robots.txt at sitemap-0.xml and take the new sitemap test", then submit sitemap-0.xml in Search Console and Bing. For hidden pictures: "copy the phone-images test in again from the latest Croftweaver starter"; it may find pictures to fix. For the build check: "take the served-build files from the latest Croftweaver starter, all three together". For the shorter permission list: "merge the latest Croftweaver permission list into my .claude/settings.json". Still on Cloudflare Pages? Your site keeps working there. The update check marks scripts/deploy.sh as for Workers sites only; don't take it, or wrangler.jsonc, until your site has moved. To move, read the move guide first. To move a site to Node 26: "take .nvmrc and the CI file from the latest Croftweaver starter, together". On Cloudflare Workers: "update my site for Workers from the latest Croftweaver, including the analytics line in src/config.ts". If you got the toolkit straight from GitHub (rather than as the download below), ask: "check if my site needs any updates from the latest Croftweaver version".

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.


For the technically curious, 0.35:

  • New skill website-new-page (always-on, now twenty-nine): page document, content review (independent_review.sh --content), owner approval, scripts/check_page_text.py on the build — PR #472, PR #473, PR #475, PR #474. Existing sites copy skills/website-new-page in by hand. Migrated-pages mode: old headings, downloads, forms and embeds in the research file, a section table, two fixed 28-day windows for the four-week check; gsc_query.py gains --start/--end, --by-date and --pages-csv, --page matches exactly (closing slash included), drill-downs list up to 100 rows — PR #507. The four-week check heads its table with the page's own total, flags a page with at least 10 clicks before that keeps less than half, and lists every query with a click as main or for information — PR #511. A site needs nothing else.
  • website-launch-check: five dashboard reads, listed once in docs/CLOUDFLARE-CHECKLIST.md §5; new-website step 12a is no longer optional (only its speed part is); no script, no new token — PR #508. A new Always item quotes each README legal pages: line, reports published as drafted as 🟡, and blocks a legal page no line covers — PR #489. After a publish, scripts/check_live_analytics.py reads the live home page's Plausible tag against src/config.ts (USE_ANALYTICS, mode): exit 0 match, 1 mismatch with likely causes, 2 not checked — PR #520.
  • cloudflare-setup.mjs: since Cloudflare's change of 15 September 2026, Block on Training also keeps Googlebot, Bingbot and Applebot out; setup notes it when it finds Training on Block, and the checklist, ai-seo and search-console-setup point to Disallow with Bot Preference Sync on to refuse training and stay in search — PR #450; launch day prints the same notes — PR #489. The ai line sets every ai_agents entry Cloudflare lists to the API's disabled; the read-back must show them all disabled, else "by hand" — PR #504. The setting's new name, "AI Crawler and Agent access policies" — PR #485. cloudflare-check.mjs also sends a Claude-SearchBot request, so a setting that refuses it is a look; search-console-setup step 4 points to AI Crawl Control → Overview and says no published measurement of time to first AI citation was found — PR #523.
  • Legal pages: /privacy, /impressum and /datenschutz carry a draft notice until the README records legal pages: reviewed by a lawyer, own texts or published as drafted, with a date; tests/placeholders.spec.ts fails a page with neither. whats-new.sh offers the new AGENTS.md and tests but never page text, so an existing site that takes the spec fails it until the AGENTS.md §5 question is asked and answered — PR #457. The starter ships src/pages/legal-notice.astro and an unrouted _impressum.astro; astro-i18n-setup gaps fixed. A live site keeps its pages, Base.astro and /impressum (--refresh copies skill folders only; no redirect). Merging tests by hand, keep your legal paths in PAGES, UNFILLED_UNTIL_LAUNCH, OWN_CARD_EXEMPT and POSITIONING_EXEMPT, and add /legal-notice only if you route it; a wrong merge fails loudly. Launch day's stop message accepts impressum and legal-notice — PR #493.
  • Starter licence: CROFTWEAVER-LICENSE.md (a copy of LICENSE), not in the built site. Sites made before 0.35 copy it from skills/new-website/templates/astro/; whats-new lists it as MISSING only for a site scaffolded from a git clone — PR #444, plan PR #443.
  • Two-stage sites: scripts/ship.sh and tests/check_ship_push.sh are template-version 0.31; take them together (whats-new also lists PUBLISHING.md). The run's first line names the site address and GitHub repo; before uploading it prints the commits that go live, newest first, a merged pull request as one line, at most 20 lines; at a terminal it asks for a typed y (any other answer: "Nothing was published"), and with no terminal or output to a file it says it isn't asking. With nothing new it says so. With more than one site: address (a commented one counts), the live check checks none and says why; the stall warning comes after about 6 minutes — PR #467, PR #490, PR #495, plan PR #458.
  • Starter icons: scripts/make-icons.mjs and tests/icons.spec.ts, taken together. A site with no icons, or only the Astro logo, runs node scripts/make-icons.mjs --setup before npm test; one with the brand kit's icons needs nothing; one built from tab-icon.md copies public/icon-512.png to public/images/logo.png; after a colour change, run node scripts/make-icons.mjs again — PR #510. The tab icon tag now lists the four sizes inside favicon.ico (16x16 32x32 48x48 64x64), which make-icons.mjs and the brand kit both write, and icons.spec.ts checks the tag against the file. A site whose icons came from an earlier brand kit has one 32 px size and fails that test: set the tag to sizes="32x32", or make the icons again with the brand kit — PR #527, PR #531. Brand kit: tab icon recipe — PR #452; standard SVG DOCTYPEs, escaped class names and no-effect styles read, not refused — PR #513; the line-end refusal says to paste again as plain text, and a redrawn currentColor mark gets one way on, not two — PR #521.
  • Workers sites: with analytics on in script mode, copy enabled: USE_ANALYTICS && (process.env.CF_PAGES_BRANCH ?? process.env.WORKERS_CI_BRANCH) === PROD_BRANCH, into your src/config.ts, together with the new tests/check_analytics_gate.sh and its fixture, which fail without it. Analytics server mode left the starter: the new EmailLink.astro fails the build in server mode on any host, so a Pages site in server mode keeps its 0.34 EmailLink.astro. Deployed by command with a wrangler.jsonc, take scripts/deploy.sh and its two package.json scripts and run npm run deploy:live; with another config name, keep passing CF_PAGES_BRANCH=<branch>. Take the 0.35 public/_headers, scripts/build-marker.mjs, scripts/ship.sh, scripts/hooks/pre-push and tests/check_ship_push.sh; merge PUBLISHING.md, AGENTS.md, CLAUDE.md and SETUP.md, keeping your own deploy lines. If functions/go/ is gone, delete tests/analytics-server.spec.ts and skip functions/go/email.ts — PR #491. move-to-workers.mjs and references/CLOUDFLARE_MOVE.md — PR #469, PR #486, PR #492, PR #494; cloudflare-check.mjs reads Workers sites (--site, --preview, workers-dev, previews) — PR #478. The move script picks the site's zone only where Cloudflare lists DNS Edit for the token, so read or account-wide permissions elsewhere no longer stop it — PR #518; with analytics on, check lists a stage-1 gap when the ANALYTICS object reads CF_PAGES_BRANCH and no other variable (a line that also reads the site's own deploy variable passes), and refuses a block comment in src/config.ts — PR #526; it compares Content-Type by its media type, so a site whose _headers sets that header can move (a dropped charset=utf-8 passes, any other change does not) — PR #532. New sites deploy on Workers: wrangler.jsonc (set its name first), scripts/deploy.sh with npm run deploy:preview and npm run deploy:live (a clean tree for live, on the production branch only: PR #535), Wrangler as a devDependency; a Pages site takes none of them until it moves — PR #533. On a Workers config with no domain, npm run ship counts "no such host" only when the DNS servers say so and also answer for github.com, so an offline Mac no longer skips a mid-move site's live check — PR #534. cloudflare-setup.mjs sets up Workers sites, not Pages: setup and launch read the Worker's version link, and on launch day replace the host's one record and attach the domain to the Worker; its token needs Account → Workers Scripts Edit — PR #543. On launch, step 7 no longer stops when the zone has an empty response-header ruleset, and a 5xx from the build check just after the domain is attached ends with status 4 (waiting for Cloudflare) and says to run it again — PR #554. The starter's public/_headers withdraws the NEL policy Cloudflare adds on a Worker's version and Preview links (workers.dev), and cloudflare-check.mjs item previews fails a preview link that still carries an active nel or a report-to; take the new _headers rule — PR #549. The deploy guide, skill docs, starter docs and README describe Workers; what only applies to Pages sits in a section for sites already on Pages, and PUBLISHING.md, SETUP.md and AGENTS.md are worth merging again — PR #552. docs/MOVE-TO-WORKERS.md is the owner's guide to the move (who it is for, the token, the day, going back, a stopped run), and references/CLOUDFLARE_MOVE.md points to it — PR #557.
  • docs/WHAT-THE-SKILLS-RUN.md names move-to-workers.mjs: its token (CLOUDFLARE_API_TOKEN, or a git-ignored .dev.vars), its Cloudflare and GitHub reads, its move-run/ folder and route commit, its state in ~/.config/croftweaver/moves/ — PR #530.
  • Sitemap: robots.txt names https://<domain>/sitemap-0.xml and the search-console steps submit it, not sitemap-index.xml. Existing sites take the new tests/seo.spec.ts test with their own public/robots.txt change, or it fails and names the line; a site whose index lists a second file keeps the index and drops the test — PR #503.
  • Advice: FAQ rich results gone since 7 May 2026 (docs removed 15 June 2026); FAQPage markup still added — PR #438. ai-seo: free AI reports first, repeated asks, no AI crawler page says it reads llms.txt, Bing's own Copilot post, Search Console's "Search generative AI" control — PR #441. website-content-guide and the starter's CONTENT_GUIDE.md: Google's E-E-A-T wording (not itself a ranking factor; trust matters most) and the figures rule (source, date, what it counts, the study's seller, finding apart from conclusion, facts-check list) — PR #440. Unchecked advice sourced or cut — PR #496. ai-seo leads with being found (two 2026 arXiv preprints: for ChatGPT, retrieval explained citations far more than page features, and the 2023 GEO gains were measured on pages already retrieved); the GEO table comes second, the audit, Common Mistakes and eval 1 follow; a site needs nothing else — PR #519. The AirOps "85% of brand mentions" figure is scoped to one vendor's study of 500+ queries in the business-software categories it names — PR #524. search-console-setup step 4: the Cloudflare check's own AI crawler requests do show in AI Crawl Control, and it says how to take them off the counts — PR #542.
  • Starter tests: served-build.spec.ts also catches a second build in the folder; take it with playwright.config.ts and scripts/build-marker.mjs (a mix fails every run) — PR #445. phone-images.spec.ts counts opacity: 0 or a parent's overflow: hidden as hidden; copy it in again and expect new failures (a carousel: load each waiting slide just before it shows) — PR #454. Cloud-session Chromium fallback — PR #460; axe contrast warning, starter README lists — PR #501; node-html-parser ^9.0.7 — PR #499. functions/_middleware.ts treats a CANONICAL_URL that is an IP address or a one-label host (localhost) as no live domain; phone-images.spec.ts waits only for the page's own images, not an embedded frame's; the pre-push hook and SETUP.md say it tests the files on disk — PR #517.
  • scripts/generate_og_cards.py stops before writing any card when none of its five font pairs is installed, lists the files it looked for, names a font to install (DejaVu Sans or Liberation Sans on Linux, Arial on Mac and Windows), and prints the font it used on every run; take it from the starter — PR #556.
  • Starter Node: .nvmrc 24 → 26, and .github/workflows/ci.yml tests on 26. Take both together, or CI tests a different major than .nvmrc names; the kit's check_node_floor.sh now checks the match. engines is unchanged (^22.23.4 || ^24.22.1 || >=26.12.1), so 22 and 24 stay supported. @types/node is ^26.6.6; Dependabot holds it at the Node major, so a site that wants the 26 types bumps it by hand — PR #558. The kit's own CI also checks and builds the starter on Node 24 — PR #559.
  • Permissions (merge .claude/settings.json by hand): delete Bash(node:*), Bash(npm exec:*), Bash(rg:*), Bash(find:*), Bash(tree:*), Bash(mv:*), Bash(open:*), the nine image-tool rules and Bash(git <verb>:*) for commit, branch, checkout, switch, init, merge, restore, stash, remote, fetch, pull and push; add the template's exact git rules, Bash(node --version) and its three deny rules; website-permissions §1 has the list — PR #471.
  • Owner docs: .gitignore copied back with cp, not git checkout; Antigravity installed one way only; the AI check runs weekly — PR #483. Team setup and checklist step 5 — PR #500. whats-new names each file a changed template test imports that the site lacks: take it, change the test, or leave it out — PR #488, replacing PR #446. create-croftweaver 0.2.2 carries the new README to npm — PR #439. Skills drop pointers to 14 skills the suite does not hold, or name the one that fits — PR #516.
  • independent-review: the claims sweep ("nothing", "only", "every") runs before round 1 of every prose review, Light included — PR #447; also PR #462, PR #468, PR #476, PR #477, PR #481, PR #482, PR #502, PR #505, PR #506, plan PR #512; it refuses a --base on the default branch that the branch does not contain — PR #514. make check guards the zip's scripts — PR #451; README "Changing the starter" — PR #456; Python 3.9 CI on ubuntu-24.04 — PR #484.
  • npm run ship at template-version 0.31 (take scripts/ship.sh and tests/check_ship_push.sh together): when the only site: address in astro.config.mjs sits in a comment, or ship can't tell whether it does, it says so and asks you to check the live site, instead of perhaps printing "✓ LIVE" for an address the build does not use — PR #539. A live site that gives no reply from this machine no longer reads as an OLD build: ship says it could not check, asks you to open /build.txt, and exits 1; an HTTP error names its status — PR #540, PR #544. Any HTTP status counts as a reply, even when curl stops early; only a commit id that differs reads as another build, which ship names ("most likely the OLD build") and follows with the Cloudflare steps; any other answer says ship could not confirm the deploy, that this does not mean the build failed, and points to /build.txt — PR #553.
  • whats-new --refresh copies only the toolkit folder's committed skills, so stray or hidden edits there no longer reach your site, and a copy that fails leaves the old one in place — PR #538.
  • Starter packages: astro ^7.4.11, @playwright/test ^1.65.0, Wrangler 4.161.0; docs/UPGRADING.md names the new astro floor — PR #536, PR #551.
  • ai-seo, search-console-insights and website-team-setup: five amounts that began with $0, such as $0/month, are now written in words, since Claude Code replaces $0 in a skill with the skill's first argument — PR #555.
  • Maintenance: BUGLOG, decision and plan-status rows — PR #437, PR #442, PR #448, PR #449, PR #453, PR #455, PR #459, PR #461, PR #463, PR #464, PR #465, PR #466, PR #479, PR #480, PR #487, PR #497, PR #498, PR #509, PR #515, PR #525, PR #528, PR #529, PR #537, PR #541, PR #545, PR #546, PR #547, PR #548, PR #550.