@se-studio/skills 1.5.6 → 1.5.8

package/CHANGELOG.md

@@ -1,5 +1,17 @@
 # @se-studio/skills
 
+## 1.5.8
+
+### Patch Changes
+
+- Add `site-workflows-stale-files-cleanup` skill and `references/stale-files-cleanup/` (checklist, false positives, monorepo/single-app layouts, Brightline case study) for repository hygiene audits on SE Studio marketing sites.
+
+## 1.5.7
+
+### Patch Changes
+
+- c29c4c8: Add `site-workflows-agent-session` skill and agent-session reference files for cross-repo work sessions, placement checklist, and parallel feature isolation.
+
 ## 1.5.6
 
 ### Patch Changes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@se-studio/skills",
-  "version": "1.5.6",
+  "version": "1.5.8",
   "description": "SE Studio agent skills for marketing site development with Contentful CMS",
   "repository": {
     "type": "git",

package/references/agent-session/customer-agents-block.md

@@ -0,0 +1,45 @@
+## Agent session workflow
+
+**Load skill `site-workflows-agent-session` at the start of every coding session.**
+
+Default mode for this repo: **site-first**.
+
+### Branch policy
+
+- Agents may commit and push **`develop`** and **`feature/*`** only.
+- **Never** push to `main`, `master`, or production — human-only.
+- Prefer **draft PRs** to `develop` over direct pushes when `gh` is available.
+
+### Core vs customer placement
+
+Before non-trivial code, run the placement checklist (in the skill). Summary:
+
+| Belongs in… | Examples |
+|-------------|----------|
+| **This repo** (`src/project/*`, `cms-edit/**`) | Brand components, styling, site routing, editor-pack |
+| **Customer shared package** (if monorepo) | Consent/analytics shared across sites in this customer |
+| **`se-core-product`** (`@se-studio/*`) | Fixes/features needed by 2+ sites, CMS infrastructure |
+
+If the checklist says **core**, stop and switch to core-first mode — do not patch `@se-studio` behaviour in this repo.
+
+### Core release order
+
+When work depends on a new `@se-studio/*` npm release:
+
+1. Release from `se-core-product` (`dev` → CI publish)
+2. Confirm version on npm
+3. `pnpm update @se-studio/<package>@<version> -r` in this repo
+4. Then push `develop`
+
+Never hand-edit `package.json` dependency versions.
+
+### Parallel features
+
+- One feature = one `feature/<scope>/<slug>` branch
+- Use a **git worktree** when multiple features touch this repo at once
+- CMS edits: `--session <feature-slug>` (isolate cms-edit sessions)
+- Track in-flight work: manifest at `~/source/se/se-core-product/work/active/<feature>.yaml` (or `work/active/` in this repo if core checkout unavailable)
+
+### Production handoff
+
+When ready for production, agents **stop** and deliver a handoff note — they do not merge to `main`. See skill Step 8.

package/references/agent-session/manifest.template.yaml

@@ -0,0 +1,32 @@
+# Copy to work/active/<feature>.yaml — one file per in-flight feature.
+# Canonical location: se-core-product/work/active/ (cross-repo visibility).
+
+feature: my-feature-slug
+mode: site-first # core-first | site-first
+project_key: om1
+primary_repo: ~/source/customers/om1/om1-website
+branch: feature/om1/my-feature-slug
+worktree: null # e.g. ~/source/worktrees/om1-my-feature-slug — required when parallel features share a repo
+integration_branch: develop
+
+related_repos:
+  - repo: se-core-product
+    path: ~/source/se/se-core-product
+    role: read-only # read-only | pending-extract | active
+
+placement:
+  decision: customer # core | customer | customer-shared | defer-extract
+  rationale: One-site hero layout tied to OM1 Figma
+  extract_to_core: null # pending | null
+  extract_rationale: null
+
+blocked_on: null # e.g. "@se-studio/core-ui@2.1.0"
+cms_session: null # set to feature slug when doing parallel CMS edits
+
+status: in_progress # in_progress | blocked | parked | ready_for_review
+started_at: 2026-07-05
+updated_at: 2026-07-05
+
+validation: []
+
+handoff: null

package/references/agent-session/projects.registry.json

@@ -0,0 +1,86 @@
+{
+  "manifestPath": "work/active/<feature>.yaml",
+  "integrationBranches": {
+    "core": "dev",
+    "customer": "develop"
+  },
+  "branchPattern": "feature/<scope>/<short-slug>",
+  "projects": [
+    {
+      "key": "se-core-product",
+      "displayName": "SE Core Product",
+      "path": "~/source/se/se-core-product",
+      "branch": "dev",
+      "type": "core",
+      "validate": "pnpm validate",
+      "exampleApps": [
+        "example-om1",
+        "example-se2026",
+        "example-brightline",
+        "example-brightlifekids",
+        "example-empty"
+      ]
+    },
+    {
+      "key": "se2026",
+      "displayName": "SE Studio Site",
+      "path": "~/source/se/se-website-2026",
+      "branch": "develop",
+      "type": "customer",
+      "contentfulSpaceId": "g0pw3n92bre6",
+      "hostedMcp": "cms-edit-se-website",
+      "validate": "pnpm check && pnpm type-check"
+    },
+    {
+      "key": "brightline",
+      "displayName": "Brightline Sites",
+      "path": "~/source/customers/brightline/brightline-sites",
+      "branch": "develop",
+      "type": "customer-monorepo",
+      "sharedPackage": "@brightline/shared",
+      "contentfulSpaceIds": ["96gdpqkm7elu", "c27ds9epot4n"],
+      "hostedMcp": "cms-edit-brightline",
+      "validate": "pnpm -r validate"
+    },
+    {
+      "key": "om1",
+      "displayName": "OM1 Website",
+      "path": "~/source/customers/om1/om1-website",
+      "branch": "develop",
+      "type": "customer",
+      "contentfulSpaceId": "ddhe5ahaolzf",
+      "hostedMcp": "cms-edit-om1",
+      "validate": "pnpm check && pnpm type-check && pnpm validate:routes"
+    },
+    {
+      "key": "pointme",
+      "displayName": "PointMe Marketing Site",
+      "path": "~/source/customers/pointme/develop-marketing-site",
+      "branch": "develop",
+      "type": "customer",
+      "contentfulSpaceId": "alwdzgjlz5qv",
+      "contentfulEnvironment": "marketing-master-2025-04-15",
+      "validate": "pnpm check && pnpm type-check"
+    },
+    {
+      "key": "pedestal",
+      "displayName": "Pedestal Sites",
+      "path": "~/source/customers/pedestal/pedestal-sites",
+      "branch": "develop",
+      "type": "customer-monorepo",
+      "sharedPackage": "@pedestal/site-common",
+      "contentfulSpaceIds": ["h4s3ip99qawo", "fea4lj2cdgl5"],
+      "hostedMcp": ["cms-edit-pedestal", "cms-edit-headwater"],
+      "validate": "pnpm -r validate"
+    },
+    {
+      "key": "hsd-extended-port",
+      "displayName": "HopSkipDrive Extended Port",
+      "path": "~/source/customers/hopskipdrive/hsd-extended-port",
+      "branch": "extended-port",
+      "type": "customer",
+      "wip": true,
+      "validate": "pnpm validate"
+    }
+  ]
+}

package/references/deps-update/projects.registry.json

@@ -66,6 +66,17 @@
       "validate": "pnpm -r validate",
       "workspace": true,
       "hasPinOverrides": false
+    },
+    {
+      "key": "hsd-extended-port",
+      "displayName": "HopSkipDrive Extended Port",
+      "path": "~/source/customers/hopskipdrive/hsd-extended-port",
+      "branch": "extended-port",
+      "wip": true,
+      "wipNote": "Parity port from legacy GraphQL/Netlify site onto @se-studio packages. Work on extended-port only — not develop/production. Defer routine deps bumps until parity snags are under control unless explicitly requested.",
+      "validate": "pnpm validate",
+      "workspace": false,
+      "hasPinOverrides": false
     }
   ]
 }

package/references/stale-files-cleanup/BRIGHTLINE_RUNBOOK.md

@@ -0,0 +1,90 @@
+# Case study — Brightline Sites stale-files cleanup (Jul 2026)
+
+Reference implementation for `site-workflows-stale-files-cleanup`. Repo: `brightline-sites` on `develop`.
+
+---
+
+## User choices
+
+| Decision | Choice |
+|----------|--------|
+| Doc disposition | Hard delete (git history as backup) |
+| BLK Contentful migration | Complete — migration scripts safe to remove |
+| Dependabot | Investigate only; fix when asked separately |
+
+---
+
+## Commits
+
+| SHA | Summary | Scale |
+|-----|---------|-------|
+| `783a329` | Remove stale scripts, docs, migration tooling | ~58 files, ~57k lines |
+| `558fc56` | Fix A/B test, cms-guidelines paths, `.env.example` | 11 files |
+| `e09da45` | Remove orphan `xlsx` devDependency | 2 files; cleared 4 Dependabot alerts |
+
+---
+
+## Removed categories (783a329)
+
+**Broken npm scripts** (missing targets):
+
+- `docs:screenshots`, `docs:pdf` (Brightline)
+- `setup:footer-nav`, `audit:site` (BLK)
+
+**Orphan scripts:**
+
+- `update-leadership-linkedin.mjs`, Vercel env ops scripts, media workbook builder, pilot batch scripts, `run-cms-screenshots-all.mjs` (both apps), unreferenced schema patch scripts
+
+**BLK migration (confirmed complete):**
+
+- `migrate-blk.ts`, `blk-master-schema.json`, `enable-locales-migration.js`
+
+**Stale docs:**
+
+- `REPO_ORIENTATION.md`, app `AGENTS.md`, "Moved" stubs, Mar 2026 audit reports, migration runbooks, schema audit snapshots, dated xlsx/json deliverables
+
+**Infra:**
+
+- Per-app `.husky/` + `husky` devDependencies
+
+---
+
+## Follow-up fixes (558fc56)
+
+- `ab-test-page.test.ts` — assert against active `home-parents` test in `abTests.ts`, not removed Long Island test
+- cms-guidelines: `example-brightline` → `brightline` filter + `apps/brightline-website` paths
+- `.env.example`: `CTM_ENABLED`, `STICKY_PHONE_ENABLED` (BL); `PREVIEW_SECRET` (BLK)
+
+---
+
+## Dependency hygiene (e09da45)
+
+- `xlsx@0.18.5` root devDep — zero imports after workbook script removal
+- `pnpm why xlsx` confirmed orphan; removed from `package.json` + lockfile
+
+---
+
+## Reference updates required
+
+Deleting without grep caught stragglers in:
+
+- `ACTION-PLAN.md`, `VERCEL-ENV-INVENTORY.md` (deleted script names)
+- `docs/media/CUSTOMER-REVIEW-BRIEF.md`, `BLK-PILOT-REVIEW-PACKET.md`
+- `MKTG-4804-fbp-explanation.md` (superseded Formstack audit link)
+- `AGENTS.md` (non-existent `deploy-cms-edit-host.sh`)
+
+---
+
+## Kept intentionally
+
+See [`FALSE_POSITIVES.md`](./FALSE_POSITIVES.md) — cms-editor, editor-pack, env-inventory, Formstack playbooks, wired schema scripts, screaming-frog configs.
+
+---
+
+## Lessons for future runs
+
+1. **Plan mode + AskQuestion** before bulk doc deletes
+2. **Grep after each phase** — playbook and action-plan refs linger
+3. **Revert validate side-effects** — `validate:routes` regenerated `abTests.ts`
+4. **Doc drift** can remain after file deletes (BLK README "standalone app" wording)
+5. **Dependabot investigate** separate from cleanup unless user conflates them

package/references/stale-files-cleanup/CHECKLIST.md

@@ -0,0 +1,145 @@
+# Stale files cleanup — discovery checklist
+
+Run these checks in parallel at the start of every hygiene audit. Adapt paths for monorepo vs single-app (see `MONOREPO.md` / `SINGLE_APP.md`).
+
+---
+
+## 1. Broken npm scripts
+
+For each `package.json` with a `scripts` section (root + `apps/*/` in monorepos):
+
+1. Extract script commands that invoke local files (`tsx scripts/…`, `node scripts/…`, `bash scripts/…`).
+2. Verify each target file exists on disk.
+3. Flag scripts pointing at missing files — **High** risk.
+
+```bash
+# Quick scan: list script files referenced from package.json
+rg '"(tsx|node|bash) scripts/' package.json apps/*/package.json
+```
+
+---
+
+## 2. Orphan scripts
+
+List runnable files under:
+
+- `scripts/` (repo root)
+- `apps/*/scripts/`
+- `docs/*/scripts/`
+
+For each file not referenced in any `package.json` script:
+
+```bash
+rg -l '<basename>' --glob '!node_modules' --glob '!.next'
+```
+
+Zero inbound refs → candidate for removal (**Low**), unless cited as an active re-run playbook in docs.
+
+---
+
+## 3. Stale documentation
+
+Search for:
+
+| Pattern | Typical meaning |
+|---------|-----------------|
+| `REPO_ORIENTATION`, `implementation-checklist-*` | Pre-monorepo or historical checklists |
+| `# Moved`, `Moved to monorepo` | Stub redirects — safe to delete if canonical doc exists |
+| `*-REPORT.md`, `*-audit.md` (dated) | Point-in-time reports |
+| `example-brightline`, `apps/example-*` | Legacy template paths — update, not always delete |
+| `deploy-cms-edit-host.sh` | Often referenced in AGENTS.md but file never existed |
+
+```bash
+rg -l 'example-brightline|apps/example-|REPO_ORIENTATION|# Moved' docs apps
+```
+
+---
+
+## 4. Audit artifacts and deliverables
+
+| Pattern | Notes |
+|---------|-------|
+| `docs/media-review-*.xlsx`, `media-review-*.json` | Regenerable via media-review playbooks |
+| `docs/schema/audit/` | Point-in-time schema audit outputs |
+| `docs/archive/` | Superseded snapshots — ask disposition |
+| `*.xlsx` under `docs/` | Source spreadsheets when templates exist elsewhere |
+
+Cross-check `.gitignore`: gitignored generated reports under `docs/seo/*-screaming-frog-*` are **local only** — do not treat as tracked stale files.
+
+```bash
+git ls-files 'docs/**/*.xlsx' 'docs/**/*-audit*' 'docs/archive/'
+```
+
+---
+
+## 5. Duplicate infrastructure (monorepo)
+
+```bash
+ls -la .husky/pre-commit apps/*/.husky/pre-commit 2>/dev/null
+rg '"husky"' package.json apps/*/package.json
+```
+
+Flag when root hook runs typecheck but app hooks only run `lint-staged`.
+
+---
+
+## 6. Orphan npm dependencies
+
+Root and app `devDependencies` with no imports:
+
+```bash
+# For each suspicious package name from package.json:
+pnpm why <package>
+rg "from '<package>'|require\\('<package>'\\)|import.*'<package>'" . \
+  --glob '!node_modules' --glob '!pnpm-lock.yaml'
+```
+
+Common orphans after script removal: `xlsx`, one-off CLI helpers.
+
+---
+
+## 7. Env template drift
+
+Compare README tables and `docs/VERCEL-ENV-VARS.md` against `.env.example` (root or per-app):
+
+```bash
+rg '^\| `[A-Z_]+`' apps/*/README.md docs/VERCEL-ENV-VARS.md
+rg '^[A-Z_]+=' apps/*/.env.example .env.example 2>/dev/null
+```
+
+Flag vars documented for humans but missing from `.env.example`.
+
+---
+
+## 8. Fragile tests tied to generated CMS state
+
+After cleanup touching A/B tests or generated files:
+
+- `src/generated/abTests.ts` — regenerated on `prebuild` / `generate:ab-tests`
+- Tests importing `generatedTestsByPath` must assert against **current** CMS entries, not removed page tests
+
+```bash
+pnpm --filter <app> test
+```
+
+Revert unrelated codegen diffs before commit (`git diff src/generated/`).
+
+---
+
+## 9. Untracked files
+
+```bash
+git status --short
+```
+
+Orphan untracked audits (e.g. `docs/*-setup-audit.md`) — ask commit vs delete.
+
+---
+
+## Output format
+
+Present findings as a table:
+
+| Path | Why stale | Evidence | Risk | Proposed action |
+
+Then proceed to user confirmation before any `git rm`.

package/references/stale-files-cleanup/FALSE_POSITIVES.md

@@ -0,0 +1,88 @@
+# Stale files cleanup — false positives (do not delete)
+
+Agents routinely mistake these for clutter. **Keep** unless the user explicitly requests removal.
+
+---
+
+## CMS editor and hosted MCP
+
+| Path | Why keep |
+|------|----------|
+| `docs/cms-editor/**` | Source playbooks for `cms-edit editor-pack generate` |
+| `cms-edit/<site>/editor-pack/**` | Committed MCP resources deployed via git push |
+| `cms-edit/host/` staging (gitignored `.env.*`) | Local cms-edit host dev |
+
+Overlap between `docs/cms-editor` and `editor-pack` is pipeline duplication, not accidental redundancy.
+
+---
+
+## Active operations documentation
+
+| Path | Why keep |
+|------|----------|
+| `docs/STATUS.md`, `docs/ACTION-PLAN.md` | Live workload docs (customer monorepos) |
+| `docs/env-inventory/`, `docs/VERCEL-ENV-*.md` | Env documentation pipeline |
+| `docs/PAGE_VARIANTS_AND_TESTS.md` | A/B test runbooks |
+| `docs/media/*.md` (briefs, not dated xlsx) | Active media-review workflow |
+
+---
+
+## Schema and SEO tooling (wired)
+
+| Path | Why keep |
+|------|----------|
+| `docs/schema/templates/` | Mustache templates for schema.org |
+| `docs/schema/page-inventory.json`, `PAGE-INVENTORY.md` | Referenced by schema recommendations |
+| `docs/schema/scripts/validate-json-ld.mjs` | Wired in root `schema:validate` |
+| `docs/schema/scripts/audit-localhost-schema.mjs` | Wired in `schema:audit:localhost*` |
+| `apps/*/seo/screaming-frog.json` | Crawl manifest config (not generated crawl reports) |
+
+---
+
+## Re-run playbooks and audit baselines
+
+| Path | Why keep |
+|------|----------|
+| `apps/*/scripts/formstack-spike.ts` (+ paired embed `.js`) | Cited by Formstack audit docs for re-runs |
+| `packages/*/docs/*-audit.md` (current, not superseded) | Active audit baselines |
+| `docs/alt-drafts/*.json` | Active pilot content batches |
+
+---
+
+## Agent skills and references
+
+| Path | Why keep |
+|------|----------|
+| `.agents/skills/`, `.cursor/skills/` (symlinks) | Synced from `@se-studio/skills` / `skills-npm` |
+| `.agents/references/` | Support docs for skills |
+| Customer-specific skills (e.g. `brightline-status-refresh`) | Site-local workflows |
+
+---
+
+## CI and deployment config
+
+| Path | Why keep |
+|------|----------|
+| `.github/workflows/*.yml` | Active CI (validate, deployment-smoke) |
+| `apps/*/scripts/vercel-deployment-smoke-check.json` | Vercel Deployment Checks registration |
+| Root `cms-edit:deploy:*` scripts | Emergency manual deploy (discouraged but intentional) |
+
+---
+
+## Generated outputs (regenerate, do not delete source)
+
+| Path | Notes |
+|------|-------|
+| `src/generated/abTests.ts` | CMS-generated — update tests, do not hand-delete |
+| `src/generated/cms-discovery/` | Regenerated by codegen scripts |
+| `docs/cms-guidelines/COMPONENT_GUIDELINES_FOR_LLM.md` | Merged output — regenerate via merge script |
+
+---
+
+## Package names vs folder names
+
+| Pattern | Notes |
+|---------|-------|
+| `example-brightlifekids` filter name | May differ from `apps/brightlife-kids-website/` — intentional for `pnpm --filter`; update **docs**, do not rename package without user request |
+
+When in doubt, grep for inbound references before proposing deletion.

package/references/stale-files-cleanup/MONOREPO.md

@@ -0,0 +1,85 @@
+# Stale files cleanup — monorepo layout
+
+For repos like `brightline-sites` with multiple apps under `apps/` and shared `packages/`.
+
+---
+
+## Detection
+
+| Signal | Monorepo |
+|--------|----------|
+| Root `pnpm-workspace.yaml` | Yes |
+| `apps/*/` with separate `package.json` | Yes |
+| Root `AGENTS.md` + optional per-app docs | Common |
+
+---
+
+## package.json scripts
+
+Audit **both**:
+
+- Root `package.json` — monorepo-wide (`validate`, `cms-edit:*`, `schema:*`)
+- Each `apps/<site>/package.json` — app dev/build/test scripts
+
+Broken script entries in **either** file fail when invoked from that package context.
+
+---
+
+## Husky duplication
+
+Canonical pattern (Brightline):
+
+- **Root** `.husky/pre-commit` → `lint-staged` + `scripts/pre-commit-typecheck.sh`
+- **App** `.husky/pre-commit` → only `lint-staged` (legacy)
+
+Cleanup: remove `apps/*/.husky/` and `husky` from app `devDependencies` when root `prepare` owns hooks.
+
+---
+
+## AGENTS.md
+
+| File | Role |
+|------|------|
+| Root `AGENTS.md` | Canonical agent rules |
+| `apps/*/AGENTS.md` | Often generic template leftovers — candidate for deletion if root doc exists |
+
+---
+
+## Filter names vs directory names
+
+| Folder | Package name (filter) |
+|--------|----------------------|
+| `apps/brightline-website` | `brightline` |
+| `apps/brightlife-kids-website` | `example-brightlifekids` |
+
+Docs may still say `example-brightline` or `apps/example-brightline` — update paths to real folder names and correct `pnpm --filter` names.
+
+---
+
+## Shared packages
+
+`packages/<shared>/` — do not delete shared docs/scripts referenced by both apps. Audit imports from apps before removing shared tooling.
+
+---
+
+## cms-edit multi-site
+
+| Path | Site |
+|------|------|
+| `cms-edit/brightline/project.json` | Brightline |
+| `cms-edit/brightlifekids/project.json` | BrightLife Kids |
+| `docs/cms-editor/<site>/` | Playbook source per site |
+
+Never delete one site's editor-pack thinking the other is redundant.
+
+---
+
+## Validate command
+
+Typically root:
+
+```bash
+pnpm validate
+```
+
+Runs `pnpm -r validate` across workspace packages. Pre-commit typecheck may only touch affected apps when paths are staged.

package/references/stale-files-cleanup/SINGLE_APP.md

@@ -0,0 +1,66 @@
+# Stale files cleanup — single-app layout
+
+For standalone SE Studio customer sites (one Next.js app at repo root or under a single `apps/` entry).
+
+---
+
+## Detection
+
+| Signal | Single-app |
+|--------|------------|
+| One primary `package.json` for the site | Yes |
+| No `apps/` sibling sites | Typical |
+| `cms-edit/project.json` at `cms-edit/` (not `cms-edit/<site>/`) | Common |
+
+---
+
+## Script locations
+
+| Location | Scope |
+|----------|-------|
+| `scripts/` | App tooling |
+| `docs/schema/scripts/` | Schema validation (if present) |
+
+Same orphan/broken-script rules as monorepos — only one `package.json` to audit.
+
+---
+
+## Husky
+
+Single `.husky/pre-commit` at repo root. No app-level duplicate to remove.
+
+---
+
+## Documentation paths
+
+| Path | Notes |
+|------|-------|
+| `docs/cms-guidelines/` | Per-component guidelines |
+| `docs/cms-editor/` | Editor playbooks (if hosted MCP enabled) |
+| `REPO_ORIENTATION.md` | Sometimes accurate — verify against current layout before deleting |
+
+Legacy `example-*` naming is less common in mature single-app repos but may persist in cms-guidelines from template copy.
+
+---
+
+## cms-edit
+
+| Path | Role |
+|------|------|
+| `cms-edit/project.json` | Project config |
+| `cms-edit/editor-pack/` | Generated MCP pack |
+| `docs/cms-editor/` | Playbook source |
+
+See [`FALSE_POSITIVES.md`](./FALSE_POSITIVES.md).
+
+---
+
+## Validate
+
+Usually from repo root:
+
+```bash
+pnpm validate
+```
+
+Or `pnpm check && pnpm type-check` per project `package.json`.

package/skills/se-marketing-sites-smoke-test-setup/SKILL.md

@@ -7,7 +7,7 @@ description: "Set up or regenerate smoke.cases.json for local smoke tests from t
 
 Local smoke tests use curated HTTP cases in **`smoke.cases.json`**. Optionally enable **`cmsIntegrity`** for a local-only Contentful article-link check (no `cms-server` import in smoke scripts).
 
-Requires `@se-studio/site-check` **^2.6.1** when using `cmsIntegrity` or `pnpm smoke-test` with integrity enabled; **2.1.2+** for cache log audit; **2.0.0+** for HTTP-only static smoke.
+Requires `@se-studio/site-check` **^2.9.0** when using `discovery` endpoint checks; **^2.6.1** when using `cmsIntegrity` or `pnpm smoke-test` with integrity enabled; **2.1.2+** for cache log audit; **2.0.0+** for HTTP-only static smoke.
 
 Preview / `DRAFT_ONLY` Contentful access in local dev is expected and not a smoke failure. **Deployment / live smoke stays HTTP-only** — do not enable `cmsIntegrity` on Vercel deployment checks.
 
@@ -204,6 +204,12 @@ curl -sI "http://localhost:<port>/some-path.md"
 {
   "siteName": "my-app",
   "port": 3012,
+  "discovery": {
+    "llmsTxt": true,
+    "markdownIndexTxt": true,
+    "cmsTxt": true,
+    "siteInfoMd": true
+  },
   "cases": [
     { "category": "home", "label": "Home", "path": "/", "expectMarkdown": true },
     { "category": "page", "label": "About", "path": "/about/", "expectMarkdown": true },
@@ -218,6 +224,19 @@ curl -sI "http://localhost:<port>/some-path.md"
 }
 ```
 
+**Discovery endpoints** (`discovery` block) — requires `@se-studio/site-check@^2.9.0`:
+
+| Path | Flag | Checks when `true` |
+|------|------|-------------------|
+| `/llms.txt` | `llmsTxt` | 200, `text/plain`, llmstxt.org structure, spot-check Key pages `.md` links |
+| `/markdown-index.txt` | `markdownIndexTxt` | 200, same-origin `.md` URL list |
+| `/cms.txt` | `cmsTxt` | 200, `text/markdown`, mentions llms + markdown-index |
+| `/site-info.md` | `siteInfoMd` | 200, `text/markdown`, title + minimum body |
+
+Omit a key or set `true` to require the endpoint. Set `false` to skip (not a failure). **PointMe:** set all four to `false` until CloudFront routes these paths to Vercel.
+
+Add `/llms.txt`, `/markdown-index.txt`, and `/site-info.md` to `route-build-policy.json` → `mustBeSsgOrStatic` (commit beside `smoke.cases.json`).
+
 `expectHtmlStatus` requires `@se-studio/site-check@^2.7.2`. Omit for normal 2xx HTML checks.
 
 Optional `cmsIntegrity` (local only — see section below):

package/skills/site-workflows-agent-session/SKILL.md

@@ -0,0 +1,279 @@
+---
+name: site-workflows-agent-session
+description: "Start and manage agent work sessions across se-core-product and customer sites. Declares work mode, feature branch, placement (core vs customer), parallel isolation, and production handoff. Load at the beginning of every coding session."
+---
+
+# Agent session workflow
+
+Orchestrates **where** to work, **where code belongs**, and **how to isolate parallel features**. Human merges to `main` / production — agents stop at handoff.
+
+**Registry:** [`packages/skills/references/agent-session/projects.registry.json`](../../references/agent-session/projects.registry.json) — repo paths, integration branches, hosted MCP keys.
+
+**Manifest template:** [`packages/skills/references/agent-session/manifest.template.yaml`](../../references/agent-session/manifest.template.yaml)
+
+**Human guide:** `docs/WORKFLOW.md` in se-core-product.
+
+---
+
+## When to load this skill
+
+Load **at the start of every coding session** — before reading code or making edits.
+
+Triggers:
+
+- User pastes a session opener (`Mode: site-first`, `Feature: …`)
+- User asks to work on a customer site or core package
+- User starts parallel work on another feature (new manifest, new branch)
+- User asks "where should this live?" (run placement checklist)
+
+---
+
+## Step 1 — Resolve session context
+
+Collect or infer:
+
+| Field | Required | Notes |
+|-------|----------|-------|
+| `mode` | Yes | `core-first` or `site-first` |
+| `feature` | Yes | Short slug, kebab-case (e.g. `om1-hero-redesign`) |
+| `project_key` | Yes | From registry (`om1`, `se-core-product`, `pedestal`, …) |
+| `primary_repo` | Yes | Absolute path from registry |
+| `branch` | Yes | `feature/<scope>/<slug>` — see naming below |
+| `worktree` | Optional | Separate checkout path when parallel features share a repo |
+
+**Default mode if unclear:** ask once. Site-specific UI/content → `site-first`. Package/framework/multi-site → `core-first`.
+
+**Branch naming:**
+
+```
+feature/<scope>/<short-slug>
+```
+
+| Scope | Example |
+|-------|---------|
+| Core work | `feature/core/search-webhook-fix` |
+| Customer site | `feature/om1/hero-redesign` |
+| Customer monorepo shared | `feature/brightline/consent-v2` |
+
+Integration branches (agents push feature branches here via PR or merge — **never `main`**):
+
+| Repo type | Integration branch |
+|-----------|-------------------|
+| `se-core-product` | `dev` |
+| Customer sites | `develop` (or registry override, e.g. `extended-port`) |
+
+---
+
+## Step 2 — Write or update manifest
+
+Path in **se-core-product** (canonical ledger for cross-repo visibility):
+
+```
+work/active/<feature>.yaml
+```
+
+Copy from `manifest.template.yaml`, fill all fields, set `status: in_progress`, `started_at` to today (ISO date).
+
+If the user works only in a customer repo with no core checkout, still create/update the manifest in se-core-product when that repo is available; otherwise create `work/active/<feature>.yaml` in the customer repo and note `manifest_location: customer` in the file.
+
+**One feature = one manifest.** Do not append unrelated work to an existing manifest.
+
+---
+
+## Step 3 — Placement checklist (before non-trivial code)
+
+Run before implementing anything beyond a one-line fix. Record results in manifest `placement:`.
+
+| Question | If yes → lean |
+|----------|----------------|
+| Will **2+ sites** need this within ~6 months? | **core** (`packages/*`) |
+| Is it CMS infrastructure (converter, shared renderer, cms-edit, search webhook)? | **core** |
+| Is it tied to **one brand** (Figma, copy, colours, one-off layout)? | **customer** (`src/project/*`) |
+| Shared only within **one customer monorepo** (e.g. `@brightline/shared`)? | **customer-shared** |
+| Bug in published `@se-studio/*` behaviour? | **core** — never fork in customer |
+
+**Outcomes** — set `placement.decision`:
+
+| Decision | Action |
+|----------|--------|
+| `core` | Edit `se-core-product` only; changeset before push to `dev`; customer waits for npm |
+| `customer` | Edit customer repo only; do not touch core |
+| `customer-shared` | Edit customer's shared package; not `@se-studio/*` |
+| `defer-extract` | Implement in customer now; set `extract_to_core: pending` + `extract_rationale` |
+
+**Site-first guard:** If checklist says `core` but mode is `site-first`, **stop** and ask whether to switch mode or record `defer-extract`.
+
+**Core-first guard:** If checklist says `customer`, implement in customer repo (read-only probe in core example apps only if useful).
+
+---
+
+## Step 4 — Git isolation
+
+### Single feature in repo
+
+```bash
+cd <primary_repo>
+git fetch origin
+git checkout -b <branch> origin/<integration-branch>
+```
+
+### Parallel features in same repo
+
+Use a **git worktree** per feature:
+
+```bash
+git worktree add <worktree-path> -b <branch> origin/<integration-branch>
+```
+
+Record `worktree` in manifest. Do not commit unrelated features on the same branch.
+
+### CMS parallel sessions
+
+When editing Contentful in parallel on the same space, use distinct cms-edit sessions:
+
+```bash
+--session <feature-slug>
+# or CONTENTFUL_CMS_SESSION=<feature-slug>
+```
+
+Record `cms_session: <feature-slug>` in manifest when doing CMS work.
+
+---
+
+## Step 5 — Work execution rules
+
+### core-first
+
+- Primary edits: `packages/*`, optionally `apps/example-*` to validate
+- Compare customer implementations **read-only** unless user approves commits there
+- Release train before customer push (see `AGENTS.md` **Client repos — wait for core**)
+
+### site-first
+
+- Primary edits: customer `src/project/*`, `cms-edit/**`, site config
+- **Do not** edit `se-core-product` unless placement is `core` and user approves mode switch
+- Consume `@se-studio/*` from npm — not monorepo workspace links
+
+### Blocked work
+
+If manifest has `blocked_on: "@se-studio/foo@1.2.3"`, do not push customer `develop` until npm publish is confirmed. Update manifest when unblocked.
+
+---
+
+## Step 6 — Validate before push
+
+Minimum per repo type (see registry `validate` for full command):
+
+| Repo | Typical |
+|------|---------|
+| se-core-product | `pnpm validate` or targeted `pnpm type-check` + tests |
+| Customer | registry `validate` field |
+
+Record commands run in manifest `validation:` before push.
+
+---
+
+## Step 7 — Push and PR policy
+
+Agents may push to:
+
+- `dev` / `develop` (via feature branch merge or direct if user prefers)
+- `feature/*` branches
+
+Agents must **never** push to `main`, `master`, or production branches.
+
+**Preferred:** open a **draft PR** targeting the integration branch:
+
+```bash
+gh pr create --base <integration-branch> --head <branch> --draft --title "<feature>: <summary>"
+```
+
+If `gh` is unavailable or user prefers direct push, push `feature/*` and note in handoff.
+
+---
+
+## Step 8 — Handoff (production-ready)
+
+When work is ready for human review / production promotion, **stop** — do not merge to `main`.
+
+1. Set manifest `status: ready_for_review`
+2. Deliver handoff using template below
+3. If core release was part of the work, list published package versions needed for customer bump
+
+### Handoff template
+
+```markdown
+## Handoff: <feature>
+
+**Mode:** <core-first | site-first>
+**Manifest:** work/active/<feature>.yaml
+
+### Repos and branches
+- <repo>: `<branch>` → merge to `<integration-branch>`
+
+### Placement
+- Decision: <core | customer | customer-shared | defer-extract>
+- Core release required: <yes — packages + versions | no>
+
+### Changes
+- <bullet summary>
+
+### Validation
+- <commands run>
+
+### Merge order (if multi-repo)
+1. <core PR / npm publish>
+2. <customer pnpm update @se-studio/...>
+3. <customer PR>
+
+### Production
+Ready for you to merge to `main` / promote Vercel. Agent will not push production.
+```
+
+---
+
+## Step 9 — Complete or park
+
+| Outcome | Manifest update |
+|---------|-----------------|
+| Merged / done | Move to `work/completed/<feature>.yaml` or delete from `work/active/` |
+| Blocked | `status: blocked`, set `blocked_on` |
+| Parked | `status: parked`, add `parked_reason` |
+
+Remove worktree when done:
+
+```bash
+git worktree remove <worktree-path>
+```
+
+---
+
+## Session opener (user control surface)
+
+User can paste:
+
+```
+Load skill: site-workflows-agent-session
+Mode: site-first
+Project: om1
+Feature: hero-redesign
+Branch: feature/om1/hero-redesign
+```
+
+Agent must load this skill, write manifest, run placement checklist, confirm branch/worktree, then proceed.
+
+---
+
+## Quick reference — project keys
+
+| key | Integration branch | Type |
+|-----|-------------------|------|
+| `se-core-product` | `dev` | core monorepo |
+| `se2026` | `develop` | customer |
+| `brightline` | `develop` | customer monorepo |
+| `om1` | `develop` | customer |
+| `pointme` | `develop` | customer |
+| `pedestal` | `develop` | customer monorepo |
+| `hsd-extended-port` | `extended-port` | customer (WIP) |
+
+Full paths and MCP keys: `projects.registry.json`.

package/skills/site-workflows-deps-update/SKILL.md

@@ -11,7 +11,31 @@ Update npm dependencies to **latest** in se-core-product and consumer repos that
 
 **Default:** Process **one repo per invocation**. At the end, summarize changes and offer the next project.
 
-**Never:** push to `main`/`master`; bump Next to 16; bump Node to 25+; use `pnpm patch` / `patchedDependencies` / `patches/`; bypass or remove `minimumReleaseAge`.
+**Never:** push to `main`/`master`; bump Next to 16; bump Node to 25+; use `pnpm patch` / `patchedDependencies` / `patches/`; bypass or remove `minimumReleaseAge`; **hand-edit `package.json` dependency versions** (use `pnpm update` instead).
+
+---
+
+## Bumping packages (all repos — agents must follow)
+
+**Do not** edit `package.json` version strings by hand. Always run `pnpm update` from the repo root so `pnpm-lock.yaml` stays aligned.
+
+```bash
+# One package after a core npm release
+pnpm update @se-studio/contentful-rest-api@<version> -r
+
+# Several @se-studio packages
+pnpm update -r @se-studio/contentful-rest-api @se-studio/core-ui
+```
+
+**`pnpm-workspace.yaml` overrides:** many customer repos pin packages under `overrides` (e.g. Point.me: `@se-studio/contentful-rest-api`, `mapbox-gl`). `pnpm update` does **not** update those lines. After updating a pinned package, set the matching override to the same range or `pnpm install --frozen-lockfile` fails.
+
+**cms-edit host repos** (`cms-edit/host` in `pnpm-workspace.yaml`): Vercel install is:
+
+```bash
+pnpm install --frozen-lockfile --config.node-linker=hoisted
+```
+
+Run that locally **before push** whenever `package.json`, lockfile, or overrides change. A mismatch surfaces as `ERR_PNPM_OUTDATED_LOCKFILE` (manifest vs lockfile specifiers).
 
 ---
 
@@ -25,9 +49,12 @@ Update npm dependencies to **latest** in se-core-product and consumer repos that
 | `om1` | OM1 Website | `develop` |
 | `pointme` | PointMe Marketing Site | `develop` |
 | `pedestal` | Pedestal Sites | `develop` |
+| `hsd-extended-port` | HopSkipDrive Extended Port **(WIP)** | `extended-port` |
 
 User may name a key (`update deps in om1`) or ask to run through all projects sequentially.
 
+**WIP:** `hsd-extended-port` is an active parity port — branch `extended-port`, not `develop`. Prefer standards alignment and targeted `@se-studio/*` catch-up over full `pnpm update -r --latest` until the snag list is stable.
+
 ---
 
 ## Step 1 — Preflight
@@ -103,6 +130,8 @@ Align nested `packageManager` fields (e.g. `apps/*/package.json`) with the root
 
 ## Step 5 — Update dependencies
 
+Use CLI updates only — do not StrReplace version strings in `package.json`.
+
 ```bash
 pnpm update -r --latest
 ```
@@ -147,6 +176,12 @@ rg '"node"' package.json apps/*/package.json packages/*/package.json 2>/dev/null
 
 ## Step 6 — Validate (unified for all repos)
 
+If the registry project has `cms-edit/host` in `pnpm-workspace.yaml`, run the frozen hoisted install check first:
+
+```bash
+pnpm install --frozen-lockfile --config.node-linker=hoisted
+```
+
 Always run the patches check **once**, then the project validate from the registry:
 
 ```bash
@@ -205,6 +240,7 @@ This is optional follow-up — the skill workflow always runs the check regardle
 
 | Issue | Action |
 |-------|--------|
+| `ERR_PNPM_OUTDATED_LOCKFILE` on frozen/hoisted install | `package.json` and `pnpm-workspace.yaml` overrides out of sync with lockfile — re-run `pnpm update` for the package and align `overrides` |
 | `next` or `@types/node` still outdated to wrong major | Re-run overrides + safety re-pin; check `pnpm-workspace.yaml` overrides |
 | Non-`@se-studio` package still outdated after update | Likely within 24h of npm publish — wait and re-run; **do not** bypass `minimumReleaseAge` |
 | `corepack use` fails | Run `corepack enable` once, retry |

package/skills/site-workflows-new-project/SKILL.md

@@ -71,19 +71,53 @@ Write `CLAUDE.md` at the project root:
 
 ## Step 6 — Create `AGENTS.md`
 
-Write `AGENTS.md` at the project root. Fill in the user's email address (from memory if known, otherwise ask) and today's date:
+Write `AGENTS.md` at the project root. Fill in the user's email address (from memory if known, otherwise ask) and today's date.
+
+Include the **agent session workflow block** from [`packages/skills/references/agent-session/customer-agents-block.md`](../../references/agent-session/customer-agents-block.md) (branch policy, placement, parallel features, handoff).
 
 ```markdown
 # Next.js: ALWAYS read docs before coding
 
 Before any Next.js work, find and read the relevant doc in `node_modules/next/dist/docs/`. Your training data is outdated — the docs are the source of truth.
 
+# @se-studio packages: ALWAYS read docs before coding
+
+Before using any `@se-studio/*` package, read the relevant `node_modules/@se-studio/<package>/docs/llms.md`.
+
 # userEmail
 The user's email address is [USER_EMAIL].
 
 # currentDate
 Today's date is [CURRENT_DATE].
 
+## Agent session workflow
+
+**Load skill `site-workflows-agent-session` at the start of every coding session.**
+
+Default mode for this repo: **site-first**.
+
+### Branch policy
+
+- Agents may commit and push **`develop`** and **`feature/*`** only.
+- **Never** push to `main`, `master`, or production — human-only.
+- Prefer **draft PRs** to `develop` over direct pushes when `gh` is available.
+
+### Core vs customer placement
+
+Before non-trivial code, run the placement checklist (skill `site-workflows-agent-session`). If the checklist says **core**, stop — do not patch `@se-studio` behaviour in this repo.
+
+### Core release order
+
+When work depends on a new `@se-studio/*` npm release: release from `se-core-product` first, confirm npm, then `pnpm update @se-studio/<package>@<version> -r` here, then push `develop`. Never hand-edit dependency versions.
+
+### Parallel features
+
+One feature = one `feature/<scope>/<slug>` branch. Use git worktrees for parallel work on this repo. CMS: `--session <feature-slug>`. Manifest: `~/source/se/se-core-product/work/active/<feature>.yaml`.
+
+### Production handoff
+
+Agents stop at handoff — they do not merge to `main`. See skill `site-workflows-agent-session` Step 8.
+
 ## CMS editing (cms-edit)
 
 Before any Contentful content edit:

package/skills/site-workflows-stale-files-cleanup/SKILL.md

@@ -0,0 +1,165 @@
+---
+name: site-workflows-stale-files-cleanup
+description: "Audit and remove stale scripts, broken package.json entries, orphan docs, and duplicate tooling on SE Studio marketing sites. Supports single-app and monorepo layouts. Use for repo cleanup, stale files audit, hygiene audit, or pruning dead code. Always ask before deleting historical docs or deliverables."
+---
+
+# Stale files cleanup (repository hygiene)
+
+Remove **dead weight** from an SE Studio site repo without changing product behavior. This is **not** [`site-workflows-project-cleanup`](../site-workflows-project-cleanup/SKILL.md) (which strips a site to a bare template).
+
+**References:**
+
+| File | Purpose |
+|------|---------|
+| [`CHECKLIST.md`](../../references/stale-files-cleanup/CHECKLIST.md) | Discovery commands and grep patterns |
+| [`FALSE_POSITIVES.md`](../../references/stale-files-cleanup/FALSE_POSITIVES.md) | Paths agents must not delete |
+| [`MONOREPO.md`](../../references/stale-files-cleanup/MONOREPO.md) | Multi-app layout rules |
+| [`SINGLE_APP.md`](../../references/stale-files-cleanup/SINGLE_APP.md) | Single-app layout rules |
+| [`BRIGHTLINE_RUNBOOK.md`](../../references/stale-files-cleanup/BRIGHTLINE_RUNBOOK.md) | Case study (Jul 2026) |
+
+**Default:** Plan mode first — present a classified audit table before deleting anything.
+
+**Never:** push to `main`/`master`; delete `docs/cms-editor/` or committed `cms-edit/*/editor-pack/` without explicit user request; fix Dependabot alerts unless the user asks.
+
+---
+
+## When to use
+
+| Situation | Action |
+|-----------|--------|
+| User asks for repo cleanup, stale files, orphan scripts, dead docs | Run full workflow |
+| Broken `pnpm` scripts fail with missing file paths | Phase 1 only (broken tooling) |
+| Post-migration or post-monorepo consolidation | Phases 2–4 with migration confirmation |
+| Dependabot noise | Optional investigate phase only |
+
+## When not to use
+
+- Stripping a customer site to a reusable template → **`site-workflows-project-cleanup`**
+- CMS content edits → **`contentful-cms-*`** skills
+- Dependency version bumps → **`site-workflows-deps-update`**
+
+---
+
+## Step 1 — Preflight
+
+1. Read repo `AGENTS.md`, root `README.md`, and `.gitignore`.
+2. Detect layout — see [`MONOREPO.md`](../../references/stale-files-cleanup/MONOREPO.md) vs [`SINGLE_APP.md`](../../references/stale-files-cleanup/SINGLE_APP.md).
+3. Confirm integration branch (`develop` for customer sites, `dev` for se-core-product). Working tree clean or user approves.
+4. Run parallel discovery per [`CHECKLIST.md`](../../references/stale-files-cleanup/CHECKLIST.md).
+
+---
+
+## Step 2 — Classify findings
+
+Group every candidate into a table for the user:
+
+| Risk | Examples | Default action |
+|------|----------|----------------|
+| **High** | `package.json` script → missing file; doc links to non-existent path | Fix script entry or restore file; fix doc |
+| **Medium** | Completed migration scripts; dated audit deliverables; duplicate Husky | Delete after user confirms |
+| **Low** | Orphan scripts with zero refs; stub "Moved" docs; legacy path names in docs | Delete or update refs |
+
+Cross-check [`FALSE_POSITIVES.md`](../../references/stale-files-cleanup/FALSE_POSITIVES.md) before listing any path as deletable.
+
+---
+
+## Step 3 — Confirm with user
+
+Use `AskQuestion` (or equivalent) before bulk deletes:
+
+1. **Historical docs and deliverables** — archive vs hard delete vs keep (default: **ask**; do not assume).
+2. **Migration / one-off ops scripts** — only remove when user confirms work is complete (e.g. Contentful locale migration, Vercel env rotation runbooks marked done).
+3. **Dependabot** — offer investigation summary; do not bump packages unless user explicitly asks.
+
+---
+
+## Step 4 — Execute (ordered phases)
+
+### Phase 1 — Broken tooling
+
+- Remove or fix `package.json` script entries whose target files do not exist (root + `apps/*/package.json` in monorepos).
+- Highest signal — these fail when invoked.
+
+### Phase 2 — Orphan scripts
+
+- Delete scripts under `scripts/`, `apps/*/scripts/`, `docs/*/scripts/` with no `package.json` wiring and no inbound references.
+- Keep scripts cited as re-run playbooks in active docs (e.g. Formstack audit spikes).
+
+### Phase 3 — Completed one-offs
+
+- Migration tooling (`migrate-*.ts`, `enable-*-migration.js`, schema dumps) after user confirms migration done.
+- Ops runbooks marked complete in `ACTION-PLAN.md` / env inventory docs.
+
+### Phase 4 — Stale docs and artifacts
+
+- Pre-monorepo orientation docs, "Moved" stubs, one-off session reports, dated `.xlsx`/`.json` audit outputs.
+- Untracked orphan audits at repo root — delete or commit per user choice.
+
+### Phase 5 — Duplicate infrastructure (monorepo)
+
+- Per-app `.husky/` when root `.husky/pre-commit` runs `lint-staged` + typecheck.
+- Remove `husky` from app `devDependencies` when root `prepare` owns hooks.
+
+### Phase 6 — Doc drift and env templates
+
+- Legacy package/filter names (`example-brightline` → `apps/<app>/` paths and real filter name).
+- Broken references in `AGENTS.md`, README, playbooks, `ACTION-PLAN.md`.
+- Vars documented in README / `VERCEL-ENV-VARS.md` but missing from `.env.example`.
+
+### Phase 7 — Orphan npm dependencies (optional)
+
+```bash
+pnpm why <package>
+rg "from '<pkg>'|require\\('<pkg>'\\)" .
+```
+
+Remove root or app devDependencies with zero imports (e.g. leftover `xlsx` after workbook script removal).
+
+---
+
+## Step 5 — Reference repair
+
+After each deletion phase, grep for deleted basenames:
+
+```bash
+rg '<basename-or-path>' --glob '!node_modules' --glob '!.next'
+```
+
+Update inbound links in README, `AGENTS.md`, media briefs, editor playbooks, and superseded-doc cross-references.
+
+---
+
+## Step 6 — Optional Dependabot investigate
+
+When the repo is on GitHub and `gh` is available:
+
+```bash
+gh api repos/<org>/<repo>/dependabot/alerts --jq \
+  '.[] | select(.state=="open") | {number, package: .security_vulnerability.package.name, severity: .security_advisory.severity, manifest: .dependency.manifest_path, summary: .security_advisory.summary}'
+```
+
+For each alert: `pnpm why <package>` — classify as direct vs transitive, runtime vs dev-only. Summarize fix paths; **do not** bump unless user asks.
+
+---
+
+## Step 7 — Validate and commit
+
+```bash
+pnpm validate   # or repo-specific validate from AGENTS.md
+```
+
+- Revert unrelated diffs from validate side-effects (e.g. regenerated `abTests.ts`, biome trailing-newline fixes) before commit.
+- Pre-existing test failures: call out explicitly; do not blame cleanup.
+
+Commit on integration branch only. Suggested message: `chore: remove stale scripts, docs, and tooling`.
+
+Hand off production promotion to the human — never push `main`.
+
+---
+
+## Success criteria
+
+- Classified audit presented before deletes
+- No false-positive paths from [`FALSE_POSITIVES.md`](../../references/stale-files-cleanup/FALSE_POSITIVES.md) removed
+- `rg` pass clean for deleted paths (or intentional stubs updated)
+- `pnpm validate` passes or pre-existing failures documented