npm - @skyf0xx/hedgehog - Versions diffs - 0.1.21 → 2.0.0 - Mend

@skyf0xx/hedgehog 0.1.21 → 2.0.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (115) hide show

package/src/golden-cores/landing-page/public/favicon.ico ADDED Viewed

Binary file

package/src/golden-cores/landing-page/public/favicon.svg ADDED Viewed

@@ -0,0 +1,9 @@
+<svg xmlns="http://www.w3.org/2000/svg" fill="none" viewBox="0 0 128 128">
+    <path d="M50.4 78.5a75.1 75.1 0 0 0-28.5 6.9l24.2-65.7c.7-2 1.9-3.2 3.4-3.2h29c1.5 0 2.7 1.2 3.4 3.2l24.2 65.7s-11.6-7-28.5-7L67 45.5c-.4-1.7-1.6-2.8-2.9-2.8-1.3 0-2.5 1.1-2.9 2.7L50.4 78.5Zm-1.1 28.2Zm-4.2-20.2c-2 6.6-.6 15.8 4.2 20.2a17.5 17.5 0 0 1 .2-.7 5.5 5.5 0 0 1 5.7-4.5c2.8.1 4.3 1.5 4.7 4.7.2 1.1.2 2.3.2 3.5v.4c0 2.7.7 5.2 2.2 7.4a13 13 0 0 0 5.7 4.9v-.3l-.2-.3c-1.8-5.6-.5-9.5 4.4-12.8l1.5-1a73 73 0 0 0 3.2-2.2 16 16 0 0 0 6.8-11.4c.3-2 .1-4-.6-6l-.8.6-1.6 1a37 37 0 0 1-22.4 2.7c-5-.7-9.7-2-13.2-6.2Z" />
+    <style>
+        path { fill: #000; }
+        @media (prefers-color-scheme: dark) {
+            path { fill: #FFF; }
+        }
+    </style>
+</svg>

package/src/golden-cores/landing-page/src/motifs/.gitkeep ADDED Viewed

File without changes

package/src/golden-cores/landing-page/src/pages/index.astro ADDED Viewed

@@ -0,0 +1,24 @@
+---
+import '../styles/global.css';
+---
+<html lang="en">
+  <head>
+    <meta charset="utf-8" />
+    <link rel="icon" type="image/svg+xml" href="/favicon.svg" />
+    <link rel="icon" href="/favicon.ico" />
+    <meta name="viewport" content="width=device-width" />
+    <meta name="generator" content={Astro.generator} />
+    <title>landing-page core</title>
+  </head>
+  <body class="bg-paper font-body text-ink">
+    <!--
+			landing-builder replaces this file at the Chain Method's build
+			phase. Until then this placeholder proves the Astro + Tailwind
+			pipeline (dev server, build, token layer) works end to end.
+		-->
+    <main class="flex min-h-screen items-center justify-center">
+      <h1 class="font-display text-2xl">landing-page core — ready to build</h1>
+    </main>
+  </body>
+</html>

package/src/golden-cores/landing-page/src/sections/.gitkeep ADDED Viewed

File without changes

package/src/golden-cores/landing-page/src/styles/global.css ADDED Viewed

@@ -0,0 +1,18 @@
+@import 'tailwindcss';
+/* The token layer — Step 5 (Systems Designer) of the Chain Method
+   overwrites every value below with the project's derived token system.
+   Nothing here is meant to ship as-is; this is the placeholder that
+   proves the pipeline (Tailwind v4's CSS-first @theme) is wired. */
+@theme {
+  --color-ink: #18181b;
+  --color-paper: #fafafa;
+  --color-accent: #2563eb;
+  --font-display: 'system-ui', sans-serif;
+  --font-body: 'system-ui', sans-serif;
+  --spacing-unit: 0.25rem;
+  --ease-standard: cubic-bezier(0.4, 0, 0.2, 1);
+}

package/src/golden-cores/landing-page/tsconfig.json ADDED Viewed

@@ -0,0 +1,5 @@
+{
+  "extends": "astro/tsconfigs/strict",
+  "include": [".astro/types.d.ts", "**/*"],
+  "exclude": ["dist"]
+}

package/src/skills/hedgehog-bootstrap/SKILL.md CHANGED Viewed

@@ -16,7 +16,7 @@ This skill touches no domain modules — no schema, no contract, nothing
 under `libs/<module>/`. That's Phase A, started fresh after Bootstrap
 closes.
-**Core lands via `hedgehog-bootstrap-core`, run first, unconditionally.**
+**Core lands via `hedgehog-bootstrap-full-stack-app-core`, run first, unconditionally.**
 That skill copies a pre-built, pre-verified workspace (Nx, enforcement
 config, `packages/db`, `apps/api`, `apps/web`) rather than generating it
 live — core is identical on every project, so it's built once upstream
@@ -36,12 +36,12 @@ Hedgehog has one non-negotiable **core** — applied to every project that
 uses Hedgehog at all, regardless of size — plus a small set of named
 **add-ons**, each scaffolded only when planning intake's scope boundary
 (`planner`) actually calls for it. The core is not "the small version of
-the stack"; it's the fixed floor, landed by `hedgehog-bootstrap-core`.
+the stack"; it's the fixed floor, landed by `hedgehog-bootstrap-full-stack-app-core`.
 Add-ons are not "extra polish"; each is standing infra with a real
 ongoing cost (a service to run, a secret to manage, a seam to keep
 idempotent) that a project without the matching need shouldn't carry.
-### Core (every project, no exceptions — see `hedgehog-bootstrap-core`)
+### Core (every project, no exceptions — see `hedgehog-bootstrap-full-stack-app-core`)
 | Layer | Choice |
 |---|---|
@@ -65,7 +65,7 @@ idempotent) that a project without the matching need shouldn't carry.
 Constraint-contingent substitutions: Prisma for Drizzle when the team
 isn't SQL-comfortable; cloud + Pulumi/SST for Railway when full
 declarative IaC is a hard requirement; tRPC for ts-rest when the client is
-committed TypeScript-only. A substitution here means `src/golden-core`
+committed TypeScript-only. A substitution here means `src/golden-cores/full-stack-app`
 itself needs regenerating against the substitute before this project's
 Bootstrap runs — not a per-project hand-edit after landing core.
@@ -85,7 +85,7 @@ stubbed or partially wired.
 A project with none of these on is still a full Hedgehog project — Nx,
 NestJS, Postgres, Docker, ts-rest, the phase discipline, and every gate
-still apply (all landed by `hedgehog-bootstrap-core`). What's cut is
+still apply (all landed by `hedgehog-bootstrap-full-stack-app-core`). What's cut is
 infra with no consumer, not the discipline itself.
 If a project's whole description has no persistent domain data and no
@@ -100,18 +100,18 @@ something with no domain module in it.
 ```
 apps/
-  web        (Next.js — UI only)                    core, landed by hedgehog-bootstrap-core
+  web        (Next.js — UI only)                    core, landed by hedgehog-bootstrap-full-stack-app-core
   mobile     (Expo — only if the Mobile add-on is on)
-  api        (NestJS — owns all domain logic + DB access)  core, landed by hedgehog-bootstrap-core
+  api        (NestJS — owns all domain logic + DB access)  core, landed by hedgehog-bootstrap-full-stack-app-core
   worker     (BullMQ consumers — only if the Queue add-on is on)
 packages/
-  db         (Drizzle schema + client)                core, landed by hedgehog-bootstrap-core
+  db         (Drizzle schema + client)                core, landed by hedgehog-bootstrap-full-stack-app-core
   contracts  (ts-rest + Zod contracts)
   hooks      (TanStack Query — shared web + mobile)
   jobs       (typed job registry / queue definitions — only if Queue is on)
   auth       (Better Auth config — only if Auth is on)
-  config     (locked ESLint/Prettier/tsconfig/env schema)  core, landed by hedgehog-bootstrap-core
+  config     (locked ESLint/Prettier/tsconfig/env schema)  core, landed by hedgehog-bootstrap-full-stack-app-core
   shared     (cross-cutting types + utils)
 docs/
@@ -144,7 +144,7 @@ recording which add-ons (Auth, Queue, Mobile) are on for this project. No
 scope boundary yet, or a `TODO.md` with no `## Add-ons` block: stop and
 point to `planner` rather than guessing which add-ons apply.
-Run `hedgehog-bootstrap-core` first, unconditionally, if it hasn't
+Run `hedgehog-bootstrap-full-stack-app-core` first, unconditionally, if it hasn't
 already landed core (check `TODO.md`'s Bootstrap section, or `nx.json`
 at the repo root). That skill has its own re-run guard and Docker check
 — don't duplicate those here.
@@ -167,11 +167,11 @@ pnpm add better-auth @thallesp/nestjs-better-auth
 Configure the Drizzle adapter against `packages/db`. Add
 `BETTER_AUTH_SECRET: z.string().min(32)` to `packages/config/env.schema.ts`
-now (it doesn't exist in the core schema `hedgehog-bootstrap-core`
+now (it doesn't exist in the core schema `hedgehog-bootstrap-full-stack-app-core`
 landed), and add a matching `BETTER_AUTH_SECRET=` line with a generated
 value to the root `.env.example` — a schema entry with no `.env.example`
 line reproduces the exact `loadEnv()` crash-on-boot that
-`hedgehog-bootstrap-core`'s `DATABASE_URL` entry exists to prevent, just
+`hedgehog-bootstrap-full-stack-app-core`'s `DATABASE_URL` entry exists to prevent, just
 for this var instead. Tag: `scope:auth`, `type:adapter`.
 Also wire the global auth guard on `apps/api`: `pnpm add
@@ -198,7 +198,7 @@ pnpm add bullmq ioredis
 ```
 Add a `redis` service to the root `docker-compose.yml`
-`hedgehog-bootstrap-core` landed (Postgres-only until now) and
+`hedgehog-bootstrap-full-stack-app-core` landed (Postgres-only until now) and
 `REDIS_URL: z.string().url()` to `packages/config/env.schema.ts` (it
 doesn't exist in the core schema), plus a matching `REDIS_URL=` line in
 the root `.env.example` pointing at that same `docker-compose.yml`
@@ -243,7 +243,7 @@ pnpm add react-native-reusables nativewind
 ```
 Configure NativeWind's theme (`tailwind.config.js` colors, light/dark) to
-match `apps/web`'s base theme (landed by `hedgehog-bootstrap-core`) — one
+match `apps/web`'s base theme (landed by `hedgehog-bootstrap-full-stack-app-core`) — one
 visual identity across platforms, set once here rather than drifting
 per-screen. Tag: `scope:mobile`.
@@ -265,14 +265,14 @@ other).
 ## Locked format/lint config
 One shared config, extended everywhere — landed by
-`hedgehog-bootstrap-core`, referenced (not re-created) by every add-on
+`hedgehog-bootstrap-full-stack-app-core`, referenced (not re-created) by every add-on
 step above:
 - `packages/config/eslint-base.js` — flat config, extended by every
   app/lib.
 - `packages/config/prettier.js` — the shared base, *without*
   `prettier-plugin-tailwindcss` (that's `apps/web`'s own config, already
-  wired by `hedgehog-bootstrap-core`).
+  wired by `hedgehog-bootstrap-full-stack-app-core`).
 A per-app override request signals to fix the base config at the source.
@@ -280,7 +280,7 @@ A per-app override request signals to fix the base config at the source.
 Update `TODO.md`: check off every add-on line now built or explicitly
 skipped (core's four lines are already checked by
-`hedgehog-bootstrap-core`). Leave Phase A/B sections as-is (per-module,
+`hedgehog-bootstrap-full-stack-app-core`). Leave Phase A/B sections as-is (per-module,
 filled in by `planner` during planning intake or when new scope enters play).
 Hand off to `hedgehog-loop` — from here, every domain module goes
 through Phase A steps 1–5(a) one at a time, gated by lefthook, each its
@@ -288,7 +288,7 @@ own commit.
 ## Constraints
-- Run `hedgehog-bootstrap-core` first, unconditionally, before any step
+- Run `hedgehog-bootstrap-full-stack-app-core` first, unconditionally, before any step
   in this file — never scaffold an add-on against a core that hasn't
   landed and verified clean.
 - Add-on steps (Auth, Queue, Mobile) run only if `TODO.md`'s `## Add-ons`
@@ -307,5 +307,5 @@ own commit.
   discipline as every other step in the discipline, even though this is
   infra rather than a domain module.
 - Never substitute a natively-installed Postgres or Redis, even to match
-  a contributor's existing local setup — see `hedgehog-bootstrap-core`'s
+  a contributor's existing local setup — see `hedgehog-bootstrap-full-stack-app-core`'s
   **Local infra: Docker, always**.

package/src/skills/{hedgehog-bootstrap-core → hedgehog-bootstrap-full-stack-app-core}/SKILL.md RENAMED Viewed

@@ -1,13 +1,13 @@
 ---
-name: hedgehog-bootstrap-core
-description: Use once, at the start of a new Hedgehog project, before hedgehog-bootstrap's add-on steps, to land the golden-core workspace (Nx, packages/config, packages/db, apps/api, apps/web, and every enforcement file) and verify it's green. Runs as the first move of the `bootstrap` agent, which `planner` invokes automatically after Confirm & Lock. No per-project decisions, no add-on awareness.
+name: hedgehog-bootstrap-full-stack-app-core
+description: Use once, at the start of a new Hedgehog project on the full-stack-app core, before hedgehog-bootstrap's add-on steps, to land the full-stack-app core workspace (Nx, packages/config, packages/db, apps/api, apps/web, and every enforcement file) and verify it's green. Runs as the first move of the `bootstrap` agent, which `planner` invokes automatically after Confirm & Lock. No per-project decisions, no add-on awareness.
 ---
-# Hedgehog Bootstrap — Core
+# Hedgehog Bootstrap — full-stack-app Core
 Lands the always-on core of a Hedgehog project — the same four pieces on
 every project, regardless of size or which add-ons are on — by copying a
-pre-built, pre-verified workspace (`src/golden-core/` in the Hedgehog
+pre-built, pre-verified workspace (`src/golden-cores/full-stack-app/` in the Hedgehog
 package) rather than generating it live: Nx workspace + enforcement
 config, `packages/db`, `apps/api`, `apps/web`. These pieces are
 deterministic — the same commands produce the same output on every
@@ -23,7 +23,7 @@ Hedgehog project.
 ## What lands
-Everything under `src/golden-core/` in the installed Hedgehog package,
+Everything under `src/golden-cores/full-stack-app/` in the installed Hedgehog package,
 copied to the repo root:
 - Root: `nx.json`, `pnpm-workspace.yaml`, `package.json` (with the
@@ -84,14 +84,14 @@ alike. No Docker: stop and point to installing Docker Desktop
 (macOS/Windows) or Docker Engine (Linux) rather than falling back to a
 natively-installed Postgres. See **Local infra: Docker, always** below.
-### 3. Land `src/golden-core/`
+### 3. Land `src/golden-cores/full-stack-app/`
 In the common case this is already done — `hedgehog init`'s installer
-copies `src/golden-core/` to the repo root at install time, the same way
+copies `src/golden-cores/full-stack-app/` to the repo root at install time, the same way
 it copies `src/agents` to `.claude/agents`. Check whether the core files
 are already present (same check as step 1). If they're missing —
 `hedgehog init` ran against an older package version, or the files were
-deleted — copy `src/golden-core/`'s contents to the repo root now as a
+deleted — copy `src/golden-cores/full-stack-app/`'s contents to the repo root now as a
 fallback. Either way, by the end of this step every file listed in "What
 lands" above should be on disk.
@@ -113,7 +113,7 @@ of one line here.
 `pnpm install` resolves against the committed `pnpm-lock.yaml` — this
 should be fast and produce no lockfile changes. A lockfile diff here
 means the shipped `pnpm-lock.yaml` doesn't match `package.json` — that's
-a packaging bug in `src/golden-core`, not something to patch locally
+a packaging bug in `src/golden-cores/full-stack-app`, not something to patch locally
 (see **If verification fails**, below).
 ### 5. Verify
@@ -150,11 +150,12 @@ The four core Bootstrap lines ship pre-checked in the `TODO.md` template.
 If step 3's fallback copy ran, check them now. Leave every add-on line
 (Auth/Queue/Mobile) untouched; `hedgehog-bootstrap` owns those.
-## Known issues baked into golden-core
+## Known issues baked into the full-stack-app core
 These are already fixed in the committed tree — listed here so anyone
-regenerating `src/golden-core` (see that skill's regeneration script)
-knows why the tree looks the way it does, and doesn't reintroduce the
+regenerating `src/golden-cores/full-stack-app` (see
+`scripts/regenerate-full-stack-app-core.sh`) knows why the tree looks the
+way it does, and doesn't reintroduce the
 bug by "cleaning up" what looks like an unnecessary pin or directive.
 - **`apps/web-e2e/tsconfig.json` needs an explicit `"types": ["node"]`.**
@@ -224,14 +225,14 @@ bug by "cleaning up" what looks like an unnecessary pin or directive.
 ## If verification fails
-A clean copy of `src/golden-core` that fails typecheck/lint/test or
+A clean copy of `src/golden-cores/full-stack-app` that fails typecheck/lint/test or
 needs a lockfile change means the shipped template itself is broken —
 not a per-project problem to hand-patch around. Stop and report exactly
 what failed (which target, which error). Fixing this means updating
-`src/golden-core` at its source (via
-`scripts/regenerate-golden-core.sh` in the Hedgehog repo itself) and
-shipping a new package version — never patch a consuming project's copy
-to route around a broken template and call core done.
+`src/golden-cores/full-stack-app` at its source (via
+`scripts/regenerate-full-stack-app-core.sh` in the Hedgehog repo itself)
+and shipping a new package version — never patch a consuming project's
+copy to route around a broken template and call core done.
 ## Local infra: Docker, always
@@ -253,7 +254,7 @@ not here.
   instead — this skill's whole point is being identical across every
   project.
 - Don't hand-edit any file this step lands to work around a verification
-  failure. Fix `src/golden-core` at the source instead (see **If
+  failure. Fix `src/golden-cores/full-stack-app` at the source instead (see **If
   verification fails**).
 - Don't add domain schema, contracts, or any `libs/<module>/*` content —
   that's Phase A, after every Bootstrap box (core and whichever add-ons

package/src/skills/hedgehog-bootstrap-landing-page-core/SKILL.md ADDED Viewed

@@ -0,0 +1,160 @@
+---
+name: hedgehog-bootstrap-landing-page-core
+description: Use once, at the start of a new Hedgehog project on the landing-page core, to land the pre-verified Astro + Tailwind workspace and verify it's green. Runs as the only move of the `bootstrap` agent on this core — there are no add-on steps, unlike full-stack-app. Invoked automatically by `planner` after Confirm & Lock.
+---
+# Hedgehog Bootstrap — landing-page Core
+Lands the whole of a `landing-page` project's workspace — there's no
+add-on layer to run after it, unlike `full-stack-app`'s
+`hedgehog-bootstrap` — by copying a pre-built, pre-verified workspace
+(`src/golden-cores/landing-page/` in the Hedgehog package) rather than
+generating it live: Astro workspace, Tailwind token-layer config, the
+library set this core is built on (GSAP, Lenis, SplitType, Paper.js).
+This piece is deterministic — the same commands produce the same output
+on every project — so the output is committed once, upstream, and copied
+here instead of re-derived by an agent on every run.
+This skill has no per-project decisions to make: no add-ons, no `TODO.md`
+dependency beyond checking its own Bootstrap line, nothing to ask.
+Landing-page's core is identical on every project running it.
+## What lands
+Everything under `src/golden-cores/landing-page/` in the installed
+Hedgehog package, copied to the repo root:
+- Root: `astro.config.mjs`, `package.json` (with the `dev` script —
+  `astro dev` — and every library in the stack pinned), `tsconfig.json`,
+  `eslint.config.mjs`, `.prettierrc.js`, `.gitignore`, `pnpm-lock.yaml`.
+- `tailwind.config.ts` — the token layer only: no component classes, no
+  plugin beyond the base. Ships with placeholder tokens (a neutral
+  starting palette, a system type stack, a 4px spacing unit) that
+  `landing-systems` overwrites at its own phase — this file existing and
+  being wired into the build is what core guarantees, not any specific
+  token values.
+- `src/pages/index.astro` — a minimal placeholder page (proves the build
+  pipeline works end to end), replaced by `landing-builder`'s own output
+  at the build phase.
+- `src/styles/global.css` — the Tailwind import and CSS custom-property
+  scaffold `landing-systems`'s token system writes into.
+- `src/sections/`, `src/motifs/` — empty, with a `.gitkeep`; real content
+  starts at the systems and build phases.
+`node_modules` is not part of the copy — `pnpm install` regenerates it
+from the committed `pnpm-lock.yaml`.
+## Steps
+### 1. Confirm this hasn't already run
+Check for `astro.config.mjs` at the repo root, or a prior
+`feat(landing): workspace` commit
+(`git log --grep="^feat(landing): workspace"`). Either means core already
+landed — stop, don't re-copy. If something about the landed core seems
+wrong, that's a Correction Protocol case (`hedgehog-landing-loop`), not a
+re-copy: patch the specific file at its source.
+### 2. Land `src/golden-cores/landing-page/`
+In the common case this is already done — `hedgehog init --core=landing-page`'s
+installer copies `src/golden-cores/landing-page/` to the repo root at
+install time, the same way it copies `src/agents` to `.claude/agents`.
+Check whether the core files are already present (same check as step 1).
+If they're missing — `hedgehog init` ran against an older package
+version, or the files were deleted — copy
+`src/golden-cores/landing-page/`'s contents to the repo root now as a
+fallback. Either way, by the end of this step every file listed in "What
+lands" above should be on disk.
+### 3. Install
+```bash
+pnpm install
+```
+Resolves against the committed `pnpm-lock.yaml` — this should be fast
+and produce no lockfile changes. A lockfile diff here means the shipped
+`pnpm-lock.yaml` doesn't match `package.json` — that's a packaging bug in
+`src/golden-cores/landing-page`, not something to patch locally (see **If
+verification fails**, below).
+### 4. Verify
+```bash
+pnpm astro check
+pnpm build
+```
+Both must be clean: no type errors from the first command, a successful
+build with no warnings from the second. This is the live check that
+proves core isn't correct by trusting the copy, but by actually running
+the same gate every phase in this core's loop runs.
+### 5. Commit
+```
+feat(landing): workspace
+```
+One commit for all of core, landed as a verified copy.
+### 6. `TODO.md`'s core line
+The Bootstrap line ships pre-checked in the `landing-page` `TODO.md`
+template. If step 2's fallback copy ran, check it now.
+## Known issues baked into the landing-page core
+These are already fixed in the committed tree — listed here so anyone
+regenerating `src/golden-cores/landing-page` (see
+`scripts/regenerate-landing-page-core.sh`) knows why the tree looks the
+way it does, and doesn't reintroduce the bug by "cleaning up" what looks
+like an unnecessary pin.
+- **`typescript` must stay pinned to the `^5` line, not `7.x`.**
+  `@astrojs/check` (which `astro check` calls into) relies on a
+  programmatic TypeScript API that the 7.x native compiler doesn't
+  expose yet — running `astro check` against TS 7 fails immediately with
+  "does not expose the programmatic API that `astro check` relies on"
+  (tracked at github.com/withastro/roadmap/discussions/1321). Re-check
+  this pin when bumping TypeScript; it may be resolved upstream by then.
+- **`create-astro`'s scaffold ships its own `AGENTS.md`/`CLAUDE.md`
+  symlink, `README.md`, and `pnpm-workspace.yaml`**, as if this were a
+  standalone repo rather than a tree that lands at a Hedgehog project's
+  root. All four are stripped before syncing — they'd otherwise collide
+  with (or silently shadow) the project's real root `CLAUDE.md` and
+  Hedgehog's own workspace conventions.
+- **MorphSVGPlugin ships inside the `gsap` package itself** — no
+  separate install, no Club GreenSock membership, no private registry.
+  GreenSock made every plugin free when GSAP joined Webflow in 2024.
+  Import it as `import { MorphSVGPlugin } from 'gsap/MorphSVGPlugin'`
+  directly from the `gsap` dependency already in `package.json`. Don't
+  reintroduce a separate paid-plugin workaround if this comes up again —
+  verify current licensing against gsap.com before assuming otherwise.
+## If verification fails
+A clean copy of `src/golden-cores/landing-page` that fails `astro check`
+or `pnpm build`, or needs a lockfile change, means the shipped template
+itself is broken — not a per-project problem to hand-patch around. Stop
+and report exactly what failed. Fixing this means updating
+`src/golden-cores/landing-page` at its source (via
+`scripts/regenerate-landing-page-core.sh` in the Hedgehog repo itself)
+and shipping a new package version — never patch a consuming project's
+copy to route around a broken template and call core done.
+## Constraints
+- Run once per project, as the `bootstrap` agent's only move on this
+  core — never invoked on its own by a user.
+- No add-on awareness, because this core has no add-ons. If a future
+  landing-page variation genuinely needs one (a CMS integration, a form
+  backend), that's a new core decision for `planner`'s Phase 0, not an
+  add-on bolted onto this one.
+- Don't hand-edit any file this step lands to work around a verification
+  failure. Fix `src/golden-cores/landing-page` at the source instead (see
+  **If verification fails**).
+- Don't write any Chain Method phase content (adjectives, tokens, motif,
+  sequence, or the built page) — that's `landing-strategist` through
+  `landing-builder`'s work, after this Bootstrap box is checked.