devrites 3.2.27 → 4.0.0

package/pack/generated/codex/skills/rite-build/reference/forge.md

@@ -1,210 +0,0 @@
-# Forge: isolated candidate builds
-
-Forge is the rare `$rite-build` branch for a vetted architecture fork. Two or
-three wrights implement the same slice in separate, manifest-owned worktrees; a
-read-only judge selects one; only that candidate lands.
-
-The engine manifest (`devrites-forge/v1`) is the sole authority for run,
-candidate, branch, worktree, worker, merge, verification, and cleanup identity.
-`forge-report.md`, names, paths, and prompts are records or inputs, never
-ownership.
-
-## Entry contract
-
-`$rite-vet` may set `Forge: yes` only when the slice has all three:
-
-```markdown
-Forge: yes — <why building the wrong architecture costs more than 2–3 attempts>
-Forge strategies: A=<complete approach> | B=<complete approach> [| C=<complete approach>]
-Forge scorecard: acceptance=<AC-### list>; test-plan=<exact test-plan.md rows/commands>
-```
-
-Strategies are distinct seams, data shapes, reuse choices, or algorithms, not
-wording variants. The scorecard covers every slice AC and every required test.
-Otherwise set `Forge: no`, both Forge detail fields to `none`, and dispatch one
-wright.
-
-Before `forge plan`, also require a Git checkout and a real host adapter that can
-declare `manifest-env-v1` and:
-
-- start each candidate in its exact worktree;
-- expose its stable worker ID, live PID, and matching process-start token before
-  its first tool call;
-- set all five Forge binding variables; and
-- end that process before extraction.
-
-Never claim that binding on the adapter's behalf. Without it, an unbound
-`forge plan` returns typed `degraded` / `serial` JSON and creates nothing; accept
-that result and use the normal serial wright.
-
-## Lifecycle
-
-### 1. Plan, then snapshot
-
-Write the normal root-owned `.wright-allowlist`. Hash the complete scorecard
-owners, not excerpts:
-
-```bash
-SLUG="$(cat .devrites/ACTIVE)"
-WORK=".devrites/work/$SLUG"
-hash_file() {
-  if command -v shasum >/dev/null 2>&1; then
-    shasum -a 256 "$1" | awk '{print $1}'
-  elif command -v sha256sum >/dev/null 2>&1; then
-    sha256sum "$1" | awk '{print $1}'
-  else
-    return 127
-  fi
-}
-ACCEPTANCE_HASH="$(hash_file "$WORK/spec.md")"
-TEST_PLAN_HASH="$(hash_file "$WORK/test-plan.md")"
-
-devrites-engine forge plan "<SLICE-###>" "$SLUG" \
-  --strategy "A=<strategy A>" \
-  --strategy "B=<strategy B>" \
-  --acceptance-hash "$ACCEPTANCE_HASH" \
-  --test-plan-hash "$TEST_PLAN_HASH" \
-  --worker-binding=manifest-env-v1
-```
-
-Add `--strategy "C=<strategy C>"` only for a third vetted strategy. Both hashes
-must be the complete 64-hex SHA-256 values of the current files. The command
-shown is only for an adapter that really provides the binding. Otherwise omit
-`--worker-binding`; the engine returns the side-effect-free serial result.
-
-Read the JSON result:
-
-- `status: planned`: take the run ID and every candidate path from its
-  manifest; then run `devrites-engine reconcile snapshot`.
-- `status: degraded, mode: serial`: record the reason and use one normal
-  wright. The engine created no Forge state.
-- non-zero exit: classify it as a technical defect. Preserve any manifest
-  state and recover it; never infer paths or silently start a serial writer.
-
-`forge plan` must precede `reconcile snapshot`: validated operational manifests
-are reconciliation-private, while `forge-report.md` and every other `.forge`
-path remain visible.
-
-### 2. Bind and dispatch every candidate
-
-For each candidate, the host starts a fresh worker at the manifest's exact
-`worktree`, pauses it before its first tool call, and obtains the engine token
-for its live PID:
-
-```bash
-devrites-engine forge process-token "$WORKER_PID"
-```
-
-Read `process_start` from the JSON; never reproduce the token algorithm in
-shell. Record that exact identity, then release the worker:
-
-```bash
-devrites-engine forge record "$RUN_ID" "$CANDIDATE" started \
-  --worker-id "$WORKER_ID" \
-  --pid "$WORKER_PID" \
-  --process-start "$PROCESS_START"
-```
-
-The candidate process receives this all-or-none environment:
-
-```text
-DEVRITES_FORGE_RUN_ID=<manifest run_id>
-DEVRITES_FORGE_CANDIDATE=<A|B|C>
-DEVRITES_FORGE_WORKER_ID=<recorded worker id>
-DEVRITES_FORGE_WORKER_PID=<recorded live pid>
-DEVRITES_FORGE_PROCESS_START=<recorded start token>
-```
-
-Its cwd is the exact manifest worktree. Give it the normal
-[`wright-dispatch.md`](wright-dispatch.md) packet plus its one recorded
-strategy. The same project-relative allowlist applies inside that candidate
-tree. Any missing, partial, stale, wrong-tree, wrong-branch, or wrong-worker
-binding is a denial, not a reason to widen scope.
-
-After the worker returns and its process exits:
-
-```bash
-devrites-engine forge record "$RUN_ID" "$CANDIDATE" finished \
-  --worker-id "$WORKER_ID"
-devrites-engine forge extract "$RUN_ID" "$CANDIDATE"
-```
-
-Extraction makes the complete tracked, staged, unstaged, untracked, deletion,
-mode, and symlink delta reachable by the recorded candidate commit and binds
-its SHA-256. Ignored, dirty, mismatched, live, or ambiguous content is
-preserved. A crashed worker is recorded `failed`; the run stays preserved for
-technical recovery and does not degrade in place.
-
-### 3. Judge, record, and merge
-
-After **every** candidate is extracted, dispatch
-[`devrites-forge-judge`](.codex/agents/devrites-forge-judge.toml) in fresh,
-read-only context. Give it the manifest, slice scorecard, base commit, and each
-recorded candidate commit/tree/delta hash. It scores the immutable diffs against
-the same acceptance, tests, principles, reuse, simplicity, and anti-slop bar.
-
-For one qualifying winner:
-
-```bash
-devrites-engine forge record "$RUN_ID" winner "<A|B|C>" \
-  --worker-id "<judge result id>"
-devrites-engine forge merge "$RUN_ID" "<A|B|C>"
-```
-
-Merge revalidates every extract and the unchanged primary baseline, performs a
-no-side-effect conflict preflight, then fast-forwards to exactly the recorded
-winner. A mismatch or conflict leaves the primary tree unchanged. Runner-up
-ideas remain report notes; never hand-merge candidates or mutate the landed
-winner inside this run.
-
-If no candidate qualifies, preserve the run and route the actual finding:
-product/acceptance ambiguity returns to planning; implementation or proof
-defects use bounded technical recovery. Retry authorization is not a human
-decision.
-
-### 4. Verify, clean, then record
-
-Hand the winner's structured artifact to the normal cycle. Run immediate
-reconciliation, doubt every stood decision, and complete test-integrity,
-targeted, browser, and other slice proof. Only after every required gate is
-green:
-
-```bash
-devrites-engine forge record "$RUN_ID" verification verified \
-  --worker-id "<verifier result id>"
-devrites-engine forge cleanup "$RUN_ID"
-devrites-engine reconcile close
-```
-
-Cleanup reads only the manifest. It removes an exact terminal, dead, clean,
-reachable worktree; preserves live, dirty, mismatched, unreachable, or
-ambiguous state with a reason; and never deletes candidate branches.
-
-Now write `.devrites/work/<slug>/forge-report.md` alongside the normal Build
-records. The report is written after reconciliation and verification, includes
-cleanup preservation results, and never authorizes merge, cleanup, or reap.
-
-```markdown
-# Forge report: <SLICE-### — name>
-Run: <run-id> · scorecard: <acceptance hash> / <test-plan hash>
-
-## Candidates
-| # | Strategy | Gates | Delta SHA-256 | Judge result |
-|---|---|---|---|---|
-| A | <approach> | <green/red> | <hash> | <score + decisive evidence> |
-| B | <approach> | <green/red> | <hash> | <score + decisive evidence> |
-
-## Verdict
-Winner: <A|B|C> — <rubric-based reason>
-Discarded: <one reason per loser>
-Runner-up notes: <ideas for later | none>
-Cleanup: <complete | preserved candidate + exact engine reason>
-```
-
-## Interrupted runs
-
-Use `devrites-engine forge reap [slug]` only for recovery. It enumerates
-validated manifests rather than matching directories or branch names. It applies the
-same exact identity, liveness, cleanliness, and reachability checks as cleanup.
-Foreign, live, dirty, malformed, mismatched, or ambiguous state is reported and
-preserved. Never infer a path, suppress a failure, or delete a branch.

package/pack/generated/codex/skills/rite-seal/reference/conventions-ledger.md

@@ -1,60 +0,0 @@
-# Recording proven conventions (the ledger, on GO)
-
-Loaded on demand by `$rite-seal` step 9. On a **GO** seal (and only then) promote the
-durable project conventions this feature *proved* into the local conventions ledger
-(`.devrites/conventions.md`). Orient reads it on later slices so the wright stops
-re-deriving the same idioms every time.
-
-The discipline mirrors DevRites' whole thesis: a convention is not "learned" until a
-**sealed slice proved it**. The ledger is evidence-gated, just like the seal.
-
-## What to promote
-
-Durable, reusable facts about *this codebase* that a future slice would otherwise
-re-discover: each as one entry:
-
-- **Commands:** the real build / test / typecheck / lint commands and how tests are run
-  (runner, file layout, co-location).
-- **Idioms:** naming + casing, layering, the error model, the result/exception style, the
-  http/client/data-access pattern.
-- **Placement:** where a kind of thing lives (where new endpoints / components / migrations go).
-- **Gotchas:** a non-obvious constraint this feature hit and proved (ordering requirement,
-  a "don't call X before Y", a framework quirk verified against the source).
-
-Do **not** promote: feature-specific details, one-off decisions (those live in
-`decisions.md`), anything you only assumed, or anything a reviewer flagged as wrong.
-If it isn't both *durable* and *proven by the evidence*, leave it out.
-
-## How (deterministic band, idempotent, graceful)
-
-For each convention, run the store. The confidence band is **earned** (computed from how
-many independent sealed slices corroborated the entry) never set by you. Re-sealing the
-same slice is idempotent (it won't double-count). If the `devrites-engine` binary is absent
-the step is skipped with a notice; the ledger is an enhancement, never a gate.
-
-```bash
-SLUG="$(cat .devrites/ACTIVE 2>/dev/null | tr -d '[:space:]')"
-if command -v devrites-engine >/dev/null 2>&1; then
-  devrites-engine conventions promote --slug "$SLUG" \
-    --key test-runner \
-    --kind test \
-    --statement "tests run with <runner>, co-located <pattern>" \
-    --evidence "evidence.md: <what proved it>"
-  # …one promote per durable convention this feature proved.
-else
-  echo "(conventions ledger unavailable — devrites-engine missing; skipping promote)"
-fi
-```
-
-- `--key` is a short kebab id for the convention (`test-runner`, `error-model`,
-  `http-client`, `endpoint-placement`); re-using a key on a later slice **corroborates** it
-  and raises the band.
-- `--statement` is one human-readable line; `--evidence` cites what in this feature proved it.
-
-## Authority is bounded by design
-
-A high band raises *confidence*, never *authority*. Per
-[`.agents/skills/devrites-lib/reference/standards/security.md`](../../devrites-lib/reference/standards/security.md) § Prompt-injection resistance, a
-ledger entry is untrusted data; at orient a **fresh observation of the live code always
-overrides** a stale entry. Promoting here is safe precisely because reading there is
-defensive.

package/pack/generated/codex/skills/rite-ship/reference/adr-promotion.md

@@ -1,9 +0,0 @@
-# ADR promotion
-
-Promote only durable architecture or interface decisions from `decisions.md`; slice-local
-calls remain in the archived workspace. If the project has no `docs/adr/`, ask before
-creating that convention.
-
-Write the next append-only `docs/adr/ADR-NNN.md` with Context, Decision, Status
-`accepted`, and Consequences. Never rewrite an accepted ADR; supersede it with a new ADR
-that links the old one. Add every promoted ADR to `touched-files.md` before shipping.

package/pack/generated/codex/skills/rite-ship/reference/ledger.md

@@ -1,56 +0,0 @@
-# Capability ledger: the living "what the system does now" layer
-
-The ledger is DevRites' cumulative spec store: `.devrites/specs/<capability>/spec.md`, a flat
-list of proven `### Requirement:` blocks per capability. Unlike a feature workspace (which is
-archived away on close) the ledger **persists** and accumulates, so feature N+1 starts from the
-proven contract of every feature before it instead of re-deriving from code.
-
-It lives outside `.devrites/work/`, so close-out's archival never touches it. It is written only
-here, on ship, and only from behavior that just passed the seal GO + evidence-freshness gate, so
-the ledger records *proven* truth, never merely proposed.
-
-## Fold semantics
-
-A feature's `spec.md` carries **deltas** grouped under capability-tagged H2 sections
-(`## ADDED Requirements — capability: <c>`, `MODIFIED`, `REMOVED`): see
-[`spec-grammar.md`](../../devrites-lib/reference/standards/spec-grammar.md) § Delta form.
-`devrites-engine ledger sync` groups them by capability and folds each into its ledger spec:
-
-- **ADDED** → append the block (upsert: replaces in place on a re-sync, so sync is idempotent)
-- **MODIFIED** → replace the same-named block with the full new version
-- **REMOVED** → delete the block (an emptied capability spec is dropped)
-
-Matching is by **requirement header identity**. A flat feature spec (no delta H2 sections) folds
-as all-ADDED into the capability named by the feature slug.
-
-## Sync workflow (rite-ship step 2b)
-
-Runs **before the commit** so the ledger change ships in the same commit as the code that proves it.
-
-1. Preview the fold: deterministic, zero-token:
-   ```bash
-   devrites-engine ledger diff .devrites/work/<slug>
-   ```
-2. **Opt-in and confirmed** (mirrors the design-memory rollup): present the option set (default
-   is to sync, since a shipped feature's proven behavior belongs in the ledger; the escape hatch
-   is skip (the feature ships without updating the living spec) a deliberate call, e.g. an
-   internal-only change with no capability contract).
-3. On yes:
-   ```bash
-   devrites-engine ledger sync .devrites/work/<slug>
-   ```
-   Then append each written `.devrites/specs/<capability>/spec.md` to `touched-files.md` so it is
-   staged and committed at the git ladder (step 4). Record the synced capabilities in `ship.md`.
-   **The ledger must be git-tracked.** Most of `.devrites/` is runtime state a project gitignores;
-   `specs/` is the exception (durable shared truth). If a `git status` / `git check-ignore` shows
-   the ledger path ignored, the commit would silently drop it: carve it out first:
-   `.devrites/*` + `!.devrites/specs/`. Surface this rather than shipping a ledger that never lands.
-4. Skip when the feature declares no requirements (a pure refactor / chore with no spec deltas).
-
-## Reading the ledger (earlier phases)
-
-`$rite-spec` and `$rite-adopt` consult the ledger before writing a new spec:
-```bash
-devrites-engine ledger list            # capabilities + requirement counts
-devrites-engine ledger show <capability>   # the proven contract to write deltas against
-```

package/scripts/build-binaries.sh

@@ -1,75 +0,0 @@
-#!/usr/bin/env bash
-# Cross-compile devrites-engine for every supported target and emit a sha256
-# sidecar per binary: the artifacts attached to the GitHub Release alongside the
-# pack tarball. Pure-Go (CGO_ENABLED=0) so every target builds
-# from one Linux runner with no cross-toolchain. The version is stamped into the
-# binary via -ldflags so `devrites-engine doctor` reports the release it came from.
-#
-# Usage: build-binaries.sh <version>          # version WITHOUT a leading "v"
-#
-# Output: dist/bin/devrites-<os>-<arch>[.exe] plus a "<sha>  <name>" .sha256 each.
-# Binary names are UNVERSIONED so the installer can fetch
-# github.com/<repo>/releases/latest/download/devrites-<os>-<arch> directly.
-set -euo pipefail
-
-VERSION="${1:-}"
-if [[ -z "$VERSION" ]]; then
-  echo "usage: build-binaries.sh <version>" >&2
-  exit 1
-fi
-
-ROOT="$(cd "$(dirname "$0")/.." && pwd)"
-ENGINE="$ROOT/engine"
-OUT="$ROOT/dist/bin"
-MODULE="github.com/devrites/devrites"
-
-if [[ ! -d "$ENGINE" ]]; then
-  echo "build-binaries: no engine/ directory at $ENGINE" >&2
-  exit 1
-fi
-
-# The release matrix: darwin arm64/amd64, linux amd64/arm64, windows amd64.
-TARGETS=(
-  "darwin/arm64"
-  "darwin/amd64"
-  "linux/amd64"
-  "linux/arm64"
-  "windows/amd64"
-)
-
-rm -rf "$OUT"
-mkdir -p "$OUT"
-
-sha256_of() {
-  # Emit "<sha256>  <filename>" (no path) so it verifies from any cwd.
-  local f="$1"
-  if command -v shasum >/dev/null 2>&1; then
-    shasum -a 256 "$f"
-  elif command -v sha256sum >/dev/null 2>&1; then
-    sha256sum "$f"
-  else
-    echo "build-binaries: no sha256 tool found" >&2
-    return 1
-  fi
-}
-
-echo "Cross-compiling devrites v${VERSION} (CGO_ENABLED=0)"
-cd "$ENGINE"
-
-for target in "${TARGETS[@]}"; do
-  os="${target%%/*}"
-  arch="${target##*/}"
-  name="devrites-${os}-${arch}"
-  [[ "$os" == "windows" ]] && name="${name}.exe"
-
-  echo "  → ${name}"
-  CGO_ENABLED=0 GOOS="$os" GOARCH="$arch" \
-    go build -trimpath \
-      -ldflags "-s -w -X ${MODULE}/internal/version.Version=v${VERSION}" \
-      -o "$OUT/$name" .
-
-  ( cd "$OUT" && sha256_of "$name" > "${name}.sha256" )
-done
-
-echo "Built $(find "$OUT" -maxdepth 1 -name 'devrites-*' ! -name '*.sha256' | wc -l | tr -d ' ') binaries in $OUT"
-ls -lh "$OUT"

package/scripts/build-release-tarball.sh

@@ -1,105 +0,0 @@
-#!/usr/bin/env bash
-# Build the archive that semantic-release attaches to a GitHub Release.
-# It extracts to `devrites-v<version>/` with the pack, engine, scripts,
-# documentation, and install tools.
-#
-# Usage: build-release-tarball.sh <version>
-set -euo pipefail
-
-VERSION="${1:-}"
-if [[ -z "$VERSION" ]]; then
-  echo "usage: build-release-tarball.sh <version>" >&2
-  exit 1
-fi
-if [[ ! "$VERSION" =~ ^[0-9A-Za-z][0-9A-Za-z._+-]*$ ]]; then
-  echo "error: version must be a portable release asset name" >&2
-  exit 1
-fi
-
-ROOT="$(cd "$(dirname "$0")/.." && pwd -P)"
-DIST="${DEVRITES_RELEASE_DIST_DIR:-$ROOT/dist}"
-NAME="devrites-v${VERSION}"
-
-cd "$ROOT"
-mkdir -p "$DIST"
-DIST="$(cd "$DIST" && pwd -P)"
-case "$DIST/" in
-  "$ROOT/pack/"* | "$ROOT/engine/"* | "$ROOT/scripts/"* | "$ROOT/mcp/"* | "$ROOT/docs/"*)
-    echo "error: release output directory overlaps the release payload" >&2
-    exit 1
-    ;;
-esac
-STAGE="$(mktemp -d "$DIST/.devrites-release-stage.XXXXXX")"
-cleanup() { rm -rf "$STAGE"; }
-trap cleanup EXIT
-
-echo "Building release tarball: ${NAME}.tar.gz"
-
-# Release contents.
-PAYLOAD=(
-  pack
-  engine
-  scripts
-  mcp
-  docs
-  install.sh
-  uninstall.sh
-  update.sh
-  README.md
-  CHANGELOG.md
-  LICENSE
-  SECURITY.md
-  NOTICE.md
-  CODE_OF_CONDUCT.md
-  CODEOWNERS
-  package.json
-)
-
-for item in "${PAYLOAD[@]}"; do
-  if [[ -e "$item" ]]; then
-    if git rev-parse --is-inside-work-tree >/dev/null 2>&1; then
-      while IFS= read -r -d '' path; do
-        [[ -e "$path" || -L "$path" ]] || continue
-        if [[ "$path" == engine/testdata/golden/* ]]; then
-          continue
-        fi
-        mkdir -p "$STAGE/$(dirname "$path")"
-        cp -P "$path" "$STAGE/$path"
-      done < <(git ls-files -z -- "$item")
-    else
-      cp -R "$item" "$STAGE/"
-    fi
-  fi
-done
-
-# Include the same prebuilt host artifacts as the npm package.
-DEVRITES_HOST_ARTIFACT_DIR="$STAGE/pack/generated" bash "$STAGE/scripts/build-host-artifacts.sh" >/dev/null
-
-# Remove development files copied with the payload.
-rm -rf "$STAGE/docs/internal" "$STAGE/scripts/.cache" 2>/dev/null || true
-
-(
-  cd "$ROOT/engine"
-  go run ./cmd/releasepack \
-    -root "$STAGE" \
-    -output "$DIST/${NAME}.tar.gz" \
-    -prefix "$NAME" \
-    -epoch "${SOURCE_DATE_EPOCH:-0}"
-)
-
-# Write a sibling checksum for install.sh to verify when available.
-# Store only "<sha256>  <filename>" so verification works from any directory.
-(
-  cd "$DIST"
-  if command -v shasum >/dev/null 2>&1; then
-    shasum -a 256 "${NAME}.tar.gz" > "${NAME}.tar.gz.sha256"
-  elif command -v sha256sum >/dev/null 2>&1; then
-    sha256sum "${NAME}.tar.gz" > "${NAME}.tar.gz.sha256"
-  else
-    echo "warning: no sha256 tool found; skipping ${NAME}.tar.gz.sha256" >&2
-  fi
-)
-
-echo "  → $DIST/${NAME}.tar.gz"
-ls -lh "$DIST/${NAME}.tar.gz"
-[[ -f "$DIST/${NAME}.tar.gz.sha256" ]] && { echo "  → $DIST/${NAME}.tar.gz.sha256"; cat "$DIST/${NAME}.tar.gz.sha256"; } || true

package/scripts/check-authority-drift.py

@@ -1,125 +0,0 @@
-#!/usr/bin/env python3
-"""Compare generated JSON authorities with their short documentation blocks."""
-
-import argparse
-import json
-import re
-import sys
-from pathlib import Path
-
-
-def table(headers, rows):
-    return "\n".join(
-        [
-            "| " + " | ".join(headers) + " |",
-            "| " + " | ".join("---" for _ in headers) + " |",
-            *["| " + " | ".join(row) + " |" for row in rows],
-        ]
-    )
-
-
-def replace_block(path, name, wanted, write):
-    text = path.read_text()
-    start = f"<!-- authority:{name}:start -->"
-    end = f"<!-- authority:{name}:end -->"
-    pattern = re.compile(re.escape(start) + r"\n.*?\n" + re.escape(end), re.DOTALL)
-    replacement = f"{start}\n{wanted}\n{end}"
-    if not pattern.search(text):
-        raise ValueError(f"{path}: missing {name} authority markers")
-    if pattern.search(text).group(0) == replacement:
-        return
-    if write:
-        path.write_text(pattern.sub(replacement, text, count=1))
-        return
-    raise ValueError(f"{path}: {name} authority block is stale")
-
-
-def main():
-    parser = argparse.ArgumentParser()
-    parser.add_argument("--root", type=Path, default=Path(__file__).resolve().parents[1])
-    parser.add_argument("--write", action="store_true")
-    args = parser.parse_args()
-    root = args.root.resolve()
-
-    manifest = json.loads((root / "engine/internal/state/workflow_manifest.json").read_text())
-    readiness = json.loads((root / "engine/internal/lib/readiness_contract.json").read_text())
-    phases = manifest["phases"]
-    reasons = readiness["reasons"]
-    policy = manifest["authorityPolicy"]
-
-    ids = [phase["id"] for phase in phases]
-    rights = [phase["transitionRight"] for phase in phases]
-    if len(ids) != len(set(ids)) or len(rights) != len(set(rights)):
-        raise ValueError("workflow manifest has duplicate phase IDs or transition rights")
-    resumes = {phase["id"]: phase.get("resumeVerb", "") for phase in phases}
-    if resumes.get("define") != "define" or resumes.get("plan") != "vet":
-        raise ValueError("workflow manifest violates ADR-0011 define/plan routing")
-    codes = [reason["code"] for reason in reasons]
-    if len(codes) != len(set(codes)):
-        raise ValueError("readiness contract has duplicate exit codes")
-
-    lifecycle = "`" + " → ".join(phase.upper() for phase in ids) + "`"
-    phase_rows = []
-    for phase in phases:
-        required = ", ".join(f"`{section}`" for section in phase.get("requiredSections", [])) or "*(none)*"
-        resume = f"`/rite-{phase['resumeVerb']}`" if phase.get("resumeVerb") else "*(terminal)*"
-        phase_rows.append([f"`{phase['id']}`", resume, required, phase["transitionRight"]])
-    reason_rows = [
-        [
-            f"`{reason['code']}`",
-            f"`{reason['id']}`",
-            reason["condition"],
-            f"`/rite-{reason['remediationVerb']}`" if reason["remediationVerb"] else "*(none)*",
-        ]
-        for reason in reasons
-    ]
-    tracking = (
-        "Git-tracked shared state: "
-        + ", ".join(f"`{path}`" for path in policy["trackedState"])
-        + ". Per-clone runtime state: "
-        + ", ".join(f"`{path}`" for path in policy["localState"])
-        + "."
-    )
-    clarify_rows = [[f"`{item['field']}`", item["policy"]] for item in manifest["clarifyReturnFields"]]
-
-    blocks = [
-        ("docs/quick-reference.md", "lifecycle", lifecycle),
-        ("docs/engine/state-schema.md", "schema-version", f"`schemaVersion: {manifest['schemaVersion']}`."),
-        (
-            "docs/engine/state-schema.md",
-            "phase-contract",
-            table(["phase", "normal resume", "required sections", "transition right"], phase_rows),
-        ),
-        ("docs/engine/state-schema.md", "state-tracking", tracking),
-        (
-            "docs/engine/state-schema.md",
-            "clarify-return-fields",
-            table(["field", "policy"], clarify_rows),
-        ),
-        (
-            "docs/cli.md",
-            "readiness-reasons",
-            table(["exit", "reason", "condition", "remediation"], reason_rows),
-        ),
-        ("SECURITY.md", "principles-trust", policy["principlesTrust"]),
-        (
-            "pack/.claude/skills/devrites-lib/reference/standards/core.md",
-            "principles-trust",
-            policy["principlesTrust"],
-        ),
-    ]
-    for relative, name, wanted in blocks:
-        replace_block(root / relative, name, wanted, args.write)
-
-    state_schema = (root / "docs/engine/state-schema.md").read_text()
-    if re.search(r"schema(?:Version| version| v)[: ]+1\b", state_schema, re.IGNORECASE):
-        raise ValueError("docs/engine/state-schema.md still claims schema v1")
-    print("authority-drift: current docs match workflow and readiness authorities")
-
-
-if __name__ == "__main__":
-    try:
-        main()
-    except (KeyError, OSError, ValueError, json.JSONDecodeError) as exc:
-        print(f"authority-drift: {exc}", file=sys.stderr)
-        sys.exit(1)