devrites 3.0.4 → 3.0.6

package/pack/generated/codex/skills/rite-ship/SKILL.md

@@ -11,13 +11,13 @@ This is the Codex mirror of a DevRites skill. In Codex:
 
 - Load DevRites engineering standards from `.agents/skills/devrites-lib/reference/standards/`. Read `.agents/skills/devrites-lib/reference/standards/core.md` before workflow work, then load the other `.agents/skills/devrites-lib/reference/standards/*.md` files exactly when this skill asks for them.
 - Use the installed `devrites-engine` binary as the canonical runtime helper surface for orientation, gates, and state mutation.
-- When this skill asks for a DevRites specialist or writer agent, **explicitly** spawn the matching Codex custom agent from `.codex/agents/devrites-*.toml` through Codex subagents (`spawn_agent`), then wait for its result and reconcile it as the skill instructs. Do not do the review inline just because the instruction to spawn is embedded here — Codex under-fires embedded spawn/skill instructions (openai/codex #23496), so treat the spawn as required, not optional.
-- The independence of a fresh-context subagent is the point. If Codex genuinely cannot spawn subagents in the current surface, run the documented inline fallback and **label the result an inline fallback, not an independent review** — an inline pass shares the calling context and is weaker evidence.
+- When this skill asks for a DevRites specialist or writer agent, **explicitly** spawn the matching Codex custom agent from `.codex/agents/devrites-*.toml` through Codex subagents (`spawn_agent`), then wait for its result and reconcile it as the skill instructs. Do not do the review inline just because the instruction to spawn is embedded here: Codex under-fires embedded spawn/skill instructions (openai/codex #23496), so treat the spawn as required, not optional.
+- The independence of a fresh-context subagent is the point. If Codex genuinely cannot spawn subagents in the current surface, run the documented inline fallback and **label the result an inline fallback, not an independent review**: an inline pass shares the calling context and is weaker evidence.
 - Codex project hooks are installed in `.codex/hooks.json`. Review and trust them with `/hooks` before relying on hook enforcement.
-- When this skill asks a HITL question via `AskUserQuestion`: Codex's equivalent (`request_user_input`) exists only in Plan mode. Outside Plan mode, render the option set as a plain numbered list in chat and **end the turn** so the human answers — NEVER silently pick an option yourself; auto-picking is AFK's contract, gated by the `.devrites/AFK` sentinel.
+- When this skill asks a HITL question via `AskUserQuestion`: Codex's equivalent (`request_user_input`) exists only in Plan mode. Outside Plan mode, render the option set as a plain numbered list in chat and **end the turn** so the human answers: NEVER silently pick an option yourself; auto-picking is AFK's contract, gated by the `.devrites/AFK` sentinel.
 
 
-# $rite-ship — ship + close the task
+# $rite-ship: ship + close the task
 
 The final phase. `$rite-seal` **decides** GO/NO-GO; `$rite-ship` **executes** the
 irreversible git actions and **closes** the feature. **Read the active workspace
@@ -27,10 +27,10 @@ Refuses to ship unless `seal.md` records a **GO** verdict.
 
 ## Rules consulted (read on demand from `.agents/skills/devrites-lib/reference/standards/`)
 **Step 0:** Read `.agents/skills/devrites-lib/reference/standards/core.md` first. Then pull on demand:
-- `git-workflow.md` — Conventional Commits, atomic commits, the never-commit list.
-- `afk-hitl.md` — type-GO is the irreversible-action gate.
-- `definition-of-done.md` — final acceptance, evidence, drift, rollback, and documentation bar.
-- [`release/ship-checklist.md`](../devrites-lib/reference/standards/release/ship-checklist.md) — compact final ship and archive pass/fail sweep.
+- `git-workflow.md`: Conventional Commits, atomic commits, the never-commit list.
+- `afk-hitl.md`: type-GO is the irreversible-action gate.
+- `definition-of-done.md`: final acceptance, evidence, drift, rollback, and documentation bar.
+- [`release/ship-checklist.md`](../devrites-lib/reference/standards/release/ship-checklist.md): compact final ship and archive pass/fail sweep.
 
 ## Operating rules
 - **Seal GO is a precondition.** No GO in `seal.md` → stop, point at `$rite-seal`.
@@ -39,14 +39,14 @@ Refuses to ship unless `seal.md` records a **GO** verdict.
   deterministically by `devrites-engine evidence-fresh` in step 1 (exit 3 = STALE), not by eyeballing
   mtimes (see `.agents/skills/devrites-lib/reference/standards/development-workflow.md`).
 - **type-GO before anything irreversible.** Render the prompt verbatim and wait for
-  the literal `GO`. Last safety net — render it every time, even under auto-trigger.
+  the literal `GO`. Last safety net: render it every time, even under auto-trigger.
 - **Never delete the audit trail.** Closing *archives* the workspace; it never erases
   the `.md` files.
 
 ## Workflow
 1. **Orient.** Run `devrites-engine preamble` for deterministic workspace orientation.
    Then read `seal.md`, `state.md`, `spec.md`, `touched-files.md`, `evidence.md`, and
-   `design-brief.md` (if the feature is UI — the design-memory rollup in step 2a reads it).
+   `design-brief.md` (if the feature is UI: the design-memory rollup in step 2a reads it).
    Confirm the verdict is **GO**, then run the deterministic evidence-freshness gate rather than
    eyeballing mtimes (mirrors `$rite-seal`):
    ```bash
@@ -54,7 +54,7 @@ Refuses to ship unless `seal.md` records a **GO** verdict.
    ```
    **Exit 3 → STALE proof: STOP**, point at `$rite-prove` (a polish/review edit made after
    `$rite-prove` invalidates the proof). Not GO → stop with the single resume command.
-1a. **Health re-check (advisory).** Run the DevRites doctor before the irreversible ladder —
+1a. **Health re-check (advisory).** Run the DevRites doctor before the irreversible ladder:
    a stale `ACTIVE` or corrupt workspace here risks shipping or closing the wrong feature.
    Advisory: surface issues, don't block.
    ```bash
@@ -82,9 +82,9 @@ Refuses to ship unless `seal.md` records a **GO** verdict.
    ```
    **rc=3 → STOP**: do not type-GO, commit, push, or archive.
 3. **Render the type-GO prompt** ([reference/git-ship.md](reference/git-ship.md)) and
-   wait. Only the literal `GO` proceeds; anything else cancels — record the cancel in
+   wait. Only the literal `GO` proceeds; anything else cancels: record the cancel in
    `ship.md` and stop (do not retry without the user asking).
-4. On `GO`: run the git ladder — commit → push → tag / PR as applicable
+4. On `GO`: run the git ladder: commit → push → tag / PR as applicable
    ([reference/git-ship.md](reference/git-ship.md)). Capture the commit SHA(s),
    branch, and tag/PR URL.
 4a. **PR branch only.** Render the structured body from
@@ -111,12 +111,12 @@ Refuses to ship unless `seal.md` records a **GO** verdict.
 
 > **Mid-flight discipline.** When tempted to ship without a GO seal, skip the type-GO,
 > stage files outside `touched-files.md`, or delete the workspace instead of archiving
-> it — stop. See [`anti-patterns`](reference/anti-patterns.md); the gate exists for the
+> it: stop. See [`anti-patterns`](reference/anti-patterns.md); the gate exists for the
 > failure mode the ask misses.
 
 ## Output
 
-**Progress first** — run `devrites-engine progress`, then use the Shipped typed template from
+**Progress first**: run `devrites-engine progress`, then use the Shipped typed template from
 the shared completion reply contract
 ([`reply-contract.md` § Shipped](../devrites-lib/reference/reply-contract.md#shipped)).
 If the user declined type-GO: state that nothing shipped, the seal still reads GO, and

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

@@ -1,7 +1,7 @@
-# rite-ship — anti-patterns
+# rite-ship: anti-patterns
 
-Load this before any irreversible action — `git commit`, `push`, `tag`, publish, deploy
-— or when tempted to skip the close-out.
+Load this before any irreversible action: `git commit`, `push`, `tag`, publish, deploy,
+or when tempted to skip the close-out.
 
 Pack-wide rationalizations + red flags: see
 [standards/anti-patterns.md](../../devrites-lib/reference/standards/anti-patterns.md).
@@ -11,9 +11,9 @@ Pack-wide rationalizations + red flags: see
 | Excuse | Rebuttal |
 |---|---|
 | "Seal said GO, so I can just push." | A GO verdict is a decision, not authorization. **Render the type-GO prompt every time** and wait for the literal `GO`. |
-| "I'll push the tag now; type-GO is a formality." | Type-GO is the last safety net before an irreversible action. Always render it — even under auto-trigger. |
+| "I'll push the tag now; type-GO is a formality." | Type-GO is the last safety net before an irreversible action. Always render it: even under auto-trigger. |
 | "`git add -A` is faster than listing touched files." | Stage only what's in `touched-files.md`. `-A` sweeps secrets, scratch files, and out-of-scope edits into the ship. |
-| "The evidence is probably still good." | If any touched file changed after `evidence.md`, the proof is stale — stop and re-prove. Ship on fresh evidence only. |
+| "The evidence is probably still good." | If any touched file changed after `evidence.md`, the proof is stale: stop and re-prove. Ship on fresh evidence only. |
 | "Delete the workspace, the feature's done." | Closing **archives** the workspace (`.devrites/archive/<slug>/`); it never deletes the audit trail. |
 
 ## Red Flags

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

@@ -1,4 +1,4 @@
-# Close-out — archive the workspace, free the active slot
+# Close-out: archive the workspace, free the active slot
 
 Closing a feature means it stops being the *active* work, not that its record is
 deleted. DevRites keeps the full audit trail; it just moves out of the live path.
@@ -28,7 +28,7 @@ deleted. DevRites keeps the full audit trail; it just moves out of the live path
 
 To resume archived work, move it back:
 `mv .devrites/archive/<slug> .devrites/work/<slug>` and write `<slug>` into
-`.devrites/ACTIVE`. Nothing is lost — close-out is reversible by design.
+`.devrites/ACTIVE`. Nothing is lost: close-out is reversible by design.
 
 ## Cross-feature retro
 

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

@@ -1,4 +1,4 @@
-# Design memory — roll proven design language into project `DESIGN.md`
+# Design memory: roll proven design language into project `DESIGN.md`
 
 Optional, UI-only step at `$rite-ship`. A feature's design decisions live in its
 feature-scoped `design-brief.md` and are thrown away when the workspace archives. **Design
@@ -6,45 +6,45 @@ memory** is the deliberate exception: when a UI feature ships, roll the design l
 *proved* up into a project-level `DESIGN.md`, so the next feature's `devrites-ux-shape`
 inherits the system instead of re-discovering it.
 
-The consumers already exist — `devrites-ux-shape` §1 and
+The consumers already exist: `devrites-ux-shape` §1 and
 `devrites-frontend-craft/reference/design-references.md` both read `DESIGN.md` when present.
 This step is the missing **producer**. It closes the loop: feature N seals its design
 language → feature N+1 builds to it.
 
 ## When it runs
 - **UI features only.** No UI in the diff → skip silently.
-- **At ship, GO sealed, after the git plan, before type-GO** (step 2a) — so the user sees
+- **At ship, GO sealed, after the git plan, before type-GO** (step 2a), so the user sees
   the full staged change set (code + `DESIGN.md`) under the single type-GO that ships it.
 - **Opt-in and confirmed.** Persisting to a project-wide artifact is outside feature scope
-  (`standards/core.md` rule 7) — so it is *never silent*. Present a ranked option set
-  (`standards/afk-hitl.md` — Option set); **default is skip**. The user opts to persist.
+  (`standards/core.md` rule 7), so it is *never silent*. Present a ranked option set
+  (see [`afk-hitl.md`](../../devrites-lib/reference/standards/afk-hitl.md), "Option set");
+  **default is skip**. The user opts to persist.
 - **AFK**: first-time `DESIGN.md` *creation* is treated as a `validating` gate (a new
-  persistent project artifact) — propose + queue, don't auto-create. An *append* to an
+  persistent project artifact): propose + queue, don't auto-create. An *append* to an
   existing `DESIGN.md` is `advisory` and may auto-proceed when `allow_gates` permits, since
   it only adds evidence-proven entries.
 
 ## Inputs (proven only)
-- `design-brief.md` — direction, color strategy, **calibration** (density / motion), key
+- `design-brief.md`: direction, color strategy, **calibration** (density / motion), key
   states, named anchors, and the per-slice **Build-time refinements**.
-- The **final diff** + `touched-files.md` — what tokens / components / states *actually
-  shipped* (the evidence). Roll up only what the diff proves, not what the brief intended.
-- Existing `DESIGN.md` if present — the merge target.
+- The **final diff** + `touched-files.md`: what tokens / components / states *shipped* (the evidence). Roll up only what the diff proves, not what the brief intended.
+- Existing `DESIGN.md` if present: the merge target.
 
-## What to roll up — the project's *converged* system, evidence-gated
+## What to roll up: the project's *converged* system, evidence-gated
 Only entries the shipped, proven feature establishes. Each is durable, cross-feature design
-language — not this feature's one-off choices.
-- **Tokens introduced + used** — new color roles / spacing steps / type steps / elevation
+language, not this feature's one-off choices.
+- **Tokens introduced + used:** new color roles / spacing steps / type steps / elevation
   / radius that shipped and are reusable. Names and values, mirrored from the code.
-- **Color strategy + calibration baseline** — the strategy (Restrained / Committed / …) and
+- **Color strategy + calibration baseline:** the strategy (Restrained / Committed / …) and
   density / motion the project keeps landing on; note a deviation as a deviation, not a new
   default.
 - **Type & spacing scales** in actual use; **motion** classes + easing; **materiality**
   (elevation set, hairline usage, glass / texture policy).
-- **Component behaviors** — for each shared component this feature established or extended:
+- **Component behaviors:** for each shared component this feature established or extended:
   the states it ships and its interaction model. Grows one feature at a time.
-- **Named-anchor lineage** — the anchors features steered toward, so later work stays
+- **Named-anchor lineage:** the anchors features steered toward, so later work stays
   coherent with what's already built.
-- **Anti-slop exceptions** — any banned default the project *intentionally* uses (with the
+- **Anti-slop exceptions:** any banned default the project *intentionally* uses (with the
   why), so build / polish don't "correct" a deliberate choice.
 
 ## Merge discipline
@@ -55,14 +55,14 @@ language — not this feature's one-off choices.
 - **Never invent.** If the feature didn't prove it, it doesn't go in. `DESIGN.md` is design
   *memory*, not design *aspiration*.
 - **Attribute + keep lean.** Tag each new entry with the feature slug so the lineage is
-  legible; one good line beats a paragraph. The file is read every future spec — keep it
+  legible; one good line beats a paragraph. The file is read every future spec: keep it
   scannable.
 
 ## How it commits
 `DESIGN.md` is a tracked project artifact, so it ships **in the feature commit**:
 1. Write / update `<project-root>/DESIGN.md` from the template below.
 2. **Append `DESIGN.md` to `touched-files.md`** so the existing ship commit-scoping (SKILL
-   steps 2 + 4) stages it — the design-memory write rides the same commit and the same
+   steps 2 + 4) stages it: the design-memory write rides the same commit and the same
    type-GO, no second commit.
 3. Note the rollup in `ship.md` (what was added, or "design-memory: skipped by user").
 
@@ -111,10 +111,10 @@ Banned defaults this project *intentionally* uses, with the why (so build/polish
 ```
 
 ## NEVER (design memory)
-- Never roll up unattended on first creation — a new persistent project artifact is a
+- Never roll up unattended on first creation: a new persistent project artifact is a
   confirmed step, never an AFK silent write.
-- Never write an entry the feature didn't *prove* shipped — no aspirational tokens.
-- Never overwrite or silently reconcile a conflicting existing entry — surface it.
+- Never write an entry the feature didn't *prove* shipped: no aspirational tokens.
+- Never overwrite or silently reconcile a conflicting existing entry: surface it.
 - Never persist a feature-only one-off as if it were the project default.
 - Never add `DESIGN.md` to the commit without appending it to `touched-files.md` first
   (it would fall outside the ship's commit scope).

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

@@ -1,4 +1,4 @@
-# The irreversible ship — type-GO + git ladder
+# The irreversible ship: type-GO + git ladder
 
 `$rite-ship` is the only DevRites phase that runs actions that cannot be undone
 silently. The seal verdict authorizes the *decision*; this prompt authorizes the
@@ -17,7 +17,7 @@ Type "GO" exactly to proceed. Anything else cancels.
 ```
 
 Rules for the prompt:
-- Render it **every time**, even with auto-trigger enabled — this is the last net.
+- Render it **every time**, even with auto-trigger enabled. This is the last net.
 - Only the literal string `GO` (no quotes) proceeds. `y`, `yes`, `go` (lowercase),
   `ok`, `sure`, `do it`, or anything else → cancel, record the cancel in `ship.md`
   as "user declined irreversible step at <ts>", and stop.
@@ -29,10 +29,10 @@ Rules for the prompt:
 Follow `.agents/skills/devrites-lib/reference/standards/git-workflow.md` and the project's own convention. Do not invent
 a release flow the project doesn't use.
 
-0. **Collapse checkpoints** (only if checkpoint mode ran — see
+0. **Collapse checkpoints** (only if checkpoint mode ran: see
    [rite-build/reference/checkpoint.md](../../rite-build/reference/checkpoint.md)). Local
    `WIP(<slug>)` commits are scratch; fold them into the working tree so the ship is one
-   atomic feature commit. `reset --soft` moves only the branch pointer — index and worktree
+   atomic feature commit. `reset --soft` moves only the branch pointer: index and worktree
    are untouched, so no change is ever lost:
    ```bash
    base=$(git rev-parse --abbrev-ref '@{upstream}' 2>/dev/null) || base=main
@@ -47,7 +47,7 @@ a release flow the project doesn't use.
 1. **Stage** only the files in `touched-files.md`. Never `git add -A`; never stage
    secrets, `.env`, or out-of-scope files (see the never-commit list in `git-workflow.md`).
 2. **Commit** with a Conventional Commit message derived from the feature (`feat(scope):
-   …` / `fix(scope): …`). Atomic — one logical change. Put the *why* in the body.
+   …` / `fix(scope): …`). Atomic: one logical change. Put the *why* in the body.
    For non-trivial features, append trailers from the workspace record:
    `Constraint:` from binding principles/irreversible risks, `Rejected:` from material alternatives,
    `Confidence:` from `seal.md`, `Scope-risk:` from the blast-radius scan, and `Not-tested:` for
@@ -55,7 +55,7 @@ a release flow the project doesn't use.
 3. **Push** to the target branch (the feature branch, or per the project's trunk
    convention).
 4. **Tag / PR** only if the project does it: cut a tag when the project tags releases,
-   or open a PR when the project reviews via PRs. Otherwise skip — pushing the branch
+   or open a PR when the project reviews via PRs. Otherwise skip: pushing the branch
    is the ship.
 
 Capture the resulting commit SHA(s), branch, and tag/PR URL for `ship.md`.
@@ -64,10 +64,10 @@ Capture the resulting commit SHA(s), branch, and tag/PR URL for `ship.md`.
 
 When this ship opens a PR, include only applicable sections:
 
-- **Summary** — what shipped and acceptance proven.
-- **Risk & rollback** — migration/auth/destructive risk and reversal from `seal.md`.
-- **What to scrutinize** — highest-blast-radius review stops.
-- **Evidence** — condensed proof plus the archived evidence bundle.
+- **Summary:** what shipped and acceptance proven.
+- **Risk & rollback:** migration/auth/destructive risk and reversal from `seal.md`.
+- **What to scrutinize:** highest-blast-radius review stops.
+- **Evidence:** condensed proof plus the archived evidence bundle.
 
 For an agent-owned staged rollout, apply [`rollout.md`](rollout.md). CI-owned deploys
 skip that branch. Delete empty sections rather than writing `N/A`.

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

@@ -1,18 +1,18 @@
-# Capability ledger — the living "what the system does now" layer
+# 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
+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
+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
+(`## 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:
 
@@ -27,13 +27,13 @@ as all-ADDED into the capability named by the feature slug.
 
 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:
+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
+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
+   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
@@ -43,7 +43,7 @@ Runs **before the commit** so the ledger change ships in the same commit as the
    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:
+   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).
 

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

@@ -1,43 +1,43 @@
-# Staged rollout & rollback — when the ship includes a live deploy
+# Staged rollout & rollback: when the ship includes a live deploy
 
 Opt-in. `$rite-ship`'s job ends at the git ladder (commit → push → tag / PR) and archiving the
 workspace; most projects deploy from CI on merge, and their pipeline owns the rollout. Reach for
 this reference only when the ship *itself* drives a live, staged production rollout the agent is
-responsible for. When it doesn't apply, skip it — the same no-op discipline as the rest of the pack.
+responsible for. When it doesn't apply, skip it: the same no-op discipline as the rest of the pack.
 
 The governing idea is the one already in [`git-workflow.md`](../../devrites-lib/reference/standards/git-workflow.md) and
 [`deprecation.md`](../../devrites-lib/reference/standards/deprecation.md): **a launch is only done when it's reversible,
 observable, and incremental.** Write the rollback plan *before* you deploy, not after it breaks.
 
 ## The rollback plan is a pre-condition
-Before the first byte ships, the plan exists, with a measured **time-to-rollback** per mechanism —
+Before the first byte ships, the plan exists, with a measured **time-to-rollback** per mechanism:
 feature flag < 1 min, redeploy < 5 min, DB rollback < 15 min. If the fastest reversal is slow, that
 is a launch risk to fix (add a flag) before shipping, not after. A destructive/migration step ships
 only with its rollback proven (expand→contract, [`deprecation.md`](../../devrites-lib/reference/standards/deprecation.md)).
 
-## Advance on evidence — the rollout decision thresholds
+## Advance on evidence: the rollout decision thresholds
 Stage the exposure and, at each stage, read the signals ([`observability.md`](../../devrites-lib/reference/standards/observability.md))
-against a fixed table — advance on green, hold on yellow, roll back on red. Don't eyeball it.
+against a fixed table: advance on green, hold on yellow, roll back on red. Don't eyeball it.
 
 | Signal | Green (advance) | Yellow (hold, investigate) | Red (roll back now) |
 |---|---|---|---|
-| Error rate | within ~10% of baseline | 10–100% over baseline | > 2× baseline |
-| p95 latency | within ~20% of baseline | 20–50% over | > 50% over |
+| Error rate | within ~10% of baseline | 10-100% over baseline | > 2× baseline |
+| p95 latency | within ~20% of baseline | 20-50% over | > 50% over |
 | Client JS errors | none new | < 0.1% of sessions | > 0.1% of sessions |
 | Business metric on the path | neutral or up | < 5% decline | > 5% decline |
 
 ## Stage the exposure, with a monitoring window at each step
-Internal/team → canary ~5% (hold 24–48h) → 25% → 50% → 100%, advancing only when **all** thresholds
+Internal/team → canary ~5% (hold 24-48h) → 25% → 50% → 100%, advancing only when **all** thresholds
 are green and you can still roll back to the previous percentage at any point. Data integrity or a
 security regression is an **immediate** rollback regardless of the table.
 
 ## Feature-flag hygiene
 Every flag has an owner and an expiry; test both states in CI; don't nest flags (state explodes);
-remove the flag and its dead branch within ~2 weeks of full rollout — a lingering flag is the
+remove the flag and its dead branch within ~2 weeks of full rollout: a lingering flag is the
 deprecation debt [`deprecation.md`](../../devrites-lib/reference/standards/deprecation.md) exists to prevent.
 
 ## Verify in the first hour (a runbook, not a vibe)
 Health endpoint returns 200 · the error dashboard is flat · latency within budget · one critical
-user flow driven by hand · logs/metrics/traces actually flowing ([`observability.md`](../../devrites-lib/reference/standards/observability.md)
+user flow driven by hand · logs/metrics/traces flowing ([`observability.md`](../../devrites-lib/reference/standards/observability.md)
 "verify the telemetry fires") · a rollback dry-run confirmed reversible. Record the observations in
-`ship.md` / `evidence.md` — an un-watched launch is an unproven one.
+`ship.md` / `evidence.md`: an un-watched launch is an unproven one.

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

@@ -28,6 +28,6 @@ workspace **before** close-out, so it travels into `.devrites/archive/<slug>/shi
 - <recorded follow-up + where it's tracked> | none
 ```
 
-Keep it short — it points at the existing audit files rather than restating them.
+Keep it short. It points at the existing audit files rather than restating them.
 The acceptance count must match `seal.md`; if they disagree, the seal is the source of
 truth and the ship should not have proceeded.