pmx-canvas 0.10.0 → 0.11.0

package/docs/design/Chrome.dc.html

@@ -13,7 +13,7 @@
 body{margin:0}
 </style>
 </helmet>
-<div style="width: 1440px; height: 1000px; box-sizing: border-box; padding: 40px 48px; background: #081524; color: #e6eef7; font-family: 'IBM Plex Sans', system-ui, sans-serif; font-size: 13px; line-height: 1.5; display: grid; grid-template-columns: 500px repeat(2, minmax(0, 1fr)); gap: 40px">
+<div style="width: 1440px; height: 1360px; box-sizing: border-box; padding: 40px 48px; background: #081524; color: #e6eef7; font-family: 'IBM Plex Sans', system-ui, sans-serif; font-size: 13px; line-height: 1.5; display: grid; grid-template-columns: 500px repeat(2, minmax(0, 1fr)); gap: 40px">
 
 <section style="display: flex; flex-direction: column; gap: 14px">
 <div><h2 style="margin: 0; font-size: 15px; font-weight: 600">7 · Tool rail in a 690px-tall window</h2><p style="margin: 2px 0 0; font-size: 12px; color: #8ea3bd">20 buttons need 850px. Settings-type tools move into one menu.</p></div>
@@ -62,7 +62,7 @@ body{margin:0}
 </section>
 
 <section style="display: flex; flex-direction: column; gap: 14px">
-<div><h2 style="margin: 0; font-size: 15px; font-weight: 600">8 · Node header</h2><p style="margin: 2px 0 0; font-size: 12px; color: #8ea3bd">Expand and the context pin always show; ⋯ on hover opens the existing node menu (now with Open in new tab), and Set as README stays in the markdown footer.</p></div>
+<div><h2 style="margin: 0; font-size: 15px; font-weight: 600">8 · Node header</h2><p style="margin: 2px 0 0; font-size: 12px; color: #8ea3bd">Expand and the context pin always show; ⋯ on hover or keyboard focus opens the node menu. Set as README lives here, becoming Remove as README on the current README. Edit stays visible below Markdown.</p></div>
 
 <span style="font-size: 11px; font-weight: 500; letter-spacing: 0.06em; text-transform: uppercase; color: #6b7d94">Today</span>
 <div style="border-radius: 12px 12px 8px 8px; border: 1px solid #1b2c44; background: #0f1d31; box-shadow: 0 0 0 1px rgba(244,197,66,0.3), 0 8px 24px rgba(244,197,66,0.1); overflow: hidden">
@@ -78,7 +78,8 @@ body{margin:0}
 <div style="border-radius: 10px; border: 1px solid #1b2c44; background: #0f1d31; box-shadow: 0 1px 2px rgba(0,0,0,0.4), 0 6px 20px rgba(0,0,0,0.24); overflow: hidden">
 <div style="display: flex; align-items: center; gap: 8px; height: 36px; padding: 0 8px 0 12px; border-bottom: 1px solid #1b2c44">
 <svg width="16" height="16" viewBox="0 0 24 24" style="color: #8ea3bd; fill: none; stroke: currentColor; stroke-width: 1.6; stroke-linecap: round; stroke-linejoin: round"><path d="M6 5h12a2 2 0 0 1 2 2v10a2 2 0 0 1-2 2H6a2 2 0 0 1-2-2V7a2 2 0 0 1 2-2zM8 10h8M8 14h5"></path></svg>
-<span style="flex: 1; font-size: 12px; font-weight: 600">PMX Canvas — guided tour</span>
+<span style="flex: 1; min-width: 0; overflow: hidden; white-space: nowrap; text-overflow: ellipsis; font-size: 12px; font-weight: 600">PMX Canvas — guided tour</span>
+<span style="flex-shrink: 0; font-size: 11px; color: #8ea3bd">README</span>
 <button aria-label="Expand (Enter)" style="width: 22px; height: 22px; border: 0; border-radius: 6px; padding: 0; background: transparent; color: #b9c6d6; display: flex; align-items: center; justify-content: center; flex-shrink: 0"><svg width="13" height="13" viewBox="0 0 24 24" style="fill: none; stroke: currentColor; stroke-width: 2; stroke-linecap: round; stroke-linejoin: round"><path d="M14 4h6v6M20 4l-7 7M10 20H4v-6M4 20l7-7"></path></svg></button>
 <button aria-label="Add to context (P)" style="width: 18px; height: 18px; box-sizing: border-box; border: 1.5px solid #6b7d94; border-radius: 999px; padding: 0; background: transparent; color: #b9c6d6; display: flex; align-items: center; justify-content: center; flex-shrink: 0"><svg width="10" height="10" viewBox="0 0 24 24" style="fill: none; stroke: currentColor; stroke-width: 2.4; stroke-linecap: round; stroke-linejoin: round"><path d="M9 4h6l-.8 5.5 2.8 3H7l2.8-3zM12 12.5V20"></path></svg></button>
 <!-- Reserve the hover-action slots: revealing More/Close must not move the pin. -->
@@ -111,7 +112,8 @@ body{margin:0}
 <div style="height: 236px; display: flex; flex-direction: column; border: 1px solid #1b2c44; border-radius: 10px; overflow: hidden; background: #0f1d31">
 <div style="flex-shrink: 0; height: 36px; display: flex; align-items: center; padding: 0 12px; border-bottom: 1px solid #1b2c44; font-size: 12px; font-weight: 600">Research index</div>
 <div style="flex: 1; min-height: 0; display: flex; flex-direction: column">
-<div style="flex: 1; min-height: 0; padding: 10px 12px; overflow: auto; font-size: 13px; color: #b9c6d6">Read the source, then follow <a href="#reference-footer" style="color: #e6eef7">the evidence</a>.<div style="margin-top: 20px; font-size: 12px; color: #8ea3bd">Set as README <span style="float: right">Edit</span></div></div>
+<div style="flex: 1; min-height: 0; padding: 10px 12px; overflow: auto; font-size: 13px; color: #b9c6d6">Read the source, then follow <a href="#reference-footer" style="color: #e6eef7">the evidence</a>.</div>
+<div style="flex-shrink: 0; border-top: 1px solid #1b2c44; padding: 6px 36px 6px 8px; text-align: right"><button style="border: 1px solid transparent; border-radius: 6px; padding: 4px 8px; background: transparent; color: #8ea3bd; font: 500 11px 'IBM Plex Sans', sans-serif">Edit</button></div>
 <div id="reference-footer" role="region" aria-label="Cross-board references" tabindex="0" style="flex-shrink: 0; max-height: min(40%, 132px); overflow: auto; overscroll-behavior: contain">
 <div style="padding: 6px 12px; border-top: 1px solid #1b2c44; font-size: 12px; color: #b9c6d6">↗ references: Research / Interview notes</div>
 <div style="padding: 6px 12px; border-top: 1px solid #1b2c44; font-size: 12px; color: #b9c6d6">↗ references: Research / Findings</div>
@@ -174,11 +176,35 @@ body{margin:0}
 <span style="font-size: 11px; color: #8ea3bd">Fit and focus keep a lane clear for floating chrome.</span>
 </div>
 </div>
+
+<div style="display: flex; flex-direction: column; gap: 8px">
+<h2 style="margin: 0; font-size: 15px; font-weight: 600">Present · hover / keyboard focus</h2>
+<p style="margin: 0; font-size: 11px; color: #8ea3bd">2026-10-25: the button describes this tooltip with aria-describedby. In the narrow ⋯ menu, the same text appears in flow below Present so the scrolling menu cannot clip it.</p>
+<div role="tooltip" style="max-width: 240px; padding: 10px 12px; border: 1px solid #2a4566; border-radius: 10px; background: #0f1d31; color: #b9c6d6; font-size: 12px; line-height: 1.35">
+<strong style="color: #e6eef7">Present board</strong>
+<p>A presentation follows either a saved tour or the board’s groups.</p>
+<p>Saved tour: ask your agent to define the stops and their order. Each stop can focus on a card, a group, a rectangular area, or a specific camera position.</p>
+<p style="margin-bottom: 0">No saved tour: every group becomes a stop, ordered top-to-bottom, then left-to-right. It doesn’t automatically visit every card.</p>
+</div>
+</div>
+<div style="display: flex; flex-direction: column; gap: 8px">
+<h2 style="margin: 0; font-size: 15px; font-weight: 600">Presentation · navigation</h2>
+<p style="margin: 0; font-size: 11px; color: #8ea3bd">Owner decision, 2026-10-25: Back and Next sit beside Exit at the top-right. Instructions appear only in hover/focus tooltips, never in a corner panel. End buttons stay focusable but unavailable; their descriptions remain accessible.</p>
+<div style="position: relative; height: 180px; border: 1px solid #1b2c44; border-radius: 10px; background: #081524">
+<div style="position: absolute; top: 16px; right: 16px; display: flex; gap: 8px">
+<button style="padding: 8px 14px; min-height: 38px; border: 1px solid #8ea3bd; border-radius: 8px; background: #0f1d31; color: #e6eef7; font: inherit; font-weight: 600; opacity: .5" aria-disabled="true">Back</button>
+<button style="padding: 8px 14px; min-height: 38px; border: 1px solid #8ea3bd; border-radius: 8px; background: #0f1d31; color: #e6eef7; font: inherit; font-weight: 600">Next</button>
+<button style="padding: 8px 14px; min-height: 38px; border: 1px solid #8ea3bd; border-radius: 8px; background: #0f1d31; color: #e6eef7; font: inherit; font-weight: 600">Exit presentation</button>
+</div>
+<div style="position: absolute; top: 66px; right: 16px; width: 168px; padding: 10px 12px; border: 1px solid #2a4566; border-radius: 10px; background: #0f1d31; box-shadow: 0 14px 36px #0006; font-size: 12px"><strong>Next stop</strong><br><span style="color: #8ea3bd">→ / ↓ / Space</span></div>
+</div>
+<p style="margin: 0; font-size: 11px; color: #8ea3bd">Back: Previous stop, ← / ↑. Next: Next stop, → / ↓ / Space. Exit: Exit presentation, Esc. Fit clears the top controls; exact camera targets and recording remain exact.</p>
+</div>
 </section>
 
 </div>
 </x-dc>
-<script type="text/x-dc" data-dc-script data-props='{"$preview":{"width":1440,"height":1000}}'>
+<script type="text/x-dc" data-dc-script data-props='{"$preview":{"width":1440,"height":1360}}'>
 class Component extends DCLogic {
   renderVals() {
     var P = {
@@ -245,7 +271,7 @@ class Component extends DCLogic {
       optIn('Trace', 'Show execution traces. Turning off keeps existing traces and never starts an agent.', false, false),
       setting('Send feedback', '', 'Share feedback about PMX Canvas.')
     ];
-    var nodeMenu = [m('Focus', ''), m('Rename…', ''), m('Collapse', ''), m('Open in new tab', '', true), msep, m('Delete', '⌫')];
+    var nodeMenu = [m('Focus', ''), m('Rename…', ''), m('Collapse', ''), m('Open in new tab', ''), msep, m('Set as README', '', true), msep, m('Delete', '⌫')];
     var oldIcons = [{ d: P.ctx }, { d: P.ask }, { d: P.open }, { d: P.expand }, { d: P.chevron }, { d: P.close }];
     return { railToday: railToday, railNew: railNew, settings: settings, nodeMenu: nodeMenu, oldIcons: oldIcons };
   }

package/docs/design/Types1.dc.html

@@ -22,7 +22,7 @@ body{margin:0}
 </div>
 
 <div style="{{s.row}}">
-<div><div style="{{s.type}}">markdown</div><p style="{{s.what}}">Body 11 → 12px. “Set as README / Edit” footer moves into ⋯; double-click still edits.</p></div>
+<div><div style="{{s.type}}">markdown</div><p style="{{s.what}}">Body 11 → 12px. Set as README moves into ⋯, becoming Remove as README when assigned. A quiet README header word stays visible on the designated card, including heading display (Chrome §8). Edit stays visible; double-click still edits. Heading display has no footer.</p></div>
 <div style="{{o.node}}">
 <div style="{{o.head}}"><svg width="16" height="16" viewBox="0 0 24 24" style="{{o.icon}} color: #4BBCFF"><path d="{{i.note}}"></path></svg><span style="{{o.title}}">PMX Canvas — guided tour</span><span style="{{o.ctl}}">⤢⌄×</span></div>
 <div style="padding: 10px 14px; display: flex; flex-direction: column; gap: 6px">
@@ -39,6 +39,7 @@ body{margin:0}
 <div style="color: #b9c6d6">An infinite spatial canvas that agents drive over MCP, HTTP or the Bun SDK — and that humans steer by pinning nodes.</div>
 <div style="color: #b9c6d6">• Pin a node in the browser<br>• The agent reads it from <code style="{{n.code}}">canvas://pinned-context</code></div>
 </div>
+<div style="border-top: 1px solid #1b2c44; padding: 6px 36px 6px 8px; text-align: right"><button style="border: 1px solid transparent; border-radius: 6px; padding: 4px 8px; background: transparent; color: #8ea3bd; font: 500 11px 'IBM Plex Sans', sans-serif">Edit</button></div>
 </div>
 </div>
 
@@ -120,7 +121,7 @@ body{margin:0}
 </div>
 
 <div style="{{s.row}}">
-<div><div style="{{s.type}}">file</div><p style="{{s.what}}">The extra toolbar row folds into the header (path · lines). Code 10 → 12px with dim line numbers.</p></div>
+<div><div style="{{s.type}}">file</div><p style="{{s.what}}">The extra toolbar row folds into the header (path · lines). Only metadata clips as space tightens; Reload and AX evidence hints remain visible on hover/focus. Code 10 → 12px with dim line numbers.</p></div>
 <div style="{{o.node}}">
 <div style="{{o.head}}"><svg width="16" height="16" viewBox="0 0 24 24" style="{{o.icon}} color: #4BBCFF"><path d="{{i.file}}"></path></svg><span style="{{o.title}}">node-sizes.ts</span><span style="{{o.ctl}}">⤢⌄×</span></div>
 <div style="display: flex; align-items: center; gap: 6px; padding: 4px 12px; border-bottom: 1px solid #1b2c44; font-family: 'IBM Plex Mono', monospace; font-size: 9px; color: #8ea3bd"><span style="padding: 1px 4px; border-radius: 3px; background: #13243b; color: #4BBCFF">TS</span><span>46 lines</span><span style="color: #5c6b80">src/shared/node-sizes.ts</span></div>

package/docs/design/Types2.dc.html

@@ -90,7 +90,7 @@ body{margin:0}
 </div>
 
 <div style="{{s.row}}">
-<div><div style="{{s.type}}">html</div><p style="{{s.what}}">The white outline around the frame goes. The page gets the canvas tokens, so it sits on the node surface.</p></div>
+<div><div style="{{s.type}}">html</div><p style="{{s.what}}">The white outline around the frame goes. The page gets the canvas tokens, so it sits on the node surface. Owner decision, 2026-10-25: generated primitives have no shared header copy buttons. Copy JSON lives in the card's ⋯ menu and includes live edits. Copy prompt is removed; primitive-specific copy controls remain.</p></div>
 <div style="{{o.node}}">
 <div style="{{o.head}}"><svg width="16" height="16" viewBox="0 0 24 24" style="{{o.icon}} color: #4BBCFF"><path d="{{i.html}}"></path></svg><span style="{{o.title}}">Release gates</span><span style="{{o.ctl}}">↗⤢⌄×</span></div>
 <div style="flex: 1; margin: 8px; border: 1px solid #f2f2f2; border-radius: 2px; padding: 10px 12px; display: flex; flex-direction: column; gap: 5px">

package/docs/design/Types3.dc.html

@@ -49,7 +49,7 @@ body{margin:0}
 </div>
 
 <div style="{{s.row}}">
-<div><div style="{{s.type}}">graph</div><p style="{{s.what}}">Chart sits on the node surface. The title isn't repeated inside; the chart type becomes header meta.</p></div>
+<div><div style="{{s.type}}">graph</div><p style="{{s.what}}">Chart sits on the node surface. The title isn't repeated inside; the chart type becomes header meta. Close slopegraph labels separate by 14px when space permits; points stay at their values, with short same-ink leaders.</p><svg width="200" height="60" role="img" aria-label="Close slopegraph labels, values unchanged"><path d="M10 42L70 20M10 52L70 26L75 34" fill="none" stroke="#4BBCFF" stroke-width="1.5"></path><circle cx="70" cy="20" r="2.5" fill="#4BBCFF"></circle><circle cx="70" cy="26" r="2.5" fill="#4BBCFF"></circle><text x="78" y="20" dominant-baseline="central" fill="#e6eef7" font-size="11">59 cli</text><text x="78" y="34" dominant-baseline="central" fill="#e6eef7" font-size="11">58 client</text></svg></div>
 <div style="{{o.node}}">
 <div style="{{o.head}}"><svg width="16" height="16" viewBox="0 0 24 24" style="{{o.icon}} color: #f4c542"><path d="{{i.chart}}"></path></svg><span style="{{o.title}}">bar — merged PRs per week</span><span style="{{o.ctl}}">↗⤢⌄×</span></div>
 <div style="flex: 1; margin: 0 8px 8px; position: relative; background: #000000; border-radius: 8px; padding: 10px 12px; font-family: system-ui, sans-serif">

package/docs/design/Zoom.dc.html

@@ -2,79 +2,56 @@
 <html lang="en">
 <head>
 <meta charset="utf-8">
-<title>Zoomed out — fit all</title>
+<title>Native spatial zoom</title>
 <script src="./support.js"></script>
 </head>
 <body>
 <x-dc>
 <helmet>
-<link rel="stylesheet" href="https://fonts.googleapis.com/css2?family=IBM+Plex+Mono:wght@400;500&amp;family=IBM+Plex+Sans:wght@400;500;600&amp;display=swap">
-<style>
-body{margin:0}
-</style>
+<link rel="stylesheet" href="https://fonts.googleapis.com/css2?family=IBM+Plex+Sans:wght@400;500;600&amp;display=swap">
+<style>body{margin:0}</style>
 </helmet>
-<div style="width: 1440px; height: 640px; box-sizing: border-box; padding: 40px 48px; background: #081524; color: #e6eef7; font-family: 'IBM Plex Sans', system-ui, sans-serif; font-size: 13px; line-height: 1.5; display: flex; flex-direction: column; gap: 20px">
-<div><h2 style="margin: 0; font-size: 15px; font-weight: 600">11 · Fit all on the demo board lands at 8%</h2><p style="margin: 2px 0 0; font-size: 12px; color: #8ea3bd">41 of 70 nodes are embedded frames and render as empty cards. Below ~25%, draw each node as its kind and title at screen size.</p></div>
-<div style="flex: 1; display: grid; grid-template-columns: repeat(2, minmax(0, 1fr)); gap: 40px">
-
-<div style="display: flex; flex-direction: column; gap: 8px">
-<span style="font-size: 11px; font-weight: 500; letter-spacing: 0.06em; text-transform: uppercase; color: #6b7d94">Today</span>
-<div style="position: relative; flex: 1; border-radius: 10px; border: 1px solid #1b2c44; overflow: hidden; background: #081524">
-<sc-for list="{{sections}}" as="sct" hint-placeholder-count="2">
-<div style="position: absolute; left: 24px; top: {{sct.y}}px; width: 600px; height: 10px; border-radius: 3px; background: #0f1d31; border: 1px solid #1b2c44; box-shadow: 0 0 0 1px rgba(244,197,66,0.3)"></div>
+<div style="width:1440px;height:640px;box-sizing:border-box;padding:40px 48px;background:#081524;color:#e6eef7;font-family:'IBM Plex Sans',system-ui,sans-serif;font-size:13px;line-height:1.5">
+<h2 style="margin:0;font-size:20px;font-weight:600">11 · Keep the native board at every zoom</h2>
+<p style="color:#8ea3bd">Maintainer decision, 2026-10-25. The same positions, sizes, groups, connections and contents scale together. No alternate grid or content enlargement.</p>
+<div style="display:flex;gap:24px;margin-top:28px">
+<sc-for list="{{views}}" as="view" hint-placeholder-count="3">
+<section style="width:432px">
+<h3 style="font-size:14px">{{view.label}}</h3>
+<svg width="432" height="380" viewBox="0 0 432 380" style="border:1px solid #1b2c44;border-radius:10px;background:#081524">
+<g transform="translate(16 44)">
+<g transform="scale({{view.scale}})">
+<rect x="0" y="0" width="396" height="308" rx="8" fill="none" stroke="#536c88"/>
+<text x="12" y="22" fill="#e6eef7" font-size="16">Release evidence</text>
+<path d="M182 128 L218 218" stroke="#6b7d94" stroke-width="2" fill="none"/>
+<path d="M211 213 L218 218 L218 210" stroke="#6b7d94" stroke-width="2" fill="none"/>
+<g transform="translate(12 36)">
+<rect width="170" height="154" rx="8" fill="#0f1d31" stroke="#1b2c44"/>
+<text x="12" y="22" fill="#e6eef7" font-size="{{view.titleSize}}">Build durations</text>
+<path d="M14 126 L45 99 L77 110 L110 72 L153 84" fill="none" stroke="#62c4b8" stroke-width="3"/>
+<path d="M14 44 V138 H156" fill="none" stroke="#536c88"/>
+<text x="16" y="59" fill="#8ea3bd" font-size="11">37 → 19 minutes</text>
+</g>
+<g transform="translate(218 146)">
+<rect width="166" height="146" rx="8" fill="#0f1d31" stroke="#1b2c44"/>
+<text x="12" y="22" fill="#e6eef7" font-size="{{view.titleSize}}">Release gates</text>
+<text x="12" y="56" fill="#e6eef7" font-size="13">✓ Tests passed</text>
+<text x="12" y="82" fill="#e6eef7" font-size="13">✓ Review complete</text>
+<text x="12" y="108" fill="#8ea3bd" font-size="12">Source: build report</text>
+</g>
+</g>
+</g>
+</svg>
+</section>
 </sc-for>
-<sc-for list="{{tiles}}" as="t" hint-placeholder-count="20">
-<div style="position: absolute; left: {{t.x}}px; top: {{t.y}}px; width: 112px; height: 72px; box-sizing: border-box; border-radius: 4px; background: #0f1d31; border: 1px solid #1b2c44; overflow: hidden"><div style="height: 6px; background: #13243b"></div></div>
-</sc-for>
-<span style="position: absolute; right: 12px; bottom: 10px; font-family: 'IBM Plex Mono', monospace; font-size: 11px; color: #5c6b80">8%</span>
-</div>
-</div>
-
-<div style="display: flex; flex-direction: column; gap: 8px">
-<span style="font-size: 11px; font-weight: 500; letter-spacing: 0.06em; text-transform: uppercase; color: #6b7d94">Proposed</span>
-<div style="position: relative; flex: 1; border-radius: 10px; border: 1px solid #1b2c44; overflow: hidden; background: #081524">
-<sc-for list="{{sections}}" as="sct" hint-placeholder-count="2">
-<div style="position: absolute; left: 24px; top: {{sct.yt}}px; font-size: 15px; font-weight: 600; line-height: 20px">{{sct.title}}</div>
-</sc-for>
-<sc-for list="{{tiles}}" as="t" hint-placeholder-count="20">
-<div style="position: absolute; left: {{t.x}}px; top: {{t.y}}px; width: 112px; height: 72px; box-sizing: border-box; padding: 8px 10px; border-radius: 6px; background: #0f1d31; border: 1px solid #1b2c44; display: flex; flex-direction: column; gap: 4px">
-<div style="display: flex; align-items: center; gap: 6px"><svg width="14" height="14" viewBox="0 0 24 24" style="flex-shrink: 0; color: #8ea3bd; fill: none; stroke: currentColor; stroke-width: 1.8; stroke-linecap: round; stroke-linejoin: round"><path d="{{t.icon}}"></path></svg><span style="font-size: 11px; color: #8ea3bd">{{t.kind}}</span></div>
-<span style="font-size: 12px; font-weight: 600; line-height: 1.3">{{t.title}}</span>
-</div>
-</sc-for>
-<span style="position: absolute; right: 12px; bottom: 10px; font-family: 'IBM Plex Mono', monospace; font-size: 11px; color: #6b7d94">8%</span>
-</div>
-</div>
-
 </div>
+<p style="color:#8ea3bd">Automatic previews stay on the board. Zoom or expand to read details. Title text grows at most 1.2×; the header line and content space stay fixed.</p>
 </div>
 </x-dc>
 <script type="text/x-dc" data-dc-script data-props='{"$preview":{"width":1440,"height":640}}'>
 class Component extends DCLogic {
   renderVals() {
-    var chart = 'M4 4v16h16M8 16v-4M12 16V8M16 16v-6';
-    var html = 'M8 8l-4 4 4 4M16 8l4 4-4 4M13.5 5l-3 14';
-    var charts = [
-      ['line', 'p95 latency'], ['bar', 'Merged PRs'], ['area', 'Nodes created'], ['pie', 'Node types'], ['stacked', 'CI minutes'],
-      ['composed', 'Throughput'], ['scatter', 'PR size'], ['radar', 'Coverage'], ['sparkline', 'Build time'], ['bullet', 'Release KPIs']
-    ];
-    var prims = [
-      ['html', 'Choice grid'], ['html', 'Plan timeline'], ['html', 'Review sheet'], ['html', 'PR write-up'], ['html', 'System map'],
-      ['html', 'Walkthrough'], ['html', 'Design sheet'], ['html', 'Component gallery'], ['html', 'Flowchart'], ['html', 'Triage board']
-    ];
-    var sections = [
-      { y: 22, yt: 18, title: '④ Charts' },
-      { y: 222, yt: 218, title: '⑦ HTML primitives' }
-    ];
-    var tiles = [];
-    function place(list, top, icon) {
-      list.forEach(function (it, i) {
-        tiles.push({ x: 24 + (i % 5) * 122, y: top + Math.floor(i / 5) * 82, kind: it[0], title: it[1], icon: icon });
-      });
-    }
-    place(charts, 50, chart);
-    place(prims, 250, html);
-    return { sections: sections, tiles: tiles };
+    return { views: [{ label: '100%', scale: 1, titleSize: 12 }, { label: '39%', scale: 0.39, titleSize: 14.4 }, { label: '20%', scale: 0.2, titleSize: 14.4 }] };
   }
 }
 </script>

package/docs/design/canvas.json

@@ -38,7 +38,7 @@
       "y": 10260
     },
     "Chrome.dc.html": {
-      "h": 1000,
+      "h": 1360,
       "title": "Rail, node header, section labels",
       "w": 1440,
       "x": 1520,

package/docs/design.md

@@ -87,8 +87,8 @@ Components reference tokens only. Raw colour values live only in the theme files
 - Tints are derived — `color-mix(in srgb, var(--c-pin) 12%, transparent)` — so the 22 alpha
   copies, `--c-warn-alt` and `--c-glow-accent` go.
 - `--c-thinking` becomes `--c-agent`.
-- **Kinds carry no colour.** Type icons use `--c-muted`; the glyph tells the kind, plus the kind
-  word on zoomed-out tiles (Zoom board). Minimap rects and group-chip kind dots are neutral, and
+- **Kinds carry no colour.** Type icons use `--c-muted`; the glyph tells the kind.
+  Minimap rects and group-chip kind dots are neutral, and
   only meaning colours mark them (pinned, agent at work). `KIND_COLOR`, `--kind-accent` and
   `--c-purple` go. Nine kind hues cannot all stay clear of ten meaning colours in nine themes,
   and every hue a kind borrows is one a meaning loses.
@@ -141,7 +141,7 @@ the same change.
 | [`Flows.dc.html`](design/Flows.dc.html) | Data lineage with staleness, what a finding rests on, opening a group | 3, 5 |
 | [`Uses.dc.html`](design/Uses.dc.html) | One relation layer for research, dependencies, decisions and agent flows | 3 |
 | [`Types1.dc.html`](design/Types1.dc.html)–[`Types3.dc.html`](design/Types3.dc.html) | Every node type, today vs proposed | 0, 4 |
-| [`Zoom.dc.html`](design/Zoom.dc.html) | Fit-all readability when frames are unmounted | 4 |
+| [`Zoom.dc.html`](design/Zoom.dc.html) | Native spatial scaling at every zoom, maintainer override 2026-10-25 | 4 |
 | [`Pane600.dc.html`](design/Pane600.dc.html) | Home and a board at the narrow end, 600 px | all |
 | [`Vision.dc.html`](design/Vision.dc.html) | How each design area maps to the vision, and the open decisions | — |
 
@@ -377,7 +377,7 @@ workflow. A demo of existing features must not be used to claim full sketch pari
 | **1. Context made visible** — its curation evaluation moved to the end of the plan (2026-10-19) | Part 1 bet, moves 0a, 2, 7 | Surface `context_reads` (already recorded since 0.7.0: who read, which nodes were delivered) per node and per board as read / not read / changed since read, using revisions; who pinned; activity lens and session receipt from presence activity and revisions; board pins (`board_pins`, tiered brief, `canvas_board pin/unpin`) and Home's pinned-boards section | What the agent did with context, Nodes in context, Board pins, Home (Folders) | From the board alone, a person can answer "did the agent read what I pinned, and is its copy current?" The evaluation in `docs/evals/` reads the same data |
 | **2. Connected memory views** — implemented, verification gates apply | Moves 0, 14 | One board/card projection for Home, links/backlinks, brief discovery and `canvas://graph{?focus,depth}`; saved wiki ID bindings, direct cross-board card edges, previous-board chains, persisted Map positions | Home Map, Home Graph (deviations below) | Map and Graph are generated from the library; orphans visible; works at 600 px and in a full window |
 | **3. Relations layer** | Moves 0, 1, 13 | Edge `reason` and an open `kind` with a per-board vocabulary; relations carried in the brief's text form; "derived from" with staleness from provenance and recipes; relation queries for the inspector | Relations, Lineage, One relation layer | Hovering a node explains each link; a changed source turns downstream nodes amber; the agent's brief includes relations |
-| **4. Frame host and viewers** | Moves 5, 9 | One frame host passing the full theme tokens; json-render defaults to the canvas theme with an opt-out for design experiments; zoomed-out cards for unmounted frames | Node types 1–3, Zoomed out | No viewer draws its own background; 20 portals mount no more frames than none; fit-all is readable |
+| **4. Frame host and viewers** | Moves 5, 9 | One frame host passing the full theme tokens; json-render defaults to the canvas theme with an opt-out for design experiments; native proportional canvas at every zoom | Node types 1–3, Zoom | Viewers use the canvas palette and fill their authored space; approaching a viewer mounts it automatically and retains its state when panning away; no alternate grid or lifetime preview cap |
 | **5. Agent output and groups as pages** | Moves 3, 0 | Work items, gates and asks as nodes; make board / inline board; opening a group keeps its outside links | One relation layer (agent flow), Lineage (open a group) | Agent output is styled by the same shell and tokens; a group opened as a board shows its outside stubs |
 | **Later: hosted version** | Part 4 (moved from Part 3, 2026-10-19) | Read-only link, comments, second writer, accounts and roles; org → team → personal scopes with configurable categories and per-user pins; built once for the ChatGPT Sites and later Cloudflare editions | HomeTeam is the earlier two-root look ahead; updated scope/category drawings are required before building, retaining explicit publication and locked cards for unreadable boards | Exports and shared views inherit the tokens; a viewer sees the same meaning colours; nothing personal reaches a wider audience without explicit publication |
 
@@ -630,6 +630,171 @@ curation evaluation after its remaining features. Local categories and lifecycle
 without a model; Jev-style classification is optional longer-term assistance, not a dependency
 of Wave 3 or the org/team/personal structure.
 
+## 0.11 implementation notes
+
+Chrome §9–10 and Types1–3 drive the section-heading, header, typography and viewer
+pass. Fit and focus reserve a 44 px screen-space top lane. JSON viewers inherit the
+named canvas palette; only duplicate root titles disappear. Mermaid renders inline.
+File-header metadata may clip within its own text container, but Reload and AX
+evidence actions and their hover/focus hints stay outside that clip (Types1).
+The maintainer's 2026-10-25 decision supersedes the earlier reading-flow footer:
+**Set as README** lives only in the card's ⋯ menu, becoming **Remove as README**
+for the current README. The agent normally assigns it; this menu is the human override.
+The designated card keeps a quiet, always-visible **README** word in its header,
+including heading-display Markdown. It uses neutral metadata ink, not pin blue or
+selection styling; the title yields before this identifier truncates.
+Ordinary Markdown keeps its visible **Edit** action; heading display has no footer.
+Chrome and Types1 reflect this decision. The menu takes keyboard focus, supports
+arrows and Tab, and restores the opener on activation or Escape.
+**Present** explains saved tours versus group-derived stops on hover and keyboard
+focus, with an accessible description. The narrow ⋯ menu shows the same explanation
+in flow below Present rather than clipping a floating tooltip. Chrome records the
+owner's exact copy; no tour behavior changes. Its saved-tour instruction says
+**ask your agent to define the stops**, not that a visual human tour editor exists.
+During presentation, **Back** and **Next** sit beside **Exit presentation** at
+the top-right, following the existing shared server cursor. The owner's final
+placement decision puts instructions only in each button's hover/focus tooltip:
+Previous stop (← / ↑), Next stop (→ / ↓ / Space), Exit presentation (Esc).
+There is no lower-left instruction panel. Unavailable end buttons remain focusable
+for their descriptions. Node/rectangle fitting reserves the controls' measured
+height; explicit camera targets and deterministic recordings remain unchanged.
+HTML primitives put **Copy JSON** in the card's ⋯ menu, not their inner header;
+**Copy prompt** is removed. JSON comes from the current mounted document, including
+unsaved interactive edits, through the nonce-bound sandbox bridge. Unloaded or
+replaced documents and denied clipboard access report failure, not stale data or
+success. Raw HTML and the custom presentation primitive have no JSON-export menu
+action. Primitive-specific Copy diff, Copy SVG and similar controls stay in place.
+The maintainer's 2026-10-25 correction rejects the experimental CSS zoom, content
+enlargement and alternate overview. The original world matrix scales cards,
+embedded contents, groups and connections proportionally at every zoom. Only title
+text grows, up to 1.2× inside a fixed 22 px header line. Header controls, padding and
+body space stay fixed in world pixels; enlarging the whole header would resize the
+iframe viewport and reflow charts while zooming. Card bodies never counter-scale.
+All cards share the same stacking and input boundary. A separate
+ext-app portal was rejected in review because it covered higher cards, bypassed
+pan gestures, and disappeared during presentation. The common world also owns
+clipping when a dock resizes the canvas. Headed Linux WebKit reproduced CSS zoom
+shrinking the iframe's internal layout and retaining stale dimensions through
+zoom transitions. Restoring the matrix keeps inner widths stable in the same probe.
+Native WKWebView compositor health remains unverified, not established by that result.
+Automatic previews mount on first approach at any scale, then retain their
+documents to preserve arbitrary app state. The rejected lifetime cap starved later
+board regions. Memory now grows with visited viewers. Visible viewers start loading
+automatically without a shared bootstrap queue or per-card clicks. A slow document
+does not hold another card's loading slot.
+Each loading replacement temporarily coexists with its painted document.
+
+The demo gives ordinary standalone charts the full authored card height instead
+of imposing a smaller plot-height cap. Compact chart types keep compact cards:
+the 36 px sparkline sits in a 120 px card, four dot-plot rows in 240 px, three bullet
+rows in 260 px, and the slopegraph in 300 px. These are demo authoring choices,
+not enforced sizes on user cards. Explicit chart `height` still caps content,
+independently of `nodeHeight`. Dashboard and form stacks explicitly use stretch
+alignment; the catalog's start-aligned default is unchanged, as are compact action
+buttons. Work-item controls must fit their authored cards without accidental
+overflow or truncated status. Enlarging the demo to 440×300 did not meet that
+requirement and is not acceptance evidence. The card body now scrolls only its
+content when needed; step controls and Edit share one fixed footer row. The full
+status word takes priority over the title. Steering input and send button wrap
+together. Expanded documents keep their sticky footer. The demo returns to a
+240 px height, with 360 and 440 px widths exercised in both Chromium and WebKit.
+Bodies still shrink proportionally.
+
+Static exports use the same embedded chart layout and named palettes, retain
+heading display, and match the live 37 px card header. Fonts and shared palette
+CSS are embedded for offline use. Saved positions, sizes and specs are unchanged;
+live work controls are intentionally absent. Export is a separate acceptance
+surface, not established by live canvas checks. Close slopegraph labels separate
+without moving data endpoints; short same-ink leaders retain their association
+(Types3). An explicitly overcrowded chart still requires adequate authored height.
+
+Relation labels keep their curve midpoint when clear. Otherwise the pill and its
+hit area move together to nearby open space, avoiding cards, group headers,
+connection handles and earlier labels. A dashed leader in the relation's ink
+ties it back to the curve. Card positions, curve routing and stacking do not
+change. Font measurements determine pill width. Dense boards can still require
+panning to a displaced label; labels remain hidden below the existing 35% floor.
+
+`ViewerHost` owns preview admission, without a second positioning or recovery path.
+`RefreshingViewerFrame` owns document loading, the painted replacement handoff and
+Retry. HTML readiness and the ext-app protocol use that host; JSON additionally
+restores its viewer-local state before promotion. The ext-app adapter no longer
+has a separate paint/recovery ladder. Document preparation failures do not fall
+back to another transport that the embedding probe already rejected.
+Ext-app protocol bootstrap runs once after initialization, or after the loaded
+document's bounded notification-only bootstrap interval. The host waits for
+input/result delivery and paint before declaring it ready; bootstrap errors use
+the same Retry as other loading failures.
+Webpages show cached text until an explicit live-preview request; Mermaid
+and native board thumbnails render inline. Mermaid's inline
+and standalone/export renderers share their palette, serialization and sanitizer.
+Inline rendering uses Mermaid's strict security mode and DOMPurify, including
+sanitized `foreignObject` labels, instead of the old diagram iframe sandbox.
+Mermaid is the exception to the static-import rule: the SPA loads it on the first
+diagram, using hashed chunks from the same server. A six-Markdown-card cold-boot
+probe requested only the entry and its small shared chunk, not Mermaid's 3.46 MB.
+With Bun 1.4.4, headed Chromium 145, 4× CPU throttling and five alternating fresh
+contexts per variant, the baseline median was 1,423.9 ms and the candidate median
+1,349.1 ms to six populated cards plus two animation frames. Ranges overlap
+(1,277.3–1,484.7 ms versus 1,315.2–1,510.1 ms), so this is not a speedup claim.
+The baseline is 0.10.0 rebuilt with the same compiler; both variants use current
+CSS and local intercepted responses, not a network or native-host benchmark.
+Reproduce with `DISPLAY=:99 node scripts/benchmark-canvas-boot.mjs <disposable-server-url> <baseline-index.js>`.
+The populated-board check uses `scripts/benchmark-populated-canvas.mjs`, the same
+70-card fixture and 18% camera, headed Chromium 145 at 1440×900, and three cold-cache
+loads plus three warm reloads per build, with other browsers and tests stopped.
+All 33 visible viewers rendered. The final comparison found baseline 0.10.0 at
+6.71–7.67 s cold and 7.17–7.32 s warm; the candidate took 7.59–8.19 s cold and
+8.00–8.39 s warm. This remains a loading cost, not an orb-only explanation or a
+speedup. Main-page long tasks totalled 4.43–4.87 s on the candidate versus
+3.46–4.20 s on baseline. Each chart document contains about 1.49 MB decoded
+(baseline 1.47 MB). Parent Resource Timing alone misses baseline iframe bytes
+and can duplicate candidate navigation bytes; do not compare or sum those totals.
+The script records frame resources separately. Removing the provisional four-document queue produced overlapping
+completion ranges and a later first viewer; the simpler independent loading path
+avoids cross-card blocking, not a claimed performance win. Warm-load aborted
+presence requests are recorded separately from viewer failures; no viewer failed.
+At the default 52% camera there are no visible iframe viewers. The candidate's
+board appeared in 0.67–0.70 s cold and 0.52–0.65 s warm versus baseline's
+1.08–1.32 s and 1.06–1.36 s. That measures deferred offscreen work, not faster
+viewer rendering. Local document responses were 2–6 ms. Portal-URL checks use
+Amp's local hairpin forwarding inside this orb, so they do not measure external
+portal transport or the user's connection. These are instrumented local readiness
+timings, not native paint latency. Linux WebKit's full fit-all load exceeded this orb's memory limit
+on both baseline and candidate; narrower populated-row checks are separate evidence.
+The self-contained MCP App cannot fetch those chunks: its document includes
+Mermaid and grows from about 1.32 MB to 4.78 MB uncompressed. This is an introduced delivery
+cost, not eliminated debt or measured native performance. Keeping one renderer
+and an offline-capable MCP document is the tradeoff; native boot remains unmeasured.
+The bundle audit found one Mermaid core, one shared renderer and one DOMPurify,
+not an embedded copy of the standalone viewer. The old standalone Mermaid bundle
+already weighed 3,492,157 bytes; moving its renderer inline brings that dependency
+tree into the self-contained MCP host. The dependency graph contains different
+major versions of `marked`, `layout-base` and `cose-base` required by Mermaid's
+renderers; forcing aliases would not be a safe deduplication. Inspect the graph
+with `bun build src/client/mcp-app/index.tsx --target=browser --format=iife --minify --metafile=/tmp/mcp-meta.json --outfile=/tmp/mcp.js`.
+Removing the payload from MCP startup requires a different script-delivery/CSP
+contract or a reduced diagram catalog, rather than deleting a duplicate host.
+Static export checks separately cover all twelve graph variants, compact plots,
+all nine named themes and 600, 1024 and 1920 px widths in headed Chromium.
+The populated 70-card export matches live saved geometry and renders offline
+without HTTP(S) requests; bounded Linux WebKit checks cover the compact chart
+section and dashboard. Linked boards and live MCP apps retain honest unavailable
+placeholders. Arbitrary user HTML can still contain external requests.
+
+There is no threshold-triggered grid or list. Zoom's revised drawing keeps the
+same positions, sizes, groups, connections and native content at every scale.
+Fit-all is for orientation; zoom or expand to read details. The earlier overview's
+scrolling and overlay-clearance fixes are superseded by its complete removal.
+
+Visual audit: Harbor headings use the drawing's 20 px semibold `#e6eef7` on
+`#081524` (15.69:1). The initial dim capture had the existing relation-focus
+highlight active, which applies 0.35 opacity to unrelated cards; Escape clears
+that view state. A neighboring card outside a 600 px viewport is spatially
+clipped, not internally truncated: focusing it restores the complete title.
+Expanded pin hints remain while their button has keyboard `:focus-visible`, even
+after pointer movement; Tab away dismisses the hint after its fade transition.
+
 ## Definition of done for any design work
 
 1. It is drawn in the proposal canvas first, at 600 px and at full-window width.

package/docs/http-api.md

@@ -217,9 +217,15 @@ content auto-height or indirect parent-group reflow after editing a child.
   update and are included in snapshots/undo. They are board-wide writes under a scope fence.
 - `POST /api/canvas/tour/go` with `{ "stop": 2 }` or `{ "step": "next" | "previous" }`
   (plus optional `"present": false`) moves the shared tour cursor →
-  `{ ok, index, total, stop }`; 400 when the stop does not exist or the board has no stops.
+  `{ ok, index, total, stop, catalogEpoch, boardGeneration, sequence }`;
+  400 when the stop does not exist or the board has no stops.
   Broadcasts `canvas-tour-step`; idle workbenches start presenting unless `present` is false.
+  Response and event share the same monotonically increasing `sequence` within the
+  server's `catalogEpoch`. Viewers accept only newer steps for their current epoch
+  and board generation, so delayed echoes cannot rewind or replay the camera.
 - `POST /api/canvas/tour/exit` leaves presentation in every viewer (`canvas-tour-exit`).
+  Returns `{ ok, catalogEpoch, boardGeneration, sequence }`; the event shares that
+  identity and the step sequence, so an old exit cannot dismiss a newer presentation.
 - `POST /api/canvas/camera/move` with exactly one of `nodeId`, `rect: { x, y, width, height }`
   or `viewport: { x, y, scale }`, plus optional `duration`, `easing`, `padding`, `pullback`
   → `{ ok, stop, viewport }`. Broadcasts `canvas-camera-move`; browsers ease to the target in
@@ -229,6 +235,29 @@ content auto-height or indirect parent-group reflow after editing a child.
 Tour steps and camera moves are navigation: no undo entry, no agent-presence write, no
 scope-fence check.
 
+`tour/go` and `tour/exit` accept optional `presenter: { clientId, intent,
+catalogEpoch, boardGeneration }`. The workbench assigns each document a random ID
+and each gesture an increasing positive safe-integer intent. The server rejects
+an old activation or an intent no newer than that document's accepted watermark
+with `{ ok: true, superseded: true }`, without moving the cursor or emitting an event.
+A structurally valid newer command supersedes older ones even if its stop is missing.
+This lets Present proceed while an earlier Exit request is stalled, without that
+late Exit stopping the restart. Resume reads cannot outlive their originating intent.
+
+This is latest-intent-wins, not FIFO: reversed relative Next requests can coalesce.
+Different documents, including a reload, remain independent; unfenced agent calls
+and other documents still act in server arrival order. Reload is not cancellation
+of an old document's pending request. A board activation retains at most 4096
+document IDs, refusing new IDs with 409 rather than evicting an ordering record.
+Switching boards resets that limit; requests stamped with the old activation still
+cannot apply. The SDK exposes the same fence through `goToTourStop(step,
+{ presenter })` and `exitTour(presenter)`; fenced go may return `{ superseded: true }`.
+
+Presentation's Back/Next buttons share this cursor with keyboard and agent navigation.
+They sit beside Exit at the top; hover/focus tooltips show the shortcuts. Node and
+rectangle targets fit below those controls, while explicit viewport targets remain
+exact. Presentation does not change the saved board viewport.
+
 The [tour model and recording walkthrough](cli.md#tour-and-presentation) describes
 targets, duration, easing, padding, and pullback. Open `/workbench?present=1` to hide
 chrome; camera movement is local to that viewer. Recording writes local files via
@@ -388,6 +417,14 @@ stored once per file. Live MCP apps become placeholders; local file contents
 are left out unless `includeFiles` is true. Files are written to `exports/`
 beside the database. Built-app files are only embedded when they are regular,
 bounded-size files inside the board's owned `.pmx-canvas/artifacts/` directory.
+Exports retain saved card positions and sizes, heading display, and the board's
+named theme. Charts and dashboards use embedded card layout without repeating
+the shell title; explicit chart heights remain unchanged. Viewer bundles, palette
+CSS and shell fonts are embedded. Read-only exports omit live work controls.
+When running from source, run `bun run build` before exporting. Export requires
+the complete built viewer assets, `surface-theme.css`, and the font files referenced
+by `global.css`; the installed package includes them. A missing asset tree is not
+a supported text-only export mode.
 The preview manifest lists card links, remote images, and statically visible
 network destinations in embedded HTML. Imported source-linked Markdown is also
 excluded unless `includeDerivedText=true`, independently of `includeFiles`;
@@ -462,6 +499,13 @@ opening that board or changing where writes go. This is supported by
 return 404. Omit `board` to read the active board. Live AX session/delivery reads
 and fixed MCP resources continue to describe the open board.
 
+The workbench's `POST /api/canvas/update` accepts `{updates: [{id, position?, size?,
+collapsed?, zIndex?}], expectedBoardId?, recordHistory?}`. `zIndex` is finite and
+persists stacking without changing geometry. The workbench raises a group and its
+children together, keeping the frame below its children. Title-bar gestures save
+stacking and geometry together on release. Layout notifications and reloads retain
+that order.
+
 ```bash
 # Get canvas state
 curl http://localhost:4313/api/canvas/state
@@ -613,6 +657,10 @@ hosted MCP App still refuses file-linked edits. This is not a crash-recovery dis
 Replacing a JSON-render node's `spec` preserves its current title; include `title`
 to rename it explicitly. A new authored spec still resets the viewer's local drafts.
 
+Markdown nodes accept `data: { "display": "heading" | "card" }` on creation and
+update. Heading display removes the card frame and uses its title as a section
+label; it does not alter content, position, or pin membership.
+
 Mermaid nodes accept `data: { "fit": "contain" | "none" }` on both
 `POST /api/canvas/node` and `PATCH /api/canvas/node/:id`. The default, `contain`,
 shrinks overflowing diagrams without changing aspect ratio; `none` keeps 100%
@@ -1294,6 +1342,8 @@ all consume this stream. Auto-reconnect with exponential backoff.
 
 The direct workbench's `connected` snapshot renews its per-process
 `workbenchToken` (also embedded in boot HTML) over both SSE and polling.
+It is followed by `boards-changed` before the layout, so later tour commands
+already have a board identity even when the separate catalog HTTP read is delayed.
 A same-bundle daemon restart does not reload the page or discard an open draft.
 Registered writes and file saves marked as workbench calls with a supplied stale capability
 return 409 until reconnect renews it; they are never silently recorded as agent

package/docs/mcp.md

@@ -146,6 +146,10 @@ tour: { stops: [...] } }` persists an ordered tour; `tour: null` resets it.
 presents a stop in the workbench, `"tour-exit"` leaves presentation, and
 `canvas_view { action: "move", nodeId | rect | viewport, duration, easing, padding, pullback }`
 eases the camera. None of these enter undo history.
+`tour-go` and `tour-exit` also accept the optional document `presenter` fence
+described in [HTTP board tours](http-api.md#board-tours). Superseded requests return
+`{ ok: true, superseded: true }` with no delivery or event. Ordinary agent calls
+omit it and retain shared arrival-order navigation.
 See the [tour model and CLI walkthrough](cli.md#tour-and-presentation) for stop
 fields. Recording is a local CLI operation; no remote recording/file-writing
 tool is added.
@@ -513,6 +517,10 @@ into `persistFile: true` with both preconditions and top-level `content` to save
 workspace `.md` file and card together. In this mode, `data` accepts only the `rendered` preview;
 refused saves change neither. See [the file-save contract](http-api.md#nodes).
 
+For Markdown nodes, `canvas_node` actions `add` and `update` accept
+`data: { display: "heading" | "card" }`. Heading display uses the existing title
+and content as a frameless section label, without changing pin membership.
+
 For Mermaid nodes, `canvas_node` actions `add` and `update` accept
 `data: { fit: "contain" | "none" }`. Contain is the default, shrinking overflow
 uniformly; none keeps 100% with scrolling. Use Open as site for 100% without