cyber-sdd 0.7.0 → 0.7.1

package/skills/spec-producer-governance/SKILL.md

@@ -40,7 +40,7 @@ USER_ANSWERS:     <answers to previously returned QUESTIONS — or null>
 
    **A `Given` is a test vector, not specification** (`sdd:suite-format-governance` carries the canonical bar and the swap test). Author each `Given`'s apparatus — its domain, entities, names, framing — from a domain **the artifact does not illustrate**. On a revise CR the apparatus never reuses the artifact's existing worked examples; on `BACKFILL` it never reuses the illustrations you read out of source. Read those examples in full at step 1 — they are evidence of the behavior you are specifying; exclude them only from the apparatus you author into a `Given`.
 
-5. **Self-check the `.feature` form before returning.** Run the deterministic form check — the `check-suite` engine (`scripts/check-suite.mts` in the `spec-gate` skill), the executable form of `sdd:suite-format-governance` — scoped to what you just authored:
+5. **Self-check the `.feature` form before returning.** Run the deterministic form check — the `check-suite` engine (`scripts/check-suite.mjs` in the `spec-gate` skill), the executable form of `sdd:suite-format-governance` — scoped to what you just authored:
 
    ```bash
    node "<spec-gate skill>/scripts/check-suite.mjs" --files <the authored .feature path(s)>
@@ -58,7 +58,7 @@ USER_ANSWERS:     <answers to previously returned QUESTIONS — or null>
 
    **Check coverage and mirroring before returning.** Every outcome and carve-out the node's `## Use Cases` / README states — including an exception named only in prose — must have at least one scenario; do not report `STATUS: complete` while a stated outcome or carve-out has none — add the missing scenario. A **duty specified on one node of a mirrored pair** (producer/judge, sender/receiver) must be **mirrored on the counterpart node**; do not report complete while only one side carries the duty — specify it on the counterpart too (`sdd:suite-format-governance`).
 
-   Also self-run **referenced-artifact-exists** — `check-spec-state.mts` in `scripts/`, scoped to
+   Also self-run **referenced-artifact-exists** — `check-spec-state.mjs` in `scripts/`, scoped to
    the `spec.md`/`README.md` you just authored or touched:
 
    ```bash

package/skills/start-mission/SKILL.md

@@ -90,7 +90,7 @@ For each unit the CR touches:
 3. On convergence → exit to the spec gate.
 4. On `blocked`, or the cap hit without converging → **do not auto-accept**. Present the failing scenarios and ask the user to **accept as-is**, **keep looping** (reset the count), or **change direction**.
 
-**Freeze re-open guard.** A node at `status: approved` or `implemented` has a **frozen `.feature`**. The unfreeze trigger is **risk, not phase** (`sdd:lifecycle-governance`), so what you may do to that file depends on the *edit class*, not on it being frozen — read the edit class **structurally**, per named `Scenario`, **never from a raw line diff** (a step orphaned off a frozen scenario onto a new adjacent scenario shows no `-` line and would misread as additive): `npx gherkin-cli@0.0.2 diff --base <baseref> <file> --format json` (`addOnly` / only `added` ⇒ additive; any `modified`/`removed` ⇒ examine for narrowing), or the spec-gate's `plugins/sdd/skills/spec-gate/scripts/classify-edit-class.mts` which wraps this same structural diff plus git rename detection. An **additive** scenario (new behavior, nothing weakened) **self-clears — it stays `@frozen`, needs no re-open**; a **pure move/rename** (`git mv`, zero content delta) likewise **preserves freeze and is not a gate-able edit**. Only a **narrowing or rewriting** edit to an existing scenario is a re-open — a freeze transition and a `status` write you do not own, so confirm it was **ratified** (the lightweight async re-open flag) before touching that scenario's content. **Never narrow or rewrite a frozen scenario without the ratified re-open**; adding and relocating need none.
+**Freeze re-open guard.** A node at `status: approved` or `implemented` has a **frozen `.feature`**. The unfreeze trigger is **risk, not phase** (`sdd:lifecycle-governance`), so what you may do to that file depends on the *edit class*, not on it being frozen — read the edit class **structurally**, per named `Scenario`, **never from a raw line diff** (a step orphaned off a frozen scenario onto a new adjacent scenario shows no `-` line and would misread as additive): `npx gherkin-cli@0.0.2 diff --base <baseref> <file> --format json` (`addOnly` / only `added` ⇒ additive; any `modified`/`removed` ⇒ examine for narrowing), or the spec-gate's `plugins/sdd/skills/spec-gate/scripts/classify-edit-class.mjs` which wraps this same structural diff plus git rename detection. An **additive** scenario (new behavior, nothing weakened) **self-clears — it stays `@frozen`, needs no re-open**; a **pure move/rename** (`git mv`, zero content delta) likewise **preserves freeze and is not a gate-able edit**. Only a **narrowing or rewriting** edit to an existing scenario is a re-open — a freeze transition and a `status` write you do not own, so confirm it was **ratified** (the lightweight async re-open flag) before touching that scenario's content. **Never narrow or rewrite a frozen scenario without the ratified re-open**; adding and relocating need none.
 
 **Route observations.** Each production-chain producer (spec-, impl-, solution-producer) may surface typed `OBSERVATIONS` (`architect` | `strategist`); never act on them silently. When several producers surface observations in one segment, **forward every producer's observations to the plan — drop or filter none of them** — and **spawn no spec of your own** from them. A granularity / split observation becomes a **new node** or a **project-spec** operation (the plan's or the user's call) — never a marker grown into this node, and never a spawn you make here. An observation the plan or user then **declines** is dropped by that decision — an explicit call, not silent loss.
 

package/skills/suite-format-governance/README.md

@@ -40,7 +40,7 @@ order, stepping down from the happy path to its branches and errors.
 ## The executable check — `check-suite`
 
 The mechanical rules — Gherkin validity, boolean `Then`s, section comments, Outline coverage, and
-the scenario-map binding — are linted by `check-suite` (`spec-gate/scripts/check-suite.mts`). The
+the scenario-map binding — are linted by `check-suite` (`spec-gate/scripts/check-suite.mjs`). The
 spec-producer self-runs it before returning, and the spec gate runs it fail-closed before the cold
 judge. It checks **form only**: whether the map's rows actually cover the drawn CFG — coverage,
 discrimination, consistency — is judged, never linted, so a green check clears no coverage

package/skills/suite-format-governance/SKILL.md

@@ -304,7 +304,7 @@ every scenario carries a map row, every row names a real scenario, and no two ro
 *and* a path class. Whether the rows **cover the CFG** is judged, not linted: that needs the drawn
 CFG's semantics, so a green check clears no coverage question. A spec with no `## Scenario map`
 section is skipped, not failed — run as `check-suite`
-(`spec-gate/scripts/check-suite.mts`): the spec-producer self-runs it before returning, and the spec
+(`spec-gate/scripts/check-suite.mjs`): the spec-producer self-runs it before returning, and the spec
 gate runs it fail-closed before the cold judge.
 
 **Form only** — coverage adequacy, discrimination,

package/skills/touch-set-correction/README.md

@@ -9,11 +9,11 @@ cyberplace repository, not shipped in this package) carries the authoritative be
 and the frozen 21-scenario contract.
 
 - **Skill contract:** [`SKILL.md`](./SKILL.md)
-- **Script:** [`scripts/touch-set-correction.mts`](./scripts/touch-set-correction.mts)
-- **Tests:** [`scripts/touch-set-correction.test.mts`](./scripts/touch-set-correction.test.mts)
+- **Script:** [`scripts/touch-set-correction.mjs`](./scripts/touch-set-correction.mjs)
+- **Tests:** [`src/touch-set-correction/touch-set-correction.test.mts`](../../src/touch-set-correction/touch-set-correction.test.mts)
   (`node:test`) — one test per frozen scenario, titled `scenario: <verbatim frozen scenario name>`.
-  [`scripts/touch-set-correction-installed.test.mts`](./scripts/touch-set-correction-installed.test.mts)
+  [`src/touch-set-correction/touch-set-correction-installed.test.mts`](../../src/touch-set-correction/touch-set-correction-installed.test.mts)
   runs the engine from a copy of the plugin's files, with no `node_modules`.
 
-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.
+The build inlines gherkin-cli into the compiled script from the committed bundle
+`src/vendor/gherkin-cli.mjs`, so it runs from an installed plugin.

package/skills/touch-set-correction/SKILL.md

@@ -36,7 +36,7 @@ touched.
 Pure derivations (`isFeature`, `fileToNode`, `reconcile`, `assembleCorrection`) take and return
 plain data — no fs/network access — kept apart from a thin IO seam (`readChangedFiles`,
 `resolveArtifactType`, `changedScenarios`, `collectChangedFiles`, `discoverLayouts`) that shells out
-to `git`, `resolve-governances.mts`, and `npx gherkin-cli`.
+to `git`, `resolve-governances.mjs`, and `npx gherkin-cli`.
 
 ## Run it