@imgly/codesign-mcp 0.1.5 → 0.1.6

package/assets/prompts/evals-danskCatalogue.md

@@ -1,31 +0,0 @@
----
-name: evals-danskCatalogue
-description: Eval — generate a 5-page landscape furniture catalogue for "DANSK STUDIO" with image-left / typography-right pages and visually verify each one.
----
-
-Generate one landscape catalogue page per row for **5 products** from furniture designer **"DANSK STUDIO"**.
-
-Layout (each page):
-
-- 2-column grid.
-- **Left column:** full-bleed product photo. Fill it with an elegant Danish-furniture photo in black-and-white (no heavy contrast). Use a real image URL (search e.g. unsplash.com for "danish chair", "danish table", "wooden lamp") or, if no fetch is possible, a neutral grey placeholder fill — but try the real image first.
-- **Right column:** typography-led.
-  - **Product name** — large, light serif (e.g. Cormorant Garamond, EB Garamond, Playfair Display Regular).
-  - **Type category** (e.g. _LOUNGE CHAIR_, _DINING TABLE_) — small caps with generous tracking.
-  - **Description** — smaller weight, restrained line length.
-  - **Price in DKK** — anchored at the bottom of the right column.
-  - Lots of white space. No decorative elements. Don't make the text too small.
-
-Vibe: think Muuto, Hay, Frama. Clean, cold, confident. White background, near-black text. No color, no rules, no ornaments.
-
-Use placeholder furniture names, descriptions, and prices (DKK 1,200–18,000 range).
-
-Workflow:
-
-1. `engine.scene.create("VerticalStack")` once at the start, get the stack via `engine.block.findByType("stack")[0]`.
-2. Create 5 landscape pages and append each to the stack. Stash all five page IDs on `globalThis` so subsequent `design_exec` calls can find them.
-3. For each product, build the content with `design_exec`. Return only short status messages (`{ type: "text", text: "..." }`) — don't embed images or scene state in your return value.
-4. Verify each page individually with `design_capture({ blockId: <pageId> })` after meaningful changes. Don't move on to the next product until the current one looks right.
-5. End with five final `design_capture` calls — one per page — so the user sees all five spreads.
-
-When you're satisfied, summarize each page's typography (font sizes in pixels — confirm by reading them with `engine.block.getTextFontSizes(id, { unit: 'Pixel' })`).

package/assets/prompts/evals-exportRoundTrip.md

@@ -1,12 +0,0 @@
----
-name: evals-exportRoundTrip
-description: Eval — export writes a real artifact to the workspace and the returned URI is usable.
----
-
-Create a one-page A6 invitation card titled "Round-trip eval", set the title text to "Hello", then export the page as:
-
-1. A PDF (target: pdf, format: pdf)
-2. A PNG image (target: image, format: png, width 1024)
-3. The raw scene (target: scene, format: scene)
-
-For each export, report the `uri` and `bytes` from the response. End by calling `list` and confirming the new design is there.

package/assets/prompts/evals-inspectPriorCode.md

@@ -1,16 +0,0 @@
----
-name: evals-inspectPriorCode
-description: Eval — past code reveals patterns, not block ids; agent uses inspect to learn an approach and re-discovers ids in the current session.
----
-
-Create a design titled "Inspect eval". In a single `edit`, create one page (A6 portrait, white background) and one text block with the string "Hello" centered on it. Set the headline color via `engine.block.setColor(headline, 'fill/color/value', { r: 0.1, g: 0.1, b: 0.1, a: 1 })`. Remember the resulting revision id.
-
-Now start a fresh recovery flow as if a process restart happened: call `list` to find the design, then `history` to see the chain.
-
-Pick the revision you just created and call `inspect({ revision })`. Confirm the response contains a `code` field with the exact JS body you ran, AND a `note`, AND a `createdAt`. Confirm `code` includes the string `setColor` and the property name `'fill/color/value'`.
-
-Then make a new edit that re-applies the SAME color operation, but as a fork off the original — i.e., do NOT reuse the literal numeric block id from the past code. Inside your edit body, re-discover the headline block by walking `engine.scene.getPages()[0]` → `engine.block.getChildren(...)` and matching on type / contents. Pass the prior revision as `parent`. Set the headline color to the same `{ r: 0.1, g: 0.1, b: 0.1, a: 1 }` — but using a freshly-discovered block id.
-
-Confirm via `history` that the new revision is a sibling of the original (same parent), and via `preview` that the headline renders correctly.
-
-The point of the eval: the agent learned the operation pattern from the past `code` field (which API + which property name to use) without trusting the past block id, which would have been invalid in the new engine session.

package/assets/prompts/evals-listProjectFiles.md

@@ -1,6 +0,0 @@
----
-name: evals-listProjectFiles
-description: Eval — list files in /project (exercises ls tool)
----
-
-List the files in /project. Report names and byte sizes you see.

package/assets/prompts/evals-readAndExplainScript.md

@@ -1,6 +0,0 @@
----
-name: evals-readAndExplainScript
-description: Eval — read /project/script.sh and explain (exercises read tool + reasoning)
----
-
-Read /project/script.sh and explain in one sentence what it does. Quote the relevant line.

package/assets/prompts/evals-resumeAcrossRestart.md

@@ -1,15 +0,0 @@
----
-name: evals-resumeAcrossRestart
-description: Eval — resume work on a design after process restart by using list + history to re-ground, then edit with remembered parent.
----
-
-You previously created a design in this workspace but you don't remember anything specific about it — your process just started. The user says: "keep working on the wedding card; the title needs more breathing room."
-
-Steps:
-
-1. Call `handbook` if you haven't this session.
-2. Call `list`. Find the design titled "Wedding Card" (or closest match).
-3. Call `history({ revision: <that design's latestLeaf> })`. Read the notes.
-4. Decide which revision to continue from. Call `edit({ parent: <that revision>, code, note })` to widen the spacing around the title (increase margin, decrease font-size, or both).
-5. Call `preview({ blockId: <page> })` to verify the change.
-6. Report back: the new revision id and a one-sentence summary of what you changed.

package/assets/prompts/evals-rewindRecovery.md

@@ -1,10 +0,0 @@
----
-name: evals-rewindRecovery
-description: Eval — deliberately editing on top of an older revision creates a non-destructive fork.
----
-
-Create a design titled "Fork eval". Make three sequential edits, each setting the page background to a different color (e.g., red → blue → green; remember each revision id).
-
-Then deliberately fork: call `edit({ parent: <the FIRST revision's id>, code, note: "fork off the original" })` to set the background to yellow.
-
-Confirm via `list` that the design's `latestLeaf` is the new fork, and via `history({ revision: <fork revision> })` that the chain is root → fork (NOT root → blue → green → fork).

package/assets/prompts/evals-searchAcrossFiles.md

@@ -1,6 +0,0 @@
----
-name: evals-searchAcrossFiles
-description: Eval — grep across /project for a keyword (exercises grep tool + $1 arg)
----
-
-Use grep to find every line in /project containing "$1". Report matches as `<file>:<line>: <text>`. If $1 is empty, search for "items".

package/assets/prompts/evals-weddingCard.md

@@ -1,20 +0,0 @@
----
-name: evals-weddingCard
-description: Eval — design an elegant wedding invitation card and visually verify it with design_capture.
----
-
-Design an elegant wedding invitation card. Include:
-
-- Couple's names: **Alex & Jordan**
-- Wedding date: **June 14, 2026**
-- Venue: **Vineyard at Twin Hills**
-- A refined visual style — restrained typography, generous whitespace, soft palette.
-
-Workflow:
-
-1. Build the design with `design_exec`. Return only short status messages (`{ type: "text", text: "..." }`) — don't embed the full scene/PNG in your return value.
-2. After every meaningful change, visually verify with `design_capture({ blockId: <pageId> })` — `blockId` is required, pass the page you're working on (`engine.scene.getCurrentPage()` or whatever you stored after `engine.block.create("page")`). The PNG comes back inline.
-3. Iterate until the composition looks right.
-4. End with one final `design_capture({ blockId: <pageId> })` so the user sees the finished card.
-
-When you're satisfied, summarize what you built and how the typography is set (font sizes in pixels — confirm by reading them with `engine.block.getTextFontSizes(id, { unit: 'Pixel' })`).

package/assets/prompts/explain.md

@@ -1,6 +0,0 @@
----
-name: explain
-description: Explain code or a concept
----
-
-Explain $@ in plain language. Assume the reader knows JavaScript but is unfamiliar with this specific code/concept.

package/assets/prompts/review.md

@@ -1,6 +0,0 @@
----
-name: review
-description: Code review a piece of code or file path
----
-
-Review $@. Identify potential issues, code smells, or improvements. Be specific and actionable.

package/dist/frontmatter.d.ts

@@ -1,15 +0,0 @@
-/**
- * Result of parsing a markdown file with optional YAML-ish frontmatter at the
- * top. Only `name` and `description` keys are recognized; everything else in
- * the fence block is ignored. Values are trimmed of surrounding whitespace.
- *
- * `body` is the input with any frontmatter fence stripped. When no fence is
- * present, `body` equals the input verbatim.
- */
-export interface ParsedFrontmatter {
-    name?: string;
-    description?: string;
-    body: string;
-}
-export declare function parseFrontmatter(input: string): ParsedFrontmatter;
-//# sourceMappingURL=frontmatter.d.ts.map

package/dist/frontmatter.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"frontmatter.d.ts","sourceRoot":"","sources":["../src/frontmatter.ts"],"names":[],"mappings":"AAAA;;;;;;;GAOG;AACH,MAAM,WAAW,iBAAiB;IAChC,IAAI,CAAC,EAAE,MAAM,CAAC;IACd,WAAW,CAAC,EAAE,MAAM,CAAC;IACrB,IAAI,EAAE,MAAM,CAAC;CACd;AAID,wBAAgB,gBAAgB,CAAC,KAAK,EAAE,MAAM,GAAG,iBAAiB,CAqCjE"}

package/dist/frontmatter.js

@@ -1,46 +0,0 @@
-const FENCE = /^---\r?\n([\s\S]*?)\r?\n---\r?\n?/;
-export function parseFrontmatter(input) {
-    const match = input.match(FENCE);
-    if (!match)
-        return { body: input };
-    const block = match[1];
-    const body = input.slice(match[0].length);
-    const out = { body };
-    const lines = block.split(/\r?\n/);
-    for (let i = 0; i < lines.length; i++) {
-        const line = lines[i];
-        const m = line.match(/^([A-Za-z0-9_-]+)\s*:\s*(.*)$/);
-        if (!m)
-            continue;
-        const [, key, rawValue] = m;
-        const trimmed = rawValue.trim();
-        // YAML pipe block scalar: `description: |` followed by indented lines.
-        // Treat the indented continuation as the value (joined with single
-        // spaces; the description field is logically a paragraph). Folded
-        // scalars (`>`) get the same treatment.
-        let value = trimmed;
-        if (trimmed === '|' || trimmed === '>') {
-            const collected = [];
-            let j = i + 1;
-            while (j < lines.length) {
-                const nextLine = lines[j];
-                if (nextLine === '' || /^\s+/.test(nextLine)) {
-                    if (nextLine.trim().length > 0)
-                        collected.push(nextLine.trim());
-                    j++;
-                }
-                else {
-                    break;
-                }
-            }
-            value = collected.join(' ').trim();
-            i = j - 1;
-        }
-        if (key === 'name')
-            out.name = value;
-        else if (key === 'description')
-            out.description = value;
-    }
-    return out;
-}
-//# sourceMappingURL=frontmatter.js.map

package/dist/frontmatter.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"frontmatter.js","sourceRoot":"","sources":["../src/frontmatter.ts"],"names":[],"mappings":"AAcA,MAAM,KAAK,GAAG,mCAAmC,CAAC;AAElD,MAAM,UAAU,gBAAgB,CAAC,KAAa;IAC5C,MAAM,KAAK,GAAG,KAAK,CAAC,KAAK,CAAC,KAAK,CAAC,CAAC;IACjC,IAAI,CAAC,KAAK;QAAE,OAAO,EAAE,IAAI,EAAE,KAAK,EAAE,CAAC;IACnC,MAAM,KAAK,GAAG,KAAK,CAAC,CAAC,CAAC,CAAC;IACvB,MAAM,IAAI,GAAG,KAAK,CAAC,KAAK,CAAC,KAAK,CAAC,CAAC,CAAC,CAAC,MAAM,CAAC,CAAC;IAC1C,MAAM,GAAG,GAAsB,EAAE,IAAI,EAAE,CAAC;IACxC,MAAM,KAAK,GAAG,KAAK,CAAC,KAAK,CAAC,OAAO,CAAC,CAAC;IACnC,KAAK,IAAI,CAAC,GAAG,CAAC,EAAE,CAAC,GAAG,KAAK,CAAC,MAAM,EAAE,CAAC,EAAE,EAAE,CAAC;QACtC,MAAM,IAAI,GAAG,KAAK,CAAC,CAAC,CAAC,CAAC;QACtB,MAAM,CAAC,GAAG,IAAI,CAAC,KAAK,CAAC,+BAA+B,CAAC,CAAC;QACtD,IAAI,CAAC,CAAC;YAAE,SAAS;QACjB,MAAM,CAAC,EAAE,GAAG,EAAE,QAAQ,CAAC,GAAG,CAAC,CAAC;QAC5B,MAAM,OAAO,GAAG,QAAQ,CAAC,IAAI,EAAE,CAAC;QAChC,uEAAuE;QACvE,mEAAmE;QACnE,kEAAkE;QAClE,wCAAwC;QACxC,IAAI,KAAK,GAAG,OAAO,CAAC;QACpB,IAAI,OAAO,KAAK,GAAG,IAAI,OAAO,KAAK,GAAG,EAAE,CAAC;YACvC,MAAM,SAAS,GAAa,EAAE,CAAC;YAC/B,IAAI,CAAC,GAAG,CAAC,GAAG,CAAC,CAAC;YACd,OAAO,CAAC,GAAG,KAAK,CAAC,MAAM,EAAE,CAAC;gBACxB,MAAM,QAAQ,GAAG,KAAK,CAAC,CAAC,CAAC,CAAC;gBAC1B,IAAI,QAAQ,KAAK,EAAE,IAAI,MAAM,CAAC,IAAI,CAAC,QAAQ,CAAC,EAAE,CAAC;oBAC7C,IAAI,QAAQ,CAAC,IAAI,EAAE,CAAC,MAAM,GAAG,CAAC;wBAAE,SAAS,CAAC,IAAI,CAAC,QAAQ,CAAC,IAAI,EAAE,CAAC,CAAC;oBAChE,CAAC,EAAE,CAAC;gBACN,CAAC;qBAAM,CAAC;oBACN,MAAM;gBACR,CAAC;YACH,CAAC;YACD,KAAK,GAAG,SAAS,CAAC,IAAI,CAAC,GAAG,CAAC,CAAC,IAAI,EAAE,CAAC;YACnC,CAAC,GAAG,CAAC,GAAG,CAAC,CAAC;QACZ,CAAC;QACD,IAAI,GAAG,KAAK,MAAM;YAAE,GAAG,CAAC,IAAI,GAAG,KAAK,CAAC;aAChC,IAAI,GAAG,KAAK,aAAa;YAAE,GAAG,CAAC,WAAW,GAAG,KAAK,CAAC;IAC1D,CAAC;IACD,OAAO,GAAG,CAAC;AACb,CAAC","sourcesContent":["/**\n * Result of parsing a markdown file with optional YAML-ish frontmatter at the\n * top. Only `name` and `description` keys are recognized; everything else in\n * the fence block is ignored. Values are trimmed of surrounding whitespace.\n *\n * `body` is the input with any frontmatter fence stripped. When no fence is\n * present, `body` equals the input verbatim.\n */\nexport interface ParsedFrontmatter {\n  name?: string;\n  description?: string;\n  body: string;\n}\n\nconst FENCE = /^---\\r?\\n([\\s\\S]*?)\\r?\\n---\\r?\\n?/;\n\nexport function parseFrontmatter(input: string): ParsedFrontmatter {\n  const match = input.match(FENCE);\n  if (!match) return { body: input };\n  const block = match[1];\n  const body = input.slice(match[0].length);\n  const out: ParsedFrontmatter = { body };\n  const lines = block.split(/\\r?\\n/);\n  for (let i = 0; i < lines.length; i++) {\n    const line = lines[i];\n    const m = line.match(/^([A-Za-z0-9_-]+)\\s*:\\s*(.*)$/);\n    if (!m) continue;\n    const [, key, rawValue] = m;\n    const trimmed = rawValue.trim();\n    // YAML pipe block scalar: `description: |` followed by indented lines.\n    // Treat the indented continuation as the value (joined with single\n    // spaces; the description field is logically a paragraph). Folded\n    // scalars (`>`) get the same treatment.\n    let value = trimmed;\n    if (trimmed === '|' || trimmed === '>') {\n      const collected: string[] = [];\n      let j = i + 1;\n      while (j < lines.length) {\n        const nextLine = lines[j];\n        if (nextLine === '' || /^\\s+/.test(nextLine)) {\n          if (nextLine.trim().length > 0) collected.push(nextLine.trim());\n          j++;\n        } else {\n          break;\n        }\n      }\n      value = collected.join(' ').trim();\n      i = j - 1;\n    }\n    if (key === 'name') out.name = value;\n    else if (key === 'description') out.description = value;\n  }\n  return out;\n}\n"]}

package/dist/test/test/frontmatter.test.d.ts

@@ -1,2 +0,0 @@
-export {};
-//# sourceMappingURL=frontmatter.test.d.ts.map

package/dist/test/test/frontmatter.test.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"frontmatter.test.d.ts","sourceRoot":"","sources":["../../../test/frontmatter.test.ts"],"names":[],"mappings":""}

package/dist/test/test/frontmatter.test.js

@@ -1,55 +0,0 @@
-import { describe, expect, it } from 'vitest';
-import { parseFrontmatter } from '../src/frontmatter.js';
-describe('parseFrontmatter', () => {
-    it('extracts name and description and returns body without the fence', () => {
-        const input = [
-            '---',
-            'name: cesdk-guide',
-            'description: Authoring guide for ce.sdk.',
-            '---',
-            '# Body',
-            'Hello.',
-            ''
-        ].join('\n');
-        const result = parseFrontmatter(input);
-        expect(result.name).toBe('cesdk-guide');
-        expect(result.description).toBe('Authoring guide for ce.sdk.');
-        expect(result.body).toBe('# Body\nHello.\n');
-    });
-    it('returns body unchanged when no frontmatter is present', () => {
-        const input = 'no fence here';
-        const result = parseFrontmatter(input);
-        expect(result.name).toBeUndefined();
-        expect(result.description).toBeUndefined();
-        expect(result.body).toBe('no fence here');
-    });
-    it('tolerates colons in description values', () => {
-        const input = '---\nname: x\ndescription: do A: then B\n---\nbody';
-        expect(parseFrontmatter(input).description).toBe('do A: then B');
-    });
-    it('trims surrounding whitespace from name+description but keeps body intact', () => {
-        const input = '---\nname:   foo\t\ndescription:  bar baz\n---\nline1\nline2\n';
-        const r = parseFrontmatter(input);
-        expect(r.name).toBe('foo');
-        expect(r.description).toBe('bar baz');
-        expect(r.body).toBe('line1\nline2\n');
-    });
-    it('collects YAML pipe block scalars (description: |) into a single line', () => {
-        const input = [
-            '---',
-            'name: skill',
-            'description: |',
-            '  First paragraph line.',
-            '  Second paragraph line.',
-            '',
-            '  After a blank.',
-            '---',
-            'body'
-        ].join('\n');
-        const r = parseFrontmatter(input);
-        expect(r.name).toBe('skill');
-        expect(r.description).toBe('First paragraph line. Second paragraph line. After a blank.');
-        expect(r.body).toBe('body');
-    });
-});
-//# sourceMappingURL=frontmatter.test.js.map

package/dist/test/test/frontmatter.test.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"frontmatter.test.js","sourceRoot":"","sources":["../../../test/frontmatter.test.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,QAAQ,EAAE,MAAM,EAAE,EAAE,EAAE,MAAM,QAAQ,CAAC;AAC9C,OAAO,EAAE,gBAAgB,EAAE,MAAM,uBAAuB,CAAC;AAEzD,QAAQ,CAAC,kBAAkB,EAAE,GAAG,EAAE;IAChC,EAAE,CAAC,kEAAkE,EAAE,GAAG,EAAE;QAC1E,MAAM,KAAK,GAAG;YACZ,KAAK;YACL,mBAAmB;YACnB,0CAA0C;YAC1C,KAAK;YACL,QAAQ;YACR,QAAQ;YACR,EAAE;SACH,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;QACb,MAAM,MAAM,GAAG,gBAAgB,CAAC,KAAK,CAAC,CAAC;QACvC,MAAM,CAAC,MAAM,CAAC,IAAI,CAAC,CAAC,IAAI,CAAC,aAAa,CAAC,CAAC;QACxC,MAAM,CAAC,MAAM,CAAC,WAAW,CAAC,CAAC,IAAI,CAAC,6BAA6B,CAAC,CAAC;QAC/D,MAAM,CAAC,MAAM,CAAC,IAAI,CAAC,CAAC,IAAI,CAAC,kBAAkB,CAAC,CAAC;IAC/C,CAAC,CAAC,CAAC;IAEH,EAAE,CAAC,uDAAuD,EAAE,GAAG,EAAE;QAC/D,MAAM,KAAK,GAAG,eAAe,CAAC;QAC9B,MAAM,MAAM,GAAG,gBAAgB,CAAC,KAAK,CAAC,CAAC;QACvC,MAAM,CAAC,MAAM,CAAC,IAAI,CAAC,CAAC,aAAa,EAAE,CAAC;QACpC,MAAM,CAAC,MAAM,CAAC,WAAW,CAAC,CAAC,aAAa,EAAE,CAAC;QAC3C,MAAM,CAAC,MAAM,CAAC,IAAI,CAAC,CAAC,IAAI,CAAC,eAAe,CAAC,CAAC;IAC5C,CAAC,CAAC,CAAC;IAEH,EAAE,CAAC,wCAAwC,EAAE,GAAG,EAAE;QAChD,MAAM,KAAK,GAAG,oDAAoD,CAAC;QACnE,MAAM,CAAC,gBAAgB,CAAC,KAAK,CAAC,CAAC,WAAW,CAAC,CAAC,IAAI,CAAC,cAAc,CAAC,CAAC;IACnE,CAAC,CAAC,CAAC;IAEH,EAAE,CAAC,0EAA0E,EAAE,GAAG,EAAE;QAClF,MAAM,KAAK,GACT,gEAAgE,CAAC;QACnE,MAAM,CAAC,GAAG,gBAAgB,CAAC,KAAK,CAAC,CAAC;QAClC,MAAM,CAAC,CAAC,CAAC,IAAI,CAAC,CAAC,IAAI,CAAC,KAAK,CAAC,CAAC;QAC3B,MAAM,CAAC,CAAC,CAAC,WAAW,CAAC,CAAC,IAAI,CAAC,SAAS,CAAC,CAAC;QACtC,MAAM,CAAC,CAAC,CAAC,IAAI,CAAC,CAAC,IAAI,CAAC,gBAAgB,CAAC,CAAC;IACxC,CAAC,CAAC,CAAC;IAEH,EAAE,CAAC,sEAAsE,EAAE,GAAG,EAAE;QAC9E,MAAM,KAAK,GAAG;YACZ,KAAK;YACL,aAAa;YACb,gBAAgB;YAChB,yBAAyB;YACzB,0BAA0B;YAC1B,EAAE;YACF,kBAAkB;YAClB,KAAK;YACL,MAAM;SACP,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;QACb,MAAM,CAAC,GAAG,gBAAgB,CAAC,KAAK,CAAC,CAAC;QAClC,MAAM,CAAC,CAAC,CAAC,IAAI,CAAC,CAAC,IAAI,CAAC,OAAO,CAAC,CAAC;QAC7B,MAAM,CAAC,CAAC,CAAC,WAAW,CAAC,CAAC,IAAI,CACxB,6DAA6D,CAC9D,CAAC;QACF,MAAM,CAAC,CAAC,CAAC,IAAI,CAAC,CAAC,IAAI,CAAC,MAAM,CAAC,CAAC;IAC9B,CAAC,CAAC,CAAC;AACL,CAAC,CAAC,CAAC","sourcesContent":["import { describe, expect, it } from 'vitest';\nimport { parseFrontmatter } from '../src/frontmatter.js';\n\ndescribe('parseFrontmatter', () => {\n  it('extracts name and description and returns body without the fence', () => {\n    const input = [\n      '---',\n      'name: cesdk-guide',\n      'description: Authoring guide for ce.sdk.',\n      '---',\n      '# Body',\n      'Hello.',\n      ''\n    ].join('\\n');\n    const result = parseFrontmatter(input);\n    expect(result.name).toBe('cesdk-guide');\n    expect(result.description).toBe('Authoring guide for ce.sdk.');\n    expect(result.body).toBe('# Body\\nHello.\\n');\n  });\n\n  it('returns body unchanged when no frontmatter is present', () => {\n    const input = 'no fence here';\n    const result = parseFrontmatter(input);\n    expect(result.name).toBeUndefined();\n    expect(result.description).toBeUndefined();\n    expect(result.body).toBe('no fence here');\n  });\n\n  it('tolerates colons in description values', () => {\n    const input = '---\\nname: x\\ndescription: do A: then B\\n---\\nbody';\n    expect(parseFrontmatter(input).description).toBe('do A: then B');\n  });\n\n  it('trims surrounding whitespace from name+description but keeps body intact', () => {\n    const input =\n      '---\\nname:   foo\\t\\ndescription:  bar baz\\n---\\nline1\\nline2\\n';\n    const r = parseFrontmatter(input);\n    expect(r.name).toBe('foo');\n    expect(r.description).toBe('bar baz');\n    expect(r.body).toBe('line1\\nline2\\n');\n  });\n\n  it('collects YAML pipe block scalars (description: |) into a single line', () => {\n    const input = [\n      '---',\n      'name: skill',\n      'description: |',\n      '  First paragraph line.',\n      '  Second paragraph line.',\n      '',\n      '  After a blank.',\n      '---',\n      'body'\n    ].join('\\n');\n    const r = parseFrontmatter(input);\n    expect(r.name).toBe('skill');\n    expect(r.description).toBe(\n      'First paragraph line. Second paragraph line. After a blank.'\n    );\n    expect(r.body).toBe('body');\n  });\n});\n"]}