@marver-design/marver 0.27.0 → 0.28.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.
- package/CHANGELOG.md +195 -0
- package/README.md +9 -4
- package/dist/{anchor-check-ChdDqL5z.mjs → anchor-check-PHUOFj1N.mjs} +1 -1
- package/dist/{audio-Dw1lfMdb.mjs → audio-DX4POHAj.mjs} +39 -4
- package/dist/{board-tree-DRioF94d.mjs → board-tree-BXR8dw4b.mjs} +3 -1
- package/dist/{boards-DlTcpF47.mjs → boards-BeWtjGUM.mjs} +50 -5
- package/dist/boards-EH2onUXM.mjs +995 -0
- package/dist/{build-DZnFysGU.mjs → build-BsAyLMT1.mjs} +9 -22
- package/dist/{capture-vadKjuCo.mjs → capture-DdZ6xgoz.mjs} +92 -30
- package/dist/cli.mjs +56 -21
- package/dist/{collab-Dxg2trOK.mjs → collab-BEAcXrBb.mjs} +1 -1
- package/dist/{comments-DxOkCSNE.mjs → comments-CrBHPEQl.mjs} +4 -4
- package/dist/config-BezZTiov.mjs +182 -0
- package/dist/conn-BMiHS42T.mjs +222 -0
- package/dist/connectors-MR9d-EBP.mjs +290 -0
- package/dist/{context-HQ4Giw58.mjs → context-BUnFiyA3.mjs} +3 -3
- package/dist/{daemon-BSA0lV8d.mjs → daemon-C5dg2R-V.mjs} +2188 -183
- package/dist/{dev-eQJhWsqg.mjs → dev-D7YS7iT2.mjs} +25 -14
- package/dist/{init-COD0x48i.mjs → init-WE5lQkQL.mjs} +8 -3
- package/dist/jam-Cj5gBvwD.mjs +373 -0
- package/dist/{link-DDXZVGtv.mjs → link-BFFRgrMt.mjs} +4 -4
- package/dist/listener-DdLEM79A.mjs +80 -0
- package/dist/{ls-D7O1G505.mjs → ls-BZ5TAtd5.mjs} +1 -1
- package/dist/{manifest-Nl3KSVOk.mjs → manifest-DPZ3WNg_.mjs} +2 -2
- package/dist/{marks-CWM3WJjc.mjs → marks-Dyn6tmjp.mjs} +3 -3
- package/dist/{marks-CKgzucHZ.mjs → marks-Kmdab_5w.mjs} +3 -3
- package/dist/{marver-id-gate-BjF6v4bT.mjs → marver-id-gate-D-R0hSt_.mjs} +1 -1
- package/dist/perf-Cn5LiRaY.mjs +1319 -0
- package/dist/perf-jam-QxD_UnzN.mjs +635 -0
- package/dist/permit-DDa6wqOs.mjs +187 -0
- package/dist/plugin-C_0yb-Fq.mjs +5089 -0
- package/dist/{poster-Bx83ZYVK.mjs → poster-DHi6I1fO.mjs} +1 -1
- package/dist/{profile-Bh5Y5zpW.mjs → profile-jIS6BcAs.mjs} +1 -1
- package/dist/{publish-bakes-aljgm45S.mjs → publish-bakes-r4PEZuPl.mjs} +3 -3
- package/dist/{queue-CAM_vNmX.mjs → queue-c-6aTHEz.mjs} +164 -25
- package/dist/{recover-t9Pno3u9.mjs → recover-nrLEVLyJ.mjs} +2 -2
- package/dist/{serve-C8rVheYk.mjs → serve-Dp3nHstu.mjs} +3 -3
- package/dist/{session-BAaJsK5c.mjs → session-DyVE7cCk.mjs} +1 -1
- package/dist/{share-W5H3BNvP.mjs → share-Ce4tP7ji.mjs} +1 -1
- package/dist/{shot-LFhC-WYD.mjs → shot-BrRtqaiS.mjs} +34 -8
- package/dist/{shot-DoHLl6ig.mjs → shot-DBWN8hPP.mjs} +1 -1
- package/dist/sizes-wjXDev3b.mjs +139 -0
- package/dist/{slots-DCDo3N0x.mjs → slots-CFNnegCc.mjs} +8 -1
- package/dist/speech-worker.mjs +23 -3
- package/dist/{sync-BQVlHZpx.mjs → sync-CQdGARJ9.mjs} +1 -1
- package/dist/transport-C5FnY9ni.mjs +203 -0
- package/dist/{work-BroFwnup.mjs → work-BYWD_1Zf.mjs} +3 -3
- package/dist/{work-Bp1p39kq.mjs → work-DJxH7cCX.mjs} +1 -1
- package/docs/jam-session.md +42 -16
- package/docs/live-jam.md +92 -10
- package/docs/performance.md +197 -35
- package/package.json +1 -1
- package/src/client/content/video.tsx +10 -2
- package/src/client/shell/App.tsx +10 -3
- package/src/client/shell/Comments.tsx +5 -3
- package/src/client/shell/ContextMenu.tsx +5 -3
- package/src/client/shell/JamSurface.tsx +56 -21
- package/src/client/shell/LockedApp.tsx +3 -0
- package/src/client/shell/Play.tsx +4 -2
- package/src/client/shell/Tip.tsx +3 -1
- package/src/client/shell/api.ts +47 -20
- package/src/client/shell/app-bridge.ts +254 -0
- package/src/client/shell/app-perf.ts +92 -0
- package/src/client/shell/canvas/Canvas.tsx +115 -22
- package/src/client/shell/canvas/FrameNode.tsx +10 -6
- package/src/client/shell/canvas/admission.ts +23 -8
- package/src/client/shell/canvas/ctl.ts +6 -0
- package/src/client/shell/canvas/sleep.ts +57 -17
- package/src/client/shell/canvas/updates.ts +2 -1
- package/src/client/shell/icons.tsx +1 -0
- package/src/client/shell/inset.ts +44 -0
- package/src/client/shell/jam-capture.ts +113 -33
- package/src/client/shell/jam-keys.ts +40 -9
- package/src/client/shell/jam-lane.tsx +14 -5
- package/src/client/shell/jam-lines.ts +66 -9
- package/src/client/shell/jam-panel.tsx +61 -6
- package/src/client/shell/jam-queue.ts +50 -8
- package/src/client/shell/jam-session.tsx +53 -4
- package/src/client/shell/jam-surface-parts.tsx +6 -3
- package/src/client/shell/jam-ui.tsx +6 -1
- package/src/client/shell/jam-voice-wait.ts +21 -0
- package/src/client/shell/jam-voice.ts +62 -15
- package/src/client/shell/main.tsx +14 -1
- package/src/client/shell/marks-ui.tsx +5 -3
- package/src/client/shell/marver-app.ts +21 -0
- package/src/client/shell/perf-run-probe.ts +34 -0
- package/src/client/shell/perf-run.ts +70 -0
- package/src/client/shell/perf.ts +11 -0
- package/src/client/shell/recorder.ts +45 -3
- package/src/client/shell/store.ts +52 -24
- package/src/client/shell/styles.css +65 -17
- package/src/client/shell/tidy.ts +3 -2
- package/src/client/shell/unsaved.ts +81 -0
- package/src/client/shell/whiteout-probes.ts +141 -0
- package/src/shared/app-api.ts +205 -0
- package/src/shared/app-perf.ts +308 -0
- package/src/shared/approval.ts +20 -0
- package/src/shared/events.ts +1 -1
- package/src/shared/logo-sniff.ts +86 -0
- package/src/shared/machine.ts +132 -0
- package/src/shared/perf-run.ts +177 -0
- package/templates/AGENTS-embedded.md +31 -1
- package/templates/AGENTS-studio.md +31 -1
- package/templates/instructions/boards.md +10 -2
- package/templates/instructions/jam.md +90 -0
- package/dist/bake-DM_uWgAA.mjs +0 -786
- package/dist/boards-CGg6piKF.mjs +0 -342
- package/dist/perf-BWzQwZqj.mjs +0 -369
- package/dist/perf-BoDSkbEb.mjs +0 -429
- package/dist/perf-jam-D55U3FZK.mjs +0 -242
- package/dist/plugin-C-E7omsh.mjs +0 -2762
package/CHANGELOG.md
CHANGED
|
@@ -2,6 +2,201 @@
|
|
|
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.28.0 - 2026-10-29
|
|
6
|
+
|
|
7
|
+
### Highlights
|
|
8
|
+
|
|
9
|
+
- **Jam works in the coding-agent session you already have open.** Start a Jam session on the canvas and your @marver
|
|
10
|
+
tags and voice captures go to the Claude Code, Codex or Cursor session open in the repo, with its conversation,
|
|
11
|
+
tools, MCP servers, skills and subagents. Claude Code is woken through its inbox, idle or busy; Codex and Cursor take
|
|
12
|
+
the work at the end of their turn. The session takes a run with `npx marver jam next`, says one line with `jam say`
|
|
13
|
+
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,
|
|
14
|
+
read "Dispatching" until your session takes the run, then "Claude Code is working" (or Codex, Cursor); hover for
|
|
15
|
+
whose run it is.
|
|
16
|
+
The commands travel through signed files, so a sandbox that blocks localhost does not stop them. Nothing to set up:
|
|
17
|
+
`marver init`, `marver dev` and starting a Jam session write each tool's hooks (`.claude/settings.local.json`,
|
|
18
|
+
`.codex/hooks.json`, `.cursor/hooks.json`) - only Marver's own entries, never in a committed file - and a hook you
|
|
19
|
+
remove by hand stays removed ([Jam session](docs/jam-session.md), [Live Jam](docs/live-jam.md)).
|
|
20
|
+
- **One line per request, and the agent knows what it means.** A request arrives as one line that names it - "Live
|
|
21
|
+
Jam: new request from your Marver canvas - "Intro frame redesign" (1a2b3c4d) - run `npx marver jam next`" - and
|
|
22
|
+
`jam next` prints a short brief: your words, newest first, the frames it may edit and how to answer.
|
|
23
|
+
`design/AGENTS.md` gains a "Live Jam" section, so the agent expects these lines and takes them as your request
|
|
24
|
+
(Claude Code shows them as sent by another session). Two pings in a row are never the same - Claude Code drops a
|
|
25
|
+
message identical to the one before it - and the canvas writes the words, so an upgrade changes them at once.
|
|
26
|
+
- **Your Claude Code session dispatches, so it multitasks.** For each request, your session hands the run to a
|
|
27
|
+
background subagent of its own, with the request and what your conversation knows that matters. The subagent says
|
|
28
|
+
"On it", does the work and hands the run back itself, while your session is free again in seconds for the next
|
|
29
|
+
request. So captures run side by side: a Claude Code session holds up to 8 runs at once (`jam.sessionMax` caps it),
|
|
30
|
+
and runs your session holds no longer count against `jam.concurrency`. Codex and Cursor have no background
|
|
31
|
+
subagents: their session holds up to 3 runs and works them one after another. When you move a run elsewhere, the
|
|
32
|
+
session stops the subagent on it first.
|
|
33
|
+
- **Two requests on one frame: your session decides.** A request on a frame one of your session's runs is changing is
|
|
34
|
+
offered to your session at once, naming the run it overlaps. The session decides: send it to the subagent on that
|
|
35
|
+
frame - to do after, or fold in now - or make it a variant in a new frame beside it. Runs of different runners still
|
|
36
|
+
never share a frame; a run your session lets go of waits for the frame and keeps what it made, so whoever takes it
|
|
37
|
+
over can finish it.
|
|
38
|
+
- **"Put this next to slide 01" just works.** `npx marver boards place <board> <scene/frame> --after|--before
|
|
39
|
+
<scene/frame>` puts a frame next to another and moves the frames after it to make room; in a deck it plays right
|
|
40
|
+
after it, and it stays there when the canvas lays the board out again. Jam runs use it, or `boards pin` on an empty
|
|
41
|
+
board (each with `--run <handle>`), instead of asking for the board file. Every board writer - `place`, `pin`, the
|
|
42
|
+
canvas's own save, and the sidebar's rename, status and drag - now takes the board's lock, so none overwrites
|
|
43
|
+
another.
|
|
44
|
+
- **Two ways to stop a capture.** `E` stops it and queues it: its tile goes from Capturing to Sending to Queued or
|
|
45
|
+
working, and nothing opens, asks you to confirm or moves the canvas. `⇧E` (Stop to review) opens its read-back as
|
|
46
|
+
before, to check it and add notes first. Both are on the capture bar, Stop first. `J` during a capture stops it to
|
|
47
|
+
review.
|
|
48
|
+
- **When your session cannot take a run, a copy of it does**, with the same context: runs Marver starts for Claude Code
|
|
49
|
+
and Codex copy your session (`--fork-session`, `exec fork`) - a person's session of this repo, never a headless one;
|
|
50
|
+
a transcript over 12 MB runs fresh. Its tile reads "Claude Code is working" like any run; hover it to see that a copy
|
|
51
|
+
of your session runs it, and why: yours was busy, yours let it go, yours was idle (Codex, Cursor), or the Jam session
|
|
52
|
+
had ended. Outside a Jam session, tags go to such a copy.
|
|
53
|
+
- **Full power by default.** Runs Marver starts for Claude Code, Codex and Cursor have the shell inside the tool's own
|
|
54
|
+
sandbox, your MCP servers and skills: Claude Code through `marver jam permit` (MCP, skills, web, subagents and edits
|
|
55
|
+
in the repo allowed; keys unreadable; nothing asked), Codex through its own automatic reviewer (`--approve-for-me`).
|
|
56
|
+
The start sheet's switches turn MCP and skills, your session's context and collaborators' comments on or off.
|
|
57
|
+
- **Only your own words reach any runner** by default: other people's comments are left out of what it reads
|
|
58
|
+
(`jam.others: true` brings them back, labelled), also in briefs frozen before this version.
|
|
59
|
+
|
|
60
|
+
### Changed
|
|
61
|
+
|
|
62
|
+
- **"Looks good" typed as a note settles the review.** A More-work note that is only an approval - "looks good",
|
|
63
|
+
"looks good to me", "lgtm", "perfect", "great job", "nice work", "thanks", "👍" and a few more - counts as Looks good
|
|
64
|
+
instead of running the capture again. Anything longer, another language or "yes, thanks" goes to the agent as More
|
|
65
|
+
work: a request is never lost as approval.
|
|
66
|
+
- **The session record goes to your session too**, like any request, instead of straight to a copy.
|
|
67
|
+
- **A capture waits longer for your last words**: 15 s after you stop (3 s before), and longer while the speech engine
|
|
68
|
+
is still answering, a minute at most - a long last phrase, or the engine starting up, no longer drops them. With the
|
|
69
|
+
microphone on and nothing heard, the capture says its words may be incomplete.
|
|
70
|
+
- **A capture's pictures no longer time out** on a canvas that has just started: they render on a lane of their own
|
|
71
|
+
instead of waiting behind the bake of every frame ("no picture of ... - it took over 20 s").
|
|
72
|
+
- **The review's before and after sit on a dark stage**, as in play mode, with white captions and more room.
|
|
73
|
+
- **Runs your session took and went quiet on** are marked stalled after 15 minutes: give it back, run it in the
|
|
74
|
+
background, or drop it. A restart of `marver dev` keeps every run a session holds.
|
|
75
|
+
- **In the Mac app the floating chrome sits right under the strip**: the sidebar, toolbar, play pills and Jam panels
|
|
76
|
+
take the larger of the edge and the top inset instead of their sum.
|
|
77
|
+
- `jam.capture` is no longer used: `E` queues a capture, `⇧E` reviews it.
|
|
78
|
+
- **A request that needs a file no run is given asks you** which file and why, instead of failing with "the agent did
|
|
79
|
+
not answer" - "put this variant next to slide 01" once asked for the board file. Tag @marver in its thread to go on.
|
|
80
|
+
- **A tile waiting on a busy frame says so**: "Waits for 01-slide", and the request's status in its thread names the
|
|
81
|
+
run that holds it, instead of "Queued · next" - "next" is now the next request that can start.
|
|
82
|
+
- **A request with no frame no longer waits for everything else.** A capture made on an empty board, a comment on the
|
|
83
|
+
board itself and the session record go to your session beside your other runs; they used to wait until nothing else
|
|
84
|
+
ran, and hold back every request after them. With no session taking the work they still run alone, and the tile says
|
|
85
|
+
so: "Waits to run alone", and "Waits · a run goes alone first" on the requests behind one. With your session full,
|
|
86
|
+
"Waits · your session is full", until it has room or you choose another session.
|
|
87
|
+
- **A review opens at its full size.** A capture's before and after pictures load as soon as it is ready to review, so
|
|
88
|
+
its review opens as wide as they need instead of opening narrow and then growing.
|
|
89
|
+
|
|
90
|
+
### Fixed
|
|
91
|
+
|
|
92
|
+
- **Clicking an "Asks you" tile shows its question again.** Since `E` moves nothing, the canvas was often far from the
|
|
93
|
+
capture and its thread opened off screen; the canvas now comes to the thread, as a notification does, and a thread
|
|
94
|
+
this board cannot show opens the capture's panel with the question and a field to answer it.
|
|
95
|
+
- **A crash in the speech engine no longer takes the canvas down.** The engine runs in a process of its own, and a
|
|
96
|
+
stretch of audio with no samples is never handed to it ("Invalid input shape {0,128}" aborted a canvas mid-session).
|
|
97
|
+
- The start sheet's Codex hint shows only when no session is connected.
|
|
98
|
+
|
|
99
|
+
### Upgrading
|
|
100
|
+
|
|
101
|
+
`npm install @marver-design/marver@latest`, then `npx marver init` to refresh the agent instructions (`design/AGENTS.md`
|
|
102
|
+
gains the Live Jam section; `instructions/jam.md` the runs from the canvas, the dispatch, two runs on one frame, and
|
|
103
|
+
`boards place`). `jam.sessionMax` left unset now means 8 for Claude Code and 3 for Codex and Cursor. Restart each
|
|
104
|
+
canvas; a coding-agent session already open connects at its next message.
|
|
105
|
+
|
|
106
|
+
## 0.27.2 - 2026-10-24
|
|
107
|
+
|
|
108
|
+
0.27.1 was never published: its changes ship here, with 0.27.2's.
|
|
109
|
+
|
|
110
|
+
### Highlights
|
|
111
|
+
|
|
112
|
+
- **Leaving a canvas that holds unsaved work asks first, in every browser.** Chrome asked only while a Jam capture was
|
|
113
|
+
being recorded, or on a stopped tab with board edits. Now a reload or a close asks whenever the page holds anything
|
|
114
|
+
the canvas does not have yet: a capture recording, finishing or not taken by the canvas yet, a board edit not saved
|
|
115
|
+
yet (a save on its way or one that failed), frame heights not written yet, or words typed and not sent (a comment, a
|
|
116
|
+
Jam edit or note). A drag is not work until it drops. The page's own reload when its canvas comes back still goes
|
|
117
|
+
without asking: it saves first. Chrome asks only on a page you have clicked or typed in since it loaded. A published
|
|
118
|
+
canvas is unchanged.
|
|
119
|
+
- **A canvas opens where you left it.** A board you reload opens on the view you had, kept per project and board,
|
|
120
|
+
unless the link names a selection: then it fits that, as before. The view is kept a second after it settles, and at
|
|
121
|
+
once when the tab is hidden or closed; a tab hidden while the view is still flying (a fit, a zoom) keeps where it was
|
|
122
|
+
going. A published canvas still opens on the whole board.
|
|
123
|
+
- **A board's first frame starts about 0.3 s sooner.** It waited 0.35 s after the board mounted, for the camera's first
|
|
124
|
+
fit to land. It now starts as the fit sets off, chosen on where the fit will land, so it is the same frame. On a real
|
|
125
|
+
project's boards the frames were ready 0.1-0.4 s sooner (a 30-frame board: 1.3 s to 1.0 s), and nothing moved more
|
|
126
|
+
([Performance](docs/performance.md#making-a-board-faster) has the numbers).
|
|
127
|
+
- **`npx marver perf run <board>`: a board measured the same way every time.** With `marver dev` running, the canvas's
|
|
128
|
+
own headless Chrome loads the board once to warm up, then measures a load, a fit and three gestures (zoom in, zoom
|
|
129
|
+
out, a pan that turns back), and writes one line: load to settled, frame times (p50, p95, frames over 33 ms), the
|
|
130
|
+
heap's peak, and whether the run is valid, with the first reason it is not. A run is read-only: its page sends no
|
|
131
|
+
write but its own records and the frames' sleep textures, and the dev server refuses any other. `--slow` throttles
|
|
132
|
+
the CPU 4x, `--repeat <n>` runs it up to 5 times. `npx marver perf --runs` compares a run only with runs made the
|
|
133
|
+
same way (board, Chrome, machine, power, `--slow`): the latest against the last with the same inputs and the last
|
|
134
|
+
with others; `--against <run>` against one you name. Your agent is told to use it before and after a change
|
|
135
|
+
([Headless runs](docs/performance.md#headless-runs)).
|
|
136
|
+
- **The Mac app needs this version.** With it, the app asks before a close, a quit or a reload loses unsaved work,
|
|
137
|
+
follows the canvas's theme, shows its View and Jam items in the menu bar and wears its logo on the tab; app 0.2 also
|
|
138
|
+
runs the canvas full height under its transparent tabs. A 0.27.0 canvas opens in the app with a lesser
|
|
139
|
+
guard and none of the rest. In a browser, none of the app's side runs.
|
|
140
|
+
|
|
141
|
+
### Changed
|
|
142
|
+
|
|
143
|
+
- **Reduce Transparency and Increase Contrast make the glass opaque.** With either set in macOS, the sidebar, the
|
|
144
|
+
toolbar and every glass surface take a solid fill and a plain border; with Increase Contrast the dimmer text takes the
|
|
145
|
+
full ink. Chrome reads the same settings.
|
|
146
|
+
- **`npx marver perf --loads` names each board as the sidebar does, and its two clocks apart.** A load is headed by its
|
|
147
|
+
board's title ("v1 lo-fi - Mac and iPhone", not "Journey"; `--json` keeps the board's name). A settled load says
|
|
148
|
+
`still from` its last move, where it said `quiet 0.0 s · last move 1.3 s`, which read as a contradiction. `slowest`
|
|
149
|
+
is now `slowest to settle`: a frame's time to its last height, which can come after `all ready`, each frame's first
|
|
150
|
+
render. [Performance](docs/performance.md) says what settled means.
|
|
151
|
+
- **The logo ladder reads `public/favicon.png` and `public/favicon.ico` too, and a logo must be one.** After
|
|
152
|
+
`share.logo`, `design/logo.svg|png`, `public/logo.svg|png` and `public/favicon.svg`, `marver build` now tries
|
|
153
|
+
`public/favicon.png` and `public/favicon.ico`. A candidate counts only as a regular file inside the repo (never a
|
|
154
|
+
symlink, even one inside it) of at most 256 KB whose bytes are an SVG, a PNG or an ICO; its type comes from its
|
|
155
|
+
bytes, so a PNG named `.svg` is published as `logo.png`. A `share.logo` that fails is ignored with one line saying
|
|
156
|
+
why; 0.27.0 followed a symlink and copied `share.logo` from anywhere. A gated `marver serve` shows a `logo.ico` before
|
|
157
|
+
sign-in, as it does a `.svg` or `.png`.
|
|
158
|
+
- **`marver ls` names a canvas as the canvas does**: `share.name` when you set one ("TMS broker", not "tms-broker"),
|
|
159
|
+
else the folder name.
|
|
160
|
+
|
|
161
|
+
### Added
|
|
162
|
+
|
|
163
|
+
- **The Mac app's bridge.** In the app, a canvas page tells the app what it holds, so closing its tab, quitting or
|
|
164
|
+
reloading asks first or waits; its theme, which the app's tabs follow; and its View and Jam menu items with their
|
|
165
|
+
keys. When its tab is shown again it reads its marks, its agents' work, the Jam queue and its board again; when the
|
|
166
|
+
app stops trusting it, it lets go of the microphone at once, one still opening too. Each canvas's file in
|
|
167
|
+
`~/.marver/running/` lists `bridge` and `inset` among its features.
|
|
168
|
+
- **Under the Mac app's tabs (app 0.2).** When the app places a canvas full height under its transparent strip,
|
|
169
|
+
everything you read or click stays below the strip: the sidebar, the toolbar, the Jam panel and sheet, play's pills
|
|
170
|
+
and the stopped banner sit 44 px lower; the selection bar, tooltips and menus never go above it; a fit, a frame's
|
|
171
|
+
focus and play's stage leave its room. The canvas's own ground and dots run under the strip and fade out just below
|
|
172
|
+
it, and a frame under it counts as out of view (not marked seen, not named to Jam). Everywhere else (Chrome, a
|
|
173
|
+
published canvas, `marver shot`, app 0.1) nothing moves.
|
|
174
|
+
- **`npx marver perf --crashes`, `--flashes` and `--machine` read the Mac app's records** (app 0.2), joined to this
|
|
175
|
+
repo's board loads: each canvas crash with its board, whether its load had settled and the last gesture before it;
|
|
176
|
+
each flash you marked with ⌃⌥F, with the gesture it fell in and the GPU process's events around it, the white-out
|
|
177
|
+
candidates apart; the machine profiles by host. In the app the canvas tells the recorder its gestures, so its
|
|
178
|
+
records land on the right board load. `--days <n>` (14) for these and `--runs` ([The Mac app's
|
|
179
|
+
half](docs/performance.md#the-mac-apps-half)).
|
|
180
|
+
- **`GET /__mv/logo`** on `marver dev`: the canvas's logo, from the same ladder and checks as `marver build`, signed
|
|
181
|
+
when the app asks, so the app shows a logo only from the canvas it verified.
|
|
182
|
+
|
|
183
|
+
### Fixed
|
|
184
|
+
|
|
185
|
+
- **"Back - your edits were saved" every time.** A tab that held an edit when its canvas stopped saved it when the
|
|
186
|
+
canvas came back and reloaded, but said so only when the save it made on the way back carried the edit. Often the
|
|
187
|
+
ordinary autosave had already saved it (a frame still in your hand when the canvas answered, then dropped) and the
|
|
188
|
+
reloaded page said nothing, though the edit was on disk. Now every board save between the stop and the reload
|
|
189
|
+
counts, and a lost one too: the reloaded page then says the file won, or that the board is gone.
|
|
190
|
+
- **A tab whose canvas came back reloads only once its heights are saved.** A heights write that failed on the way back
|
|
191
|
+
was dropped by the reload. Now the tab reloads once every height has reached `_sizes.json`; until then it works as
|
|
192
|
+
live and sends them again.
|
|
193
|
+
|
|
194
|
+
### Upgrading
|
|
195
|
+
|
|
196
|
+
`npm install @marver-design/marver@latest`, then `npx marver init` to refresh the agent instructions (they compare a
|
|
197
|
+
board before and after a change with `npx marver perf run`, and say what counts as a logo). Restart each canvas: the
|
|
198
|
+
Mac app sees the bridge only on a canvas started from this version.
|
|
199
|
+
|
|
5
200
|
## 0.27.0 - 2026-10-23
|
|
6
201
|
|
|
7
202
|
### Highlights
|
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
|
|
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
|
-
**
|
|
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
|
|
|
@@ -116,7 +118,8 @@ The same glow, driven from the terminal. When your agent takes a request, it cre
|
|
|
116
118
|
| `npx marver work …` | Working glow from the terminal: `start <scene/frame …>` · `done … \| --all` (prints the canvas link) · `list` |
|
|
117
119
|
| `npx marver link <scene/frame \| scene ...>` | The canvas link that lands on those frames - their board, selected and in view (needs `dev` running) |
|
|
118
120
|
| `npx marver shot <frame ...> \| --scene <name> \| --all [--scale 1-4] [--json]` | Render frames headless and print the PNG paths (needs `dev` running); a scene is one browser, several frames at a time; 2x by default |
|
|
119
|
-
| `npx marver perf [--loads \| --jam] [--json]` | What the canvas did lately: each edit's reloads; `--loads` each board load (time to settled, how many moves and why, the slowest frames, errors); `--jam` Jam's timings ([Performance](docs/performance.md)) |
|
|
121
|
+
| `npx marver perf [--loads \| --jam \| --runs] [--json]` | What the canvas did lately: each edit's reloads; `--loads` each board load (time to settled, how many moves and why, the slowest frames, errors); `--jam` Jam's timings; `--runs` the headless runs compared ([Performance](docs/performance.md)) |
|
|
122
|
+
| `npx marver perf run <board> [--slow] [--repeat n]` | Measure a board the same way every time - a load, a fit, a zoom and a pan in the canvas's own headless Chrome, read-only - so you or your agent can compare before and after a change (needs `dev` running; [Headless runs](docs/performance.md#headless-runs)) |
|
|
120
123
|
| `npx marver boards [--json]` | The sidebar as the files say it is: folders and sub-folders, boards in reading order with their title, type, status, `order` and description, the landing board; a board file that is not valid JSON says why, with line and column |
|
|
121
124
|
| `npx marver boards new <name> [--folder f] [--type t]` | A board in its type's starting layout - a feature's spec, lo-fi and hi-fi bands, a start board rendering `context/` |
|
|
122
125
|
| `npx marver folders add <module ...>` | Add a typed folder: `start`, `features`, `surfaces`, `projects`, `feedback`, `context`, `decks`, `archive` |
|
|
@@ -124,6 +127,8 @@ The same glow, driven from the terminal. When your agent takes a request, it cre
|
|
|
124
127
|
|
|
125
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.
|
|
126
129
|
|
|
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. In a browser none of this runs; browsers ask before a reload or a close loses unsaved work too.
|
|
131
|
+
|
|
127
132
|
## Shortcuts
|
|
128
133
|
|
|
129
134
|
**Canvas** - two-finger scroll pans · pinch or ctrl/cmd+scroll zooms · space+drag pans from anywhere · click empty canvas deselects / exits interact.
|
|
@@ -147,7 +152,7 @@ The same glow, driven from the terminal. When your agent takes a request, it cre
|
|
|
147
152
|
|
|
148
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.
|
|
149
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.
|
|
150
|
-
- **Name your canvas**: `share: { name: "Your App" }` in `design/config.ts` titles the gate, labels the brand pill, 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.
|
|
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 and the Mac app's tab wear it.
|
|
151
156
|
- **Uninstall**: delete `design/`, remove the dependency. (If `init` patched your tsconfig `exclude`, revert that one line.)
|
|
152
157
|
|
|
153
158
|
## Status
|
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
import {
|
|
1
|
+
import { a as frameUrl, d as withBrowser, n as MOUNTED, o as manifestFrame, s as planShot } from "./shot-BrRtqaiS.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 {
|
|
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
|
|
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
|
-
}
|
|
257
|
+
});
|
|
223
258
|
});
|
|
224
259
|
return;
|
|
225
260
|
}
|
|
@@ -189,6 +189,8 @@ const readTitle = (v) => {
|
|
|
189
189
|
};
|
|
190
190
|
/** Title Case off a slug - the display when no title is set ("old-stuff" → "Old Stuff"). */
|
|
191
191
|
const humanize = (s) => s.replace(/-/g, " ").replace(/(^|\s)\S/g, (c) => c.toUpperCase());
|
|
192
|
+
/** What a board, folder or scene is called on screen: its title, else its humanized slug. */
|
|
193
|
+
const labelOf = (name, title) => title ?? humanize(name);
|
|
192
194
|
const rank = (o) => typeof o === "number" && Number.isFinite(o) ? o : Infinity;
|
|
193
195
|
/** A folder's title, description and type, present only when set. */
|
|
194
196
|
const folderExtras = (it) => ({
|
|
@@ -361,4 +363,4 @@ function folderMap(t) {
|
|
|
361
363
|
return out;
|
|
362
364
|
}
|
|
363
365
|
//#endregion
|
|
364
|
-
export {
|
|
366
|
+
export { resolveType as A, KIND_FOLDERS as C, readReason as D, readCapability as E, readStatusWord as O, HAS_STATUS as S, knownType as T, validateWire as _, buildTree as a, DECISIONS as b, folderMap as c, isBoardFile as d, isBoardName as f, readTitle as g, readDescription as h, archiveLast as i, settableStatuses as j, readType as k, framesOn as l, parseFolders as m, BOARD_NAME as n, flatten as o, labelOf as p, FOLDERS_FILE as r, folderEntries as s, ALL_SCENES as t, humanize as u, wireKids as v, PROPOSED_PUBLISH as w, FOLDER_MODULES as x, BOARD_TYPES as y };
|
|
@@ -1,8 +1,8 @@
|
|
|
1
1
|
import { r as NAME } from "./cli.mjs";
|
|
2
|
-
import { a as
|
|
3
|
-
import {
|
|
4
|
-
import { _ as STATUS_LABEL, d as annotateBoards, h as PHASE_LABEL, s as scanFrames } from "./manifest-
|
|
5
|
-
import { resolveTargets } from "./link-
|
|
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
|
+
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-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 };
|