create-pmos 0.12.0 → 0.12.1

package/README.md

@@ -333,6 +333,14 @@ 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.12.1
+
+A small kernel refresh: the **`prototype` skill's grilling step** (leg A of the D60 prototype loop)
+now dispatches an **independent griller** as a distinct, fresh-context critic — the specimens are
+sharpened by a genuine second party, not the same agent reviewing its own work. Update an existing
+kit with `npx create-pmos@latest --update`. (The Terminal Workspace app is unchanged in this
+release, so an already-current `pmos` install won't reinstall.)
+
 ## What's new in 0.12.0
 
 **The sidebar says what is actually true.** 0.11.x told you things were *unreadable* when they were

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-pmos",
-  "version": "0.12.0",
+  "version": "0.12.1",
   "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@120ca72
+kernel-source: pmos@b4d45ee
 assembled: 2026-07-29
 mode: vendor

package/payload/skills/prototype.skill

@@ -109,12 +109,22 @@ system, a convention set, or a prototype to validate an idea.
    applies in-loop; claim-sourcing waits for the content lane at production). The non-visual analogue
    is the same rule: real inputs and real outputs, because fake ones hide exactly the friction the
    specimen exists to surface. Respect the accessibility floors even at low fidelity.
-6. **Grill — dialogue, never a score.** A craft-grade critic (fresh context, default-to-refute
-   stance, the class's craft loaded) interrogates each specimen: *why this structure? what job does
-   the focal element serve? what would the best practitioner in this class say is wrong? what was NOT
-   tried?* One question at a time, a recommended answer with each, no action until shared
-   understanding is confirmed. Sharpen the specimens from it. **Produces no score, no verdict, no
-   threshold, no `evals` row** — re-introducing scoring here under any name is a D60 violation.
+6. **Grill — dialogue, never a score. Dispatch
+   [`prototype-grill`](/build-skills/prototype-grill.skill).** A craft-grade critic (fresh context,
+   default-to-refute stance, the class's craft loaded) interrogates each specimen: *why this
+   structure? what job does the focal element serve? what would the best practitioner in this class
+   say is wrong? what was NOT tried?* It writes `prototype/<id>/grilling.md`. Sharpen the specimens
+   from it. **Produces no score, no verdict, no threshold, no `evals` row** — re-introducing scoring
+   here under any name is a D60 violation.
+
+   **The critic must be a DIFFERENT agent from the one that produced the specimens.** This was prose
+   here from the day the lane existed, with nothing to dispatch and nothing to check it — so the
+   cheapest path was to grill your own work, and a dialogue with one party is a monologue with extra
+   steps. It stopped being hypothetical on 2026-07-29, when
+   [`r2-free-zone-baseline.md`](/prototype/pmos-autonomous-drive/r2-free-zone-baseline.md) grilled
+   its own specimens and flagged itself for it. If no second agent is available, **report that as a
+   blocker** and let the PM knowingly accept a self-grilling — a recorded compromise, never a
+   fabricated dialogue.
 7. **PM disposition** (the only gate on leg A, and it is the PM's):
    - **promote** → open a **new feature-lane initiative**; its PRD and rubric are **derived from the
      validated specimen** (what was seen and chosen becomes the spec's substance). Leg B, where the

package/payload/skills-native/prototype/SKILL.md

@@ -111,12 +111,22 @@ system, a convention set, or a prototype to validate an idea.
    applies in-loop; claim-sourcing waits for the content lane at production). The non-visual analogue
    is the same rule: real inputs and real outputs, because fake ones hide exactly the friction the
    specimen exists to surface. Respect the accessibility floors even at low fidelity.
-6. **Grill — dialogue, never a score.** A craft-grade critic (fresh context, default-to-refute
-   stance, the class's craft loaded) interrogates each specimen: *why this structure? what job does
-   the focal element serve? what would the best practitioner in this class say is wrong? what was NOT
-   tried?* One question at a time, a recommended answer with each, no action until shared
-   understanding is confirmed. Sharpen the specimens from it. **Produces no score, no verdict, no
-   threshold, no `evals` row** — re-introducing scoring here under any name is a D60 violation.
+6. **Grill — dialogue, never a score. Dispatch
+   [`prototype-grill`](/build-skills/prototype-grill.skill).** A craft-grade critic (fresh context,
+   default-to-refute stance, the class's craft loaded) interrogates each specimen: *why this
+   structure? what job does the focal element serve? what would the best practitioner in this class
+   say is wrong? what was NOT tried?* It writes `prototype/<id>/grilling.md`. Sharpen the specimens
+   from it. **Produces no score, no verdict, no threshold, no `evals` row** — re-introducing scoring
+   here under any name is a D60 violation.
+
+   **The critic must be a DIFFERENT agent from the one that produced the specimens.** This was prose
+   here from the day the lane existed, with nothing to dispatch and nothing to check it — so the
+   cheapest path was to grill your own work, and a dialogue with one party is a monologue with extra
+   steps. It stopped being hypothetical on 2026-07-29, when
+   [`r2-free-zone-baseline.md`](/prototype/pmos-autonomous-drive/r2-free-zone-baseline.md) grilled
+   its own specimens and flagged itself for it. If no second agent is available, **report that as a
+   blocker** and let the PM knowingly accept a self-grilling — a recorded compromise, never a
+   fabricated dialogue.
 7. **PM disposition** (the only gate on leg A, and it is the PM's):
    - **promote** → open a **new feature-lane initiative**; its PRD and rubric are **derived from the
      validated specimen** (what was seen and chosen becomes the spec's substance). Leg B, where the