create-pmos 0.518.0 → 0.520.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-pmos",
-  "version": "0.518.0",
+  "version": "0.520.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. Includes `workflow-sweep`, which audits the state every board derives from and separates real defects from work you simply have not done. `create-pmos workspace` also installs + launches the local Terminal Workspace GUI. No database, no network, no telemetry.",
   "license": "MIT",
   "bin": {
@@ -32,6 +32,44 @@
     "audit"
   ],
   "pmosChanges": [
+    {
+      "v": "0.520.0",
+      "at": "2026-11-04T01:52:53.932Z",
+      "f": 4,
+      "prs": [
+        {
+          "n": 1216,
+          "t": "Every initiative has its own description",
+          "s": "Every initiative has its own description",
+          "k": "new"
+        }
+      ]
+    },
+    {
+      "v": "0.519.0",
+      "at": "2026-11-04T01:26:27.710Z",
+      "f": 4,
+      "prs": [
+        {
+          "n": 1213,
+          "t": "Every undated initiative is a Timeline row with No dates",
+          "s": "Every undated initiative is a Timeline row with No dates",
+          "k": "fix"
+        },
+        {
+          "n": 1214,
+          "t": "Chat prompt suggestions run on claude -p by default, and never fail silently",
+          "s": "Chat prompt suggestions run on claude -p by default, and never fail silently",
+          "k": "fix"
+        },
+        {
+          "n": 1215,
+          "t": "Background runs read long connector results; guide fills the wide Viewer",
+          "s": "Background runs read long connector results; guide fills the wide Viewer",
+          "k": "fix"
+        }
+      ]
+    },
     {
       "v": "0.518.0",
       "at": "2026-11-04T00:33:13.219Z",
@@ -358,52 +396,6 @@
           "d": "On a wide Viewer, Home's list could fold away and refuse to open again. Now the toggle opens and closes it every time."
         }
       ]
-    },
-    {
-      "v": "0.500.0",
-      "at": "2026-11-03T04:25:59.021Z",
-      "f": 4,
-      "prs": [
-        {
-          "n": 1183,
-          "t": "Delete a captured meeting-note point from its edit card",
-          "s": "Delete a captured meeting-note point from its edit card",
-          "k": "new",
-          "h": "Delete a meeting point",
-          "d": "A point captured from a meeting could not be removed. Now you can delete it from its edit card."
-        }
-      ]
-    },
-    {
-      "v": "0.499.0",
-      "at": "2026-11-03T03:30:26.339Z",
-      "f": 4,
-      "prs": [
-        {
-          "n": 1180,
-          "t": "The context meter knows the default model is 1M",
-          "s": "The context meter knows the default model is 1M",
-          "k": "fix",
-          "h": "The context meter reads right",
-          "d": "The context meter assumed a smaller model and filled up too early. Now it knows the default model has a much larger window."
-        },
-        {
-          "n": 1181,
-          "t": "`pmos initiative list` names records on a document lane",
-          "s": "pmos initiative list names records on a document lane",
-          "k": "fix",
-          "h": "Initiative lists name every record",
-          "d": "Listing initiatives missed the records of document work. Now it names them too."
-        },
-        {
-          "n": 1182,
-          "t": "Claude login test passes for a signed-in new user; picker shows each login once",
-          "s": "Claude login test passes for a signed-in new user; picker shows each login once",
-          "k": "fix",
-          "h": "Claude sign-in is checked properly",
-          "d": "The sign-in check could fail a user who was signed in, and the picker showed one login twice. Now it checks the real login and lists each one once."
-        }
-      ]
     }
   ]
 }

package/payload/AGENTS.md

@@ -33,7 +33,7 @@ It refuses frontmatter, fenced and indented code, table rows, headings, delibera
 
 | Hosted tool (as skills name them) | File-mode equivalent |
 |---|---|
-| `create_initiative` | write `pmos/state/initiatives/<id>.md` (frontmatter: id, title, parent_kr, stage, status, **type** — the D56 lane, default `feature` — plus `intent` for the chore lane, prd_path, rubric_path, created; plus `outcome_metric` + `outcome_horizon` — the D57 declaration for post-ship success criteria. No initiative goes without one: after you create it, and once its PRD exists, run `pmos outcomes propose <id>` and show the cited draft; write it with `pmos outcomes declare` only after the PM's yes) |
+| `create_initiative` | write `pmos/state/initiatives/<id>.md` (frontmatter: id, title, parent_kr, stage, status, **type** — the D56 lane, default `feature` — plus `intent` for the chore lane, prd_path, rubric_path, created; plus `outcome_metric` + `outcome_horizon` — the D57 declaration for post-ship success criteria. No initiative goes without one: after you create it, and once its PRD exists, run `pmos outcomes propose <id>` and show the cited draft; write it with `pmos outcomes declare` only after the PM's yes; plus `description` — one paragraph that says what the initiative is, shown in About before any PRD exists: `pmos initiative describe <id>` lists the cited lines to draft it from, and `pmos initiative describe <id> "<text>"` writes it only after the PM's yes) |
 | `save_spec` | the PRD file itself at `pmos/planning/prd/<id>-prd.md` (set `prd_path` on the initiative file) |
 | `get_spec` / `get_planning_artifact` | read `pmos/planning/…` |
 | `get_skill` | read `pmos/skills/<name>.skill` |

package/payload/KIT-VERSION

@@ -1,3 +1,3 @@
-kernel-source: pmos@ed082f08
+kernel-source: pmos@5c846c69
 assembled: 2026-11-04
 mode: vendor

package/payload/planning/evals/eval-calibration.md

@@ -2,7 +2,7 @@
 type: Reference
 title: "Eval calibration log"
 description: "Append-only record of every PM override of an evaluator verdict."
-generated: {by: process:create-pmos, at: "2026-11-04T00:33:09Z"}
+generated: {by: process:create-pmos, at: "2026-11-04T01:52:50Z"}
 status: stable
 ---
 

package/payload/planning/okrs/health-budgets.md

@@ -2,7 +2,7 @@
 type: Reference
 title: "Health budgets"
 description: "Closed registry of health-budget anchors (D59), edited only by the PM."
-generated: {by: process:create-pmos, at: "2026-11-04T00:33:09Z"}
+generated: {by: process:create-pmos, at: "2026-11-04T01:52:50Z"}
 status: stable
 ---
 

package/payload/state/discoveries.md

@@ -2,7 +2,7 @@
 type: Reference
 title: "Discoveries and friction log"
 description: "Append-only record of what runs discovered and where the process rubbed."
-generated: {by: process:create-pmos, at: "2026-11-04T00:33:09Z"}
+generated: {by: process:create-pmos, at: "2026-11-04T01:52:50Z"}
 status: stable
 ---
 

package/workspace/board-columns-test.js

@@ -113,7 +113,7 @@ const ITEMS = [
     const before = await rowsIn(p);
     await p.click('#ibBody [data-tsort="status"]'); await p.waitForTimeout(200);
     const byStatus = await rowsIn(p), aria = await p.evaluate(() => document.querySelector('#ibBody [data-tsort="status"]').getAttribute('aria-sort'));
-    ok('S pressing Status puts late, at risk and on hold first', byStatus.slice(0, 3).join() === 'lightbox,magw,email-otp' && aria === 'ascending', JSON.stringify(byStatus));
+    ok('S pressing Status puts late, at risk and on hold first (the undated usage-billing is a row since batch 26 item 8)', byStatus.slice(0, 4).join() === 'lightbox,magw,usage-billing,email-otp' && aria === 'ascending', JSON.stringify(byStatus));
     await p.click('#ibBody [data-tsort="status"]'); await p.waitForTimeout(200);
     ok('S a second press goes back to time order', (await rowsIn(p)).join() === before.join(), JSON.stringify([before, await rowsIn(p)]));
     // P: the Columns menu

package/workspace/board-programs-test.js

@@ -218,9 +218,9 @@ process.on('unhandledRejection', (e) => { console.error(e); finish(1); });
       const row = [...d.querySelectorAll('.tg-r[data-row]')].find((r) => /Mobile OTP login/.test(r.textContent));
       return { member: !!row, nd: row ? (row.querySelector('.tg-nd') || {}).textContent : '', loose: [...d.querySelectorAll('.tg-r[data-row]')].some((r) => /Loose undated/.test(r.textContent)), none: T.none.length };
     });
-    ok('T an undated initiative in a program keeps its row under the program and says "No dates"; an undated one outside a program is named in the foot only (batch 8 item 4)', nd.member && nd.nd === 'No dates' && !nd.loose && nd.none === 2, JSON.stringify(nd));
+    ok('T an undated initiative in a program keeps its row under the program and says "No dates"; an undated one outside a program is a row too (batch 8 item 4, batch 26 item 8)', nd.member && nd.nd === 'No dates' && nd.loose && nd.none === 2, JSON.stringify(nd));
     // batch 11 item 19: By product, a program's undated initiative keeps its "No dates" row under its product (it disappeared once grouped by
-    // product); an undated one in no program is still named in the foot only
+    // product); since batch 26 item 8 an undated one in no program is a "No dates" row too
     const bnd = await p.evaluate(async () => {
       const S = await import('/pm/bd-span.js'), now = new Date(2026, 9, 26);
       const a = { key: 'board:a', id: 'a', title: 'Dated one', start: '2026-10-01', end: '2026-11-20', track: { key: 'build' } };
@@ -232,11 +232,11 @@ process.on('unhandledRejection', (e) => { console.error(e); finish(1); });
         const d = document.createElement('div'); d.innerHTML = T.html;
         const rs = [...d.querySelectorAll('[data-row]')], row = rs.find((r) => r.dataset.row === 'board:b');
         const out = { phone, rows: rs.map((r) => r.dataset.row), nd: row ? (row.querySelector('.tg-nd') || {}).textContent : '', none: T.none.length };
-        if (!(out.nd === 'No dates' && out.rows.join() === 'board:a,board:b' && out.none === 2)) return out;
+        if (!(out.nd === 'No dates' && out.rows.join() === 'board:a,board:b,board:c' && out.none === 2)) return out;
       }
       return true;
     });
-    ok('T By product: a program\'s undated initiative keeps its "No dates" row under its product, desktop and phone; one in no program is in the foot only (batch 11 item 19)', bnd === true, JSON.stringify(bnd));
+    ok('T By product: a program\'s undated initiative keeps its "No dates" row under its product, desktop and phone; one in no program is a row too (batch 11 item 19, batch 26 item 8)', bnd === true, JSON.stringify(bnd));
     // batch 14 item 2: a product whose initiatives are all undated (outside a program) kept no group, so it was missing from the Board
     const pnd = await p.evaluate(async () => {
       const S = await import('/pm/bd-span.js'), now = new Date(2026, 9, 26);
@@ -249,8 +249,27 @@ process.on('unhandledRejection', (e) => { console.error(e); finish(1); });
       const row = d.querySelector('[data-row="board:m"]');
       return { heads: [...d.querySelectorAll('[data-prod]')].map((x) => x.dataset.prod).join(), nd: row ? (row.querySelector('.tg-nd') || {}).textContent : '', loose: !!d.querySelector('[data-row="board:c"]'), foot: ((d.querySelector('.tg-ft .tg-none span') || {}).textContent || '') };
     });
-    ok('T a product with only undated initiatives keeps its head and its "No dates" rows; they leave the foot, which still names the rest (batch 14 item 2)',
-      pnd.heads === 'p:x,p:ms' && pnd.nd === 'No dates' && !pnd.loose && pnd.foot === 'Loose undated', JSON.stringify(pnd));
+    ok('T a product with only undated initiatives keeps its head and its "No dates" rows (batch 14 item 2)',
+      pnd.heads === 'p:x,p:ms' && pnd.nd === 'No dates' && pnd.loose, JSON.stringify(pnd));
+    // batch 26 item 8 (Wawan: "8 have no dates" sat in the foot and none was a row): every undated initiative is a "No dates" row beside today, in
+    // every grouping (Programs first, By product, no groups), desktop and phone; the foot keeps the count and "Ask to propose dates", with no names
+    const all = await p.evaluate(async () => {
+      const S = await import('/pm/bd-span.js'), now = new Date(2026, 9, 26);
+      const r = (k, s, e) => ({ key: 'board:' + k, id: k, title: 'Row ' + k, start: s, end: e, track: { key: 'discover' } });
+      const a = r('a', '2026-10-01', '2026-11-20'), u1 = r('u1', null, null), u2 = r('u2', null, null), u3 = r('u3', null, null);
+      const prog = [{ kind: 'program', key: 'p', program: { id: 'p', title: 'P', products: [] }, products: [{ name: 'X', rows: [u1] }], rows: [u1] }, { kind: 'product', key: 'x', rows: [a, u2, u3] }];
+      const byProd = [{ kind: 'product', key: 'x', rows: [a, { ...u1, inProgram: 'p' }, u2] }, { kind: 'product', key: 'y', rows: [u3] }];
+      const bad = [];
+      for (const [name, groups] of [['programs', prog], ['product', byProd], ['none', undefined]]) for (const phone of [false, true]) {
+        const T = S.timelineHtml([a, u1, u2, u3], { jira: null }, 'quarter', { now, groups, phone, askHref: () => '#ask' });
+        const d = document.createElement('div'); d.innerHTML = T.html;
+        const nd = ['u1', 'u2', 'u3'].map((k) => d.querySelector(`[data-row="board:${k}"] .tg-nd`)).filter((x) => x && x.textContent === 'No dates').length;
+        const ft = d.querySelector(phone ? '.tg-none' : '.tg-ft .tg-none'), txt = ft ? ft.textContent : '';
+        if (nd !== 3 || !d.querySelector('#askDates') || !/3 have no dates/.test(txt) || /Row u/.test(txt)) bad.push({ name, phone, nd, txt });
+      }
+      return bad;
+    });
+    ok('T every undated initiative is a "No dates" row in every grouping, desktop and phone, in no program too; the foot keeps the count and Ask to propose dates (batch 26 item 8)', !all.length, JSON.stringify(all));
     ok('T a legend in the chip row names done, planned, Milestone (Deliver, Evaluate and milestone tasks, batch 11 item 3) and today; no program milestone key while a program draws none (batch 13 item 4)', /Done in Jira/.test(t.lgd) && /To do/.test(t.lgd) && !/Program milestone/.test(t.lgd) && /Milestone/.test(t.lgd) && /Today/.test(t.lgd), t.lgd);
     await p.click('#ibBody .tg-pg .tg-pgo');
     // the program opens in the floating Viewer (shell A), which sits over the right of the timeline; close it before the next press
@@ -319,7 +338,7 @@ process.on('unhandledRejection', (e) => { console.error(e); finish(1); });
     // the phone (TsCPhone, TsCPhoneSpan): the timeline is a view; the span buttons become one picker beside the product picker
     const { ctx, page: p, errors } = await open({ view: 'time', w: 390, h: 844, store: { 'pmos.board.pview': 'time', 'pmos.board.span': 'quarter' } });
     const ph = await p.evaluate(() => ({ spans: !document.querySelector('#bdSpans').hidden, pick: (document.querySelector('#bdSpanBtn') || {}).textContent || '', rows: [...document.querySelectorAll('#ibBody .tgq-r .tgq-n b')].map((b) => b.textContent), names: document.querySelectorAll('#ibBody .tgq-r[data-row] .tgq-n').length }));
-    ok('S phone: one span picker beside the product, no span row; each row carries its name above its bar, Monitor and Evaluate rows too (batch 8 item 2)', !ph.spans && ph.pick === 'Quarter' && ph.names === 3 && ph.rows.includes('Legacy IdP sunset') && ph.rows.includes('Inline login for eShop checkout'), JSON.stringify(ph));
+    ok('S phone: one span picker beside the product, no span row; each row carries its name above its bar, Monitor and Evaluate rows too (batch 8 item 2), and the undated one as a "No dates" row (batch 26 item 8)', !ph.spans && ph.pick === 'Quarter' && ph.names === 4 && ph.rows.includes('Usage-based billing') && ph.rows.includes('Legacy IdP sunset') && ph.rows.includes('Inline login for eShop checkout'), JSON.stringify(ph));
     await p.click('#bdSpanBtn'); await p.click('#bdSpanMenu [data-spick="year"]'); await p.waitForTimeout(200);
     ok('S phone: the picker changes the span', await p.evaluate(() => document.querySelector('#ibBody .tg-s').dataset.span === 'year' && document.querySelector('#bdSpanBtn').textContent === 'Year' && localStorage.getItem('pmos.board.span') === 'year'));
     await p.evaluate(() => { const sc = document.querySelector('#ibBody .tg-sc'); sc.scrollLeft = sc.scrollWidth; }); await p.waitForTimeout(200);

package/workspace/briefing-premium-board-test.js

@@ -337,7 +337,7 @@ const IVREAD = () => {
    * timeline spans C: TsAllSpans); the scroll itself is checked in board-programs-test.js (T) */
   await view(p, 'time');
   const tl = await p.evaluate(() => ({ spans: [...document.querySelectorAll('#bdSpans [data-sp]')].map((b) => b.textContent + (b.getAttribute('aria-checked') === 'true' ? '*' : '')).join(), shown: !document.querySelector('#bdSpans').hidden, rows: [...document.querySelectorAll('#ibBody .tg-r .tg-n.ini2 b')].map((b) => b.textContent), bars: document.querySelectorAll('#ibBody .tg-bar').length, none: (document.querySelector('.tg-none') || {}).textContent || '', ask: (document.querySelector('#askDates') || {}).href || '', hid: (document.querySelector('.tg-hid') || {}).textContent || '', lgd: (document.querySelector('.tg-lgd') || {}).textContent || '', today: (document.querySelector('#ibBody .tg-tpill') || {}).textContent === 'Today' }));
-  ok('B6 the timeline has six spans and starts on Quarter, one row per initiative with dates; the others are named, with an ask to propose dates', tl.shown && tl.spans === 'Sprint,Quarter*,Half,Year,2 yr,5 yr' && tl.rows.length === 3 && tl.bars === 3 && /^4 have no dates: Usage-based billing, Audit log export, Refund reason codes, Docs search/.test(tl.none) && /\/premium\.html\?ask=board%3Aw1&q=Propose/.test(tl.ask), JSON.stringify(tl));
+  ok('B6 the timeline has six spans and starts on Quarter, one row per initiative; the 4 with no dates are rows too (batch 26 item 8), counted in the foot with an ask to propose dates', tl.shown && tl.spans === 'Sprint,Quarter*,Half,Year,2 yr,5 yr' && tl.rows.length === 7 && ['Usage-based billing', 'Audit log export', 'Refund reason codes', 'Docs search'].every((n) => tl.rows.includes(n)) && tl.bars === 3 && /^4 have no dates/.test(tl.none) && !/Docs search/.test(tl.none) && /\/premium\.html\?ask=board%3Aw1&q=Propose/.test(tl.ask), JSON.stringify(tl));
   ok('B6 Monitor and Evaluate show on the Quarter, with no hidden count in the footer (batch 8 item 2); the legend (PgTimeline: done, planned, the Jira forecast, Milestone (batch 11 item 3), today) and Today are drawn', tl.hid === '' && /Done in Jira/.test(tl.lgd) && /To do/.test(tl.lgd) && /Jira forecast/.test(tl.lgd) && /Milestone/.test(tl.lgd) && /Today/.test(tl.lgd) && tl.today, JSON.stringify(tl));
   ok('B6 the spans help popover went with the theme grouping (TsCGrill): the first head is a plain "Initiative"', await p.evaluate(() => !document.querySelector('#popRules') && !document.querySelector('#ibBody [data-rules]') && /^Initiative/.test(document.querySelector('#ibBody .tg-h .tg-n').textContent)));
   await p.click('#ibBody .tg-n[data-key="board:partner-rate-limits"]');
@@ -361,7 +361,7 @@ const IVREAD = () => {
   ok('B6 Year draws Quarter\'s rows (TsAllSpans): one row per initiative with its bar, months as columns; no themes, no Group chip; the chips and the legend stay', yr.rows.join() === tl.rows.join() && yr.bars === 3 && !yr.themes && !yr.group && yr.lgd && yr.jira && yr.heads.length >= 12 && yr.heads.every((h) => /^[A-Z][a-z]{2}$/.test(h)), JSON.stringify(yr));
   await spanTo(p, 'y5');
   const y5 = await p.evaluate(() => ({ rows: document.querySelectorAll('#ibBody .tg-q[data-span="y5"] .tg-n.ini2').length, heads: [...document.querySelectorAll('#ibBody .tg-h .tg-p > span[data-y] b')].map((b) => b.textContent), dates: [...document.querySelectorAll('#ibBody .tg-endl, #ibBody .tg-lab, #ibBody .tg-cms')].map((e) => e.innerText.replace(/\s+/g, ' ').trim()) }));   // with the Next milestone column (batch 19 item 5) the column says it
-  ok('B6 5 yr draws the same rows with years as columns, and each bar ends with what lands, then when (batch 13 item 4)', y5.rows === 3 && y5.heads.length >= 5 && y5.heads.every((h) => /^\d{4}$/.test(h)) && y5.dates.length === 3 && y5.dates.every((d) => /^[A-Z][\w ]* [A-Z][a-z]{2} \d{1,2}( ’\d\d)?( \+\d+d)?$/.test(d)), JSON.stringify(y5));
+  ok('B6 5 yr draws the same rows with years as columns, and each bar ends with what lands, then when (batch 13 item 4)', y5.rows === 7 && y5.heads.length >= 5 && y5.heads.every((h) => /^\d{4}$/.test(h)) && y5.dates.length === 3 && y5.dates.every((d) => /^[A-Z][\w ]* [A-Z][a-z]{2} \d{1,2}( ’\d\d)?( \+\d+d)?$/.test(d)), JSON.stringify(y5));
   const sp = [];
   for (const [k, sel, re] of [['sprint', '.sp[data-span="sprint"]', /Initiative and ticket.*Backlog · \d+ not in/], ['half', '.tg-q[data-span="half"]', /Self-serve onboarding v2/], ['y2', '.tg-q[data-span="y2"]', /Self-serve onboarding v2/]]) { await spanTo(p, k); sp.push(await p.evaluate(([q2, r]) => { const e = document.querySelector('#ibBody ' + q2); return !!e && !document.querySelector('#ibBody .bd-wtag') && new RegExp(r).test(e.textContent); }, [sel, re.source])); }
   ok('B6 Sprint (BdSpans: tickets and the backlog row), Half and 2 yr (Quarter\'s rows) are drawn, with no "Waiting for design" tag', sp.every(Boolean), JSON.stringify(sp));
@@ -369,7 +369,7 @@ const IVREAD = () => {
   {
     const f = F.facts(); f.rows = f.rows.map((r) => ({ ...r, start: null, end: null }));
     const R = await open({ model: BP.build(f) }); await view(R.page, 'time');
-    ok('B6 with no dates anywhere it draws nothing and says so', await R.page.evaluate(() => document.querySelectorAll('#ibBody .tg-bar').length === 0 && /No initiative on screen has a date on record/.test(document.querySelector('#ibBody').textContent)));
+    ok('B6 with no dates anywhere it draws no bar; every initiative is a "No dates" row (batch 26 item 8)', await R.page.evaluate(() => document.querySelectorAll('#ibBody .tg-bar').length === 0 && document.querySelectorAll('#ibBody .tg-r[data-row]').length > 0 && [...document.querySelectorAll('#ibBody .tg-r[data-row]')].every((r) => !!r.querySelector('.tg-nd'))));
     await R.ctx.close();
   }
   await view(p, 'track');

package/workspace/calm-timeline-test.js

@@ -166,7 +166,7 @@ const ITEMS = [
       lane: [...document.querySelectorAll('#ibBody .tg-lane.closed')].map((x) => ({ span: x.querySelectorAll('.tg-p .tg-span').length, end: (x.querySelector('.tg-p .tg-endl') || {}).textContent || '', dots: x.querySelectorAll('.tg-offd .cz-dot').length })),
     }));
     ok('G folded, a program shows the roll-up line, its ◇s and its end date', g.prog.length > 0 && g.prog.every((x) => x.span > 0 && x.dm > 0 && /’\d\d$/.test(x.end)), JSON.stringify(g));
-    ok('G folded, a product shows the roll-up, its end date and one dot per initiative off track', g.lane.length > 0 && g.lane.some((x) => x.span > 0 && x.end && x.dots === 3), JSON.stringify(g));
+    ok('G folded, a product shows the roll-up, its end date and one dot per initiative off track (its undated one counts: it is a row since batch 26 item 8)', g.lane.length > 0 && g.lane.some((x) => x.span > 0 && x.end && x.dots === 4), JSON.stringify(g));
     await c2.close();
   }
 
@@ -179,7 +179,7 @@ const ITEMS = [
       dots: [...document.querySelectorAll('#ibBody .tgq-r[data-row] .tgq-n')].map((b) => (b.querySelector('.cz-dot') || {}).className || ''),
       scroll: document.documentElement.scrollWidth <= innerWidth + 1,
     }));
-    ok('M the phone keeps the end labels, a dot only off track, and no sideways page scroll', m.labels >= 5 && m.dots.filter(Boolean).length === 3 && m.scroll, JSON.stringify(m));
+    ok('M the phone keeps the end labels, a dot only off track (the undated row too, batch 26 item 8), and no sideways page scroll', m.labels >= 5 && m.dots.filter(Boolean).length === 4 && m.scroll, JSON.stringify(m));
     ok('M no page error on the phone', errors.length === 0, errors.join(' | '));
     await ctx.close();
   }

package/workspace/changelog.json

@@ -1,4 +1,42 @@
 [
+ {
+  "v": "0.520.0",
+  "at": "2026-11-04T01:52:53.932Z",
+  "f": 4,
+  "prs": [
+   {
+    "n": 1216,
+    "t": "Every initiative has its own description",
+    "s": "Every initiative has its own description",
+    "k": "new"
+   }
+  ]
+ },
+ {
+  "v": "0.519.0",
+  "at": "2026-11-04T01:26:27.710Z",
+  "f": 4,
+  "prs": [
+   {
+    "n": 1213,
+    "t": "Every undated initiative is a Timeline row with No dates",
+    "s": "Every undated initiative is a Timeline row with No dates",
+    "k": "fix"
+   },
+   {
+    "n": 1214,
+    "t": "Chat prompt suggestions run on claude -p by default, and never fail silently",
+    "s": "Chat prompt suggestions run on claude -p by default, and never fail silently",
+    "k": "fix"
+   },
+   {
+    "n": 1215,
+    "t": "Background runs read long connector results; guide fills the wide Viewer",
+    "s": "Background runs read long connector results; guide fills the wide Viewer",
+    "k": "fix"
+   }
+  ]
+ },
  {
   "v": "0.518.0",
   "at": "2026-11-04T00:33:13.219Z",

package/workspace/guide/agent-capabilities.md

@@ -31,6 +31,7 @@ This page lists every job, so you know what runs and why. Each row links to the
 | [New dates, done and tidy names](claude-proposes.md) | Each morning, and when a date passes | The tasks of the initiative, and the evidence that work happened | The initiative's ✦ | `PMOS_PROPOSE=off` |
 | [Grill](claude-proposes.md) | Before an initiative leaves a stage, when a forecast turns at risk, when scope or dates move a lot, and once a month on running work with late work. Also when you write "grill this" in the initiative's chat. | The initiative, your stored research, your meeting notes and the decisions that stand | "Claude grilled it" under the initiative's ✦ | Settings › Claude's checks: Off. `PMOS_GRILL=off` |
 | [You decided this before](ask-the-past.md) | You add an initiative that repeats an earlier decision | `DECISIONS.md`, the decision records, the PM journal, `planning/out-of-scope/` and the initiative records | The initiative's ✦ | `pmos ai off past-repeat` |
+| [Initiative descriptions](descriptions.md) | Once a day. At most 3 drafts a day for each product. | The PRD's first Problem or Why paragraph, or the record's own first paragraph | "Description" under the initiative's ✦ | `pmos ai off descriptions`. `PMOS_DESCRIPTIONS=off` |
 | [Expected outcomes](outcomes.md) | Once a day. At most 3 drafts a day for each product. | The PRD's success criteria, or the anchored key result | "Expected outcome" under the initiative's ✦. Today when a check is due. | `pmos ai off outcomes`. `PMOS_OUTCOMES=off` |
 | [Metric drafts](metric-drafts.md) | A product with no North Star, the first 14 days of a quarter, a program with no goal, and an initiative that gets a PRD | The last 8 weeks of real readings | The page of that product, program or initiative | `PMOS_METRIC_DRAFT=off` |
 | [Horizon scan](horizon-scan.md) | Daily by default, at most once a day. Scan now: at most 3 a day. | The public web for your kept watch list, and your repository | Report documents and proposals you approve | Cadence: Off. `PMOS_SCAN=off` |
@@ -70,4 +71,4 @@ When you ask an agent session to do a piece of work, it can finish it, including
 - `pmos ai log [<job>]`: the last audit lines. Each dropped proposal shows why.
 - `pmos ai off [<job>]` and `pmos ai on [<job>]`: turn every AI job, or one job, off or on. `PMOS_AI=off` in the environment wins over the setting.
 
-The AI jobs are `past-repeat`, `decision-memory`, `outcomes`, `drift`, `rehearse`, `next-prompt` and `sharpen-prompt`. A background run cannot change the switch.
+The AI jobs are `past-repeat`, `decision-memory`, `outcomes`, `descriptions`, `drift`, `rehearse`, `next-prompt` and `sharpen-prompt`. A background run cannot change the switch.

package/workspace/guide/descriptions.md

@@ -0,0 +1,43 @@
+---
+type: Guide
+title: "Initiative descriptions"
+description: "Every initiative says what it is in About, before any PRD exists. Where the description is kept, how Claude drafts it, how you keep one, how a PRD enriches it, and pmos initiative describe."
+timestamp: 2026-11-04
+---
+
+# Initiative descriptions
+
+Every initiative has a description: one paragraph that says what it is. About, in the initiative's mission control, shows it. An initiative needs one long before its PRD is written.
+
+## Where it is kept
+
+The description is the `description:` line in the initiative's record. It is not in the PRD. One paragraph, up to 700 characters.
+
+## What About shows
+
+- The record has a description: About shows it.
+- The PRD says more than the description: About also shows the PRD's paragraph once, below it, marked **From the PRD**.
+- The record has no description: About shows the PRD's first Problem, Why or Background paragraph, marked **From the PRD**.
+- Neither: About says "No description yet" and shows **Ask Claude to draft it**.
+
+## Claude drafts it
+
+Once a day Claude drafts a description for an initiative that has none, and files it under the initiative's ✦ in **Check these**. The draft is the PRD's own paragraph, or the first paragraph of the record that says what the work is. Each draft cites the line it comes from. When there is nothing to read, Claude makes no draft. At most 3 drafts a day for each product.
+
+When a PRD is written later and says more than the description, Claude drafts **A fuller description from the PRD**.
+
+- ✓ saves the draft to the record. Undo puts back what was there.
+- ✕ drops it. Claude does not draft the same one again.
+
+## Ask Claude to draft it
+
+**Ask Claude to draft it** opens Home's chat with a prompt. Claude reads what it can, shows you a draft, and saves it after you say yes.
+
+## Commands
+
+- `pmos initiative describe <id>`: the description, and the lines Claude can draft it from.
+- `pmos initiative describe <id> "<text>"`: save the description. Claude runs this only after your yes.
+
+## Turn it off
+
+`pmos ai off descriptions` stops the daily drafts. `pmos ai on descriptions` starts them again. `PMOS_DESCRIPTIONS=off` also stops them.

package/workspace/guide/index.md

@@ -1,14 +1,14 @@
 ---
 type: Guide
 title: "Guide: start here"
-timestamp: 2026-11-03
+timestamp: 2026-11-04
 ---
 
 # Guide: start here
 
 This guide describes the PMOS workspace as it works today. It ships with the app. When a change alters how the workspace looks or behaves, the same change updates this guide.
 
-To open the guide from any page, press the round menu button at the bottom of the page, then the **?** icon (Guide). The guide opens wide in the Viewer. Every page is in the list on the left, by group, with **Find a page** on top; a group folds and stays folded. Above each page, one chip for each of its sections takes you there. A link to another guide page opens that page in the same place. Press ← to go back. On a phone, or when the Viewer is narrow, the list icon beside the title shows the list.
+To open the guide from any page, press the round menu button at the bottom of the page, then the **?** icon (Guide). The guide opens wide in the Viewer and uses its full width. Every page is in the list on the left, by group, with **Find a page** on top; a group folds and stays folded. Above each page, one chip for each of its sections takes you there. A link to another guide page opens that page in the same place. Press ← to go back. On a phone, or when the Viewer is narrow, the list icon beside the title shows the list.
 
 ## The screen
 
@@ -56,6 +56,7 @@ PMOS has three places: **Home**, **Board** and **Intelligence**. The round menu
 - [Claude proposes: the one ✦ on each initiative](claude-proposes.md): what Claude finds when you add an initiative, new dates, done and tidy names for late tasks, ✓, ✕, Undo, and `pmos propose`.
 - [The next prompt, suggested and sharpened](next-prompt.md): what the chat suggests after a reply, and the sharper version of a rough prompt.
 - [Ask about the past](ask-the-past.md): why something was decided or dropped, answered in the initiative chat from the records; "You decided this before" on a new initiative.
+- [Initiative descriptions](descriptions.md): what About says about an initiative, where it is kept, Claude's drafts, and `pmos initiative describe`.
 - [Expected outcomes](outcomes.md): what each initiative should change once it ships, the date to check it, and `pmos outcomes`.
 - [Rehearse a plan](rehearse.md): what a date change or a cut breaks or helps, before you approve it, and `pmos rehearse`.
 - [Your impact](your-impact.md): what counts as your impact, the weekly check in Home's chat, the switch, and `pmos impact`. Private to you.

package/workspace/guide/initiatives-roadmap.md

@@ -111,6 +111,7 @@ Every measurement needs a source: the file the value comes from and its commit,
 | `pmos initiative drop <proposal>` | Closes a proposal. |
 | `pmos initiative list` | Shows the Roadmap in rank order, with each lifecycle stage, check-by date and the open proposals. |
 | `pmos initiative export <id>` | Writes the breakdown as markdown to the terminal. |
+| `pmos initiative describe <id> ["<text>"]` | Shows the description and the lines Claude can draft it from. With text, saves the description. See [Initiative descriptions](descriptions.md). |
 
 Every command takes `--json` and `--root <dir>`. The command does not accept `--by` or `--via`. `pmos initiative now`, `next` and `later` are retired: they write nothing, say what to use instead and exit 2.
 

package/workspace/guide/next-prompt.md

@@ -30,7 +30,7 @@ Each card names only the initiatives, tasks and PRs that the reply or your messa
 
 ## While you type
 
-When you stop typing for about 1.5 seconds on a rough prompt of three or more words, a small spinner card shows while Claude sharpens it. Then one lit **Sharper** card shows. Tap it to put the sharper text in the box. ↶ in the box puts back what you wrote. When the sharper version says the same as yours, no card shows.
+When you stop typing for about 1.5 seconds on a rough prompt of three or more words, a small spinner card shows while Claude sharpens it. This takes a few seconds. Then one lit **Sharper** card shows. Tap it to put the sharper text in the box. ↶ in the box puts back what you wrote. When the sharper version says the same as yours, no card shows.
 
 The sliders icon on the Sharper card sets how Claude sharpens:
 
@@ -45,7 +45,7 @@ The same menu has the **Sharpen as I type** switch. Off means no spinner and no
 | Row | What it does |
 |---|---|
 | Suggest the next prompt | On by default. Off: no cards after a reply. |
-| Sharpen as I type | On when Claude's runs use your API key (Settings › Claude › API key), because a sharper version then shows in about 2 seconds. Without a key, each one is a background Claude run that takes 10 seconds or more, so it starts off. You can turn it on anyway. |
+| Sharpen as I type | On by default. Off: no spinner and no Sharper card. |
 | Sharpen as | Polish, Prompt engineer or Your own. |
 | Your own rules | The rules for Your own, up to 1000 characters. |
 
@@ -57,6 +57,8 @@ The suggestions and the sharper prompt go through the same guardrail as every AI
 - **Proven only.** Each suggested move points to the line of PMOS code that makes it work, and PMOS checks that line before the card shows. An answer to the reply points to the line of the reply it answers. A card that PMOS cannot check is not shown.
 - **Replay-tested.** A new version shows nothing until its recorded cases pass, and those include cases that must be dropped.
 - **Audited.** Each run writes a line to the AI audit, with no text of your conversation in it.
+- **Your own Claude session.** Both run as a short background `claude -p` run on your own Claude login, which can only read files. Your API key is not used unless you set `PMOS_NEXT_PROMPT_API=on`. Then, when a call on the key fails, the same request goes to the background run instead.
+- **No silent failure.** When a run gives no card, the audit says why. `pmos ai log next-prompt` and `pmos ai log sharpen-prompt` show the last lines.
 - **Off switch.** `pmos ai off next-prompt` stops the suggestions after a reply. `pmos ai off sharpen-prompt` stops the Sharper card. `pmos ai off` stops every AI job.
 
 The reply and the words a card refers to are kept in your PMOS state folder (`next-prompt/`, the newest 30 files), outside every repository. Your choices for these rows are kept there too, in `next-prompt/prefs.json`.

package/workspace/guide/programs.md

@@ -2,7 +2,7 @@
 type: Guide
 title: "Programs on the Board: All products, groupings and the program panel"
 description: "A program groups initiatives across products. How it shows on the Board (stage track, Kanban, timeline and List), the All products mode, the By product grouping, the program panel and the side panel width."
-timestamp: 2026-11-03
+timestamp: 2026-11-04
 ---
 
 # Programs on the Board
@@ -22,6 +22,7 @@ A cancelled or archived initiative leaves its program's views: the band, the pro
 - To group by product only, open **Filter** and choose **By product**. A program member then shows a small layers icon and stays under its product in every view, the timeline included. A chip shows while By product is on.
 - **Kanban** shows programs as swimlanes, then products. Press a column header to fold the column to a strip with its count. An empty column starts folded. The Board remembers each fold.
 - The **timeline** draws a program row that brackets its initiatives' bars, on every span. Program milestones are diamonds. Milestones that are close together merge into one diamond with a count.
+- On the timeline, **every initiative has a row**, in a program or not, in every grouping. An initiative with no dates says **No dates** beside today; in each group it comes after the dated ones. Under the chart, a line gives how many have no dates, with **Ask to propose dates**.
 - On the timeline, a **product's head row** also shows milestones. Nothing is added by hand: the row shows every milestone of the product's initiatives, which are each milestone task and each initiative's end diamond (its Deliver or Evaluate date). The diamonds are the same as on the initiative rows: open, filled when done, orange when late. Diamonds that are close together merge into one diamond with a count and the date range under it. Press it to see a list with the milestone, its initiative and the date. Press a line to open that initiative. Hold the pointer on a single diamond to see its milestone and initiative. A thin line goes from the first start to the last end of the product's initiatives. When the product is folded, the row stays the same, so it is a summary of the product. On a phone the diamonds have no dates; tap the row to see all the milestones in date order. A product inside a program has no such row, because the program row shows its milestones.
 - On the timeline, an initiative row shows only its **pinned** milestones. By default that is its last milestone. Press a diamond to see every milestone of the initiative, with how many are on the timeline. Press the pin beside a milestone to show it or to hide it. To see every milestone or none, open **Filter** and pick **Milestones on the timeline: Pinned**, **All** or **None**. The Board keeps your pick. From a terminal: `pmos task set <task> --pin`, `--no-pin`, or `--pin-default` to go back to the default.
 - The label at the end of an initiative row says what lands and when. When a milestone task is in the last milestone stage, or is on the end date, or is in the Deliver stage, or is so close to the end date that its diamond would sit on the end diamond, the label shows its name and its own date, and the end date of the initiative shows when you hold the pointer on the label. Otherwise the latest milestone task of the initiative names the end in the same way, even when it is months before the end date. Only an initiative with no dated milestone task shows **Deliver** (or **Evaluate**) and the end date. Press that end diamond: the card has the same words as the label, then the milestones of the initiative.

package/workspace/guide/settings.md

@@ -49,7 +49,7 @@ Under the update card, **Updates** shows what changed in the published kits. **T
 
 **API key.** Some runs of Claude, for example Grill, can use the Claude API and not a Claude session. Paste an Anthropic API key and press **Save** to turn this on. The key stays on this computer, in a file only you can read, outside every repository. PMOS never shows the key again: the row only says that a key is set. Press **Remove** to delete it. A key saved here is used before `ANTHROPIC_API_KEY`. A command that a run starts does not get the key. Only the computer that runs the workspace can change it. Set `PMOS_GRILL_API=off` to stop runs on the API.
 
-**Sharpen prompts.** Suggest the next prompt (on by default) shows up to two prompts above the chat box after a reply. Sharpen as I type offers a sharper version of a rough prompt. It is on when an API key is set, and off without one, because a background run is too slow to follow your typing. Sharpen as picks Polish, Prompt engineer (the default) or Your own, and Your own rules holds the rules for Your own. The same style and switch are in the menu on the chat's Sharper card. See [The next prompt, suggested and sharpened](next-prompt.md).
+**Sharpen prompts.** Suggest the next prompt (on by default) shows up to two prompts above the chat box after a reply. Sharpen as I type offers a sharper version of a rough prompt. It is on by default and runs in your own Claude session. Sharpen as picks Polish, Prompt engineer (the default) or Your own, and Your own rules holds the rules for Your own. The same style and switch are in the menu on the chat's Sharper card. See [The next prompt, suggested and sharpened](next-prompt.md).
 
 ## Claude's checks: when Claude grills, and what it may spend
 

package/workspace/lib/board-trail.js

@@ -163,7 +163,8 @@ function trail({ root, ids, rows = [], moves = [], now = Date.now(), io } = {})
   const evalNames = X.list ? X.list('planning/evals') : [];
   const rowBy = new Map(rows.map((r) => [r.id, r]));
   const fmCache = new Map();
-  const fmOf = (id) => { if (!fmCache.has(id)) { const t = X.text('planning/initiatives/' + id + '.md'); fmCache.set(id, t == null ? null : { fm: frontmatter(t), text: t }); } return fmCache.get(id); };
+  // a kit product keeps its records in pmos/state/initiatives and its PRDs under pmos/ (initiative-description-field: About read none there)
+  const fmOf = (id) => { if (!fmCache.has(id)) { const t = X.text('planning/initiatives/' + id + '.md') ?? X.text('pmos/state/initiatives/' + id + '.md'); fmCache.set(id, t == null ? null : { fm: frontmatter(t), text: t }); } return fmCache.get(id); };
 
   // "usually N days": every record's ladder, and every run of board moves
   const samples = Object.fromEntries(STAGES.map((s) => [s, []]));
@@ -204,8 +205,10 @@ function trail({ root, ids, rows = [], moves = [], now = Date.now(), io } = {})
     const stage = wk ? null : stageKey(row.stage);
     const lane = String(row.lane || fm.lane || 'feature').toLowerCase();
     const evals = evalFiles(id, evalNames);
-    const prdRel = pathOf(fm.prd_path), rubRel = pathOf(fm.rubric_path);
-    const prdText = prdRel ? X.text(prdRel) : null, prdFm = frontmatter(prdText);
+    let prdRel = pathOf(fm.prd_path); const rubRel = pathOf(fm.rubric_path);
+    let prdText = prdRel ? X.text(prdRel) : null;
+    if (prdRel && prdText == null && !prdRel.startsWith('pmos/')) { const k = X.text('pmos/' + prdRel); if (k != null) { prdText = k; prdRel = 'pmos/' + prdRel; } }
+    const prdFm = frontmatter(prdText);
     const briefName = (X.list ? X.list('planning/briefs') : []).find((n) => n.startsWith(id) && n.endsWith('.md'));
     const jv = X.jira ? X.jira(id) : null;
     const tks = jv && jv.ok && Array.isArray(jv.tickets) ? jv.tickets : [];
@@ -276,6 +279,8 @@ function trail({ root, ids, rows = [], moves = [], now = Date.now(), io } = {})
       skipped, parts, next: parts ? (parts.find((p) => !p.done) || {}).name || null : null, you,
       links: { prd: prdRel, prdVersion: prdRel && (typeof prdFm.version === 'string' || typeof prdFm.version === 'number') && String(prdFm.version).trim() ? String(prdFm.version).trim().slice(0, 12) : null,
         rubric: rubRel, evaluation: evals[0] || null, epic: jv && jv.ok && jv.epic && jv.epic.key ? jv.epic.key : null },
+      // the record's own description (initiative-description-field): About shows it before the PRD's paragraph
+      desc: typeof fm.description === 'string' && fm.description.trim() ? fm.description.replace(/\\("|\\)/g, '$1').replace(/\s+/g, ' ').trim().slice(0, 700) : null,
       drafted, gate: jv && jv.ok ? jv.gate || null : null, drift: drift.map((t) => t.key), deps, theme: tkey, tickets,
     };
   }