devrites 6.7.2 → 6.7.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -2,6 +2,18 @@
2
2
 
3
3
  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`.
4
4
 
5
+ ## [6.7.4](https://github.com/ViktorsBaikers/DevRites/compare/v6.7.3...v6.7.4) (2026-10-17)
6
+
7
+ ### Fixed
8
+
9
+ * **devrites:** a host reminder is not a turn end ([#128](https://github.com/ViktorsBaikers/DevRites/issues/128)) ([45f4922](https://github.com/ViktorsBaikers/DevRites/commit/45f492269f568449572f27d355641d181d6dd21c))
10
+
11
+ ## [6.7.3](https://github.com/ViktorsBaikers/DevRites/compare/v6.7.2...v6.7.3) (2026-10-17)
12
+
13
+ ### Fixed
14
+
15
+ * **devrites:** a repair contract is never a finding anchor ([#127](https://github.com/ViktorsBaikers/DevRites/issues/127)) ([ec8d427](https://github.com/ViktorsBaikers/DevRites/commit/ec8d427b525fe9852e99c4af6a46ce79ba75230d))
16
+
5
17
  ## [6.7.2](https://github.com/ViktorsBaikers/DevRites/compare/v6.7.1...v6.7.2) (2026-10-17)
6
18
 
7
19
  ### Fixed
package/README.md CHANGED
@@ -31,7 +31,7 @@ history can't lose it. After you clear the conversation, switch hosts, or hand
31
31
  the feature to another engineer, the next session reads the same plan,
32
32
  decisions, and evidence before it continues.
33
33
 
34
- **Status:** [`v6.7.2`](https://github.com/ViktorsBaikers/DevRites/releases/tag/v6.7.2): see [`CHANGELOG.md`](CHANGELOG.md) for release notes.
34
+ **Status:** [`v6.7.4`](https://github.com/ViktorsBaikers/DevRites/releases/tag/v6.7.4): see [`CHANGELOG.md`](CHANGELOG.md) for release notes.
35
35
 
36
36
  This is the latest published release; `main` may contain unreleased work.
37
37
 
@@ -116,7 +116,9 @@ Basis: <files read · commands run to reach this finding>
116
116
  - **Proportionality:** a Critical/Important row's `breaks` quotes the line it violates:
117
117
  a spec ID (`AC`/`REQ`/`INV`/`PROH`/`DEC`/`EDGE`) or a shipped standard rule
118
118
  (`<standard>.md § <section>`: security, regression, principles). Root anchors the
119
- quote like the `file:line` quote. No anchor, or one the defect does not break,
119
+ quote like the `file:line` quote. A repair contract, recheck packet or earlier
120
+ finding only restates a prior claim and is never an anchor. No anchor, or one
121
+ the defect does not break,
120
122
  admits the row as Suggestion logged `Deferred: <claim> — no spec anchor` for an
121
123
  optional follow-up slice; it never drives a repair round. Hardening no spec line
122
124
  asks for is a Suggestion, however plausible. The `when` must also be reachable:
@@ -63,7 +63,9 @@ executable controller/harness/bundle bytes or a missing writer, read
63
63
  - Never end the turn with a progress note while a wave runs or a next step
64
64
  exists: on a headless host a text-only reply ends the session and kills
65
65
  running children. Wait with the host's wait tool and keep working; end only
66
- at a recorded stop.
66
+ at a recorded stop. A host reminder or rule notice (style rule, advisory) is
67
+ not a stop either: follow it in your next tool call, never in a text-only
68
+ acknowledgement.
67
69
  - Parse flags only from this invocation. `--ship`, `--yolo`, `--max-slices`,
68
70
  `--parallel`, `--full`, and `--cross-model` activate only as exact standalone
69
71
  tokens in `$ARGUMENTS`; examples or earlier messages can never arm them.
@@ -116,7 +116,9 @@ Basis: <files read · commands run to reach this finding>
116
116
  - **Proportionality:** a Critical/Important row's `breaks` quotes the line it violates:
117
117
  a spec ID (`AC`/`REQ`/`INV`/`PROH`/`DEC`/`EDGE`) or a shipped standard rule
118
118
  (`<standard>.md § <section>`: security, regression, principles). Root anchors the
119
- quote like the `file:line` quote. No anchor, or one the defect does not break,
119
+ quote like the `file:line` quote. A repair contract, recheck packet or earlier
120
+ finding only restates a prior claim and is never an anchor. No anchor, or one
121
+ the defect does not break,
120
122
  admits the row as Suggestion logged `Deferred: <claim> — no spec anchor` for an
121
123
  optional follow-up slice; it never drives a repair round. Hardening no spec line
122
124
  asks for is a Suggestion, however plausible. The `when` must also be reachable:
@@ -65,7 +65,9 @@ executable controller/harness/bundle bytes or a missing writer, read
65
65
  - Never end the turn with a progress note while a wave runs or a next step
66
66
  exists: on a headless host a text-only reply ends the session and kills
67
67
  running children. Wait with the host's wait tool and keep working; end only
68
- at a recorded stop.
68
+ at a recorded stop. A host reminder or rule notice (style rule, advisory) is
69
+ not a stop either: follow it in your next tool call, never in a text-only
70
+ acknowledgement.
69
71
  - Parse flags only from this invocation. `--ship`, `--yolo`, `--max-slices`,
70
72
  `--parallel`, `--full`, and `--cross-model` activate only as exact standalone
71
73
  tokens in `$ARGUMENTS`; examples or earlier messages can never arm them.
@@ -116,7 +116,9 @@ Basis: <files read · commands run to reach this finding>
116
116
  - **Proportionality:** a Critical/Important row's `breaks` quotes the line it violates:
117
117
  a spec ID (`AC`/`REQ`/`INV`/`PROH`/`DEC`/`EDGE`) or a shipped standard rule
118
118
  (`<standard>.md § <section>`: security, regression, principles). Root anchors the
119
- quote like the `file:line` quote. No anchor, or one the defect does not break,
119
+ quote like the `file:line` quote. A repair contract, recheck packet or earlier
120
+ finding only restates a prior claim and is never an anchor. No anchor, or one
121
+ the defect does not break,
120
122
  admits the row as Suggestion logged `Deferred: <claim> — no spec anchor` for an
121
123
  optional follow-up slice; it never drives a repair round. Hardening no spec line
122
124
  asks for is a Suggestion, however plausible. The `when` must also be reachable:
@@ -65,7 +65,9 @@ executable controller/harness/bundle bytes or a missing writer, read
65
65
  - Never end the turn with a progress note while a wave runs or a next step
66
66
  exists: on a headless host a text-only reply ends the session and kills
67
67
  running children. Wait with the host's wait tool and keep working; end only
68
- at a recorded stop.
68
+ at a recorded stop. A host reminder or rule notice (style rule, advisory) is
69
+ not a stop either: follow it in your next tool call, never in a text-only
70
+ acknowledgement.
69
71
  - Parse flags only from this invocation. `--ship`, `--yolo`, `--max-slices`,
70
72
  `--parallel`, `--full`, and `--cross-model` activate only as exact standalone
71
73
  tokens in `$ARGUMENTS`; examples or earlier messages can never arm them.
@@ -116,7 +116,9 @@ Basis: <files read · commands run to reach this finding>
116
116
  - **Proportionality:** a Critical/Important row's `breaks` quotes the line it violates:
117
117
  a spec ID (`AC`/`REQ`/`INV`/`PROH`/`DEC`/`EDGE`) or a shipped standard rule
118
118
  (`<standard>.md § <section>`: security, regression, principles). Root anchors the
119
- quote like the `file:line` quote. No anchor, or one the defect does not break,
119
+ quote like the `file:line` quote. A repair contract, recheck packet or earlier
120
+ finding only restates a prior claim and is never an anchor. No anchor, or one
121
+ the defect does not break,
120
122
  admits the row as Suggestion logged `Deferred: <claim> — no spec anchor` for an
121
123
  optional follow-up slice; it never drives a repair round. Hardening no spec line
122
124
  asks for is a Suggestion, however plausible. The `when` must also be reachable:
@@ -64,7 +64,9 @@ executable controller/harness/bundle bytes or a missing writer, read
64
64
  - Never end the turn with a progress note while a wave runs or a next step
65
65
  exists: on a headless host a text-only reply ends the session and kills
66
66
  running children. Wait with the host's wait tool and keep working; end only
67
- at a recorded stop.
67
+ at a recorded stop. A host reminder or rule notice (style rule, advisory) is
68
+ not a stop either: follow it in your next tool call, never in a text-only
69
+ acknowledgement.
68
70
  - Parse flags only from this invocation. `--ship`, `--yolo`, `--max-slices`,
69
71
  `--parallel`, `--full`, and `--cross-model` activate only as exact standalone
70
72
  tokens in `$ARGUMENTS`; examples or earlier messages can never arm them.
@@ -116,7 +116,9 @@ Basis: <files read · commands run to reach this finding>
116
116
  - **Proportionality:** a Critical/Important row's `breaks` quotes the line it violates:
117
117
  a spec ID (`AC`/`REQ`/`INV`/`PROH`/`DEC`/`EDGE`) or a shipped standard rule
118
118
  (`<standard>.md § <section>`: security, regression, principles). Root anchors the
119
- quote like the `file:line` quote. No anchor, or one the defect does not break,
119
+ quote like the `file:line` quote. A repair contract, recheck packet or earlier
120
+ finding only restates a prior claim and is never an anchor. No anchor, or one
121
+ the defect does not break,
120
122
  admits the row as Suggestion logged `Deferred: <claim> — no spec anchor` for an
121
123
  optional follow-up slice; it never drives a repair round. Hardening no spec line
122
124
  asks for is a Suggestion, however plausible. The `when` must also be reachable:
@@ -65,7 +65,9 @@ executable controller/harness/bundle bytes or a missing writer, read
65
65
  - Never end the turn with a progress note while a wave runs or a next step
66
66
  exists: on a headless host a text-only reply ends the session and kills
67
67
  running children. Wait with the host's wait tool and keep working; end only
68
- at a recorded stop.
68
+ at a recorded stop. A host reminder or rule notice (style rule, advisory) is
69
+ not a stop either: follow it in your next tool call, never in a text-only
70
+ acknowledgement.
69
71
  - Parse flags only from this invocation. `--ship`, `--yolo`, `--max-slices`,
70
72
  `--parallel`, `--full`, and `--cross-model` activate only as exact standalone
71
73
  tokens in `$ARGUMENTS`; examples or earlier messages can never arm them.
@@ -116,7 +116,9 @@ Basis: <files read · commands run to reach this finding>
116
116
  - **Proportionality:** a Critical/Important row's `breaks` quotes the line it violates:
117
117
  a spec ID (`AC`/`REQ`/`INV`/`PROH`/`DEC`/`EDGE`) or a shipped standard rule
118
118
  (`<standard>.md § <section>`: security, regression, principles). Root anchors the
119
- quote like the `file:line` quote. No anchor, or one the defect does not break,
119
+ quote like the `file:line` quote. A repair contract, recheck packet or earlier
120
+ finding only restates a prior claim and is never an anchor. No anchor, or one
121
+ the defect does not break,
120
122
  admits the row as Suggestion logged `Deferred: <claim> — no spec anchor` for an
121
123
  optional follow-up slice; it never drives a repair round. Hardening no spec line
122
124
  asks for is a Suggestion, however plausible. The `when` must also be reachable:
@@ -65,7 +65,9 @@ executable controller/harness/bundle bytes or a missing writer, read
65
65
  - Never end the turn with a progress note while a wave runs or a next step
66
66
  exists: on a headless host a text-only reply ends the session and kills
67
67
  running children. Wait with the host's wait tool and keep working; end only
68
- at a recorded stop.
68
+ at a recorded stop. A host reminder or rule notice (style rule, advisory) is
69
+ not a stop either: follow it in your next tool call, never in a text-only
70
+ acknowledgement.
69
71
  - Parse flags only from this invocation. `--ship`, `--yolo`, `--max-slices`,
70
72
  `--parallel`, `--full`, and `--cross-model` activate only as exact standalone
71
73
  tokens in `$ARGUMENTS`; examples or earlier messages can never arm them.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "devrites",
3
- "version": "6.7.2",
3
+ "version": "6.7.4",
4
4
  "description": "DevRites: a disciplined senior-engineer workflow pack for Claude Code, Codex, omp, pi, and Devin CLI",
5
5
  "license": "SEE LICENSE IN LICENSE",
6
6
  "homepage": "https://github.com/ViktorsBaikers/DevRites#readme",