@marver-design/marver 0.27.2 → 0.29.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (91) hide show
  1. package/CHANGELOG.md +160 -0
  2. package/README.md +6 -4
  3. package/dist/{anchor-check-gkxkPAIv.mjs → anchor-check-DhlpKl2K.mjs} +1 -1
  4. package/dist/{audio-Dw1lfMdb.mjs → audio-DX4POHAj.mjs} +39 -4
  5. package/dist/{boards-BqUqKNW8.mjs → boards-BeWtjGUM.mjs} +49 -4
  6. package/dist/boards-EH2onUXM.mjs +995 -0
  7. package/dist/{build-VgNg4rr8.mjs → build-CWbrb2bl.mjs} +9 -5
  8. package/dist/{capture-vadKjuCo.mjs → capture-DEtM4qm5.mjs} +259 -34
  9. package/dist/cli.mjs +40 -19
  10. package/dist/{comments-YEU1Zhv9.mjs → comments-XNhMmSSu.mjs} +4 -4
  11. package/dist/config-BezZTiov.mjs +182 -0
  12. package/dist/conn-BMiHS42T.mjs +222 -0
  13. package/dist/connectors-DekQvKt9.mjs +292 -0
  14. package/dist/{context-Ccjrhr1J.mjs → context-BUnFiyA3.mjs} +2 -2
  15. package/dist/{daemon-Dc9AH0M3.mjs → daemon-Sc_z8gT6.mjs} +2209 -205
  16. package/dist/{dev-ri6nAlRp.mjs → dev-DWBKQhxf.mjs} +31 -15
  17. package/dist/{init-W0nxR1OY.mjs → init-CYlFaRzG.mjs} +7 -2
  18. package/dist/jam-Cj5gBvwD.mjs +373 -0
  19. package/dist/{link-CdTgn94Y.mjs → link-BFFRgrMt.mjs} +3 -3
  20. package/dist/listener-DdLEM79A.mjs +80 -0
  21. package/dist/logo-CXY-1yrn.mjs +305 -0
  22. package/dist/{ls-BZ5TAtd5.mjs → ls-NqmePKOf.mjs} +1 -1
  23. package/dist/{manifest-aFyDmL8C.mjs → manifest-DPZ3WNg_.mjs} +1 -1
  24. package/dist/{marks-CnCCfAbD.mjs → marks-BnNANic9.mjs} +22 -3
  25. package/dist/{marks-BF9pNEgH.mjs → marks-DBp3h1Mc.mjs} +3 -6
  26. package/dist/{marver-id-gate-D-R0hSt_.mjs → marver-id-gate-vBLb_Icb.mjs} +1 -1
  27. package/dist/{perf-DkAUFT6W.mjs → perf-Denssrko.mjs} +45 -27
  28. package/dist/{perf-jam-BaH3Lg0m.mjs → perf-jam-CLkERSHo.mjs} +9 -2
  29. package/dist/permit-DDa6wqOs.mjs +187 -0
  30. package/dist/{plugin-B8UghYuF.mjs → plugin-DqoZB-D6.mjs} +849 -789
  31. package/dist/{poster-BNgafWMK.mjs → poster-CrsjqhY4.mjs} +1 -1
  32. package/dist/{profile-jIS6BcAs.mjs → profile-B1FKOM1e.mjs} +1 -1
  33. package/dist/{publish-bakes-38Nja78p.mjs → publish-bakes-DW-NDgU2.mjs} +3 -3
  34. package/dist/{queue-CAM_vNmX.mjs → queue-DeSQm24g.mjs} +189 -35
  35. package/dist/{recover-B8AiI29B.mjs → recover-GtJ9UDAB.mjs} +2 -2
  36. package/dist/{serve-Dp3nHstu.mjs → serve-DQv3Ti6X.mjs} +8 -4
  37. package/dist/{session-BAaJsK5c.mjs → session-VDJfXEEm.mjs} +1 -1
  38. package/dist/{share-Ce4tP7ji.mjs → share-Bu_kuOKL.mjs} +1 -1
  39. package/dist/{shot-CMQgMVZm.mjs → shot-DBWN8hPP.mjs} +1 -1
  40. package/dist/{shot-Ch24tiMO.mjs → shot-T04Ixrvq.mjs} +7 -6
  41. package/dist/sizes-wjXDev3b.mjs +139 -0
  42. package/dist/{slots-CFNnegCc.mjs → slots-Dn4Onb0V.mjs} +101 -3
  43. package/dist/speech-worker.mjs +23 -3
  44. package/dist/{sync-CQdGARJ9.mjs → sync-CMozOwZ0.mjs} +1 -1
  45. package/dist/transport-C5FnY9ni.mjs +203 -0
  46. package/dist/{work-Bxz-ObF3.mjs → work-BYWD_1Zf.mjs} +3 -3
  47. package/dist/{work-CNhFF9pU.mjs → work-DJxH7cCX.mjs} +1 -1
  48. package/docs/boards-and-folders.md +11 -0
  49. package/docs/jam-session.md +52 -18
  50. package/docs/live-jam.md +95 -10
  51. package/docs/performance.md +1 -1
  52. package/docs/publish.md +7 -0
  53. package/package.json +1 -1
  54. package/src/client/shell/Comments.tsx +5 -4
  55. package/src/client/shell/ContextMenu.tsx +5 -4
  56. package/src/client/shell/JamSurface.tsx +135 -29
  57. package/src/client/shell/Play.tsx +16 -4
  58. package/src/client/shell/api.ts +7 -3
  59. package/src/client/shell/app-bridge.ts +11 -3
  60. package/src/client/shell/comments-store.ts +14 -0
  61. package/src/client/shell/goto.ts +4 -3
  62. package/src/client/shell/icons.tsx +1 -0
  63. package/src/client/shell/jam-capture.ts +136 -37
  64. package/src/client/shell/jam-keys.ts +170 -18
  65. package/src/client/shell/jam-lane.tsx +14 -5
  66. package/src/client/shell/jam-lines.ts +76 -10
  67. package/src/client/shell/jam-panel.tsx +58 -4
  68. package/src/client/shell/jam-queue.ts +55 -8
  69. package/src/client/shell/jam-session.tsx +55 -6
  70. package/src/client/shell/jam-state.ts +19 -4
  71. package/src/client/shell/jam-surface-parts.tsx +6 -3
  72. package/src/client/shell/jam-ui.tsx +10 -1
  73. package/src/client/shell/jam-voice-wait.ts +21 -0
  74. package/src/client/shell/jam-voice.ts +14 -5
  75. package/src/client/shell/live-picture.ts +134 -0
  76. package/src/client/shell/open-item.ts +83 -0
  77. package/src/client/shell/open-resolve.ts +50 -0
  78. package/src/client/shell/store.ts +6 -2
  79. package/src/client/shell/styles.css +29 -11
  80. package/src/client/shell/tidy.ts +3 -2
  81. package/src/client/stage/main.tsx +30 -8
  82. package/src/shared/app-api.ts +173 -3
  83. package/src/shared/app-perf.ts +4 -2
  84. package/src/shared/approval.ts +20 -0
  85. package/src/shared/events.ts +1 -1
  86. package/templates/AGENTS-embedded.md +28 -1
  87. package/templates/AGENTS-studio.md +28 -1
  88. package/templates/instructions/boards.md +7 -1
  89. package/templates/instructions/jam.md +94 -0
  90. package/dist/boards-BHKP5yhI.mjs +0 -342
  91. package/dist/live-Cgzsicwi.mjs +0 -4
package/CHANGELOG.md CHANGED
@@ -2,6 +2,166 @@
2
2
 
3
3
  Notable changes to `@marver-design/marver`. Format follows [Keep a Changelog](https://keepachangelog.com); versions follow semver.
4
4
 
5
+ ## 0.29.0 - 2026-10-31
6
+
7
+ ### Highlights
8
+
9
+ - **Your agent sees a capture's pictures.** A run was given the ids of a capture's pictures and no way to open them,
10
+ so no picture you took reached your agent. Each request now lists its pictures - the frame each shows and the file
11
+ to open, `design/.local/jam/pictures/<id>.png` - and `design/instructions/jam.md` tells the agent to open the ones it
12
+ needs. In a browser as in the Mac app.
13
+ - **The Mac app tells you when a canvas needs you.** A running canvas now tells Marver's Mac app (0.3) what waits on
14
+ you - a question from Marver, a capture ready to review, a run that failed or stalled - and whether an agent is
15
+ working or a Jam session runs, as it changes. The app counts it on the canvas's tab, hidden or not; with notices on,
16
+ a canvas you are not looking at sends one, and the Dock counts them all. A canvas on 0.28 or earlier shows none of
17
+ this in the app. In a browser nothing changes: the sidebar and the lane say it as before
18
+ ([What needs you](docs/boards-and-folders.md#what-is-new-what-needs-you)).
19
+ - **A notice opens what it names.** Click one in the Mac app and the canvas opens it on its board, where you can see
20
+ it: a question in its thread on the frame (Play is left, and comment pins you hid with `⇧C` come back for it), or,
21
+ when no frame on the board holds it, in a panel with a field to answer; a review in its review; a failed run with
22
+ Retry in view, a stalled one with its three choices (a stalled capture's or Jam session's on its tile in the lane,
23
+ on the board you are on). On a board locked to play, Play stays and the thread opens over it. An item that has moved
24
+ on opens as it is now - a resolved thread read-only - and one that is gone opens its board. Nothing moves while you
25
+ are capturing or have words you have not sent.
26
+ - **A picture in play is what you saw, in the Mac app.** With app 0.3, a capture's pictures in play - `I`, and the ones
27
+ it takes itself as you point and as it ends - are the stage as it was on your screen: a menu you opened, text you
28
+ typed, the comment pins. They are captioned "as you saw it" in the read-back and the review. One is taken once the
29
+ whole stage is in view with nothing over it and has shown its screen for a second (a device preset, a slide fitted
30
+ to the window); otherwise, in a browser, and whenever the app cannot take it, the picture is a fresh render of the
31
+ frame, as before ([Jam sessions](docs/jam-session.md)).
32
+
33
+ ### Added
34
+
35
+ - **A published canvas wears your logo in the browser's tab.** When your repo has a logo (`design/logo.svg`, or the
36
+ first logo file `marver build` finds), it is the only tab icon of the canvas and its sign-in page, so a browser tab -
37
+ and the Mac app's tab for a shared canvas - shows it rather than Marver's mark; without one, Marver's mark as before.
38
+ A canvas published before keeps Marver's mark until you build it again
39
+ ([Publishing](docs/publish.md#name-the-canvas)).
40
+ - `npx marver perf --jam` counts the Mac app's live pictures - kept, failed, rendered instead - and lists a capture
41
+ whose live pictures failed among what went wrong.
42
+
43
+ ### Changed
44
+
45
+ - **Opening a capture's thread shows it where you can see it.** Clicking an "Asks you" tile, or Open thread on a
46
+ capture, opens its thread on the frame: Play is left and comment pins you hid with `⇧C` come back, where it used to
47
+ open unseen under them. With no frame on the board for it, it opens in the capture's panel as before, and on a board
48
+ locked to play, in that panel over Play; a resolved thread opens read-only in the thread panel.
49
+
50
+ ### Fixed
51
+
52
+ - **A canvas in a subfolder of a git repository keeps Jam's hook files out of commits.** In a monorepo, or a
53
+ `canvas/` folder beside your app, `.codex/hooks.json` and `.cursor/hooks.json` showed up in `git status` as new
54
+ files: their line in `.git/info/exclude` named them from the repository's top, not from the canvas's folder. It
55
+ names the folder now.
56
+
57
+ ### Upgrading
58
+
59
+ `npm install @marver-design/marver@latest`, then `npx marver init` to refresh the agent instructions
60
+ (`instructions/jam.md`: a capture's pictures are files to open, and what a live one shows). Restart each canvas; the
61
+ Mac app picks up what a canvas can do as it starts. A published canvas wears your logo once you build and deploy it
62
+ again.
63
+
64
+ ## 0.28.0 - 2026-10-29
65
+
66
+ ### Highlights
67
+
68
+ - **Jam works in the coding-agent session you already have open.** Start a Jam session on the canvas and your @marver
69
+ tags and voice captures go to the Claude Code, Codex or Cursor session open in the repo, with its conversation,
70
+ tools, MCP servers, skills and subagents. Claude Code is woken through its inbox, idle or busy; Codex and Cursor take
71
+ the work at the end of their turn. The session takes a run with `npx marver jam next`, says one line with `jam say`
72
+ and hands its reply back with `jam done`, and the canvas posts it in the thread. A capture's tile, and a tag's status,
73
+ read "Dispatching" until your session takes the run, then "Claude Code is working" (or Codex, Cursor); hover for
74
+ whose run it is.
75
+ The commands travel through signed files, so a sandbox that blocks localhost does not stop them. Nothing to set up:
76
+ `marver init`, `marver dev` and starting a Jam session write each tool's hooks (`.claude/settings.local.json`,
77
+ `.codex/hooks.json`, `.cursor/hooks.json`) - only Marver's own entries, never in a committed file - and a hook you
78
+ remove by hand stays removed ([Jam session](docs/jam-session.md), [Live Jam](docs/live-jam.md)).
79
+ - **One line per request, and the agent knows what it means.** A request arrives as one line that names it - "Live
80
+ Jam: new request from your Marver canvas - "Intro frame redesign" (1a2b3c4d) - run `npx marver jam next`" - and
81
+ `jam next` prints a short brief: your words, newest first, the frames it may edit and how to answer.
82
+ `design/AGENTS.md` gains a "Live Jam" section, so the agent expects these lines and takes them as your request
83
+ (Claude Code shows them as sent by another session). Two pings in a row are never the same - Claude Code drops a
84
+ message identical to the one before it - and the canvas writes the words, so an upgrade changes them at once.
85
+ - **Your Claude Code session dispatches, so it multitasks.** For each request, your session hands the run to a
86
+ background subagent of its own, with the request and what your conversation knows that matters. The subagent says
87
+ "On it", does the work and hands the run back itself, while your session is free again in seconds for the next
88
+ request. So captures run side by side: a Claude Code session holds up to 8 runs at once (`jam.sessionMax` caps it),
89
+ and runs your session holds no longer count against `jam.concurrency`. Codex and Cursor have no background
90
+ subagents: their session holds up to 3 runs and works them one after another. When you move a run elsewhere, the
91
+ session stops the subagent on it first.
92
+ - **Two requests on one frame: your session decides.** A request on a frame one of your session's runs is changing is
93
+ offered to your session at once, naming the run it overlaps. The session decides: send it to the subagent on that
94
+ frame - to do after, or fold in now - or make it a variant in a new frame beside it. Runs of different runners still
95
+ never share a frame; a run your session lets go of waits for the frame and keeps what it made, so whoever takes it
96
+ over can finish it.
97
+ - **"Put this next to slide 01" just works.** `npx marver boards place <board> <scene/frame> --after|--before
98
+ <scene/frame>` puts a frame next to another and moves the frames after it to make room; in a deck it plays right
99
+ after it, and it stays there when the canvas lays the board out again. Jam runs use it, or `boards pin` on an empty
100
+ board (each with `--run <handle>`), instead of asking for the board file. Every board writer - `place`, `pin`, the
101
+ canvas's own save, and the sidebar's rename, status and drag - now takes the board's lock, so none overwrites
102
+ another.
103
+ - **Two ways to stop a capture.** `E` stops it and queues it: its tile goes from Capturing to Sending to Queued or
104
+ working, and nothing opens, asks you to confirm or moves the canvas. `⇧E` (Stop to review) opens its read-back as
105
+ before, to check it and add notes first. Both are on the capture bar, Stop first. `J` during a capture stops it to
106
+ review.
107
+ - **When your session cannot take a run, a copy of it does**, with the same context: runs Marver starts for Claude Code
108
+ and Codex copy your session (`--fork-session`, `exec fork`) - a person's session of this repo, never a headless one;
109
+ a transcript over 12 MB runs fresh. Its tile reads "Claude Code is working" like any run; hover it to see that a copy
110
+ of your session runs it, and why: yours was busy, yours let it go, yours was idle (Codex, Cursor), or the Jam session
111
+ had ended. Outside a Jam session, tags go to such a copy.
112
+ - **Full power by default.** Runs Marver starts for Claude Code, Codex and Cursor have the shell inside the tool's own
113
+ sandbox, your MCP servers and skills: Claude Code through `marver jam permit` (MCP, skills, web, subagents and edits
114
+ in the repo allowed; keys unreadable; nothing asked), Codex through its own automatic reviewer (`--approve-for-me`).
115
+ The start sheet's switches turn MCP and skills, your session's context and collaborators' comments on or off.
116
+ - **Only your own words reach any runner** by default: other people's comments are left out of what it reads
117
+ (`jam.others: true` brings them back, labelled), also in briefs frozen before this version.
118
+
119
+ ### Changed
120
+
121
+ - **"Looks good" typed as a note settles the review.** A More-work note that is only an approval - "looks good",
122
+ "looks good to me", "lgtm", "perfect", "great job", "nice work", "thanks", "👍" and a few more - counts as Looks good
123
+ instead of running the capture again. Anything longer, another language or "yes, thanks" goes to the agent as More
124
+ work: a request is never lost as approval.
125
+ - **The session record goes to your session too**, like any request, instead of straight to a copy.
126
+ - **A capture waits longer for your last words**: 15 s after you stop (3 s before), and longer while the speech engine
127
+ is still answering, a minute at most - a long last phrase, or the engine starting up, no longer drops them. With the
128
+ microphone on and nothing heard, the capture says its words may be incomplete.
129
+ - **A capture's pictures no longer time out** on a canvas that has just started: they render on a lane of their own
130
+ instead of waiting behind the bake of every frame ("no picture of ... - it took over 20 s").
131
+ - **The review's before and after sit on a dark stage**, as in play mode, with white captions and more room.
132
+ - **Runs your session took and went quiet on** are marked stalled after 15 minutes: give it back, run it in the
133
+ background, or drop it. A restart of `marver dev` keeps every run a session holds.
134
+ - **In the Mac app the floating chrome sits right under the strip**: the sidebar, toolbar, play pills and Jam panels
135
+ take the larger of the edge and the top inset instead of their sum.
136
+ - `jam.capture` is no longer used: `E` queues a capture, `⇧E` reviews it.
137
+ - **A request that needs a file no run is given asks you** which file and why, instead of failing with "the agent did
138
+ not answer" - "put this variant next to slide 01" once asked for the board file. Tag @marver in its thread to go on.
139
+ - **A tile waiting on a busy frame says so**: "Waits for 01-slide", and the request's status in its thread names the
140
+ run that holds it, instead of "Queued · next" - "next" is now the next request that can start.
141
+ - **A request with no frame no longer waits for everything else.** A capture made on an empty board, a comment on the
142
+ board itself and the session record go to your session beside your other runs; they used to wait until nothing else
143
+ ran, and hold back every request after them. With no session taking the work they still run alone, and the tile says
144
+ so: "Waits to run alone", and "Waits · a run goes alone first" on the requests behind one. With your session full,
145
+ "Waits · your session is full", until it has room or you choose another session.
146
+ - **A review opens at its full size.** A capture's before and after pictures load as soon as it is ready to review, so
147
+ its review opens as wide as they need instead of opening narrow and then growing.
148
+
149
+ ### Fixed
150
+
151
+ - **Clicking an "Asks you" tile shows its question again.** Since `E` moves nothing, the canvas was often far from the
152
+ capture and its thread opened off screen; the canvas now comes to the thread, as a notification does, and a thread
153
+ this board cannot show opens the capture's panel with the question and a field to answer it.
154
+ - **A crash in the speech engine no longer takes the canvas down.** The engine runs in a process of its own, and a
155
+ stretch of audio with no samples is never handed to it ("Invalid input shape {0,128}" aborted a canvas mid-session).
156
+ - The start sheet's Codex hint shows only when no session is connected.
157
+
158
+ ### Upgrading
159
+
160
+ `npm install @marver-design/marver@latest`, then `npx marver init` to refresh the agent instructions (`design/AGENTS.md`
161
+ gains the Live Jam section; `instructions/jam.md` the runs from the canvas, the dispatch, two runs on one frame, and
162
+ `boards place`). `jam.sessionMax` left unset now means 8 for Claude Code and 3 for Codex and Cursor. Restart each
163
+ canvas; a coding-agent session already open connects at its next message.
164
+
5
165
  ## 0.27.2 - 2026-10-24
6
166
 
7
167
  0.27.1 was never published: its changes ship here, with 0.27.2's.
package/README.md CHANGED
@@ -40,7 +40,7 @@ Frames appear on the canvas the moment the files land. That's the loop.
40
40
 
41
41
  ## The canvas
42
42
 
43
- - **Frames, scenes, boards.** Frames are screens, scenes group them (`design/scenes/<scene>/<frame>.tsx`), boards arrange them. Agents write `design/boards/<name>.json` (a frame list is enough); switch boards at the top of the sidebar. Every frame goes on the board it belongs to, and a frame that belongs to two goes on both (`npx marver boards pin <board> <scene/frame ...>`); a frame on no board is listed apart, under Not on a board. Right-click any board, scene, or frame in the sidebar to copy its path - the exact string to paste to your agent - and rename or drag-reorder boards from there too. Boards can live in folders, two levels deep - a folder holds boards and folders, a sub-folder holds boards: right-click the Boards header (or its `+`) for a new folder, a folder for a new one inside it, name it inline, drag boards in and out at either level (the seam shows exactly where a release lands, indented with the level) and folders among boards or into a folder; agents do the same by writing `"folder": "<name>"` on a board and `design/boards/_folders.json` for empty, ranked or nested folders (a sub-folder names its `"parent"`; `npx marver boards` prints the tree). The [boards and folders guide](docs/boards-and-folders.md) has every move. Boards, folders and scenes take a `title` - any name you like, "MVP", "UI", "Checkout (v2) 🛒" - while their file, key and directory stay the slug agents address; Rename in the sidebar edits the title. Every board wears an icon for its type - start, feature, surface, project, feedback, context, deck, archive - its own or its folder's, and feature boards wear a status read from the project's `context/`. Every object takes a one-sentence `description` (project in `design/config.ts`, boards and folders in their JSON, a scene's first `_brief.md` line, `meta.description` on a frame) and `design/manifest.json` carries them all - a new agent session orients in one read.
43
+ - **Frames, scenes, boards.** Frames are screens, scenes group them (`design/scenes/<scene>/<frame>.tsx`), boards arrange them. Agents write `design/boards/<name>.json` (a frame list is enough); switch boards at the top of the sidebar. Every frame goes on the board it belongs to, and a frame that belongs to two goes on both (`npx marver boards pin <board> <scene/frame ...>`; `npx marver boards place <board> <scene/frame> --after <scene/frame>` puts one next to another); a frame on no board is listed apart, under Not on a board. Right-click any board, scene, or frame in the sidebar to copy its path - the exact string to paste to your agent - and rename or drag-reorder boards from there too. Boards can live in folders, two levels deep - a folder holds boards and folders, a sub-folder holds boards: right-click the Boards header (or its `+`) for a new folder, a folder for a new one inside it, name it inline, drag boards in and out at either level (the seam shows exactly where a release lands, indented with the level) and folders among boards or into a folder; agents do the same by writing `"folder": "<name>"` on a board and `design/boards/_folders.json` for empty, ranked or nested folders (a sub-folder names its `"parent"`; `npx marver boards` prints the tree). The [boards and folders guide](docs/boards-and-folders.md) has every move. Boards, folders and scenes take a `title` - any name you like, "MVP", "UI", "Checkout (v2) 🛒" - while their file, key and directory stay the slug agents address; Rename in the sidebar edits the title. Every board wears an icon for its type - start, feature, surface, project, feedback, context, deck, archive - its own or its folder's, and feature boards wear a status read from the project's `context/`. Every object takes a one-sentence `description` (project in `design/config.ts`, boards and folders in their JSON, a scene's first `_brief.md` line, `meta.description` on a frame) and `design/manifest.json` carries them all - a new agent session orients in one read.
44
44
  - **Devices view.** Hotkeys `1`-`5` (or the Devices menu) size every frame to mobile / tablet / laptop / monitor / tv to sweep your breakpoints; `0` restores your own layout exactly. Widths live in `design/config.ts`.
45
45
  - **Prototype links.** `data-goto="scene/frame"` on any element links frames into a walkable prototype - across boards, too.
46
46
  - **Five ways to view a board.** The canvas (frames on a plane), the board (the same, tidy), **present** (`p`: a full-screen clickable walkthrough - `data-goto` navigates, arrows step, `[` / `]` cycle variants, laser, comments, theme and device pickers in the toolbar), **focus** (one frame as a document - the reading preset for specs), and **slides** (a deck). A published board names its landing view; a frame deep link opens straight into it.
@@ -95,7 +95,9 @@ Tag `@marver` in a comment and your own coding agent picks it up - reads the thr
95
95
 
96
96
  The trust boundary is hard: only comments written on the owner's machine trigger (a device-bound ledger - a drive-by comment on a published canvas cannot start work), the agent runs locked down (each CLI with its shell removed or OS-sandboxed - the per-agent table is in the guide), and every reply carries provenance: which agent ran it, as which dev user, on which model when the agent names one. Marver ships no AI; the agent that acts is the one you already run. The [Live Jam guide](docs/live-jam.md) has the config block, every agent's jail, and what to check when a mention does nothing.
97
97
 
98
- **Captures and sessions.** Or skip the typing: press `S`, point at things, click through the prototype and say what is wrong, then `E`. A capture records your words (transcribed on your machine - the audio never leaves it), every click, pick and note, and pictures of the frames you touched at the size you saw them, and your agent works from that. Captures line up in a lane along the bottom - queued, working, ready to review - and each comes back with before and after pictures: `⏎` looks good, `⇧⏎` more work. `J` runs a whole review as a session and ends with a written record of it in `context/sessions/`. The [Jam sessions guide](docs/jam-session.md) has the keys and the settings.
98
+ **Your own session does it (0.28).** Start a Jam session and nothing else: while it runs, your tags and captures go to the Claude Code, Codex or Cursor session you already have open in the repo - with its conversation, tools, MCP servers and skills. Claude Code hands each run to a background subagent of its own, so it stays free and several run at once. When it cannot take a run, a copy of it does, with the same context and the same power. `marver init` and `marver dev` connect your sessions with local hooks, never committed; Codex asks you to trust them once (`/hooks`). The [Live Jam guide](docs/live-jam.md#your-own-session-takes-the-work-028) has the details.
99
+
100
+ **Captures and sessions.** Or skip the typing: press `S`, point at things, click through the prototype and say what is wrong, then `E` - it goes straight to your agent (`⇧E` stops it to look it over first). A capture records your words (transcribed on your machine - the audio never leaves it), every click, pick and note, and pictures of the frames you touched at the size you saw them, and your agent works from that. Captures line up in a lane along the bottom - queued, working, ready to review - and each comes back with before and after pictures: `⏎` looks good, `⇧⏎` more work. `J` runs a whole review as a session and ends with a written record of it in `context/sessions/`. The [Jam sessions guide](docs/jam-session.md) has the keys and the settings.
99
101
 
100
102
  ## Working state
101
103
 
@@ -125,7 +127,7 @@ The same glow, driven from the terminal. When your agent takes a request, it cre
125
127
 
126
128
  **Where the canvas runs.** Each canvas on your Mac takes one of twenty fixed ports, localhost:4805 to localhost:4824 - usually the same one each time - and prints its link; `npx marver ls` lists them all. `--port <n>`, or a `port` in `design/config.ts` (other than the old 5199), gives a canvas a port of its own instead. Because an address is reused by whichever canvas starts there next, a tab left open after its canvas stopped says so, and how to bring it back, and keeps your unsaved edits until its own canvas is back, and a local canvas runs no service workers.
127
129
 
128
- **The Mac app.** In Marver's Mac app a canvas tells the app what it holds, so closing its tab, quitting or reloading asks before losing unsaved work, and the app follows its theme and shows its View and Jam items in the menu bar. In a browser none of this runs; browsers ask before a reload or a close loses unsaved work too.
130
+ **The Mac app.** In Marver's Mac app a canvas tells the app what it holds, so closing its tab, quitting or reloading asks before losing unsaved work, and the app follows its theme and shows its View and Jam items in the menu bar. Since 0.29 (app 0.3) it also tells the app what needs you - a question, a capture to review, a run that failed or stalled - which the app counts on the canvas's tab and, with notices on, sends as a notice that opens it; and a capture's pictures in play are your screen as you saw it ([what needs you](docs/boards-and-folders.md#what-is-new-what-needs-you)). In a browser none of this runs; browsers ask before a reload or a close loses unsaved work too.
129
131
 
130
132
  ## Shortcuts
131
133
 
@@ -150,7 +152,7 @@ The same glow, driven from the terminal. When your agent takes a request, it cre
150
152
 
151
153
  - **Next.js**: supported with one caveat - frames render in Vite, outside Next. `next/font` CSS variables are undefined inside frames (give font tokens a fallback chain), `next/image`/`next/link` should be plain `img`/`data-goto` in frames, and Server Components cannot run there. `init` writes the specifics into `design/AGENTS.md` when it detects Next.
152
154
  - **Upgrade**: `npm i -D @marver-design/marver@latest && npx marver init`. The canvas tells you when a new version is out (one anonymous registry check per day, cached in `design/.local/`; `MARVER_NO_UPDATE_CHECK=1` disables), and warns when your `design/instructions/` predate the installed package. Re-running init refreshes the managed files (AGENTS.md, `design/instructions/`) - your edits to them are detected and preserved; when both you and a release changed a file, the fresh version is staged at `design/.local/latest/` for you (or your agent) to merge. Everything else in `design/` is yours and never touched.
153
- - **Name your canvas**: `share: { name: "Your App" }` in `design/config.ts` titles the gate, labels the brand pill, names the canvas in `marver ls`, and tags every powered-by link. Unset, the gate falls back to your `package.json` name and the canvas shell to the directory name - `app` inside most containers. Its logo is the first of `share.logo`, `design/logo.svg|png`, `public/logo.svg|png` and `public/favicon.svg|png|ico` that is a real file in the repo (never a symlink) of at most 256 KB, an SVG, PNG or ICO by its bytes; the gate page and the Mac app's tab wear it.
155
+ - **Name your canvas**: `share: { name: "Your App" }` in `design/config.ts` titles the gate, labels the brand pill, names the canvas in `marver ls`, and tags every powered-by link. Unset, the gate falls back to your `package.json` name and the canvas shell to the directory name - `app` inside most containers. Its logo is the first of `share.logo`, `design/logo.svg|png`, `public/logo.svg|png` and `public/favicon.svg|png|ico` that is a real file in the repo (never a symlink) of at most 256 KB, an SVG, PNG or ICO by its bytes; the gate page, a published canvas's browser tab (built with 0.29 or later) and the Mac app's tab wear it.
154
156
  - **Uninstall**: delete `design/`, remove the dependency. (If `init` patched your tsconfig `exclude`, revert that one line.)
155
157
 
156
158
  ## Status
@@ -1,4 +1,4 @@
1
- import { a as frameUrl, d as withBrowser, n as MOUNTED, o as manifestFrame, s as planShot } from "./shot-Ch24tiMO.mjs";
1
+ import { a as frameUrl, d as withBrowser, n as MOUNTED, o as manifestFrame, s as planShot } from "./shot-T04Ixrvq.mjs";
2
2
  //#region src/server/anchor-check.ts
3
3
  /**
4
4
  * The anchor check (spec 26, Part 6): `comments new --on|--at`, `comments move` and a Live Jam re-pin
@@ -1,7 +1,8 @@
1
1
  import { modelPaths, modelsReady } from "./speech-models-DomiLQcY.mjs";
2
2
  import { createRequire } from "node:module";
3
- import { Worker } from "node:worker_threads";
3
+ import { fileURLToPath } from "node:url";
4
4
  import { randomBytes } from "node:crypto";
5
+ import { fork } from "node:child_process";
5
6
  import { WebSocketServer } from "ws";
6
7
  const TICKET_MS = 3e4;
7
8
  /** A segment on the socket: a capture's audio or a session's talk, numbered (`<owner>~<n>`). */
@@ -40,6 +41,41 @@ const speechLive = {};
40
41
  /** The model holds about a gigabyte while loaded: with no capture for this long, the worker lets it go
41
42
  * (the next capture loads it again in under a second). */
42
43
  const IDLE_MS = 6e5;
44
+ /** The engine runs in a process of its own (27 Oct): ONNX raises its errors as C++ exceptions, which no thread can
45
+ * catch - in a worker thread one aborted the whole canvas mid-session. In its own process the same error ends only
46
+ * transcription; the service sees it go (`exit`), tells its captures they may be incomplete, and starts a fresh one
47
+ * for the next capture. Typed arrays cross as they are (`serialization: 'advanced'`). */
48
+ function engine(url, paths) {
49
+ const child = fork(fileURLToPath(url), [], {
50
+ serialization: "advanced",
51
+ execArgv: [],
52
+ stdio: [
53
+ "ignore",
54
+ "ignore",
55
+ "inherit",
56
+ "ipc"
57
+ ],
58
+ env: {
59
+ ...process.env,
60
+ MARVER_SPEECH_PATHS: JSON.stringify(paths)
61
+ }
62
+ });
63
+ return {
64
+ on: (ev, f) => child.on(ev, f),
65
+ postMessage: (m) => {
66
+ try {
67
+ if (child.connected) child.send(m);
68
+ } catch {}
69
+ },
70
+ terminate: async () => {
71
+ child.kill();
72
+ },
73
+ unref: () => {
74
+ child.unref();
75
+ child.channel?.unref?.();
76
+ }
77
+ };
78
+ }
43
79
  function createSpeech(opts = {}) {
44
80
  const ready_ = opts.modelsReady ?? modelsReady;
45
81
  /** talk segments: their start on the page clock (ms), so their words get the time they were said */
@@ -84,8 +120,7 @@ function createSpeech(opts = {}) {
84
120
  return null;
85
121
  }
86
122
  if (!await ready_()) return null;
87
- const url = opts.workerUrl ?? new URL(import.meta.url.endsWith(".ts") ? "./speech-worker.ts" : "./speech-worker.mjs", import.meta.url);
88
- const w = new Worker(url, { workerData: { paths: modelPaths() } });
123
+ const w = engine(opts.workerUrl ?? new URL(import.meta.url.endsWith(".ts") ? "./speech-worker.ts" : "./speech-worker.mjs", import.meta.url), modelPaths());
89
124
  w.unref();
90
125
  return new Promise((resolve) => {
91
126
  let settled = false;
@@ -219,7 +254,7 @@ function createSpeech(opts = {}) {
219
254
  capture: id,
220
255
  offset,
221
256
  pcm
222
- }, [pcm.buffer]);
257
+ });
223
258
  });
224
259
  return;
225
260
  }
@@ -1,8 +1,8 @@
1
1
  import { r as NAME } from "./cli.mjs";
2
- import { a as checkRealDirs, d as readMembership, f as readRegistry, i as checkBoardsDir, n as addFolders, r as boardFields, s as listBoardFiles, u as pinFrames } from "./boards-BHKP5yhI.mjs";
2
+ import { a as checkBoardsDir, c as listBoardFiles, d as pinFrames, f as placeFrame, m as readRegistry, n as addFolders, o as checkRealDirs, p as readMembership, r as boardFields } from "./boards-EH2onUXM.mjs";
3
3
  import { A as resolveType, E as readCapability, T as knownType, a as buildTree, c as folderMap, f as isBoardName, o as flatten, u as humanize, x as FOLDER_MODULES, y as BOARD_TYPES } from "./board-tree-BXR8dw4b.mjs";
4
- import { _ as STATUS_LABEL, d as annotateBoards, h as PHASE_LABEL, s as scanFrames } from "./manifest-aFyDmL8C.mjs";
5
- import { resolveTargets } from "./link-CdTgn94Y.mjs";
4
+ import { _ as STATUS_LABEL, d as annotateBoards, h as PHASE_LABEL, s as scanFrames } from "./manifest-DPZ3WNg_.mjs";
5
+ import { resolveTargets } from "./link-BFFRgrMt.mjs";
6
6
  import { existsSync, mkdirSync, writeFileSync } from "node:fs";
7
7
  import { join } from "node:path";
8
8
  //#region src/cli/boards.ts
@@ -198,6 +198,51 @@ function boardsPin(root, board, targets) {
198
198
  const live = scanFrames(root).frames.map((f) => f.id);
199
199
  return pinFrames(root, board, resolveTargets(live, targets).all, live);
200
200
  }
201
+ /** `--run <handle>` (F1): a Live Jam run's new frames are given to that run first, so no other runner gets them while it
202
+ * works (the canvas refuses when another run or your chat agent has one). */
203
+ async function toRun(root, frames, opts) {
204
+ if (typeof opts.run !== "string" || !opts.run) throw new Error("name the run: --run <handle> (r-xxxxxxxx.N, from jam next)");
205
+ const { ownConn } = await import("./jam-Cj5gBvwD.mjs");
206
+ const { request } = await import("./transport-C5FnY9ni.mjs");
207
+ for (const frame of frames) {
208
+ const r = await request(root, ownConn(root, process.env, typeof opts.as === "string" ? opts.as : void 0), "own", {
209
+ handle: opts.run,
210
+ frame
211
+ });
212
+ if (r.ok === false) throw new Error(String(r.error ?? "the canvas did not give it to that run"));
213
+ }
214
+ }
215
+ /** `marver boards pin <board> <scene/frame ...> --run <handle>` (F5): pinned as `boards pin` does, each frame given to that
216
+ * Live Jam run first - how a run that reserves no frame puts what it made on an empty board, where nothing is to place it beside. */
217
+ async function boardsPinRun(root, board, targets, opts) {
218
+ if (!targets.length) throw new Error("name the frames: boards pin <board> <scene/frame | scene ...>");
219
+ const live = scanFrames(root).frames.map((f) => f.id);
220
+ const frames = resolveTargets(live, targets).all;
221
+ await toRun(root, frames, opts);
222
+ return pinFrames(root, board, frames, live);
223
+ }
224
+ /** `marver boards place <board> <scene/frame> --after|--before <scene/frame> [--run <handle>]` (F1): a frame next to
225
+ * another, the frames after it moved right to make room - what "put this next to slide 01" needs, with no board file
226
+ * edited by hand. `--run`: a Live Jam run's new frame (a variant) is given to that run first, so no other runner gets it
227
+ * while it works (the canvas refuses when another run or your chat agent has it). */
228
+ async function boardsPlace(root, board, targets, opts) {
229
+ const after = typeof opts.after === "string" ? opts.after : void 0, before = typeof opts.before === "string" ? opts.before : void 0;
230
+ if (targets.length !== 1) throw new Error("name one frame to place: boards place <board> <scene/frame> --after <scene/frame>");
231
+ if (!!after === !!before) throw new Error("say where: --after <scene/frame> or --before <scene/frame> (one of them)");
232
+ const manifest = scanFrames(root);
233
+ const live = manifest.frames.map((f) => f.id);
234
+ const one = (raw) => {
235
+ const r = resolveTargets(live, [raw]);
236
+ if (r.exact.length !== 1 || r.all.length !== 1) throw new Error(`"${raw}" is not one frame - name a frame (<scene>/<name>), not a scene`);
237
+ return r.exact[0];
238
+ };
239
+ const frame = one(targets[0]), anchor = one(after ?? before);
240
+ if (opts.run !== void 0) await toRun(root, [frame], opts);
241
+ const { loadConfig } = await import("./config-BezZTiov.mjs").then((n) => n.t);
242
+ const viewports = await loadConfig(root).then((c) => c.viewports, () => ({}));
243
+ const { readSizes } = await import("./sizes-wjXDev3b.mjs").then((n) => n.u);
244
+ return placeFrame(root, board, frame, after ? "after" : "before", anchor, manifest.frames, viewports, readSizes(root));
245
+ }
201
246
  /** `marver folders add <module...>` - the shared sidebar's typed folders (spec 20): start, features,
202
247
  * surfaces, projects, feedback, context, decks, archive. Appended; never renames or moves one. */
203
248
  function foldersAdd(root, modules) {
@@ -207,4 +252,4 @@ function foldersAdd(root, modules) {
207
252
  return addFolders(root, modules.map((m) => FOLDER_MODULES[m]));
208
253
  }
209
254
  //#endregion
210
- export { boardsCommand, boardsNew, boardsPin, foldersAdd };
255
+ export { boardsCommand, boardsNew, boardsPin, boardsPinRun, boardsPlace, foldersAdd };