sdtk-kit 1.1.0 → 1.2.0

package/LICENSE

@@ -1,21 +1,21 @@
-MIT License
-
-Copyright (c) 2026 SDTK
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
+MIT License
+
+Copyright (c) 2026 SDTK
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -1,135 +1,135 @@
-# sdtk-kit
-
-> Install all five SDTK toolkits in one command.
-
-```bash
-npm install -g sdtk-kit
-```
-
-After install, all five SDTK CLI tools are available globally:
-
-| CLI           | Toolkit        | Purpose                                          |
-|---------------|----------------|--------------------------------------------------|
-| `sdtk-spec`   | SDTK-SPEC      | Spec-first SDLC: PM → BA → ARCH → DEV → QA     |
-| `sdtk-design` | SDTK-DESIGN    | MVP design: idea → prototype → handoff           |
-| `sdtk-code`   | SDTK-CODE      | Governed coding: handoff → PR with review gates  |
-| `sdtk-ops`    | SDTK-OPS       | Operations: deploy → smoke → sign-off            |
-| `sdtk-wiki`   | SDTK-WIKI      | Local second brain: your project memory          |
-
-## Quick start
-
-```bash
-# Initialize the spec toolkit in your project
-sdtk-spec init --runtime claude   # or --runtime codex
-
-# Generate a 17-file spec scaffold for your first feature
-sdtk-spec generate --feature-key MY_FEATURE
-```
-
-## Unified vs standalone install
-
-You have two install options:
-
-**Option 1 — Install everything at once (recommended for new projects)**
-
-```bash
-npm install -g sdtk-kit
-```
-
-npm installs all five sub-toolkits as dependencies. All CLI binaries land on PATH in one step.
-
-**Option 2 — Install individual toolkits**
-
-```bash
-npm install -g sdtk-spec-kit    # spec / planning
-npm install -g sdtk-design-kit  # design
-npm install -g sdtk-code-kit    # coding
-npm install -g sdtk-ops-kit     # operations
-npm install -g sdtk-wiki-kit    # local second brain
-```
-
-Use Option 2 if you only need one or two toolkits, or if you want granular version control per toolkit.
-
-Both options are permanently supported. `sdtk-kit` does not replace the standalone packages.
-
-## How the unified CLI works (maintainer note)
-
-`sdtk-kit` declares the five sub-toolkits as dependencies AND ships thin bin
-shims (`bin/sdtk-*.js`) that re-export each sub-package's CLI. This is required
-because `npm install -g <pkg>` only links the bin entries of the top-level
-package, never of its dependencies. A pure deps-only meta-package would install
-the sub-toolkits but leave zero CLIs on PATH.
-
-Do not remove the `bin` field or the `bin/` shims — they are the mechanism that
-puts `sdtk-spec`, `sdtk-code`, `sdtk-ops`, `sdtk-design`, and `sdtk-wiki` on PATH
-after a global install.
-
-## Version pinning model
-
-`sdtk-kit` uses caret-range dependencies (`^X.Y.Z`) on each sub-toolkit. This means:
-
-- **Patch and minor updates** of sub-toolkits are picked up automatically when you run `npm update -g sdtk-kit`.
-- **Major version bumps** in any sub-toolkit require a coordinated `sdtk-kit` major-bump and re-publish.
-- If you need exact version control per toolkit, use standalone packages instead.
-
-Current pinned versions (as of sdtk-kit v1.0.0):
-
-| Package          | Version |
-|------------------|---------|
-| sdtk-spec-kit    | ^0.4.7  |
-| sdtk-code-kit    | ^0.1.3  |
-| sdtk-ops-kit     | ^0.2.4  |
-| sdtk-design-kit  | ^0.3.0  |
-| sdtk-wiki-kit    | ^0.1.4  |
-
-## Updating
-
-```bash
-npm update -g sdtk-kit
-```
-
-This updates all sub-toolkits within their caret ranges.
-
-## Uninstalling
-
-To remove sdtk-kit and its sub-toolkits:
-
-```bash
-npm uninstall -g sdtk-kit
-```
-
-Note: `npm uninstall` removes the package and its transitive dependencies. If you had any sub-toolkits installed standalone _before_ installing sdtk-kit, npm may or may not remove them depending on your npm version. Run `npm uninstall -g sdtk-spec-kit sdtk-code-kit sdtk-ops-kit sdtk-design-kit sdtk-wiki-kit` to be sure.
-
-## Troubleshooting
-
-**Command not found after install**
-
-Re-open your terminal. npm global installs require a new shell session on some systems.
-
-Check your global prefix:
-
-```bash
-npm config get prefix
-```
-
-Ensure `<prefix>/bin` is in `PATH`.
-
-**Windows PATH issues**
-
-On Windows, npm global binaries land in `%APPDATA%\npm`. Make sure this is in your `PATH`. Run `npm config get prefix` to confirm the location.
-
-**Binary collision**
-
-If you have standalone sub-toolkits installed at different versions than what `sdtk-kit` pins, `npm install -g sdtk-kit` will upgrade them to the pinned versions. To keep a standalone version pinned, install it standalone after sdtk-kit:
-
-```bash
-npm install -g sdtk-kit
-npm install -g sdtk-spec-kit@0.4.6  # pin to an older version
-```
-
-## Links
-
-- Docs: [https://sdtk.dev](https://sdtk.dev)
-- Source: [https://github.com/codexsdtk/sdtk-toolkit](https://github.com/codexsdtk/sdtk-toolkit)
-- Issues: [https://github.com/codexsdtk/sdtk-toolkit/issues](https://github.com/codexsdtk/sdtk-toolkit/issues)
-- License: MIT
+# sdtk-kit
+
+> Install all five SDTK toolkits in one command.
+
+```bash
+npm install -g sdtk-kit
+```
+
+After install, all five SDTK CLI tools are available globally:
+
+| CLI           | Toolkit        | Purpose                                          |
+|---------------|----------------|--------------------------------------------------|
+| `sdtk-spec`   | SDTK-SPEC      | Spec-first SDLC: PM → BA → ARCH → DEV → QA     |
+| `sdtk-design` | SDTK-DESIGN    | MVP design: idea → prototype → handoff           |
+| `sdtk-code`   | SDTK-CODE      | Governed coding: handoff → PR with review gates  |
+| `sdtk-ops`    | SDTK-OPS       | Operations: deploy → smoke → sign-off            |
+| `sdtk-wiki`   | SDTK-WIKI      | Local second brain: your project memory          |
+
+## Quick start
+
+```bash
+# Initialize the spec toolkit in your project
+sdtk-spec init --runtime claude   # or --runtime codex
+
+# Generate a 17-file spec scaffold for your first feature
+sdtk-spec generate --feature-key MY_FEATURE
+```
+
+## Unified vs standalone install
+
+You have two install options:
+
+**Option 1 — Install everything at once (recommended for new projects)**
+
+```bash
+npm install -g sdtk-kit
+```
+
+npm installs all five sub-toolkits as dependencies. All CLI binaries land on PATH in one step.
+
+**Option 2 — Install individual toolkits**
+
+```bash
+npm install -g sdtk-spec-kit    # spec / planning
+npm install -g sdtk-design-kit  # design
+npm install -g sdtk-code-kit    # coding
+npm install -g sdtk-ops-kit     # operations
+npm install -g sdtk-wiki-kit    # local second brain
+```
+
+Use Option 2 if you only need one or two toolkits, or if you want granular version control per toolkit.
+
+Both options are permanently supported. `sdtk-kit` does not replace the standalone packages.
+
+## How the unified CLI works (maintainer note)
+
+`sdtk-kit` declares the five sub-toolkits as dependencies AND ships thin bin
+shims (`bin/sdtk-*.js`) that re-export each sub-package's CLI. This is required
+because `npm install -g <pkg>` only links the bin entries of the top-level
+package, never of its dependencies. A pure deps-only meta-package would install
+the sub-toolkits but leave zero CLIs on PATH.
+
+Do not remove the `bin` field or the `bin/` shims — they are the mechanism that
+puts `sdtk-spec`, `sdtk-code`, `sdtk-ops`, `sdtk-design`, and `sdtk-wiki` on PATH
+after a global install.
+
+## Version pinning model
+
+`sdtk-kit` uses caret-range dependencies (`^X.Y.Z`) on each sub-toolkit. This means:
+
+- **Patch and minor updates** of sub-toolkits are picked up automatically when you run `npm update -g sdtk-kit`.
+- **Major version bumps** in any sub-toolkit require a coordinated `sdtk-kit` major-bump and re-publish.
+- If you need exact version control per toolkit, use standalone packages instead.
+
+Current pinned versions (as of sdtk-kit v1.0.0):
+
+| Package          | Version |
+|------------------|---------|
+| sdtk-spec-kit    | ^0.4.7  |
+| sdtk-code-kit    | ^0.1.3  |
+| sdtk-ops-kit     | ^0.2.4  |
+| sdtk-design-kit  | ^0.3.0  |
+| sdtk-wiki-kit    | ^0.1.4  |
+
+## Updating
+
+```bash
+npm update -g sdtk-kit
+```
+
+This updates all sub-toolkits within their caret ranges.
+
+## Uninstalling
+
+To remove sdtk-kit and its sub-toolkits:
+
+```bash
+npm uninstall -g sdtk-kit
+```
+
+Note: `npm uninstall` removes the package and its transitive dependencies. If you had any sub-toolkits installed standalone _before_ installing sdtk-kit, npm may or may not remove them depending on your npm version. Run `npm uninstall -g sdtk-spec-kit sdtk-code-kit sdtk-ops-kit sdtk-design-kit sdtk-wiki-kit` to be sure.
+
+## Troubleshooting
+
+**Command not found after install**
+
+Re-open your terminal. npm global installs require a new shell session on some systems.
+
+Check your global prefix:
+
+```bash
+npm config get prefix
+```
+
+Ensure `<prefix>/bin` is in `PATH`.
+
+**Windows PATH issues**
+
+On Windows, npm global binaries land in `%APPDATA%\npm`. Make sure this is in your `PATH`. Run `npm config get prefix` to confirm the location.
+
+**Binary collision**
+
+If you have standalone sub-toolkits installed at different versions than what `sdtk-kit` pins, `npm install -g sdtk-kit` will upgrade them to the pinned versions. To keep a standalone version pinned, install it standalone after sdtk-kit:
+
+```bash
+npm install -g sdtk-kit
+npm install -g sdtk-spec-kit@0.4.6  # pin to an older version
+```
+
+## Links
+
+- Docs: [https://sdtk.dev](https://sdtk.dev)
+- Source: [https://github.com/codexsdtk/sdtk-toolkit](https://github.com/codexsdtk/sdtk-toolkit)
+- Issues: [https://github.com/codexsdtk/sdtk-toolkit/issues](https://github.com/codexsdtk/sdtk-toolkit/issues)
+- License: MIT

package/bin/sdtk-code.js

@@ -1,6 +1,6 @@
-#!/usr/bin/env node
-"use strict";
-
-// Bin shim — re-exports the sdtk-code CLI from the sdtk-code-kit dependency.
-// See bin/sdtk-spec.js for the rationale behind these shims.
-require("sdtk-code-kit/bin/sdtk-code.js");
+#!/usr/bin/env node
+"use strict";
+
+// Bin shim — re-exports the sdtk-code CLI from the sdtk-code-kit dependency.
+// See bin/sdtk-spec.js for the rationale behind these shims.
+require("sdtk-code-kit/bin/sdtk-code.js");

package/bin/sdtk-design.js

@@ -1,6 +1,6 @@
-#!/usr/bin/env node
-"use strict";
-
-// Bin shim — re-exports the sdtk-design CLI from the sdtk-design-kit dependency.
-// See bin/sdtk-spec.js for the rationale behind these shims.
-require("sdtk-design-kit/bin/sdtk-design.js");
+#!/usr/bin/env node
+"use strict";
+
+// Bin shim — re-exports the sdtk-design CLI from the sdtk-design-kit dependency.
+// See bin/sdtk-spec.js for the rationale behind these shims.
+require("sdtk-design-kit/bin/sdtk-design.js");

package/bin/sdtk-ops.js

@@ -1,6 +1,6 @@
-#!/usr/bin/env node
-"use strict";
-
-// Bin shim — re-exports the sdtk-ops CLI from the sdtk-ops-kit dependency.
-// See bin/sdtk-spec.js for the rationale behind these shims.
-require("sdtk-ops-kit/bin/sdtk-ops.js");
+#!/usr/bin/env node
+"use strict";
+
+// Bin shim — re-exports the sdtk-ops CLI from the sdtk-ops-kit dependency.
+// See bin/sdtk-spec.js for the rationale behind these shims.
+require("sdtk-ops-kit/bin/sdtk-ops.js");

package/bin/sdtk-spec.js

@@ -1,12 +1,12 @@
-#!/usr/bin/env node
-"use strict";
-
-// Bin shim — re-exports the sdtk-spec CLI from the sdtk-spec-kit dependency.
-//
-// Why this exists: `npm install -g <pkg>` only links the bin entries of the
-// top-level package, NOT of its dependencies. A pure meta-package (deps only,
-// no bin) therefore installs the sub-packages but leaves no CLI on PATH.
-//
-// Each sub-toolkit CLI reads process.argv directly, so requiring its bin
-// entry here runs it with the real arguments unchanged.
-require("sdtk-spec-kit/bin/sdtk.js");
+#!/usr/bin/env node
+"use strict";
+
+// Bin shim — re-exports the sdtk-spec CLI from the sdtk-spec-kit dependency.
+//
+// Why this exists: `npm install -g <pkg>` only links the bin entries of the
+// top-level package, NOT of its dependencies. A pure meta-package (deps only,
+// no bin) therefore installs the sub-packages but leaves no CLI on PATH.
+//
+// Each sub-toolkit CLI reads process.argv directly, so requiring its bin
+// entry here runs it with the real arguments unchanged.
+require("sdtk-spec-kit/bin/sdtk.js");

package/bin/sdtk-wiki.js

@@ -1,6 +1,6 @@
-#!/usr/bin/env node
-"use strict";
-
-// Bin shim — re-exports the sdtk-wiki CLI from the sdtk-wiki-kit dependency.
-// See bin/sdtk-spec.js for the rationale behind these shims.
-require("sdtk-wiki-kit/bin/sdtk-wiki.js");
+#!/usr/bin/env node
+"use strict";
+
+// Bin shim — re-exports the sdtk-wiki CLI from the sdtk-wiki-kit dependency.
+// See bin/sdtk-spec.js for the rationale behind these shims.
+require("sdtk-wiki-kit/bin/sdtk-wiki.js");

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "sdtk-kit",
-  "version": "1.1.0",
+  "version": "1.2.0",
   "description": "Install all five SDTK toolkits in one command. Meta-package for sdtk-spec-kit, sdtk-code-kit, sdtk-ops-kit, sdtk-design-kit, and sdtk-wiki-kit.",
   "type": "commonjs",
   "bin": {
@@ -22,7 +22,7 @@
   },
   "dependencies": {
     "sdtk-spec-kit": "^0.4.7",
-    "sdtk-code-kit": "^0.2.0",
+    "sdtk-code-kit": "^0.3.0",
     "sdtk-ops-kit": "^0.2.4",
     "sdtk-design-kit": "^0.3.0",
     "sdtk-wiki-kit": "^0.2.0"

package/scripts/postinstall.js

@@ -1,40 +1,40 @@
-#!/usr/bin/env node
-"use strict";
-
-// Skip banner in CI environments and headless installs.
-// This avoids noisy output in automated pipelines that install sdtk-kit
-// as a transitive dependency.
-const isCI =
-  process.env.CI === "true" ||
-  process.env.NODE_ENV === "test" ||
-  process.env.npm_config_loglevel === "silent" ||
-  process.env.npm_config_loglevel === "error";
-
-if (isCI) {
-  process.exit(0);
-}
-
-const lines = [
-  "",
-  "  ╔══════════════════════════════════════════════════════╗",
-  "  ║            SDTK — All Five Toolkits Installed        ║",
-  "  ╚══════════════════════════════════════════════════════╝",
-  "",
-  "  You now have all five SDTK CLI tools available:",
-  "",
-  "    sdtk-spec    — Spec-first SDLC: PM → BA → ARCH → DEV → QA",
-  "    sdtk-design  — MVP design: idea → prototype → handoff",
-  "    sdtk-code    — Governed coding: handoff → PR with review gates",
-  "    sdtk-ops     — Operations: deploy → smoke → sign-off",
-  "    sdtk-wiki    — Local second brain: your project memory",
-  "",
-  "  Start with the SPEC toolkit:",
-  "",
-  "    sdtk-spec init --runtime claude   (or --runtime codex)",
-  "    sdtk-spec generate --feature-key <YOUR_FEATURE>",
-  "",
-  "  Docs: https://sdtk.dev",
-  "",
-];
-
-process.stdout.write(lines.join("\n") + "\n");
+#!/usr/bin/env node
+"use strict";
+
+// Skip banner in CI environments and headless installs.
+// This avoids noisy output in automated pipelines that install sdtk-kit
+// as a transitive dependency.
+const isCI =
+  process.env.CI === "true" ||
+  process.env.NODE_ENV === "test" ||
+  process.env.npm_config_loglevel === "silent" ||
+  process.env.npm_config_loglevel === "error";
+
+if (isCI) {
+  process.exit(0);
+}
+
+const lines = [
+  "",
+  "  ╔══════════════════════════════════════════════════════╗",
+  "  ║            SDTK — All Five Toolkits Installed        ║",
+  "  ╚══════════════════════════════════════════════════════╝",
+  "",
+  "  You now have all five SDTK CLI tools available:",
+  "",
+  "    sdtk-spec    — Spec-first SDLC: PM → BA → ARCH → DEV → QA",
+  "    sdtk-design  — MVP design: idea → prototype → handoff",
+  "    sdtk-code    — Governed coding: handoff → PR with review gates",
+  "    sdtk-ops     — Operations: deploy → smoke → sign-off",
+  "    sdtk-wiki    — Local second brain: your project memory",
+  "",
+  "  Start with the SPEC toolkit:",
+  "",
+  "    sdtk-spec init --runtime claude   (or --runtime codex)",
+  "    sdtk-spec generate --feature-key <YOUR_FEATURE>",
+  "",
+  "  Docs: https://sdtk.dev",
+  "",
+];
+
+process.stdout.write(lines.join("\n") + "\n");