@marver-design/marver 0.15.0 → 0.16.1

package/templates/instructions/shape.md

@@ -60,7 +60,7 @@ detection is lexical), and declare `intent` on every content frame:
 ```tsx
 import { Doc, Row, Col, Md, Diagram, Img, Chart } from '@marver-design/marver/content'
 
-export const meta = { title: 'Checkout - how it works', intent: 'diagram' }
+export const meta = { title: 'Checkout - how it works', intent: 'diagram', description: 'The agreed flow, five screens - the source for the wireframes' }
 
 export default () => (
   <Doc layout="wide">

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.