devrites 6.0.0 → 6.0.1

package/CHANGELOG.md

@@ -2,6 +2,12 @@
 
 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.0.1](https://github.com/ViktorsBaikers/DevRites/compare/v6.0.0...v6.0.1) (2026-10-14)
+
+### Fixed
+
+* **skills:** route .devrites writes to workflow artifacts ([#102](https://github.com/ViktorsBaikers/DevRites/issues/102)) ([8bb83b2](https://github.com/ViktorsBaikers/DevRites/commit/8bb83b21ef80cbcde3788e434830e38217297e31))
+
 ## [6.0.0](https://github.com/ViktorsBaikers/DevRites/compare/v5.14.4...v6.0.0) (2026-10-10)
 
 ### ⚠ BREAKING CHANGES

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.0.0`](https://github.com/ViktorsBaikers/DevRites/releases/tag/v6.0.0): see [`CHANGELOG.md`](CHANGELOG.md) for release notes.
+**Status:** [`v6.0.1`](https://github.com/ViktorsBaikers/DevRites/releases/tag/v6.0.1): 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

@@ -68,6 +68,8 @@ rejected result, stop, or a launch refused with no handle — run
 `devrites-engine claim release --session <id> --id <claim-id>`. Claims expire
 by TTL only as crash recovery; `claim list` shows who holds what. Claims are
 advisory coordination, never a substitute for the one-writer-per-worktree rule.
+Claims cover product paths only; root-authored `.devrites/**` files use
+[`workflow-artifacts.md`](workflow-artifacts.md) admission instead.
 Expiry is not proof the holder stopped: size `claim add --ttl <minutes>` to the
 expected write (engine max 240) and re-add before it lapses; before writing, also
 read `claim list --all` — a foreign `expired` claim on overlapping paths whose

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

@@ -75,7 +75,9 @@ Same-worktree (non-isolated) dispatch claims before writing: `devrites-engine
 claim add --session <id> <task-paths>`; retain its returned `<claim-id>`, then run
 `devrites-engine claim check --session <id> <task-paths>` — a held claim from a
 live foreign session releases the retained claim and stops the dispatch, per
-[`agents.md`](../../devrites-lib/reference/standards/agents.md). Ask the host
+[`agents.md`](../../devrites-lib/reference/standards/agents.md). `.devrites/**`
+is never a task path; see [Workflow Artifact admission](../../devrites-lib/reference/standards/workflow-artifacts.md).
+Ask the host
 for the exact writer in fresh context and wait. Track it through the
 launch barrier — `devrites-engine dispatch <slug> open --phase build --wave
 <slice-id> --role slice-wright`, then `start` with the host handle, `seal`, and

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

@@ -68,6 +68,8 @@ rejected result, stop, or a launch refused with no handle — run
 `devrites-engine claim release --session <id> --id <claim-id>`. Claims expire
 by TTL only as crash recovery; `claim list` shows who holds what. Claims are
 advisory coordination, never a substitute for the one-writer-per-worktree rule.
+Claims cover product paths only; root-authored `.devrites/**` files use
+[`workflow-artifacts.md`](workflow-artifacts.md) admission instead.
 Expiry is not proof the holder stopped: size `claim add --ttl <minutes>` to the
 expected write (engine max 240) and re-add before it lapses; before writing, also
 read `claim list --all` — a foreign `expired` claim on overlapping paths whose

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

@@ -75,7 +75,9 @@ Same-worktree (non-isolated) dispatch claims before writing: `devrites-engine
 claim add --session <id> <task-paths>`; retain its returned `<claim-id>`, then run
 `devrites-engine claim check --session <id> <task-paths>` — a held claim from a
 live foreign session releases the retained claim and stops the dispatch, per
-[`agents.md`](../../devrites-lib/reference/standards/agents.md). Ask the host
+[`agents.md`](../../devrites-lib/reference/standards/agents.md). `.devrites/**`
+is never a task path; see [Workflow Artifact admission](../../devrites-lib/reference/standards/workflow-artifacts.md).
+Ask the host
 for the exact writer in fresh context and wait. Track it through the
 launch barrier — `devrites-engine dispatch <slug> open --phase build --wave
 <slice-id> --role slice-wright`, then `start` with the host handle, `seal`, and

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

@@ -68,6 +68,8 @@ rejected result, stop, or a launch refused with no handle — run
 `devrites-engine claim release --session <id> --id <claim-id>`. Claims expire
 by TTL only as crash recovery; `claim list` shows who holds what. Claims are
 advisory coordination, never a substitute for the one-writer-per-worktree rule.
+Claims cover product paths only; root-authored `.devrites/**` files use
+[`workflow-artifacts.md`](workflow-artifacts.md) admission instead.
 Expiry is not proof the holder stopped: size `claim add --ttl <minutes>` to the
 expected write (engine max 240) and re-add before it lapses; before writing, also
 read `claim list --all` — a foreign `expired` claim on overlapping paths whose

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

@@ -75,7 +75,9 @@ Same-worktree (non-isolated) dispatch claims before writing: `devrites-engine
 claim add --session <id> <task-paths>`; retain its returned `<claim-id>`, then run
 `devrites-engine claim check --session <id> <task-paths>` — a held claim from a
 live foreign session releases the retained claim and stops the dispatch, per
-[`agents.md`](../../devrites-lib/reference/standards/agents.md). Ask the host
+[`agents.md`](../../devrites-lib/reference/standards/agents.md). `.devrites/**`
+is never a task path; see [Workflow Artifact admission](../../devrites-lib/reference/standards/workflow-artifacts.md).
+Ask the host
 for the exact writer in fresh context and wait. Track it through the
 launch barrier — `devrites-engine dispatch <slug> open --phase build --wave
 <slice-id> --role slice-wright`, then `start` with the host handle, `seal`, and

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

@@ -68,6 +68,8 @@ rejected result, stop, or a launch refused with no handle — run
 `devrites-engine claim release --session <id> --id <claim-id>`. Claims expire
 by TTL only as crash recovery; `claim list` shows who holds what. Claims are
 advisory coordination, never a substitute for the one-writer-per-worktree rule.
+Claims cover product paths only; root-authored `.devrites/**` files use
+[`workflow-artifacts.md`](workflow-artifacts.md) admission instead.
 Expiry is not proof the holder stopped: size `claim add --ttl <minutes>` to the
 expected write (engine max 240) and re-add before it lapses; before writing, also
 read `claim list --all` — a foreign `expired` claim on overlapping paths whose

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

@@ -75,7 +75,9 @@ Same-worktree (non-isolated) dispatch claims before writing: `devrites-engine
 claim add --session <id> <task-paths>`; retain its returned `<claim-id>`, then run
 `devrites-engine claim check --session <id> <task-paths>` — a held claim from a
 live foreign session releases the retained claim and stops the dispatch, per
-[`agents.md`](../../devrites-lib/reference/standards/agents.md). Ask the host
+[`agents.md`](../../devrites-lib/reference/standards/agents.md). `.devrites/**`
+is never a task path; see [Workflow Artifact admission](../../devrites-lib/reference/standards/workflow-artifacts.md).
+Ask the host
 for the exact writer in fresh context and wait. Track it through the
 launch barrier — `devrites-engine dispatch <slug> open --phase build --wave
 <slice-id> --role slice-wright`, then `start` with the host handle, `seal`, and

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

@@ -68,6 +68,8 @@ rejected result, stop, or a launch refused with no handle — run
 `devrites-engine claim release --session <id> --id <claim-id>`. Claims expire
 by TTL only as crash recovery; `claim list` shows who holds what. Claims are
 advisory coordination, never a substitute for the one-writer-per-worktree rule.
+Claims cover product paths only; root-authored `.devrites/**` files use
+[`workflow-artifacts.md`](workflow-artifacts.md) admission instead.
 Expiry is not proof the holder stopped: size `claim add --ttl <minutes>` to the
 expected write (engine max 240) and re-add before it lapses; before writing, also
 read `claim list --all` — a foreign `expired` claim on overlapping paths whose

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

@@ -75,7 +75,9 @@ Same-worktree (non-isolated) dispatch claims before writing: `devrites-engine
 claim add --session <id> <task-paths>`; retain its returned `<claim-id>`, then run
 `devrites-engine claim check --session <id> <task-paths>` — a held claim from a
 live foreign session releases the retained claim and stops the dispatch, per
-[`agents.md`](../../devrites-lib/reference/standards/agents.md). Ask the host
+[`agents.md`](../../devrites-lib/reference/standards/agents.md). `.devrites/**`
+is never a task path; see [Workflow Artifact admission](../../devrites-lib/reference/standards/workflow-artifacts.md).
+Ask the host
 for the exact writer in fresh context and wait. Track it through the
 launch barrier — `devrites-engine dispatch <slug> open --phase build --wave
 <slice-id> --role slice-wright`, then `start` with the host handle, `seal`, and

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

@@ -68,6 +68,8 @@ rejected result, stop, or a launch refused with no handle — run
 `devrites-engine claim release --session <id> --id <claim-id>`. Claims expire
 by TTL only as crash recovery; `claim list` shows who holds what. Claims are
 advisory coordination, never a substitute for the one-writer-per-worktree rule.
+Claims cover product paths only; root-authored `.devrites/**` files use
+[`workflow-artifacts.md`](workflow-artifacts.md) admission instead.
 Expiry is not proof the holder stopped: size `claim add --ttl <minutes>` to the
 expected write (engine max 240) and re-add before it lapses; before writing, also
 read `claim list --all` — a foreign `expired` claim on overlapping paths whose

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

@@ -75,7 +75,9 @@ Same-worktree (non-isolated) dispatch claims before writing: `devrites-engine
 claim add --session <id> <task-paths>`; retain its returned `<claim-id>`, then run
 `devrites-engine claim check --session <id> <task-paths>` — a held claim from a
 live foreign session releases the retained claim and stops the dispatch, per
-[`agents.md`](../../devrites-lib/reference/standards/agents.md). Ask the host
+[`agents.md`](../../devrites-lib/reference/standards/agents.md). `.devrites/**`
+is never a task path; see [Workflow Artifact admission](../../devrites-lib/reference/standards/workflow-artifacts.md).
+Ask the host
 for the exact writer in fresh context and wait. Track it through the
 launch barrier — `devrites-engine dispatch <slug> open --phase build --wave
 <slice-id> --role slice-wright`, then `start` with the host handle, `seal`, and

package/package.json

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