devrites 6.9.2 → 6.9.3

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,12 @@
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.9.3](https://github.com/ViktorsBaikers/DevRites/compare/v6.9.2...v6.9.3) (2026-10-18)
6
+
7
+ ### Fixed
8
+
9
+ * **devrites:** dispatch named roles only through the host agent tool ([#134](https://github.com/ViktorsBaikers/DevRites/issues/134)) ([60ca9d5](https://github.com/ViktorsBaikers/DevRites/commit/60ca9d59ed47758e403aa92ed033885b257270bd))
10
+
5
11
  ## [6.9.2](https://github.com/ViktorsBaikers/DevRites/compare/v6.9.1...v6.9.2) (2026-10-18)
6
12
 
7
13
  ### 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.9.2`](https://github.com/ViktorsBaikers/DevRites/releases/tag/v6.9.2): see [`CHANGELOG.md`](CHANGELOG.md) for release notes.
34
+ **Status:** [`v6.9.3`](https://github.com/ViktorsBaikers/DevRites/releases/tag/v6.9.3): 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
 
@@ -51,7 +51,10 @@ If the candidate diff has no matching surfaces, record
51
51
  a reviewer, auditor, or test-analyst wave adds `--packet <file>`, the exact packet
52
52
  those agents receive, and `open` refuses one that seeds a gate result, outcome,
53
53
  count, or "already passed" claim; at Review and Seal it also needs the packet to
54
- name the frozen candidate diff and the manifest to cover every checkpointed path), launch every native agent nonblocking, record each returned host handle
54
+ name the frozen candidate diff and the manifest to cover every checkpointed path), launch every native agent nonblocking through the host's own agent
55
+ tool (never a shell-launched host CLI such as `omp -p` or `claude -p`: that is a
56
+ dispatch bridge, its PID handle dies with the session, and its return is a `gap`),
57
+ record each returned host handle
55
58
  (`dispatch ... start --wave <w> --role <r> --handle <id>`), then `seal` —
56
59
  seal fails until every declared role has a distinct handle, which makes a
57
60
  serial launch-then-wait pattern impossible to record. Record each completion
@@ -51,7 +51,10 @@ If the candidate diff has no matching surfaces, record
51
51
  a reviewer, auditor, or test-analyst wave adds `--packet <file>`, the exact packet
52
52
  those agents receive, and `open` refuses one that seeds a gate result, outcome,
53
53
  count, or "already passed" claim; at Review and Seal it also needs the packet to
54
- name the frozen candidate diff and the manifest to cover every checkpointed path), launch every native agent nonblocking, record each returned host handle
54
+ name the frozen candidate diff and the manifest to cover every checkpointed path), launch every native agent nonblocking through the host's own agent
55
+ tool (never a shell-launched host CLI such as `omp -p` or `claude -p`: that is a
56
+ dispatch bridge, its PID handle dies with the session, and its return is a `gap`),
57
+ record each returned host handle
55
58
  (`dispatch ... start --wave <w> --role <r> --handle <id>`), then `seal` —
56
59
  seal fails until every declared role has a distinct handle, which makes a
57
60
  serial launch-then-wait pattern impossible to record. Record each completion
@@ -51,7 +51,10 @@ If the candidate diff has no matching surfaces, record
51
51
  a reviewer, auditor, or test-analyst wave adds `--packet <file>`, the exact packet
52
52
  those agents receive, and `open` refuses one that seeds a gate result, outcome,
53
53
  count, or "already passed" claim; at Review and Seal it also needs the packet to
54
- name the frozen candidate diff and the manifest to cover every checkpointed path), launch every native agent nonblocking, record each returned host handle
54
+ name the frozen candidate diff and the manifest to cover every checkpointed path), launch every native agent nonblocking through the host's own agent
55
+ tool (never a shell-launched host CLI such as `omp -p` or `claude -p`: that is a
56
+ dispatch bridge, its PID handle dies with the session, and its return is a `gap`),
57
+ record each returned host handle
55
58
  (`dispatch ... start --wave <w> --role <r> --handle <id>`), then `seal` —
56
59
  seal fails until every declared role has a distinct handle, which makes a
57
60
  serial launch-then-wait pattern impossible to record. Record each completion
@@ -51,7 +51,10 @@ If the candidate diff has no matching surfaces, record
51
51
  a reviewer, auditor, or test-analyst wave adds `--packet <file>`, the exact packet
52
52
  those agents receive, and `open` refuses one that seeds a gate result, outcome,
53
53
  count, or "already passed" claim; at Review and Seal it also needs the packet to
54
- name the frozen candidate diff and the manifest to cover every checkpointed path), launch every native agent nonblocking, record each returned host handle
54
+ name the frozen candidate diff and the manifest to cover every checkpointed path), launch every native agent nonblocking through the host's own agent
55
+ tool (never a shell-launched host CLI such as `omp -p` or `claude -p`: that is a
56
+ dispatch bridge, its PID handle dies with the session, and its return is a `gap`),
57
+ record each returned host handle
55
58
  (`dispatch ... start --wave <w> --role <r> --handle <id>`), then `seal` —
56
59
  seal fails until every declared role has a distinct handle, which makes a
57
60
  serial launch-then-wait pattern impossible to record. Record each completion
@@ -51,7 +51,10 @@ If the candidate diff has no matching surfaces, record
51
51
  a reviewer, auditor, or test-analyst wave adds `--packet <file>`, the exact packet
52
52
  those agents receive, and `open` refuses one that seeds a gate result, outcome,
53
53
  count, or "already passed" claim; at Review and Seal it also needs the packet to
54
- name the frozen candidate diff and the manifest to cover every checkpointed path), launch every native agent nonblocking, record each returned host handle
54
+ name the frozen candidate diff and the manifest to cover every checkpointed path), launch every native agent nonblocking through the host's own agent
55
+ tool (never a shell-launched host CLI such as `omp -p` or `claude -p`: that is a
56
+ dispatch bridge, its PID handle dies with the session, and its return is a `gap`),
57
+ record each returned host handle
55
58
  (`dispatch ... start --wave <w> --role <r> --handle <id>`), then `seal` —
56
59
  seal fails until every declared role has a distinct handle, which makes a
57
60
  serial launch-then-wait pattern impossible to record. Record each completion
@@ -51,7 +51,10 @@ If the candidate diff has no matching surfaces, record
51
51
  a reviewer, auditor, or test-analyst wave adds `--packet <file>`, the exact packet
52
52
  those agents receive, and `open` refuses one that seeds a gate result, outcome,
53
53
  count, or "already passed" claim; at Review and Seal it also needs the packet to
54
- name the frozen candidate diff and the manifest to cover every checkpointed path), launch every native agent nonblocking, record each returned host handle
54
+ name the frozen candidate diff and the manifest to cover every checkpointed path), launch every native agent nonblocking through the host's own agent
55
+ tool (never a shell-launched host CLI such as `omp -p` or `claude -p`: that is a
56
+ dispatch bridge, its PID handle dies with the session, and its return is a `gap`),
57
+ record each returned host handle
55
58
  (`dispatch ... start --wave <w> --role <r> --handle <id>`), then `seal` —
56
59
  seal fails until every declared role has a distinct handle, which makes a
57
60
  serial launch-then-wait pattern impossible to record. Record each completion
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "devrites",
3
- "version": "6.9.2",
3
+ "version": "6.9.3",
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",