Publish /llms.txt and reconcile Phase 1 Foundation completion dates

What was done

1. Published /llms.txt at site root via public/llms.txt. Lifted from .tmp/seo/llms.txt template, with two additions to the Knowledge resources block: the new cost FAQ at /dev-iq/faqs/cost/ and the SEO Plan page at /dev-iq/seo-plan/. Both shipped today and warrant inclusion in the AI-discoverability index. Build verified — file lands at dist/llms.txt, will serve as https://baileyengineers.com/llms.txt after deploy.
2. Corrected Phase 1 Foundation completion dates in items.json. The previous dates (March 1–20, 2026) were aspirational guesses I made when first populating the file. Ryan clarified that the new website didn’t actually launch until 2026-04-26 — meaning the schema, robots.txt, sitemap, GA4, and breadcrumbs all went live on that date, not earlier. Updated the seven affected items to completedAt: 2026-04-26.
3. Added a new “site-launch” item at the top of Phase 1 Foundation to record the website upload-and-test milestone explicitly: {"id": "site-launch", "title": "New website uploaded and tested", "status": "done", "completedAt": "2026-04-26"}. Gives the seo-plan page a concrete launch event to hang the rest of the foundation work off of.
4. Marked llms-txt done in items.json (previous status pending, target 2026-05-10) — file is now in public/, builds clean, will be live on next deploy.
5. Reconciled website-schema to 2026-04-28 specifically — the WebSite schema’s name property was added today (during the schema-validation pass), so its current shipping date is today, not site-launch day.

Why

The seo-plan page is a public progress tracker. Wrong dates would erode the credibility the page is supposed to build. Ryan flagged the GA4 date specifically; the same logic applies to all the Phase 1 items — they couldn’t have been “completed” before the site that hosts them actually went live. Corrected the whole block while we were in there.

llms.txt was the next P0 in the SEO plan (target 2026-05-10, was 12 days out). It’s a small mechanical move with high upside — AI assistants increasingly use llms.txt as a first-pass index of a site’s structure, so publishing one before competitors do is a cheap visibility signal.

Files affected

Created:

• public/llms.txt — site-root machine-readable index per llmstxt.org
• src/content/devlog/2026-04-28-llms-txt-and-dates.md — this entry

Modified:

• src/content/seo-plan/items.json — Phase 1 Foundation date corrections + site-launch item + llms-txt done

What’s next

SSOT fix on FAQ articles to clear the 6 schema-vs-body drift warnings the validator flagged. Plan: render the visible “Common questions” <dl> from the same data.faq[] array that drives the FAQPage schema (single pass through the data), then strip the ## Common questions markdown sections from the 10 collection article bodies. Architecturally drift becomes impossible going forward.

Bing Webmaster Tools is the next pending Phase 1 item (target 2026-05-15) — Bing’s index powers ChatGPT search, so registering there has compounding AI-visibility value beyond just Bing search itself. Outside the codebase but should be on Ryan’s calendar.