create-pmos 0.11.0 → 0.12.0

package/README.md

@@ -333,6 +333,65 @@ 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.0
+
+**The sidebar says what is actually true.** 0.11.x told you things were *unreadable* when they were
+simply *not there* — and used the same red for both.
+
+If you pointed the workspace at an ordinary folder or a repository that isn't a PMOS repo, almost
+everything read as an error. None of it was.
+
+- **A folder that isn't a git repository** now says so, quietly. It used to say `branch unreadable`,
+  which is an alarm about a completely ordinary directory.
+- **A repository with no initiative records** reads **no initiatives yet** — a fact about the
+  repository, calmly stated. Pointing the workspace at any repo you like is a supported thing to do.
+- **A shell session** no longer reports its non-existent transcript as a failed identification. A
+  shell is a prompt, not an agent narrating itself.
+- **A row keeps its name.** Previously a plain folder rendered as a row titled `branch unreadable` —
+  a row with no name at all, unfindable in a tree of them.
+
+Red still means red: a corrupt state queue, a genuine git failure, or an engine that is installed but
+throws all still draw the alarm. The point is that they no longer share it with the normal case.
+
+Three controls also stopped being ambiguous:
+
+- **`＋ new session — run an agent here`** now names the repository and branch it will start in.
+  "Here" meant the selected tree all along; with every repository on screen at once, nothing said
+  which that was.
+- **`＋ session here`** starts a session. It used to select the tree and stop.
+- **A row with no sessions no longer expands** just because something needs your attention — that
+  count is already shown on the row, and opening an empty container to "reveal" it taught you to
+  distrust the tree.
+
+And the pane is called **repos & sessions** rather than `work`.
+
+> **One disclosure.** The Review Gate for this work was not scored before release. Its rubric makes
+> the honesty checks *runnable* precisely so they cannot be satisfied by reading the code, and they
+> were not run by an independent evaluator. Everything above was verified by the automated suites
+> (412 checks) and by hand; none of it was independently reviewed.
+
+## What's new in 0.11.1
+
+**Fixes: the ladder never actually worked.** If you installed 0.11.0 and every row in the new
+sidebar read `ladder unreadable` in red — that was us, not your repository.
+
+The engine that derives an initiative's stage, next step and blockers was **not included in any
+published package**. It lives at `scripts/workflow-state.js` in the PMOS repo, and the workspace
+looked for it two directories above itself — a path that exists in a development checkout and in no
+install. The surface 0.11.0 was released for could not run for anyone who installed it.
+
+0.11.1 bundles the engine with the app, and adds the check that would have caught this: publishing
+now **derives a ladder from the packed tarball** and fails if it cannot, rather than only confirming
+that files are present.
+
+So rows now show what 0.11.0 described: lane, derived stage, and the next step or the blocker —
+each one naming the branch it was derived from.
+
+A repository with no `planning/initiatives/` records is no longer an error; it simply has no
+initiatives, and reads calmly. Some of the wording around that is still terser than it should be
+(a folder that is not a git repository currently reports an unreadable branch rather than saying it
+is not a repository) — that is being fixed separately and is a label, not a failure.
+
 ## What's new in 0.11.0
 
 **The workspace navigates by initiative instead of by folder.** If you upgrade and the left column

package/package.json

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

package/workspace/lib/console-state.js

@@ -126,14 +126,45 @@ function radar({ stateDir, snapshotDir }) {
  * option. It is deliberately not `require`d out of the opened directory: the engine only reads
  * files and runs `git -C <root> log`, so no code from a workspace the PM merely opened is ever
  * executed. An install that does not carry the engine gets an honest error, never a blank panel.
+ *
+ * WHERE THE ENGINE ACTUALLY LIVES — the defect this list exists to close (incident
+ * kit-workflow-engine-missing). "Bundled with the workspace" was the INTENT above; packaging never
+ * implemented it. `npm-pkg/package.json` ships only bin/ payload/ workspace/, so in a published
+ * install there is no repo two levels up and `../../scripts/workflow-state.js` resolves to nothing.
+ * Every adopter row read "ladder unreadable" from 0.11.0 back to whenever this surface shipped —
+ * the ladder had never once run outside a PMOS checkout. Two locations, tried in order:
+ *
+ *   1. `../../scripts/workflow-state.js` — a repo checkout (PMOS-self, any dev clone). Preferred on
+ *      purpose: it is the very file `.github/scripts/initiative-gate.sh` executes, so a developer's
+ *      panel can never disagree with what CI is about to print on their PR.
+ *   2. `lib/engine/workflow-state.js` — the copy the publish step vendors into the bundle. This is
+ *      what an adopter runs, and the only reason the ladder derives at all outside this repo.
+ *
+ * ABSENT and BROKEN are answered differently, because they are different facts (R10). A path that
+ * does not exist means "try the next one"; a path that exists and throws is a real fault in an
+ * engine that IS installed, and reporting that as "not present" would send the PM looking for a
+ * packaging bug they do not have.
  */
+const ENGINE_PATHS = [
+  path.join(__dirname, '..', '..', 'scripts', 'workflow-state.js'),
+  path.join(__dirname, 'engine', 'workflow-state.js'),
+];
+function loadEngine() {
+  const tried = [];
+  for (const p of ENGINE_PATHS) {
+    if (!fs.existsSync(p)) { tried.push(p); continue; }
+    try { return { ok: true, engine: require(p), from: p }; }
+    catch (e) {
+      return { ok: false, error: `the workflow engine at ${p} is installed but failed to load — ${String((e && e.message) || e).slice(0, 160)}` };
+    }
+  }
+  return { ok: false, error: `the workflow engine is not present in this install — the ladder cannot be derived here (looked in: ${tried.join(', ')})` };
+}
 function workflow({ root }) {
   if (!root) return { ok: false, error: 'no workspace root resolved for the workflow surface' };
-  let engine;
-  try { engine = require(path.join(__dirname, '..', '..', 'scripts', 'workflow-state.js')); }
-  catch {
-    return { ok: false, error: 'the workflow engine (scripts/workflow-state.js) is not present in this install — the ladder cannot be derived here' };
-  }
+  const loaded = loadEngine();
+  if (!loaded.ok) return { ok: false, error: loaded.error };
+  const engine = loaded.engine;
   let ids;
   try { ids = engine.listInitiatives(root); }
   catch (e) { return { ok: false, error: 'could not list initiative records: ' + String((e && e.message) || 'error').slice(0, 120) }; }
@@ -189,4 +220,6 @@ function workflow({ root }) {
   };
 }
 
-module.exports = { metrics, radar, workflow, computeMetricsFromRuns, loadJson, loadJsonl };
+// ENGINE_PATHS/loadEngine are exported for the packaging guard in workspace/test.js: the incident
+// that made them a list was invisible to every unit test precisely because resolution was inline.
+module.exports = { metrics, radar, workflow, computeMetricsFromRuns, loadJson, loadJsonl, ENGINE_PATHS, loadEngine };

package/workspace/lib/engine/anchor-resolve.js

@@ -0,0 +1,277 @@
+#!/usr/bin/env node
+'use strict';
+/*
+ * PMOS anchor resolution — the one place a `parent_kr` string becomes a structured answer.
+ *
+ *   const A = require('./anchor-resolve');
+ *   const index = A.parseOkrIndex(root);          // what the OKR documents actually declare
+ *   const r     = A.resolveAnchor(raw, index);    // { kind, objective, kr, status, ... }
+ *   A.canonical(r)                                // the one normative written form
+ *
+ * WHY THIS EXISTS. Before this module, `parent_kr` was a string that nothing dereferenced. The
+ * ladder's R1 passed any non-empty value that did not contain `health:` as `done` without ever
+ * opening the OKR documents — so `parent_kr: banana` passed, and so did an anchor naming a KR that
+ * existed in no file (`q3-2026:integrity:kr-a` and `:kr-b` did exactly that for two days). The
+ * workspace's OKR surface, meanwhile, never read `parent_kr` at all. One field, several readers,
+ * none of them agreeing what it meant. See
+ * planning/explainers/okr-anchor-resolution-surface-explainer.md.
+ *
+ * THREE RULES, all load-bearing (planning/prd/anchor-normalization-spec.md R-2/R-3/R-4):
+ *
+ *   1. PERMANENTLY BACKWARD-COMPATIBLE (R-2). Every syntax present in the corpus at authoring time
+ *      is accepted, and keeps being accepted — not behind a migration window. The kit ships to
+ *      adopters as `create-pmos` (D55), so records written in the legacy forms exist in repos no
+ *      rewrite here can reach. ACCEPTED_FORMS below is that enumeration, and it is a promise.
+ *
+ *   2. HEALTH IS A FORM TEST, NEVER A SUBSTRING SEARCH (R-3). The corpus contains
+ *      `okrs-q3-2026 → O1.KR1    # or health:<id> from planning/okrs/health-budgets.md` — an OKR
+ *      anchor whose *commentary* mentions health. A substring search classifies it as a health
+ *      anchor and then rejects it as an undeclared budget: recognised, then refused, for a reason
+ *      that is not the reader's fault. Classification therefore tests the START of the value.
+ *
+ *   3. THE OBJECTIVE AND KR PATTERNS WIDEN TOGETHER (R-4). Widening the objective pattern alone
+ *      would let a previously-unmatched KR attach to the *previous matched* objective rather than
+ *      stay unmatched — a silent mis-filing, which is worse than the omission it replaces.
+ *
+ * HONESTY BY CONSTRUCTION. `status` is one of `resolved` · `unresolvable` · `empty` · `unknown`.
+ * `unknown` means the OKR documents could not be read and never collapses into either a pass or a
+ * failure — a resolver that cannot see its inputs says so rather than guessing. Nothing in this
+ * module blocks anything: per the spec's assumption A1 the gates keep accepting any non-empty
+ * anchor, and the RED belongs to the surface. This module reports; callers decide.
+ *
+ * Zero dependencies, stock Node. Runs in CI, in the ladder, and inside the workspace server.
+ */
+
+const fs = require('fs');
+const path = require('path');
+
+/*
+ * The census, from the explainer, as executable documentation. Each entry is a real form found in
+ * planning/initiatives/ at authoring time (2026-07-28). Adding a form here without a matching
+ * pattern below, or vice versa, is the drift this list exists to make visible — the test suite
+ * asserts every example resolves.
+ */
+const ACCEPTED_FORMS = [
+  { example: 'health:tech',                    note: 'D59 registry form, bare' },
+  { example: 'health:tech (D59 — commentary)', note: 'registry form with trailing commentary' },
+  { example: 'q3-2026:o1:kr1',                 note: 'CANONICAL — colon triple' },
+  { example: 'q3-2026:integrity:kr-a',         note: 'canonical, non-numeric objective + KR ids' },
+  { example: 'Q3-2026:O1:KR2',                 note: 'canonical, upper-case variant' },
+  { example: 'okrs-q3-2026 → O1.KR1',          note: 'legacy arrow form, filename-prefixed' },
+  { example: 'okrs-q3-2026 → O1',              note: 'legacy arrow, objective only (no KR)' },
+  { example: 'q3-2026 → O1.KR2',               note: 'legacy arrow, period-prefixed' },
+  { example: 'O1.KR3',                         note: 'legacy bare objective.KR' },
+  { example: '**O1**',                         note: 'legacy bare objective, markdown-bolded' },
+  { example: "okrs-q3-2026 → O2.KR2 / B4 (Cohen's kappa)", note: 'trailing commentary after a slash' },
+  { example: 'okrs-q3-2026 → O1.KR1    # or health:<id> from planning/okrs/health-budgets.md',
+    note: 'R-3 trap: OKR anchor whose COMMENTARY mentions health — must classify as okr' },
+];
+
+/*
+ * Objective and KR tokens are deliberately NOT `O\w+` / `KR\w+`. The OKR document's own H1 is
+ * `# OKRs — Q3 2026`, and a loose objective pattern matches `OKRs` there, inventing an objective
+ * called `okrs` that every subsequent KR would then attach to. The shape is therefore pinned:
+ * an objective is `O` + digits, or `O-` + a word; a KR is `KR` + digits, or `KR-` + a word.
+ */
+const OBJ_TOKEN = '(O\\d+|O-[A-Za-z][A-Za-z0-9-]*)';
+const KR_TOKEN = '(KR\\d+|KR-[A-Za-z][A-Za-z0-9-]*)';
+const PERIOD = '((?:q|Q)[1-4]-\\d{4})';
+
+const RE_OBJ_HEADING = new RegExp('^#{1,3}\\s+' + OBJ_TOKEN + '\\s*(?:[—–:-]\\s*(.*))?$');
+const RE_KR_BULLET = new RegExp('^\\s*[-*]\\s*\\*\\*\\s*' + KR_TOKEN + '\\s*[—–:-]?\\s*(.+?)\\*\\*');
+
+// Anchor forms. Order matters only in that the colon forms are tried before the looser ones.
+const RE_HEALTH = /^health:([a-z0-9_-]+)/i;                       // START-anchored — rule 2
+const RE_COLON_KR = new RegExp('^(?:okrs-)?' + PERIOD + ':([a-z0-9][a-z0-9-]*):(kr-?[a-z0-9-]+)$', 'i');
+const RE_COLON_OBJ = new RegExp('^(?:okrs-)?' + PERIOD + ':([a-z0-9][a-z0-9-]*)$', 'i');
+const RE_ARROW = new RegExp('^(?:okrs-)?' + PERIOD + '\\s*(?:→|->)\\s*' + OBJ_TOKEN + '(?:\\.' + KR_TOKEN + ')?$', 'i');
+const RE_BARE = new RegExp('^' + OBJ_TOKEN + '(?:\\.' + KR_TOKEN + ')?$', 'i');
+
+/** Strip markdown emphasis and trailing commentary. `(`, `#` and `/` never appear inside an id. */
+function stripCommentary(raw) {
+  let s = String(raw == null ? '' : raw).replace(/\*\*/g, '').trim();
+  const cut = s.search(/[(#/]/);
+  if (cut >= 0) s = s.slice(0, cut);
+  return s.trim();
+}
+
+/** `O-INTEGRITY` → `integrity`; `O1` → `o1`. The anchors write `integrity`, the heading writes
+ *  `O-INTEGRITY`; the explainer flagged that a widened parser must pick one. This picks: the id is
+ *  the heading token minus a leading `O-`, lower-cased. */
+function objectiveId(token) {
+  const t = String(token || '').trim();
+  const m = /^O-(.+)$/i.exec(t);
+  return (m ? m[1] : t).toLowerCase();
+}
+
+/** `KR1` → `kr1`; `KR-C` → `kr-c`. Case only. */
+function krId(token) {
+  return String(token || '').trim().toLowerCase();
+}
+
+function listOkrFiles(root) {
+  const out = [];
+  const seen = new Set();
+  const walk = (dir, depth) => {
+    if (depth > 4) return;
+    let entries;
+    try { entries = fs.readdirSync(dir, { withFileTypes: true }); } catch { return; }
+    for (const e of entries) {
+      if (e.name.startsWith('.') || e.name === 'node_modules') continue;
+      const full = path.join(dir, e.name);
+      if (e.isDirectory()) {
+        if (e.name === 'okrs') {
+          let files;
+          try { files = fs.readdirSync(full); } catch { continue; }
+          for (const f of files) {
+            if (!f.endsWith('.md')) continue;
+            const p = path.join(full, f);
+            if (!seen.has(p)) { seen.add(p); out.push(p); }
+          }
+        } else walk(full, depth + 1);
+      }
+    }
+  };
+  walk(root, 0);
+  return out.sort();
+}
+
+/**
+ * Read every OKR document under `root` and return what they declare.
+ * → { ok, objectives: [{id, token, name, krs:[{id, token, name}], file}], files, error }
+ * `ok:false` is a genuine read failure and must render as an error, never as "no objectives".
+ */
+function parseOkrIndex(root) {
+  const files = listOkrFiles(root);
+  if (!files.length) {
+    return { ok: false, objectives: [], files: [], error: 'no OKR documents found under ' + root };
+  }
+  const objectives = [];
+  const byId = new Map();
+  let period = null;
+  for (const file of files) {
+    let text;
+    try { text = fs.readFileSync(file, 'utf8'); }
+    catch (e) {
+      return { ok: false, objectives: [], files, error: `could not read ${file}: ${String((e && e.message) || e).slice(0, 120)}` };
+    }
+    let cur = null;
+    for (const line of text.split('\n')) {
+      if (!period) {
+        const p = /^\s*[-*]?\s*period\s*:\s*(\d{4})-(Q[1-4])\s*$/i.exec(line);
+        if (p) period = `${p[2].toLowerCase()}-${p[1]}`;
+      }
+      const o = RE_OBJ_HEADING.exec(line);
+      if (o) {
+        const id = objectiveId(o[1]);
+        cur = byId.get(id);
+        if (!cur) {
+          cur = { id, token: o[1], name: (o[2] || '').replace(/\*\*/g, '').trim(), krs: [], file: path.relative(root, file) };
+          byId.set(id, cur);
+          objectives.push(cur);
+        }
+        continue;
+      }
+      const k = RE_KR_BULLET.exec(line);
+      // A KR with no open objective stays UNATTACHED (rule 3) — never inherited from a previous one.
+      if (k && cur && !cur.krs.some((x) => x.id === krId(k[1]))) {
+        cur.krs.push({ id: krId(k[1]), token: k[1], name: (k[2] || '').trim() });
+      }
+    }
+  }
+  return { ok: true, objectives, files: files.map((f) => path.relative(root, f)), period: period || null, error: null };
+}
+
+function readBudgets(root) {
+  const p = path.join(root, 'planning', 'okrs', 'health-budgets.md');
+  try { return { ok: true, text: fs.readFileSync(p, 'utf8'), path: path.relative(root, p) }; }
+  catch { return { ok: false, text: '', path: path.relative(root, p) }; }
+}
+
+/**
+ * Resolve one raw `parent_kr` value.
+ * → { raw, kind, status, objective, kr, budget, period, form, reason }
+ *   kind   : 'health' | 'okr' | 'empty'
+ *   status : 'resolved' | 'unresolvable' | 'empty' | 'unknown'
+ * `index` comes from parseOkrIndex; `budgets` from readBudgets (optional — omit to skip the
+ * registry check, which callers that only need the FORM can do).
+ */
+function resolveAnchor(raw, index, budgets) {
+  const original = String(raw == null ? '' : raw).trim();
+  const base = { raw: original, kind: 'empty', status: 'empty', objective: null, kr: null, budget: null, period: null, form: null, reason: null };
+  if (!original) return Object.assign(base, { reason: 'parent_kr is empty — unanchored work is rejected (D59)' });
+
+  // Rule 2: the FORM decides, not a substring. Commentary is stripped only for the OKR branch,
+  // because a health anchor's id must sit at the very start of the raw value.
+  const h = RE_HEALTH.exec(original);
+  if (h) {
+    const id = h[1].toLowerCase();
+    const out = Object.assign({}, base, { kind: 'health', budget: id, form: 'health:<id>' });
+    if (!budgets) return Object.assign(out, { status: 'unknown', reason: 'health budget registry not supplied to the resolver' });
+    if (!budgets.ok) return Object.assign(out, { status: 'unknown', reason: `health-budget registry unreadable at ${budgets.path}` });
+    // Same case handling as the classifier (R-3): recognised case-insensitively, looked up the same way.
+    const declared = new RegExp('health:' + id.replace(/[.*+?^${}()|[\]\\]/g, '\\$&') + '\\b', 'i').test(budgets.text);
+    return declared
+      ? Object.assign(out, { status: 'resolved', reason: `declared in ${budgets.path}` })
+      : Object.assign(out, { status: 'unresolvable', reason: `health:${id} is not a declared budget in ${budgets.path}` });
+  }
+
+  const s = stripCommentary(original);
+  if (!s) {
+    return Object.assign(base, { kind: 'okr', status: 'unresolvable', reason: 'no anchor left after commentary was stripped' });
+  }
+
+  let period = null, objTok = null, krTok = null, form = null;
+  let m;
+  if ((m = RE_COLON_KR.exec(s))) { period = m[1].toLowerCase(); objTok = m[2]; krTok = m[3]; form = 'q3-2026:<objective>:<kr>'; }
+  else if ((m = RE_COLON_OBJ.exec(s))) { period = m[1].toLowerCase(); objTok = m[2]; form = 'q3-2026:<objective>'; }
+  else if ((m = RE_ARROW.exec(s))) { period = m[1].toLowerCase(); objTok = m[2]; krTok = m[3] || null; form = 'legacy arrow'; }
+  else if ((m = RE_BARE.exec(s))) { objTok = m[1]; krTok = m[2] || null; form = 'legacy bare'; }
+  else {
+    return Object.assign(base, { kind: 'okr', status: 'unresolvable', form: 'unrecognised', reason: `'${s}' matches no accepted anchor form` });
+  }
+
+  const out = Object.assign({}, base, {
+    kind: 'okr', form, period,
+    objective: objectiveId(objTok),
+    kr: krTok ? krId(krTok) : null,
+  });
+
+  if (!index) return Object.assign(out, { status: 'unknown', reason: 'OKR index not supplied to the resolver' });
+  if (!index.ok) return Object.assign(out, { status: 'unknown', reason: index.error || 'OKR documents unreadable' });
+
+  const obj = index.objectives.find((o) => o.id === out.objective);
+  if (!obj) {
+    return Object.assign(out, { status: 'unresolvable', reason: `objective '${out.objective}' is not declared in ${index.files.join(', ')}` });
+  }
+  if (!out.kr) {
+    // Assumption A2: objective-only anchoring is a legitimate resolvable kind, not debt.
+    return Object.assign(out, { status: 'resolved', reason: `objective '${obj.id}' — no KR written (objective-level anchor)` });
+  }
+  const kr = obj.krs.find((k) => k.id === out.kr);
+  if (!kr) {
+    return Object.assign(out, { status: 'unresolvable', reason: `objective '${obj.id}' declares no KR '${out.kr}' (has: ${obj.krs.map((k) => k.id).join(', ') || 'none'})` });
+  }
+  return Object.assign(out, { status: 'resolved', reason: `${obj.id}/${kr.id} — ${kr.name}`.slice(0, 160) });
+}
+
+/**
+ * The one normative written form (R-1, as amended 2026-07-28 by PM decision).
+ * Returns null when the input does not resolve to something writable — callers must not invent one.
+ */
+function canonical(resolved, fallbackPeriod) {
+  if (!resolved) return null;
+  if (resolved.kind === 'health') return resolved.budget ? `health:${resolved.budget}` : null;
+  if (resolved.kind !== 'okr' || !resolved.objective) return null;
+  const period = resolved.period || fallbackPeriod || null;
+  if (!period) return null;
+  return resolved.kr ? `${period}:${resolved.objective}:${resolved.kr}` : `${period}:${resolved.objective}`;
+}
+
+module.exports = {
+  parseOkrIndex, readBudgets, resolveAnchor, canonical,
+  objectiveId, krId, stripCommentary, listOkrFiles,
+  ACCEPTED_FORMS,
+  // exported for the tests that assert the widening happened together (R-4)
+  RE_OBJ_HEADING, RE_KR_BULLET,
+};