**Commit author identity is restricted to an allowlist.** pipelines enforces an author-identity allowlist in its pre-commit, pre-push, and CI checks, rejecting any commit whose author or committer name and email pair does not match one of a configured set of permitted identities. | Verified by a negative test that a commit with an identity outside the configured allowlist is rejected by the hook and by the CI check.

**Generated status with three hooks and four states.** The reference implementation lives in `pipelines_hooks/specs/`, exposing the hooks `spec-status`, `spec-decomposition`, and `spec-trailers`. Delivery status is generated, never hand-edited, and each requirement is in exactly one of the states SPECIFIED, LANDED, VERIFIED, or RETIRED. New landings use explicit Spec trailers or historical Spec subjects, never unrelated prose or none exemption reasons; historical receipts retain their existing validation. When specs exist, incomplete shallow Git history refuses generation and writes with exit 2 and a full-history fetch remedy, leaving status files unchanged; full history still rejects reverted or unreachable receipts. Repository ownership comes from origin or a sole configured remote, correcting stale checkout-derived owners without losing live legacy receipts; without an unambiguous remote identity, retain the old owner or finally the checkout name. A parent rolls up to the minimum state of its live children. A parent rolled up to LANDED carries its children's landing commits, and one rolled up to VERIFIED also carries their bound tests. During a resolved merge, default `spec-status` evaluates the index candidate tree with HEAD and MERGE_HEAD as parents and records evidence only from actual non-merge commits. An explicit `--head` remains authoritative even with unresolved conflicts. Default merge inference fails closed when conflicts remain or the worktree differs from its index. `spec-trailers` excludes commits already reachable from `origin/main` even when the pushed-over base is older, while continuing to validate all new branch commits against the current requirement and binding tree. | The files `pipelines_hooks/specs/status.py`, `decomposition.py`, and `trailers.py` exist; pending-merge tests in `tests/hooks/test_spec_status.py` verify candidate-tree history, explicit-head behavior, and fail-closed conflicts and index/worktree mismatch; `pipelines-hook spec-status --write` followed by `pipelines-hook spec-decomposition` runs clean in this repository.

**Test binding forms.** A test binds to a requirement with `@pytest.mark.spec("<ID>")` in Python or a `// spec: <ID>` comment in other languages, as parsed by `pipelines_hooks/specs/bindings.py`. | `pipelines_hooks/specs/bindings.py` exists and a bound test in this repository is picked up by `pipelines-hook spec-status`.

**The spec-delivery page.** `scripts/spec_dashboard*.py` is rendered through the reusable workflow `.github/workflows/pages_pipeline.yml` with `spec_dashboard_enabled: true`, and publishes at `https://knuckles-team.github.io/<repo>/spec-delivery/`. | `scripts/spec_dashboard.py` and `.github/workflows/pages_pipeline.yml` exist, and the workflow declares the `spec_dashboard_enabled` input.

**Reference callers in the five core repositories.** The reference callers are Medulla (`release.yml`), Meristem (`advisory.yml`), arbora (`pages.yml`), Scion SDK (`pages.yml`), and Overstory (`advisory.yml`). They are the one standard a connector copies. | Each named workflow file exists in its repository and calls `Knuckles-Team/pipelines/.github/workflows/pages_pipeline.yml@main` with `spec_dashboard_enabled: true`.

**The lane contract in each development skill.** Each repository's `<repo>-development` skill carries the section "Rapid delivery: the 5-minute contract", which is the lane contract for agents working in it. | A search of each core repository's `<repo>-development` skill finds the section heading "Rapid delivery: the 5-minute contract".

**Preserve retired identities across spec ownership moves.** `pipelines_hooks/specs/standard.py` uses the shared retirement parser. A retired row keeps its original prefix; active canonical-form rows must match the owning spec. | `test_moved_retired_identity_uses_shared_status_parser` accepts a retired historical ID and refuses active rows that merely mention retirement.

**CI checks changed prose.** `ste-staged` checks committed PR or push changes on clean CI checkouts. Local runs check the staged index. Unavailable requested base commits fail closed. Existing per-file `(code, message)` finding counts remain exempt. | Real Git fixtures cover PR and push event bases, new findings, legacy debt, staged content, and invalid bases.

**Every repository ships one-command agent setup.** Each repository tracks an idempotent, non-interactive `scripts/bootstrap.sh` that installs a current uv, the pinned Python (`.python-version`, else the fleet standard), the locked environment (`uv sync --locked`, or the repository's equivalent), and the pre-commit and pre-push hooks, then prints the gate command `uvx pre-commit run --all-files`. The script never pipes a network response into a shell: uv comes from `pip install --user` (retrying with `--break-system-packages`) or the script stops with the install link, so the `supply-chain` rule SC-INSTALL-001 stays clean. | `pipelines-hook agent-contract` reports `scripts/bootstrap.sh is not tracked` for a repository without it, reports SC-INSTALL-001 for a script containing `curl ... \| sh`, and passes under `--strict` for a conformant fixture.

**Every repository carries the standard tool-neutral AGENTS.md section.** `AGENTS.md` holds the marked block `<!-- agent-contract:start -->` to `<!-- agent-contract:end -->` with the labels Owner boundary, Setup, Gates and Commits, and a link to the organization `AGENTS.md` at `https://github.com/Knuckles-Team/.github/blob/main/AGENTS.md`. The block is tool-neutral; a tool-specific entry file such as `CLAUDE.md` only imports `AGENTS.md`. The connector scaffold in `universal-skills` generates both the script and the block. | `pipelines-hook agent-contract --strict` fails for an `AGENTS.md` without the block, a missing label or a missing org link, and passes for a conformant fixture.

**The agent-contract check is warn-level first.** The hook `agent-contract` (pre-push) reports findings and exits 0; `--strict` makes them blocking once the fleet has converged. It reads the tracked set only. | The default run exits 0 with a `WARN` line for a nonconforming fixture, and `--strict` exits 1.

**`ansible-tower-mcp` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`ansible-tower-mcp` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`ansible-tower-mcp` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`ansible-tower-mcp` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/ansible-tower-mcp/pages` returns a site.

`ansible-tower-mcp` has the rapid-delivery section in its development skill. | Check that its `ansible-tower-mcp-development` skill has the section "Rapid delivery: the 5-minute contract".

**`archimate-mcp` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`archimate-mcp` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`archimate-mcp` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`archimate-mcp` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/archimate-mcp/pages` returns a site.

`archimate-mcp` has the rapid-delivery section in its development skill. | Check that its `archimate-mcp-development` skill has the section "Rapid delivery: the 5-minute contract".

**`archivebox-api` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`archivebox-api` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`archivebox-api` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`archivebox-api` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/archivebox-api/pages` returns a site.

`archivebox-api` has the rapid-delivery section in its development skill. | Check that its `archivebox-api-development` skill has the section "Rapid delivery: the 5-minute contract".

**`aris-mcp` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`aris-mcp` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`aris-mcp` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`aris-mcp` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/aris-mcp/pages` returns a site.

`aris-mcp` has the rapid-delivery section in its development skill. | Check that its `aris-mcp-development` skill has the section "Rapid delivery: the 5-minute contract".

**`arr-mcp` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`arr-mcp` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`arr-mcp` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`arr-mcp` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/arr-mcp/pages` returns a site.

`arr-mcp` has the rapid-delivery section in its development skill. | Check that its `arr-mcp-development` skill has the section "Rapid delivery: the 5-minute contract".

**`atlassian-agent` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`atlassian-agent` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`atlassian-agent` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`atlassian-agent` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/atlassian-agent/pages` returns a site.

`atlassian-agent` has the rapid-delivery section in its development skill. | Check that its `atlassian-agent-development` skill has the section "Rapid delivery: the 5-minute contract".

**`audio-transcriber` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`audio-transcriber` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`audio-transcriber` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`audio-transcriber` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/audio-transcriber/pages` returns a site.

`audio-transcriber` has the rapid-delivery section in its development skill. | Check that its `audio-transcriber-development` skill has the section "Rapid delivery: the 5-minute contract".

**`audiobookshelf-mcp` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`audiobookshelf-mcp` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`audiobookshelf-mcp` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`audiobookshelf-mcp` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/audiobookshelf-mcp/pages` returns a site.

`audiobookshelf-mcp` has the rapid-delivery section in its development skill. | Check that its `audiobookshelf-mcp-development` skill has the section "Rapid delivery: the 5-minute contract".

**`caddy-mcp` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`caddy-mcp` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`caddy-mcp` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`caddy-mcp` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/caddy-mcp/pages` returns a site.

`caddy-mcp` has the rapid-delivery section in its development skill. | Check that its `caddy-mcp-development` skill has the section "Rapid delivery: the 5-minute contract".

**`camunda-mcp` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`camunda-mcp` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`camunda-mcp` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`camunda-mcp` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/camunda-mcp/pages` returns a site.

`camunda-mcp` has the rapid-delivery section in its development skill. | Check that its `camunda-mcp-development` skill has the section "Rapid delivery: the 5-minute contract".

**`ciso-assistant-api` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`ciso-assistant-api` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`ciso-assistant-api` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`ciso-assistant-api` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/ciso-assistant-api/pages` returns a site.

`ciso-assistant-api` has the rapid-delivery section in its development skill. | Check that its `ciso-assistant-api-development` skill has the section "Rapid delivery: the 5-minute contract".

**`clarity-api` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`clarity-api` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`clarity-api` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`clarity-api` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/clarity-api/pages` returns a site.

`clarity-api` has the rapid-delivery section in its development skill. | Check that its `clarity-api-development` skill has the section "Rapid delivery: the 5-minute contract".

**`container-manager-mcp` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`container-manager-mcp` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`container-manager-mcp` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`container-manager-mcp` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/container-manager-mcp/pages` returns a site.

`container-manager-mcp` has the rapid-delivery section in its development skill. | Check that its `container-manager-mcp-development` skill has the section "Rapid delivery: the 5-minute contract".

**`data-science-mcp` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`data-science-mcp` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`data-science-mcp` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`data-science-mcp` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/data-science-mcp/pages` returns a site.

`data-science-mcp` has the rapid-delivery section in its development skill. | Check that its `data-science-mcp-development` skill has the section "Rapid delivery: the 5-minute contract".

**`dockerhub-api` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`dockerhub-api` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`dockerhub-api` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`dockerhub-api` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/dockerhub-api/pages` returns a site.

`dockerhub-api` has the rapid-delivery section in its development skill. | Check that its `dockerhub-api-development` skill has the section "Rapid delivery: the 5-minute contract".

**`documentdb-mcp` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`documentdb-mcp` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`documentdb-mcp` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`documentdb-mcp` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/documentdb-mcp/pages` returns a site.

`documentdb-mcp` has the rapid-delivery section in its development skill. | Check that its `documentdb-mcp-development` skill has the section "Rapid delivery: the 5-minute contract".

**`egeria-mcp` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`egeria-mcp` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`egeria-mcp` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`egeria-mcp` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/egeria-mcp/pages` returns a site.

`egeria-mcp` has the rapid-delivery section in its development skill. | Check that its `egeria-mcp-development` skill has the section "Rapid delivery: the 5-minute contract".

**`emerald-exchange` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`emerald-exchange` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`emerald-exchange` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`emerald-exchange` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/emerald-exchange/pages` returns a site.

`emerald-exchange` has the rapid-delivery section in its development skill. | Check that its `emerald-exchange-development` skill has the section "Rapid delivery: the 5-minute contract".

**`erpnext-agent` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`erpnext-agent` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`erpnext-agent` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`erpnext-agent` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/erpnext-agent/pages` returns a site.

`erpnext-agent` has the rapid-delivery section in its development skill. | Check that its `erpnext-agent-development` skill has the section "Rapid delivery: the 5-minute contract".

**`fan-manager` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`fan-manager` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`fan-manager` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`fan-manager` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/fan-manager/pages` returns a site.

`fan-manager` has the rapid-delivery section in its development skill. | Check that its `fan-manager-development` skill has the section "Rapid delivery: the 5-minute contract".

**`firefly-iii-mcp` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`firefly-iii-mcp` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`firefly-iii-mcp` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`firefly-iii-mcp` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/firefly-iii-mcp/pages` returns a site.

`firefly-iii-mcp` has the rapid-delivery section in its development skill. | Check that its `firefly-iii-mcp-development` skill has the section "Rapid delivery: the 5-minute contract".

**`freshrss-agent` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`freshrss-agent` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`freshrss-agent` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`freshrss-agent` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/freshrss-agent/pages` returns a site.

`freshrss-agent` has the rapid-delivery section in its development skill. | Check that its `freshrss-agent-development` skill has the section "Rapid delivery: the 5-minute contract".

**`genius-agent` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`genius-agent` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`genius-agent` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`genius-agent` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/genius-agent/pages` returns a site.

`genius-agent` has the rapid-delivery section in its development skill. | Check that its `genius-agent-development` skill has the section "Rapid delivery: the 5-minute contract".

**`github-agent` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`github-agent` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`github-agent` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`github-agent` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/github-agent/pages` returns a site.

`github-agent` has the rapid-delivery section in its development skill. | Check that its `github-agent-development` skill has the section "Rapid delivery: the 5-minute contract".

**`gitlab-api` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`gitlab-api` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`gitlab-api` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`gitlab-api` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/gitlab-api/pages` returns a site.

`gitlab-api` has the rapid-delivery section in its development skill. | Check that its `gitlab-api-development` skill has the section "Rapid delivery: the 5-minute contract".

**`gramps-mcp` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`gramps-mcp` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`gramps-mcp` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`gramps-mcp` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/gramps-mcp/pages` returns a site.

`gramps-mcp` has the rapid-delivery section in its development skill. | Check that its `gramps-mcp-development` skill has the section "Rapid delivery: the 5-minute contract".

**`hdhomerun-mcp` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`hdhomerun-mcp` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`hdhomerun-mcp` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`hdhomerun-mcp` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/hdhomerun-mcp/pages` returns a site.

`hdhomerun-mcp` has the rapid-delivery section in its development skill. | Check that its `hdhomerun-mcp-development` skill has the section "Rapid delivery: the 5-minute contract".

**`home-assistant-agent` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`home-assistant-agent` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`home-assistant-agent` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`home-assistant-agent` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/home-assistant-agent/pages` returns a site.

`home-assistant-agent` has the rapid-delivery section in its development skill. | Check that its `home-assistant-agent-development` skill has the section "Rapid delivery: the 5-minute contract".

**`jellyfin-mcp` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`jellyfin-mcp` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`jellyfin-mcp` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`jellyfin-mcp` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/jellyfin-mcp/pages` returns a site.

`jellyfin-mcp` has the rapid-delivery section in its development skill. | Check that its `jellyfin-mcp-development` skill has the section "Rapid delivery: the 5-minute contract".

**`jena-mcp` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`jena-mcp` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`jena-mcp` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`jena-mcp` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/jena-mcp/pages` returns a site.

`jena-mcp` has the rapid-delivery section in its development skill. | Check that its `jena-mcp-development` skill has the section "Rapid delivery: the 5-minute contract".

**`kafka-mcp` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`kafka-mcp` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`kafka-mcp` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`kafka-mcp` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/kafka-mcp/pages` returns a site.

`kafka-mcp` has the rapid-delivery section in its development skill. | Check that its `kafka-mcp-development` skill has the section "Rapid delivery: the 5-minute contract".

**`keycloak-agent` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`keycloak-agent` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`keycloak-agent` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`keycloak-agent` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/keycloak-agent/pages` returns a site.

`keycloak-agent` has the rapid-delivery section in its development skill. | Check that its `keycloak-agent-development` skill has the section "Rapid delivery: the 5-minute contract".

**`lakekeeper-mcp` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`lakekeeper-mcp` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`lakekeeper-mcp` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`lakekeeper-mcp` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/lakekeeper-mcp/pages` returns a site.

`lakekeeper-mcp` has the rapid-delivery section in its development skill. | Check that its `lakekeeper-mcp-development` skill has the section "Rapid delivery: the 5-minute contract".

**`langfuse-agent` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`langfuse-agent` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`langfuse-agent` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`langfuse-agent` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/langfuse-agent/pages` returns a site.

`langfuse-agent` has the rapid-delivery section in its development skill. | Check that its `langfuse-agent-development` skill has the section "Rapid delivery: the 5-minute contract".

**`leanix-agent` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`leanix-agent` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`leanix-agent` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`leanix-agent` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/leanix-agent/pages` returns a site.

`leanix-agent` has the rapid-delivery section in its development skill. | Check that its `leanix-agent-development` skill has the section "Rapid delivery: the 5-minute contract".

**`legal-peripherals-mcp` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`legal-peripherals-mcp` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`legal-peripherals-mcp` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`legal-peripherals-mcp` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/legal-peripherals-mcp/pages` returns a site.

`legal-peripherals-mcp` has the rapid-delivery section in its development skill. | Check that its `legal-peripherals-mcp-development` skill has the section "Rapid delivery: the 5-minute contract".

**`lgtm-mcp` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`lgtm-mcp` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`lgtm-mcp` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`lgtm-mcp` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/lgtm-mcp/pages` returns a site.

`lgtm-mcp` has the rapid-delivery section in its development skill. | Check that its `lgtm-mcp-development` skill has the section "Rapid delivery: the 5-minute contract".

**`listmonk-api` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`listmonk-api` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`listmonk-api` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`listmonk-api` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/listmonk-api/pages` returns a site.

`listmonk-api` has the rapid-delivery section in its development skill. | Check that its `listmonk-api-development` skill has the section "Rapid delivery: the 5-minute contract".

**`bellwether-mcp` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). The repository was renamed from `market-data-mcp`; the old name redirects to it. | The rollup is the minimum state of its four children.

`bellwether-mcp` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`bellwether-mcp` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`bellwether-mcp` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/bellwether-mcp/pages` returns a site.

`bellwether-mcp` has the rapid-delivery section in its development skill. | Check that its `market-data-mcp-development` skill, which still carries the pre-rename directory name, has the section "Rapid delivery: the 5-minute contract".

**`mattermost-mcp` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`mattermost-mcp` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`mattermost-mcp` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`mattermost-mcp` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/mattermost-mcp/pages` returns a site.

`mattermost-mcp` has the rapid-delivery section in its development skill. | Check that its `mattermost-mcp-development` skill has the section "Rapid delivery: the 5-minute contract".

**`mealie-mcp` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`mealie-mcp` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`mealie-mcp` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`mealie-mcp` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/mealie-mcp/pages` returns a site.

`mealie-mcp` has the rapid-delivery section in its development skill. | Check that its `mealie-mcp-development` skill has the section "Rapid delivery: the 5-minute contract".

**`media-downloader` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`media-downloader` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`media-downloader` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`media-downloader` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/media-downloader/pages` returns a site.

`media-downloader` has the rapid-delivery section in its development skill. | Check that its `media-downloader-development` skill has the section "Rapid delivery: the 5-minute contract".

**`microsoft-agent` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`microsoft-agent` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`microsoft-agent` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`microsoft-agent` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/microsoft-agent/pages` returns a site.

`microsoft-agent` has the rapid-delivery section in its development skill. | Check that its `microsoft-agent-development` skill has the section "Rapid delivery: the 5-minute contract".

**`nextcloud-agent` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`nextcloud-agent` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`nextcloud-agent` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`nextcloud-agent` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/nextcloud-agent/pages` returns a site.

`nextcloud-agent` has the rapid-delivery section in its development skill. | Check that its `nextcloud-agent-development` skill has the section "Rapid delivery: the 5-minute contract".

**`objectstore-mcp` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`objectstore-mcp` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`objectstore-mcp` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`objectstore-mcp` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/objectstore-mcp/pages` returns a site.

`objectstore-mcp` has the rapid-delivery section in its development skill. | Check that its `objectstore-mcp-development` skill has the section "Rapid delivery: the 5-minute contract".

**`okta-agent` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`okta-agent` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`okta-agent` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`okta-agent` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/okta-agent/pages` returns a site.

`okta-agent` has the rapid-delivery section in its development skill. | Check that its `okta-agent-development` skill has the section "Rapid delivery: the 5-minute contract".

**`onetrust-api` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`onetrust-api` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`onetrust-api` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`onetrust-api` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/onetrust-api/pages` returns a site.

`onetrust-api` has the rapid-delivery section in its development skill. | Check that its `onetrust-api-development` skill has the section "Rapid delivery: the 5-minute contract".

**`openbao-mcp` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`openbao-mcp` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`openbao-mcp` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`openbao-mcp` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/openbao-mcp/pages` returns a site.

`openbao-mcp` has the rapid-delivery section in its development skill. | Check that its `openbao-mcp-development` skill has the section "Rapid delivery: the 5-minute contract".

**`opensearch-mcp` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`opensearch-mcp` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`opensearch-mcp` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`opensearch-mcp` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/opensearch-mcp/pages` returns a site.

`opensearch-mcp` has the rapid-delivery section in its development skill. | Check that its `opensearch-mcp-development` skill has the section "Rapid delivery: the 5-minute contract".

**`owncast-agent` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`owncast-agent` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`owncast-agent` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`owncast-agent` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/owncast-agent/pages` returns a site.

`owncast-agent` has the rapid-delivery section in its development skill. | Check that its `owncast-agent-development` skill has the section "Rapid delivery: the 5-minute contract".

**`paperless-ngx-mcp` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`paperless-ngx-mcp` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`paperless-ngx-mcp` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`paperless-ngx-mcp` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/paperless-ngx-mcp/pages` returns a site.

`paperless-ngx-mcp` has the rapid-delivery section in its development skill. | Check that its `paperless-ngx-mcp-development` skill has the section "Rapid delivery: the 5-minute contract".

**`plane-agent` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`plane-agent` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`plane-agent` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`plane-agent` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/plane-agent/pages` returns a site.

`plane-agent` has the rapid-delivery section in its development skill. | Check that its `plane-agent-development` skill has the section "Rapid delivery: the 5-minute contract".

**`portainer-agent` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`portainer-agent` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`portainer-agent` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`portainer-agent` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/portainer-agent/pages` returns a site.

`portainer-agent` has the rapid-delivery section in its development skill. | Check that its `portainer-agent-development` skill has the section "Rapid delivery: the 5-minute contract".

**`postiz-agent` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`postiz-agent` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`postiz-agent` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`postiz-agent` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/postiz-agent/pages` returns a site.

`postiz-agent` has the rapid-delivery section in its development skill. | Check that its `postiz-agent-development` skill has the section "Rapid delivery: the 5-minute contract".

**`pulselink-mcp` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`pulselink-mcp` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`pulselink-mcp` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`pulselink-mcp` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/pulselink-mcp/pages` returns a site.

`pulselink-mcp` has the rapid-delivery section in its development skill. | Check that its `pulselink-mcp-development` skill has the section "Rapid delivery: the 5-minute contract".

**`qbittorrent-agent` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`qbittorrent-agent` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`qbittorrent-agent` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`qbittorrent-agent` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/qbittorrent-agent/pages` returns a site.

`qbittorrent-agent` has the rapid-delivery section in its development skill. | Check that its `qbittorrent-agent-development` skill has the section "Rapid delivery: the 5-minute contract".

**`repository-manager` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`repository-manager` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`repository-manager` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`repository-manager` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/repository-manager/pages` returns a site.

`repository-manager` has the rapid-delivery section in its development skill. | Check that its `repository-manager-development` skill has the section "Rapid delivery: the 5-minute contract".

**`rom-manager` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`rom-manager` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`rom-manager` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`rom-manager` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/rom-manager/pages` returns a site.

`rom-manager` has the rapid-delivery section in its development skill. | Check that its `rom-manager-development` skill has the section "Rapid delivery: the 5-minute contract".

**`salesforce-agent` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`salesforce-agent` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`salesforce-agent` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`salesforce-agent` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/salesforce-agent/pages` returns a site.

`salesforce-agent` has the rapid-delivery section in its development skill. | Check that its `salesforce-agent-development` skill has the section "Rapid delivery: the 5-minute contract".

**`scholarx` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`scholarx` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`scholarx` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`scholarx` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/scholarx/pages` returns a site.

`scholarx` has the rapid-delivery section in its development skill. | Check that its `scholarx-development` skill has the section "Rapid delivery: the 5-minute contract".

**`searxng-mcp` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`searxng-mcp` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`searxng-mcp` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`searxng-mcp` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/searxng-mcp/pages` returns a site.

`searxng-mcp` has the rapid-delivery section in its development skill. | Check that its `searxng-mcp-development` skill has the section "Rapid delivery: the 5-minute contract".

**`servicenow-api` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`servicenow-api` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`servicenow-api` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`servicenow-api` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/servicenow-api/pages` returns a site.

`servicenow-api` has the rapid-delivery section in its development skill. | Check that its `servicenow-api-development` skill has the section "Rapid delivery: the 5-minute contract".

**`spark-mcp` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`spark-mcp` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`spark-mcp` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`spark-mcp` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/spark-mcp/pages` returns a site.

`spark-mcp` has the rapid-delivery section in its development skill. | Check that its `spark-mcp-development` skill has the section "Rapid delivery: the 5-minute contract".

**`sql-mcp` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`sql-mcp` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`sql-mcp` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`sql-mcp` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/sql-mcp/pages` returns a site.

`sql-mcp` has the rapid-delivery section in its development skill. | Check that its `sql-mcp-development` skill has the section "Rapid delivery: the 5-minute contract".

**`stirlingpdf-agent` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`stirlingpdf-agent` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`stirlingpdf-agent` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`stirlingpdf-agent` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/stirlingpdf-agent/pages` returns a site.

`stirlingpdf-agent` has the rapid-delivery section in its development skill. | Check that its `stirlingpdf-agent-development` skill has the section "Rapid delivery: the 5-minute contract".

**`systems-manager` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`systems-manager` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`systems-manager` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`systems-manager` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/systems-manager/pages` returns a site.

`systems-manager` has the rapid-delivery section in its development skill. | Check that its `systems-manager-development` skill has the section "Rapid delivery: the 5-minute contract".

**`technitium-dns-mcp` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`technitium-dns-mcp` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`technitium-dns-mcp` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`technitium-dns-mcp` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/technitium-dns-mcp/pages` returns a site.

`technitium-dns-mcp` has the rapid-delivery section in its development skill. | Check that its `technitium-dns-mcp-development` skill has the section "Rapid delivery: the 5-minute contract".

**`tunnel-manager` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`tunnel-manager` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`tunnel-manager` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`tunnel-manager` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/tunnel-manager/pages` returns a site.

`tunnel-manager` has the rapid-delivery section in its development skill. | Check that its `tunnel-manager-development` skill has the section "Rapid delivery: the 5-minute contract".

**`twenty-mcp` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`twenty-mcp` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`twenty-mcp` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`twenty-mcp` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/twenty-mcp/pages` returns a site.

`twenty-mcp` has the rapid-delivery section in its development skill. | Check that its `twenty-mcp-development` skill has the section "Rapid delivery: the 5-minute contract".

**`uptime-kuma-agent` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`uptime-kuma-agent` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`uptime-kuma-agent` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`uptime-kuma-agent` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/uptime-kuma-agent/pages` returns a site.

`uptime-kuma-agent` has the rapid-delivery section in its development skill. | Check that its `uptime-kuma-agent-development` skill has the section "Rapid delivery: the 5-minute contract".

**`vaultwarden-mcp` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`vaultwarden-mcp` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`vaultwarden-mcp` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`vaultwarden-mcp` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/vaultwarden-mcp/pages` returns a site.

`vaultwarden-mcp` has the rapid-delivery section in its development skill. | Check that its `vaultwarden-mcp-development` skill has the section "Rapid delivery: the 5-minute contract".

**`vector-mcp` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`vector-mcp` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`vector-mcp` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`vector-mcp` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/vector-mcp/pages` returns a site.

`vector-mcp` has the rapid-delivery section in its development skill. | Check that its `vector-mcp-development` skill has the section "Rapid delivery: the 5-minute contract".

**`wger-agent` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`wger-agent` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`wger-agent` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`wger-agent` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/wger-agent/pages` returns a site.

`wger-agent` has the rapid-delivery section in its development skill. | Check that its `wger-agent-development` skill has the section "Rapid delivery: the 5-minute contract".

**`world-reference-mcp` adopts the standard spec-delivery method and page.** Rollup of the four children below, following the reference implementation (PIPE-CONNSPEC-R001 to PIPE-CONNSPEC-R005). | The rollup is the minimum state of its four children.

`world-reference-mcp` has a `specs/` tree with a generated `status.json`. | Check that `specs/` exists and contains a `status.json` written by `pipelines-hook spec-status --write`.

`world-reference-mcp` has the three spec hooks in its pre-commit config. | Check that the pre-commit config lists `spec-status`, `spec-decomposition`, and `spec-trailers` from `Knuckles-Team/pipelines`.

`world-reference-mcp` has a caller of the reusable Pages workflow with the dashboard enabled and Pages turned on. | Check that a workflow calls `pages_pipeline.yml@main` with `spec_dashboard_enabled: true`, and `gh api repos/Knuckles-Team/world-reference-mcp/pages` returns a site.

`world-reference-mcp` has the rapid-delivery section in its development skill. | Check that its `world-reference-mcp-development` skill has the section "Rapid delivery: the 5-minute contract".

**Canonical title determines generated spec identity.** The generator reuses the spec-standard title parser; a missing canonical title retains the prior identity or directory fallback. | `test_canonical_title_controls_generated_identity` covers missing and stale metadata without changing requirement IDs.

**Requirement state read from the engine (rollup).** The status generator must compare its output with the engine-derived state of EG-SDLC-R005 when an endpoint is set. A difference fails the spec-status gate and names each row. `status.json` stays a generated export. Children `.1` and `.2` deliver it. | See each child.

**Wiring.** `main` at `pipelines_hooks/specs/status.py:99` calls `compare_engine_state` in `pipelines_hooks/specs/engine_state.py` after generation. It reads the arbora `spec.status` operation over plain HTTP. | `tests/hooks/test_engine_state.py::test_difference_names_rows` feeds one differing row.

**Hot-path proof.** The test generates status for a fixture repository and reads a fixture endpoint. Equal states pass. One differing row fails the gate with that row ID. | `tests/hooks/test_engine_state.py::test_generator_and_engine_agree` asserts both outcomes.

**Binding suggester ranks existing tests for unverified rows.** `main` in `pipelines_hooks/specs/bind_suggest.py` scores each tracked test against every SPECIFIED or LANDED leaf row. It scores a test that the row text names, a test that names the row ID or an old alias, and a test whose name shares at least two title terms. It reads and writes no repository file, and the same tree gives the same ranked output. | `tests/hooks/test_spec_bind_suggest.py::test_ranks_named_test_first_and_is_repeatable` asserts the ranking, the term threshold and repeatability on a fixture repository.

**Explicit retired standard-ID aliases.** An exact retired standard requirement ID may map to one current active requirement row through `.config/spec-aliases.toml`. Require the source ID to be absent from current requirement rows, including retired tombstones. Reject absent or retired targets, alias chains and cycles, and exact standard aliases intercepted by retired prefixes. Keep one-hop prefix and pre-standard aliases unchanged. Historical and current trailer ranges retain unknown-ID and bound-test enforcement; an exact alias never applies to unlisted children. | `tests/hooks/test_spec_standard_aliases.py` covers renumbered history, current ranges, status evidence, and adversarial aliases.

**Row-level Depends-on.** `parse_rows` in `pipelines_hooks/specs/requirements_doc.py` reads prerequisite IDs from a requirement cell, including IDs of other repositories. No other field is added to a row. | `tests/hooks/test_goal_priority.py::test_row_depends_on_parses`

**Priority from competency questions.** `score` in `pipelines_hooks/specs/priority.py` computes 10 for each `EG-CQ-` row that transitively depends on a row, plus 2 for each open row it transitively unblocks, halved for a non-functional row. | `tests/hooks/test_goal_priority.py::test_priority_formula`

**Priority, frontier, and unserved from the organization aggregate.** `aggregate` in `scripts/architecture_explorer/delivery.py` computes `priority`, `frontier`, and `unserved` over the rows of every repository. The per-repository `status.json` generator writes none of them, so a repository's `status.json` keeps its prior shape. Unserved rows are open functional leaf rows no competency question reaches. | `tests/hooks/test_goal_priority.py::test_generator_leaves_status_shape_unchanged` and `tests/test_architecture_delivery.py::test_aggregate_over_repositories`

**Derived release bundles.** `bundles` in `pipelines_hooks/specs/priority.py` groups open rows joined by cross-repository `Depends-on` edges. Each bundle orders its repositories by the release train and lists, per row, the bundle rows it unblocks. The bundle priority is the maximum row priority. | `tests/hooks/test_goal_priority.py::test_bundle_orders_steps_by_release_train`

**Architecture page delivery views.** `scripts/architecture_explorer/delivery.py` recomputes the scores over every repository. `template.html` shows Next up, Delivery path, a priority sort, a competency-question filter, a “No CQ dependency path” filter that distinguishes CQ reachability from architecture placement and implementation links, and competency-question badges on each row. | `tests/test_architecture_delivery.py::test_aggregate_over_repositories` and `test_page_embeds_delivery_views`

**Repository switcher kept in sync with the core repo list.** The documentation site's repository switcher is renamed and its repository list is completed to match the full declared set of core repositories, replacing any per-repository duplicate copies and staying synchronized with the shared parity check and release receipt. Meristem's now-obsolete generator for a standalone web UI deployment manifest is also removed, since the web UI runs within Arbora. | A parity check confirms the switcher's repository list matches the declared core-repository set and release receipt, and a source scan confirms the obsolete standalone deployment generator no longer exists.

**Layered documentation from overview to reference.** The published documentation presents a layered information architecture: concise top-level introductions, then per-component overviews, then detailed reference pages, so a reader can go only as deep as they need. | A navigation-depth and link-structure audit confirms each tier, introduction, component, and reference, exists and links progressively into the next.

**Present-tense docs with accessible embedded start.** The published README and documentation home present content in the intended canonical order, include an embedded observable quick-start demonstration, use accessible multimodal and shared visual assets, run on the shared Material-themed site with short navigation, and describe the running engine's current behavior in present tense rather than its history. | Strict documentation build, theme, accessibility, and content-diff checks confirm the README order, embedded start, shared visuals, and present-tense wording.

**One progressively disclosed skill-graph corpus.** Concepts, components, and reference pages are drawn from one progressively disclosed skill-graph content corpus rather than separate, independently maintained sources. | A build check confirms the published concept, component, and reference pages are generated from the single skill-graph corpus with consistent navigation depth.

**Generate architecture and reference pages from registries.** Architecture, capability, and reference documentation pages are generated directly from the underlying registries and contracts rather than hand-authored, so published content stays consistent with the implementation it describes. | A build-time comparison confirms each generated page's content matches its source registry or contract.

**Rehome generated docs out of the legacy docs directory.** Every generated or gate-checked artifact currently stored under a repository's legacy docs directory is moved to its new canonical tracked location, every quality gate that referenced the old location is repointed to the new one, and the legacy docs directory is then removed. | A source scan confirms no gate or build step still reads from the removed docs directory and that each migrated artifact exists at its new tracked location.

**Ecosystem flow diagram with exact names and project marks.** The documentation home page renders the shared Material theme chrome together with an architecture flow diagram showing the path from people through the Arbora web UI, Tuig, Axil, and messaging/protocol clients to Arbora, Meristem, and Medulla, plus the source-system-to-Scion SDK flow, using each project's exact display title and a versioned logo mark. | Focused theme rendering tests plus a changed-file documentation build confirm the diagram's flow, project titles, and logo marks render correctly.

**Correct ownership and quick start in consumer parity checks.** The shared Pages parity check verifies that a consumer site's documentation correctly states process and front-door ownership, includes a stdio-based quick start, renders on the shared Material theme with short navigation, and keeps its content flows accessible. | A multi-page render, link, and accessibility audit plus a changed-file build check confirm ownership statements, the quick start, and accessible navigation on the consumer site.

The shared generator must show accessible component package diagrams and export Mermaid source. It must include every spec. | `test_deterministic_escaped_output_and_plan_diagram_coverage` in `tests/test_spec_dashboard_metadata.py`.

**Generate API contract docs from the contract registry.** API contract documentation pages are generated from the canonical contract and method registry rather than hand-written, so the published reference stays synchronized with the registry's actual definitions. | A build-time comparison between the generated documentation pages and the source contract registry confirms they match.

**Present-tense home page with screenshot and repo map.** The shared theme's documentation home page is present-tense HTML with short navigation, a real product screenshot, a map of the full declared core-repository set from the shared registry (currently seven), and an Arbora-hosted observable quick-start walkthrough. | Strict MkDocs render, accessibility, theme, and privacy gates, together with the documentation build run, confirm the home page's content and that it passes without regressions.

The spec-delivery page must map specs to implementation references. It must replace the Concepts column. | `test_implementation_tests_docs_and_missing_sources_are_distinct` in `tests/test_spec_dashboard_metadata.py`.

The generator must read Code declarations and existing source citations from spec.md and plan.md. | `test_source_declarations_and_citations_in_both_documents` in `tests/test_spec_dashboard_metadata.py`.

Source declarations must survive status regeneration without adding hand-edited status fields. | Needs a status-regeneration integration check. `test_enrichment_preserves_delivery_records_and_status_bytes` checks enrichment only; it does not prove regeneration.

Each implementation link must identify its source revision and path. External links must remain unverified. | `test_implementation_tests_docs_and_missing_sources_are_distinct` in `tests/test_spec_dashboard_metadata.py`.

The page must state Not mapped when a spec has no code references. | `test_code_cells_replace_concepts` in `tests/test_spec_dashboard_metadata.py`.

The spec table must distinguish implementation, test, and documentation links. | `test_implementation_tests_docs_and_missing_sources_are_distinct` in `tests/test_spec_dashboard_metadata.py`.