@erclx/canon 5.24.0 → 5.25.0

package/docs/agents/design-board.md

@@ -1,33 +0,0 @@
----
-title: Design board
-description: Generating a static index over a project's design surfaces, what each panel reads, and which two stay toolkit-checkout-only
----
-
-# Design board
-
-`canon design board [--out <path>] [--root <path>]` generates a static page set indexing six design surfaces and reports the path a reader opens with `canon serve`. `--root` defaults to the main worktree the same way `canon teach`'s verbs resolve their own root. The surfaces panel's landing-page half and the whole components panel render only when that root is this toolkit's own checkout, since both read this repository's own build output rather than anything a target project produces. Running the installed CLI from inside a checkout of this project prints a mismatch warning when the caller's working directory disagrees with the root it resolved.
-
-Each panel reads what is already on disk and reports its own missing source rather than failing the run, so an absent build, an empty corpus, or a toolkit-only gate renders an empty-state message instead of a broken frame.
-
-```bash
-canon design board
-canon serve .canon/tmp/render/board
-```
-
-| Option             | Default                   | Behavior                                      |
-| ------------------ | ------------------------- | --------------------------------------------- |
-| `-o, --out <path>` | `.canon/tmp/render/board` | Output directory                              |
-| `--root <path>`    | The main worktree         | Project root the board reads its sources from |
-
-## Panels
-
-- **Tokens** renders `DESIGN.md` through the same renderer `canon design render` uses, rather than a second one, reading `<root>/canon/DESIGN.md` or `<root>/.claude/DESIGN.md` for a target that has not run `canon migrate surface-roots`.
-- **Surfaces** iframes the built landing page from `<root>/web/dist/` and a teach workspace from `<root>/.canon/teach/`, copying each whole into the board's own tree. The landing-page half reports a toolkit-only notice outside this toolkit's own checkout, and either half reports its own missing build or absent workspace rather than rendering a broken frame.
-- **Wireframes** reads every `**/*.md` under `<root>/canon/wireframes/` or `<root>/.claude/wireframes/`, excluding `index.md` at any depth, and renders each file as-is inside a `<pre>`, labeled from its own `description` frontmatter field. Reports the whole panel empty rather than per file when the directory is absent or holds nothing to render.
-- **Past candidates** lists an arm capture image per folder under `<root>/.canon/picks/`, skipping `references/`, and states the corpus carries none rather than rendering an empty grid.
-- **Components** iframes the gallery built by `bun run web:gallery`, a second Astro config at `web/gallery.config.mjs` reading `web/gallery-src/` and writing `web/gallery-dist/`. That config's `srcDir` is never read by `web:build`'s own config, so the gallery never reaches the published `web/dist/`. The gallery page renders every component under `web/src/components/` except two whose props carry no defaults, which it names rather than filling with invented data. Reports a toolkit-only notice outside this toolkit's own checkout, and a missing gallery build otherwise.
-- **References** lists whatever image an operator has dropped flat under `<root>/.canon/picks/references/`, with no fetching and no second token source: a reference is an image, nothing more. Reports the folder as absent or as present but carrying no image rather than rendering an empty grid.
-
-## What it does not do
-
-The board never writes outside its own output directory and never builds `web/dist/` on a caller's behalf. `web/dist/` and `.canon/teach/` are read, not written, and copied into the board's tree only for that run: the generator clears and recreates its output directory on every call, so a caller relying on it to persist between runs is relying on an accident. It refuses rather than clearing a directory that is or contains the project root or the caller's own working directory, which is what an `--out .` typo would otherwise do, including when a global install resolves the project root to a different checkout than the one the caller stands in.

package/governance/rules/standards/diagrams.md

@@ -1,14 +0,0 @@
----
-# Generated by `canon gov regen` from standards/diagrams.md. Edit that frontmatter, not this file.
-description: Shape and content rules for .canon/diagrams/<kind>.md files
-paths:
-  - '.canon/diagrams/**'
----
-
-# Diagram standards
-
-## Authority
-
-- Follow the diagrams standard for shape and content rules for .canon/diagrams/<kind>.md files. It is the single source. Read it with `canon standards diagrams`.
-- Layout, budgets, accessibility, labels, and render verification inside the fence are a separate topic. The mermaid standard routes them.
-- A diagram entry carries structure and flow, not implementation. Read the standard before adding or revising a kind.

package/governance/rules/standards/mermaid.md

@@ -1,15 +0,0 @@
----
-# Generated by `canon gov regen` from standards/mermaid.md. Edit that frontmatter, not this file.
-description: Direction and layout, node and edge budgets, accessibility fields, label punctuation, and render verification for a Mermaid diagram
-paths:
-  - '**/*.md'
----
-
-# Mermaid standards
-
-## Authority
-
-- Follow the mermaid standard for direction and layout, node and edge budgets, accessibility fields, label punctuation, and render verification for a Mermaid diagram. It is the single source. Read it with `canon standards mermaid`.
-- Apply this rule only when the edit drafts or revises a Mermaid fence. Skip it on a markdown edit carrying no diagram.
-- Read it before drafting the fence. Do not work the layout or the budgets from memory.
-- Which diagram a document carries and what question it answers is a separate topic. The diagrams standard routes it.

package/scripts/core/check-gallery-exclusion.sh

@@ -1,50 +0,0 @@
-#!/usr/bin/env bash
-set -e
-set -o pipefail
-
-SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-PROJECT_ROOT="${PROJECT_ROOT:-$(cd "$SCRIPT_DIR/../.." && pwd)}"
-
-WEB_DIST="$PROJECT_ROOT/web/dist"
-GALLERY_DIST="$PROJECT_ROOT/web/gallery-dist"
-MARKER='name="canon-gallery-marker"'
-
-# Nothing to grep without a build. Callers run this after `bun run web:build`
-# and `bun run web:gallery`, so an absent dist here means a build step itself
-# failed rather than something this check can verify.
-if [ ! -d "$WEB_DIST" ]; then
-  echo "No $WEB_DIST. Run bun run web:build first." >&2
-  exit 1
-fi
-
-if [ ! -d "$GALLERY_DIST" ]; then
-  echo "No $GALLERY_DIST. Run bun run web:gallery first." >&2
-  exit 1
-fi
-
-# A prose notice is not load-bearing: rewording it silently retires the leak
-# check it backed with every workflow still green. The marker is a fixed
-# `<meta>` tag `web/gallery-src/pages/index.astro` carries for exactly this,
-# so asserting it survives in the gallery's own build is what turns a dropped
-# marker into a loud failure here rather than a blind spot in the check below.
-if ! grep -rl "$MARKER" "$GALLERY_DIST" >/dev/null 2>&1; then
-  echo "The gallery build at $GALLERY_DIST carries no $MARKER. The gallery page dropped its own marker, which is what the leak check below reads for." >&2
-  exit 1
-fi
-
-# `web/gallery.config.mjs` keeps the components-panel gallery out of the
-# published build by never pointing its srcDir at it. A later config change
-# that widens srcDir, or a gallery file moving under web/src/, would publish
-# this repository's component internals to a live domain with every other
-# check still green, which is what this guards against.
-if find "$WEB_DIST" -iname '*gallery*' | grep -q .; then
-  echo "A file named for the gallery reached $WEB_DIST. See web/gallery.config.mjs's srcDir." >&2
-  exit 1
-fi
-
-if grep -rl "$MARKER" "$WEB_DIST" >/dev/null 2>&1; then
-  echo "The gallery's own marker ($MARKER) reached $WEB_DIST. See web/gallery.config.mjs's srcDir." >&2
-  exit 1
-fi
-
-echo "check-gallery-exclusion: gallery marker present in $GALLERY_DIST, absent from $WEB_DIST"