sdtk-kit 1.0.0 → 1.0.1

package/README.md

@@ -52,6 +52,18 @@ Use Option 2 if you only need one or two toolkits, or if you want granular versi
 
 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:

package/bin/sdtk-code.js

@@ -0,0 +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");

package/bin/sdtk-design.js

@@ -0,0 +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");

package/bin/sdtk-ops.js

@@ -0,0 +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");

package/bin/sdtk-spec.js

@@ -0,0 +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");

package/bin/sdtk-wiki.js

@@ -0,0 +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");

package/package.json

@@ -1,9 +1,17 @@
 {
   "name": "sdtk-kit",
-  "version": "1.0.0",
+  "version": "1.0.1",
   "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": {
+    "sdtk-spec": "bin/sdtk-spec.js",
+    "sdtk-code": "bin/sdtk-code.js",
+    "sdtk-ops": "bin/sdtk-ops.js",
+    "sdtk-design": "bin/sdtk-design.js",
+    "sdtk-wiki": "bin/sdtk-wiki.js"
+  },
   "files": [
+    "bin/",
     "scripts/",
     "README.md",
     "LICENSE"