@marver-design/marver 0.14.0 → 0.16.0

package/templates/instructions/slides.md

@@ -233,7 +233,11 @@ do to a slide. Gaps go on the parent (`gap`), never as per-child margins.
 - **Images** (`Img`): full-bleed with a scrim and a short assertion, or
   generously matted. Never a small image floating in space.
 - **Video** (`Video src poster`): the poster IS the slide at rest - choose
-  it like a photograph. Local sources require a poster.
+  it like a photograph. Omit `poster` and marver renders one from the clip
+  (`<clip>.poster.png` beside it, committed like any asset); author one when
+  the clip's opening is not the picture you want. In slides mode the
+  player mounts on its own; everywhere else a frame is live, the poster is
+  the play button (the same primitive serves screens and specs).
 - **Backgrounds are code**: theme-derived gradients, an oversized numeral, a
   clipped photo, one geometric accent. ONE effect per slide, and decoration
   never touches the evidence's contrast.

package/templates/instructions/welcome.md

@@ -61,7 +61,10 @@ without narrating into the void; your next message is the reveal.
    State your understanding of the product in 2-3 sentences, ask "did I get
    that right?" - then STOP: no further tool calls, end your turn, resume when
    the human replies. (Only exception: they explicitly asked for unattended
-   execution - assume, mark UNCONFIRMED, surface it first.)
+   execution - assume, mark UNCONFIRMED, surface it first.) Once they confirm,
+   write that understanding as one sentence into `description` in
+   design/config.ts - the project's line in design/manifest.json, the first
+   thing every later session reads.
 2. **Confirm the stack aloud - what detection ACTUALLY found.** Read AGENTS.md's
    UI line and design/theme.css and narrate the reality, for example: "Tailwind
    + shadcn/ui; brand tokens in <file>; design/theme.css imports them." No

package/templates/instructions/wireframe.md

@@ -14,6 +14,9 @@ lands on what is actually being decided.
 
 ## The rules (strict)
 
+0. **Every frame says what it is.** `meta.title` and `meta.description` (one sentence:
+   the screen's job, and "wireframe" while it is one) - the manifest carries them, so
+   a later session knows the lo-fi from the hi-fi without opening files.
 1. **Throwaway code is correct here.** Plain divs, inline layout, one file per frame.
    Do NOT build proper components for wireframes and do NOT touch the app's
    `components/` directory - lo-fi structure hardening into real components is how

package/dist/{comments-DHB_8BRa.mjs → comments-oYcZ3cE-.mjs}

@@ -4,8 +4,8 @@ import { i as readLog, r as listBoards, t as appendEvents } from "./comments-DZy
 import { a as syncOnce, i as loadCollab, n as connectClaim, r as connectToken, t as connect } from "./sync-BZaCWqK-.mjs";
 import { n as localProfile } from "./profile-BjAPAJSb.mjs";
 import { join } from "node:path";
-import { createInterface } from "node:readline";
 import { randomUUID } from "node:crypto";
+import { createInterface } from "node:readline";
 //#region src/cli/comments.ts
 /**
 * `marver comments <action>` - the collaboration CLI.