@lifeaitools/rdc-skills 0.35.2 → 0.35.3

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "rdc",
-  "version": "0.35.2",
+  "version": "0.35.3",
   "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/CHANGELOG.md

@@ -7,6 +7,25 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ---
 
+## v0.35.3 — coding standards wired into plan/preplan/build/fixit/review
+
+### Fixed
+- `docs/CODING-STANDARDS.md` (regen-root's SOLID/Clean-Architecture standard)
+  existed but was never referenced by any skill that actually reads source
+  documents before working — `preplan`, `plan`, `build`, `fixit`, and
+  `review` all now load it (regen-root; skip if absent). Applied to both the
+  `commands/*.md` and `skills/*/SKILL.md` copies where they diverge.
+- `skills/review/SKILL.md` incorrectly attributed `rdc-solid-score` to ATF;
+  it is this package's own validator (`scripts/solid-score.mjs`), which ATF's
+  Test-Ladder separately invokes as a consumer, not an owner.
+
+### Added
+- WIP, best-effort references to ATF's Test-Ladder and rdc-harness's
+  proof-ledger/mutation-check pattern in `build`, `fixit`, and `review` — not
+  a hard gate; explicitly a no-op where a target repo doesn't ship either.
+
+---
+
 ## v0.25.11 — private Coolify maintenance path
 
 ### Added

package/commands/build.md

@@ -108,7 +108,9 @@ Read the task title and description, then:
 
 3. **Load the plan** (if exists): check `.rdc/plans/` for matching topic (fallback: `.rdc/plans/`).
 
-4. **Read CLAUDE.md files** for all affected packages.
+4. **Read CLAUDE.md files** for all affected packages, plus `docs/CODING-STANDARDS.md`
+   (SOLID/Clean-Architecture standard — regen-root; skip if absent) — carry it into every
+   dispatched agent prompt.
 
 5. **Classify each task** → assign agent type from the table above.
 
@@ -163,6 +165,12 @@ Read the task title and description, then:
     - Read the full output — zero failures, zero type errors
     - If any step fails: fix and re-run the entire gate. Do not skip.
     - NEVER `pnpm build` / `pnpm test` / `pnpm -r` (crashes machine)
+    - **ATF Test-Ladder / rdc-harness (WIP — best-effort, not a hard gate yet):** if a
+      touched package/repo ships an ATF `STP-001.md` or an `rdc-harness`-style
+      `tools/mutate-check.mjs`/`tools/proof-ledger.mjs` pair, run it and quote the result
+      alongside vitest/tsc. A red mutation gate is a real finding — report it, do not
+      silently drop it because it isn't wired into this checklist as required yet.
+      Absence of either system in the target is not a failure; do not install one ad hoc.
 
 11. **After verification passes:**
     - Push all commits:

package/commands/fixit.md

@@ -70,7 +70,8 @@ This signals the Stop hook that fixit is handling its own documentation.
 
 ### 4. Make the fix
 
-Do the minimal work. Scope creep rule: if you discover the fix requires more than originally scoped, **stop immediately**:
+Do the minimal work, conforming to `docs/CODING-STANDARDS.md` where present
+(regen-root; skip if absent). Scope creep rule: if you discover the fix requires more than originally scoped, **stop immediately**:
 1. Close the work item: `update_work_item_status('<id>', 'blocked', '["Escalated — scope exceeded fixit threshold"]')`
 2. Delete the marker file
 3. Tell the user to use `/rdc:build` instead
@@ -108,6 +109,11 @@ failure this step exists to prevent. Carry the change to where it is consumed an
 
 Under `RDC_TEST=1`: echo `[RDC_TEST] skipping delivery (publish/deploy)` and proceed.
 
+**ATF Test-Ladder / rdc-harness (WIP — best-effort, not a hard gate yet):** if the touched
+package/repo already ships an ATF `STP-001.md` or an `rdc-harness`-style
+`tools/mutate-check.mjs`/`tools/proof-ledger.mjs` pair, run it and quote the result. Neither
+is fleet-wide yet — its absence is not itself a fixit failure.
+
 ### 6. Report, review, close, and clean up
 
 **Precondition: Step 5.5 delivery is verified.** If delivery is blocked, set `blocked` (not

package/commands/plan.md

@@ -34,6 +34,10 @@ description: >-
    .claude/rules/work-items-rpc.md            — work item schema, RPC, status enums
    .claude/rules/system-quick-links.md        — routing map to all system architecture docs
    .claude/rules/version-numbering.md         — version bump rules for affected packages
+   docs/CODING-STANDARDS.md                   — SOLID/Clean-Architecture standard; names
+                                                 ATF's Test-Ladder and rdc-harness's
+                                                 proof-ledger pattern where either applies
+                                                 (regen-root; skip if absent)
    ```
 
    **Step 1b — Identify affected domains, then load the matching architecture doc:**
@@ -112,6 +116,12 @@ description: >-
      - completeness: independently observable acceptance criteria plus at least one required `decomp-*` and `test-*` checklist row; and
      - proportionality: estimated files/LOC, declared surfaces, and change kind.
    - Do not invent architecture evidence. Missing, unregistered, broad-refactor, multi-surface, or disproportionate contracts are intentionally routed to human Design Review.
+   - **ATF Test-Ladder / rdc-harness (WIP — best-effort, not a hard gate yet):** if the
+     package being planned has its own ATF `STP-001.md` or ships an `rdc-harness`-style
+     `tools/proof-ledger.mjs`/`tools/mutate-check.mjs` pair, name it in the work package's
+     test requirements as an additional validation signal alongside vitest/tsc. Neither
+     system is fleet-wide or hook-enforced yet — do not fabricate a ladder or a proof
+     ledger for a package that doesn't already have one.
 
 6. **Write plan doc** to `.rdc/plans/<topic-slug>.md` (fallback: `.rdc/plans/<topic-slug>.md` if `.rdc/` does not exist):
    ```markdown

package/commands/preplan.md

@@ -37,6 +37,10 @@ description: >-
    .claude/rules/infrastructure-contract.md   — hard deployment + registry rules
    .claude/rules/work-items-rpc.md            — work item schema and RPC patterns
    .claude/rules/system-quick-links.md        — routing map to system architecture docs
+   docs/CODING-STANDARDS.md                   — SOLID/Clean-Architecture standard; names
+                                                 ATF's Test-Ladder and rdc-harness's
+                                                 proof-ledger pattern where either applies
+                                                 (regen-root; skip if absent)
    ```
 
    **Step 2b — Identify affected domains, then load the matching architecture doc:**

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lifeaitools/rdc-skills",
-  "version": "0.35.2",
+  "version": "0.35.3",
   "description": "RDC typed-agent dispatch skill suite for Claude Code - plan, build, review, overnight builds",
   "keywords": [
     "claude-code",

package/skills/build/SKILL.md

@@ -293,7 +293,9 @@ Read the task title and description, then:
 
    **Plan verifier escalation:** A separate verifier agent is optional, not default. Dispatch one only when the plan touches 5+ UI routes, 3+ data/API boundaries, auth/security, production deployment, or when this rubric fails twice. The verifier reads the plan and work-item checklists only; it does not write code.
 
-4. **Read CLAUDE.md files** for all affected packages.
+4. **Read CLAUDE.md files** for all affected packages, plus `docs/CODING-STANDARDS.md`
+   (SOLID/Clean-Architecture standard — regen-root; skip if absent) — carry it into every
+   dispatched agent prompt.
 
 5. **Classify each task** → assign agent type from the table above.
 
@@ -625,6 +627,12 @@ Read the task title and description, then:
     - Runs `npx tsc --noEmit` for every touched app/package
     - Starts the dev server and probes every modified route (expects HTTP 200, not 500)
     - Runs vitest for every touched package
+    - **ATF Test-Ladder / rdc-harness (WIP — best-effort, not a hard gate yet):** if a
+      touched package/repo ships an ATF `STP-001.md` or an `rdc-harness`-style
+      `tools/mutate-check.mjs`/`tools/proof-ledger.mjs` pair, run it and quote the result
+      alongside tsc/vitest. A red mutation gate is a real finding — report it even though
+      it isn't wired into this checklist as required yet. Absence of either system in the
+      target is not a failure; do not install one ad hoc.
     - For every durable workflow, runs the committed E2E harness and rejects the
       item unless its receipt proves public ingress -> queued/running -> terminal
       state, persisted outputs, and fixture cleanup on the deploy-equivalent

package/skills/fixit/SKILL.md

@@ -69,7 +69,8 @@ This signals the Stop hook that fixit is handling its own documentation.
 
 ### 4. Make the fix
 
-Do the minimal work. Scope creep rule: if you discover the fix requires more than originally scoped, **stop immediately**:
+Do the minimal work, conforming to `docs/CODING-STANDARDS.md` where present
+(regen-root; skip if absent). Scope creep rule: if you discover the fix requires more than originally scoped, **stop immediately**:
 1. Close the work item: `update_work_item_status('<id>', 'blocked', '["Escalated — scope exceeded fixit threshold"]')`
 2. Delete the marker file
 3. Tell the user to use `/rdc:build` instead
@@ -147,6 +148,11 @@ Hard rules for this gate:
 Under `RDC_TEST=1`: echo `[RDC_TEST] skipping delivery (publish/deploy)` and proceed; the
 gate is validated structurally, not executed.
 
+**ATF Test-Ladder / rdc-harness (WIP — best-effort, not a hard gate yet):** if the touched
+package/repo already ships an ATF `STP-001.md` or an `rdc-harness`-style
+`tools/mutate-check.mjs`/`tools/proof-ledger.mjs` pair, run it and quote the result. Neither
+is fleet-wide yet — its absence is not itself a fixit failure.
+
 ### 6. Close and clean up
 
 Submit implementation report first, move to review, then close as validator.

package/skills/review/SKILL.md

@@ -11,6 +11,10 @@ description: "Usage `rdc:review [--unattended]` — Post-build quality gate: tsc
 
 > **Sandbox contract:** This skill honors `RDC_TEST=1` per `guides/agent-bootstrap.md` § RDC_TEST Sandbox Contract. Destructive external calls short-circuit under the flag.
 
+> **Standard being enforced:** `docs/CODING-STANDARDS.md` (SOLID/Clean-Architecture —
+> regen-root; skip if absent). Step 8c is where it's actually checked, via this package's
+> own `rdc-solid-score` (also invoked by ATF's Test-Ladder as a consumer, not an owner).
+
 
 # rdc:review — Quality Gate
 
@@ -124,7 +128,10 @@ description: "Usage `rdc:review [--unattended]` — Post-build quality gate: tsc
    output. Either non-empty is a FORM/FIT failure — dispatch
    `architecture-reviewer` (skill: "architecture-reviewer") for the judgment
    half if a boundary finding needs a suggested fix, not just a named
-   violation.
+   violation. `rdc-solid-score` is this package's own SOLID validator
+   (`scripts/solid-score.mjs`), which ATF's Test-Ladder also invokes at rung
+   TI-3/R3 as a dogfooding example — this step is not an ATF integration;
+   ATF is a separate consumer of the same tool, not its owner.
 
    **Severity gate:**
    - Any regression, or any boundary violation → verdict cannot be CLEAN.
@@ -133,6 +140,14 @@ description: "Usage `rdc:review [--unattended]` — Post-build quality gate: tsc
      nothing wrong to report, but say so explicitly rather than silently
      passing.
 
+   **rdc-harness (WIP — best-effort, not a hard gate yet):** if the reviewed
+   repo ships an `rdc-harness`-style `tools/mutate-check.mjs` and
+   `tools/proof-ledger.mjs` pair, run `tools/mutate-check.mjs` and quote its
+   result. A proof-ledger count is not citable evidence while its own
+   mutation gate is red — report that combination as HAS_ISSUES rather than
+   passing along a ledger number the gate itself has disowned. Absence of
+   this tooling in the target repo is not a finding; do not install it ad hoc.
+
    Under `RDC_TEST=1`: echo `[RDC_TEST] skipping form/fit/function gate` and continue.
 
 9. **Verification gate — dispatch the verify agent:**