create-pmos 0.20.1 → 0.22.0

package/README.md

@@ -333,6 +333,38 @@ 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.21.0
+
+**The workspace terminal's lines are no longer double-spaced.** Run
+`npx create-pmos@latest workspace`; the version bump means an existing install auto-upgrades.
+
+- **A terminal row is 20px instead of 26px.** Agent output in the terminal panel was rendering with
+  13.5px of empty space around a 12.5px character — and because agent CLIs print blank lines
+  between blocks, and those were 26px too, the whole transcript read as nearly double-spaced. It
+  now matches the spacing the workspace was designed with.
+- **Your agent gets more terminal.** This was never only cosmetic: the workspace divides the
+  panel's height by the row height to decide how many lines to tell the shell it has. The same
+  panel that reported 21 lines now reports 28, so full-screen agent interfaces have a third more
+  room to draw into.
+- *(If you are curious: the number `1.65` appeared twice in one file and meant two different things.
+  As a CSS rule it multiplies the font size — 12.5 × 1.65 = 20.6px, which is the design. Handed to
+  the terminal engine, the same number multiplies the font's own already-leaded box, which is 16px
+  — giving 26px. A comment in the file asserted the two agreed, which is how it survived.)*
+
+## What's new in 0.20.1
+
+**An HTML document opens rendered, not as its own source.** Opening an `.html` file in the
+workspace's document viewer showed you the markup instead of the page.
+
+## What's new in 0.20.0
+
+**External links name a real record instead of inventing one.** The Jira/Confluence/Docs link
+controls used to fabricate every identifier they recorded. A `＋` button now opens a form and
+records nothing until you supply the reference or a session resolves it — and `resolved` cannot be
+asserted, only evidenced: a row claiming it without naming the profile that resolved it is refused.
+PMOS still holds no credential and makes no outbound request; the lookup runs in an agent session
+carrying your own MCP.
+
 ## What's new in 0.19.0
 
 **A long document scrolls its own panel, and starting a session asks what is already running.** Run

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-pmos",
-  "version": "0.20.1",
+  "version": "0.22.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@1d54a27
+kernel-source: pmos@38fc236
 assembled: 2026-07-31
 mode: vendor

package/workspace/package-lock.json

@@ -1,12 +1,12 @@
 {
   "name": "pmos-workspace",
-  "version": "0.20.0",
+  "version": "0.22.0",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "pmos-workspace",
-      "version": "0.20.0",
+      "version": "0.22.0",
       "license": "MIT",
       "dependencies": {
         "@xterm/addon-fit": "^0.11.0",

package/workspace/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pmos-workspace",
-  "version": "0.20.1",
+  "version": "0.22.0",
   "private": true,
   "description": "PMOS Terminal Workspace \u2014 local companion hosting real PTYs beside the library and gates (D62)",
   "license": "MIT",

package/workspace/public/pm/data.js

@@ -766,6 +766,11 @@ export async function loadRepos() {
       name,
       kind: prod && prod.kind === 'github' ? 'github' : 'local',
       count: prod && prod.count !== null ? prod.count : null,
+      // The board's OTHER population, published beside the count rather than folded into it — see
+      // `prod.unrecorded` in loadBoard and the sub-line in panel-repos.js#toTuple. A row that
+      // reports only the spine's number is accurate about itself and silent about the rest of the
+      // panel; the two together are what make panel 1 and panel 2 unable to disagree.
+      unrecorded: prod && typeof prod.unrecorded === 'number' ? prod.unrecorded : 0,
     };
   });
 }
@@ -824,12 +829,17 @@ export async function addRepo({ source, kind }) {
     publishBoards();
     const prod = products.get(p.name);
     return {
-      repo: { name: p.name, kind: 'local', count: prod.count },
+      repo: { name: p.name, kind: 'local', count: prod.count, unrecorded: prod.unrecorded || 0 },
       log: [
         { t: 'registered ' + w.root, c: 'var(--muted-foreground)' },
         prod.error
           ? { t: 'the initiative spine could not be read — ' + prod.error, c: 'var(--destructive)' }
-          : { t: 'read planning/ … ' + (prod.count || 0) + ' initiative record(s)', c: 'var(--muted-foreground)' },
+          // The log says WHERE the records were read from, because "0 initiative record(s)" against
+          // a repo that has them is the defect this initiative exists to close — a line naming
+          // `planning/` on a kit repo that keeps them in `pmos/state/` would have described a
+          // directory the server never opened.
+          : { t: 'read ' + (prod.count === 1 ? '1 initiative record' : (prod.count || 0) + ' initiative records')
+              + (prod.unrecorded ? ' · ' + prod.unrecorded + ' artifact group(s) with no record' : ''), c: 'var(--muted-foreground)' },
         { t: 'done — ' + p.name + ' added', c: 'var(--success)' },
       ],
     };

package/workspace/public/pm/panel-repos.js

@@ -57,7 +57,16 @@ function toTuple(r) {
    * read (a folder with no `planning/`, a tree that errored) rendered "local · " — a sub-line that
    * trails off mid-sentence and reads as a bug in the row rather than as "PMOS has not counted
    * this". The dash is the design's own vocabulary for a value that is not there. */
-  const sub = r.sub || (n === null ? '—' : n + (n === 1 ? ' initiative' : ' initiatives'));
+  /* …AND THE ROW MAY NOT STATE A NUMBER THE BOARD CONTRADICTS. The headline count is the SPINE's —
+   * that ruling stands, it is what keeps `176 initiatives` off a repository holding 138 records and
+   * 38 orphans. What it did not cover is the other side of the same coin: with no records found and
+   * artifacts grouped anyway, the row printed a confident `0 initiatives` over a board the PM could
+   * see was not empty, and on this repo it silently dropped 20 groups from a headline of 177. The
+   * second clause names that population in the board's own vocabulary ("artifacts with no
+   * initiative record"), counted separately and never added in. Absent when there are none. */
+  const un = typeof r.unrecorded === 'number' && r.unrecorded > 0 ? r.unrecorded : 0;
+  const sub = r.sub || (n === null ? '—'
+    : n + (n === 1 ? ' initiative' : ' initiatives') + (un ? ' · ' + un + ' unrecorded' : ''));
   const kind = (r.kind || r.source) === 'local' ? 'local' : (r.kind || r.source) === 'github' ? 'github'
     : (r.remote || r.origin) ? 'github' : 'local';
   return [String(id), sub, kind];

package/workspace/public/pm/tab-term.js

@@ -37,7 +37,9 @@
  *      so the first real metrics arrive after the woff2 lands).
  *
  * The xterm palette is the DESIGN's: `--term-bg` for the background — dark in both themes, D41 —
- * and IBM Plex Mono at the design's 12.5px / 1.65. xterm's colour parser does not understand
+ * and IBM Plex Mono at the design's 12.5px. Its LINE HEIGHT is not the design's 1.65: that number
+ * is a CSS line-height and xterm's option of the same name is not one, so it is converted rather
+ * than copied — see TERM_LINE_HEIGHT. xterm's colour parser does not understand
  * `oklch()`, so the token is resolved to a concrete sRGB value at runtime (canvas round-trip, with
  * the pre-computed hex as the fallback) rather than handed to xterm as written.
  */
@@ -446,6 +448,31 @@ if (typeof window !== 'undefined') {
 
 /* ── fixture pane ──────────────────────────────────────────────────────────────────────────── */
 
+/* ── one terminal row ────────────────────────────────────────────────────────────────────────
+ * TWO pane kinds, TWO different meanings for the same number, and that is the whole of the defect
+ * this constant exists to keep fixed.
+ *
+ *   FAUX SHELL (fixture) — SCROLL_STYLE below. `line-height:1.65` is CSS: a unitless multiplier on
+ *   the FONT SIZE. One line box is 12.5 × 1.65 = 20.625px. That is the PM's prototype, ported
+ *   character for character (planning/design/four-panel/prototype-original.html:929), and it is
+ *   also the value design-parity.js compares. It was never wrong; leave it alone.
+ *
+ *   LIVE TERMINAL (real) — the xterm options. `lineHeight` there is xterm's OWN option, and its
+ *   renderer computes `cell.height = floor(char.height × lineHeight)` where `char.height` is the
+ *   font's MEASURED glyph box — 16px for IBM Plex Mono at 12.5px, already carrying the leading the
+ *   typeface ships with. So xterm's number adds leading ON TOP OF leading where CSS's replaces it.
+ *
+ * Passing the design's CSS 1.65 straight into xterm therefore rendered floor(1.65 × 16) = 26px
+ * rows against a 20.625px reference — 26% looser than the design, 13.5px of empty space around a
+ * 12.5px glyph — and the header comment at the top of this file recorded the belief that the two
+ * agreed. Measured in Chromium against the served woff2: 1.0 → 16px, 1.2 → 19px, 1.3 → 20px,
+ * 1.65 → 26px. 1.3 is the ratio that reproduces the design's line box through xterm's formula.
+ *
+ * It is not paint-only: addon-fit divides the pane height by the cell height to pick `rows`, and
+ * syncSize() sends that to the PTY. At 26px a 565px pane told the shell it had 21 rows; at 20px it
+ * tells it 28. The row height IS how much terminal the agent CLI gets to draw into.
+ */
+const TERM_LINE_HEIGHT = 1.3;
 const SCROLL_STYLE = 'flex:1;min-height:0;overflow-y:auto;padding:14px 16px;font-family:var(--mono);font-size:12.5px;line-height:1.65;color:#c4ccce';
 const LINE_STYLE = (c) => 'color:' + c + ';white-space:pre-wrap;overflow-wrap:anywhere';
 const PROMPT_ROW_STYLE = 'display:flex;gap:8px;align-items:baseline';
@@ -542,7 +569,10 @@ function buildReal(tab) {
   const term = new Terminal({
     fontFamily: '"IBM Plex Mono", ui-monospace, SFMono-Regular, Menlo, Consolas, monospace',
     fontSize: 12.5,
-    lineHeight: 1.65,
+    // NOT the design's 1.65 — and that is the whole point. See TERM_LINE_HEIGHT above: xterm's
+    // `lineHeight` multiplies the font's MEASURED box, where the design's CSS number multiplies the
+    // font size. Handing the CSS number to xterm is what made a row 26px instead of 20.6px.
+    lineHeight: TERM_LINE_HEIGHT,
     theme: xtheme(),
     cursorBlink: true,
     scrollback: 5000,

package/workspace/server.js

@@ -495,11 +495,97 @@ function findDirsNamed(root, name, maxDepth) {
   return found;
 }
 function planningRoots(root) { return findDirsNamed(root, 'planning', BUNDLE_MAX_DEPTH); }
-// A repo with a planning/ bundle (at any shallow depth) or a DECISIONS.md gets the initiative lens
-// + curated knowledge; anything else is a plain document tree. Detection is nested-aware so a repo
-// that vendors a PMOS bundle under a sub-folder still shows its initiatives (the reported defect).
+
+/*
+ * ── WHERE A REPOSITORY KEEPS ITS INITIATIVE RECORDS ──────────────────────────────────────────
+ *
+ * THE ONE ANSWER. `surfaceSpine` and `surfaceOkr` both used `findDirsNamed(root,'initiatives',2)`
+ * directly, and that search reaches `planning/initiatives/` at the repo root and nothing deeper —
+ * one level above where the scaffolder THIS PROJECT PUBLISHES puts records:
+ *
+ *     planning/initiatives/            depth 2   pmos-self                       … found before
+ *     pmos/planning/initiatives/       depth 3   a bundle vendored under pmos/   … MISSED
+ *     pmos/state/initiatives/          depth 3   every create-pmos kit           … MISSED
+ *
+ * So a kit adopter's repository reported `ok:true, empty:true` — a SUCCESSFUL read of nothing —
+ * and panel 1 printed a confident `0 initiatives` over a repo full of records. `planningRoots`
+ * finds `pmos/planning` (that name IS at depth 2), so the library lens saw the same repo's
+ * documents while the spine saw no records at all: two panels, one repository, contradictory.
+ *
+ * The fact was already in this process twice. `stateDirFor` resolves — and will create —
+ * `pmos/state/`, and `scripts/workflow-state.js#layout`, the engine every ladder derives through,
+ * branches on `pmos/state/initiatives` by name. Only the READ path had never been told.
+ *
+ * DERIVED FROM BUNDLE ROOTS, NOT FROM A DEEPER WALK. Raising BUNDLE_MAX_DEPTH would have found
+ * these directories and also widened `prototype`, `okf`, `skills` and `build-skills` discovery,
+ * for which this change has no finding. Instead each bundle root — the repo root, plus the parent
+ * of every discovered `planning/` and `state/` directory — is asked for the two layouts PMOS
+ * ships. That is a fixed pair of existence checks per bundle root over walks already performed,
+ * and it cannot start proposing records out of a directory nobody vendored.
+ */
+function isDirSafe(p) { try { return fs.statSync(p).isDirectory(); } catch { return false; } }
+
+function bundleRoots(root) {
+  const out = [root];
+  const seen = new Set([path.resolve(root)]);
+  const add = (d) => { const r = path.resolve(d); if (!seen.has(r)) { seen.add(r); out.push(d); } };
+  for (const p of planningRoots(root)) add(path.dirname(p));
+  for (const d of findDirsNamed(root, 'state', BUNDLE_MAX_DEPTH)) add(path.dirname(d));
+  return out;
+}
+
+/** Every directory this repository keeps initiative RECORDS in. Existence-checked, de-duplicated. */
+function initiativeDirs(root) {
+  const out = [];
+  const seen = new Set();
+  const add = (d) => {
+    const r = path.resolve(d);
+    if (seen.has(r) || !isDirSafe(d)) return;
+    seen.add(r); out.push(d);
+  };
+  // The original search first, so no layout that worked before can stop working.
+  for (const d of findDirsNamed(root, 'initiatives', BUNDLE_MAX_DEPTH)) add(d);
+  for (const b of bundleRoots(root)) {
+    add(path.join(b, 'planning', 'initiatives'));       // pmos-self, at the root or in a bundle
+    add(path.join(b, 'state', 'initiatives'));          // the create-pmos kit (kit/build-kit.sh)
+  }
+  return out;
+}
+
+/*
+ * The health-budget registry, read from the bundle root that HAS one.
+ *
+ * `anchors.readBudgets(root)` is a fixed `<root>/planning/okrs/health-budgets.md`. A kit vendors it
+ * to `pmos/planning/okrs/health-budgets.md` (build-kit.sh writes it on every fresh vendor), so in
+ * a kit repo it was never read — and every `parent_kr: health:<id>` resolved against an empty
+ * registry into `unanchored`, with a reason that blamed the record. Finding the records without
+ * this would have replaced an invisible initiative with a misfiled one.
+ *
+ * A repo with no registry ANYWHERE still gets the root-relative `{ok:false}` — absence is reported,
+ * never faked, and `budgets_readable` stays false so the surface can say so.
+ */
+function budgetsFor(A, root) {
+  const first = A.readBudgets(root);
+  if (first && first.ok) return first;
+  for (const b of bundleRoots(root)) {
+    if (path.resolve(b) === path.resolve(root)) continue;
+    const r = A.readBudgets(b);
+    if (r && r.ok) return { ...r, path: path.relative(root, path.join(b, 'planning', 'okrs', 'health-budgets.md')) };
+    // The engine's kit path for the same registry (workflow-state.js#layout).
+    const kit = path.join(b, 'state', 'health-budgets.md');
+    try { return { ok: true, text: fs.readFileSync(kit, 'utf8'), path: path.relative(root, kit) }; }
+    catch { /* not here either — keep looking, then fall back to the root's own answer */ }
+  }
+  return first;
+}
+
+// A repo with a planning/ bundle (at any shallow depth), initiative records in a layout PMOS ships,
+// or a DECISIONS.md gets the initiative lens + curated knowledge; anything else is a plain document
+// tree. Detection is nested-aware so a repo that vendors a PMOS bundle under a sub-folder still
+// shows its initiatives (the reported defect) — including a kit whose records are its whole bundle.
 function wsShape(root) {
-  return planningRoots(root).length || fs.existsSync(path.join(root, 'DECISIONS.md')) ? 'pmos' : 'plain';
+  return planningRoots(root).length || initiativeDirs(root).length
+    || fs.existsSync(path.join(root, 'DECISIONS.md')) ? 'pmos' : 'plain';
 }
 
 // ── Library: the file tree the sidebar browses. ───────────────────────────────────────
@@ -739,12 +825,37 @@ function walkMd(dir, acc) {
   }
   return acc;
 }
+/*
+ * Initiative RECORDS that live outside every planning root — `pmos/state/initiatives/` in a
+ * create-pmos kit. `walkMd` over the planning roots cannot reach them, so in a kit repo the one
+ * document that carries the lane and the anchor was absent from its own initiative's artifact list
+ * even once the spine could see it. They are read through the SAME `docMeta` as every other
+ * document (ROLE_BY_DIR maps an `initiatives/` parent to role `record`, wherever it sits), so the
+ * join, the role and the id come from one implementation rather than a second opinion.
+ */
+function looseRecordMetas(root, proots) {
+  const under = (d) => proots.some((p) => insideRoot(path.resolve(p), path.resolve(d)));
+  const out = [];
+  for (const dir of initiativeDirs(root)) {
+    if (under(dir)) continue;                  // already covered by the planning walk
+    let ents = [];
+    try { ents = fs.readdirSync(dir, { withFileTypes: true }); } catch { continue; }
+    for (const e of ents) {
+      if (!e.isFile() || !e.name.endsWith('.md') || e.name.startsWith('.')) continue;
+      const m = docMeta(root, path.join(dir, e.name));
+      if (m) out.push(m);
+    }
+  }
+  return out;
+}
+
 function initiativeIndex(root) {
   const proots = planningRoots(root);          // planning/ at the root OR nested (e.g. IDPF/pmos/planning)
   const specimens = specimenMetas(root);       // prototype/<id>/ — outside planning/, grouped by dir
-  if (!proots.length && !specimens.length) return { initiatives: [], ungrouped: [] };
+  const records = looseRecordMetas(root, proots);   // pmos/state/initiatives/ — outside planning/ too
+  if (!proots.length && !specimens.length && !records.length) return { initiatives: [], ungrouped: [] };
   const metas = proots.flatMap((p) => walkMd(p, [])).map((f) => docMeta(root, f))
-    .filter(Boolean).concat(specimens);
+    .filter(Boolean).concat(specimens).concat(records);
   // Pass 1: every id an artifact explicitly declares. Only these are real initiatives —
   // a filename stem is promoted to a group only when it matches a declared id or when
   // several artifacts share it, so a lone research note never invents an initiative.
@@ -1075,10 +1186,10 @@ function surfaceOkr(root) {
   // Anchor health, NOT the initiative↔KR join — the join is an explicit non-goal of this spec. What
   // is reported is only whether each anchor names something these documents declare, because an
   // anchor pointing at nothing is precisely what went unseen for two days.
-  const budgets = A.readBudgets(root);
+  const budgets = budgetsFor(A, root);
   const unresolvable = [];
   let checked = 0, empty = 0;
-  for (const dir of findDirsNamed(root, 'initiatives', BUNDLE_MAX_DEPTH)) {
+  for (const dir of initiativeDirs(root)) {
     let files = [];
     try { files = fs.readdirSync(dir).filter((f) => f.endsWith('.md')); } catch { continue; }
     for (const f of files) {
@@ -1124,7 +1235,7 @@ function surfaceSpine(root) {
   if (!index.ok) {
     return { objectives: [], budgets: [], unanchored: [], unreadable: index.error || 'the OKR documents could not be read' };
   }
-  const budgetsDoc = A.readBudgets(root);
+  const budgetsDoc = budgetsFor(A, root);
 
   // the empty spine, keyed for O(1) attachment below
   const objectives = index.objectives.map((o) => ({
@@ -1138,7 +1249,7 @@ function surfaceSpine(root) {
   const budgets = new Map();       // health:<id> groups — peers of objectives (D59), not a footnote
   const unanchored = [];           // R6 — never dropped to make the tree tidy
 
-  for (const dir of findDirsNamed(root, 'initiatives', BUNDLE_MAX_DEPTH)) {
+  for (const dir of initiativeDirs(root)) {
     let files = [];
     try { files = fs.readdirSync(dir).filter((f) => f.endsWith('.md')).sort(); } catch { continue; }
     for (const f of files) {