cyber-sdd 0.6.0 → 0.7.0

package/skills/touch-set-correction/scripts/touch-set-correction.mjs

@@ -0,0 +1,12 @@
+// Launcher for the engine of the same name. Run it as `node <skill>/scripts/<engine>.mjs`.
+// A checkout runs the .mts source. An npm install keeps the skill under node_modules, where Node
+// will not strip types, so it runs the self-contained bundle built for the package.
+import { spawnSync } from 'node:child_process'
+import { fileURLToPath } from 'node:url'
+
+const self = fileURLToPath(import.meta.url)
+const installed = /[\\/]node_modules[\\/]/.test(self)
+const target = self.replace(/\.mjs$/, installed ? '.bundle.mjs' : '.mts')
+const run = spawnSync(process.execPath, [...process.execArgv, target, ...process.argv.slice(2)], { stdio: 'inherit' })
+if (run.error) throw run.error
+process.exitCode = run.status ?? 1

package/skills/touch-set-correction/scripts/touch-set-correction.mts

@@ -206,8 +206,17 @@ export function readChangedFiles(base: string, head: string, cwd: string): { pat
 	return results
 }
 
-const HERE = dirname(fileURLToPath(import.meta.url))
-const RESOLVE_GOVERNANCES_PATH = join(HERE, '..', '..', 'resolve-governances', 'scripts', 'resolve-governances.mts')
+const HERE = fileURLToPath(import.meta.url)
+// A bundle (built for npm, where Node will not strip types) runs its sibling engines as bundles too.
+const ENGINE_EXT = HERE.endsWith('.mts') ? '.mts' : '.bundle.mjs'
+const RESOLVE_GOVERNANCES_PATH = join(
+	dirname(HERE),
+	'..',
+	'..',
+	'resolve-governances',
+	'scripts',
+	`resolve-governances${ENGINE_EXT}`,
+)
 
 /** Resolves one file's artifact-type via `resolve-governances --path` (best-effort — its own
  *  no-match "classify by convention" case). On ANY failure (absent tool, bad JSON, non-zero exit)
@@ -299,7 +308,7 @@ export function collectChangedFiles(base: string, head: string, root: string, cw
 	}))
 }
 
-const DISCOVER_SPECS_PATH = join(HERE, '..', '..', 'discover-specs', 'scripts', 'discover-specs.mts')
+const DISCOVER_SPECS_PATH = join(dirname(HERE), '..', '..', 'discover-specs', 'scripts', `discover-specs${ENGINE_EXT}`)
 
 interface DiscoveredSpec {
 	path: string

package/skills/verify-scenarios/README.md

@@ -16,7 +16,7 @@ The engine imports gherkin-cli from the spec gate's committed bundle
 (`../spec-gate/vendor/gherkin-cli.mjs`), so it runs from an installed plugin.
 
 ```bash
-node scripts/verify-scenarios.mts --feature .agents/spec/identity/identity.feature --node cyberlegion/identity
-node scripts/verify-scenarios.mts --feature x.feature --node proj/x --run --config .agents/sdd/scenario-bridge.toml
-node scripts/verify-scenarios.mts --feature x.feature --node proj/x --report .agents/.scenario-report.xml --format json
+node scripts/verify-scenarios.mjs --feature .agents/spec/identity/identity.feature --node cyberlegion/identity
+node scripts/verify-scenarios.mjs --feature x.feature --node proj/x --run --config .agents/sdd/scenario-bridge.toml
+node scripts/verify-scenarios.mjs --feature x.feature --node proj/x --report .agents/.scenario-report.xml --format json
 ```

package/skills/verify-scenarios/SKILL.md

@@ -74,7 +74,7 @@ Hand-rolled regex parse, no xml dependency — verified against vitest 4.1.7's J
 ## Run
 
 ```bash
-node "<skill>/scripts/verify-scenarios.mts" \
+node "<skill>/scripts/verify-scenarios.mjs" \
   --feature <path/to/x.feature> --node <project>/<node> \
   [--config .agents/sdd/scenario-bridge.toml] [--root .] [--feature-root <dir>] \
   [--report <xml>] [--run] [--format toon|json]
@@ -100,7 +100,7 @@ report — the common monorepo shape, where specs sit at a repo-root spec corpus
 sit under its `project-path` (e.g. `packages/<project>/`):
 
 ```bash
-node "<skill>/scripts/verify-scenarios.mts" \
+node "<skill>/scripts/verify-scenarios.mjs" \
   --feature .agents/specs/cyberlegion-plugin/identity/identity.feature \
   --node cyberlegion-plugin/identity \
   --feature-root . \
@@ -110,7 +110,7 @@ node "<skill>/scripts/verify-scenarios.mts" \
 ## Boundaries
 
 Read-only over the `.feature` and test reports; writes nothing. Consumes `gherkin-cli` (via `npx
-gherkin-cli@0.0.2 parse <feature> --format json`) for the scenario set — never re-implements a
+gherkin-cli parse <feature> --format json`) for the scenario set — never re-implements a
 Gherkin parser. Does not reorganize `.feature` files by runner and does not wire itself into the
 impl-judge (a separate CR grows the default `sdd-impl-judge` to call this for deterministic
 artifact-types, run through SDD's own spec gate).