[IsaiahSama]

Part of #3256 (step 1 of the steps comment).

What

api_v2's estate snapshot held only landing's .md pages. Landing builds three more pages from code, and none of them had an api_v2 record:

• /bank-holiday-calendar (work-employment);
• /health-and-emergency-services/find-an-emergency-shelter;
• /health-and-emergency-services/water-outages.

So they're missing from api_v2-driven category listings today (sandbox), and from search, the sitemap and GET /catalog once those stop adding the static registry pages. #3604 lists this as something the API_V2_URL switch-on (alpha-infra#801) waits for.

build-seed-data.ts now writes a page from the META in every -meta.ts under apps/landing/src/routes, and estate.json gains the three pages (125 → 128).

How

• Fields. Each page takes from its META:

  • url, title and description;
  • its category (subcategory ?? category);
  • frontmatter.keywords, which api_v2 search reads from there;
  • its visibility (default public).

  It has no parent, form or publish date.

• content_slug is the META url. That is landing's registry slug for a feature page and the service_status key, so the import's visibility overlay still applies.

• The body is empty. Landing renders these pages from their own routes, which take precedence over the $ catch-all, so it never shows the body. The public chat assistant's api_v2 ingest (apps/chat/src/ingest/api-v2-source.ts) chunks every /catalog page's body, though, so any text there becomes a source chat cites. An earlier version of this PR carried an editor note there; review caught it reaching chat, and the decision on the issue changed to an empty body. Chat now ingests only the title and description.

• require() with one lint-disable comment. tsx runs this script as CommonJS, and top-level await import() fails with "Top-level await is currently not supported with the cjs output format". The -meta.ts files have only type-only imports.

• A local FeatureMeta type. The script copies from landing rather than importing from it, as with NESTED_WITHOUT_URL.

Left out: the StormReady checklist (.tsx). routes/$.tsx does v2Page ?? findPage(splat), so an api_v2 row at its url would take precedence over the self-rendered page. It waits on #3239.

Landing's render parity test is unchanged. apps/landing/src/lib/api-v2-render-parity.test.tsx (#3135) requires every seeded page to render the same HTML as its static twin. With an empty body, these three do, so the test now checks them too. (The note version needed an exemption list there; this version reverts it.)

Not in this PR

• Sandbox. Sandbox has had its one-time import, so this snapshot doesn't reach it. api_v2/landing: list tool and feature pages in api_v2 listings, search and sitemap #3256 step 2 creates the three pages there by hand, unless api_v2: catch and fix drift between estate.json and a deployed database before cutover #3709's drift work covers them.
• Smoke tests, before step 2. Once these rows exist on sandbox, two Landing v2 smoke tests need them exempted. content-source.live.pw.ts expects x-content-source: api_v2 on every /catalog page, but only routes/$.tsx sets it. visibility.live.pw.ts expects a Preview catalog page to 404, but these routes don't read api_v2's visibility. Recorded on api_v2/landing: list tool and feature pages in api_v2 listings, search and sitemap #3256.
• Staging and prod get the pages when they import at cutover.

Checks

On the final version:

• seed.test.ts: a new case checks each page's category, parent, form id, visibility, content_slug, keywords and empty body. It failed before the script change, fails when the feature pages are left out of the snapshot, and fails when they're forced to draft. The existing per-page test also seeds a database and serves the three pages under their categories.
• Full nx run api_v2:test: 44 files, 1068 tests pass.
• Full nx run landing:test: 93 files, 1557 tests pass, with the parity test at its base version.
• eslint and prettier are clean on every changed file. Running pnpm seed-data again changes nothing.

On the first version (the note body), not re-run since; CI covers them:

• nx run editor_v2:test, which also reads estate.json: 224 files, 2040 tests pass.
• api_v2:lint, tsc -p apps/api_v2/tsconfig.check.json, api_v2:build and pnpm exec tsc -b are clean.
• Local smoke: api_v2 with SEED=true on a throwaway database.
  • GET /catalog lists all three as public.
  • /categories/work-employment lists the calendar, and /categories/health-and-emergency-services lists the other two.
  • /search/documents carries their keywords.
  • GET /pages?url=/bank-holiday-calendar returns 200.

Closes doesn't take effect on a v2-rewrite PR, and #3256 stays open for step 2 and the checklist anyway.

🤖 Generated with Claude Code

[github-actions]

Amplify PR previews

App	Status	URL
forms	⏭ Not affected	—
landing	✅ Ready	https://worktree-3256-feature-route-records.d3kbl8o0ovutw4.amplifyapp.com
chat	⏭ Not affected	—
form-builder	⏭ Not affected	—
analytics	⏭ Not affected	—

Commit: a7bbb07 · Branches auto-delete when this PR closes.

ℹ️ feature-flagging uses a single shared preview slot at a fixed URL (preview.feature-flagging.sandbox.alpha.gov.bb) — GitHub login works, but only one FF preview exists at a time (the most recent FF PR build wins). It reads/writes sandbox flag data.