create-pmos 0.493.0 → 0.495.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-pmos",
-  "version": "0.493.0",
+  "version": "0.495.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,104 @@
     "audit"
   ],
   "pmosChanges": [
+    {
+      "v": "0.495.0",
+      "at": "2026-11-02T23:26:48.050Z",
+      "f": 3,
+      "prs": [
+        {
+          "n": 1164,
+          "t": "Report fixes from the live check of 0.494.0",
+          "s": "Report fixes from the live check of 0.494.0",
+          "k": "fix"
+        },
+        {
+          "n": 1167,
+          "t": "Keep a live New workflow draft on the Workflows list",
+          "s": "Keep a live New workflow draft on the Workflows list",
+          "k": "fix"
+        },
+        {
+          "n": 1166,
+          "t": "Initiative telemetry card starts collapsed (batch 24)",
+          "s": "Initiative telemetry card starts collapsed (batch 24)",
+          "k": "fix"
+        },
+        {
+          "n": 1168,
+          "t": "A sent chat message shows at once",
+          "s": "A sent chat message shows at once",
+          "k": "fix"
+        },
+        {
+          "n": 1169,
+          "t": "A default workflow, set with a star in Settings › Workflows (canvas DfA)",
+          "s": "A default workflow, set with a star in Settings › Workflows (canvas DfA)",
+          "k": "new"
+        }
+      ]
+    },
+    {
+      "v": "0.494.0",
+      "at": "2026-11-02T15:32:51.920Z",
+      "f": 3,
+      "prs": [
+        {
+          "n": 1156,
+          "t": "A report change from the chat edits the existing draft in place",
+          "s": "A report change from the chat edits the existing draft in place",
+          "k": "fix"
+        },
+        {
+          "n": 1150,
+          "t": "A report's chat icon opens its own conversation beside it",
+          "s": "A report's chat icon opens its own conversation beside it",
+          "k": "new"
+        },
+        {
+          "n": 1149,
+          "t": "Product groups use the product name, not the folder name",
+          "s": "Product groups use the product name, not the folder name",
+          "k": "fix"
+        },
+        {
+          "n": 1157,
+          "t": "Weekly impact check as thank-you bubbles, counted by default (batch 23 item 4)",
+          "s": "Weekly impact check as thank-you bubbles, counted by default (batch 23 item 4)",
+          "k": "new"
+        },
+        {
+          "n": 1158,
+          "t": "Grill every initiative with open work, not only late work; Home says how many",
+          "s": "Grill every initiative with open work, not only late work; Home says how many",
+          "k": "fix"
+        },
+        {
+          "n": 1159,
+          "t": "Pages open faster after a break and after a start",
+          "s": "Pages open faster after a break and after a start",
+          "k": "imp"
+        },
+        {
+          "n": 1161,
+          "t": "A report template keeps its look and sections (canvas TplA)",
+          "s": "A report template keeps its look and sections (canvas TplA)",
+          "k": "new"
+        },
+        {
+          "n": 1162,
+          "t": "Finished report slides, the Pyramid deck (canvas RsA)",
+          "s": "Finished report slides, the Pyramid deck (canvas RsA)",
+          "k": "new"
+        },
+        {
+          "n": 1160,
+          "t": "Tighter phone initiative page, one 16 px inset (batch 23 item 5)",
+          "s": "Tighter phone initiative page, one 16 px inset (batch 23 item 5)",
+          "k": "new"
+        }
+      ]
+    },
     {
       "v": "0.493.0",
       "at": "2026-11-02T14:33:09.369Z",
@@ -269,32 +367,6 @@
           "k": "new"
         }
       ]
-    },
-    {
-      "v": "0.475.0",
-      "at": "2026-11-01T06:12:23.972Z",
-      "f": 3,
-      "prs": [
-        {
-          "n": 1110,
-          "t": "Set up a project from the Cozy Home in one guided conversation",
-          "s": "Set up a project from the Cozy Home in one guided conversation",
-          "k": "new"
-        }
-      ]
-    },
-    {
-      "v": "0.474.0",
-      "at": "2026-11-01T01:28:22.776Z",
-      "f": 3,
-      "prs": [
-        {
-          "n": 1129,
-          "t": "A published copy keeps the Tasks section when a stage holds a note",
-          "s": "A published copy keeps the Tasks section when a stage holds a note",
-          "k": "fix"
-        }
-      ]
     }
   ]
 }

package/payload/KIT-VERSION

@@ -1,3 +1,3 @@
-kernel-source: pmos@af2b38f6
+kernel-source: pmos@483e2976
 assembled: 2026-11-02
 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-02T14:33:05Z"}
+generated: {by: process:create-pmos, at: "2026-11-02T23:26:44Z"}
 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-02T14:33:05Z"}
+generated: {by: process:create-pmos, at: "2026-11-02T23:26:44Z"}
 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-02T14:33:05Z"}
+generated: {by: process:create-pmos, at: "2026-11-02T23:26:44Z"}
 status: stable
 ---
 

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

@@ -6,6 +6,7 @@
 const path = require('path');
 const { spawn } = require('child_process');
 const { findBrowser } = require('./lib/find-browser');
+const { openMission } = require('./lib/open-mission');
 const T = require('./test-run').configure({ name: 'briefing-premium-adddoc' });
 const BP = require('./lib/board-premium.js');
 const IP = require('./lib/initiative-premium.js');
@@ -49,7 +50,7 @@ const PAGES = {
 
   const open = async (kind, { w = 1280, h = 900, theme = 'light', custom = [], add = { status: 200, body: { ok: true } } } = {}) => {
     const P = PAGES[kind];
-    const ctx = await browser.newContext({ viewport: { width: w, height: h } });
+    const ctx = await openMission(await browser.newContext({ viewport: { width: w, height: h } }));
     if (kind === 'board') await ctx.addInitScript(() => { try { localStorage.setItem('pmos.premium.openAs', 'popup'); } catch { /* none */ } });
     const page = await ctx.newPage();
     let current = custom, calls = 0, reply = add; const errors = [], posts = [];

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

@@ -16,6 +16,7 @@ const fs = require('fs');
 const path = require('path');
 const { spawn } = require('child_process');
 const { findBrowser } = require('./lib/find-browser');
+const { openMission } = require('./lib/open-mission');
 const T = require('./test-run').configure({ name: 'briefing-premium-board' });
 const BP = require('./lib/board-premium.js');
 const F = require('./fixtures/board-premium-facts.js');
@@ -79,7 +80,7 @@ const IVREAD = () => {
   browser = await chromium.launch({ executablePath: exe });
 
   const open = async ({ w = 1440, h = 900, theme = 'light', model = mk(), answers = null, trail = null, qs = '', slowSheet = 0 } = {}) => {
-    const ctx = await browser.newContext({ viewport: { width: w, height: h } });
+    const ctx = await openMission(await browser.newContext({ viewport: { width: w, height: h } }));
     const page = await ctx.newPage();
     if (slowSheet) await page.route('**/pm/cozy-panels.css', async (r) => { await new Promise((ok) => setTimeout(ok, slowSheet)); r.continue(); });   // the panels sheet lands after the first Viewer
     let current = model, calls = 0; const errors = [], posts = []; let answer = { status: 200, body: { ok: true } }; let thread = { ok: true, turns: [], working: false };
@@ -417,13 +418,13 @@ const IVREAD = () => {
 
   /* B2 reading and failure */
   {
-    const ctx = await browser.newContext({ viewport: { width: 1280, height: 900 } }), pg = await ctx.newPage(); let calls = 0;
+    const ctx = await openMission(await browser.newContext({ viewport: { width: 1280, height: 900 } })), pg = await ctx.newPage(); let calls = 0;
     await pg.route('**/api/board-premium*', (r) => { calls++; if (calls < 2) return r.fulfill({ status: 202, contentType: 'application/json', body: JSON.stringify({ ok: true, state: 'reading' }) }); return r.fulfill({ contentType: 'application/json', body: JSON.stringify({ ok: true, state: 'ready', model: mk(), as_of: Date.now() }) }); });
     await pg.goto(BASE + '/premium-board.html');
     ok('B2 while the board is read the page says so, with the seconds, and shows no row instead of a guess', await until(() => pg.evaluate(() => /Reading the board · \d+ s so far/.test(document.querySelector('#snap').textContent) && document.querySelectorAll('#ibBody .ini2').length === 0 && /shows nothing until it has read/.test(document.querySelector('#ibBody').textContent)), 4000));
     ok('B2 it asks again and draws when the answer is ready', await until(() => pg.evaluate(() => document.querySelectorAll('#ibBody .ini2').length === 7 && /^Real data/.test(document.querySelector('#snap').textContent)), 9000));
     await ctx.close();
-    const c2 = await browser.newContext({ viewport: { width: 1280, height: 900 } }), p2 = await c2.newPage();
+    const c2 = await openMission(await browser.newContext({ viewport: { width: 1280, height: 900 } })), p2 = await c2.newPage();
     await p2.route('**/api/board-premium*', (r) => r.fulfill({ status: 500, contentType: 'application/json', body: JSON.stringify({ ok: false, state: 'error', error: 'the board could not be read' }) }));
     await p2.goto(BASE + '/premium-board.html');
     ok('B2 a failed read says why and draws nothing', await until(() => p2.evaluate(() => /The reason: the board could not be read/.test((document.querySelector('#ibBody .bd-msg') || {}).textContent || '') && document.querySelectorAll('#ibBody .ini2').length === 0), 4000));
@@ -567,7 +568,7 @@ const IVREAD = () => {
     ok('E3 the real model has the eight steps and a track on every row', !!m && m.steps.length === 8 && m.initiatives.list.rows.every((r) => r.track && typeof r.track.k === 'number'));
     const post = await fetch(BASE + '/api/board-premium', { method: 'POST', headers: await T.pressHeaders(BASE), body: '{}' }).then((r) => r.status);
     ok('E4 the model route is read-only', post === 405, String(post));
-    const ctx = await browser.newContext({ viewport: { width: 1280, height: 900 } }), pg = await ctx.newPage(), errs = [];
+    const ctx = await openMission(await browser.newContext({ viewport: { width: 1280, height: 900 } })), pg = await ctx.newPage(), errs = [];
     pg.on('pageerror', (e) => errs.push(String(e)));
     await pg.goto(BASE + '/premium-board.html');
     ok('E5 the real page draws this repository\'s board and its count agrees with the route', await until(() => pg.evaluate((n) => document.querySelectorAll('#ibBody .ini2').length > 0 && document.querySelector('#nIni').textContent === n, String(m.initiatives.open || m.initiatives.list.rows.length)), 30000));

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

@@ -13,6 +13,7 @@
 const path = require('path');
 const { spawn } = require('child_process');
 const { findBrowser } = require('./lib/find-browser');
+const { openMission } = require('./lib/open-mission');
 const T = require('./test-run').configure({ name: 'briefing-premium-initiative' });
 const IP = require('./lib/initiative-premium.js');
 const F = require('./fixtures/initiative-premium-facts.js');
@@ -52,7 +53,7 @@ const WRITES = /^\/api\/(?:boards\/(?:move|tasks\/(?:add|state))|lifecycle|core-
   browser = await chromium.launch({ executablePath: exe });
 
   const open = async ({ w = 1280, h = 900, theme = 'light', model = mk(), answers = null, url = '/premium.html?ini=self-serve-v2&ws=w1&board=w1' } = {}) => {
-    const ctx = await browser.newContext({ viewport: { width: w, height: h } });
+    const ctx = await openMission(await browser.newContext({ viewport: { width: w, height: h } }));
     const page = await ctx.newPage();
     let current = model, calls = 0, answer = { status: 200, body: { ok: true } };
     const errors = [], posts = [];
@@ -260,12 +261,13 @@ const WRITES = /^\/api\/(?:boards\/(?:move|tasks\/(?:add|state))|lifecycle|core-
       const cs = (s) => { const e = document.querySelector(s); return e ? getComputedStyle(e) : null; };
       const fab = document.querySelector('#czFab'), fr = fab && fab.getBoundingClientRect();
       const c = document.querySelector('#czViewer .iv-tel').getBoundingClientRect();
-      return { font: cs('body').fontFamily, cta: (cs('#czViewer .iv-go') || {}).backgroundColor, ctaAlt: !document.querySelector('#czViewer .iv-go'), solid: tok('--cz-solid'), blue: tok('--cz-blue'), well: tok('--cz-well'), card: tok('--cz-card'), box: cs('#czViewer .iv-mc').backgroundColor, rad: parseFloat(cs('#czViewer .iv-mc').borderTopLeftRadius), fab: fr ? [Math.round(fr.width), Math.round(fr.height)] : null, over: document.documentElement.scrollWidth - innerWidth, cardW: Math.round(c.width) };
+      return { font: cs('body').fontFamily, cta: (cs('#czViewer .iv-go') || {}).backgroundColor, ctaAlt: !document.querySelector('#czViewer .iv-go'), solid: tok('--cz-solid'), blue: tok('--cz-blue'), well: tok('--cz-well'), card: tok('--cz-card'), box: cs('#czViewer .iv-mc').backgroundColor, rad: parseFloat(cs(innerWidth <= 760 ? '#czViewer .iv-tel' : '#czViewer .iv-mc').borderTopLeftRadius), fab: fr ? [Math.round(fr.width), Math.round(fr.height)] : null, over: document.documentElement.scrollWidth - innerWidth, cardW: Math.round(c.width) };
     });
     const d = [];
     if (!/^Nunito/.test(g.font)) d.push('font ' + g.font);
     if (!g.ctaAlt && ![g.solid, g.blue].includes(g.cta)) d.push('cta ' + g.cta + ' want ' + g.solid + ' or ' + g.blue);
     if (![g.well, g.card].includes(g.box) && !/rgba/.test(g.box)) d.push('card box ' + g.box);
+    // a phone has no wrapper card (batch 23 item 5, canvas PmA): the mission is the first card there
     if (g.rad < 12) d.push('card radius ' + g.rad);
     // on a phone the initiative's page is the Viewer, full screen over the list: the floating menu waits under it (HbCPhone)
     if (w > 760 && (!g.fab || g.fab[0] !== 56 || g.fab[1] !== 56)) d.push('fab ' + JSON.stringify(g.fab));

package/workspace/changelog.json

@@ -1,4 +1,102 @@
 [
+ {
+  "v": "0.495.0",
+  "at": "2026-11-02T23:26:48.050Z",
+  "f": 3,
+  "prs": [
+   {
+    "n": 1164,
+    "t": "Report fixes from the live check of 0.494.0",
+    "s": "Report fixes from the live check of 0.494.0",
+    "k": "fix"
+   },
+   {
+    "n": 1167,
+    "t": "Keep a live New workflow draft on the Workflows list",
+    "s": "Keep a live New workflow draft on the Workflows list",
+    "k": "fix"
+   },
+   {
+    "n": 1166,
+    "t": "Initiative telemetry card starts collapsed (batch 24)",
+    "s": "Initiative telemetry card starts collapsed (batch 24)",
+    "k": "fix"
+   },
+   {
+    "n": 1168,
+    "t": "A sent chat message shows at once",
+    "s": "A sent chat message shows at once",
+    "k": "fix"
+   },
+   {
+    "n": 1169,
+    "t": "A default workflow, set with a star in Settings › Workflows (canvas DfA)",
+    "s": "A default workflow, set with a star in Settings › Workflows (canvas DfA)",
+    "k": "new"
+   }
+  ]
+ },
+ {
+  "v": "0.494.0",
+  "at": "2026-11-02T15:32:51.920Z",
+  "f": 3,
+  "prs": [
+   {
+    "n": 1156,
+    "t": "A report change from the chat edits the existing draft in place",
+    "s": "A report change from the chat edits the existing draft in place",
+    "k": "fix"
+   },
+   {
+    "n": 1150,
+    "t": "A report's chat icon opens its own conversation beside it",
+    "s": "A report's chat icon opens its own conversation beside it",
+    "k": "new"
+   },
+   {
+    "n": 1149,
+    "t": "Product groups use the product name, not the folder name",
+    "s": "Product groups use the product name, not the folder name",
+    "k": "fix"
+   },
+   {
+    "n": 1157,
+    "t": "Weekly impact check as thank-you bubbles, counted by default (batch 23 item 4)",
+    "s": "Weekly impact check as thank-you bubbles, counted by default (batch 23 item 4)",
+    "k": "new"
+   },
+   {
+    "n": 1158,
+    "t": "Grill every initiative with open work, not only late work; Home says how many",
+    "s": "Grill every initiative with open work, not only late work; Home says how many",
+    "k": "fix"
+   },
+   {
+    "n": 1159,
+    "t": "Pages open faster after a break and after a start",
+    "s": "Pages open faster after a break and after a start",
+    "k": "imp"
+   },
+   {
+    "n": 1161,
+    "t": "A report template keeps its look and sections (canvas TplA)",
+    "s": "A report template keeps its look and sections (canvas TplA)",
+    "k": "new"
+   },
+   {
+    "n": 1162,
+    "t": "Finished report slides, the Pyramid deck (canvas RsA)",
+    "s": "Finished report slides, the Pyramid deck (canvas RsA)",
+    "k": "new"
+   },
+   {
+    "n": 1160,
+    "t": "Tighter phone initiative page, one 16 px inset (batch 23 item 5)",
+    "s": "Tighter phone initiative page, one 16 px inset (batch 23 item 5)",
+    "k": "new"
+   }
+  ]
+ },
  {
   "v": "0.493.0",
   "at": "2026-11-02T14:33:09.369Z",

package/workspace/guide/briefing-premium.md

@@ -2,7 +2,7 @@
 type: Guide
 title: "The premium Briefing (/premium.html)"
 description: "The Briefing page at /premium.html: the hero sentence, What you need to do, Today, the dock, and what each one reads from the repository."
-timestamp: 2026-11-01
+timestamp: 2026-11-02
 ---
 
 # The premium Briefing
@@ -435,6 +435,7 @@ Every popup has this chat, including the ones that have no row of their own: a t
 
 - **Your first message** in a dialog starts one session for that row, the page or the initiative, in its repository. Claude gets the row as the page shows it: the title, what the page says, the facts and the files to start from. Then it gets your words.
 - **The message box** takes several lines. **Enter** sends; **Shift+Enter** starts a new line. The box grows as you type, up to about eight lines, and then scrolls. The send button stays at its foot, also with a phone keyboard open.
+- **Your message shows at once.** When you send, the box empties and your message appears in the chat straight away, a little lighter with **Sending…** until PMOS takes it, then with **You · HH:MM**. If the message could not be sent, it leaves the chat and your words go back in the box, so you can send them again. This is the same in every chat: Home, an initiative, a new workflow, and the Board and Intelligence chat.
 - **Later messages** in the same dialog go to the same session. Write `/compact`, `/clear` or any other slash command, and Claude Code runs it.
 - **What it may do** is set by your own Claude Code settings. Claude can change files and run commands. When your settings say to ask first, the question shows in the panel with its options; press one to answer.
 - **Claude's questions** show as a card in the conversation. Claude Code's question picker cannot show in the panel, so the session does not open it: the card shows each question with its options as buttons. Press an option to answer a single question. When Claude asks several questions, or a question takes more than one answer, press the options and then **Send answers**. You can also write your own answer in the box. A session that started before this change still opens the picker: end it in the session list, and your next message resumes the same conversation without it.
@@ -460,7 +461,9 @@ Any chat can become a report. There is no button for it: say it in the chat, for
 - **A new report** asks a few questions first, and Claude's picks are filled in: **Format**, **Readers**, **Goes out** (**Once** or **Repeats**, with how often, the day and the time), **Look** (the standard PMOS look, 16:9 slides) and **Sources**. The chip under Claude's answer says **Answer a few questions, then Draft it**. Change any answer, then press **Draft it**. Nothing goes out. That press records the report and its first template (T1), and the report drafts in its own session, not in your chat. While it drafts, the tab says so. If the session ends with no draft, **Draft it again** starts it again.
 - **The report's current state.** When a report is set up, the chip under Claude's answer says **Open the report**, and the tab opens its latest draft in the reader. Under a draft that is not issued, Claude's review reads it as your readers would and lists what to fix, in the ✦ pattern: **Do it** passes one fix to the report's own session, **Do all** passes them all, and **Not now** hides one. The checks that found nothing are named under it. There is no score.
 - **A change from the chat.** Ask for a change to the draft in the chat, for example "use 30 Jun on both slides". The chip says **Change to the draft** and passes it to the report's own session. Your chat does not draft the report.
+- **Talk to Claude about the report.** The chat icon in the reader's header, beside the template icon, opens the report's own conversation in Home's chat, with the report beside it (on a phone the chat takes the page). Claude knows which report and draft it is. Say what to change, then press the chip to pass it to the report's session; the draft beside the chat changes. From another page the icon takes you to Home.
 - **Template versions.** The template icon in the reader's header opens the questions with the current answers. A changed answer is marked and said in words, for example "Format: Slides → Document". **Make a different template** saves it as the next version (T2, T3, …), and **Keep the current template** leaves it. **Template history** lists each version with the cycles issued under it, and **Go back** makes an earlier one current. Nothing is deleted. **Sections, look and cycles** opens the structure, the design and the cycles below.
+- **A template keeps its sections and look.** Each version also holds the report's **Sections** (shown as chips, in order) and its **Look** (a small title slide, its name and the sample it follows). To change them, ask in the chat. Sections you name, or a look Claude made from your words, wait in the template as one ✦ **Make T4**, with the change in words (for example "Sections: + Customers" and "Look: D1 → D2") and a **changed** tag on each row. Press ✕ to drop it or ✓ to make it. Nothing is saved before ✓, and the open draft stays as it is. Each earlier version says what **Go back** restores: format, readers, schedule, sections and look. Cycles already made keep the look they were made with. Saving sections or a look in **Sections, look and cycles** also makes a new version.
 - **A goal with a report in it.** When a goal names a report, that point counts only when you issue the report. If only report points are open, the goal waits for you to issue it.
 - **Your own sections.** Name them in the chat, for example "use these sections: Decision question; Current position; Options and recommendation; Open items; Sources". The tab shows them as the slides. ✓ saves them as the report's structure (S1), and the first draft follows them. Your first section is the report's lead, the one before Sources holds the asks to the readers, and Sources is always last. If you describe a change without a list, **Structure and look** shows the change: the first draft uses the seven standard sections, Claude starts the change right after ✓, and **Use this** keeps it. When you press **Use this**, Claude writes the draft again with the new sections.
 - **A look to follow.** Say how the report should look, or name a file for it to follow, such as your draft deck (a PDF, PowerPoint, Word file or picture). **Structure and look** shows **Look** with the file's name. After ✓, Claude adds the file as the look's sample and makes the look from it.

package/workspace/guide/claude-proposes.md

@@ -60,13 +60,13 @@ Claude also tests an initiative without being asked. There is no Grill button an
 - before it leaves a stage (the stage has one open task or none left),
 - when its forecast turns at risk or will miss,
 - when its scope or dates move a lot (30% more or fewer tasks, or the end moves 14 days or more),
-- once a month, when it is running and has late work.
+- once a month, every running initiative that has open tasks: the ones with late work first, then the ones it grilled longest ago. Each one at most once in 30 days, and only while the monthly credit lasts.
 
 You can also start one any time: in the initiative's chat, write "grill this" (or "grill it"). The run starts at once in the background, and the chat says so in one line. If it cannot start, for example because another grill is running or this month's credit is spent, the chat says why. The findings arrive under the ✦ as for the other runs.
 
 Each finding is a proposal in the group "Claude grilled it", under the same ✦. Each row shows the mark and the name of the angle that found it: Premortem, Red team, Voices, Reframe, Scope or What-if. Voices are simulated from your stored research and meeting notes, only with 3 sources or more, and carry the tag "Simulated, not evidence". A What-if carries "Simulated, not the plan". Each finding ends with one next step. ✓ adds that step as a task. ✎ lets you write the step in your own words first; ✓ then adds your words. ✕ drops the finding. A finding never rides on the header's ✓. Above the findings, one quiet line names the angles Claude chose, when and why it ran, and what the run cost. Three findings show at a time; "+N smaller findings" and its ⋯ show the rest. On a phone the findings are cards side by side: swipe for the next. With no findings, nothing shows.
 
-When Claude grilled an initiative this week and left findings, Home says so in one line under "Good morning", and its ✦ opens the findings. When a key result will miss its goal, or drifted to at risk, Intelligence's ✦ line names it and the initiative Claude grilled for it; its ✦ opens those findings.
+When Claude grilled an initiative this week and left findings, Home says so in one line under "Good morning", and its ✦ opens the findings. When it grilled more than one, the line names the newest and says how many more, for example "I grilled Inline login and 5 more this week: 21 findings." The others' findings are under each initiative's own ✦. When a key result will miss its goal, or drifted to at risk, Intelligence's ✦ line names it and the initiative Claude grilled for it; its ✦ opens those findings.
 
 Every run counts against a monthly credit cap. A run starts only when the cap holds its whole budget, and it stops at that budget, so the month never goes past the cap. At the cap Claude pauses until the next month.
 

package/workspace/guide/data-freshness.md

@@ -1,7 +1,7 @@
 ---
 type: Guide
 title: "Data freshness: how the workspace keeps up to date, and how old each source is"
-timestamp: 2026-10-28
+timestamp: 2026-11-02
 ---
 
 # Data freshness
@@ -109,6 +109,8 @@ A refresh waits for the sources it uses. The briefing waits for work assigned to
 - A schedule you never changed moves to the new default once (quick reads every 30 or 60 minutes in working hours). A schedule you picked stays as it is.
 - **One server runs the schedules.** When several PMOS servers run on one computer (for example an npm install and a checkout), only one of them runs the schedules and starts background runs; the others serve pages only. If that server stops, another one takes over within 3 minutes. A refresh you press runs on the server where you press it.
 - **Quiet start**: a server starts no background run in its first 5 minutes, so the first pages load quickly. A missed refresh catches up after that.
+- **Warm start**: 5 seconds after PMOS starts, it reads what Home and the Board show once, so your first page opens as fast as later ones. This read writes nothing you would see as read or seen. `PMOS_WARM=off` turns it off.
+- **Fresh answers, asked once**: when two parts of a page ask for the same thing at the same moment, the server is asked once and both get the same answer. Nothing is kept after it arrives, so the next look always reads again.
 
 ### The refresh log
 

package/workspace/guide/initiatives-screen.md

@@ -19,7 +19,9 @@ An open initiative uses one column. At its top is the **mission**: one panel wit
 - **To finish this stage.** It shows how many tasks of the stage are done, the stage's open milestone tasks with their dates, and the move to the next stage. The move is blue only when every task of the stage is done and nothing waits on you. At other times it is quiet. Under the rows are the owner, the stakeholders, the workflow and the program. On a wide screen this part stands beside the telemetry card.
 - **About.** It has the description and the success measure. The description is the first paragraph of the PRD's Problem section. Press **Show more** to read all of it, or **Open the PRD** to open the file. The success measure is the one Claude drafts. A proposal opens About until you press its check mark. A kept measure shows each row with its now value and its target. When there is no description or no measure, About gives you a link that asks Claude in Home to write it.
 
-Press the arrow on the telemetry card to hide all three parts. A banner stays: the stage, the dates, the days left, the count of tasks done, the success measure and the move to the next stage. Press the arrow again to show the telemetry card first. **To finish this stage** and **About** each have their own arrow, and they stay as you left them when you hide and show the mission. The workspace keeps these choices for each initiative in this browser. On a phone, the first screen shows **To finish this stage** and **About** closed.
+When you open an initiative, the three parts are hidden at first and only a banner shows: the stage, the dates, the days left, the count of tasks done, the success measure and the move to the next stage. Press the arrow on the banner to show the telemetry card first. Press the arrow on the telemetry card to hide all three parts again. **To finish this stage** and **About** each have their own arrow, and they stay as you left them when you hide and show the mission. The workspace keeps these choices for each initiative in this browser. On a phone, the first screen shows **To finish this stage** and **About** closed.
+
+On a phone, the page uses one 16 px margin and has no grey panel around the mission. The telemetry card is shorter: the stage name is on the first line, and the dates, **Time left** and **Elapsed** are on the next line, so the picture does not repeat the Today label. **To finish this stage** and **About** are one white card. The first row shows the next stage and the count of tasks done. Its round arrow opens the move sheet. The second row shows the owner, the stakeholders, the workflow and the program. The third row is **About**. In Tasks, the rows start near the card's edge, and the late and open counts of a stage are on the same line as its dates.
 
 Tasks has no **Full width** icon: use the split panel to make the Viewer wider. On a phone, Tasks is a list only. The workspace keeps a Timeline or Kanban view that you chose on a larger screen, and shows it again there.
 

package/workspace/guide/report-slides.md

@@ -2,7 +2,7 @@
 type: Guide
 title: "Report slides: present and print a report"
 description: "How the Reports page shows a report as the PM-OS biweekly slides, how to present and print them, and how your notes become the words on the slides."
-timestamp: 2026-10-13
+timestamp: 2026-11-02
 ---
 
 # Report slides
@@ -27,4 +27,17 @@ The type is Launch, Improvement, Fix, Security, Deprecation or Beta. To give an
 
 A draft from before the slides has no slides block. Press **Redraft** to add it. Your notes stay as you wrote them.
 
+## The finished slides in the report viewer
+
+When you open a drafted report in the viewer, the **Slides** view shows the finished deck. The answer comes first, and the title of each slide is a finding. Read only the titles and you have the story:
+
+1. **Title**: the answer. This is the first sentence of your `report.headline` note when you wrote one, so write the answer first. A long sentence is cut so that it fits. If there is no note, PMOS writes a sentence that says which initiatives are off plan.
+2. **The answer**: one sentence, then the rest of the first paragraph of your headline note, and up to three supports, off-plan initiatives first. Your ask is beside them.
+3. **Scorecard**: the title is the verdict on one line, for example "3 of 12 off plan" with up to three names. Each initiative's stage, its status (a shape and a colour), done of total with the change since the last report, and the KR value against its target. The gap is the value minus the target. Only a row that is off plan (at risk or off track) has a comment. A row that is on track has none.
+4. **Timeline**: the dated work, the due dates and any overdue item, for up to six initiatives. The title compares two due dates of the rows on the slide.
+5. **Needs your call**: only when the report has an audience and the `report.asks` note has words. Write each option on its own line that starts with "- ". Write "by" and a date in the note to show a deadline. PMOS adds nothing that you did not write.
+6. **Sources**: the sources that PMOS read, and "What we don't know yet" for each source that it could not read, with the reason. PMOS reads these from the draft's "Sources reached and not reached" section, from the cycle's data file and from the "Sources:" paragraph of the notes.
+
+Each slide names its source and shows its page number. **Download › PDF** opens the print window with the same slides, one on each page: choose **Save as PDF** there. There is no PDF file to download from PMOS itself, because the browser makes the PDF. **Download › PPTX** gives the same slides as a PowerPoint file. The slides use the report's saved look: its font and its own title or main colour. If the report has no saved look, they use the standard PMOS look. PMOS does not draw KR trend lines, last-quarter bars or forecast ranges, because the draft does not have that data yet.
+
 A report that you set up can have its own design, as a deck or an interactive document, with a presenter view, speaker notes and notes on the slide. See [Design how a report looks](report-design.md).

package/workspace/guide/reports.md

@@ -47,6 +47,8 @@ The Reports page shows a report as slides. [Report slides](report-slides.md) tel
 
 When you draft a slot again, every note stays as you wrote it, next to its initiative. The order of the blocks can change. A note for an initiative that is no longer in the window moves to "Notes kept from an earlier draft".
 
+When you ask Claude in a chat to change a report, the change goes to the latest draft of that report, in its own file. The report's session edits only the notes that the change is about, even when they have text, and keeps every other note and every number as it is. It keeps each caveat (a sentence that says something is provisional, not decided or unverified), also when you ask for shorter text, and it tells you which notes it changed and quotes any sentence it removed. It drafts the same slot again only when you ask for fresh numbers. It never drafts a new slot for today. A change to a number, a date, a section or a slide is not made in the draft: the session tells you which setting to change in the template or the studio. If the latest cycle is issued, it is frozen, and the change is not passed on.
+
 ## The commands
 
 `pmos report draft <cadence> [<slot>]` writes the draft to `planning/reports/<cadence>/<slot>.md`. The slot is a date, YYYY-MM-DD. If you do not give a slot, the slot is today. If a draft for the slot exists, the command stops and writes nothing. To draft the slot again and keep every note, add `--redraft`. To fix the clock, add `--now <time>`: two drafts with the same inputs and the same `--now` are the same, byte for byte.

package/workspace/guide/workflows.md

@@ -1,8 +1,8 @@
 ---
 type: Guide
 title: "Workflows: the stages each kind of initiative goes through"
-description: "Settings › Workflows: the workflow list, one numbered list of stages across To do, In progress and Done, the stage panel, Only when conditions, removing a stage in use, New workflow in the chat, moving initiatives to a simpler workflow, and the pmos workflow commands."
-timestamp: 2026-11-01
+description: "Settings › Workflows: the workflow list, the default workflow (the star), one numbered list of stages across To do, In progress and Done, the stage panel, Only when conditions, removing a stage in use, New workflow in the chat, moving initiatives to a simpler workflow, and the pmos workflow commands."
+timestamp: 2026-11-02
 ---
 
 # Workflows
@@ -14,11 +14,21 @@ Open it from **Menu › Settings › Workflows**. The address is `/premium-workf
 ## The page
 
 - **The list** on the left shows each workflow and how many initiatives use it. **+** starts a new workflow. An archived workflow shows last, under **Archived**.
+- **The star** on a row marks the **default workflow**: the workflow a new initiative starts on. Point at a row, or tab to it, to see its star, and press it to make that workflow the default. The toast has **Undo**. Product feature is the default until you pick another, and it can be the default again.
 - **The workflow** is one numbered list of stages, in three columns: **To do**, **In progress** and **Done**. Drag a stage to change its place or its column. **Add a stage** adds one at the end of that column. The dashed **Won't do · Archived** column is in every workflow: any initiative can go there from any stage, and come back to Triage.
 - **Triage** is always the first stage, in To do.
 - Tap the name of the workflow to rename it. **⋯** has **Copy** and **Archive**. You cannot archive a workflow that initiatives use.
 - **Product feature** cannot change. **Copy it** to make a workflow of your own from it. A stage of Product feature has **Copy it** too: the copy opens on that stage.
 
+## The default workflow
+
+A new initiative starts in Triage on the default workflow. It does not matter how you add it: from Triage, from a Horizon scan proposal, from the initiative form, or with `pmos initiative new`. PMOS still reads the initiative's BRD and proposes a switch when the work reads like another workflow. You decide.
+
+- The default is per workspace. A workspace that never set a default uses the one you set in Settings.
+- Changing the default does not move initiatives that already exist.
+- If you archive the default workflow, Product feature is the default again. Restoring the workflow does not make it the default again: press its star.
+- The **In:** chip in the chat names where a message goes. It does not show a workflow.
+
 ## A stage
 
 Tap a stage to open it in the side panel. Tap its name at the top to rename it. The panel has:
@@ -47,6 +57,8 @@ Press **+**. The chat opens, scoped **New workflow**. Tell Claude how the work g
 - **Edit by hand** opens the draft on the page, so you can change it before you create it.
 - You can also start **blank** (only Triage) or **from a copy** of a workflow.
 
+You can open another workflow while a draft is going. The draft keeps its row at the end of the list, marked **draft**, until you create it. Press that row to go back to the chat and the draft beside it. In the chat list on Home, the same chat shows **In: New workflow**.
+
 ## Move initiatives to a simpler workflow
 
 To use fewer stages, copy Product feature and make the copy simpler. For example, use Discovery, Implementation and Evaluation.
@@ -62,7 +74,7 @@ To use fewer stages, copy Product feature and make the copy simpler. For example
 
 An agent writes a draft or a reading with these commands, and moves an initiative along its workflow when you ask. It never saves, copies or archives a workflow: those are your presses on the page.
 
-- `pmos workflow list` names the workflows of this repository.
+- `pmos workflow list` names the workflows of this repository and marks the default one.
 - `pmos workflow show <id>` shows one workflow, its stages numbered.
 - `pmos workflow draft --file <path>` writes the draft that the New workflow chat shows. `--note` adds a line.
 - `pmos workflow show-draft` shows the draft that is open.

package/workspace/guide/your-impact.md

@@ -2,7 +2,7 @@
 type: Guide
 title: "Your impact"
 description: "What Your impact is, what counts and what never counts, the weekly check in Home's chat, the switch in Settings, and the pmos impact commands."
-timestamp: 2026-10-28
+timestamp: 2026-11-02
 ---
 
 # Your impact
@@ -19,15 +19,14 @@ There are no numbers. You see no points, scores, counts, streaks, levels or rank
 
 ## The weekly check
 
-Once a day, Claude reads your sources and files what it found. After the week ends, Claude lists that week's items in Home's chat and asks whether each one is real:
+Once a day, Claude reads your sources and files what it found. After the week ends, Claude shows that week's items in Home's chat as thank-you notes: the words in bold, who and what under them, and the source link. They already count. You do not have to do anything.
 
-- ✓ keeps one item. Only a kept item counts.
-- ✕ drops it. Claude does not file anything like it again.
-- ✓✓ keeps every item that is not checked yet.
+- If an item is not right, press ⋯ on its row, then **Not right, drop it**. A dropped item does not count, and Claude does not file it again.
+- **Undo** brings a dropped item back.
 
-Each row has its source, so you can open the message or the ticket before you choose.
+You can drop items until the next week ends. After that, every item you did not drop counts as real.
 
-Adler's sprout and your impact log stay hidden until two weekly checks show that at least 9 of 10 items are real. Then Adler's sprout grows a leaf for each week's kept items, and the log in the Viewer shows your weeks, newest first. A quiet week says "A quiet week". Nothing wilts and nothing resets.
+Adler's sprout and your impact log stay hidden until two weekly checks show that at least 9 of 10 items are real. A week counts toward this only if Claude showed you its check. Then Adler's sprout grows a leaf for each week's items, and the log in the Viewer shows your weeks, newest first. A quiet week says "A quiet week". Nothing wilts and nothing resets.
 
 ## Where you see it
 

package/workspace/ini-workflow-test.js

@@ -10,6 +10,7 @@ const fs = require('fs');
 const path = require('path');
 const { spawn } = require('child_process');
 const { findBrowser } = require('./lib/find-browser');
+const { openMission } = require('./lib/open-mission');
 const T = require('./test-run').configure({ name: 'ini-workflow' });
 const IP = require('./lib/initiative-premium.js');
 const F = require('./fixtures/initiative-premium-facts.js');
@@ -71,7 +72,7 @@ const BRIEF = BRP.build(BRF.facts());
   const shot = async (p, name) => { if (SHOTS) await p.screenshot({ path: path.join(SHOTS, name + '.png') }); };
 
   const open = async ({ w = 1440, h = 900, theme = 'light', B = board('triage', { pmos: true }), fresh = true } = {}) => {
-    const ctx = await browser.newContext({ viewport: { width: w, height: h } });
+    const ctx = await openMission(await browser.newContext({ viewport: { width: w, height: h } }));
     const page = await ctx.newPage();
     const S = { B };
     const errors = [], posts = [];