create-pmos 0.20.1 → 0.21.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.21.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@ccaf639
 assembled: 2026-07-31
 mode: vendor

package/workspace/package-lock.json

@@ -1,12 +1,12 @@
 {
   "name": "pmos-workspace",
-  "version": "0.20.0",
+  "version": "0.21.0",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "pmos-workspace",
-      "version": "0.20.0",
+      "version": "0.21.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.21.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/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,