devrites 6.7.0 → 6.7.2

package/CHANGELOG.md

@@ -2,6 +2,18 @@
 
 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.7.2](https://github.com/ViktorsBaikers/DevRites/compare/v6.7.1...v6.7.2) (2026-10-17)
+
+### Fixed
+
+* **devrites:** reslice review re-admits the findings driving rounds ([#126](https://github.com/ViktorsBaikers/DevRites/issues/126)) ([3339ac4](https://github.com/ViktorsBaikers/DevRites/commit/3339ac40692f4a3fb0a7efb8677c1770c613504e))
+
+## [6.7.1](https://github.com/ViktorsBaikers/DevRites/compare/v6.7.0...v6.7.1) (2026-10-17)
+
+### Fixed
+
+* **devrites:** findings need a trigger the feature really faces ([#125](https://github.com/ViktorsBaikers/DevRites/issues/125)) ([f577aad](https://github.com/ViktorsBaikers/DevRites/commit/f577aad46dcf4aaa53a138c8a86662dca646b9a1))
+
 ## [6.7.0](https://github.com/ViktorsBaikers/DevRites/compare/v6.6.0...v6.7.0) (2026-10-17)
 
 ### Added

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.7.0`](https://github.com/ViktorsBaikers/DevRites/releases/tag/v6.7.0): see [`CHANGELOG.md`](CHANGELOG.md) for release notes.
+**Status:** [`v6.7.2`](https://github.com/ViktorsBaikers/DevRites/releases/tag/v6.7.2): see [`CHANGELOG.md`](CHANGELOG.md) for release notes.
 
 This is the latest published release; `main` may contain unreleased work.
 

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

@@ -119,7 +119,15 @@ Basis: <files read · commands run to reach this finding>
   quote like the `file:line` quote. No anchor, or one the defect does not break,
   admits the row as Suggestion logged `Deferred: <claim> — no spec anchor` for an
   optional follow-up slice; it never drives a repair round. Hardening no spec line
-  asks for is a Suggestion, however plausible.
+  asks for is a Suggestion, however plausible. The `when` must also be reachable:
+  a hostile actor enters only through a trust boundary the feature really has
+  (users, network, external systems, untrusted files). A trigger that needs one it
+  never faces — the code under test forging its own evidence, a tampering second
+  user on a single-owner dev host, a swapped remote daemon under a local dev tool —
+  is a Suggestion too. So is an environment state the feature's declared
+  environment does not have (a mount option, kernel setting or daemon location
+  absent from the target host): guard against it only when the spec names it.
+  A finding never pulls a deferred slice's scope forward.
 - **`no-findings`:** `No-findings:` names checks and inspected evidence. Bare
   pass, empty list, or “looks good” is malformed.
 - **`gap`:** names missing/unreadable/stale input; skipped/failed required check;

package/pack/.claude/skills/rite-build/reference/wright-dispatch.md

@@ -105,7 +105,10 @@ through the launch barrier — `devrites-engine dispatch <slug> open --phase bui
 <slice-id> --role slice-wright --slice <SLICE-ID> --contract <file>` (it refuses a
 contract that forbids writer-safe checks or names none), then `start` with the host handle, `seal`, and
 `return` on completion (auto-records dispatch/return metrics). Every 5 wright
-rounds on one slice, `open` blocks for a reslice review: propose an
+rounds on one slice, `open` blocks for a reslice review. First re-admit each
+finding still driving rounds under the Proportionality rule of
+[agents.md § Result admission](../../devrites-lib/reference/standards/agents.md#result-admission): one without a broken anchor or a reachable trigger becomes a
+Suggestion and drives no further round. Then propose an
 acceptance-preserving split (`root_no_change_analysis` → `FOLD` per
 [acceptance-preserving-reslice](../../devrites-lib/reference/standards/acceptance-preserving-reslice.md);
 open findings move to the new slice owning their paths), or record

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

@@ -119,7 +119,15 @@ Basis: <files read · commands run to reach this finding>
   quote like the `file:line` quote. No anchor, or one the defect does not break,
   admits the row as Suggestion logged `Deferred: <claim> — no spec anchor` for an
   optional follow-up slice; it never drives a repair round. Hardening no spec line
-  asks for is a Suggestion, however plausible.
+  asks for is a Suggestion, however plausible. The `when` must also be reachable:
+  a hostile actor enters only through a trust boundary the feature really has
+  (users, network, external systems, untrusted files). A trigger that needs one it
+  never faces — the code under test forging its own evidence, a tampering second
+  user on a single-owner dev host, a swapped remote daemon under a local dev tool —
+  is a Suggestion too. So is an environment state the feature's declared
+  environment does not have (a mount option, kernel setting or daemon location
+  absent from the target host): guard against it only when the spec names it.
+  A finding never pulls a deferred slice's scope forward.
 - **`no-findings`:** `No-findings:` names checks and inspected evidence. Bare
   pass, empty list, or “looks good” is malformed.
 - **`gap`:** names missing/unreadable/stale input; skipped/failed required check;

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

@@ -105,7 +105,10 @@ through the launch barrier — `devrites-engine dispatch <slug> open --phase bui
 <slice-id> --role slice-wright --slice <SLICE-ID> --contract <file>` (it refuses a
 contract that forbids writer-safe checks or names none), then `start` with the host handle, `seal`, and
 `return` on completion (auto-records dispatch/return metrics). Every 5 wright
-rounds on one slice, `open` blocks for a reslice review: propose an
+rounds on one slice, `open` blocks for a reslice review. First re-admit each
+finding still driving rounds under the Proportionality rule of
+[agents.md § Result admission](../../devrites-lib/reference/standards/agents.md#result-admission): one without a broken anchor or a reachable trigger becomes a
+Suggestion and drives no further round. Then propose an
 acceptance-preserving split (`root_no_change_analysis` → `FOLD` per
 [acceptance-preserving-reslice](../../devrites-lib/reference/standards/acceptance-preserving-reslice.md);
 open findings move to the new slice owning their paths), or record

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

@@ -119,7 +119,15 @@ Basis: <files read · commands run to reach this finding>
   quote like the `file:line` quote. No anchor, or one the defect does not break,
   admits the row as Suggestion logged `Deferred: <claim> — no spec anchor` for an
   optional follow-up slice; it never drives a repair round. Hardening no spec line
-  asks for is a Suggestion, however plausible.
+  asks for is a Suggestion, however plausible. The `when` must also be reachable:
+  a hostile actor enters only through a trust boundary the feature really has
+  (users, network, external systems, untrusted files). A trigger that needs one it
+  never faces — the code under test forging its own evidence, a tampering second
+  user on a single-owner dev host, a swapped remote daemon under a local dev tool —
+  is a Suggestion too. So is an environment state the feature's declared
+  environment does not have (a mount option, kernel setting or daemon location
+  absent from the target host): guard against it only when the spec names it.
+  A finding never pulls a deferred slice's scope forward.
 - **`no-findings`:** `No-findings:` names checks and inspected evidence. Bare
   pass, empty list, or “looks good” is malformed.
 - **`gap`:** names missing/unreadable/stale input; skipped/failed required check;

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

@@ -105,7 +105,10 @@ through the launch barrier — `devrites-engine dispatch <slug> open --phase bui
 <slice-id> --role slice-wright --slice <SLICE-ID> --contract <file>` (it refuses a
 contract that forbids writer-safe checks or names none), then `start` with the host handle, `seal`, and
 `return` on completion (auto-records dispatch/return metrics). Every 5 wright
-rounds on one slice, `open` blocks for a reslice review: propose an
+rounds on one slice, `open` blocks for a reslice review. First re-admit each
+finding still driving rounds under the Proportionality rule of
+[agents.md § Result admission](../../devrites-lib/reference/standards/agents.md#result-admission): one without a broken anchor or a reachable trigger becomes a
+Suggestion and drives no further round. Then propose an
 acceptance-preserving split (`root_no_change_analysis` → `FOLD` per
 [acceptance-preserving-reslice](../../devrites-lib/reference/standards/acceptance-preserving-reslice.md);
 open findings move to the new slice owning their paths), or record

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

@@ -119,7 +119,15 @@ Basis: <files read · commands run to reach this finding>
   quote like the `file:line` quote. No anchor, or one the defect does not break,
   admits the row as Suggestion logged `Deferred: <claim> — no spec anchor` for an
   optional follow-up slice; it never drives a repair round. Hardening no spec line
-  asks for is a Suggestion, however plausible.
+  asks for is a Suggestion, however plausible. The `when` must also be reachable:
+  a hostile actor enters only through a trust boundary the feature really has
+  (users, network, external systems, untrusted files). A trigger that needs one it
+  never faces — the code under test forging its own evidence, a tampering second
+  user on a single-owner dev host, a swapped remote daemon under a local dev tool —
+  is a Suggestion too. So is an environment state the feature's declared
+  environment does not have (a mount option, kernel setting or daemon location
+  absent from the target host): guard against it only when the spec names it.
+  A finding never pulls a deferred slice's scope forward.
 - **`no-findings`:** `No-findings:` names checks and inspected evidence. Bare
   pass, empty list, or “looks good” is malformed.
 - **`gap`:** names missing/unreadable/stale input; skipped/failed required check;

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

@@ -105,7 +105,10 @@ through the launch barrier — `devrites-engine dispatch <slug> open --phase bui
 <slice-id> --role slice-wright --slice <SLICE-ID> --contract <file>` (it refuses a
 contract that forbids writer-safe checks or names none), then `start` with the host handle, `seal`, and
 `return` on completion (auto-records dispatch/return metrics). Every 5 wright
-rounds on one slice, `open` blocks for a reslice review: propose an
+rounds on one slice, `open` blocks for a reslice review. First re-admit each
+finding still driving rounds under the Proportionality rule of
+[agents.md § Result admission](../../devrites-lib/reference/standards/agents.md#result-admission): one without a broken anchor or a reachable trigger becomes a
+Suggestion and drives no further round. Then propose an
 acceptance-preserving split (`root_no_change_analysis` → `FOLD` per
 [acceptance-preserving-reslice](../../devrites-lib/reference/standards/acceptance-preserving-reslice.md);
 open findings move to the new slice owning their paths), or record

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

@@ -119,7 +119,15 @@ Basis: <files read · commands run to reach this finding>
   quote like the `file:line` quote. No anchor, or one the defect does not break,
   admits the row as Suggestion logged `Deferred: <claim> — no spec anchor` for an
   optional follow-up slice; it never drives a repair round. Hardening no spec line
-  asks for is a Suggestion, however plausible.
+  asks for is a Suggestion, however plausible. The `when` must also be reachable:
+  a hostile actor enters only through a trust boundary the feature really has
+  (users, network, external systems, untrusted files). A trigger that needs one it
+  never faces — the code under test forging its own evidence, a tampering second
+  user on a single-owner dev host, a swapped remote daemon under a local dev tool —
+  is a Suggestion too. So is an environment state the feature's declared
+  environment does not have (a mount option, kernel setting or daemon location
+  absent from the target host): guard against it only when the spec names it.
+  A finding never pulls a deferred slice's scope forward.
 - **`no-findings`:** `No-findings:` names checks and inspected evidence. Bare
   pass, empty list, or “looks good” is malformed.
 - **`gap`:** names missing/unreadable/stale input; skipped/failed required check;

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

@@ -105,7 +105,10 @@ through the launch barrier — `devrites-engine dispatch <slug> open --phase bui
 <slice-id> --role slice-wright --slice <SLICE-ID> --contract <file>` (it refuses a
 contract that forbids writer-safe checks or names none), then `start` with the host handle, `seal`, and
 `return` on completion (auto-records dispatch/return metrics). Every 5 wright
-rounds on one slice, `open` blocks for a reslice review: propose an
+rounds on one slice, `open` blocks for a reslice review. First re-admit each
+finding still driving rounds under the Proportionality rule of
+[agents.md § Result admission](skill://devrites-lib/reference/standards/agents.md#result-admission): one without a broken anchor or a reachable trigger becomes a
+Suggestion and drives no further round. Then propose an
 acceptance-preserving split (`root_no_change_analysis` → `FOLD` per
 [acceptance-preserving-reslice](skill://devrites-lib/reference/standards/acceptance-preserving-reslice.md);
 open findings move to the new slice owning their paths), or record

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

@@ -119,7 +119,15 @@ Basis: <files read · commands run to reach this finding>
   quote like the `file:line` quote. No anchor, or one the defect does not break,
   admits the row as Suggestion logged `Deferred: <claim> — no spec anchor` for an
   optional follow-up slice; it never drives a repair round. Hardening no spec line
-  asks for is a Suggestion, however plausible.
+  asks for is a Suggestion, however plausible. The `when` must also be reachable:
+  a hostile actor enters only through a trust boundary the feature really has
+  (users, network, external systems, untrusted files). A trigger that needs one it
+  never faces — the code under test forging its own evidence, a tampering second
+  user on a single-owner dev host, a swapped remote daemon under a local dev tool —
+  is a Suggestion too. So is an environment state the feature's declared
+  environment does not have (a mount option, kernel setting or daemon location
+  absent from the target host): guard against it only when the spec names it.
+  A finding never pulls a deferred slice's scope forward.
 - **`no-findings`:** `No-findings:` names checks and inspected evidence. Bare
   pass, empty list, or “looks good” is malformed.
 - **`gap`:** names missing/unreadable/stale input; skipped/failed required check;

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

@@ -105,7 +105,10 @@ through the launch barrier — `devrites-engine dispatch <slug> open --phase bui
 <slice-id> --role slice-wright --slice <SLICE-ID> --contract <file>` (it refuses a
 contract that forbids writer-safe checks or names none), then `start` with the host handle, `seal`, and
 `return` on completion (auto-records dispatch/return metrics). Every 5 wright
-rounds on one slice, `open` blocks for a reslice review: propose an
+rounds on one slice, `open` blocks for a reslice review. First re-admit each
+finding still driving rounds under the Proportionality rule of
+[agents.md § Result admission](../../devrites-lib/reference/standards/agents.md#result-admission): one without a broken anchor or a reachable trigger becomes a
+Suggestion and drives no further round. Then propose an
 acceptance-preserving split (`root_no_change_analysis` → `FOLD` per
 [acceptance-preserving-reslice](../../devrites-lib/reference/standards/acceptance-preserving-reslice.md);
 open findings move to the new slice owning their paths), or record

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "devrites",
-  "version": "6.7.0",
+  "version": "6.7.2",
   "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",