cyber-sdd 0.6.1 → 0.7.1

package/.claude-plugin/plugin.json

@@ -1,13 +1,12 @@
 {
-	"$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
 	"name": "sdd",
+	"version": "0.7.1",
 	"description": "Spec-Driven Development. Scaffold, validate, and maintain behavioral specs (spec.md + .feature files) for software features.",
 	"author": {
 		"name": "unional"
 	},
 	"homepage": "https://github.com/cyberuni/cyber-sdd",
 	"repository": "https://github.com/cyberuni/cyber-sdd",
-	"version": "0.6.1",
 	"skills": "./skills",
 	"agents": [
 		"./agents/sdd-automaton.md",

package/.codex-plugin/plugin.json

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

package/agents/sdd-scanner.md

@@ -82,7 +82,7 @@ count** maintained in the ledger.
   idempotent: **before drafting**, detect whether the mission was **already distilled** (a prior
   `strategy` entry whose `distills` equals its `<cr-ref>`) and if so **draft nothing**. Decide this by a
   **structured JSONL parse, never a substring/regex text match** — **reuse** the exported
-  `distilledCrRefs` engine from `../skills/plan-retirement/scripts/retire-plans.mts` over the project
+  `distilledCrRefs` engine from `../skills/plan-retirement/scripts/retire-plans.mjs` over the project
   `ledger/` directory and membership-test the `<cr-ref>`. It parses each line with `JSON.parse`, so it
   is correct against a **pretty-printed** entry (a space after the colon), a wrapped or reordered
   object — a naive no-space grep (`"distills":"<cr-ref>"`) silently under-counts and re-drafts an

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/package.json

@@ -1,6 +1,6 @@
 {
   "name": "cyber-sdd",
-  "version": "0.6.1",
+  "version": "0.7.1",
   "description": "Spec-Driven Development. Scaffold, validate, and maintain behavioral specs (spec.md + .feature files) for software features.",
   "repository": {
     "type": "git",
@@ -10,32 +10,30 @@
   "license": "MIT",
   "type": "module",
   "bin": {
-    "sdd-check-specs": "./dist/check-project-specs/scripts/check-project-specs.js"
+    "sdd-check-specs": "./skills/check-project-specs/scripts/check-project-specs.mjs"
   },
   "files": [
-    "dist",
     "skills",
     "agents",
-    ".plugin",
+    "plugin.json",
     ".codex-plugin",
-    ".claude-plugin",
-    "!skills/**/*.test.mts"
+    ".claude-plugin"
   ],
-  "dependencies": {
-    "gherkin-cli": "0.2.1"
-  },
   "homepage": "https://github.com/cyberuni/cyber-sdd",
   "devDependencies": {
-    "tsdown": "^0.23.0"
+    "gherkin-cli": "0.2.1",
+    "tsdown": "^0.23.0",
+    "universal-plugin": "^0.16.0"
   },
   "engines": {
     "node": ">=22.11"
   },
   "scripts": {
-    "build": "tsdown",
+    "build:skills": "universal-plugin plugin build",
     "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\"",
+    "check:scripts": "universal-plugin plugin build --check",
+    "check:spec": "node ./src/check-project-specs/check-project-specs.mts",
+    "test": "node --test \"src/**/*.test.mts\"",
     "typecheck": "tsc -p tsconfig.json"
   }
 }

package/plugin.json

@@ -0,0 +1,55 @@
+{
+	"$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
+	"name": "sdd",
+	"version": "0.7.1",
+	"description": "Spec-Driven Development. Scaffold, validate, and maintain behavioral specs (spec.md + .feature files) for software features.",
+	"author": {
+		"name": "unional"
+	},
+	"homepage": "https://github.com/cyberuni/cyber-sdd",
+	"repository": "https://github.com/cyberuni/cyber-sdd",
+	"skills": "./skills",
+	"agents": [
+		"./agents/sdd-automaton.md",
+		"./agents/sdd-impl-judge.md",
+		"./agents/sdd-scanner.md",
+		"./agents/sdd-spec-judge.md",
+		"./agents/sdd-warden.md"
+	],
+	"extensions": {
+		"org.cyberuni.universal-plugin": {
+			"vendors": ["claude-code", "codex"],
+			"scripts": {
+				"skills/align-spec/scripts/align-spec.mjs": "src/align-spec/align-spec.mts",
+				"skills/blast-estimate/scripts/blast-estimate.mjs": "src/blast-estimate/blast-estimate.mts",
+				"skills/check-field-mandates/scripts/check-field-mandates.mjs": "src/check-field-mandates/check-field-mandates.mts",
+				"skills/check-partition-quality/scripts/check-partition-quality.mjs": "src/check-partition-quality/check-partition-quality.mts",
+				"skills/check-plan-safety/scripts/check-plan-safety.mjs": "src/check-plan-safety/check-plan-safety.mts",
+				"skills/check-plugin-manifests/scripts/check-plugin-manifests.mjs": "src/check-plugin-manifests/check-plugin-manifests.mts",
+				"skills/check-project-specs/scripts/check-project-specs.mjs": "src/check-project-specs/check-project-specs.mts",
+				"skills/check-retired-terms/scripts/check-retired-terms.mjs": "src/check-retired-terms/check-retired-terms.mts",
+				"skills/check-scenario-overlap/scripts/check-scenario-overlap.mjs": "src/check-scenario-overlap/check-scenario-overlap.mts",
+				"skills/check-spec-references/scripts/check-spec-references.mjs": "src/check-spec-references/check-spec-references.mts",
+				"skills/check-spec-structure/scripts/check-spec-structure.mjs": "src/check-spec-structure/check-spec-structure.mts",
+				"skills/collision-ladder/scripts/collision-ladder.mjs": "src/collision-ladder/collision-ladder.mts",
+				"skills/concept-index/scripts/concept-index.mjs": "src/concept-index/concept-index.mts",
+				"skills/discover-plans/scripts/discover-plans.mjs": "src/discover-plans/discover-plans.mts",
+				"skills/discover-specs/scripts/discover-specs.mjs": "src/discover-specs/discover-specs.mts",
+				"skills/init/scripts/wire-statusline.mjs": "src/init/wire-statusline.mts",
+				"skills/manage-ignore/scripts/manage-ignore.mjs": "src/manage-ignore/manage-ignore.mts",
+				"skills/manage-scenario-bridge/scripts/manage-scenario-bridge.mjs": "src/manage-scenario-bridge/manage-scenario-bridge.mts",
+				"skills/manage-spec-anchors/scripts/manage-spec-anchors.mjs": "src/manage-spec-anchors/manage-spec-anchors.mts",
+				"skills/mission-graph/scripts/mission-graph.mjs": "src/mission-graph/mission-graph.mts",
+				"skills/place-node/scripts/place-node.mjs": "src/place-node/place-node.mts",
+				"skills/plan-retirement/scripts/retire-plans.mjs": "src/plan-retirement/retire-plans.mts",
+				"skills/resolve-governances/scripts/resolve-governances.mjs": "src/resolve-governances/resolve-governances.mts",
+				"skills/resolve-tracking/scripts/resolve-tracking.mjs": "src/resolve-tracking/resolve-tracking.mts",
+				"skills/spec-gate/scripts/check-spec-state.mjs": "src/spec-gate/check-spec-state.mts",
+				"skills/spec-gate/scripts/check-suite.mjs": "src/spec-gate/check-suite.mts",
+				"skills/spec-gate/scripts/classify-edit-class.mjs": "src/spec-gate/classify-edit-class.mts",
+				"skills/touch-set-correction/scripts/touch-set-correction.mjs": "src/touch-set-correction/touch-set-correction.mts",
+				"skills/verify-scenarios/scripts/verify-scenarios.mjs": "src/verify-scenarios/verify-scenarios.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
@@ -35,7 +35,7 @@ node "<skill>/scripts/align-spec.mts" [--spec-dir <spec>] [--nodes <a,b,...>] [-
 
 ## The procedure — Detect
 
-Detect has two layers, and this skill's engine (`scripts/align-spec.mts`) ships code for only
+Detect has two layers, and this skill's engine (`scripts/align-spec.mjs`) ships code for only
 the mechanical one:
 
 1. **Mechanical scenario-diff (engine code)** — for each node's `.feature`, run the same