mixdog 1.0.11 → 1.1.0

package/src/defaults/skills/docx/references/html.md

@@ -1,13 +1,13 @@
 # HTML route (Word)
 
-Owns the default route for a new Word document: the model designs the document in HTML and CSS and passes it as `author`'s `script`; a local Chrome or Edge lays it out at the printable width of its `@page` sheet; the runtime reads what the browser drew — each block's computed type, spacing, fills, rules, and widths — and writes native Word: paragraphs and runs, Heading styles, Word lists, tables on the grid the browser drew, pictures. The file stays editable in Word (no text boxes, no screenshots of text). The approach is dom-docx's (computed styles from Chromium; a flex row as a borderless table; a box as a one-cell table), set on Mixdog's own writer so Korean type, the audit, the brief, and the review apply unchanged.
+The default route for a new designed Word document: the model writes HTML/CSS for the content, without selecting a preset, and passes it as `author`'s `script`. A local Chrome or Edge lays it out at the printable width of its `@page` sheet. The runtime maps computed type, spacing, fills, rules, and widths to native Word paragraphs, runs, headings, lists, tables, and pictures. Text stays editable, not a screenshot. Word flows differently from a browser: the supported mappings below and the converted-page comparison define what can be delivered.
 
 ## 1. The call
 `office action:'author' path:<file.docx> script:<html> [overwrite:true] [mode:'portable'|'background'] [render:false]`
 - Returns `session`, `audit`, `logs` (what could not be carried — each names its element), and unless `render:false` the rendered pages with `render.reviewToken` and `render.compare`: one image per page, the browser's print of the HTML on the left, the Word render on the right.
 - The HTML is kept as `<file>.docx.mixdog-source.html`. **Default — fix by editing that file** and calling `author path:<file.docx>` with no `script` (no `overwrite` needed).
 - Refusals land nothing: `html_failed` names the cause (a missing `@page` size, a browser that could not start).
-- After landing, the document is an ordinary session: `batch` edits, `render`, `qa`, `finalize` as SKILL.md describes. A `<!-- BRIEF … -->` comment (the deck's keys: `subject/audience/action`, `sources`, `facts`) holds the document to its facts and asks the scored critique at finalize, as `design.brief` does.
+- After landing, the document is an ordinary session: `batch` edits, `render`, `qa`, `finalize` as SKILL.md describes. A `<!-- BRIEF … -->` comment (`subject/audience/action`, `sources`, `facts`, optionally `concept` as free text) holds the document to its facts and asks the scored critique at finalize, as `design.brief` does.
 
 ## 2. Document contract
 **Hard rule — the sheet is declared**: `@page { size: A4; margin: 20mm 20mm 18mm; }` (A3, A4, A5, B4, B5, letter, legal, each optionally `landscape`, or two lengths). The body is the text column: the runtime sets `body { margin: 0 }` and lays it out at the sheet's width between its margins. Pad inside boxes, never on `body`. → runtime `html_failed`
@@ -31,15 +31,16 @@ Owns the default route for a new Word document: the model designs the document i
 
 **Not carried** (reported in `logs`, never silently): `position: absolute|fixed` (left out), `transform` (drawn upright), CSS columns (one column), a picture inside a line of text (left out), `rowspan` (the cell keeps its first row), border radius and shadows (square, flat).
 **Default — charts are `data-chart`**: the pdf skill's spec (type, labels, values or series, colors, format, labelColor, size, gap, axisLine…) drawn as SVG and placed as a picture; give the element a height. A chart the reader must edit belongs in a workbook.
-**Default — type in pt, faces installed here**: `font-family` names an installed face first (`'Malgun Gothic'`, `'Noto Sans KR'`) — the face is written into the file; the reader's Word needs it too. Body 10–11 pt at `line-height` 1.6–1.75 for Hangul (Word holds each line at exactly that pitch), captions 8.5–9 pt, headings by a clear step. `word-break: keep-all` on `body`.
+**Default — type in pt, faces from the concept**: `font-family` lists the concept's face for each script (`${MIXDOG_SKILL_DIR}/../pptx/references/concepts.md` §5 menu: sans, serif, or mixed), the Latin face and the Korean face both named, a generic family last. Word writes the face name into the file; a recipient without it sees a substitute and the runtime says so (advisory, not blocking). **The document type scale** (shared with flowing PDF): body 10–11 pt at `line-height` 1.6–1.7 for Hangul (1.4–1.5 Latin; Word holds each line at exactly that pitch), captions and running heads 8.5–9 pt, title 24–32 pt, section heading 15–18 pt, subsection 12–13 pt. The deck's 13 pt text-mode body is a screen size and does not apply. `word-break: keep-all` on `body`.
 
 ## 3. Design
-The document's direction is the deck's: `${MIXDOG_SKILL_DIR}/../pptx/references/direction.md` §3, §5, §6 (style vocabulary, palette from one seed hue with one accent that has one job, type pairing) read for a page in the hand, and `writing.md` for the words. What a frontier report page does, and what to avoid:
-- **The first page carries the decision**: eyebrow → assertion title (break it at a phrase with `<br>`, never leave one word on its own line) → one-line lede → a rule → a row of two to four figure cards (figure over label, each card one fill) → the conclusion in a callout. Pages after it: assertion headings, short paragraphs, an exhibit per section.
-- **Exhibits are numbered and titled above, sourced below**: `그림 1. 월별 평균 대기 시간 (분)` in bold caption type over the chart or table, `출처: …` in muted caption type under it.
+The document's direction is the one you chose, optionally from a concept (`${MIXDOG_SKILL_DIR}/../pptx/references/concepts.md`; the brief's `concept:` line is optional free text): its palette roles (`paper`, `ink`, `muted`, `line`, `tint`, `accent`) written as CSS custom properties on `:root` and used by name, its type pairing, and its table and emphasis forms. `writing.md` is for the words. Write the stylesheet for this document; do not carry over an earlier unrelated document's. What a frontier page does, and what to avoid:
+- **The opening follows the genre**, not one anatomy. A decision brief or board report opens with the conclusion (title → lede → optionally a row of two to four figure cards → the conclusion in a carrier); a feature or essay opens with a headline and the first paragraph; a letter or memo opens with the sender block and subject line; a technical manual opens with title, version, and contents; a form opens with its title and instructions. Break an assertion title at a phrase with `<br>`, never leaving one word on its own line. Pages after it follow the same genre: assertion headings and an exhibit per section for a report, flowing prose for an essay.
+- **Emphasis carriers — choose one for the concept, or none**: a boxed note (full border or one-cell table in `tint`), a tinted band across the text column, a margin note beside the prose, a left-rule quote, a bold lead sentence, an oversized numeral, or no callout at all. The order of this list is not a default order; a left-bar callout is one option among them, not the house form. A conclusion that is only one sentence may just be the first paragraph, set larger.
+- **Exhibits are numbered and titled above, sourced below** where the document has exhibits: `그림 1. 월별 평균 대기 시간 (분)` in caption type over the chart or table, `출처: …` in `muted` caption type under it. A letter or essay has none.
 - **A side note beside the prose** (`display:grid; grid-template-columns: 1.6fr 1fr`) carries a definition, a method, or a quote; it fills the space a short paragraph leaves beside a chart.
-- **Tables are sized to their content**, figures right-aligned with the header over them, a total row set apart (bold over a rule), hairlines between rows, no vertical rules.
-- **No page half empty**: content that leaves most of the last page blank is regrouped (a side note, a closing ask box) or tightened, not padded. A page before the last that stops short — a table or figure kept whole moved on — is reported by `qa` and finalize as `page_bottom_empty`: keep `break-inside: avoid` for short tables and figures, and let a long table break with its `thead` repeating.
+- **Tables are sized to their content**, figures right-aligned with the header over them and a total row set apart; the rest of the anatomy is the concept's: ruled (bold header on a rule, hairlines between rows, no vertical rules), zebra (alternating `tint` rows, no rules), open (a single rule under the header, generous rows), or a full grid (forms, technical parameter tables).
+- **No page half empty by accident**: content that leaves most of the last page blank is regrouped (a side note, a closing box) or tightened, not padded. A page before the last that stops short — a table or figure kept whole moved on — is reported by `qa` and finalize as `page_bottom_empty`: keep `break-inside: avoid` for short tables and figures, and let a long table break with its `thead` repeating. A deliberate chapter or section break (`break-before: page`) that leaves a page short is fine when the critique records it as deliberate.
 - Avoid the generated look `${MIXDOG_SKILL_DIR}/../pptx/references/html.md` §8 lists (cream paper and a terracotta accent, an all-caps label over every heading, identical shaded boxes everywhere, centred everything).
 
 ## 4. Review

package/src/defaults/skills/docx/references/native-authoring.md

@@ -9,7 +9,8 @@ file is a Word document.
 - Document face: `set_document_font properties:{ name, nameEastAsia, size, color }`
   sets the body's face, size and ink as the document's own, so a paragraph
   added later — by `append_text` or by hand in Word — matches the body; a
-  Korean document names a Korean face (Malgun Gothic) so its digits and Hangul
+  Korean document names an installed face covering Hangul and digits
+  (for example Noto Sans KR, Malgun Gothic, or a Korean serif) so they
   share one.
 - Page: `set_page properties:{ pageSize, orientation, topMargin, bottomMargin,
   leftMargin, rightMargin, columns, columnSpacing }`. A new document is A4;
@@ -88,6 +89,11 @@ to author the requested document, then inspect the real pages.
 The carriers a report needs beyond running prose, each as the operations that draw it the same in Word
 and in the portable file. Distances are points; `properties` go on `append_text` (or `set_paragraph_format`
 for an existing paragraph). Use a carrier when the content has that job, never as decoration (`SKILL.md` §4).
+Colours are the author's palette roles — `<ink>`, `<muted>`, `<line>`, `<tint>`, `<accent>` — as six-digit hex.
+The optional concept examples are not required. The carriers below are the native route's (editing a
+document, a template, a small generated one); a new designed document draws the same jobs in HTML, with the concept's
+own forms (`references/html.md` §3). Where this list gives one form (a left-bar callout, a ruled table), it is one
+option: a boxed note, a tinted band, or no callout, and open or zebra tables, are equally native (`border`, `shading`, `borders`).
 
 - **Type ladder for a Korean report** (body 10.5 pt): `Title` 24-26 bold · `Heading 1` 15-16 bold,
   `spacingBefore:18, spacingAfter:6, keepWithNext:true` · `Heading 2` 12.5-13 bold, `spacingBefore:12,
@@ -95,23 +101,24 @@ for an existing paragraph). Use a carrier when the content has that job, never a
   (lineSpacing is a minimum in points: 1.7× for Hangul, never 1.15× — Korean lines set at Latin leading
   touch; the alignment is explicit because a Korean Word's Normal style justifies, and justified Hangul
   opens gaps between words that the portable file, set left, never shows) · caption
-  9 pt muted (`color:'6B7280'`). One Latin face and one East Asian face for the whole document
-  (`name` + `nameEastAsia` on a paragraph, `fontName` + `fontNameEastAsia` on `add_table` — the table names its
-  own type and refuses the paragraph's field names); an essay takes a serif pairing
-  (Cambria + 바탕/Noto Serif KR), a brief sets both faces in the Korean sans (`name` and `nameEastAsia` both
-  Malgun Gothic, or both Noto Sans KR): beside Calibri figures the Hangul prints larger and heavier, and
-  "184,200건" reads as two sizes. The ladder is written once, as the document's styles, before the first
-  paragraph: `{ op:'define_styles', styles:{ Title:{ name, nameEastAsia, size:24, bold:true, color:'111827',
+  9 pt `<muted>`. This is the one document scale, shared with flowing PDF. One Latin face and one East Asian face
+  for the whole document (`name` + `nameEastAsia` on a paragraph, `fontName` + `fontNameEastAsia` on `add_table` — the
+  table names its own type and refuses the paragraph's field names), chosen from the concept's face menu: an essay or
+  letter takes a serif pairing (Cambria + 바탕/Noto Serif KR), a brief sets both faces in a Korean sans (`name` and
+  `nameEastAsia` both Noto Sans KR, or both Malgun Gothic), an editorial piece mixes serif headings with a sans body:
+  beside Calibri figures the Hangul prints larger and heavier, and "184,200건" reads as two sizes. The ladder is
+  written once, as the document's styles, before the first
+  paragraph: `{ op:'define_styles', styles:{ Title:{ name, nameEastAsia, size:24, bold:true, color:<ink>,
   alignment:'left', lineSpacing:30, lineSpacingRule:'exact', spacingAfter:8 }, 'Heading 1':{ …, size:15, bold:true,
   spacingBefore:18, spacingAfter:6, keepWithNext:true }, 'Heading 2':{ … }, Normal:{ name, nameEastAsia, size:10.5,
-  lineSpacing:18, spacingAfter:8, alignment:'left' }, Caption:{ size:9, color:'6B7280', spacingBefore:4,
+  lineSpacing:18, spacingAfter:8, alignment:'left' }, Caption:{ size:9, color:<muted>, spacingBefore:4,
   spacingAfter:14 } } }`; then `append_text style:'Heading 1' text:'2. 근거'` carries nothing else, and a
   caption is `style:'Caption'`.
 - **Cover group**: eyebrow (`size:9.5, bold:true, color:<accent>, spacingAfter:4`) → `Title` with
   `alignment:'left'` (Word's own Title style centers it and the portable file does not; say which) and
   `lineSpacing:<1.25 × its size>, lineSpacingRule:'exact'` (30 for 24 pt) — a minimum can only widen a line, and on
   Malgun Gothic's own line the two lines of one wrapped title stood nearly twice the size apart → subtitle
-  (`size:13, color:'374151', spacingAfter:8`) → meta lines (`size:9.5, color:'6B7280'`) → a rule: an empty
+  (`size:13, color:<ink> or <muted>, spacingAfter:8`) → meta lines (`size:9.5, color:<muted>`) → a rule: an empty
   paragraph with `border:{ side:'bottom', size:8, color:<accent> }, spacingAfter:24`. The summary follows on
   the same page; `insert_break kind:'page'` only when the document is long enough to earn a cover page.
 - **Table of contents**: `insert_toc paragraph:<after the cover>` once every `Heading 1..3` exists
@@ -122,38 +129,41 @@ for an existing paragraph). Use a carrier when the content has that job, never a
   style — a heading lists itself as the first entry.
 - **Section header**: `Heading 1` with `keepWithNext:true`; a numbered section carries its number in the text
   ("2. 근거"), never a typed tab or a list marker.
-- **Callout** (the conclusion, a warning, the ask): one paragraph with `shading:'EEF2F7', border:{ side:'left',
+- **Callout** (the conclusion, a warning, the ask) — optional, and its form is the concept's: a tinted band
+  (`shading:<tint>` with indents, no border), a boxed note (`border` on all four sides in `<line>` or `<accent>`), a
+  left rule (below), or none — the conclusion as a larger first paragraph. The left-rule form: one paragraph with
+  `shading:<tint>, border:{ side:'left',
   size:12, color:<accent> }, indentLeft:12, indentRight:12, spacingBefore:6, spacingAfter:12`; a label
   paragraph above it in the same field (`bold:true, size:8.5, color:<accent>, spacingAfter:2, shading, indentLeft`)
   when the field needs a name. Every paragraph of one callout carries the same `shading` and indents so the
   field reads as one. Points inside it (a warning's items) are list items with those same properties plus
   `listKind`: on a list item `indentLeft` places the mark and the text hangs 18 pt after it, inside the field.
 - **Quote**: `indentLeft:16, border:{ side:'left', size:16, color:<accent> }, size:12.5, lineSpacing:20,
-  color:'1F2937', spacingBefore:10, keepTogether:true, keepWithNext:true`; the attribution a caption under it
-  (`size:9, color:'6B7280', indentLeft:16, spacingAfter:12`) beginning "— ". The two keeps hold the quote whole and on
+  color:<ink>, spacingBefore:10, keepTogether:true, keepWithNext:true`; the attribution a caption under it
+  (`size:9, color:<muted>, indentLeft:16, spacingAfter:12`) beginning "— ". The two keeps hold the quote whole and on
   the page of its attribution — without them a two-line quote ending a page left one line behind and carried the other
   over with its speaker. The space above sets it apart from what it follows: without it a quote under a list sat as
   close to the last item as the items to each other and read as one more of them.
 - **Stat strip** (two to four figures with one cause): `add_table` with one row of values and one row of labels,
   `properties:{ borders:{ top:{ enabled:false }, left:{ enabled:false }, right:{ enabled:false }, insideV:{ enabled:false },
-  insideH:{ enabled:false }, bottom:{ style:'single', size:4, color:'C9CED6' } }, repeatHeader:false,
-  columnAlignments:['left', …], rowStyles:[{ fontSize:22, color:<accent>, bold:true }, { fontSize:9, color:'6B7280' }] }`
+  insideH:{ enabled:false }, bottom:{ style:'single', size:4, color:<line> } }, repeatHeader:false,
+  columnAlignments:['left', …], rowStyles:[{ fontSize:22, color:<accent>, bold:true }, { fontSize:9, color:<muted> }] }`
   — one table, the figures at display size over their labels at caption size. A single `fontSize` sets the labels at
   22 pt too ("평균 대기 시간 단축" over three lines). → runtime `table_label_oversized`
 - **Chart**: `add_chart categories:[…] values:[…] chartType:'bar'|'column' unit highlight forecast accent` — one series
-  drawn as a picture in the document's accent (`accent:'1F5E4B'`, the hex the document's headings and callouts use;
+  drawn as a picture in the document's accent (`accent:<accent hex>`, the concept's accent that the document's headings and emphasis use;
   without it the writer's teal), every bar carrying its value and no grid; `bar` for a ranking (names on the
   left), `column` for periods, `highlight` the bar the paragraph is about, `forecast` the bars that are projections
   (a plan, an estimate: drawn pale in a dashed outline, never as counted figures). It lands like `add_image` (`width`,
   `properties:{ alignment:'center' }`) with a caption under it; its altText names each figure. The bars cannot be
   edited in Word — a chart the reader will edit belongs in a workbook.
-- **Caption**: the paragraph under a table or picture, `size:9, color:'6B7280', spacingBefore:4,
+- **Caption**: the paragraph under a table or picture, `size:9, color:<muted>, spacingBefore:4,
   spacingAfter:14`: what it shows and its source. The table above it takes `properties.keepWithNext:true`
   so the caption never starts the next page alone, and the paragraph that introduces a table or chart takes
   `keepWithNext:true` too — without it a heading and its lead-in closed one page and the table opened the next; a picture (`add_image`) keeps with its caption on its own,
   and `properties:{ alignment:'center' }` centres it.
 - **Running header**: `set_header_footer kind:'header'` with `properties:{ name, nameEastAsia, size:8.5,
-  color:'6B7280' }` — without them the line prints in the document default, louder than the eyebrow under it.
+  color:<muted> }` — a running head and folio are a choice of the concept (a letter or essay takes none) — without them the line prints in the document default, louder than the eyebrow under it.
   The cover page carries neither: after the default header and the page numbers (`add_page_numbers separator:' / '`
   prints "1 / 3"), `set_header_footer kind:'header' variant:'first' text:''` and the same for the footer give the
   first page empty ones.

package/src/defaults/skills/goal-management/SKILL.md

@@ -150,11 +150,17 @@ status. Do not resume or extend the Goal without the user's approval.
 
 ### Blocked and redirected work
 
-Report an impasse that only external state or the user can clear with `block`
-once per turn, with a stable description of the same condition. The runtime
-stops after three consecutive turns confirm it; until then continue any
-available work. Treat equivalent blockers as the same condition even when their
-wording or stated next step changes. Never block for difficulty, slowness,
+`block` stops the Goal immediately, with a stable description of an impasse
+that only external state or the user can clear. Do not block the first time a
+blocker appears: block only after the same condition has repeated for three
+consecutive Goal turns, counting the user-triggered turn and automatic
+continuations; after a resume, count only turns since that resume. Until then,
+continue any available work and re-check the blocker against current state with
+a tool each turn rather than restating it. When current state verifies an
+impasse that only the user can clear (their action, approval, credentials, or a
+resource they control), block on that turn. Once the threshold is met, block
+instead of reporting the same blocker again. Treat equivalent blockers as the
+same condition even when their wording or stated next step changes. Never block for difficulty, slowness,
 uncertainty, a choice you can make, confirmation for in-scope work, or
 clarification that would only help. Use `abandon` only when the user redirects away from
 the objective; it preserves a stopped record rather than declaring success.

package/src/defaults/skills/local-provider/SKILL.md

@@ -27,7 +27,8 @@ available before Local Provider is installed or enabled.
    Prefer original publishers or established conversion publishers; popularity
    is not proof of correctness, licensing permission, or runtime compatibility.
 3. Inspect the chosen exact `filename` in that repository, with the intended
-   `contextWindow` if needed (default 8192). The runtime pins revision and
+   `contextWindow` if needed (16384 minimum; default 32768 when the GPU holds
+   it, else 16384). The runtime pins revision and
    SHA-256 from HF and reads a bounded portion of the actual GGUF header for
    architecture, context, and a VRAM estimate. Split shards, gated repositories,
    auxiliary files and missing metadata may be refused; explain the limitation

package/src/defaults/skills/pdf/SKILL.md

@@ -26,20 +26,23 @@ A PDF is a fixed rendering to read faithfully or a document to produce: a new do
 6. Close a read-only session when done; anything that changed the file ends with `action:'finalize' session:<id> review:true`.
 
 ## Create
-**Default — HTML for a new document**: a new PDF is written as one HTML document and printed with `office action:'author' path:<file.pdf> script:<html>`; read `references/html.md` before writing the HTML. The browser lays out CSS (grid, flex, inline SVG charts, Hangul line breaks) far better than blocks can. Choose the kind of document first (`references/html.md` §1):
-- **Designed pages — the default for anything a reader judges by its look**: a report, proposal, one-pager, brochure, certificate, or handout. Each sheet is one `<section class="slide">` under the pptx skill's own frame: load the `pptx` skill (Skill name:"pptx") and follow its brief, direction, composition, writing, and HTML route as written, with the differences `references/html.md` §2 lists. `author` runs the deck's gates, measured audit, and receipt on the pages, then prints the HTML itself; finalize takes the deck's scored critique.
-- **Flowing text**: a contract, manual, letter, or long report the browser paginates by itself (`references/html.md` §3-§9).
+**Step 1 — design for the content and reader**: choose the structure, type, palette, and density for the intended use. Existing files, templates, and brand requirements take precedence. `${MIXDOG_SKILL_DIR}/../pptx/references/concepts.md` is optional inspiration, not a required selection; `concept:` is optional free text. Neither a prescribed motif nor a fixed colour, whitespace, or layout ratio is required.
+
+**Default — HTML for a new document**: write the layout in HTML/CSS and print with `office action:'author' path:<file.pdf> script:<html>`; read `references/html.md` first. The browser handles grid, flex, inline SVG, and Hangul line breaks. Choose the page model from the content (`references/html.md` §1), not a style catalogue:
+- **Designed pages**: a document a reader judges by its look and meets page by page — a brochure, one-pager, certificate, handout, proposal or report built as composed spreads. Each sheet is one `<section class="slide">` under the pptx skill's own frame: load the `pptx` skill (Skill name:"pptx") and follow its brief, direction, composition, writing, and HTML route as written, with the differences `references/html.md` §2 lists. `author` runs the deck's gates, measured audit, and receipt on the pages, then prints the HTML itself; finalize takes the deck's scored critique.
+- **Flowing text**: a document whose text the browser paginates by itself — a contract, manual, letter, essay, or a long report with running prose and tables (`references/html.md` §3-§9).
 
 The blocks below stay for two cases: a fillable form (the browser prints form controls as pictures, never as fields — or print the page from HTML and add the fields with `add_form_field`), and a small document generated from data with no design of its own. With no local Chrome or Edge, `author` fails with `html_failed` naming the launch error, and the blocks are the route.
 
 **Blocks route**:
-- Plan the reading purpose, type hierarchy, margins and page flow, then specify block styles directly. The writer supplies flow, not an art direction. `design.profile` explicitly opts into a preset; otherwise it does not inject a palette or redesign supplied blocks. A representative page is optional when it resolves a real design uncertainty.
+- Plan the reading purpose, type hierarchy, margins and page flow, then specify block styles directly. The writer supplies flow, not an art direction. `design.profile` explicitly opts into a preset; otherwise it does not redesign supplied blocks. Its default ink is a neutral one; `properties.palette` (below) sets the concept's colours for the blocks that carry colour. A representative page is optional when it resolves a real design uncertainty.
 - `office action:'create' path:<file.pdf> format:'pdf' blocks:[...] fields:[...] properties:{ title, author, subject, keywords, pageSize:'a4'|'letter'|[w,h], orientation, margin, fontPath, pageNumbers, footer }`, then render and review before finalizing.
 - Blocks: `{ type:'heading', text, level:1-3, size }`, `{ type:'paragraph', text, size, color, after }` (`\n` breaks a line; unspaced text wraps by character), `{ type:'list', items:[…], marker, ordered:true, indent }` (the marker is drawn with a hanging indent, so never type `• ` into a paragraph), `{ type:'table', rows, headers, columnWidths:[weights], columnAlignments:['left','right'], rowHeight, fontSize, headerFill, headerColor }` (the header row repeats after a page break; cells wrap and rows grow; without `columnAlignments` a column of figures — `₩2,400,000` and `$120` included — is set right and a label column — including `1호`, `2호` — stays left; the anatomy is the Word one: a bold header on a rule, hairlines between rows, no vertical rules, `grid:true` for the full cell grid; `headers:false` for a table with no header row, such as the totals under an invoice's lines — give that block the `x` and `width` of the figure columns it closes, so each total stands under its column rather than across the page from its label; `totalRow:true` sets the last row bold under a rule), `{ type:'image', path, width, height, align:'center'|'right' }` (PNG or JPEG; fits the text width unless sized), `{ type:'pagebreak' }`.
-  The document anatomy beyond prose, each one block the writer flows the same on every page: `{ type:'cover', eyebrow, title, subtitle, meta:[…] }` (the title group of the first page — eyebrow in the accent, title, subtitle, meta lines, one rule under; the summary follows on the same page unless a `pagebreak` says otherwise), `{ type:'stats', items:[{ value, label }] }` (several figures with one cause on one baseline, equal columns, one rule under — at most four, and every value is a fact with a source), `{ type:'callout', label, text, fill }` (a tinted field with its label above the text: the conclusion, a warning, the ask; never split across pages), `{ type:'quote', text, attribution }` (someone else's words behind a rule in the accent, the attribution a caption under), `{ type:'chart', categories:[…], values:[…], chartType:'bar'|'column', unit, highlight, title, height }` (one series drawn by the page in the document's face: `bar` lays the bars across — a ranking, its names on the left — and `column` stands them up for periods left to right; every bar carries its value (`unit` follows the number: `'건'`, `'%'`), there is no grid, and `highlight` — an index or a category — takes the accent while the other bars recede; values are zero or more, one per category; a `caption` right after it travels with it), `{ type:'caption', text }` (the small muted line under a table, picture, or chart: what it shows and its source), `{ type:'rule' }` (a hairline between sections). Body copy leads at 1.5× its size so Hangul lines breathe; a heading keeps 1.2× and never ends a page. A report is: cover → callout (the conclusion) or stats → headings with prose, tables with captions → quote where a voice carries the point → closing callout (the ask); an essay is headings and prose alone.
+  The document anatomy beyond prose, each one block the writer flows the same on every page: `{ type:'cover', eyebrow, title, subtitle, meta:[…] }` (the title group of the first page — eyebrow in the accent, title, subtitle, meta lines, one rule under; the summary follows on the same page unless a `pagebreak` says otherwise), `{ type:'stats', items:[{ value, label }] }` (several figures with one cause on one baseline, equal columns, one rule under — at most four, and every value is a fact with a source), `{ type:'callout', label, text, fill }` (a tinted field with its label above the text: the conclusion, a warning, the ask; never split across pages), `{ type:'quote', text, attribution }` (someone else's words behind a rule in the accent, the attribution a caption under), `{ type:'chart', categories:[…], values:[…], chartType:'bar'|'column', unit, highlight, title, height }` (one series drawn by the page in the document's face: `bar` lays the bars across — a ranking, its names on the left — and `column` stands them up for periods left to right; every bar carries its value (`unit` follows the number: `'건'`, `'%'`), there is no grid, and `highlight` — an index or a category — takes the accent while the other bars recede; values are zero or more, one per category; a `caption` right after it travels with it), `{ type:'caption', text }` (the small muted line under a table, picture, or chart: what it shows and its source), `{ type:'rule' }` (a hairline between sections). Body copy leads at 1.5× its size so Hangul lines breathe; a heading keeps 1.2× and never ends a page. Which of these a document uses follows its genre: a decision report may open on a cover and a callout or stats strip, a letter or essay is headings and prose alone, a data log is a table with captions; a callout, quote, or closing ask appears only where the content has that job, and the order is not fixed.
+  `properties.palette: { accent, muted, field, line }` (six-digit hex without `#`, all optional) overrides the writer's default ink for the cover eyebrow and rule, callout, quote rule, stats, chart bars, and table header and rules: `accent` the one emphasis colour, `muted` captions and labels, `field` the tinted callout and stat ground, `line` rules and hairlines. Take the four from the chosen concept's roles (`accent`, `muted`, `tint`, `line`).
   A form the reader fills travels with the copy that introduces it: `{ type:'field', name, label, fieldType:'text|checkbox|radio|dropdown|optionlist', height }` and `{ type:'fieldRow', items:[{ name, label, type }], gutter }` flow like any other block (a `checkbox` or `radio` is drawn as a square with its label beside it, a typed box with its label above; a `radio` with `options:[…]` is a question — its label above, the options in one row, each mark with its own words beside it; a `caption` right after a field block travels with its last row), so the writer fixes the page and the coordinates where the reader meets them, and a heading is never left on the page before its own boxes. Fields passed in `fields:[…]` keep the absolute `page`/`x`/`y` they were given, which is what stamping a form onto a scan needs.
   The block list is checked before anything is written: an unknown `type`, a block named with `kind`, an unknown field, or a missing `rows`/`items`/`text` is refused with every fault at once, instead of flowing as an empty paragraph. The writer flows and paginates; `pageNumbers` is on for multi-page output (`N / total`, bottom right) unless set `false`.
-- Fonts: the standard fonts cover Latin only. Korean, CJK, Cyrillic, or Greek text embeds a Unicode font found on the system (Malgun Gothic on Windows, Nanum/DejaVu/Noto on Linux); `properties.fontPath` chooses one, the result's `font.path` says which was used, and `action:'detect'` names it beforehand as `portable.pdfUnicodeFont`. When none is installed the call fails with the hint: ask for a font file rather than transliterating.
+- Fonts: the standard fonts cover Latin only. Korean, CJK, Cyrillic, or Greek text embeds a Unicode font found on the system (for example Malgun Gothic or Noto on Windows, Nanum/DejaVu/Noto on Linux); a PDF embeds what it drew with, so the reader needs no font. `properties.fontPath` chooses one, the result's `font.path` says which was used, and `action:'detect'` names it beforehand as `portable.pdfUnicodeFont`. When none is installed the call fails with the hint: ask for a font file rather than transliterating.
 - Form fields: `{ name, label, type:'text|checkbox|radio|dropdown|optionlist', page, x, y, width, height, value, options, multiline, maxLength, fontSize, labelSize, required, readOnly }` — a PDF field is a bare box, so `label` is the caption drawn above it (without one the page reaches the reader as unnamed rectangles), and the box may be written as `rect:[x, y, width, height]`; the layout is linted before writing — missing or duplicate names and out-of-page boxes fail, overlaps and boxes too small to use (under 24 × 12 pt typed, 8 × 8 pt marks) come back as `formIssues` on the result. A field that belongs with the copy around it is better declared as a `field` or `fieldRow` block, which flows with that copy instead of holding a page number the text may have moved off.
 
 ## Edit

package/src/defaults/skills/pdf/references/html.md

@@ -1,16 +1,16 @@
 # HTML route (PDF)
 
-Owns the default route for a new PDF: the model writes one HTML document and passes it as `author`'s `script`; a local Chrome or Edge lays it out under the document's own `@page` rules, the runtime checks it, and the browser prints it — text stays text, headings become bookmarks, the file is tagged. Everything else in SKILL.md (render, finalize, the rules) applies unchanged.
+The default route for a new PDF: the model writes HTML/CSS for the content and intended reader, without selecting a preset, and passes it as `author`'s `script`. A local Chrome or Edge lays it out under the document's own `@page` rules, the runtime checks it, and the browser prints it — text stays text, headings become bookmarks, and the file is tagged. Inspect the printed pages for breaks, clipping, missing content, and readability before finalizing.
 
 ## 1. Two kinds of document
 The HTML itself says which one it is: `<section class="slide">` pages make it designed pages (§2); anything else flows (§4-§8).
 | | Designed pages (§2) | Flowing text (§4-§8) |
 |---|---|---|
-| For | reports, proposals, one-pagers, brochures, certificates, handouts — anything judged by its look | contracts, manuals, letters, long running text |
+| For | one-pagers, brochures, certificates, handouts, proposals and reports composed as spreads — anything judged by its look and taken in page by page | contracts, manuals, letters, essays, and reports of running prose and tables |
 | Pages | one `section.slide` per sheet, composed like a slide | the browser paginates the flow |
 | Frame | the pptx skill's: brief, plan and facts gates, geometry gate, measured audit, receipt, scored critique | this file's checks and the per-page critique of SKILL.md |
 
-**Default — designed pages** whenever the document has a cover, key figures, or pages a reader takes in at a glance; flowing text when the content is read straight through and its length decides the page count.
+**The route follows the page model, not a concept id**: designed pages when each sheet is a composed unit or a fixed page count is needed; flowing text when the content is read straight through and its length decides the page count. Either can be a report.
 
 ## 2. Designed pages — the deck's frame
 Load the `pptx` skill and follow it as written for the brief (SKILL.md §3: `subject/audience/action`, `directions`, `style`, `facts`, `slide plan`), the workflow, `direction.md`, `composition.md`, `writing.md`, and its HTML route (`references/html.md`); the PDF differs only here:
@@ -18,7 +18,7 @@ Load the `pptx` skill and follow it as written for the brief (SKILL.md §3: `sub
 - **Type in pt**: here 1 px is 0.75 pt (the deck's canvas runs 0.5 pt per px), so take the pptx references' roles, not their px. A page is read in the hand, not projected: the `text` reading mode of `direction.md` §1, body 9.5–11 pt, captions 7.5–8.5 pt (the audit's print floors: body 9 pt, a one-line caption or note 7 pt, never the deck's screen 12 / 9 pt), page titles 20–32 pt, a hero numeral 60 pt and up; the plan's `hero` promise reads 40 pt+, `statement` 22 pt+. Margins 15–20 mm.
 - **Charts are `data-chart`**, written exactly as the pptx HTML route's §5 (type, labels, values or series, colors, min/max, format, labelColor, size in pt, legend, grid, valueAxis, categoryAxis, gap, stacked, hole, plot): the deck frame reads it as a native chart (a plan line names it `chart`), and the runtime draws the same spec as an inline SVG on the page before it prints, value labels as text. A chart no spec covers (a dumbbell, an annotated line) is an inline `<svg>` drawn from the facts' values and named `picture` in the plan. `<table>` (`table`), `<img>`, and `data-icon` print as drawn.
 - **Every page prints**: each `section.slide` goes on its own sheet and stays displayed in print (never hide the inactive ones in CSS); `aside.notes` is not printed. Pages that print onto more sheets than there are slides are refused.
-- **No margin boxes**: with `margin: 0` there is nowhere for `@page` page numbers — set the folio and running head inside the slide, as the deck sets its page number. `h1`–`h3` still become bookmarks.
+- **No margin boxes**: with `margin: 0` there is nowhere for `@page` page numbers — set the folio and running head inside the slide, as the deck sets its page number, if the concept's chrome has them at all (a brand or statement page carries none). `h1`–`h3` still become bookmarks.
 - **What comes back**: `designedPages: true`, the deck's `audit` (`status` pass/fail, top targets), `receipt` (with the printed pages' render readings), `render.contactSheet`, and `logs`; a later `render` on the session returns the receipt and contact sheet again, and `qa` adds the brief's readings (`plan_count_mismatch`, `fact_without_locator`). Refusals are the deck's: `html_failed`, `geometry_gate`, `plan_gate`, `facts_gate`. There is no `render.compare`: the PDF is the browser's own print.
 - **Finalize** takes the pptx skill's critique (its SKILL.md §5), one entry per page keyed `page` (or `slide`): `verdict`, the five scores, a page-specific `note`, `fixes`, `checks`; an anchor page carries `role`. An error the audit found holds finalize until the HTML is fixed and authored again.
 - Copy that outgrows its page is split onto another page or cut (the deck's rule); content whose length should decide the page count is flowing text instead.
@@ -35,29 +35,34 @@ Load the `pptx` skill and follow it as written for the brief (SKILL.md §3: `sub
 **Hard rule — pictures are local**: `<img src>` is a file beside the PDF (relative paths resolve from its folder) or a `data:` URI; a web URL is refused, and so is a picture that did not load. There is no network: no CDN fonts, scripts, or stylesheets. → runtime `layout_gate` (`remote_image`, `image_missing`)
 **Hard rule — nothing wider than the page**: a table, a code block, a picture, or a row of cards wider than the printable width is cut at the margin by print. Give pictures `max-width: 100%`, let tables wrap their cells (`table-layout: fixed` with column widths in %), and wrap long code. A box inside a container with `overflow: hidden` is the container's business and is not reported. → runtime `layout_gate` (`overflow_x`)
 - A full-bleed cover before a flowing body uses a named page: `@page cover { margin: 0 }` with `.cover { page: cover; break-after: page; }`.
-**Default — the brief and its facts**: an optional `<!-- BRIEF` … `-->` comment at the top, one `key: value` per line (`subject/audience/action`, `sources`, `facts: F1 2,400건 — 운영 시트 B4 · F2 …`). When it is present, every figure the printed pages show that no fact carries comes back in `facts` (`pages[].figures`); it is reported, not refused — answer it by adding the fact with its source or correcting the figure. `facts: sample — <why>` marks every figure illustrative, and the delivery says so. Dates, page counters, and small ordinals are not figures.
+**Default — the brief and its facts**: an optional `<!-- BRIEF` … `-->` comment at the top, one `key: value` per line (`subject/audience/action`, optionally `concept: <free text>` (`concepts.md` §1), `sources`, `facts: F1 2,400건 — 운영 시트 B4 · F2 …`). When it is present, every figure the printed pages show that no fact carries comes back in `facts` (`pages[].figures`); it is reported, not refused — answer it by adding the fact with its source or correcting the figure. `facts: sample — <why>` marks every figure illustrative, and the delivery says so. Dates, page counters, and small ordinals are not figures.
 
 ## 5. Flowing text: pages and breaks
-- **Running head, foot, and page numbers** live in the `@page` margin boxes, never in the body: `@page { @bottom-right { content: counter(page) " / " counter(pages); font: 8.5pt 'Malgun Gothic'; color: #6B7280; } @top-left { content: "분기 운영 보고서"; … } }`. `counter(page)` works only there. Turn them off on a cover with `@page :first { @bottom-right { content: none } }` or the named cover page.
-- **Breaks**: `h1, h2, h3 { break-after: avoid; }` keeps a heading with what follows; `figure, table.compact, .callout, .card, tr { break-inside: avoid; }` keeps a unit whole; `p, li { orphans: 2; widows: 2; }`; `thead { display: table-header-group; }` repeats a long table's header on every page; `break-before: page` opens a chapter on a new sheet. A block that may not break but is taller than a page breaks anyway — the result warns `unbreakable_too_tall`; shorten it or let it break. A kept block that moves on leaves the page before it short: `qa` and finalize report a page before the last whose body stops above 70% of its height as `page_bottom_empty`, so keep only short units whole.
+- **Running head, foot, and page numbers** are a choice of the concept, and when present live in the `@page` margin boxes, never in the body. `counter(page)` works only there. Pick one variant (none is also right for a letter, a short document, or a statement piece), with the face and colour from the concept's roles:
+  - running head top-right, folio bottom-right (a long filed report): `@page { @top-right { content: "분기 운영 보고서"; font: 8.5pt <face>; color: <muted>; } @bottom-right { content: counter(page) " / " counter(pages); font: 8.5pt <face>; color: <muted>; } }`
+  - centred folio alone (a manual, an essay): `@page { @bottom-center { content: counter(page); font: 9pt <face>; color: <muted>; } }`
+  - folio only on the inside edge, small (an editorial piece): `@page :left { @bottom-left { content: counter(page); … } } @page :right { @bottom-right { content: counter(page); … } }`
+  - none: no margin boxes at all (a letter, a notice).
+  Turn them off on a cover with `@page :first { @top-right { content: none } @bottom-right { content: none } }` (naming every box the document sets) or the named cover page.
+- **Breaks**: `h1, h2, h3 { break-after: avoid; }` keeps a heading with what follows; `figure, table.compact, .callout, .card, tr { break-inside: avoid; }` keeps a unit whole; `p, li { orphans: 2; widows: 2; }`; `thead { display: table-header-group; }` repeats a long table's header on every page; `break-before: page` opens a chapter on a new sheet. A block that may not break but is taller than a page breaks anyway — the result warns `unbreakable_too_tall`; shorten it or let it break. A kept block that moves on leaves the page before it short: `qa` and finalize report a page before the last whose body stops above 70% of its height as `page_bottom_empty`, so keep only short units whole. A deliberate chapter or section break that leaves a page short is fine when the finalize critique says it is deliberate.
 - **Backgrounds print**. A colour field or band behind a section prints as drawn; `position: fixed` repeats on every page, so use it only for a deliberate watermark or edge band.
 - **Bookmarks** come from `h1`–`h3`: keep heading levels true to the structure (one `h1` for the title, `h2` per section), and never fake a heading with a styled `div`. A heading set on two lines with `<br>` keeps the space in its bookmark.
 - **Not in the browser**: running heads taken from the content (`string-set`), table-of-contents page numbers (`target-counter()`), footnotes (`float: footnote`), and `leader()`. A contents list names the sections without page numbers (the bookmarks carry the navigation), and notes are endnotes.
 
 ## 6. Text and fonts (both kinds)
 - Set `word-break: keep-all; overflow-wrap: break-word` on `body`, `text-wrap: pretty` on prose, `text-wrap: balance` on headings; wrap a name that must not break in `white-space: nowrap`.
-- Faces: the browser embeds what it drew with, so a face must be installed on this machine — `'Malgun Gothic'` on Windows, `'Noto Sans KR'` / `'Noto Serif KR'` where installed, Latin system faces. A face that is missing falls back silently: list the installed face first and a generic family last, and check the render.
-- Sizes in `pt` or `mm`: body 10–11.5 pt with `line-height` 1.55–1.7 for Hangul, captions and running heads 8–9 pt, headings by a clear step (title ~24–32 pt, section ~15–18 pt). Measure: 30–40 Hangul characters per line for body copy; a full-width A4 column runs long, so a report body often sits in a narrower column beside a side rail for captions or key figures.
-- Contrast 4.5:1 for body text, 3:1 for 14 pt bold and up. A weight renders only if the face has it (Malgun Gothic has regular and bold); a missing weight is synthesized or rounded.
+- Faces: the browser embeds what it drew with, so the reader needs no font — but the face must be installed on this machine. Choose from the concept's menu (`concepts.md` §5): a sans (`'Noto Sans KR'`, `'Malgun Gothic'`), a serif (`'Noto Serif KR'`, `'Batang'`), or a serif-over-sans mix, with a Latin face named beside it. A face that is missing falls back silently: list the installed face first and a generic family last, and check the render.
+- Sizes in `pt` or `mm` (the one document scale, shared with Word): body 10–11 pt with `line-height` 1.6–1.7 for Hangul, captions and running heads 8.5–9 pt, headings by a clear step (title ~24–32 pt, section ~15–18 pt, subsection 12–13 pt). Measure: 30–40 Hangul characters per line for body copy; a full-width A4 column runs long, so a report body often sits in a narrower column beside a side rail for captions or key figures.
+- Contrast 4.5:1 for body text, 3:1 for 14 pt bold and up. A weight renders only if the face has it (Malgun Gothic has regular and bold; Noto families carry more); a missing weight is synthesized or rounded.
 
 ## 7. Tables, charts, pictures
-- **Tables** are real `<table>` with `<thead>`: a bold header on a rule, hairlines between rows, no vertical rules unless the grid carries meaning; figures right-aligned with `font-variant-numeric: tabular-nums`, labels left; a total row bold under a rule. A caption under it says what it shows and its source.
+- **Tables** are real `<table>` with `<thead>`; the treatment is the concept's — ruled (bold header on a rule, hairlines between rows), zebra (alternating `tint` rows, no rules), open (one rule under the header, wide rows), or a full grid (forms, parameter tables) — and no vertical rules unless the grid carries meaning; figures right-aligned with `font-variant-numeric: tabular-nums`, labels left; a total row set apart. The first listed is not a default. A caption under it says what it shows and its source.
 - **Charts** are `data-chart` on an empty, sized element (the spec of §2), drawn by the runtime as SVG before printing; a chart no spec covers is an inline `<svg>` with numbers computed from one set of values (bar length = value / max × width), not typed separately. Either way: direct value labels, no gridline clutter, the subject's bar or point in the accent and the rest receding, the unit in the format (`"#,##0\"건\""`). JavaScript runs, but a chart library must be inlined, since nothing loads from the network.
 - **Pictures**: `<img>` with `alt`, `max-width: 100%`, `object-fit` for a crop. A generated picture is mood or illustration, never evidence (figures, screenshots, and product UI are real or absent). Flowing text has no `data-icon`: draw icons as inline SVG (designed pages have it, §2).
 
 ## 8. Flowing text: design pass
 Designed pages take the pptx skill's design pass instead. Before writing flowing HTML, plan once and check the plan against the defaults:
-1. **Plan** from the subject and the sources: palette of 4–6 hex values with roles (paper, ink, muted ink, one accent with one job, one tint for fields); type roles in pt; the grid (margins, column, side rail); the document anatomy — cover or title block → the conclusion first (a callout or a row of key figures) → sections with their evidence → the closing ask.
+1. **Plan** from the subject and the sources, in the chosen concept (`concepts.md`): the palette roles (`paper`, `ink`, `muted`, `line`, `tint`, `accent`, optional `accent2`) as CSS custom properties; type roles in pt from the face menu; the grid (margins, column, side rail); the anatomy the genre calls for — a report may lead with its conclusion, an essay with its first paragraph, a letter with the sender block, a manual with contents. Emphasis carriers are a choice: a boxed note, a tinted band, a margin note, a left-rule quote, an oversized numeral, or no callout; the first listed is not a default. Write this document's stylesheet fresh.
 2. **Check**: one anchor per page (the first thing the eye lands on is that page's claim); three tiers of space (inside a unit < between units < around sections); proximity carries relation (a label nearer its value than the next value); decoration never stands in for content. Avoid the generated look unless the brief asks for it: cream paper with a serif and a terracotta accent, an all-caps tracked label over every heading, identical rounded cards with one soft shadow, gradient washes, centred everything.
 
 ## 9. Review

package/src/defaults/skills/pptx/SKILL.md

@@ -16,7 +16,7 @@ Use `office` to create, redesign, and review PowerPoint decks. Read this guide
 before the first deck operation. A new deck is written as HTML slides by default
 (`references/html.md`); the pptxgenjs script and its kit remain the second route.
 
-The model designs; the runtime measures. The kit supplies editable primitives, not a required visual style. Facts, safety, file integrity, legibility, and current rendered review remain mandatory. Palette, typography scales, spacing ladders, layout recipes, and stylistic avoid lists are defaults: adapt them to the audience, brand, or reference deck rather than sacrificing the result to match a recipe. Existing accessible product assets and user materials precede generated imagery; the runtime has no photo library.
+The model designs; the runtime converts and measures. Write HTML/CSS for the actual content, audience, and use, not to fill a predefined layout. Facts, safety, file integrity, legibility, and current rendered review remain mandatory. Palette, typography, spacing, motifs, density, repetition, and layout recipes in the references are optional examples, not requirements or acceptance criteria. Neither a named concept nor a style score proves quality. Existing accessible product assets and user materials precede generated imagery; the runtime has no photo library.
 
 ## 0. Route by task
 | Task | Route | Done when |
@@ -30,8 +30,9 @@ Prerequisites: the Office capability (`metadata.requires`) — its portable back
 ## 1. Load routing
 | File | Owns | Read when |
 |---|---|---|
-| `references/direction.md` | reading mode, argument mode, visual styles, representative direction trials, palette from a seed, typography | always, before the brief |
-| `references/composition.md` | the page brief, relationship atoms, composition lenses, page recipes, starting structures, spacing, lines and surfaces, rhythm, text, device menu, component specs, icons, machine tells | always, before the slide plan |
+| `references/concepts.md` | optional examples of palette, type, and document treatments | only when examples help resolve an open design choice; no id must be selected |
+| `references/direction.md` | reading modes, argument structures, and visual direction examples | when the reading mode or direction is unclear |
+| `references/composition.md` | relationship vocabulary, composition examples, and script-kit devices | when a page needs composition help or a script-kit device |
 | `references/writing.md` | sentence rules, one register, the notation of numbers, dates, money, and units, room for translation, the read-back | always, before the copy (§2 step 2) |
 | `references/html.md` | the HTML route: the document contract, the brief as an HTML comment, what CSS converts to, text and fonts, `data-chart`, icons and SVG, the `images:` plan, the one-shot design pass and the generated-look list, review with `render.compare` | always for a new deck on the HTML route, before the plan; it replaces `kit-index.md` there |
 | `references/kit-index.md` | every helper of `kit.md`, `charts.md`, and `pictures.md` by signature, defaults, and the guidance above it, with the kit's rules — read it instead of those files' code: tokens, `palette()`, `typography()`, masters, measured text (`reading()` and `columns()` for the commentary beside or under a carrier — both refuse a block that would cross the foot; `avail(top)` measures the height first), the anchors of a deck without pictures (`poster()`, `numeralBeat()`, `motif()`, `orb()` — the beat's one hero object; `display()` and `dateline()` for the editorial text page on paper; `emph:` for the headline's contrast phrase), layout by weight, shapes (`stage()` — the context field a structure stands on; `shareDown(top, columnsH(...))` when the reading sits under it, `readingH()` to register a reading to its row, `loop(s, st, …)` / `hub(s, st, …)` for radii from the stage), the relationship structures (timeline, steps, hub, loop, merge, tiers, lanes, quadrants, venn, quote, brace groups) | always on the script route, before the script |
@@ -40,11 +41,11 @@ Prerequisites: the Office capability (`metadata.requires`) — its portable back
 | `references/review.md` | representative direction trials, source questions, independent image review | for a new visual direction, substantive redesign, or quality comparison |
 
 ## 2. Workflow
-1. Read the always-loaded references; add `pictures.md` only on its trigger (chart helpers are in the index). Before choosing a visual direction, identify the available brand assets, product views, and reference deck (`direction.md` §4). For a product pitch, select the real view or artifact that demonstrates the benefit before substituting a generic diagram. No generation lane does not imply no pictures. **Default — the picture lane is checked, not assumed**: when the plan wants a picture no supplied asset covers, load the `image` skill and `list` its lanes before authoring, so the deck knows whether one can be generated at all. A picture is generated only where the user asked for one or the claim needs the artifact itself; a signed-in lane is not a reason to add imagery. With no lane the picture is omitted, the page anchors on the drawn devices instead (`spot()`, `orb()`, `poster()`, `motif()`), and the delivery says the deck went without generated pictures. Done when the brief names each selected asset and its source, or explains why typography or a conceptual diagram is more faithful.
+1. Read the HTML contract and writing guide; load other references only for the decisions they help. Identify supplied brand assets, product views, and reference material. For a product pitch, prefer the real artifact that demonstrates the benefit to an interchangeable diagram. When an illustration is needed and authorized but no supplied asset covers it, load the `image` skill and check its lanes; do not assume generation is available or add imagery merely because it is. Without it, choose a faithful text or drawn explanation and disclose any unmet image requirement. Done when selected assets and their sources are known.
 2. Ground: with source material, read it and write the fact sheet (each figure with its page or cell) before any outline; then the outline as assertion titles that read as one argument in sequence (`references/writing.md` for the sentence and notation rules). Done when every figure the outline will show has a fact line with a locator (§3).
    **Hard rule — copy is rewritten, never reinvented**: slide copy is condensed from the source in the deck's language with the source's own vocabulary; entity names, product names, figures, and abbreviations stay in their original form; a figure the source does not contain is not on the slide. → runtime `number_without_fact` for figures; wording → manual
-3. Direct: define plausible directions, then compare two rendered compositions of the same representative content when the direction is open (`direction.md` §4; `references/review.md`). Select by reader understanding and visual craft, not style names; a fixed template or small edit keeps its approved direction. A preferred color alone does not settle composition. Use the kit palette and type as starting points, or adapt its tokens to the brand before creating slides. Done when the brief records the selection and the visible reason, not merely a named style.
-4. Plan each slide before any geometry (`composition.md` §0): job, relationship, move, composition, carriers, texture, rhythm. Decide what the reader should understand from the visual itself; choose the relevant evidence or a faithful visual explanation before arranging the remaining copy. Content over the mode's budget is split or cut, never squeezed. Then the deck's sequence in the brief's `rhythm:` line (`composition.md` §7: the marks — cover, section fields, closing — 5-13 evidence pages apart, the page grammar turning about every other page, never the same grammar on five in a row, a quiet page answered by colour within two), checked in the receipt's `deck.shape` before the render. Done when every slide has its plan line (§3).
+3. Direct: choose the reading order, type, palette, density, and structure for this request. Supplied templates and brand requirements take precedence. A `concept:` line is optional free text, not a catalogue selection. Related deliverables share facts and any requested identity, not necessarily layouts. Compare representative rendered pages only when it resolves a real uncertainty; an existing approved direction needs no contest. Done when the design has a reason grounded in the content and reader.
+4. Plan each slide's purpose, relationships, composition, and carriers in the brief (§3). Describe the layout in ordinary words, without selecting a recipe. Use as much space and repetition as the content needs: a comparison series may repeat a layout, a statement may be sparse, and an evidence page may be dense. Preserve the facts and qualifications; split content when it cannot remain readable rather than shrinking or deleting evidence. Done when every slide has a plan line describing what it actually carries.
 5. HTML route: the brief (§3) as a `<!-- BRIEF -->` comment, then one `<section class="slide">` per page, written after the design pass of `references/html.md` §8; the rest of this step is the script route. Script: the brief (§3) as a comment block, then `deck({ style, hue, accentHue?, mode, script, pairing, fonts })` — the brief's style id is passed here, not only written down — then the slides. The runtime runs the kit — the code blocks of `kit.md`, `charts.md`, and `pictures.md` — before the script, so the script never pastes a helper (it may redefine one). Each slide is measured down before it is drawn — `const top = head(…)`, `avail(top)` for the height left, `shareDown(top, columnsH(…))` / `readingH()` when a row or rail shares it, then the carrier on the stage or column those give (`composition.md` §4 "measure down before drawing"; the helpers refuse under their floors and name the fix, so no y or h is guessed) — and drawn spine → nodes → connectors → labels → garnish; every text box is measured (`MEASURE` through the kit helpers).
 6. `office action:'author' path:<deck.pptx> script:<html or pptxgenjs script>` (a source that opens with `<` is read as HTML; `overwrite:true` when re-authoring the same path) writes the file, opens the session, and returns three things (the HTML route adds `render.compare`, the HTML beside the PPTX render per page):
    - **pages** — every slide rendered and one contact sheet of the whole deck (unless `render:false`); the rendered pages come back as `images[]` (`page`, `path`) with the sheet as `contactSheet` (its file is always written; its image is attached past four slides, since a shorter deck's pages already show the sequence), and `pageCount` says how many the deck has;
@@ -70,6 +71,7 @@ Prerequisites: the Office capability (`metadata.requires`) — its portable back
 ```
 // BRIEF
 // subject/audience/action: <what this deck must make someone do>
+// concept: <optional free-text design intent; no catalogue id required>
 // reading mode: presentation | balanced | text · argument mode: pyramid | narrative | instructional | showcase | briefing
 // directions: A <style, seed hue, pairing, motif — one-sentence note> · B <…> · selected: <A|B> · why: <visible reason from trial, or fixed-template constraint>
 // style: <direction.md §3 id or custom> · palette: hue <deg> [· accent hue <deg>] · accent: <hex> · type: MODE <mode> → body <pt> · script: ko | ja | zh | latin · pairing: serif | weight | concord · fonts: noto | safe

package/src/defaults/skills/pptx/references/composition.md

@@ -2,14 +2,14 @@
 
 Owns how one slide is composed once the direction exists (`direction.md`). This is vocabulary the author composes with, not a catalog the slide picks from: there is no slide type to select, only a page job, a relationship, and a composition move the author decides before writing a coordinate. `kit.md` draws the core page, `charts.md` adds native data carriers, and `pictures.md` adds the picture families.
 
-Rule strength as in `direction.md`: **Hard rule** (with `→ runtime \`code\`` or `→ manual`), **Default**, **Reference**.
+Use this file as optional vocabulary and script-kit guidance. Layout recipes, density targets, rhythm intervals, type sizes, and decorative treatments are examples, not quotas for an HTML-authored page. Semantic relationships, explicit carrier promises, legibility, and the kit's actual geometry constraints still apply.
 
 ## 0. The page brief — decided before geometry (one plan line per slide)
 Each slide's plan line in the brief (`SKILL.md` §3) names, in this order:
 - **job** — cover · section · claim · evidence · process · comparison · structure · picture · closing (what the page does for the reader).
 - **relationship** — the atom the content carries (§1), or `none` for a focal claim.
 - **move** — what the reader now believes, decides, or does. **Hard rule — every slide states its move**: a slide that cannot state it is an outline defect — cut it or merge it, never decorate around it. → manual
-- **composition** — the page-scale move (§2 lens + §3 recipe in ordinary words: "one dark field on the left third holding the number; evidence hangs from a vertical rule on the right").
+- **composition** — describe the intended arrangement in ordinary words; no lens or recipe must be selected.
 - **carriers** — what carries the content: chart · table · picture · hero · statement · quote · specimen · diagram · prose · list (`author` refuses a page that does not carry what its line named: `plan_promise_missing`, `SKILL.md` §3).
 - **texture** — prose · list · specimen · keywords (§8).
 - **rhythm** — anchor · dense · breathing (§7).
@@ -50,7 +50,7 @@ Before coordinates, name the move the page makes and the jobs it serves (surface
 ## 3. Page recipes — back to front, omit every layer without a job (Reference)
 | Page job | Back-to-front stack | Stop when |
 |---|---|---|
-| cover | hero field — a full accent or dark field (Naver, Sequoia), a full-bleed picture under a scrim (Samsung, NVIDIA), or paper with a wordmark and one illustration field (Kakao) → optional scrim or wash → one purposeful contour or motif at full size (`motif()`) → kicker + title + one line (date · author), never a list. Without a picture the title itself is the anchor: `poster()` sets the claim at poster scale on the field (Sequoia, a16z), and the one hero object stands on the right third — `orb()`, the lit sphere half the page tall that 13 of 26 measured mock covers carry (the object 0.26-0.67 of the canvas; a motif at low alpha reads as background and a beat without an object measures 0) | copy is safe and title and field read as one object |
+| cover | hero field — a full accent or dark field (Naver, Sequoia), a full-bleed picture under a scrim (Samsung, NVIDIA), or paper with a wordmark and one illustration field (Kakao) → optional scrim or wash → one purposeful contour or motif at full size (`motif()`) → kicker + title + one line (date · author), never a list. Without a picture the title itself is the anchor: `poster()` sets the claim at poster scale on the field (Sequoia, a16z), and the one hero object stands on the right third — a picture, a drawn artifact, a `motif()` at full size, or a numeral (not `orb()`: the glowing sphere is on the generated-look list, `html.md` §8, and stays a script-route device for a brief that asks for it; the object 0.26-0.67 of the canvas — a motif at low alpha reads as background and a beat without an object measures 0) | copy is safe and title and field read as one object |
 | section | the cover's field again with the section name (Sequoia), a progressive agenda on the dark field with the current section lit (`agenda()`, the Coatue device), the section's number at 220 pt beside its claim (`numeralBeat()`, its default `size`; the a16z opener — every section a different accent field), or the label alone on paper (Kakao), or the section on its own picture — `picture()` full-bleed under a `scrim()`, the number and name in the scrim's light (the photo section of the Sequoia and Coatue decks; the one section device that carries a picture, so a photo deck's marks are not its cover repeated) → restrained wash → the motif at half size. Three devices, one deck: the section marks vary between them, never the same beat repeated | the deck language is recognizable and the reader knows where the deck is |
 | claim | quiet field → the statement or number at scale → one emphasis run or attribution → air where it gives the focal element room (below or beside, entering high). On paper the editorial hero (the frontier text page, measured across 26 rendered mock pages, September 2026): kicker → `display()` at cover size on two lines over 45-60% of the width → the deck line at lead size → a `statBand()` of three or four peers, or the one hero object (a picture, a product, a disc) on the right third → `dateline()` and the source closing the corners. Such a page measures only 0.02-0.09 largest object; the headline at 4-5 × the body, the strip under it, and the four corners are what separate it — never a card under the text | 40-60% of the canvas is deliberately empty |
 | evidence | title (+ sub line) on the open canvas, the source line at the foot → native chart/table/leaders filling the body between them, 40-60% of the canvas → the legend, a hero figure, or the kicker in the rail → optional takeaway on the dark field | the claim is native and the evidence is the largest element |
@@ -58,7 +58,7 @@ Before coordinates, name the move the page makes and the jobs it serves (surface
 | comparison | matched planes seamed by weight → optional shared wash or divider → matched labels → one difference marker on one side only | crop, elevation, and paint stay symmetric unless asymmetry is the claim |
 | structure | one field or outline → hierarchy by nesting, indentation, or scale → labels registered to their unit | placement alone communicates with color stripped |
 | picture | the picture family from `pictures.md` §2 — on a body page almost always the artifact row (`tiles()`: three or four screenshots, stills, or clippings on one baseline, a label and a caption each) or the collage (`clippings()`); the full-bleed photograph under a scrim is a cover or section device → modifier → native type on the calm zone | the captions say what each artifact proves; text sits on a scrim or beside the picture, never on it bare |
-| closing | the cover's field echoed (every reference deck closes on its cover's field: Samsung's photo, Naver's green, NVIDIA's swoosh, Kakao's mascot) → echoed contour or gradient, the motif at a corner, the cover's hero object at half size (`orb()`) → the ask or the thanks as the one line, in the on-dark accent (`poster()` at a step under the cover's size) → contact/meta | the ask is the most legible line |
+| closing | the cover's field echoed (every reference deck closes on its cover's field: Samsung's photo, Naver's green, NVIDIA's swoosh, Kakao's mascot) → echoed contour or gradient, the motif at a corner, the cover's hero object at half size → the ask or the thanks as the one line, in the on-dark accent (`poster()` at a step under the cover's size) → contact/meta | the ask is the most legible line |
 
 ## 4. Starting structures — relationship → geometry (Reference, first placements only)
 Canvas 13.33 × 7.5 in, margin `M` 0.6; safe area x 0.6-12.73, y 0.6-6.9. Proportion follows information weight; these are first placements, not slots.