create-pmos 0.13.0 → 0.15.0

package/README.md

@@ -333,6 +333,45 @@ Refreshes the skills, concepts, and scripts only. Your records — `state/`, `pl
 `okf/product/` — are yours, and an update never touches them. `pmos/KIT-VERSION` always says
 exactly what you're running.
 
+## What's new in 0.15.0
+
+**A major Terminal Workspace rebuild** (#242) — the PM spine, a Claude Design refresh, and a proper
+viewer column, plus five new capabilities. Run `npx create-pmos@latest workspace`; the version bump
+means an existing install auto-upgrades.
+
+- **A Focus queue** — the workspace surfaces what actually needs you, as a queue to work down rather
+  than a grid to scan.
+- **A phone surface** — the workspace now has a real mobile navigation model, so you can triage from
+  a phone, not only a desktop.
+- **Claude profiles** — per-session profile descriptors, so different agent setups are legible at a
+  glance.
+- **Multi-product repo-scan** — the ingest pipeline can scan across more than one product repo.
+- **A Jira handoff model** — a links model for handing an initiative off to an external tracker from
+  the workspace (opt-in; the file-mode kit still needs no network).
+
+The file-mode kit itself is unchanged and still dependency-free — all of the above lives in the
+optional Terminal Workspace GUI.
+
+## What's new in 0.14.0
+
+**The foundation of an autonomous workflow driver lands in the workspace.** Two new libraries
+(`workspace/lib/drive-plan.js` + `drive-guard.js`) give the workflow loop a head and a conscience:
+
+- **A planner that knows when to stop.** The workflow ladder never returns "nothing left to do" —
+  it always names a next honest action, so a naive `while (next)` loop never exits. The planner
+  decides `dispatch` vs `stop` on three explicit triggers: **human-gate** (the next step is a PM
+  decision — a contract or an acceptance), **no-progress** (the same next action twice running means
+  the last dispatch moved nothing — a stop, not a retry), and **budget** (a hard ceiling so an
+  unforeseen case still terminates).
+- **A guard that can't sign the PM's name.** A gate in PMOS is "a file with the right words in it,"
+  which an autonomous writer could satisfy. The guard is the driver's *only* write path and refuses
+  to write acceptances, a `PM_approved` flag (at any nesting depth, or smuggled as raw text), or a
+  disposition token — so the loop can advance work but can never self-approve past a human gate.
+
+This is the planner + guard (14 tests cover them); the return path, an independent verify pass, and
+a live board run are the next increments under the same contract. Run `npx create-pmos@latest
+workspace` to pick it up — the workspace version bump means an existing install auto-upgrades.
+
 ## What's new in 0.13.0
 
 **Six more skills now travel with the kit** — the allowlist had been shipping dangling references to

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-pmos",
-  "version": "0.13.0",
+  "version": "0.15.0",
   "description": "Scaffold the PMOS portable kit — run the PMOS product-management workflow (initiative → lane-fit spec → contract → build → three gates, with work-type lanes for features, research, maintenance, incidents, and content) entirely inside your own repo, with all state as git-versioned files. `create-pmos workspace` also installs + launches the local Terminal Workspace GUI. No database, no network, no telemetry.",
   "license": "MIT",
   "bin": {

package/payload/KIT-VERSION

@@ -1,3 +1,3 @@
-kernel-source: pmos@2374d99
-assembled: 2026-07-29
+kernel-source: pmos@7b15792
+assembled: 2026-07-30
 mode: vendor