create-pmos 0.1.1 → 0.1.2

package/README.md

@@ -50,6 +50,30 @@ Next steps in /home/you/my-product:
 Do those three lines and setup is over. A fresh kit with zero history is not behind — it is
 exactly where every product starts.
 
+### Behind a corporate proxy? (403 on install)
+
+On many work laptops, npm goes through a company registry mirror — and a brand-new public package
+gets **403 Forbidden** until it's been vetted (a sandboxed AI session's network proxy can do the
+same). That's your environment being careful, not something broken — and there are three clean
+ways through:
+
+1. **Try a plain terminal first** — if the 403 came from inside an AI-session sandbox, the normal
+   terminal may just work.
+2. **Ask IT to allowlist `create-pmos`** — a routine request, and an easy one: public npm, MIT,
+   zero dependencies, no install scripts, no network code.
+3. **The registry-free install** — the package is just a file, so skip the registry entirely.
+   From any allowed network, download
+   `https://registry.npmjs.org/create-pmos/-/create-pmos-<version>.tgz`, move it to the work
+   machine, then:
+
+   ```bash
+   tar xzf create-pmos-*.tgz
+   node package/bin/create-pmos.js my-product
+   ```
+
+   Same result, byte-identical kit, no proxy involved. (Which is fitting — keeping your work
+   inside your own boundary is the whole point of this kit.)
+
 ## Your first conversation
 
 Open the folder with your coding agent and talk to it like a colleague — clear about the goal,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-pmos",
-  "version": "0.1.1",
+  "version": "0.1.2",
   "description": "Scaffold the PMOS portable kit — run the PMOS product-management workflow (initiative → PRD → eval rubric → contract → build → three gates) entirely inside your own repo, with all state as git-versioned files. No database, no network, no telemetry.",
   "license": "MIT",
   "bin": {

package/payload/KIT-VERSION

@@ -1,3 +1,3 @@
-kernel-source: pmos@30a011b
+kernel-source: pmos@e558777
 assembled: 2026-07-17
 mode: vendor

package/payload/README.md

@@ -35,6 +35,11 @@ workflow: `initiative/<id>` branches, merge = Acceptance), but GitHub is optiona
 existing code there is nothing to ingest: start by seeding `planning/okrs/` (the okr skill) and a
 first right-sized initiative; the product's code grows in the same folder.
 
+**403 on `npx` (corporate proxy/mirror)?** Try a plain terminal (not a sandboxed AI session); ask
+IT to allowlist `create-pmos` (zero deps, no install scripts, no network code); or install
+registry-free — download the `.tgz` from `registry.npmjs.org/create-pmos/-/create-pmos-<v>.tgz`
+on any allowed network, then `tar xzf create-pmos-*.tgz && node package/bin/create-pmos.js <dir>`.
+
 **No GitHub?** Skip the workflow file and run the gate by hand before merging any initiative
 branch: `HEAD_REF=$(git branch --show-current) bash pmos/scripts/gate-initiative.sh` — green means
 anchored; your local `git merge` is the Acceptance Gate. If the repo later lands on GitHub, copy