devrites 6.4.4 → 6.5.0

package/CHANGELOG.md

@@ -2,6 +2,22 @@
 
 All notable changes to DevRites are documented here. The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/) and DevRites adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). Releases are generated automatically by [semantic-release](https://semantic-release.gitbook.io/) from Conventional Commits on `main`.
 
+## [6.5.0](https://github.com/ViktorsBaikers/DevRites/compare/v6.4.5...v6.5.0) (2026-10-17)
+
+### Added
+
+* **devrites:** autocomplete lands local checkpoints without a prompt ([#121](https://github.com/ViktorsBaikers/DevRites/issues/121)) ([82831f2](https://github.com/ViktorsBaikers/DevRites/commit/82831f21c9556391452dbdcc4a9f68dd4d729ccf))
+
+### Fixed
+
+* **no-release:** treat uncompiled LSP errors as stale ([#120](https://github.com/ViktorsBaikers/DevRites/issues/120)) ([c1b0cb2](https://github.com/ViktorsBaikers/DevRites/commit/c1b0cb2fd929923f2edc00121b4d7ba8ad2c7c30))
+
+## [6.4.5](https://github.com/ViktorsBaikers/DevRites/compare/v6.4.4...v6.4.5) (2026-10-16)
+
+### Fixed
+
+* **devrites:** recheck packets carry only the role's own fingerprints ([#119](https://github.com/ViktorsBaikers/DevRites/issues/119)) ([781a9d4](https://github.com/ViktorsBaikers/DevRites/commit/781a9d473dd20ad10f02ca8d45793e8a8844ce46))
+
 ## [6.4.4](https://github.com/ViktorsBaikers/DevRites/compare/v6.4.3...v6.4.4) (2026-10-16)
 
 ### Fixed

package/README.md

@@ -31,7 +31,7 @@ history can't lose it. After you clear the conversation, switch hosts, or hand
 the feature to another engineer, the next session reads the same plan,
 decisions, and evidence before it continues.
 
-**Status:** [`v6.4.4`](https://github.com/ViktorsBaikers/DevRites/releases/tag/v6.4.4): see [`CHANGELOG.md`](CHANGELOG.md) for release notes.
+**Status:** [`v6.5.0`](https://github.com/ViktorsBaikers/DevRites/releases/tag/v6.5.0): see [`CHANGELOG.md`](CHANGELOG.md) for release notes.
 
 This is the latest published release; `main` may contain unreleased work.
 

package/docs/adr/0037-autocomplete-lands-local-checkpoints.md

@@ -0,0 +1,36 @@
+# ADR-0037: Autocomplete lands local checkpoints and self-resolves own scratch
+
+- **Status:** Accepted
+- **Date:** 2026-10-17
+- **Supersedes:** the ADR-0022 clause that put local checkpoint commits under fresh approval
+
+## Context
+
+ADR-0022 kept the rule that a seal GO, AFK mode, or autocomplete flag never
+authorizes an irreversible action, and listed `commit` with push, tag, and PR. The
+generated `AGENTS.md` block repeated it. The checkpoint protocol and
+`afk-hitl.md` already treated a local, unpushed `WIP(<slug>):` checkpoint as
+landing automatically and folded at `/rite-ship`. Hosts read the generated block as
+a host ask-first rule, so `/rite-autocomplete` stopped for a human at every slice
+checkpoint. On Boxset, 3 of 5 human stops in one day were local checkpoint approvals.
+The other 2 were safety gates for fixed `/tmp` paths that the writer had itself
+created, which filesystem birth times proved afterwards.
+
+## Decision
+
+- A local, unpushed `WIP(<slug>):` checkpoint commit made under the checkpoint
+  protocol (exact manifest staging, scope checks, no amend, reset, rebase, push, or
+  force) is not irreversible. It lands without a prompt in AFK and HITL runs.
+- Push, tag, PR, the ship commit, and any history rewrite remain irreversible and
+  keep fresh, explicit, per-attempt user approval.
+- A writer's overwrite or removal of a path outside the workspace that it created
+  itself in the same wave is not filesystem destruction. When birth times and
+  ownership prove it, the root records the evidence and continues. An unprovable
+  path still pauses.
+- A host repository's own ask-first commit rule still wins.
+
+## Consequences
+
+- `/rite-autocomplete` runs from Frame to a sealed, locally checkpointed feature
+  without per-slice human stops; `/rite-ship` remains the single human Git gate.
+- Each landed checkpoint stays reversible by the owner (`git reset`) until ship.

package/docs/adr/README.md

@@ -67,7 +67,7 @@ architecture; per-feature `decisions.md` files stay scoped to that feature.
 | [0019](0019-native-boundary-with-deterministic-gates.md) | Native boundary with deterministic gates | Accepted in part; semantic gates superseded by 0022, native writer and fresh approval retained | `engine/internal/gate/gate_test.go` |
 | [0020](0020-thin-engine-native-orchestration-boundary.md) | Thin engine and native host orchestration | Accepted in part; engine-surface/migration scope superseded by 0022, native orchestration retained | `tests/native-orchestration-contract-test.sh`, `engine/root_routing_test.go` |
 | [0021](0021-observable-workspace-compatibility.md) | Observable and reversible workspace compatibility | Superseded by 0022 | historical |
-| [0022](0022-native-orchestration-thin-engine.md) | Native orchestration with a thin deterministic engine | Accepted in part; snapshot/JSON-output clauses superseded by 0023; retained policy-command/install clauses narrowed by 0024; no-migrator normalization scope superseded by 0029 | `engine/root_routing_test.go`, `engine/internal/gate/gate_test.go`, `engine/internal/lib/cursor_compat_test.go`, `tests/native-orchestration-contract-test.sh` |
+| [0022](0022-native-orchestration-thin-engine.md) | Native orchestration with a thin deterministic engine | Accepted in part; snapshot/JSON-output clauses superseded by 0023; retained policy-command/install clauses narrowed by 0024; no-migrator normalization scope superseded by 0029; local WIP checkpoint approval superseded by 0037 | `engine/root_routing_test.go`, `engine/internal/gate/gate_test.go`, `engine/internal/lib/cursor_compat_test.go`, `tests/native-orchestration-contract-test.sh` |
 | [0023](0023-native-workspace-reads-line-output.md) | Native workspace reads and line-oriented engine output | Accepted in part; AFK/recovery/doctor retention superseded by 0024 | `engine/root_routing_test.go`, `engine/internal/gate/gate_test.go`, `tests/native-orchestration-contract-test.sh`, `tests/npx-pack-smoke.sh` |
 | [0024](0024-native-policy-offline-installer-boundary.md) | Native policy and offline installer boundary | Accepted in part; offline engine-update clause superseded by 0028 | `tests/native-orchestration-contract-test.sh`, `tests/phase-gate-routing-test.sh`, `tests/install-smoke.sh`, `tests/host-artifacts-test.sh` |
 | [0025](0025-evidence-gated-workspace-upgrades.md) | Evidence-gated semantic workspace upgrades | Accepted; no-migrator scope superseded by 0029 | `tests/phase-gate-routing-test.sh`, `tests/host-artifacts-test.sh` |
@@ -82,3 +82,4 @@ architecture; per-feature `decisions.md` files stay scoped to that feature.
 | [0034](0034-workflow-artifact-byte-corrections-get-code-review.md) | Workflow Artifact byte corrections get code review, not a plan loop | Accepted; narrows 0027's semantic review for contract-preserving Workflow Artifact byte fixes | `engine/internal/lib/drift_test.go` |
 | [0035](0035-claude-root-leaves-plan-mode.md) | The Claude root no longer runs in plan mode | Accepted; supersedes the Claude root plan-mode clauses of 0015/0017 | `tests/native-orchestration-contract-test.sh`, `engine/internal/install/install_test.go` |
 | [0036](0036-archive-recall-is-a-read-time-query.md) | Archive recall is a read-time query | Accepted; consistent with 0014/0022 (no engine index or store) | `engine/internal/lib/recall_test.go` |
+| [0037](0037-autocomplete-lands-local-checkpoints.md) | Autocomplete lands local checkpoints and self-resolves own scratch | Accepted; supersedes the ADR-0022 local-commit approval clause | `tests/authority-drift-test.sh` |

package/pack/.claude/skills/devrites-lib/reference/standards/afk-hitl.md

@@ -247,6 +247,11 @@ prove the old path unused before removing it, and a rollback for every destructi
 ([`deprecation.md`](deprecation.md)). The gate requires the safe path; it does not
 cancel the work.
 
+A writer's overwrite or removal of a path outside the workspace that it created itself in
+the same wave is not destruction. The root proves it with each path's birth time
+(`stat -c %W`) at or after the wave's `started` time and the writer's ownership, records
+that evidence, and continues without a question. Any path it cannot prove pauses as above.
+
 By default, AFK widens what's *automatic*; it never widens what's *irreversible*.
 
 Red checks remain hard non-advance build gates, but are not inherently irreversible or

package/pack/.claude/skills/devrites-lib/reference/standards/agents.md

@@ -86,6 +86,8 @@ session B's `claim check` passes at minute 35 over session A's still-running wri
 - Never message a running read-only leaf: a mid-run note voids it like a seeded packet.
   Root proof that lands after dispatch is weighed at reconciliation, not forwarded; a
   leaf gap it would close (e.g. "no independent runtime run") closes there.
+- A recheck packet lists only fingerprints that same role raised, plus the correction
+  diff. Another role's finding goes to that role's recheck, never a sibling's packet.
 - **Verify the packet is clean before admitting the account.** Confirm the returned packet/trace carries no host-injected context: an automatic memory/summary banner naming an earlier phase verdict (e.g. `past Temper PASS … next is /rite-define`) or harness reminder text seeds the pass and voids it. Cancel that account — never admit it — name the lost coverage, and re-dispatch with the host's context injection disabled for that child. Tool config changes that do not stop native child auto-injection are not a fix; verify on the next spawn instead of assuming.
 - A parent-context pass contributes attributed evidence but is not independent: exclude it from independent accounting and name the lost coverage.
 - Final severity is set at reconciliation after re-verifying the claimed consequence at the cited site (reviewer severity advisory); dismissals record a reason, and true facts about neighboring code route elsewhere instead of being dismissed.

package/pack/.claude/skills/devrites-lib/reference/standards/code-navigation.md

@@ -35,7 +35,9 @@ Review.
    oversized server, a pre-edit result, or a timed-out probe is `stale` (or `unavailable:
    <reason>` when none ran), never clean; fall back to the project typecheck/compile command. **Failing case:**
    the language server returns 0 diagnostics before the project finishes compiling and
-   the slice records "diagnostics clean".
+   the slice records "diagnostics clean". The converse holds: an error that the project
+   compile/typecheck of the current bytes does not reproduce is stale. Record it once
+   with that command's result and move on; never stub, suppress, or re-chase it.
 
 Skipping step 1 on a multi-file slice is a Build orient gap unless recorded
 `cannot_verify`.

package/pack/.claude/skills/rite-build/reference/checkpoint.md

@@ -10,7 +10,9 @@ not a gate.
 The checkpoint stays local, unpushed scratch folded at `/rite-ship`; where the
 host repository's own agent contract requires approval before commits — an
 ask-first rule such as this repository's `AGENTS.md` — that contract wins, and
-the orchestrator pauses for approval before landing it.
+the orchestrator pauses for approval before landing it. The DevRites-generated
+`AGENTS.md` block is not such a rule: under it the checkpoint lands without a
+prompt, AFK or HITL. Push, tag, PR, and the ship commit stay human-gated.
 
 ## When (and when not)
 

package/pack/generated/claude/skills/devrites-lib/reference/standards/afk-hitl.md

@@ -247,6 +247,11 @@ prove the old path unused before removing it, and a rollback for every destructi
 ([`deprecation.md`](deprecation.md)). The gate requires the safe path; it does not
 cancel the work.
 
+A writer's overwrite or removal of a path outside the workspace that it created itself in
+the same wave is not destruction. The root proves it with each path's birth time
+(`stat -c %W`) at or after the wave's `started` time and the writer's ownership, records
+that evidence, and continues without a question. Any path it cannot prove pauses as above.
+
 By default, AFK widens what's *automatic*; it never widens what's *irreversible*.
 
 Red checks remain hard non-advance build gates, but are not inherently irreversible or

package/pack/generated/claude/skills/devrites-lib/reference/standards/agents.md

@@ -86,6 +86,8 @@ session B's `claim check` passes at minute 35 over session A's still-running wri
 - Never message a running read-only leaf: a mid-run note voids it like a seeded packet.
   Root proof that lands after dispatch is weighed at reconciliation, not forwarded; a
   leaf gap it would close (e.g. "no independent runtime run") closes there.
+- A recheck packet lists only fingerprints that same role raised, plus the correction
+  diff. Another role's finding goes to that role's recheck, never a sibling's packet.
 - **Verify the packet is clean before admitting the account.** Confirm the returned packet/trace carries no host-injected context: an automatic memory/summary banner naming an earlier phase verdict (e.g. `past Temper PASS … next is /rite-define`) or harness reminder text seeds the pass and voids it. Cancel that account — never admit it — name the lost coverage, and re-dispatch with the host's context injection disabled for that child. Tool config changes that do not stop native child auto-injection are not a fix; verify on the next spawn instead of assuming.
 - A parent-context pass contributes attributed evidence but is not independent: exclude it from independent accounting and name the lost coverage.
 - Final severity is set at reconciliation after re-verifying the claimed consequence at the cited site (reviewer severity advisory); dismissals record a reason, and true facts about neighboring code route elsewhere instead of being dismissed.

package/pack/generated/claude/skills/devrites-lib/reference/standards/code-navigation.md

@@ -35,7 +35,9 @@ Review.
    oversized server, a pre-edit result, or a timed-out probe is `stale` (or `unavailable:
    <reason>` when none ran), never clean; fall back to the project typecheck/compile command. **Failing case:**
    the language server returns 0 diagnostics before the project finishes compiling and
-   the slice records "diagnostics clean".
+   the slice records "diagnostics clean". The converse holds: an error that the project
+   compile/typecheck of the current bytes does not reproduce is stale. Record it once
+   with that command's result and move on; never stub, suppress, or re-chase it.
 
 Skipping step 1 on a multi-file slice is a Build orient gap unless recorded
 `cannot_verify`.

package/pack/generated/claude/skills/rite-build/reference/checkpoint.md

@@ -10,7 +10,9 @@ not a gate.
 The checkpoint stays local, unpushed scratch folded at `/rite-ship`; where the
 host repository's own agent contract requires approval before commits — an
 ask-first rule such as this repository's `AGENTS.md` — that contract wins, and
-the orchestrator pauses for approval before landing it.
+the orchestrator pauses for approval before landing it. The DevRites-generated
+`AGENTS.md` block is not such a rule: under it the checkpoint lands without a
+prompt, AFK or HITL. Push, tag, PR, and the ship commit stay human-gated.
 
 ## When (and when not)
 

package/pack/generated/codex/AGENTS.md

@@ -20,7 +20,7 @@ This project has DevRites installed for both Claude Code and Codex.
 - Every generated specialist is hook-free. Among the lifecycle `devrites-*` specialists, `devrites-slice-wright` alone uses `default_permissions = ":workspace"` and every other specialist in that family uses `default_permissions = ":read-only"`. The shipped profiles are the full role-to-permission map; `/rite-doctor` step 3 checks them. Exact paths are instruction-enforced: put the project-relative paths in the task, wait for the wright, compare its file list and `git diff --name-only` with that contract, and reject any extra path. Never bypass the wright, widen its contract, or edit source in the root; the root must never recreate an engine dispatch bridge.
 - The explicit `/overhaul` skill ships its own `overhaul-*` agents outside the DevRites lifecycle. They use `default_permissions = ":workspace"`, are dispatched only by that skill, and follow its own approval gate and path contracts instead of the lifecycle writer rules above.
 - The explicit `/rite-fast` skill ships its own `fast-*` agents. Only `fast-builder` uses `default_permissions = ":workspace"`; `fast-planner`, `fast-checker`, and `fast-critic` stay `:read-only`. `/rite-fast` dispatches them itself and applies its own exact-path contracts.
-- A seal GO, AFK mode, or autocomplete flag never authorizes an irreversible action. Disclose the exact commit/push/tag/PR plan and obtain fresh explicit user approval for that attempt; any changed or retried plan needs fresh approval. Native host permission and sandbox prompts remain authoritative and cannot be inferred or bypassed.
+- A seal GO, AFK mode, or autocomplete flag never authorizes an irreversible action. Disclose the exact push/tag/PR/ship-commit plan and obtain fresh explicit user approval for that attempt; any changed or retried plan needs fresh approval. Local unpushed `WIP(<slug>):` checkpoint commits under the checkpoint protocol are not irreversible and land without a prompt. Native host permission and sandbox prompts remain authoritative and cannot be inferred or bypassed.
 
 ## Workflow contract
 

package/pack/generated/codex/skills/devrites-lib/reference/standards/afk-hitl.md

@@ -247,6 +247,11 @@ prove the old path unused before removing it, and a rollback for every destructi
 ([`deprecation.md`](deprecation.md)). The gate requires the safe path; it does not
 cancel the work.
 
+A writer's overwrite or removal of a path outside the workspace that it created itself in
+the same wave is not destruction. The root proves it with each path's birth time
+(`stat -c %W`) at or after the wave's `started` time and the writer's ownership, records
+that evidence, and continues without a question. Any path it cannot prove pauses as above.
+
 By default, AFK widens what's *automatic*; it never widens what's *irreversible*.
 
 Red checks remain hard non-advance build gates, but are not inherently irreversible or

package/pack/generated/codex/skills/devrites-lib/reference/standards/agents.md

@@ -86,6 +86,8 @@ session B's `claim check` passes at minute 35 over session A's still-running wri
 - Never message a running read-only leaf: a mid-run note voids it like a seeded packet.
   Root proof that lands after dispatch is weighed at reconciliation, not forwarded; a
   leaf gap it would close (e.g. "no independent runtime run") closes there.
+- A recheck packet lists only fingerprints that same role raised, plus the correction
+  diff. Another role's finding goes to that role's recheck, never a sibling's packet.
 - **Verify the packet is clean before admitting the account.** Confirm the returned packet/trace carries no host-injected context: an automatic memory/summary banner naming an earlier phase verdict (e.g. `past Temper PASS … next is $rite-define`) or harness reminder text seeds the pass and voids it. Cancel that account — never admit it — name the lost coverage, and re-dispatch with the host's context injection disabled for that child. Tool config changes that do not stop native child auto-injection are not a fix; verify on the next spawn instead of assuming.
 - A parent-context pass contributes attributed evidence but is not independent: exclude it from independent accounting and name the lost coverage.
 - Final severity is set at reconciliation after re-verifying the claimed consequence at the cited site (reviewer severity advisory); dismissals record a reason, and true facts about neighboring code route elsewhere instead of being dismissed.

package/pack/generated/codex/skills/devrites-lib/reference/standards/code-navigation.md

@@ -35,7 +35,9 @@ Review.
    oversized server, a pre-edit result, or a timed-out probe is `stale` (or `unavailable:
    <reason>` when none ran), never clean; fall back to the project typecheck/compile command. **Failing case:**
    the language server returns 0 diagnostics before the project finishes compiling and
-   the slice records "diagnostics clean".
+   the slice records "diagnostics clean". The converse holds: an error that the project
+   compile/typecheck of the current bytes does not reproduce is stale. Record it once
+   with that command's result and move on; never stub, suppress, or re-chase it.
 
 Skipping step 1 on a multi-file slice is a Build orient gap unless recorded
 `cannot_verify`.

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

@@ -10,7 +10,9 @@ not a gate.
 The checkpoint stays local, unpushed scratch folded at `$rite-ship`; where the
 host repository's own agent contract requires approval before commits — an
 ask-first rule such as this repository's `AGENTS.md` — that contract wins, and
-the orchestrator pauses for approval before landing it.
+the orchestrator pauses for approval before landing it. The DevRites-generated
+`AGENTS.md` block is not such a rule: under it the checkpoint lands without a
+prompt, AFK or HITL. Push, tag, PR, and the ship commit stay human-gated.
 
 ## When (and when not)
 

package/pack/generated/devin/AGENTS.md

@@ -15,7 +15,7 @@ This project has DevRites installed for Devin CLI.
 - Custom profiles do not inherit interactive tool grants, and background subagents auto-deny unapproved tools. Dispatch the write-capable wright in the foreground, or make sure its `edit`, `write`, and `exec` tools are approved first. Specialists cannot use `ask_user_question`; the root relays user questions and answers through the task text and returned result.
 - DevRites runtime helpers run through the installed `devrites-engine` binary.
 - Skills and agent profiles are loaded when a session starts. If they were installed while this session was open, restart the session or reopen the project before relying on them.
-- A seal GO, AFK mode, or autocomplete flag never authorizes an irreversible action. Disclose the exact commit/push/tag/PR plan and obtain fresh explicit user approval for that attempt; any changed or retried plan needs fresh approval.
+- A seal GO, AFK mode, or autocomplete flag never authorizes an irreversible action. Disclose the exact push/tag/PR/ship-commit plan and obtain fresh explicit user approval for that attempt; any changed or retried plan needs fresh approval. Local unpushed `WIP(<slug>):` checkpoint commits under the checkpoint protocol are not irreversible and land without a prompt.
 
 ## Workflow contract
 

package/pack/generated/devin/skills/devrites-lib/reference/standards/afk-hitl.md

@@ -247,6 +247,11 @@ prove the old path unused before removing it, and a rollback for every destructi
 ([`deprecation.md`](deprecation.md)). The gate requires the safe path; it does not
 cancel the work.
 
+A writer's overwrite or removal of a path outside the workspace that it created itself in
+the same wave is not destruction. The root proves it with each path's birth time
+(`stat -c %W`) at or after the wave's `started` time and the writer's ownership, records
+that evidence, and continues without a question. Any path it cannot prove pauses as above.
+
 By default, AFK widens what's *automatic*; it never widens what's *irreversible*.
 
 Red checks remain hard non-advance build gates, but are not inherently irreversible or

package/pack/generated/devin/skills/devrites-lib/reference/standards/agents.md

@@ -86,6 +86,8 @@ session B's `claim check` passes at minute 35 over session A's still-running wri
 - Never message a running read-only leaf: a mid-run note voids it like a seeded packet.
   Root proof that lands after dispatch is weighed at reconciliation, not forwarded; a
   leaf gap it would close (e.g. "no independent runtime run") closes there.
+- A recheck packet lists only fingerprints that same role raised, plus the correction
+  diff. Another role's finding goes to that role's recheck, never a sibling's packet.
 - **Verify the packet is clean before admitting the account.** Confirm the returned packet/trace carries no host-injected context: an automatic memory/summary banner naming an earlier phase verdict (e.g. `past Temper PASS … next is /rite-define`) or harness reminder text seeds the pass and voids it. Cancel that account — never admit it — name the lost coverage, and re-dispatch with the host's context injection disabled for that child. Tool config changes that do not stop native child auto-injection are not a fix; verify on the next spawn instead of assuming.
 - A parent-context pass contributes attributed evidence but is not independent: exclude it from independent accounting and name the lost coverage.
 - Final severity is set at reconciliation after re-verifying the claimed consequence at the cited site (reviewer severity advisory); dismissals record a reason, and true facts about neighboring code route elsewhere instead of being dismissed.

package/pack/generated/devin/skills/devrites-lib/reference/standards/code-navigation.md

@@ -35,7 +35,9 @@ Review.
    oversized server, a pre-edit result, or a timed-out probe is `stale` (or `unavailable:
    <reason>` when none ran), never clean; fall back to the project typecheck/compile command. **Failing case:**
    the language server returns 0 diagnostics before the project finishes compiling and
-   the slice records "diagnostics clean".
+   the slice records "diagnostics clean". The converse holds: an error that the project
+   compile/typecheck of the current bytes does not reproduce is stale. Record it once
+   with that command's result and move on; never stub, suppress, or re-chase it.
 
 Skipping step 1 on a multi-file slice is a Build orient gap unless recorded
 `cannot_verify`.

package/pack/generated/devin/skills/rite-build/reference/checkpoint.md

@@ -10,7 +10,9 @@ not a gate.
 The checkpoint stays local, unpushed scratch folded at `/rite-ship`; where the
 host repository's own agent contract requires approval before commits — an
 ask-first rule such as this repository's `AGENTS.md` — that contract wins, and
-the orchestrator pauses for approval before landing it.
+the orchestrator pauses for approval before landing it. The DevRites-generated
+`AGENTS.md` block is not such a rule: under it the checkpoint lands without a
+prompt, AFK or HITL. Push, tag, PR, and the ship commit stay human-gated.
 
 ## When (and when not)
 

package/pack/generated/omp/skills/devrites-lib/reference/standards/afk-hitl.md

@@ -247,6 +247,11 @@ prove the old path unused before removing it, and a rollback for every destructi
 ([`deprecation.md`](deprecation.md)). The gate requires the safe path; it does not
 cancel the work.
 
+A writer's overwrite or removal of a path outside the workspace that it created itself in
+the same wave is not destruction. The root proves it with each path's birth time
+(`stat -c %W`) at or after the wave's `started` time and the writer's ownership, records
+that evidence, and continues without a question. Any path it cannot prove pauses as above.
+
 By default, AFK widens what's *automatic*; it never widens what's *irreversible*.
 
 Red checks remain hard non-advance build gates, but are not inherently irreversible or

package/pack/generated/omp/skills/devrites-lib/reference/standards/agents.md

@@ -86,6 +86,8 @@ session B's `claim check` passes at minute 35 over session A's still-running wri
 - Never message a running read-only leaf: a mid-run note voids it like a seeded packet.
   Root proof that lands after dispatch is weighed at reconciliation, not forwarded; a
   leaf gap it would close (e.g. "no independent runtime run") closes there.
+- A recheck packet lists only fingerprints that same role raised, plus the correction
+  diff. Another role's finding goes to that role's recheck, never a sibling's packet.
 - **Verify the packet is clean before admitting the account.** Confirm the returned packet/trace carries no host-injected context: an automatic memory/summary banner naming an earlier phase verdict (e.g. `past Temper PASS … next is /rite-define`) or harness reminder text seeds the pass and voids it. Cancel that account — never admit it — name the lost coverage, and re-dispatch with the host's context injection disabled for that child. Tool config changes that do not stop native child auto-injection are not a fix; verify on the next spawn instead of assuming.
 - A parent-context pass contributes attributed evidence but is not independent: exclude it from independent accounting and name the lost coverage.
 - Final severity is set at reconciliation after re-verifying the claimed consequence at the cited site (reviewer severity advisory); dismissals record a reason, and true facts about neighboring code route elsewhere instead of being dismissed.

package/pack/generated/omp/skills/devrites-lib/reference/standards/code-navigation.md

@@ -35,7 +35,9 @@ Review.
    oversized server, a pre-edit result, or a timed-out probe is `stale` (or `unavailable:
    <reason>` when none ran), never clean; fall back to the project typecheck/compile command. **Failing case:**
    the language server returns 0 diagnostics before the project finishes compiling and
-   the slice records "diagnostics clean".
+   the slice records "diagnostics clean". The converse holds: an error that the project
+   compile/typecheck of the current bytes does not reproduce is stale. Record it once
+   with that command's result and move on; never stub, suppress, or re-chase it.
 
 Skipping step 1 on a multi-file slice is a Build orient gap unless recorded
 `cannot_verify`.

package/pack/generated/omp/skills/rite-build/reference/checkpoint.md

@@ -10,7 +10,9 @@ not a gate.
 The checkpoint stays local, unpushed scratch folded at `/rite-ship`; where the
 host repository's own agent contract requires approval before commits — an
 ask-first rule such as this repository's `AGENTS.md` — that contract wins, and
-the orchestrator pauses for approval before landing it.
+the orchestrator pauses for approval before landing it. The DevRites-generated
+`AGENTS.md` block is not such a rule: under it the checkpoint lands without a
+prompt, AFK or HITL. Push, tag, PR, and the ship commit stay human-gated.
 
 ## When (and when not)
 

package/pack/generated/pi/AGENTS.md

@@ -16,7 +16,7 @@ This project has DevRites installed for pi.
 - The explicit `/rite-fast` skill ships its own `fast-*` agents. Only `fast-builder` carries write tools; `fast-planner`, `fast-checker`, and `fast-critic` stay read-only. `/rite-fast` dispatches them itself and applies its own exact-path contracts.
 - DevRites runtime helpers run through the installed `devrites-engine` binary.
 - Installed `.pi/` content loads only after the project is trusted. If pi has not trusted this project, the skills, agents, and prompts above are not active.
-- A seal GO, AFK mode, or autocomplete flag never authorizes an irreversible action. Disclose the exact commit/push/tag/PR plan and obtain fresh explicit user approval for that attempt; any changed or retried plan needs fresh approval.
+- A seal GO, AFK mode, or autocomplete flag never authorizes an irreversible action. Disclose the exact push/tag/PR/ship-commit plan and obtain fresh explicit user approval for that attempt; any changed or retried plan needs fresh approval. Local unpushed `WIP(<slug>):` checkpoint commits under the checkpoint protocol are not irreversible and land without a prompt.
 
 ## Workflow contract
 

package/pack/generated/pi/skills/devrites-lib/reference/standards/afk-hitl.md

@@ -247,6 +247,11 @@ prove the old path unused before removing it, and a rollback for every destructi
 ([`deprecation.md`](deprecation.md)). The gate requires the safe path; it does not
 cancel the work.
 
+A writer's overwrite or removal of a path outside the workspace that it created itself in
+the same wave is not destruction. The root proves it with each path's birth time
+(`stat -c %W`) at or after the wave's `started` time and the writer's ownership, records
+that evidence, and continues without a question. Any path it cannot prove pauses as above.
+
 By default, AFK widens what's *automatic*; it never widens what's *irreversible*.
 
 Red checks remain hard non-advance build gates, but are not inherently irreversible or

package/pack/generated/pi/skills/devrites-lib/reference/standards/agents.md

@@ -86,6 +86,8 @@ session B's `claim check` passes at minute 35 over session A's still-running wri
 - Never message a running read-only leaf: a mid-run note voids it like a seeded packet.
   Root proof that lands after dispatch is weighed at reconciliation, not forwarded; a
   leaf gap it would close (e.g. "no independent runtime run") closes there.
+- A recheck packet lists only fingerprints that same role raised, plus the correction
+  diff. Another role's finding goes to that role's recheck, never a sibling's packet.
 - **Verify the packet is clean before admitting the account.** Confirm the returned packet/trace carries no host-injected context: an automatic memory/summary banner naming an earlier phase verdict (e.g. `past Temper PASS … next is /rite-define`) or harness reminder text seeds the pass and voids it. Cancel that account — never admit it — name the lost coverage, and re-dispatch with the host's context injection disabled for that child. Tool config changes that do not stop native child auto-injection are not a fix; verify on the next spawn instead of assuming.
 - A parent-context pass contributes attributed evidence but is not independent: exclude it from independent accounting and name the lost coverage.
 - Final severity is set at reconciliation after re-verifying the claimed consequence at the cited site (reviewer severity advisory); dismissals record a reason, and true facts about neighboring code route elsewhere instead of being dismissed.

package/pack/generated/pi/skills/devrites-lib/reference/standards/code-navigation.md

@@ -35,7 +35,9 @@ Review.
    oversized server, a pre-edit result, or a timed-out probe is `stale` (or `unavailable:
    <reason>` when none ran), never clean; fall back to the project typecheck/compile command. **Failing case:**
    the language server returns 0 diagnostics before the project finishes compiling and
-   the slice records "diagnostics clean".
+   the slice records "diagnostics clean". The converse holds: an error that the project
+   compile/typecheck of the current bytes does not reproduce is stale. Record it once
+   with that command's result and move on; never stub, suppress, or re-chase it.
 
 Skipping step 1 on a multi-file slice is a Build orient gap unless recorded
 `cannot_verify`.

package/pack/generated/pi/skills/rite-build/reference/checkpoint.md

@@ -10,7 +10,9 @@ not a gate.
 The checkpoint stays local, unpushed scratch folded at `/rite-ship`; where the
 host repository's own agent contract requires approval before commits — an
 ask-first rule such as this repository's `AGENTS.md` — that contract wins, and
-the orchestrator pauses for approval before landing it.
+the orchestrator pauses for approval before landing it. The DevRites-generated
+`AGENTS.md` block is not such a rule: under it the checkpoint lands without a
+prompt, AFK or HITL. Push, tag, PR, and the ship commit stay human-gated.
 
 ## When (and when not)
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "devrites",
-  "version": "6.4.4",
+  "version": "6.5.0",
   "description": "DevRites: a disciplined senior-engineer workflow pack for Claude Code, Codex, omp, pi, and Devin CLI",
   "license": "SEE LICENSE IN LICENSE",
   "homepage": "https://github.com/ViktorsBaikers/DevRites#readme",

package/scripts/codex-generate.sh

@@ -111,7 +111,7 @@ This project has DevRites installed for both Claude Code and Codex.
 - Every generated specialist is hook-free. Among the lifecycle `devrites-*` specialists, `devrites-slice-wright` alone uses `default_permissions = ":workspace"` and every other specialist in that family uses `default_permissions = ":read-only"`. The shipped profiles are the full role-to-permission map; `/rite-doctor` step 3 checks them. Exact paths are instruction-enforced: put the project-relative paths in the task, wait for the wright, compare its file list and `git diff --name-only` with that contract, and reject any extra path. Never bypass the wright, widen its contract, or edit source in the root; the root must never recreate an engine dispatch bridge.
 - The explicit `/overhaul` skill ships its own `overhaul-*` agents outside the DevRites lifecycle. They use `default_permissions = ":workspace"`, are dispatched only by that skill, and follow its own approval gate and path contracts instead of the lifecycle writer rules above.
 - The explicit `/rite-fast` skill ships its own `fast-*` agents. Only `fast-builder` uses `default_permissions = ":workspace"`; `fast-planner`, `fast-checker`, and `fast-critic` stay `:read-only`. `/rite-fast` dispatches them itself and applies its own exact-path contracts.
-- A seal GO, AFK mode, or autocomplete flag never authorizes an irreversible action. Disclose the exact commit/push/tag/PR plan and obtain fresh explicit user approval for that attempt; any changed or retried plan needs fresh approval. Native host permission and sandbox prompts remain authoritative and cannot be inferred or bypassed.
+- A seal GO, AFK mode, or autocomplete flag never authorizes an irreversible action. Disclose the exact push/tag/PR/ship-commit plan and obtain fresh explicit user approval for that attempt; any changed or retried plan needs fresh approval. Local unpushed `WIP(<slug>):` checkpoint commits under the checkpoint protocol are not irreversible and land without a prompt. Native host permission and sandbox prompts remain authoritative and cannot be inferred or bypassed.
 
 ## Workflow contract
 

package/scripts/devin-generate.sh

@@ -213,7 +213,7 @@ This project has DevRites installed for Devin CLI.
 - Custom profiles do not inherit interactive tool grants, and background subagents auto-deny unapproved tools. Dispatch the write-capable wright in the foreground, or make sure its `edit`, `write`, and `exec` tools are approved first. Specialists cannot use `ask_user_question`; the root relays user questions and answers through the task text and returned result.
 - DevRites runtime helpers run through the installed `devrites-engine` binary.
 - Skills and agent profiles are loaded when a session starts. If they were installed while this session was open, restart the session or reopen the project before relying on them.
-- A seal GO, AFK mode, or autocomplete flag never authorizes an irreversible action. Disclose the exact commit/push/tag/PR plan and obtain fresh explicit user approval for that attempt; any changed or retried plan needs fresh approval.
+- A seal GO, AFK mode, or autocomplete flag never authorizes an irreversible action. Disclose the exact push/tag/PR/ship-commit plan and obtain fresh explicit user approval for that attempt; any changed or retried plan needs fresh approval. Local unpushed `WIP(<slug>):` checkpoint commits under the checkpoint protocol are not irreversible and land without a prompt.
 
 ## Workflow contract
 

package/scripts/pi-generate.sh

@@ -256,7 +256,7 @@ This project has DevRites installed for pi.
 - The explicit `/rite-fast` skill ships its own `fast-*` agents. Only `fast-builder` carries write tools; `fast-planner`, `fast-checker`, and `fast-critic` stay read-only. `/rite-fast` dispatches them itself and applies its own exact-path contracts.
 - DevRites runtime helpers run through the installed `devrites-engine` binary.
 - Installed `.pi/` content loads only after the project is trusted. If pi has not trusted this project, the skills, agents, and prompts above are not active.
-- A seal GO, AFK mode, or autocomplete flag never authorizes an irreversible action. Disclose the exact commit/push/tag/PR plan and obtain fresh explicit user approval for that attempt; any changed or retried plan needs fresh approval.
+- A seal GO, AFK mode, or autocomplete flag never authorizes an irreversible action. Disclose the exact push/tag/PR/ship-commit plan and obtain fresh explicit user approval for that attempt; any changed or retried plan needs fresh approval. Local unpushed `WIP(<slug>):` checkpoint commits under the checkpoint protocol are not irreversible and land without a prompt.
 
 ## Workflow contract