@lifeaitools/rdc-skills 0.38.0 → 0.38.1

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "rdc",
-  "version": "0.38.0",
+  "version": "0.38.1",
   "description": "RDC typed-agent dispatch skill suite for Claude Code — plan, build, review, overnight unattended builds with work-item tracking and TDD enforcement.",
   "author": {
     "name": "LIFEAI",

package/clauth-plugin.json

@@ -1,7 +1,7 @@
 {
   "schema": "lifeai.plugin.v1",
   "id": "rdc-skills",
-  "version": "0.38.0",
+  "version": "0.38.1",
   "publisher": "LIFEAI",
   "core": false,
   "documentation": {

package/git-sha.json

@@ -1,3 +1,3 @@
 {
-  "sha": "bbbd79996feafdb0aae6bf5c1f8bbebed904db74"
+  "sha": "597fd36853cf0e514b5b8729ac1de893ea026b00"
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lifeaitools/rdc-skills",
-  "version": "0.38.0",
+  "version": "0.38.1",
   "description": "RDC typed-agent dispatch skill suite for Claude Code - plan, build, review, overnight builds",
   "keywords": [
     "claude-code",
@@ -19,7 +19,7 @@
     "type": "plugin",
     "skills": "skills/",
     "guides": "guides/",
-    "version": "0.38.0",
+    "version": "0.38.1",
     "commands": "commands/"
   },
   "bin": {

package/skills/close/SKILL.md

@@ -23,9 +23,10 @@ description: rdc:close () — decide whether this session can exit, fix what is
 judgment layer on top: it fixes what the engine reports. The engine never commits, edits or deploys; those need a
 decision, and the decision is yours.
 
-If a session ends without a close, a SessionEnd hook starts a detached worker that lands what is **already
-committed** and writes an unclean record for the rest. The next session in that lane is told what was left. So close
-properly; the hook is a safety net, not the plan.
+If a session ends without a close, a SessionEnd hook (`rdc-close --hook --detach`, used by the harness and not by
+you) starts a detached worker that lands what is **already committed** and writes an unclean record for the rest.
+The next session in that lane is told what was left, and is also told when a lane starts with uncommitted paths even
+though no exit ran (a crash fires no SessionEnd). So close properly; the hook is a safety net, not the plan.
 
 ## Procedure
 
@@ -50,8 +51,18 @@ properly; the hook is a safety net, not the plan.
    - `/rdc:report` when the work contract's tier asks for a session report.
    - Finalize the CodeFlow session (`codeflow_finalize`).
 
-4. **Close.** `node "$LIFEAI_ENV/bin/rdc-close.mjs" run` lands anything committed, runs `clauth scrub`, re-checks, and
-   writes the session marker. Exit 0 means closed. Exit 1 prints the failing checks: go back to step 2.
+4. **Close.** `node "$LIFEAI_ENV/bin/rdc-close.mjs" run`:
+   - runs every check, even when a marker already exists (the marker covers HEAD and the tree, not stash, other
+     repositories, deploy or the contract);
+   - if the lane is clean and a commit is not yet on `origin/<integration>`, lands it through the contract's ship
+     route. In lifeai-env that route publishes the package by default, so `run` uses it land-only
+     (`--existing --no-publish`): no publish and no global install. Releasing stays a deliberate `/rdc:release`;
+   - runs `clauth scrub`;
+   - writes the session marker only when every check is clear. Otherwise it writes an unclean record and retires
+     any marker.
+
+   Exit 0 means closed. Exit 1 prints the failing checks: go back to step 2. `rdc-close status` says whether this
+   session's marker is current (exit 0) or not (exit 1). Exit 2 is a usage error.
 
 5. **Report one line.** Closed (marker current, with the commit it names), or the blockers that remain and the one
    decision that clears them.
@@ -59,7 +70,8 @@ properly; the hook is a safety net, not the plan.
 ## Rules
 
 - Never say "closed" without `rdc-close run` exiting 0 **in this turn**. A marker goes stale on any later commit or
-  edit, so a close claimed earlier does not carry.
+  edit, so a close claimed earlier does not carry. A stash or a dirty second repository does not change the marker,
+  which is why `run` checks them every time.
 - Never commit, reset or delete another session's work. A dirty sibling worktree is preserved, not cleaned.
 - Deploy only when the engine says a deployable changed. `deploy: na` is the answer for a docs-only or tooling-only
   session; do not run `/rdc:deploy` for the sake of it.