@erclx/canon 5.52.0 → 5.54.0

package/claude/skills/canvas-board/references/canvas.md

@@ -1,170 +0,0 @@
----
-title: Canvas reference
-description: Page folders, frame files, the layout.json shape, token resolution, and what a frame must not assume on a local design canvas
----
-
-# Canvas reference
-
-Applies to the canvas content under `.canon/canvas/`, where each page is a folder of HTML frames and a layout file placing them. A frame is a draft drawn to be looked at and picked from, so it changes whenever someone tries a direction, and the operator clears it once the direction lands where the project keeps its design.
-
-The folder is gitignored, so nothing in a repository checks its shape and nothing backs it up by default.
-
-## Contents
-
-- [Scope](#scope)
-- [What a working canvas looks like](#what-a-working-canvas-looks-like)
-- [Pages](#pages)
-- [Frames](#frames)
-- [House style](#house-style)
-- [Layout](#layout)
-- [Tokens](#tokens)
-- [What a frame must not assume](#what-a-frame-must-not-assume)
-- [Template](#template)
-
-## Scope
-
-Governs the canvas content under `.canon/canvas/`: page folder names, frame files, the `layout.json` shape, how tokens reach a frame, and what a frame must not assume about where it renders.
-
-- Also governs the house style of an explanation frame, being a diagram, a board of notes, or a comparison
-- A mockup of the project's own interface is not an explanation frame, and follows the project's design document for type, color, and layout
-
-Does not govern:
-
-- The design decisions a mockup frame is drafting, such as type, color, and layout taste: the project's own design document
-- The project's design document and the token module it renders from, which a picked direction is carried into: `design.md`
-- The procedure that starts the canvas, reads the operator's selection, and carries a pick back, which belongs to the surface driving the canvas
-- Voice, rhythm, and sentence construction in any text a frame shows: the `write-human` skill
-
-## What a working canvas looks like
-
-A canvas works when the operator and a session can point at the same thing and see the same thing:
-
-- Which pages exist, and which frames sit on each?
-- Where does each frame sit on its page, and at what width does it render?
-- Does each frame show the project's own tokens rather than values copied into it?
-- Does a frame render the same in the live canvas as in a capture?
-
-A canvas failing these is non-conforming even when it satisfies every shape rule below.
-
-## Pages
-
-- Make one folder per page directly under `.canon/canvas/`. A page groups the frames compared side by side, such as the candidates for one decision.
-- Name a page as one path segment of letters, digits, dots, dashes, and underscores, starting with a letter or a digit. A name opening with a dot is hidden from every listing.
-- Never write a folder whose name opens with a dot. Those names are reserved for files the canvas generates and removes itself.
-- Rename a page rather than copying it under a new name, so its layout and frames stay together.
-
-## Frames
-
-- Write one frame as one `.html` file inside its page folder. The filename without its extension is the frame's name, and the name follows the page naming rule.
-- Write a frame as a whole document or as a fragment. The server writes in the `html`, `head`, and `body` a fragment leaves out, marked so a pick still matches the file.
-- State a `body` whenever the frame states a `head`. The browser builds one the file leaves out, and an address the operator picks inside the frame can no longer be matched to the file.
-- Write every table with its `tbody` stated, for the same reason. A browser adds one the file leaves out.
-
-### Content and edits
-
-A frame is the only copy of its markup, so it carries everything it needs.
-
-- Keep a frame self-contained. Inline its own styles and scripts, or link a file inside the same page folder, since a frame is served from its page and nothing outside the canvas resolves.
-- Use the project's custom properties, `var(--<name>)`, for every value the token stylesheet defines. A literal copied from it shows the right color today and the wrong one after the next token change.
-- Edit a frame by rewriting its file. The file is the frame, and nothing else holds a copy of its markup.
-
-## House style
-
-Applies to an explanation frame only. A mockup of the project's interface renders at the app's own sizes and follows the project's design document instead.
-
-- Write text in sentence case. Use no all-caps text and no `text-transform: uppercase`.
-- Keep lines short, one fact a line.
-- Set body text at 20px or larger and headings at 44px or larger. Set nothing under 16px.
-- Render an explanation frame about 1100px wide.
-
-### Colors, faces, and fit
-
-Take colors from the project's custom properties. A frame defining colors of its own sets the dark values on `:root` and the light ones under `[data-theme="light"]`, since the shell sets `data-theme` on each frame's root.
-
-- Name only the faces the canvas serves into every frame, being `Geist Variable` for text, `Noto Sans Mono` for code, and `Excalifont` for a hand-drawn look
-- Those render the same in a capture and in any browser, so a height fitted against them holds
-- Make each box tall enough to show all its content, with no scrollbar and no clipped line
-- Run `canon canvas fit <page>/<frame>` rather than estimating, since it measures the content in the capture browser and sets the height
-- Read frames left to right in reading order. Let `frame add` place each frame after the last with the standard gap, and move one only when the operator asks for a position.
-
-## Layout
-
-- Keep one `layout.json` per page, beside its frames. It holds each frame's box and nothing else, so moving a frame never rewrites its markup.
-- Key each box by the frame's name, under one top-level `frames` object.
-- Give every box four finite numbers in pixels: `x` and `y` for its top-left corner on the page, `width` for the width the frame renders at, and `height` for the height it shows on the canvas.
-
-### Missing boxes and writes
-
-The layout file is shared state, so a write never discards a box another writer or reader holds.
-
-- Leave a frame out of the layout only when its position does not matter yet. A reader places an unnamed frame in a row after the others, at the default size of 1440 by 900.
-- Never write the file while a writer holds its lock, which is the same name with `.lock` appended. Two writers each replacing the whole file lose one of the two edits.
-- Treat a layout that does not parse as a defect to repair, never as an empty one to overwrite. Writing over it erases every box it held.
-
-The keys below are the ones a reader parses. The frame names are placeholders.
-
-```json
-{
-  "frames": {
-    "hero-a": { "x": 0, "y": 0, "width": 1440, "height": 900 },
-    "hero-b": { "x": 1520, "y": 0, "width": 1440, "height": 900 }
-  }
-}
-```
-
-## Tokens
-
-- Expect the token stylesheet first in every frame's `head` when it is served, ahead of anything the frame links. A stylesheet the frame links itself still wins the cascade.
-- Read the tokens from the canvas tool's own module inside its own checkout, else the project's installed base stylesheet plus its project override folder, else none
-- A canvas with no token source renders unstyled and says so
-- Never paste the token stylesheet into a frame. The injected copy follows the project, and a pasted one stops following it the moment it is written.
-
-## What a frame must not assume
-
-- Do not assume a viewport. A frame renders at its layout width on the canvas and in a capture alike, so size it with media queries against that width rather than against the operator's window.
-- Do not assume the theme. The canvas theme toggle is the operator's own state, and a capture shows each frame in its default theme.
-- Do not assume a network. Name a served face, or ship the font beside the frame, since a capture refuses a frame naming a font it cannot find.
-
-### Font, source, and checkout
-
-Do not assume a default font. Set `font-family` with a served face first on an element the frame's text inherits from, since a capture checks the first family of the text it renders and the browser's default serif is absent from many machines.
-
-- A frame naming a machine family such as `DejaVu Sans` renders at another height in another browser, which `canon canvas fit` reports
-- Do not assume the frame is the source. A picked direction is carried into the project's design document or a plan, and the operator clears the frame once it has been carried.
-- Do not assume the canvas survives the checkout. The folder is gitignored, so a lost checkout loses every page in it.
-
-## Template
-
-A new frame starts from this skeleton. The names in it are placeholders.
-
-```html
-<!doctype html>
-<html lang="en">
-  <head>
-    <meta charset="utf-8" />
-    <title>frame-name</title>
-    <style>
-      html {
-        font-family: installed-family, sans-serif;
-      }
-      main {
-        padding: var(--space-lg);
-        color: var(--color-text);
-        background: var(--color-background);
-      }
-      /* only a color the frame defines itself: dark on :root, light here */
-      :root {
-        --frame-accent: #7aa2ff;
-      }
-      [data-theme='light'] {
-        --frame-accent: #1f4fd8;
-      }
-    </style>
-  </head>
-  <body>
-    <main>
-      <h1>frame-name</h1>
-    </main>
-  </body>
-</html>
-```

package/claude/skills/draft-and-pick/REQUIREMENT.md

@@ -1,26 +0,0 @@
----
-name: draft-and-pick
-description: Why a pointer answers under the old `draft-and-pick` name, and the test that retires it
----
-
-# Draft and pick requirement
-
-## Gap
-
-Without this skill, a person typing the old name after the rename to `pick-by-eye` meets an unknown command that names no successor. A target that has not run `canon migrate skill-names` still tells people to type it, and so does a live gitignored record, which the sweep never reads.
-
-## Must
-
-- Name `pick-by-eye` as the skill to run, so a typed invocation of the old name reaches the new one in one step
-- Carry `disable-model-invocation: true`, so routing never matches the old description against a request `pick-by-eye` owns
-- Retire once `canon migrate skill-names --json` reports zero citations in every target the rollout reaches and no live `.canon/` record names the old name
-
-## Must not
-
-- Carry any part of the draft and pick loop, which would give one behavior two bodies that drift apart
-- Retire on a release number, which retires it on a date nothing measured
-
-## Out of scope
-
-- The work itself, which `pick-by-eye` owns
-- Rewriting a stale citation, which `canon migrate skill-names` owns in a tracked file and the controlling session owns on the board

package/claude/skills/draft-and-pick/SKILL.md

@@ -1,11 +0,0 @@
----
-name: draft-and-pick
-description: Renamed from `draft-and-pick` to `pick-by-eye`. Answers a typed invocation of the old pick skill name by pointing at the new one.
-disable-model-invocation: true
-metadata:
-  family: decide
----
-
-# Draft and pick
-
-This skill is now `pick-by-eye`. Run `/canon:pick-by-eye` instead, and change any file that still names this one.

package/claude/skills/draft-doc/REQUIREMENT.md

@@ -1,26 +0,0 @@
----
-name: draft-doc
-description: Why a pointer answers under the old `draft-doc` name, and the test that retires it
----
-
-# Draft doc requirement
-
-## Gap
-
-Without this skill, a person typing the old name after the rename to `write-doc` meets an unknown command that names no successor. A target that has not run `canon migrate skill-names` still tells people to type it, and so does a live gitignored record, which the sweep never reads.
-
-## Must
-
-- Name `write-doc` as the skill to run, so a typed invocation of the old name reaches the new one in one step
-- Carry `disable-model-invocation: true`, so routing never matches the old description against a request `write-doc` owns
-- Retire once `canon migrate skill-names --json` reports zero citations in every target the rollout reaches and no live `.canon/` record names the old name
-
-## Must not
-
-- Carry any part of the document draft, which would give one behavior two bodies that drift apart
-- Retire on a release number, which retires it on a date nothing measured
-
-## Out of scope
-
-- The work itself, which `write-doc` owns
-- Rewriting a stale citation, which `canon migrate skill-names` owns in a tracked file and the controlling session owns on the board

package/claude/skills/draft-doc/SKILL.md

@@ -1,11 +0,0 @@
----
-name: draft-doc
-description: Renamed from `draft-doc` to `write-doc`. Answers a typed invocation of the old doc skill name by pointing at the new one.
-disable-model-invocation: true
-metadata:
-  family: generate
----
-
-# Draft doc
-
-This skill is now `write-doc`. Run `/canon:write-doc` instead, and change any file that still names this one.

package/claude/skills/draft-figure/REQUIREMENT.md

@@ -1,26 +0,0 @@
----
-name: draft-figure
-description: Why a pointer answers under the old `draft-figure` name, and the test that retires it
----
-
-# Draft figure requirement
-
-## Gap
-
-Without this skill, a person typing the old name after the rename to `draw-figure` meets an unknown command that names no successor. A target that has not run `canon migrate skill-names` still tells people to type it, and so does a live gitignored record, which the sweep never reads.
-
-## Must
-
-- Name `draw-figure` as the skill to run, so a typed invocation of the old name reaches the new one in one step
-- Carry `disable-model-invocation: true`, so routing never matches the old description against a request `draw-figure` owns
-- Retire once `canon migrate skill-names --json` reports zero citations in every target the rollout reaches and no live `.canon/` record names the old name
-
-## Must not
-
-- Carry any part of the figure draft, which would give one behavior two bodies that drift apart
-- Retire on a release number, which retires it on a date nothing measured
-
-## Out of scope
-
-- The work itself, which `draw-figure` owns
-- Rewriting a stale citation, which `canon migrate skill-names` owns in a tracked file and the controlling session owns on the board

package/claude/skills/draft-figure/SKILL.md

@@ -1,11 +0,0 @@
----
-name: draft-figure
-description: Renamed from `draft-figure` to `draw-figure`. Answers a typed invocation of the old figure skill name by pointing at the new one.
-disable-model-invocation: true
-metadata:
-  family: generate
----
-
-# Draft figure
-
-This skill is now `draw-figure`. Run `/canon:draw-figure` instead, and change any file that still names this one.

package/claude/skills/draft-identity/REQUIREMENT.md

@@ -1,26 +0,0 @@
----
-name: draft-identity
-description: Why a pointer answers under the old `draft-identity` name, and the test that retires it
----
-
-# Draft identity requirement
-
-## Gap
-
-Without this skill, a person typing the old name after the rename to `design-identity` meets an unknown command that names no successor. A target that has not run `canon migrate skill-names` still tells people to type it, and so does a live gitignored record, which the sweep never reads.
-
-## Must
-
-- Name `design-identity` as the skill to run, so a typed invocation of the old name reaches the new one in one step
-- Carry `disable-model-invocation: true`, so routing never matches the old description against a request `design-identity` owns
-- Retire once `canon migrate skill-names --json` reports zero citations in every target the rollout reaches and no live `.canon/` record names the old name
-
-## Must not
-
-- Carry any part of the logo and social card draft, which would give one behavior two bodies that drift apart
-- Retire on a release number, which retires it on a date nothing measured
-
-## Out of scope
-
-- The work itself, which `design-identity` owns
-- Rewriting a stale citation, which `canon migrate skill-names` owns in a tracked file and the controlling session owns on the board

package/claude/skills/draft-identity/SKILL.md

@@ -1,11 +0,0 @@
----
-name: draft-identity
-description: Renamed from `draft-identity` to `design-identity`. Answers a typed invocation of the old identity skill name by pointing at the new one.
-disable-model-invocation: true
-metadata:
-  family: generate
----
-
-# Draft identity
-
-This skill is now `design-identity`. Run `/canon:design-identity` instead, and change any file that still names this one.

package/claude/skills/draft-ready/REQUIREMENT.md

@@ -1,26 +0,0 @@
----
-name: draft-ready
-description: Why a pointer answers under the old `draft-ready` name, and the test that retires it
----
-
-# Draft ready requirement
-
-## Gap
-
-Without this skill, a person typing the old name after the rename to `plan-ready` meets an unknown command that names no successor. A target that has not run `canon migrate skill-names` still tells people to type it, and so does a live gitignored record, which the sweep never reads.
-
-## Must
-
-- Name `plan-ready` as the skill to run, so a typed invocation of the old name reaches the new one in one step
-- Carry `disable-model-invocation: true`, so routing never matches the old description against a request `plan-ready` owns
-- Retire once `canon migrate skill-names --json` reports zero citations in every target the rollout reaches and no live `.canon/` record names the old name
-
-## Must not
-
-- Carry any part of the ready folder packaging, which would give one behavior two bodies that drift apart
-- Retire on a release number, which retires it on a date nothing measured
-
-## Out of scope
-
-- The work itself, which `plan-ready` owns
-- Rewriting a stale citation, which `canon migrate skill-names` owns in a tracked file and the controlling session owns on the board

package/claude/skills/draft-ready/SKILL.md

@@ -1,11 +0,0 @@
----
-name: draft-ready
-description: Renamed from `draft-ready` to `plan-ready`. Answers a typed invocation of the old ready skill name by pointing at the new one.
-disable-model-invocation: true
-metadata:
-  family: generate
----
-
-# Draft ready
-
-This skill is now `plan-ready`. Run `/canon:plan-ready` instead, and change any file that still names this one.

package/claude/skills/draft-screencast/REQUIREMENT.md

@@ -1,26 +0,0 @@
----
-name: draft-screencast
-description: Why a pointer answers under the old `draft-screencast` name, and the test that retires it
----
-
-# Draft screencast requirement
-
-## Gap
-
-Without this skill, a person typing the old name after the rename to `script-screencast` meets an unknown command that names no successor. A target that has not run `canon migrate skill-names` still tells people to type it, and so does a live gitignored record, which the sweep never reads.
-
-## Must
-
-- Name `script-screencast` as the skill to run, so a typed invocation of the old name reaches the new one in one step
-- Carry `disable-model-invocation: true`, so routing never matches the old description against a request `script-screencast` owns
-- Retire once `canon migrate skill-names --json` reports zero citations in every target the rollout reaches and no live `.canon/` record names the old name
-
-## Must not
-
-- Carry any part of the screencast script draft, which would give one behavior two bodies that drift apart
-- Retire on a release number, which retires it on a date nothing measured
-
-## Out of scope
-
-- The work itself, which `script-screencast` owns
-- Rewriting a stale citation, which `canon migrate skill-names` owns in a tracked file and the controlling session owns on the board

package/claude/skills/draft-screencast/SKILL.md

@@ -1,11 +0,0 @@
----
-name: draft-screencast
-description: Renamed from `draft-screencast` to `script-screencast`. Answers a typed invocation of the old screencast skill name by pointing at the new one.
-disable-model-invocation: true
-metadata:
-  family: generate
----
-
-# Draft screencast
-
-This skill is now `script-screencast`. Run `/canon:script-screencast` instead, and change any file that still names this one.

package/claude/skills/draft-slides/REQUIREMENT.md

@@ -1,26 +0,0 @@
----
-name: draft-slides
-description: Why a pointer answers under the old `draft-slides` name, and the test that retires it
----
-
-# Draft slides requirement
-
-## Gap
-
-Without this skill, a person typing the old name after the rename to `make-deck` meets an unknown command that names no successor. A target that has not run `canon migrate skill-names` still tells people to type it, and so does a live gitignored record, which the sweep never reads.
-
-## Must
-
-- Name `make-deck` as the skill to run, so a typed invocation of the old name reaches the new one in one step
-- Carry `disable-model-invocation: true`, so routing never matches the old description against a request `make-deck` owns
-- Retire once `canon migrate skill-names --json` reports zero citations in every target the rollout reaches and no live `.canon/` record names the old name
-
-## Must not
-
-- Carry any part of the deck draft, which would give one behavior two bodies that drift apart
-- Retire on a release number, which retires it on a date nothing measured
-
-## Out of scope
-
-- The work itself, which `make-deck` owns
-- Rewriting a stale citation, which `canon migrate skill-names` owns in a tracked file and the controlling session owns on the board

package/claude/skills/draft-slides/SKILL.md

@@ -1,11 +0,0 @@
----
-name: draft-slides
-description: Renamed from `draft-slides` to `make-deck`. Answers a typed invocation of the old slides skill name by pointing at the new one.
-disable-model-invocation: true
-metadata:
-  family: generate
----
-
-# Draft slides
-
-This skill is now `make-deck`. Run `/canon:make-deck` instead, and change any file that still names this one.

package/claude/skills/make-deck/REQUIREMENT.md

@@ -1,36 +0,0 @@
----
-name: make-deck
-description: Why the skill draws a deck as HTML in the project's tokens inside its own folder, why the CLI owns the conversion, and why one render is read back before the deck is called done
----
-
-# Make deck requirement
-
-## Gap
-
-Without this skill, a session writes a deck into whatever path occurs to it, so a second deck overwrites the first and nothing lists either. It writes pptxgenjs code or hex colors, so the deck ignores the project's design. Every slide comes out as a title over bullets, which reads as a document rather than a deck.
-
-It invents attributes the converter does not read, so a section, a chart, or an entrance silently goes missing. A first render shipped unread hands the audience the overlap, the overflow, and every element the converter fell back to a picture for.
-
-## Must
-
-- The existing decks and the slide format are read from the CLI before drawing, and a new deck takes a name no listed deck carries unless the request names one
-- Each deck lands in its own folder under the slides record folder, one HTML file per slide in filename order, drawn with the project's custom properties
-- The composition varies across the deck, and content fits the slide frame with short titles and tight lines
-- The render command produces the deck itself
-- Every fallback and refusal the render reports is read, one QA pass runs over the rendered images, and what both report is fixed once
-
-## Must not
-
-- Hardcode a deck name, an attribute, or a chart type, or reimplement the conversion, the master, or the packaging the CLI owns
-- Write a deck into the shared layouts folder, which is never listed as a deck
-- Invent token values when the project has no token stylesheet, rather than saying the deck renders unstyled
-- Write centered body text or content that overflows a slide
-- Loop on aesthetics past a single fix pass, or fail the render when the image tools for the QA pass are missing
-
-## Out of scope
-
-- Converting HTML to PowerPoint, which the CLI owns end to end
-- The project's palette and faces, which its token stylesheet owns
-- Writing the content the deck is about, which the caller owns
-- Drafting a deck as a canvas page, which no skill owns until that authoring surface is measured
-- Recording a demo, which `script-screencast` owns

package/claude/skills/make-deck/SKILL.md

@@ -1,80 +0,0 @@
----
-name: make-deck
-description: Draws a deck as HTML slides in the project's own design, one folder under `.canon/slides/` per deck, then renders it to an editable PowerPoint file via `canon slides render`. Use when asked to "draft slides", "make a deck", "build a presentation", "turn this into slides", or "render the deck". Holds the deck design rules. Do NOT reimplement the conversion. The CLI owns layout into PowerPoint shapes, the master, and packaging. Assumes the `canon` CLI is on PATH.
-metadata:
-  family: generate
----
-
-# Make deck
-
-Draw each slide as an HTML file in a deck folder, then shell out to `canon slides render`. The CLI lays every slide out in a browser and rebuilds it as editable PowerPoint shapes. This skill owns the content, the slide markup, and the design choices the markup encodes.
-
-## Read the decks and the format
-
-Run the list first, then read the format. Never hardcode a deck name, an attribute, or a chart type.
-
-```bash
-canon slides list --json 2>/dev/null
-```
-
-The list returns one row per deck, carrying its `name`, `title`, slide count, and `path`. When the request names a deck the list holds, edit that folder. Otherwise pick a new kebab-case name no row carries.
-
-Read `${CLAUDE_SKILL_DIR}/references/deck.md`. It states what `deck.json` holds, what each slide declares on its `<body>`, the motion attributes, speaker notes, and charts. Each refusal prints as a `✗` line from the render.
-
-## Draw the deck
-
-A deck folder sits at `.canon/slides/<deck>/` from the project root, and holds:
-
-- One `.html` file per slide, rendered in filename order. Number them with a zero-padded prefix, such as `01-cover.html`, so a slide inserted later sorts where it belongs.
-- `deck.json`, optional, for the title, the header and footer bands, slide numbers, the mark, and embedded faces.
-- `assets/` for images the slides reference by a relative path.
-
-Never write a slide into `.canon/slides/layouts/`. That folder holds the project's shared layouts and is never listed as a deck.
-
-Each slide is a full HTML document laid out at 1280 by 720 CSS pixels. Position its blocks absolutely or with a flex or grid container sized to that frame, and keep every element inside it.
-
-## Design rules
-
-The render injects the project's token stylesheet ahead of each slide's own styles, so the deck takes the project's design rather than the toolkit's.
-
-- Use the project's custom properties, such as `var(--color-accent)`, for every color, face, and spacing value, read from `.claude/design/base.css` and overrides under `.claude/design/project/`
-- When neither exists, say the deck renders unstyled rather than inventing values to cover it
-- Leave the `--color-*` roles to the stylesheet. The master reads its colors off the first slide's `<html>`, so a slide computing its own `--color-text` is reported, since the bands keep the master's.
-- Vary the composition across slides. Never repeat a title over bullets on every slide. Reach for columns, a row of large numbers, a grid of cards, a chart, a pull quote, and section dividers.
-
-### Fit and shapes
-
-Text and shapes have to survive the conversion.
-
-- Keep titles short and lines tight, so text fits its box at the size the design sets rather than overflowing the frame.
-- Never write centered body text.
-- Prefer CSS the converter maps to native shapes. An unmappable property is drawn as a picture and reported on stderr, so a slide full of gradients and filters stops being editable.
-
-## Render
-
-Shell out to the CLI. It writes the deck and reports the path.
-
-```bash
-canon slides render <deck>
-```
-
-With one deck in the project the name can be left out. The render refuses with the deck list when there are several. Pass `--open` to open the deck, and `--mirror <dir>`, or set `CANON_SLIDES_MIRROR`, to copy it into a synced folder.
-
-Read every `✗` line the render prints. A picture fallback, a refused link, chart, or effect, and a missing token each leave the deck written with that piece degraded or left out.
-
-## QA loop
-
-Run this once after the first render, then stop.
-
-1. Convert the deck with `soffice --headless --convert-to pdf <deck>.pptx`, then `pdftoppm -r 90 -png <deck>.pdf slide`. If either is missing, skip the image pass and say so rather than fail the render.
-2. Open and inspect every rendered image in this session, checking each slide for overlap, overflow, low contrast, and empty regions.
-3. Fix the reported issues and the `✗` lines in the slide files once, re-render, and stop. Do not loop indefinitely on aesthetics.
-
-## Response
-
-After rendering, report:
-
-- The deck folder, the slide count, and the written `.pptx` path
-- Whether the project's token stylesheet was found
-- Each `✗` line the final render printed, or that it printed none
-- Any QA issues found and what changed, or that the deck passed clean