cyber-sdd 0.6.0 → 0.7.0

package/.claude-plugin/plugin.json

@@ -7,7 +7,7 @@
 	},
 	"homepage": "https://github.com/cyberuni/cyber-sdd",
 	"repository": "https://github.com/cyberuni/cyber-sdd",
-	"version": "0.6.0",
+	"version": "0.7.0",
 	"skills": "./skills",
 	"agents": [
 		"./agents/sdd-automaton.md",

package/.codex-plugin/plugin.json

@@ -1,5 +1,5 @@
 {
-	"$schema": "https://raw.githubusercontent.com/cyberuni/marketplace/main/schema/claude/plugin.json",
+	"$schema": "https://json.schemastore.org/codex-plugin-manifest.json",
 	"name": "sdd",
 	"description": "Spec-Driven Development. Scaffold, validate, and maintain behavioral specs (spec.md + .feature files) for software features.",
 	"author": {
@@ -7,7 +7,7 @@
 	},
 	"homepage": "https://github.com/cyberuni/cyber-sdd",
 	"repository": "https://github.com/cyberuni/cyber-sdd",
-	"version": "0.6.0",
+	"version": "0.7.0",
 	"skills": "./skills",
 	"agents": [
 		"./agents/sdd-automaton.md",

package/.plugin/plugin.json

@@ -7,7 +7,7 @@
 	},
 	"homepage": "https://github.com/cyberuni/cyber-sdd",
 	"repository": "https://github.com/cyberuni/cyber-sdd",
-	"version": "0.6.0",
+	"version": "0.7.0",
 	"skills": "./skills",
 	"agents": [
 		"./agents/sdd-automaton.md",

package/agents/sdd-automaton.md

@@ -96,7 +96,7 @@ session, or fold judging into your context, which **forfeits grader independence
 as such. Do not design for depth > 2.
 
 A cold-judge or builder dispatch **may** instead be realized through a general-purpose dispatch
-capability's `subagent | channel` seam (ADR-0023, referenced by intent — never a pinned mechanism);
+capability's `subagent | channel` seam (referenced by intent — never a pinned mechanism);
 that is an alternative realization of the same spawns above, not a change to the default depth-1/
 depth-2 behavior described here.
 
@@ -108,5 +108,4 @@ handoff. Hand SDD's own judges (`sdd-spec-judge`, `sdd-impl-judge`) to the
 capability **by file path, never by name** — `agents/<name>.md` under the SDD plugin root, the folder
 your own definition ships in. Locate that root from the SDD skill that spawned you (two levels above
 its base directory) or the plugin root your brief names; if no file is there, send the capability no
-request for that judge and spawn it as a portable cold subagent (`sdd:<name>`) instead. Full model: `start-mission`'s "Dispatch transport" note and the `design/harness-spawning`
-node of the SDD project spec (repo-only).
+request for that judge and spawn it as a portable cold subagent (`sdd:<name>`) instead. Full model: `start-mission`'s "Dispatch transport" note.

package/agents/sdd-impl-judge.md

@@ -1,6 +1,6 @@
 ---
 name: sdd-impl-judge
-description: "Internal SDD impl-judge (default). Grades the implementation against the frozen .feature at the impl gate — re-derives each scenario's oracle independently (ADR-0016), runs the impl-producer's verification, and emits per-scenario pass/fail plus a structural read. Spawned cold by the conductor; never user-triggered."
+description: "Internal SDD impl-judge (default). Grades the implementation against the frozen .feature at the impl gate — re-derives each scenario's oracle independently, runs the impl-producer's verification, and emits per-scenario pass/fail plus a structural read. Spawned cold by the conductor; never user-triggered."
 model: sonnet
 effort: high
 ---
@@ -18,7 +18,7 @@ the **conductor** (`start-mission`) turns the rollup into the gate
 verdict and the leash.
 
 Its verdict answers **"does the frozen contract hold"**, not "did the producer's tests pass" — the
-producer's own green run is a **pre-filter, never the verdict** (ADR-0016). It does **not** judge
+producer's own green run is a **pre-filter, never the verdict**. It does **not** judge
 domain contract quality — a plugin's own impl-judge does that when the registry resolves one for the
 artifact-type.
 
@@ -39,7 +39,8 @@ when you grade against that bar. The **impl-gate lens set is {builder, architect
   candidates the matcher hands you (floor `sdd:builder-impl-governance` /
   `sdd:architect-impl-governance`). Compose per the precedence above — never hand-enumerate.
 - **Fixed-universal:** `sdd:ownership-governance` — the write-ownership matrix; the impl-judge must
-  not modify `spec.md` or the `.feature`, and a behavior-changing gap is a `BLOCKER`, not an edit.
+  not modify `spec.md` or the `.feature`, and a behavior-changing gap is a `BLOCKER`, not an edit —
+  and `sdd:gate-validation-governance` — the gate-legality contract (legal-state tuples, derived sync).
 
 ## Input
 
@@ -49,7 +50,7 @@ IMPLEMENTATION_PATHS:  impl-layer paths from the ## Artifacts table
 VERIFICATION_PATHS:    the verification the impl-producer authored (or discoverable across IMPLEMENTATION_PATHS)
 ```
 
-## The layered verdict (ADR-0016)
+## The layered verdict
 
 Cold context removes the author's *conversational* bias but not a same-model grader's *correlated*
 blind spots, and re-running the producer's own assertions only confirms internal consistency. So the

package/agents/sdd-scanner.md

@@ -196,7 +196,7 @@ is separate from strategy-drafting above; you draft nothing and write nothing to
   tracked issue.
 - There is **no legal terminal value** for a plan brief's `status` field to autofix into — the
   contract's own answer to "this mission is over" is retirement (a tracked deletion), not a status
-  flag (`design/provenance-model.md` reserves the plan-level `status` to the two-value dispatch
+  flag (the plan-level `status` is reserved to the two-value dispatch
   flag `active | approved`). You never write a plan brief's `status`.
 
 ## Boundaries

package/agents/sdd-spec-judge.md

@@ -102,13 +102,13 @@ present (or a reference/descriptive node) ⇒ `{ result: pass, missing: [] }`.
   reading the files — the gate never hard-depends on NodeJS):
   - State-machine legality of the `(status, markers, .feature, approval)` tuple:
     ```bash
-    node "<spec-gate skill>/scripts/check-spec-state.mts" [--root <specs-dir>]
+    node "<spec-gate skill>/scripts/check-spec-state.mjs" [--root <specs-dir>]
     ```
   - Gherkin validity, boolean form, and scenario ordering/sectioning — scope it to the CR's
     touched `.feature` files with `--files`; `--root` sweeps the whole corpus:
     ```bash
-    node "<spec-gate skill>/scripts/check-suite.mts" --files <feature> [<feature> ...]
-    node "<spec-gate skill>/scripts/check-suite.mts" [--root <specs-dir>]
+    node "<spec-gate skill>/scripts/check-suite.mjs" --files <feature> [<feature> ...]
+    node "<spec-gate skill>/scripts/check-suite.mjs" [--root <specs-dir>]
     ```
 - **Non-deterministic agent reasoning** — the three lenses' coverage, scope, and structural-fit
   judgment, and the contradiction checks that need reading.

package/agents/sdd-warden.md

@@ -57,6 +57,14 @@ marker shape you leave — their fields and schema are owned there; never restat
   routing-table row (the "concept of kind K lives in home H" taxonomy and its tie-breaks) is
   correctly placed even where the strategy alone would put it elsewhere. Report a node misplaced only
   when it **neither** follows the declared strategy **nor** matches a routing-table row.
+- **Depth on capability nodes; `design/` by its own shape** (`sdd:spec-structure-governance`). A
+  capability node three levels deep is a depth finding naming it, its sub-grouping owed to a
+  `concept:` tag. Never apply that cap inside `design/`: there, read the placement map for the
+  **design version** — the folder it names is legal, and so are the files inside it; any other
+  sub-folder of `design/` besides `decisions/` is a **perspective folder** finding naming it; a named
+  design version with **no** recorded cut trigger is a finding, and so is a named design version
+  whose folder does not exist (a stale record the cut left behind). Tell a version folder from a
+  perspective folder by the map, never by guessing from its contents.
 - **Stations, not status.** You run the `corpus/` stations (`check-spec-structure`,
   `check-scenario-overlap`, `align-spec`) in-session and **never** write a spec's `status`. A station
   is **not** a dependency — you depend on the corpus structure + discovery, not on any given station

package/dist/check-project-specs/scripts/check-project-specs.js

@@ -67,6 +67,7 @@ const ENGINES = [
 */
 function enginePath(e, here = HERE) {
 	const skillsDir = resolve(dirname(here), "../..");
+	if (here.endsWith(".bundle.mjs")) return join(skillsDir, e.script.replace(/\.mts$/, ".bundle.mjs"));
 	return join(skillsDir, here.endsWith(".mts") ? e.script : e.script.replace(/\.mts$/, ".js"));
 }
 /** Walk up from `start` for the workspace marker. Returns '' when not found. */

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "cyber-sdd",
-  "version": "0.6.0",
+  "version": "0.7.0",
   "description": "Spec-Driven Development. Scaffold, validate, and maintain behavioral specs (spec.md + .feature files) for software features.",
   "repository": {
     "type": "git",
@@ -32,7 +32,7 @@
     "node": ">=22.11"
   },
   "scripts": {
-    "build": "tsdown",
+    "build": "tsdown && node scripts/build-skill-engines.mjs",
     "build:vendor": "tsdown -c tsdown.vendor.config.ts",
     "check:spec": "node ./skills/check-project-specs/scripts/check-project-specs.mts",
     "test": "node --test \"skills/*/scripts/*.test.mts\"",

package/skills/align-spec/README.md

@@ -6,9 +6,9 @@ spec (or a chosen node set) — for audits, post-large-change verification, and
 only project-spec tool that **reconciles** rather than only reporting.
 
 ```bash
-node scripts/align-spec.mts --spec-dir <spec>                    # audit (TOON drift report)
-node scripts/align-spec.mts --spec-dir <spec> --check            # CI guard (fails on drift)
-node scripts/align-spec.mts --spec-dir <spec> --nodes a,b --base HEAD~1
+node scripts/align-spec.mjs --spec-dir <spec>                    # audit (TOON drift report)
+node scripts/align-spec.mjs --spec-dir <spec> --check            # CI guard (fails on drift)
+node scripts/align-spec.mjs --spec-dir <spec> --nodes a,b --base HEAD~1
 ```
 
 Detect splits into a mechanical **scenario-diff** (this engine, reusing `spec-gate`'s

package/skills/align-spec/SKILL.md

@@ -22,7 +22,7 @@ node-shape or propose splits (`check-spec-structure`'s job).
 ## Run the scan
 
 ```bash
-node "<skill>/scripts/align-spec.mts" [--spec-dir <spec>] [--nodes <a,b,...>] [--base <ref>] [--check] [--format toon|json]
+node "<skill>/scripts/align-spec.mjs" [--spec-dir <spec>] [--nodes <a,b,...>] [--base <ref>] [--check] [--format toon|json]
 ```
 
 - Default `--spec-dir` is `.`; default `--base` is `HEAD` (the scenario-diff baseline); default