chore(release): 0.9.0

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

.debrand

@@ -1,4 +1,4 @@
-# Upstream (michaelshimeles/paper-rs) carries no ArtCraft/Discord branding; keep it that way. Run: perl tools/craft-skills/skills/debrand/debrand.pl --check .
+# The tree carries no ArtCraft/Discord branding; keep it that way. Run: perl tools/craft-skills/skills/debrand/debrand.pl --check .
 keep ^(LICENSE-(MIT|APACHE)|\.debrand)$
 forbid (?i)artcraft
 forbid (?i)discord

.github/CODEOWNERS

@@ -0,0 +1 @@
+* @nxtime

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,19 @@
+---
+name: Bug report
+about: Something does not work as expected
+labels: bug
+---
+
+**What happened**
+
+**What you expected**
+
+**Steps to reproduce**
+1.
+2.
+
+**Version and platform**
+PaperCraft version (the release you installed), OS, and the GPU if it is a rendering problem.
+
+**Screenshot, recording or project**
+Attach one if you can. Remove anything private first.

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,5 @@
+blank_issues_enabled: true
+contact_links:
+  - name: Security vulnerability
+    url: https://github.com/nxtime/papercraft/security/advisories/new
+    about: Report security problems privately, not as an issue.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,14 @@
+---
+name: Feature request
+about: Suggest an idea or a missing capability
+labels: enhancement
+---
+
+**The problem**
+What are you trying to do, and what gets in the way?
+
+**What you would like**
+
+**Alternatives you considered**
+
+**Is it already in ROADMAP.md?**

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,24 @@
+## What and why
+
+<!-- What changed, and the problem it solves. Link the issue: Fixes #123 -->
+
+## How I tested it
+
+<!-- Tests added, commands run, platforms tried. -->
+
+## AI assistance
+
+<!-- Which tool helped and how much, or "none". See AI_POLICY.md. You must understand every line. -->
+
+## Screenshots
+
+<!-- For UI changes: before and after, at scale 2, in each theme. -->
+
+## Checklist
+
+- [ ] Tests first; new code is covered, error paths included
+- [ ] `cargo fmt --all`, `cargo clippy --all-targets` and the affected `cargo test --test` targets pass
+- [ ] Follows [RULES.md](../RULES.md) (no overflow, data safety, one undo step per tool call)
+- [ ] Docs, tool descriptions and `PROGRESS.md` updated where needed
+- [ ] Conventional commit messages
+- [ ] I read and understand every line of this change (AI-assisted or not)

.github/workflows/release.yml

@@ -0,0 +1,95 @@
+# Builds Windows, macOS and Linux on GitHub's runners when a v* tag is pushed, then publishes a
+# GitHub release with the files once the full test suite (test.yml) passes. Gitea reads .github/workflows too, so every job is gated on the
+# server URL: this pipeline only ever runs on github.com.
+name: release
+
+on:
+  push:
+    tags: ["v*"]
+  workflow_dispatch:
+    inputs:
+      tag:
+        description: Existing tag to build and release (e.g. v0.8.4)
+        required: true
+
+permissions:
+  contents: write
+
+env:
+  CARGO_TERM_COLOR: always
+  TAG: ${{ inputs.tag || github.ref_name }}
+
+jobs:
+  test:
+    uses: ./.github/workflows/test.yml
+    with: { ref: "${{ inputs.tag || github.ref }}" }
+
+  windows:
+    if: github.server_url == 'https://github.com'
+    runs-on: windows-latest
+    steps:
+      - uses: actions/checkout@v4
+        with: { ref: "${{ inputs.tag || github.ref }}" }
+      - uses: dtolnay/rust-toolchain@stable
+      - uses: Swatinem/rust-cache@v2
+      - name: Build and zip
+        shell: pwsh
+        run: |
+          cargo build --release --locked --bins
+          $v = $env:TAG.TrimStart('v')
+          New-Item -ItemType Directory -Force dist | Out-Null
+          $exes = 'papercraft','papercraft-cli','papercraft-mcp','papercraft-relay' | ForEach-Object { "target/release/$_.exe" }
+          Compress-Archive -Path $exes -DestinationPath "dist/papercraft-$v-windows-x86_64.zip"
+      - uses: actions/upload-artifact@v4
+        with: { name: windows, path: dist/* }
+
+  macos:
+    if: github.server_url == 'https://github.com'
+    runs-on: macos-latest
+    steps:
+      - uses: actions/checkout@v4
+        with: { ref: "${{ inputs.tag || github.ref }}" }
+      - uses: dtolnay/rust-toolchain@stable
+        with: { targets: aarch64-apple-darwin }
+      - uses: Swatinem/rust-cache@v2
+      - name: Package (Apple silicon, ad-hoc signed, not notarized)
+        run: packaging/macos/package.sh --arch aarch64
+      - uses: actions/upload-artifact@v4
+        with: { name: macos, path: dist/release/* }
+
+  linux:
+    if: github.server_url == 'https://github.com'
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+        with: { ref: "${{ inputs.tag || github.ref }}" }
+      - uses: dtolnay/rust-toolchain@stable
+      - uses: Swatinem/rust-cache@v2
+      - name: Build dependencies
+        run: |
+          sudo apt-get update
+          sudo apt-get install -y pkg-config libssl-dev libxkbcommon-x11-dev libxcb-xkb-dev libx11-xcb-dev libwayland-dev libvulkan-dev libdbus-1-dev
+      - name: Build and tar
+        run: |
+          cargo build --release --locked --bins
+          v="${TAG#v}"
+          mkdir -p dist stage
+          cp target/release/papercraft target/release/papercraft-cli target/release/papercraft-mcp target/release/papercraft-relay stage/
+          tar -C stage -czf "dist/papercraft-$v-linux-x86_64.tar.gz" .
+          tar -C stage -czf "dist/papercraft-cli-$v-linux-x86_64.tar.gz" papercraft-cli papercraft-mcp
+      - uses: actions/upload-artifact@v4
+        with: { name: linux, path: dist/* }
+
+  publish:
+    if: github.server_url == 'https://github.com'
+    needs: [test, windows, macos, linux]
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/download-artifact@v4
+        with: { path: files, merge-multiple: true }
+      - name: Create the release
+        env:
+          GH_TOKEN: ${{ github.token }}
+        run: |
+          gh release create "$TAG" files/* --repo "$GITHUB_REPOSITORY" --title "PaperCraft ${TAG#v}" \
+            --generate-notes --verify-tag || gh release upload "$TAG" files/* --repo "$GITHUB_REPOSITORY" --clobber

.github/workflows/test.yml

@@ -0,0 +1,34 @@
+# The full test suite. Local runs cover only the targets a change touches (RULES.md, "The machine
+# you build on"); this is where everything runs, before a release can publish. Run it alone with
+# `gh workflow run test.yml -f ref=<branch or tag>`. Gitea reads .github/workflows too, so the job
+# is gated on the server URL.
+name: test
+
+on:
+  workflow_call:
+    inputs:
+      ref:
+        type: string
+        required: false
+  workflow_dispatch:
+    inputs:
+      ref:
+        description: Branch or tag to test (default the one you run from)
+        required: false
+
+env:
+  CARGO_TERM_COLOR: always
+
+jobs:
+  test:
+    if: github.server_url == 'https://github.com'
+    # Windows: the platform the app is developed on, and its runners render with a software GPU.
+    runs-on: windows-latest
+    steps:
+      - uses: actions/checkout@v4
+        with: { ref: "${{ inputs.ref || github.ref }}" }
+      - uses: dtolnay/rust-toolchain@stable
+        with: { targets: wasm32-unknown-unknown }
+      - uses: Swatinem/rust-cache@v2
+      - run: cargo test --locked --no-fail-fast
+      - run: cargo check --locked --lib --target wasm32-unknown-unknown

.playwright-mcp/console-2026-10-25T20-31-26-027Z.log

@@ -0,0 +1,2 @@
+[    3482ms] [INFO] %cDownload the React DevTools for a better development experience: https://react.dev/link/react-devtools font-weight:bold @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[    3531ms] [LOG] [HMR] connected @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719

.playwright-mcp/console-2026-10-25T20-31-41-217Z.log

@@ -0,0 +1,9 @@
+[     210ms] [LOG] [Fast Refresh] rebuilding @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[    1039ms] [LOG] [Fast Refresh] done in 930ms @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[    1076ms] [INFO] %cDownload the React DevTools for a better development experience: https://react.dev/link/react-devtools font-weight:bold @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[    1086ms] [LOG] [HMR] connected @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[   37298ms] [ERROR] Pattern attribute value [0-9() -]{10,16} is not a valid regular expression: Uncaught SyntaxError: Invalid regular expression: /[0-9() -]{10,16}/v: Invalid character in character class @ http://localhost:3000/motorista/entrar:0
+[   60872ms] [LOG] [Fast Refresh] rebuilding @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[   60976ms] [LOG] [Fast Refresh] done in 99ms @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[   61021ms] [LOG] [Fast Refresh] done in 99ms @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[   66490ms] [LOG] [Fast Refresh] done in 99ms @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719

.playwright-mcp/console-2026-10-25T20-32-58-325Z.log

@@ -0,0 +1,13 @@
+[      93ms] [LOG] [Fast Refresh] done in 99ms @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[     953ms] [INFO] %cDownload the React DevTools for a better development experience: https://react.dev/link/react-devtools font-weight:bold @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[     963ms] [LOG] [HMR] connected @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[    4345ms] [LOG] [Fast Refresh] rebuilding @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[    4433ms] [LOG] [Fast Refresh] done in 189ms @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[    4548ms] [VERBOSE] [DOM] Password forms should have (optionally hidden) username fields for accessibility: (More info: https://goo.gl/9p2vKq) %o @ http://localhost:3000/entrar/senha:0
+[    9731ms] [LOG] [Fast Refresh] done in 5486ms @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[    9777ms] [LOG] [Fast Refresh] done in 5486ms @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[   11070ms] [LOG] [Fast Refresh] done in 5486ms @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[   30758ms] [ERROR] WebSocket connection to 'ws://localhost:3000/_next/hmr?id=fBVPvwqt_6CU4TU3WWYmu' failed:  @ http://localhost:3000/_next/static/chunks/1bba_next_dist_client_0ru2jkh0js1s8._.js:16225
+[   31764ms] [ERROR] WebSocket connection to 'ws://localhost:3000/_next/hmr?id=fBVPvwqt_6CU4TU3WWYmu' failed: Error in connection establishment: net::ERR_CONNECTION_REFUSED @ http://localhost:3000/_next/static/chunks/1bba_next_dist_client_0ru2jkh0js1s8._.js:16225
+[   32766ms] [ERROR] WebSocket connection to 'ws://localhost:3000/_next/hmr?id=fBVPvwqt_6CU4TU3WWYmu' failed: Error in connection establishment: net::ERR_CONNECTION_REFUSED @ http://localhost:3000/_next/static/chunks/1bba_next_dist_client_0ru2jkh0js1s8._.js:16225
+[   33776ms] [LOG] [HMR] connected @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719

.playwright-mcp/console-2026-10-25T20-33-32-647Z.log

@@ -0,0 +1,79 @@
+[     805ms] [INFO] %cDownload the React DevTools for a better development experience: https://react.dev/link/react-devtools font-weight:bold @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[     813ms] [LOG] [HMR] connected @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[    1121ms] [VERBOSE] [DOM] Password forms should have (optionally hidden) username fields for accessibility: (More info: https://goo.gl/9p2vKq) %o @ http://localhost:3000/entrar/senha:0
+[    2267ms] [LOG] [Fast Refresh] rebuilding @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[    2310ms] [LOG] [Fast Refresh] done in 144ms @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[    9621ms] [LOG] [Fast Refresh] rebuilding @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[    9763ms] [LOG] [Fast Refresh] done in 243ms @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[   48693ms] [LOG] [Fast Refresh] done in 39171ms @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[   48749ms] [LOG] [Fast Refresh] done in 39171ms @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[   48826ms] [LOG] [Fast Refresh] done in 39171ms @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[   51025ms] [LOG] [Fast Refresh] done in 39171ms @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[   51539ms] [LOG] [Fast Refresh] done in 39171ms @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[   51907ms] [LOG] [Fast Refresh] done in 39171ms @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[  107213ms] [LOG] [Fast Refresh] done in 39171ms @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[  118297ms] [LOG] [Fast Refresh] done in 39171ms @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[  123464ms] [LOG] [Fast Refresh] done in 39171ms @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[  125669ms] [LOG] [Fast Refresh] done in 39171ms @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[  125771ms] [LOG] [Fast Refresh] done in 39171ms @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[  126799ms] [LOG] [Fast Refresh] done in 39171ms @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[  126941ms] [LOG] [Fast Refresh] done in 39171ms @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[  127929ms] [LOG] [Fast Refresh] done in 39171ms @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[  127981ms] [LOG] [Fast Refresh] done in 39171ms @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[  154930ms] [LOG] [Fast Refresh] done in 39171ms @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[  156620ms] [LOG] [Fast Refresh] done in 39171ms @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[  157845ms] [LOG] [Fast Refresh] done in 39171ms @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[  158106ms] [LOG] [Fast Refresh] done in 39171ms @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[  158454ms] [LOG] [Fast Refresh] done in 39171ms @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[  158504ms] [LOG] [Fast Refresh] done in 39171ms @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[  158748ms] [LOG] [Fast Refresh] done in 39171ms @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[  158848ms] [LOG] [Fast Refresh] done in 39171ms @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[  158955ms] [LOG] [Fast Refresh] done in 39171ms @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[  159307ms] [LOG] [Fast Refresh] done in 39171ms @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[  159399ms] [LOG] [Fast Refresh] done in 39171ms @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[  159488ms] [LOG] [Fast Refresh] done in 39171ms @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[  159901ms] [LOG] [Fast Refresh] done in 39171ms @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[  159993ms] [LOG] [Fast Refresh] done in 39171ms @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[  187894ms] [LOG] [Fast Refresh] done in 39171ms @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[  188000ms] [LOG] [Fast Refresh] done in 39171ms @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[  205603ms] [LOG] [Fast Refresh] done in 39171ms @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[  207208ms] [LOG] [Fast Refresh] done in 39171ms @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[  207296ms] [LOG] [Fast Refresh] done in 39171ms @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[  207951ms] [LOG] [Fast Refresh] done in 39171ms @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[  208126ms] [LOG] [Fast Refresh] done in 39171ms @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[  208244ms] [LOG] [Fast Refresh] done in 39171ms @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[  208353ms] [LOG] [Fast Refresh] done in 39171ms @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[  208415ms] [LOG] [Fast Refresh] done in 39171ms @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[  208590ms] [LOG] [Fast Refresh] done in 39171ms @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[  208695ms] [LOG] [Fast Refresh] done in 39171ms @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[  208794ms] [LOG] [Fast Refresh] done in 39171ms @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[  208878ms] [LOG] [Fast Refresh] done in 39171ms @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[  208986ms] [LOG] [Fast Refresh] done in 39171ms @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[  209132ms] [LOG] [Fast Refresh] done in 39171ms @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[  209234ms] [LOG] [Fast Refresh] done in 39171ms @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[  228278ms] [LOG] [Fast Refresh] rebuilding @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[  228308ms] [LOG] [Fast Refresh] done in 3ms @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[  238991ms] [LOG] [Fast Refresh] done in 10713ms @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[  239037ms] [LOG] [Fast Refresh] done in 10713ms @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[  239175ms] [LOG] [Fast Refresh] rebuilding @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[  239206ms] [LOG] [Fast Refresh] done in 3ms @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[  239602ms] [LOG] [Fast Refresh] done in 3ms @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[  239697ms] [LOG] [Fast Refresh] done in 3ms @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[  264111ms] [LOG] [Fast Refresh] done in 3ms @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[  265916ms] [LOG] [Fast Refresh] done in 3ms @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[  321743ms] [LOG] [Fast Refresh] done in 3ms @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[  333352ms] [LOG] [Fast Refresh] done in 3ms @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[  369410ms] [LOG] [Fast Refresh] done in 3ms @ http://localhost:3000/_next/static/chunks/1bba_next_dist_041c6vio7na_y._.js:719
+[  413886ms] [ERROR] WebSocket connection to 'ws://localhost:3000/_next/hmr?id=ruCdDO_vey1tElDs8WYR0' failed:  @ http://localhost:3000/_next/static/chunks/1bba_next_dist_client_0ru2jkh0js1s8._.js:16225
+[  414902ms] [ERROR] WebSocket connection to 'ws://localhost:3000/_next/hmr?id=ruCdDO_vey1tElDs8WYR0' failed: Error in connection establishment: net::ERR_CONNECTION_REFUSED @ http://localhost:3000/_next/static/chunks/1bba_next_dist_client_0ru2jkh0js1s8._.js:16225
+[  415904ms] [ERROR] WebSocket connection to 'ws://localhost:3000/_next/hmr?id=ruCdDO_vey1tElDs8WYR0' failed: Error in connection establishment: net::ERR_CONNECTION_REFUSED @ http://localhost:3000/_next/static/chunks/1bba_next_dist_client_0ru2jkh0js1s8._.js:16225
+[  416906ms] [ERROR] WebSocket connection to 'ws://localhost:3000/_next/hmr?id=ruCdDO_vey1tElDs8WYR0' failed: Error in connection establishment: net::ERR_CONNECTION_REFUSED @ http://localhost:3000/_next/static/chunks/1bba_next_dist_client_0ru2jkh0js1s8._.js:16225
+[  417908ms] [ERROR] WebSocket connection to 'ws://localhost:3000/_next/hmr?id=ruCdDO_vey1tElDs8WYR0' failed: Error in connection establishment: net::ERR_CONNECTION_REFUSED @ http://localhost:3000/_next/static/chunks/1bba_next_dist_client_0ru2jkh0js1s8._.js:16225
+[  418911ms] [ERROR] WebSocket connection to 'ws://localhost:3000/_next/hmr?id=ruCdDO_vey1tElDs8WYR0' failed: Error in connection establishment: net::ERR_CONNECTION_REFUSED @ http://localhost:3000/_next/static/chunks/1bba_next_dist_client_0ru2jkh0js1s8._.js:16225
+[  423918ms] [ERROR] WebSocket connection to 'ws://localhost:3000/_next/hmr?id=ruCdDO_vey1tElDs8WYR0' failed: Error in connection establishment: net::ERR_CONNECTION_REFUSED @ http://localhost:3000/_next/static/chunks/1bba_next_dist_client_0ru2jkh0js1s8._.js:16225
+[  428928ms] [ERROR] WebSocket connection to 'ws://localhost:3000/_next/hmr?id=ruCdDO_vey1tElDs8WYR0' failed: Error in connection establishment: net::ERR_CONNECTION_REFUSED @ http://localhost:3000/_next/static/chunks/1bba_next_dist_client_0ru2jkh0js1s8._.js:16225
+[  433950ms] [ERROR] WebSocket connection to 'ws://localhost:3000/_next/hmr?id=ruCdDO_vey1tElDs8WYR0' failed: Error in connection establishment: net::ERR_CONNECTION_REFUSED @ http://localhost:3000/_next/static/chunks/1bba_next_dist_client_0ru2jkh0js1s8._.js:16225
+[  438984ms] [ERROR] WebSocket connection to 'ws://localhost:3000/_next/hmr?id=ruCdDO_vey1tElDs8WYR0' failed: Error in connection establishment: net::ERR_CONNECTION_REFUSED @ http://localhost:3000/_next/static/chunks/1bba_next_dist_client_0ru2jkh0js1s8._.js:16225
+[  444022ms] [ERROR] WebSocket connection to 'ws://localhost:3000/_next/hmr?id=ruCdDO_vey1tElDs8WYR0' failed: Error in connection establishment: net::ERR_CONNECTION_REFUSED @ http://localhost:3000/_next/static/chunks/1bba_next_dist_client_0ru2jkh0js1s8._.js:16225
+[  449184ms] [ERROR] WebSocket connection to 'ws://localhost:3000/_next/hmr?id=ruCdDO_vey1tElDs8WYR0' failed: Error in connection establishment: net::ERR_CONNECTION_REFUSED @ http://localhost:3000/_next/static/chunks/1bba_next_dist_client_0ru2jkh0js1s8._.js:16225
+[  454479ms] [ERROR] WebSocket connection to 'ws://localhost:3000/_next/hmr?id=ruCdDO_vey1tElDs8WYR0' failed: Error in connection establishment: net::ERR_CONNECTION_REFUSED @ http://localhost:3000/_next/static/chunks/1bba_next_dist_client_0ru2jkh0js1s8._.js:16225

.playwright-mcp/page-2026-10-25T20-31-29-604Z.yml

@@ -0,0 +1,28 @@
+- generic [ref=e2]:
+  - complementary [ref=e3]:
+    - generic [ref=e8]:
+      - generic [ref=e9]: Rota Fresca
+      - generic [ref=e10]: Distribuição de alimentos
+    - generic [ref=e11]:
+      - heading "Do depósito à prateleira, na hora certa." [level=2] [ref=e12]
+      - paragraph [ref=e13]: Pedidos, entregas e notas da sua rede no mesmo lugar.
+  - main [ref=e14]:
+    - link "Precisa de ajuda?" [ref=e16] [cursor=pointer]:
+      - /url: mailto:suporte@rotafresca.com.br
+    - generic [ref=e17]:
+      - generic [ref=e18]:
+        - heading "Entrar" [level=1] [ref=e19]
+        - paragraph [ref=e20]: Use o e-mail da sua conta. Conforme o tipo de conta, pedimos a senha ou mandamos um link de acesso.
+      - generic [ref=e21]:
+        - generic [ref=e22]:
+          - generic [ref=e23]: E-mail
+          - textbox "E-mail" [ref=e24]:
+            - /placeholder: nome@empresa.com.br
+        - button "Continuar" [ref=e25]
+      - generic [ref=e26]: ou
+      - generic [ref=e33]:
+        - paragraph [ref=e34]: É motorista?
+        - paragraph [ref=e35]: Entre pelo app Rota Fresca no celular, com o seu número. Não precisa de e-mail.
+    - generic [ref=e36]:
+      - paragraph [ref=e37]: Recebeu um convite? Abra o link do e-mail para criar seu acesso.
+      - paragraph [ref=e38]: Termos de uso · Privacidade

.playwright-mcp/page-2026-10-25T20-31-42-327Z.yml

@@ -0,0 +1,20 @@
+- generic [active] [ref=f1e1]:
+  - generic [ref=f1e2]:
+    - generic [ref=f1e3]:
+      - generic [ref=f1e8]:
+        - generic [ref=f1e9]: Rota Fresca
+        - generic [ref=f1e10]: App do motorista
+      - banner [ref=f1e11]:
+        - heading "Entrar" [level=1] [ref=f1e12]
+        - paragraph [ref=f1e13]: Use o número de celular que a central cadastrou. Mandamos um código, sem senha.
+      - generic [ref=f1e14]:
+        - generic [ref=f1e15]: Celular
+        - generic [ref=f1e16]:
+          - generic [ref=f1e17]: "+55"
+          - textbox "(21) 98877-4410" [ref=f1e18]
+    - generic [ref=f1e19]:
+      - button "Receber código no WhatsApp" [ref=f1e20]
+      - button "Receber por SMS" [ref=f1e21]
+      - paragraph [ref=f1e22]: Trocou de número? Fale com a central.
+  - button "Open Next.js Dev Tools" [ref=f1e28] [cursor=pointer]
+  - alert [ref=f1e32]

.playwright-mcp/page-2026-10-25T20-32-59-335Z.yml

@@ -0,0 +1,32 @@
+- generic [active] [ref=f2e1]:
+  - generic [ref=f2e2]:
+    - complementary [ref=f2e3]:
+      - generic [ref=f2e9]:
+        - generic [ref=f2e10]: Rota Fresca
+        - generic [ref=f2e11]: Distribuição de alimentos
+      - generic [ref=f2e12]:
+        - heading "Do depósito à prateleira, na hora certa." [level=2] [ref=f2e13]
+        - paragraph [ref=f2e14]: Pedidos, entregas e notas da sua rede no mesmo lugar.
+    - main [ref=f2e15]:
+      - link "Precisa de ajuda?" [ref=f2e17] [cursor=pointer]:
+        - /url: mailto:suporte@rotafresca.com.br
+      - generic [ref=f2e18]:
+        - generic [ref=f2e19]:
+          - heading "Entrar" [level=1] [ref=f2e20]
+          - paragraph [ref=f2e21]: Use o e-mail da sua conta. Conforme o tipo de conta, pedimos a senha ou mandamos um link de acesso.
+        - generic [ref=f2e22]:
+          - generic [ref=f2e23]:
+            - generic [ref=f2e24]: E-mail
+            - textbox "E-mail" [ref=f2e25]:
+              - /placeholder: nome@empresa.com.br
+          - button "Continuar" [ref=f2e26]
+        - generic [ref=f2e27]: ou
+        - button "Entrar com chave de acesso (passkey)" [ref=f2e31]
+        - generic [ref=f2e35]:
+          - paragraph [ref=f2e36]: É motorista?
+          - paragraph [ref=f2e37]: Entre pelo app Rota Fresca no celular, com o seu número. Não precisa de e-mail.
+      - generic [ref=f2e38]:
+        - paragraph [ref=f2e39]: Recebeu um convite? Abra o link do e-mail para criar seu acesso.
+        - paragraph [ref=f2e40]: Termos de uso · Privacidade
+  - button "Open Next.js Dev Tools" [ref=f2e46] [cursor=pointer]
+  - alert [ref=f2e50]

.playwright-mcp/page-2026-10-25T20-33-03-457Z.yml

@@ -0,0 +1,38 @@
+- generic [active] [ref=f2e1]:
+  - button "Open Next.js Dev Tools" [ref=f2e46] [cursor=pointer]
+  - alert [ref=f2e50]: Digite sua senha
+  - generic [ref=f2e51]:
+    - complementary [ref=f2e52]:
+      - generic [ref=f2e58]:
+        - generic [ref=f2e59]: Rota Fresca
+        - generic [ref=f2e60]: Distribuição de alimentos
+      - generic [ref=f2e61]:
+        - heading "Do depósito à prateleira, na hora certa." [level=2] [ref=f2e62]
+        - paragraph [ref=f2e63]: Pedidos, entregas e notas da sua rede no mesmo lugar.
+    - main [ref=f2e64]:
+      - link "Precisa de ajuda?" [ref=f2e66] [cursor=pointer]:
+        - /url: mailto:suporte@rotafresca.com.br
+      - generic [ref=f2e67]:
+        - generic [ref=f2e68]:
+          - generic [ref=f2e69]: ana.souza@rotafresca.com.br
+          - button "Trocar" [ref=f2e74]
+        - generic [ref=f2e75]:
+          - heading "Digite sua senha" [level=1] [ref=f2e76]
+          - paragraph [ref=f2e77]: Conta de consultor. Depois da senha pedimos o código do autenticador.
+        - generic [ref=f2e78]:
+          - generic [ref=f2e79]:
+            - generic [ref=f2e80]:
+              - generic [ref=f2e81]: Senha
+              - textbox "Senha" [ref=f2e82]
+            - generic [ref=f2e83]:
+              - generic [ref=f2e84]:
+                - checkbox "Mostrar senha" [ref=f2e85]
+                - checkbox [aria-hidden]
+                - text: Mostrar senha
+              - link "Esqueci minha senha" [ref=f2e86] [cursor=pointer]:
+                - /url: /entrar/redefinir
+          - button "Entrar" [ref=f2e87]
+        - paragraph [ref=f2e88]: Pode colar a senha ou usar o gerenciador de senhas do navegador.
+      - generic [ref=f2e89]:
+        - paragraph [ref=f2e90]: Recebeu um convite? Abra o link do e-mail para criar seu acesso.
+        - paragraph [ref=f2e91]: Termos de uso · Privacidade

.playwright-mcp/page-2026-10-25T20-33-15-378Z.yml

@@ -0,0 +1,40 @@
+- generic [ref=f2e1]:
+  - button "Open Next.js Dev Tools" [ref=f2e46] [cursor=pointer]
+  - alert [ref=f2e50]: Rota Fresca
+  - generic [ref=f2e51]:
+    - complementary [ref=f2e52]:
+      - generic [ref=f2e58]:
+        - generic [ref=f2e59]: Rota Fresca
+        - generic [ref=f2e60]: Distribuição de alimentos
+      - generic [ref=f2e61]:
+        - heading "Do depósito à prateleira, na hora certa." [level=2] [ref=f2e62]
+        - paragraph [ref=f2e63]: Pedidos, entregas e notas da sua rede no mesmo lugar.
+    - main [ref=f2e64]:
+      - link "Precisa de ajuda?" [ref=f2e66] [cursor=pointer]:
+        - /url: mailto:suporte@rotafresca.com.br
+      - generic [ref=f2e67]:
+        - generic [ref=f2e68]:
+          - generic [ref=f2e69]: ana.souza@rotafresca.com.br
+          - button "Trocar" [ref=f2e74]
+        - generic [ref=f2e75]:
+          - heading "Digite sua senha" [level=1] [ref=f2e76]
+          - paragraph [ref=f2e77]: Conta de consultor. Depois da senha pedimos o código do autenticador.
+        - generic [ref=f2e78]:
+          - generic [ref=f2e79]:
+            - generic [ref=f2e80]:
+              - generic [ref=f2e81]: Senha
+              - textbox "Senha" [active] [invalid] [ref=f2e82]
+            - generic [ref=f2e83]:
+              - generic [ref=f2e84]:
+                - checkbox "Mostrar senha" [ref=f2e85]
+                - checkbox [aria-hidden]
+                - text: Mostrar senha
+              - link "Esqueci minha senha" [ref=f2e86] [cursor=pointer]:
+                - /url: /entrar/redefinir
+          - alert [ref=f2e92]:
+            - generic [ref=f2e93]: Senha incorreta. Confira e tente de novo.
+          - button "Entrar" [ref=f2e87]
+        - paragraph [ref=f2e88]: Pode colar a senha ou usar o gerenciador de senhas do navegador.
+      - generic [ref=f2e89]:
+        - paragraph [ref=f2e90]: Recebeu um convite? Abra o link do e-mail para criar seu acesso.
+        - paragraph [ref=f2e91]: Termos de uso · Privacidade

.playwright-mcp/page-2026-10-25T20-33-33-487Z.yml

@@ -0,0 +1,32 @@
+- generic [active] [ref=f3e1]:
+  - generic [ref=f3e2]:
+    - complementary [ref=f3e3]:
+      - generic [ref=f3e9]:
+        - generic [ref=f3e10]: Rota Fresca
+        - generic [ref=f3e11]: Distribuição de alimentos
+      - generic [ref=f3e12]:
+        - heading "Do depósito à prateleira, na hora certa." [level=2] [ref=f3e13]
+        - paragraph [ref=f3e14]: Pedidos, entregas e notas da sua rede no mesmo lugar.
+    - main [ref=f3e15]:
+      - link "Precisa de ajuda?" [ref=f3e17] [cursor=pointer]:
+        - /url: mailto:suporte@rotafresca.com.br
+      - generic [ref=f3e18]:
+        - generic [ref=f3e19]:
+          - heading "Entrar" [level=1] [ref=f3e20]
+          - paragraph [ref=f3e21]: Use o e-mail da sua conta. Conforme o tipo de conta, pedimos a senha ou mandamos um link de acesso.
+        - generic [ref=f3e22]:
+          - generic [ref=f3e23]:
+            - generic [ref=f3e24]: E-mail
+            - textbox "E-mail" [ref=f3e25]:
+              - /placeholder: nome@empresa.com.br
+          - button "Continuar" [ref=f3e26]
+        - generic [ref=f3e27]: ou
+        - button "Entrar com chave de acesso (passkey)" [ref=f3e31]
+        - generic [ref=f3e35]:
+          - paragraph [ref=f3e36]: É motorista?
+          - paragraph [ref=f3e37]: Entre pelo app Rota Fresca no celular, com o seu número. Não precisa de e-mail.
+      - generic [ref=f3e38]:
+        - paragraph [ref=f3e39]: Recebeu um convite? Abra o link do e-mail para criar seu acesso.
+        - paragraph [ref=f3e40]: Termos de uso · Privacidade
+  - button "Open Next.js Dev Tools" [ref=f3e46] [cursor=pointer]
+  - alert [ref=f3e50]

.playwright-mcp/page-2026-10-25T20-33-34-597Z.yml

@@ -0,0 +1,38 @@
+- generic [active] [ref=f3e1]:
+  - button "Open Next.js Dev Tools" [ref=f3e46] [cursor=pointer]
+  - alert [ref=f3e50]
+  - generic [ref=f3e51]:
+    - complementary [ref=f3e52]:
+      - generic [ref=f3e58]:
+        - generic [ref=f3e59]: Rota Fresca
+        - generic [ref=f3e60]: Distribuição de alimentos
+      - generic [ref=f3e61]:
+        - heading "Do depósito à prateleira, na hora certa." [level=2] [ref=f3e62]
+        - paragraph [ref=f3e63]: Pedidos, entregas e notas da sua rede no mesmo lugar.
+    - main [ref=f3e64]:
+      - link "Precisa de ajuda?" [ref=f3e66] [cursor=pointer]:
+        - /url: mailto:suporte@rotafresca.com.br
+      - generic [ref=f3e67]:
+        - generic [ref=f3e68]:
+          - generic [ref=f3e69]: ana.souza@rotafresca.com.br
+          - button "Trocar" [ref=f3e74]
+        - generic [ref=f3e75]:
+          - heading "Digite sua senha" [level=1] [ref=f3e76]
+          - paragraph [ref=f3e77]: Conta de consultor. Depois da senha pedimos o código do autenticador.
+        - generic [ref=f3e78]:
+          - generic [ref=f3e79]:
+            - generic [ref=f3e80]:
+              - generic [ref=f3e81]: Senha
+              - textbox "Senha" [ref=f3e82]
+            - generic [ref=f3e83]:
+              - generic [ref=f3e84]:
+                - checkbox "Mostrar senha" [ref=f3e85]
+                - checkbox [aria-hidden]
+                - text: Mostrar senha
+              - link "Esqueci minha senha" [ref=f3e86] [cursor=pointer]:
+                - /url: /entrar/redefinir
+          - button "Entrar" [ref=f3e87]
+        - paragraph [ref=f3e88]: Pode colar a senha ou usar o gerenciador de senhas do navegador.
+      - generic [ref=f3e89]:
+        - paragraph [ref=f3e90]: Recebeu um convite? Abra o link do e-mail para criar seu acesso.
+        - paragraph [ref=f3e91]: Termos de uso · Privacidade

.playwright-mcp/page-2026-10-25T20-33-35-637Z.yml

@@ -0,0 +1,33 @@
+- generic [active] [ref=f3e1]:
+  - button "Open Next.js Dev Tools" [ref=f3e46] [cursor=pointer]
+  - alert [ref=f3e50]
+  - generic [ref=f3e92]:
+    - complementary [ref=f3e93]:
+      - generic [ref=f3e99]:
+        - generic [ref=f3e100]: Rota Fresca
+        - generic [ref=f3e101]: Distribuição de alimentos
+      - generic [ref=f3e102]:
+        - heading "Do depósito à prateleira, na hora certa." [level=2] [ref=f3e103]
+        - paragraph [ref=f3e104]: Pedidos, entregas e notas da sua rede no mesmo lugar.
+    - main [ref=f3e105]:
+      - link "Precisa de ajuda?" [ref=f3e107] [cursor=pointer]:
+        - /url: mailto:suporte@rotafresca.com.br
+      - generic [ref=f3e108]:
+        - heading "Confirme que é você" [level=1] [ref=f3e113]
+        - generic [ref=f3e114]:
+          - generic [ref=f3e115]:
+            - generic [ref=f3e116]:
+              - generic [ref=f3e117]: Código
+              - textbox "Código" [ref=f3e118]
+            - generic [ref=f3e119]:
+              - checkbox "Não pedir de novo neste computador por 30 dias" [checked] [ref=f3e120]
+              - checkbox [checked] [aria-hidden]
+              - text: Não pedir de novo neste computador por 30 dias
+          - button "Confirmar" [ref=f3e121]
+        - generic [ref=f3e122]:
+          - link "Usar um código de recuperação" [ref=f3e123] [cursor=pointer]:
+            - /url: /entrar/codigo?recuperacao=1
+          - paragraph [ref=f3e124]: Perdeu o celular? Peça ao administrador da conta para refazer o autenticador.
+      - generic [ref=f3e125]:
+        - paragraph [ref=f3e126]: Recebeu um convite? Abra o link do e-mail para criar seu acesso.
+        - paragraph [ref=f3e127]: Termos de uso · Privacidade

.playwright-mcp/page-2026-10-25T20-33-42-991Z.yml

@@ -0,0 +1,47 @@
+- generic [active] [ref=f3e1]:
+  - button "Open Next.js Dev Tools" [ref=f3e46] [cursor=pointer]
+  - alert [ref=f3e50]: Bom dia, Ana
+  - generic [ref=f3e128]:
+    - complementary [ref=f3e129]:
+      - generic [ref=f3e130]:
+        - generic [ref=f3e136]:
+          - generic [ref=f3e137]: Rota Fresca
+          - generic [ref=f3e138]: Distribuição de alimentos
+        - navigation [ref=f3e139]:
+          - link "Painel" [ref=f3e140] [cursor=pointer]:
+            - /url: /painel
+          - link "Roteiro do dia" [ref=f3e143] [cursor=pointer]:
+            - /url: /roteiro
+          - link "Lojas (PDVs)" [ref=f3e146] [cursor=pointer]:
+            - /url: /lojas
+          - link "Pedidos" [ref=f3e149] [cursor=pointer]:
+            - /url: /pedidos
+          - link "Entregas" [ref=f3e152] [cursor=pointer]:
+            - /url: /entregas
+          - link "Validade e lotes" [ref=f3e155] [cursor=pointer]:
+            - /url: /validade
+          - link "Relatórios" [ref=f3e158] [cursor=pointer]:
+            - /url: /relatorios
+          - link "Integrações e notas" [ref=f3e161] [cursor=pointer]:
+            - /url: /integracoes
+          - link "Leitura de documentos" [ref=f3e164] [cursor=pointer]:
+            - /url: /documentos
+          - link "Contatos e mensagens" [ref=f3e167] [cursor=pointer]:
+            - /url: /contatos
+          - link "Configurações" [ref=f3e170] [cursor=pointer]:
+            - /url: /configuracoes
+      - generic [ref=f3e173]:
+        - generic [aria-hidden] [ref=f3e174]: A
+        - generic [ref=f3e175]:
+          - generic [ref=f3e176]: Ana Souza
+          - generic [ref=f3e177]: Consultora · Zona Oeste
+    - main [ref=f3e178]:
+      - generic [ref=f3e179]:
+        - generic [ref=f3e180]:
+          - heading "Bom dia, Ana" [level=1] [ref=f3e181]
+          - paragraph [ref=f3e182]: domingo, 25 de outubro
+        - generic [ref=f3e183]:
+          - textbox "Buscar loja, pedido ou produto" [ref=f3e187]
+          - button "Notificações" [ref=f3e188]
+          - button "Importar / Exportar" [ref=f3e189]
+          - button "Novo pedido" [ref=f3e190]

AGENTS.md

@@ -0,0 +1,77 @@
+# Guidance for coding agents
+
+PaperCraft is a native Rust design and whiteboard canvas (egui, wgpu, winit) that AI agents drive
+over MCP and a CLI. Read [CONTRIBUTING.md](CONTRIBUTING.md) and [RULES.md](RULES.md) first; this
+file is the short version for agents, and [AI_POLICY.md](AI_POLICY.md) says what the person using
+you is accountable for.
+
+## Commands
+
+```sh
+cargo build --release
+cargo fmt --all
+cargo clippy --all-targets
+cargo test --test incremental                   # only the targets your change touches
+cargo test --lib editor::changes                # unit tests of one module
+cargo check --lib --target wasm32-unknown-unknown
+```
+
+Do not run the full suite locally: it builds dozens of test binaries. It runs on GitHub before
+each release (`.github/workflows/test.yml`). `tests/update.rs` cannot run on Windows outside CI
+(it needs elevation); that failure is known.
+
+Builds run on the person's own machine, so mind its resources (RULES.md, "The machine you build
+on"): check free memory and running builds first, cap jobs at no more than half the cores
+(`cargo test -j 8 -- --test-threads=8` on 16 cores), run at low priority, run one heavy job at a
+time, and stop at once if they say it is slow.
+
+## Running the app safely
+
+Never run a test copy against the person's real projects or MCP port, and never close or restart
+their running PaperCraft. Give yours its own folder and port, and keep its PID so you can stop only
+your own process:
+
+```sh
+PAPERCRAFT_HOME=/tmp/pc PAPERCRAFT_MCP_PORT=29998 ./target/release/papercraft
+```
+
+Do not stop processes by name.
+
+## Layout
+
+`src/model` (document), `src/editor` (tools and edits), `src/render` (wgpu), `src/mcp` (tools,
+HTML/CSS mapping, lint), `src/ui` (egui panels), `src/io` (import and export), `src/project`
+(store and formats), `tests/` (scenario tests), `specs/` (feature specs), `skills/` (agent
+skills). The README's project layout lists the rest.
+
+## Conventions
+
+* Tests first; match the style of the tests next to yours, and check the behaviour is not already
+  covered.
+* Changes to the document go through `Editor::edit`: one transaction, one undo step.
+* Handle errors; do not `unwrap` user data and do not discard errors with `let _ =`.
+* Comments explain *why*, never summarise the code. No dead code, debug prints or
+  commented-out blocks.
+* Files stay under about 800 lines; split by feature.
+* Reuse the shared UI kit and theme instead of one-off values. Nothing may overflow its container.
+* Writes to projects are atomic and format changes ship a migration (see RULES.md, "Data safety").
+* Adding or removing an MCP tool means a test in `tests/mcp.rs`, a precise description, and the
+  tool count updated in the README and ROADMAP.
+* Commits are conventional (`feat(scope): summary`) and focused. Do not commit, push or tag unless
+  the person asked you to.
+
+## Designing with PaperCraft (skills, examples, screenshots)
+
+* Themes are modes, never copies: one artboard per screen, a value per mode on each variable, and
+  `set_variable_mode` to switch. Never duplicate artboards for light and dark.
+* Every colour on a themed screen is a variable.
+* Check each artboard for overflow, programmatically and by screenshot in each mode, and run
+  `lint_design`.
+* Release design locks when you finish.
+
+## Avoid
+
+* Creative additions nobody asked for; stay inside the task.
+* Trivial tests, wide or optional types added to appease the compiler, and swallowed errors.
+* Editing generated files, lockfiles or release artifacts by hand, or touching files unrelated to
+  the task. Leave other people's uncommitted work alone.

AI_POLICY.md

@@ -0,0 +1,40 @@
+# AI usage policy
+
+PaperCraft is built to be driven by AI agents, and many of its contributors use them too. AI tools
+are welcome here. What we ask is that a person stays accountable for everything submitted.
+
+## For contributors
+
+* **You own what you submit.** Read every line of your pull request before asking for review. If
+  you cannot explain what a change does and how it fits the rest of the system without asking an
+  AI, do not submit it yet.
+* **Disclose meaningful AI help.** Say which tool you used and roughly how much it wrote in the
+  pull request description (for example "drafted with Claude Code, reviewed and tested by me").
+  Autocomplete and spell-checking do not need a note.
+* **Write issues yourself.** An agent can help you research, but the report should be in your own
+  words, trimmed to what matters, with reproduction steps you ran. Long generated text that nobody
+  checked puts the burden on maintainers.
+* **Think before you generate.** Agents jump to code and make their own job easy: trivial tests,
+  wide or optional types, swallowed errors, redundant comments, copied local patterns that do not
+  fit. Push back on all of it. [RULES.md](RULES.md) lists the standards to hold the output to.
+* **Verify.** Run the checks in [CONTRIBUTING.md](CONTRIBUTING.md), use the app, and attach
+  screenshots for UI changes. "The agent said it works" is not a test result.
+* **Answer automated review.** If a bot reviews your pull request, fix its findings or reply with
+  a one-line reason a finding does not apply.
+* **No bulk or drive-by pull requests.** Many small generated changes across the tree, or changes
+  to something nobody asked for, will be closed. Open an issue first for anything beyond a small
+  fix.
+
+Pull requests that clearly skip these steps may be closed without a detailed review. Repeated
+low-effort submissions can lead to a block, under the [Code of Conduct](CODE_OF_CONDUCT.md).
+
+## For coding agents
+
+Read [AGENTS.md](AGENTS.md). It holds the commands, conventions and guardrails an agent working in
+this repository should follow.
+
+## Why
+
+Every issue and pull request is read by a person. Review time is the scarce resource, and a change
+nobody understood costs more than it saves. AI that is reviewed, tested and understood by the
+person submitting it is a good way to build PaperCraft; AI used to skip that work is not.

CLAUDE.md

@@ -0,0 +1 @@
+@AGENTS.md

CODE_OF_CONDUCT.md

@@ -0,0 +1,31 @@
+# Code of Conduct
+
+PaperCraft is built by people with different backgrounds and experience. We want everyone to be
+able to contribute without harassment.
+
+## Our standard
+
+Be respectful and constructive. Assume good intent, give specific and kind feedback, and accept
+it the same way. Disagree about the work, not the person.
+
+Not acceptable:
+
+* harassment, insults, slurs, or personal or political attacks;
+* sexualised language or imagery, or unwelcome attention;
+* threats, doxxing, or publishing someone's private information;
+* sustained disruption of discussions, or pressure to merge or answer;
+* anything else a reasonable person would consider inappropriate in a professional setting.
+
+## Scope
+
+This applies in issues, pull requests, discussions, commit messages and any space where someone
+represents the project.
+
+## Enforcement
+
+Maintainers may edit or remove comments, close or lock threads, and block people who break these
+rules. To report a problem, use GitHub's "Report content" on the comment, or contact a maintainer
+through a private channel on their GitHub profile. Reports are handled privately and in good
+faith, and retaliation against a reporter is itself a violation.
+
+The spirit of this text follows the [Contributor Covenant](https://www.contributor-covenant.org).

CONTRIBUTING.md

@@ -0,0 +1,129 @@
+# Contributing to PaperCraft
+
+Thanks for wanting to help. PaperCraft is an alpha, so there is plenty to do and the bar for a
+first contribution is low: a typo fix, a clearer error message, a missing test or a one-line bug
+fix are all welcome.
+
+Please read [RULES.md](RULES.md) before writing code: it holds the standards a change is judged by.
+By taking part you agree to the [Code of Conduct](CODE_OF_CONDUCT.md). Using an AI tool is fine;
+the [AI usage policy](AI_POLICY.md) says what you stay responsible for, and coding agents should read
+[AGENTS.md](AGENTS.md).
+
+## Ways to help
+
+* **Report a bug** or **suggest a feature** with an [issue](https://github.com/nxtime/papercraft/issues/new/choose).
+  A screenshot or a short recording helps; so does the project folder (or a page of it) that
+  triggers the bug.
+* **Pick something from [ROADMAP.md](ROADMAP.md).** Rows marked `todo` or `partial` are open. Say
+  which one you are taking in an issue first, so two people do not build the same thing.
+* **Improve the docs, skills or screenshots.** [docs/](docs), [skills/](skills) and the README are
+  as important as code.
+* **Review a pull request.** A second pair of eyes is always useful.
+
+Security problems do not go in public issues: see [SECURITY.md](SECURITY.md).
+
+## Before you start
+
+For anything bigger than a small fix, open an issue (or comment on one) describing the problem and
+how you plan to solve it. Large features start as a short spec in [specs/](specs): a `spec.md`
+(why, what, what is out of scope) and a `plan.md`. [specs/component-props](specs/component-props)
+shows the shape. A spec agreed up front saves a rewrite later.
+
+## Set up
+
+You need Rust 1.95 or newer (`rust-version` in `Cargo.toml`) and the platform libraries listed in
+the README's [Build from source](README.md#build-from-source).
+
+```sh
+git clone https://github.com/nxtime/papercraft
+cd papercraft
+cargo build --release
+```
+
+Run a test copy next to your own PaperCraft so it cannot touch your real projects or collide with
+the running app's MCP port:
+
+```sh
+PAPERCRAFT_HOME=/tmp/pc PAPERCRAFT_MCP_PORT=29998 ./target/release/papercraft
+```
+
+`PAPERCRAFT_HOME` moves the project root and the config folder; `PAPERCRAFT_MCP_PORT` moves the
+MCP server. Always set both when developing.
+
+The code depends on [`craft-ui`](https://git.marcospaulo.dev.br/masi/craft-libs), which Cargo
+fetches from a public git repository at the revision pinned in `Cargo.toml`.
+
+## Make the change
+
+1. Fork the repository and branch from `main` (`fix/short-name`, `feat/short-name`).
+2. **Write the test first.** Fix a bug by adding a test that fails, then make it pass. See
+   [Tests](#tests).
+3. Keep the change focused. One concern per pull request; unrelated cleanups go in their own.
+4. Run the checks below and fix what they report.
+5. Update the docs the change touches: the README, `docs/`, the tool description for an MCP tool,
+   the skills if agents should now behave differently.
+6. Add a short entry to [PROGRESS.md](PROGRESS.md) for user-visible changes.
+
+### Checks
+
+```sh
+cargo fmt --all
+cargo clippy --all-targets
+cargo test --test <target>                            # the targets your change touches
+cargo check --lib --target wasm32-unknown-unknown     # the web build
+```
+
+Each file in `tests/` is its own binary linking the whole app, so the full suite is slow and heavy
+on a desktop. It runs on GitHub instead: before every release (`.github/workflows/test.yml`), or
+on demand with `gh workflow run test.yml -f ref=<branch>`.
+
+Keep the tree free of the third-party branding patterns listed in `.debrand`.
+
+### Tests
+
+* Unit tests sit next to the code in `#[cfg(test)]` modules.
+* Scenario tests live in [tests/](tests). They drive the editor with synthetic pointer and
+  keyboard events; `tests/mcp.rs` covers every MCP tool on a headless session.
+* Aim for **80% coverage** on code you add or change, including the error paths.
+* GPU-dependent tests skip when no adapter exists. Set `PAPERCRAFT_REQUIRE_GPU=1` to make them
+  fail instead.
+* `tests/update.rs` cannot run on Windows (it needs elevation); that failure is known and not
+  yours.
+* For UI work, run the app, look at it, and attach a screenshot. Headless rendering needs no
+  display: `papercraft --screenshot ui.png --demo --size 1440x900 --scale 2`.
+
+## Commits
+
+[Conventional commits](https://www.conventionalcommits.org): `type(scope): summary`, with the
+types `feat`, `fix`, `refactor`, `docs`, `test`, `chore`, `perf` and `ci`.
+
+```
+fix(ui): keep the review row's revert button off the hover edge
+feat(mcp): add set_screens
+docs(readme): add the demo video
+```
+
+Write the summary in the imperative, under about 72 characters, and use the body to say *why*.
+Reference the issue (`Fixes #123`).
+
+## Pull requests
+
+* Fill in the template: what changed, why, how you tested it, screenshots for UI changes.
+* Keep it reviewable. If it grows past a few hundred lines of non-generated code, split it.
+* The branch must be up to date with `main`; rebase rather than merge.
+* Expect review comments; they are about the code, not you. Push fixes as new commits and we
+  squash on merge.
+* A maintainer merges once a review is approved.
+
+## Releases
+
+Maintainers cut releases. A `v*` tag pushed to GitHub builds Windows, macOS and Linux and
+publishes them (`.github/workflows/release.yml`). Contributors do not need to bump versions.
+
+## Licensing
+
+PaperCraft is dual-licensed under [MIT](LICENSE-MIT) or [Apache-2.0](LICENSE-APACHE). Unless you
+state otherwise, anything you submit is licensed under the same terms, with no extra conditions.
+Only submit work you wrote or have the right to submit. Code ported from another project needs a
+compatible license and an entry in [THIRD_PARTY.md](THIRD_PARTY.md); bundled assets go in
+[ATTRIBUTION.md](ATTRIBUTION.md).

Cargo.lock

@@ -784,7 +784,7 @@ dependencies = [
 [[package]]
 name = "craft-ui"
 version = "0.1.0"
-source = "git+https://git.marcospaulo.dev.br/masi/craft-libs?rev=22544b6d619d4f16779b8bdfa3f0b642a86fc065#22544b6d619d4f16779b8bdfa3f0b642a86fc065"
+source = "git+https://git.marcospaulo.dev.br/masi/craft-libs?rev=9c470aa935c4ce48f2ba4f0a17f9410c0c8660fb#9c470aa935c4ce48f2ba4f0a17f9410c0c8660fb"
 dependencies = [
  "egui",
 ]
@@ -3128,7 +3128,7 @@ dependencies = [
 
 [[package]]
 name = "papercraft"
-version = "0.7.2"
+version = "0.9.0"
 dependencies = [
  "arboard",
  "axum",
@@ -3161,6 +3161,7 @@ dependencies = [
  "resvg",
  "rfd",
  "rmcp",
+ "ruzstd",
  "semver",
  "serde",
  "serde_json",
@@ -3174,8 +3175,10 @@ dependencies = [
  "web-sys",
  "web-time",
  "wgpu",
+ "windows-sys 0.61.2",
  "winit",
  "winresource",
+ "zstd",
 ]
 
 [[package]]
@@ -3853,6 +3856,15 @@ version = "1.0.23"
 source = "registry+https://github.com/rust-lang/crates.io-index"
 checksum = "cf54715a573b99ac80df0bc206da022bcd442c974952c7b9720069370852e21f"
 
+[[package]]
+name = "ruzstd"
+version = "0.8.3"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "a7c1c839d570d835527c9a5e4db7cb2198683a988cb9d7293fc8674e6bd58fc8"
+dependencies = [
+ "twox-hash",
+]
+
 [[package]]
 name = "ryu"
 version = "1.0.23"
@@ -4754,6 +4766,12 @@ dependencies = [
  "thiserror 2.0.21",
 ]
 
+[[package]]
+name = "twox-hash"
+version = "2.1.5"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "86a801b3cea342a06d468c8710662aa29e5e05e4f5c0d62f00bbb7f2ad7941c2"
+
 [[package]]
 name = "type-map"
 version = "0.5.1"
@@ -4777,7 +4795,7 @@ checksum = "f2f6fb2847f6742cd76af783a2a2c49e9375d0a111c7bef6f71cd9e738c72d6e"
 dependencies = [
  "memoffset",
  "tempfile",
- "windows-sys 0.60.2",
+ "windows-sys 0.61.2",
 ]
 
 [[package]]
@@ -6018,6 +6036,34 @@ version = "1.0.23"
 source = "registry+https://github.com/rust-lang/crates.io-index"
 checksum = "29666d0abbfad1e3dc4dcf6144730dd3a3ab225bbbdac83319345b1b44ccfc1b"
 
+[[package]]
+name = "zstd"
+version = "0.13.3"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "e91ee311a569c327171651566e07972200e76fcfe2242a4fa446149a3881c08a"
+dependencies = [
+ "zstd-safe",
+]
+
+[[package]]
+name = "zstd-safe"
+version = "7.3.0"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "64d80649ab6db9d9f6f9c80a40becd948eda4714a0a5ac8c4d157a32231c7882"
+dependencies = [
+ "zstd-sys",
+]
+
+[[package]]
+name = "zstd-sys"
+version = "2.1.2+zstd.1.5.7"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "481ada9c543b2323cbb7bbdbb5249177fbf0188ed959ed2c15e4b22421c84ed3"
+dependencies = [
+ "cc",
+ "pkg-config",
+]
+
 [[package]]
 name = "zune-core"
 version = "0.5.3"

Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "papercraft"
-version = "0.7.2"
+version = "0.9.0"
 edition = "2024"
 rust-version = "1.95"
 description = "A native infinite-canvas app for planning, working and sketching"
@@ -44,7 +44,7 @@ env_logger = "0.11"
 rfd = "0.17"
 fastrand = "2"
 dirs = "6"
-craft-ui = { version = "0.1.0", git = "https://git.marcospaulo.dev.br/masi/craft-libs", rev = "22544b6d619d4f16779b8bdfa3f0b642a86fc065" }
+craft-ui = { version = "0.1.0", git = "https://git.marcospaulo.dev.br/masi/craft-libs", rev = "9c470aa935c4ce48f2ba4f0a17f9410c0c8660fb" }
 i_overlay = "9.0.1"
 miniz_oxide = "0.9.1"
 usvg = "0.48"
@@ -97,8 +97,14 @@ reqwest = { version = "0.13", default-features = false, features = ["native-tls"
 # libc: SIGINT to the spawned chat CLIs.
 keyring = { version = "3", default-features = false, features = ["apple-native", "windows-native", "sync-secret-service", "crypto-rust"] }
 libc = "0.2"
+# Pages and versions on disk are zstd-compressed JSON (`project::packed`).
+zstd = "0.13"
 
 # Browser build (`src/web.rs`): canvas + WebGPU/WebGL surface, DOM events instead of winit.
+# Process RAM and CPU readings for the performance overlay (`ui::perf`).
+[target.'cfg(windows)'.dependencies]
+windows-sys = { version = "0.61", features = ["Win32_Foundation", "Win32_System_ProcessStatus", "Win32_System_Threading"] }
+
 [target.'cfg(target_arch = "wasm32")'.dependencies]
 wgpu = { version = "30", features = ["webgl"] }
 wasm-bindgen = "0.2"
@@ -106,4 +112,6 @@ wasm-bindgen-futures = "0.4"
 js-sys = "0.3"
 console_error_panic_hook = "0.1"
 console_log = "1"
+# zstd without C, for the browser: reads the packed files native builds write.
+ruzstd = "0.8"
 web-sys = { version = "0.3", features = ["Window", "Document", "Element", "HtmlElement", "HtmlCanvasElement", "KeyboardEvent", "PointerEvent", "WheelEvent", "ClipboardEvent", "DataTransfer", "MediaQueryList", "Location", "Performance", "Navigator", "Clipboard", "CssStyleDeclaration", "console", "WebSocket", "MessageEvent", "CloseEvent", "ErrorEvent", "Storage", "Crypto", "DragEvent", "FileList", "File", "Blob", "Request", "RequestInit", "Response"] }

PROGRESS.md

@@ -76,6 +76,133 @@ are credited in `THIRD_PARTY.md`.
 * **Not carried over**: comments, design tokens, AI image generation, video export, teams;
   moving layers between pages; remote image URLs (see README Known gaps).
 
+### 2026-10-28: overflow lint rule and `get_bounds`
+
+* `lint_design` has an `overflow` rule (`src/mcp/lint_overflow.rs`): layers past their artboard or clipping parent, and text taller than its box. Scrolling frames and what is pinned in them are exempt; it is never auto-fixed. It is a pure function over a node set, so a scope filter can pass any subset.
+* New tool `get_bounds {nodeIds?, pageId?, depth?}` (`src/mcp/bounds.rs`): every layer's rect in one read (about 2000 rows per call, then `continueWith`). Tool count is now 87 (one more than before; if another branch also adds a tool, recount). Tests: `tests/mcp_bounds.rs`.
+
+### 2026-10-28: agent reads no longer look like edits
+
+* Read-only tool calls (`get_node_info`, `get_children`, ...) have honest verbs ("Looking at the design") and light the "Working" pill for 1.5 s instead of 6 s, so it goes out right after a sweep ends.
+* A sweep of reads draws at most one layer outline (a read outlines only when no other read ran in the last 2 s) and no longer pans the follow-agent camera; edits behave as before. "Is this a read" comes from `mcp::tools::edits_doc`.
+
+### 2026-10-28: 0.9.0 (presentations, critique, several agents, lighter chats)
+
+* Export the screens as a presentation PDF: cover, contents and a slide per screen (File menu, palette, `--format presentation`, `export_presentation`).
+* `critique_design` reviews finished work through personas (vision, UX, flow, QA, visual, accessibility, copy, end-user); `design_lessons` keeps the findings the person approved for every later design.
+* Several agents on one project: named CLI agents (`--as`), conflict reports and `ifRev` on writes, `claim_nodes` / `release_claims` / `list_claims`, scoped delegate builds and per-agent undo. 94 tools.
+* Screens keep their device height and scroll what does not fit; sections group screens on the canvas; pages can carry icons.
+* UI kits for shadcn, MUI, Mantine, Bootstrap and Chakra; `write_html` follows the browser more closely.
+* Memory: chat screenshots move to files (kept 14 days), thumbnails stay small, canvas images decode only for the GPU. A long chat dropped from about 1 GB to about 400 MB.
+* Fix: long answer options in a question card wrap instead of widening the whole chat.
+
+### 2026-10-28: 0.8.4 (demo video, fresh screenshots)
+
+* README opens with a time-lapse of designing a habit-tracker app (`docs/demo.gif`, full video `docs/demo.mp4`), and every screenshot is retaken from that design.
+* Fix: the Performance overlay reads its settings from the project config folder, so `PAPERCRAFT_HOME` isolates it too.
+
+### 2026-10-28: 0.8.3 (menus, panel grips, narrow windows)
+
+* Menus open 6 px below their button, are at least 180 px wide and show an icon beside each item. Below 1100 px the hamburger opens every menu in one popup.
+* Side panels: a slim rounded grip in the gap resizes them (double click resets) and `/` hides or shows both. Panels size to their content and step aside when the window is too narrow for the canvas.
+* Sharper window buttons (pixel-snapped glyphs); the hamburger morphs into a back arrow while the File / Edit strip slides open and shut.
+* Fixes: lint Fix buttons no longer cover the issue text; review rows keep their badge and revert button off the hover edge; the Export button stays on one line.
+
+### 2026-10-28: 0.8.2 (refresh-rate cap, accurate RAM/CPU, toolbar)
+
+* Settings > Performance > Refresh rate is now a real frame cap applied live (30 to 360 Hz, 60 by default); **Auto** draws as fast as the display allows and is the default on macOS.
+* Performance Monitor: RAM is the private working set and CPU is divided by logical cores on Windows, so both match Task Manager.
+* Windows and Linux toolbar: a hamburger button shows or hides the File / Edit strip (remembered); the close button uses the theme's danger colour on the acrylic surface, with hover animation and a pointing-hand cursor.
+
+### 2026-10-28: 0.8.1 (Performance Monitor on Windows, Design tab speed)
+
+* Performance Monitor: RAM (working set) and CPU now show on Windows; before they were `n/a` there. The overlay and slow-frame badge judge frames against a refresh rate you pick in Settings > Performance: 30 to 360 Hz (144, 165 and 240 included), 60 by default.
+* Design tab: the lint and the open-feedback scan are kept until the document changes instead of walking every node each frame; a 12.6k-node page no longer drops to a few FPS while the tab is open.
+* Windows and Linux: window buttons in the toolbar; controls and acrylic come from craft-ui.
+
+### 2026-10-27: 0.8.0 (screens, packed pages, canvas performance)
+
+* Screens (`specs/screens`): a frame can be declared a screen or an overlay (drawer, modal, sheet) with `set_screens`, inspector toggles, or Declare N screens on the page. Agent edits to layers hidden behind an overlay or opaque layer in their screen are refused unless `allowHidden`; partly covered ones are reported with their visible share. `get_basic_info` lists screens, `get_node_info` tells a layer's visibility, `lint_design` skips hidden layers, On click lists screens, nested screens get canvas labels.
+* Pages and saved versions are stored as zstd-compressed compact JSON (`.json.zst`, project format 3): the 68 MB Interview project is 1.3 MB on disk and loads faster. A legacy `.json` still reads and is replaced on the next save; older builds refuse format 3.
+* Canvas performance: the editor logs which layers each change touched, so the scene cache re-tessellates only those and keeps no copy of the document (443 → 346 MB on Interview). Zoom holds its geometry until it settles, tiny layers are skipped, vertices are 24 bytes, redraws follow vsync, the idle pointer no longer redraws, freed memory goes back to the system when idle, off-screen frame labels are skipped, and the layers panel keeps its row heights between frames (panning a large page: ~9 → ~0.7 ms a frame).
+* Frame labels: none on frames too narrow on screen, overlapping labels are dropped (selected and larger frames first), long names end in an ellipsis.
+* Dropdowns size to their longest option (capped), keep the name of `A / B / Name` options, scroll when long and show the full name on hover.
+* Settings: a Performance page (FPS, frame time, RAM, CPU, GPU, optional overlay and slow-frame badge), agent logos in the agent rows; the Chat page no longer collapses.
+
+### 2026-10-25: 0.8.0 (properties modal, row merges)
+
+* Properties modal (inspector, on a main: Edit properties…): a tab per property (name, kind, layer, default, delete); an options property as a Table (a row per option, a column per layer · style; colours picked from the project's variables with a swatch, visibility as a toggle, icon, image and text fields; add or remove options and columns) or as Source (each option's changes as JSON with syntax highlighting); templates from the + Property menu; Save replaces them all. The inline list is name, kind and a remove button. The `status` template writes colours the project has as variables as those variables.
+* Canvas overlays (agent glow, agent outlines, review outlines, the agent-elsewhere chip) sit below modals instead of showing through them. Two segmented controls in one row no longer share widget ids (the second did not respond).
+* `merge_variants` keeps what each moved instance shows (texts that came from its old variant), carries nested instances' property values (a badge's Tone) in the options, and takes `textLayers` for state texts only.
+
+### 2026-10-25: 0.8.0 (prototype links tool, merge icon colours)
+
+* `set_prototype_links`: agents can link a layer to a screen for Present mode (back arrows, rows, tabs); before, only the inspector could.
+* `merge_variants` compares an icon's colour (keeping its variable), now that icons are compared as one unit.
+
+### 2026-10-25: 0.8.0 (data safety fixes)
+
+* Sync no longer throws away an instance written over a nested one the way older versions stored it (its own root, no swap): it becomes a swap of the main's child at that place. Projects built before #11 lost such layers (a checked checkbox, a status badge) on the next edit of the outer main.
+* Icons: the HTML parser keeps attribute names in lowercase, so the icon and plugin code never removed the SVG's original `viewBox`; since #14 that made `<x-paper-icon>` (and icon swaps) scale twice and come out tiny. Unreleased builds only; 0.7.3 is not affected.
+* `merge_variants` refuses merges that would leave one option and changes nothing then.
+
+### 2026-10-25: 0.8.0 (merge variants, pinned bars)
+
+* `merge_variants`: per-state components (`Tab bar / Hoje`, `Status / Sucesso`...) become one component with an enum property. Each variant's differences from the base, matched by layer path (fills, colours, borders, weight, radius, visibility, icons; texts on request), become its option; every instance on every page moves to the base with its value; the base takes the family name; the emptied variants are deleted. A variant with layers the base lacks is left out and reported.
+* Absolute children of a scrolling screen stay pinned while its content scrolls (a tab bar, a floating button), and do not add to the scroll range.
+
+### 2026-10-25: 0.8.0 (fix #22)
+
+* #22: a hug column whose width comes from its parent (stretched or filled) re-measures its height once its text wraps at that width, and the parent measures again, instead of keeping a height measured while the text was narrow.
+
+### 2026-10-25: 0.8.0 (component properties)
+
+* Main components carry properties (`Node.props`): `text`, `bool`, `icon` and `enum`, whose options are changes in the overrides format (a layer name, `$root` or a path `Item > Label`, to a text or styles that may hold `text`, `icon` and `visibility`), so they restyle, retext, show, hide or re-icon any layer. Instances keep their values (`prop_values`) as overrides, so main edits keep them; changing the definitions re-applies every instance on every page.
+* Templates: `text` (a property per text layer), `active` (which item of a tab bar, nav or segmented row is active) and `status` (options with a colour tint the root and colour the label and icon).
+* `set_component_props`, `set_instance_props`, `props='{...}'` on `<x-paper-instance>`, properties in `get_components`, `{Prop}` in code link templates, and an inspector section (a control per property on an instance; Texts and Active item templates on a main). Icon swaps keep the layer's name and link (a `children` override); recoloured icon shapes inside instances now keep their colour after a sync.
+* Spec: `specs/component-props/spec.md`.
+
+### 2026-10-25: 0.8.0 (scrolling screens)
+
+* Screens keep their size and scroll what overflows: a frame's `scroll` flag (CSS `overflow: auto|scroll`, `overflow-y-auto` in the Tailwind export) makes it fixed height and clipped, and the wheel over it scrolls its content on the canvas and in Present, then pans once the content ends. The offset is view state, not saved; hit-testing and overlays follow it.
+* Toggles: a scroll button beside each screen's name (shown when it scrolls, overflows, or is hovered), Scroll overflow on a selected frame, and Screens scroll on the page for every screen at once. A fit-content screen that grew goes back to its min height.
+* Agents are told to keep screens at their size and use overflow:auto for long content.
+
+### 2026-10-25: 0.8.0 (fixes #19, #20, #21)
+
+* #19: a clipping frame draws its border after its children, so filled rows no longer hide it. Clipping stays rectangular: children's square corners still show past a rounded border.
+* #20: a border written with a colour variable (`1px solid var(--border)`) binds the stroke, a literal one unbinds it, and reads show `var(--name)` for bound strokes. `find_nodes` says when it stopped at 500 matches.
+* #21: hug (fit-content) frames grow around growing children (CSS flex-basis auto) instead of staying at their min height; with short content the min height stays and the growing child fills it, so a pinned footer works.
+
+### 2026-10-25: 0.8.0 (follow agents, skeletons)
+
+* Follow agents (Settings, Chat; on by default): in Design and Chat mode alike, the canvas pans, and switches page, to the layer any agent changes (the chat, Claude Code over MCP, a helper). Moving the canvas yourself pauses it for a moment; off, a chip offers the agent's page.
+* Skeletons: the moment the model starts writing a tool call (`ToolDraft` and `ToolInput` events from Claude Code's stream and the API), the canvas shows a shimmering skeleton over its target, or where a new artboard goes, labelled with what it is doing, until the call has run. Fresh agent content comes in through a skeleton that fades, so an outline never frames empty space.
+* Top bar: the title and the agent pill leave room measured from the buttons on the right, so nothing overlaps at narrow widths.
+
+### 2026-10-25: 0.8.0 (fixes #14 to #18)
+
+* #14: `write_html` fits an `<svg>` viewBox into its width and height like a browser (centred, aspect kept).
+* #15: a note on something placed straight in its artboard treats the artboard as the screen: tidy keeps cards off it instead of in its free space.
+* #16: `not-an-instance` no longer matches look-alikes with a different icon; its fix names the `<x-paper-instance>` to write (swap_instance refuses plain frames).
+* #17: instances with their own text re-measure it when the main's text style changes, so hug buttons keep fitting their labels (also covers the size reset after a swap).
+* #18: `lint_design` reports borders whose hex equals a color variable, and `fix` binds them (`stroke`), so a mode switch reaches them.
+
+### 2026-10-25: 0.7.3 (QA sub-agent, helper agents, auto mode, mid-turn messages, isolated dev settings)
+
+* QA sub-agent: Claude Code chats always get a Sonnet `qa` agent that lints and screenshots built frames and returns only findings, so screenshots stay out of the main context.
+* Helper agents (`src/mcp/delegate.rs`, Settings, Chat, Helper): `delegate` hands `qa`, `read` or `build` tasks to a cheaper agent CLI (pi with MiniMax M3.1 Flash, opencode, an Ollama-backed agent, any command taking `{prompt}`). It drives PaperCraft through `papercraft-cli`, runs off the UI thread, and only its last 6,000 characters come back. With a helper set, the chat agent orchestrates: keeps the brief and taste, delegates review, bulk reading and fully specified edits.
+* Dev config isolation: `PAPERCRAFT_HOME` also isolates the chat settings (`$PAPERCRAFT_HOME/.config`), so a second copy for testing never touches the installed app's settings.
+* Live check in an isolated copy: `delegate` ran the pi helper (MiniMax M3.1 Flash) as QA, a message added mid-turn went Waiting then Seen, and the agent drafted #13.
+* Fixes #10, #11, #12, #13:
+  * #10: `move_nodes` to another page keeps mains' component keys and relinks every instance to moved nodes; new `rename_file` renames a project.
+  * #11: swapped nested instances persist as swap overrides (`InstanceLink.swap`), preserving component identity across outer component updates and copies.
+  * #12: `move_nodes` to another page takes the moved nodes' annotations along; detached notes resolve as `Detached #n`.
+  * #13: `get_computed_styles` reports a text colour bound to a variable as `var(--name)`.
+* Auto mode (the composer's Auto chip): when a turn ends on `ask_user` questions, the first (recommended) option of each is sent and the chat goes on, until Stop or a turn hits its budget. The agent is told to put its recommendation first, default what only the user can know, and end each turn with next steps.
+* The Present button uses a play icon drawn like the icons beside it. Composer chips wrap instead of running under Stop and Add. Top bar: the agent pill drops its text when it would run under the buttons on the right.
+* While a chat turn works, the composer's Add (or Enter) queues a message (`src/mcp/steer.rs`). It rides on the agent's next PaperCraft tool result for that chat, so every backend reads it mid-turn; the composer shows each as Waiting or Seen. What no tool call picked up is sent as the next message when the turn ends, or goes back into the box after Stop.
+
 ### 2026-10-24: 0.7.2 (UI kits, code links, issues from the app, design playbook)
 
 * Code links (Figma Code Connect style): a main component carries its library import and a React and an egui template (`set_code_link`). The React, Tailwind, inline JSX and egui exports write linked instances as that code, with overrides filled in and imports gathered once; the AI spec lists them as Library Components with a "use it, do not rebuild it" rule and stops describing their inner layers.
@@ -124,6 +251,17 @@ are credited in `THIRD_PARTY.md`.
 * Agent view lists runs and supports review, whole-run revert, per-change undo and accept all. Review adds canvas outlines and a finish toast; palette commands review or revert the last run.
 * Id-paired page diffs power review; History version compare UI remains todo. Completed with full restore (including variables, modes and tokens), tool edit classification, and wasm support.
 
+### 2026-10-28: Incremental lint
+
+Agents re-linted whole pages after every edit. A bounded change log (`src/editor/changes.rs`, the
+last 10000 layer changes, each with the client that made it) now records which layers every
+commit, undo and redo touched; variable edits count as touching the layers bound to them. Write
+tools return `rev`, `get_basic_info` reports it, `get_changes {since, page?, exclude?, by?}` lists
+the changes, and `lint_design {since | changedOnly}` checks only those layers plus their
+ancestors, descendants and siblings (`src/mcp/incremental.rs`), with `covered` saying what ran.
+Tests: `tests/incremental.rs`, unit tests next to the code, the attribution check in
+`tests/mcp.rs::parallel_sessions_get_their_own_runs`.
+
 ### 2026-10-21: Design libraries and offline CLI
 
 * Variables are now collections with modes, slash groups, four types and aliases, stored in `design.json` (project version 2; 0.4.0 refuses migrated projects). Each page keeps a derived cache; every edit is one undo step per page, and the page-only removals are gone. Per-page active mode per collection.

README.md

@@ -12,9 +12,17 @@
 </p>
 
 <p align="center">
-  <img src="docs/screenshots/readme/hero.png" alt="PaperCraft with the Redesign page of its own design file open: layers on the left, the canvas in the middle, the inspector on the right" width="100%">
+  <a href="docs/demo.mp4">
+    <img src="docs/demo.gif" alt="PaperCraft's editor breaking apart into its panels on a 3D stage, then chat mode with an agent, annotations pinned to a sign-in screen, the variables and libraries modals, and the home screen" width="100%">
+  </a>
   <br>
-  <sub>PaperCraft editing its own design file (the Redesign page).</sub>
+  <sub>A 40-second tour: the editor, chat mode, annotations and design systems. <a href="docs/demo.mp4">Watch it in full quality</a> (MP4, 1080p60). Rendered from the app's own design with <a href="tools/showcase/README.md">tools/showcase</a>, not screen-recorded.</sub>
+</p>
+
+<p align="center">
+  <img src="docs/screenshots/readme/hero.png" alt="PaperCraft with the Pulse habit-tracker design open: layers on the left, three annotated screens on the canvas, the inspector on the right" width="100%">
+  <br>
+  <sub>The finished design: three screens, a component library and annotations.</sub>
 </p>
 
 <p align="center">
@@ -25,6 +33,7 @@
   <a href="#keyboard-shortcuts">Shortcuts</a> ·
   <a href="#status-and-known-limits">Status</a> ·
   <a href="#project-layout">Layout</a> ·
+  <a href="#contributing">Contributing</a> ·
   <a href="#license-and-credits">License</a>
 </p>
 
@@ -54,11 +63,11 @@ It is an alpha. It is good for building screens, design systems and sketches, an
 <table>
   <tr>
     <td width="50%" valign="top">
-      <img src="docs/screenshots/readme/variables.png" alt="The Variables modal listing the Colors collection with four Catppuccin modes" width="100%">
-      <br><sub>Variables modal: collections, modes, groups and types.</sub>
+      <img src="docs/screenshots/readme/variables.png" alt="The Variables modal listing the Colors collection with Light and Dark values for brand, foreground and background" width="100%">
+      <br><sub>Variables modal: collections, modes (Light and Dark here), groups and types.</sub>
     </td>
     <td width="50%" valign="top">
-      <img src="docs/screenshots/readme/assets.png" alt="The Assets side view with components grouped into Banner, Button, Checkbox and Chip" width="100%">
+      <img src="docs/screenshots/readme/assets.png" alt="The Assets side view with the Habit row component and the shadcn Button kit" width="100%">
       <br><sub>Assets view: components grouped by name, from this file and enabled libraries.</sub>
     </td>
   </tr>
@@ -68,12 +77,32 @@ It is an alpha. It is good for building screens, design systems and sketches, an
       <br><sub>Libraries modal: publish this file, enable libraries from the store.</sub>
     </td>
     <td width="50%" valign="top">
-      <img src="docs/screenshots/readme/agent-review.png" alt="Agent run review: a list of changes on the left and green, yellow and red outlines on the canvas" width="100%">
-      <br><sub>Review of an agent run, with the changes outlined on the canvas.</sub>
+      <img src="docs/screenshots/readme/agent-review.png" alt="The Agent side view: a finished run with Review and Revert, above the list of earlier runs" width="100%">
+      <br><sub>The Agent view: runs, with Review and Revert for the latest.</sub>
     </td>
   </tr>
 </table>
 
+<table>
+  <tr>
+    <td width="50%" valign="top">
+      <img src="docs/screenshots/readme/toolbar-panels.png" alt="The toolbar with the menu button folded into a back arrow, the File to Theme strip, and the floating left panel with a slim grip beside it" width="100%">
+      <br><sub>Toolbar and panels: the menu button shows or hides the File / Edit strip, and the slim grip between a panel and the canvas resizes it (double click resets). <kbd>/</kbd> hides both side panels.</sub>
+    </td>
+    <td width="50%" valign="top">
+      <img src="docs/screenshots/readme/menus.png" alt="The Tools menu open below its button, each tool with an icon and its shortcut" width="100%">
+      <br><sub>Menus open a little below their button, are never narrower than 180 px, and carry an icon next to each item.</sub>
+    </td>
+  </tr>
+  <tr>
+    <td width="50%" valign="top">
+      <img src="docs/screenshots/readme/annotations.png" alt="The Annotations side view listing five notes grouped by screen, with their category chips" width="100%">
+      <br><sub>Annotations: rule, behaviour, content and data notes, kept with the layers they describe.</sub>
+    </td>
+    <td width="50%" valign="top"></td>
+  </tr>
+</table>
+
 **Prototyping and review**
 * Prototype links between frames and a **Present** mode that follows them with a camera glide.
 * **Version history:** named and automatic saved versions per page; rename, restore, delete.
@@ -90,7 +119,7 @@ Projects live in `~/Documents/papercraft/<name>/` (`project.json`, one JSON file
 
 ## Agents
 
-PaperCraft exposes **70 tools** (`src/mcp/tools.rs`) three ways. They run the same code inside the app.
+PaperCraft exposes **94 tools** (`src/mcp/tools.rs`) three ways. They run the same code inside the app.
 
 | Way | Notes |
 |---|---|
@@ -141,7 +170,7 @@ EOF
 Chat mode (⌘J, or `Design | Chat` in the top bar) puts a conversation next to the canvas. It runs Claude Code and Codex through their CLIs, any agent that speaks the Agent Client Protocol (ACP, such as OpenCode, Gemini CLI or Cursor) found on your PATH, or the Anthropic API with your own key. It shows tool calls, checkpoints and run review in the thread. Chats are saved in the project's `chats/` folder. See [docs/chat.md](docs/chat.md).
 
 <p align="center">
-  <img src="docs/screenshots/readme/chat.png" alt="Chat mode: the chat column on the left shows a finished agent run with its Review, Revert and Accept actions, and the canvas on the right" width="100%">
+  <img src="docs/screenshots/readme/chat.png" alt="Chat mode: the chat column on the left with its starter prompts and input, and the annotated habit-tracker screens on the canvas" width="100%">
   <br>
   <sub>Chat mode with a finished agent run: review, revert or accept from the thread.</sub>
 </p>
@@ -162,12 +191,13 @@ Releases are at [git.marcospaulo.dev.br/masi/papercraft/releases](https://git.ma
 
 | Build | File |
 |---|---|
+| Windows (x86_64) | `papercraft-<version>-windows-x86_64.zip`: `papercraft.exe`, `papercraft-cli.exe`, `papercraft-mcp.exe` and `papercraft-relay.exe` |
 | macOS app (Apple silicon) | `papercraft-<version>-macos-aarch64.dmg`, containing PaperCraft.app |
 | Linux (x86_64) | `papercraft-<version>-linux-x86_64.tar.gz` |
 | CLI tools, macOS | `papercraft-cli-<version>-macos-aarch64.zip` (`papercraft-cli` and `papercraft-mcp`) |
 | CLI tools, Linux | `papercraft-cli-<version>-linux-x86_64.tar.gz` |
 
-macOS builds are ad-hoc signed and not notarized: on another Mac, open the app with right-click, Open the first time. Other platforms: build from source.
+The Windows zip is unsigned: SmartScreen may ask you to confirm the first run. macOS builds are ad-hoc signed and not notarized: on another Mac, open the app with right-click, Open the first time. Other platforms: build from source.
 
 ### Build from source
 
@@ -179,9 +209,10 @@ cargo build --release
 ./target/release/papercraft ~/Documents/papercraft/Plan    # open a project folder
 ./target/release/papercraft --demo                         # sample board, not saved
 packaging/macos/package.sh                                 # PaperCraft.app on a DMG, plus the CLI zip
+pwsh packaging/windows/package.ps1 -Arch x64               # Windows MSI, portable zip and CLI zip
 ```
 
-**macOS:** `xcode-select --install` for the linker. It renders with Metal through wgpu. **Linux:** install the runtime libraries (`sudo apt install libxkbcommon-x11-0 libxcb-xkb1 libvulkan1 mesa-vulkan-drivers` on Debian or Ubuntu); it runs on X11 and Wayland through Vulkan, with GL as a fallback, and file dialogs use the XDG desktop portal.
+**Windows:** the MSVC build tools (Visual Studio Build Tools with the C++ workload); it renders through wgpu on Direct3D 12 or Vulkan. **macOS:** `xcode-select --install` for the linker. It renders with Metal through wgpu. **Linux:** install the runtime libraries (`sudo apt install libxkbcommon-x11-0 libxcb-xkb1 libvulkan1 mesa-vulkan-drivers` on Debian or Ubuntu); it runs on X11 and Wayland through Vulkan, with GL as a fallback, and file dialogs use the XDG desktop portal.
 
 To run a test copy next to your own PaperCraft, give it its own folder and port: `PAPERCRAFT_HOME=/tmp/pc PAPERCRAFT_MCP_PORT=29998 ./target/release/papercraft`.
 
@@ -228,24 +259,32 @@ The scenario tests drive the editor with synthetic pointer and keyboard events;
 | PageUp / PageDown | Previous / next page | ⌘\\ | Show / hide UI |
 | ⌘J | Design / Chat mode | ⌘L | Add selection to chat (Chat mode) |
 | N | Annotate tool | ⌘⇧A | Annotations: full, badges, hidden |
+| / | Show / hide the side panels | | |
 
 Draw a frame around existing shapes and it adopts them; dragging a layer into or out of a frame re-parents it. Hold ⌘ while dragging to suspend snapping.
 
 ## Status and known limits
 
 > [!IMPORTANT]
-> PaperCraft is an alpha. [ROADMAP.md](ROADMAP.md) lists what is missing, in priority order; [PROGRESS.md](PROGRESS.md) is the milestone history.
+> PaperCraft is an alpha (0.8.x). It is used daily on Windows, macOS and Linux, and its project format migrates forward, but expect rough edges. [ROADMAP.md](ROADMAP.md) lists what is missing, in priority order; [PROGRESS.md](PROGRESS.md) is the milestone history.
+
+**What works today:** local projects with pages and an infinite canvas; vector, text, auto layout, constraints, components with properties and variants, variables with modes, shared libraries and screens; annotations, lint and Present mode with prototype links; PNG, SVG and PDF export, Figma, Excalidraw and SVG import; the MCP server, CLI (online and offline) and in-app Chat mode; versions, agent runs with review and revert; optional relay sync.
+
+**Known limits:**
 
 * **No rotation.** Nodes are axis-aligned boxes; rotated imports are baked into paths.
 * **Text** is Inter only, with no shaping (no ligatures, complex scripts or RTL) and no font picker. IME preedit is not displayed.
 * **Rendering approximations.** Frame clipping is a rectangle, so rounded frames do not clip their corners. Overlay, dodge, burn, light, difference, exclusion and the HSL blend modes draw as Normal on the canvas (they are exact in SVG and PDF export). There is no layer or background blur yet.
-* **Variables:** gradients keep fixed colors; there are no text styles and no component variants or properties.
+* **Variables:** gradients keep fixed colors, and there are no text styles (named type styles that update every text layer).
+* **Components:** properties (text, bool, icon, enum) and `merge_variants` cover variants, but there are no variant sets with several axes, and no responsive per-breakpoint variants or breakpoint preview.
+* **Prototyping:** links and flows work in Present mode; smart transitions and hover states do not exist yet.
 * **Booleans are destructive:** the result is a new vector path with flattened curves.
 * **`write_html`** ignores margin, tables and transforms (it reports them as `ignoredStyles`) and does not fetch remote images; pass a local path or a `data:` URI.
 * **Agents:** one project is open at a time in the app, and `move_nodes` stays on one page. The in-app Chat mode runs Claude Code, Codex, ACP agents or your own Anthropic key. Agents that are not in Chat connect over MCP or the CLI.
 * **Sharing** has no live presence (cursors, selections) yet.
+* **Scale:** cached frames take about 3 ms at 10k visible nodes; it is not tuned for 100k.
 * **Pen pressure** is simulated from stroke velocity on macOS tablets, because winit 0.30 does not expose it for mouse-like pen events.
-* **Releases** cover macOS (Apple silicon) and Linux x86_64. Windows packaging scripts exist but are not part of releases.
+* **Releases:** the Gitea releases ship Windows x86_64. macOS (Apple silicon) and Linux x86_64 builds come from the packaging scripts or from source; the Linux build is not part of the current releases.
 * **PDF** text is outlined, not selectable.
 
 ## Project layout
@@ -280,12 +319,14 @@ analysis/            behaviour studies and design notes
 docs/                guides and screenshots
 ```
 
+## Contributing
+
+Bug reports, ideas, docs and code are welcome. Start with [CONTRIBUTING.md](CONTRIBUTING.md) (setup, checks, commits, pull requests) and [RULES.md](RULES.md) (the standards a change is reviewed against). AI tools are welcome under the [AI usage policy](AI_POLICY.md), and coding agents should read [AGENTS.md](AGENTS.md). Security problems go through [SECURITY.md](SECURITY.md), and everyone follows the [Code of Conduct](CODE_OF_CONDUCT.md).
+
 ## License and credits
 
 Dual-licensed under [MIT](LICENSE-MIT) or [Apache-2.0](LICENSE-APACHE), at your option.
 
 Bundled fonts, icons and other assets keep their own licenses, listed in [ATTRIBUTION.md](ATTRIBUTION.md); Inter is © The Inter Project Authors under the SIL Open Font License 1.1. Some algorithms are ported from MIT-licensed projects (rough.js, hachure-fill, Excalidraw), with their notices in [THIRD_PARTY.md](THIRD_PARTY.md).
 
-PaperCraft started as a fork of [storytold/paper-rs](https://git.marcospaulo.dev.br/storytold/paper-rs); thanks to its contributors.
-
 PaperCraft is not affiliated with Paper or Figma. Only the behavior of other tools was studied (see `analysis/`); no code, shaders, icons, fonts or assets from them are used.

ROADMAP.md

@@ -22,7 +22,7 @@ Agents can already build a design system through the tools; people cannot yet ma
 | 7 | Number variables (spacing, radius, font size) | **done** | Typed number, string and boolean variables in collections with groups and aliases; fields bind (size, gap, padding, radius, font size, line height, opacity, visible) in the inspector and `bind_variable`. |
 | 8 | Stroke and gradient variables | partial | Strokes and text color bind to variables. Gradients keep fixed colors. |
 | 9 | Text styles | todo | Named type styles (Heading / L, Body / M) that update every text layer using them. |
-| 10 | Component variants and properties | todo | Variants are separate components named `Button / Primary`. No variant sets, boolean or text properties. |
+| 10 | Component variants and properties | partial | Main components carry text, bool, icon and enum properties; `merge_variants` folds per-state components into one. Multi-axis variant sets todo. |
 | 11 | Swap instance, detach by tool | **done** | `swap_instance` and `detach_instance` MCP tools + UI controls in Design tab and Inspector. |
 | 12 | Cross-page and shared libraries | **done** | Instances of a main on any page; publish a project as a library, enable, update and disable it in other projects (Libraries modal, `*_library` tools). |
 | 13 | Export design tokens | **done** | `get_variables` with `format: "css"`, `"json"` (W3C DTCG + modes), or `"tailwind"` (`@theme`), plus Copy CSS / Copy JSON in Design tab. |
@@ -32,7 +32,7 @@ Agents can already build a design system through the tools; people cannot yet ma
 
 | # | Item | Status | Notes |
 |---|---|---|---|
-| 15 | MCP and CLI tool surface | **done** | 67 tools, one undo step per call, `papercraft-cli list / schema / call`. |
+| 15 | MCP and CLI tool surface | **done** | 94 tools, one undo step per call, `papercraft-cli list / schema / call`. |
 | 16 | Agent skills | **done** | `skills/papercraft` and `skills/papercraft-design`. |
 | 17 | Accessibility annotations | todo | Reading order, roles and alt text on layers, checked by the linter. |
 | 18 | Code export from frames | **done** | `get_jsx` supports `format: "inline"`, `"tailwind"` (Tailwind utility classes), and `"html"` (HTML + CSS rules with `:root` variables). |
@@ -63,7 +63,7 @@ Agents can already build a design system through the tools; people cannot yet ma
 | 32 | Version history | **done** | Named and automatic saved versions per page: rename, restore, delete (`src/versions.rs`). Restore now includes variables and tokens; compare todo. |
 | 33 | Figma import | **done** | `.fig` binary (Kiwi wire decoder + zip container) and Figma REST API JSON import in `src/io/fig.rs`. |
 | 34 | Multiplayer and cloud sync | partial | Optional shared projects through the relay, with merge of concurrent edits to one page. Presence (cursors, selections) todo. Stays optional. |
-| 35 | Release builds for Windows and Linux | todo | The code targets them (wgpu, winit); packaging today is the macOS DMG and the `papercraft-cli` zip. |
+| 35 | Release builds for Windows and Linux | partial | Windows x86_64 zips are released and `packaging/windows` builds an MSI; Linux x86_64 is not in the current releases. |
 
 ## 5. Quality
 

RULES.md

@@ -0,0 +1,124 @@
+# Project rules
+
+The standards a change to PaperCraft is reviewed against. [CONTRIBUTING.md](CONTRIBUTING.md) says
+*how* to contribute; this file says what "good" means once you do.
+
+## Code
+
+* **Immutability by default.** Return new values rather than mutating shared ones. The document
+  changes only through `Editor::edit` transactions, so every change is one undo step and is
+  logged for the renderer's cache.
+* **Small, cohesive files.** 200 to 400 lines is typical, 800 is the ceiling. Split a module
+  when it grows past that. Organise by feature, not by type.
+* **Small functions** (under about 50 lines) and **shallow nesting** (4 levels at most); prefer
+  early returns.
+* **Handle errors explicitly.** No `unwrap` or `expect` on user data, file contents or network
+  responses; return an error with context. User-facing messages are plain language. Never swallow
+  an error silently.
+* **Validate at the boundaries**: MCP and CLI arguments, imported files (Figma, Excalidraw, SVG),
+  project folders and anything from the relay. Treat all of it as untrusted.
+* **No magic numbers.** Name thresholds, sizes and delays as constants; UI measures come from
+  the theme, not literals.
+* **No dead code, debug prints or commented-out blocks.**
+* **Match the surrounding code**: naming, comment density and idiom. Comments say *why*, not
+  *what*.
+* **Cross-platform.** Code must build on Windows, macOS and Linux and for the web build. Gate
+  platform code with `cfg`, never assume a path separator, and keep
+  `cargo check --lib --target wasm32-unknown-unknown` passing.
+* **No new heavy dependencies** without discussion. Licenses must be compatible with
+  MIT OR Apache-2.0.
+
+## Data safety
+
+PaperCraft stores people's work. Treat that as the top priority.
+
+* Writes to projects are **atomic** (`src/io/atomic.rs`); never write a page in place.
+* A format change bumps the project format version and ships a **migration**. Older data must
+  keep loading; if a newer build writes something an older build cannot read, the older build
+  must refuse it rather than corrupt it.
+* Agent and sync paths must never silently drop a layer. If a merge cannot keep something, it
+  says so.
+* Destructive operations are undoable or confirmed.
+
+## The machine you build on
+
+A full build links dozens of test binaries and can take every core and most of the memory of a
+desktop. The person is still using that machine, often with PaperCraft open.
+
+* **Look before you start a heavy job.** Check free memory, CPU load and what is already running
+  (the person's app, another build, other agents) before a build, a test run or clippy. If memory
+  is short or another build is running, wait or ask.
+* **Leave room.** Cap Cargo at no more than half the logical cores (`-j 8` on a 16-core machine,
+  or `CARGO_BUILD_JOBS`) and the test harness too (`-- --test-threads=8`); go lower when memory is
+  tight, since linking is the peak. Run heavy jobs at low priority (`nice` on Unix, Below Normal
+  on Windows).
+* **One heavy job at a time.** Never run two builds side by side; each target folder is a full
+  build's worth of compiling and linking. Parallel agents share one build slot.
+* **Run only what your change touches**: `cargo check` before `cargo build`, and the test
+  targets that cover the change (`cargo test --test incremental`). The full suite runs on GitHub
+  before a release (`.github/workflows/test.yml`), not on a desktop.
+* **Stop at once when the person says the machine is slow**, then check that no compiler, linker
+  or test process of yours is left over.
+* **Clean up.** Delete scratch target folders and worktrees when the work is merged; they grow to
+  tens of gigabytes.
+
+## UI
+
+* **Use the shared kit.** Controls, spacing, radii and colours come from `craft-ui`,
+  `src/ui/kit.rs` and the theme, not one-off values.
+* **Themes are modes.** Never branch on a theme to pick a colour; read it from the palette.
+* **Nothing overflows.** Text truncates with an ellipsis, rows keep their controls inside, and
+  panels step aside when the window is narrow. Test a narrow window and a long name.
+* **Targets are at least 44 px** where a person taps or clicks something primary, and everything
+  stays reachable from the keyboard.
+* **Animation is quick**: eased and under about 200 ms.
+* **Look at it.** Run the app or take a headless screenshot at scale 2 in each theme before
+  asking for review.
+
+## MCP tools and the CLI
+
+* Every tool has a precise one-paragraph description, a JSON schema, and a test in
+  `tests/mcp.rs`. Descriptions are what agents read; write them for that reader.
+* One tool call is **one undo step**.
+* Names follow the existing style (`verb_noun`); reuse Paper-compatible names and argument shapes
+  where a tool has an equivalent.
+* Reads are cheap and bounded. Apply limits, say when you truncated, and never dump the whole
+  document by default.
+* The server listens on `127.0.0.1` only and rejects browser origins. Do not weaken that.
+* Update the tool count in the README and ROADMAP when you add or remove tools.
+
+## Designs made with PaperCraft
+
+These apply to example projects, templates, screenshots and skill content, and are what the
+skills teach agents.
+
+* **Themes are modes, never copies.** One artboard per screen. Give each variable a value per
+  mode and switch with `set_variable_mode`. Do not duplicate artboards as light and dark
+  versions, and do not rebuild a screen with other hex values.
+* **Every colour on a themed screen is a variable** (`var(--name)` on fills and text,
+  `bind_variable` for strokes, opacity and visibility).
+* **No overflow.** Nothing extends past its artboard or clipping parent. Scrolling content is
+  clipped inside its viewport and ends above floating bars with a fade and enough bottom padding.
+  Check each artboard programmatically *and* by screenshot in each mode.
+* Run `lint_design` and fix what it finds: contrast, the 4 px grid, type scale and 44 px targets.
+* Release design locks when you are done so the next person can inspect.
+
+## Skills and docs
+
+* Skills in [skills/](skills) are instructions for agents: keep them short, concrete and tested
+  against a real agent run.
+* Docs describe what exists. Do not document a feature that is not built; put plans in `specs/`
+  and `ROADMAP.md`.
+* Screenshots come from the real app, in a generic project (no personal data, local paths or
+  real names), at scale 2.
+
+## Branding
+
+The tree carries no third-party product branding; `.debrand` lists the forbidden patterns and
+the check runs in review. Describe PaperCraft on its own terms.
+
+## Review
+
+A pull request is approved when it has no unresolved **critical** (security, data loss) or
+**high** (bug, significant quality) issues. Medium and low comments are suggestions the author
+may take or decline with a reason.

SECURITY.md

@@ -0,0 +1,29 @@
+# Security policy
+
+## Supported versions
+
+PaperCraft is an alpha. Security fixes go into the latest release and `main`.
+
+## Reporting a vulnerability
+
+**Do not open a public issue.** Use GitHub's private reporting: the repository's **Security** tab,
+then **Report a vulnerability**. Include what you found, how to reproduce it, the version and
+platform, and the impact you see.
+
+A maintainer will acknowledge the report as soon as they can and keep you updated until it is
+fixed. Please give us reasonable time to ship a fix before you disclose it.
+
+## What counts
+
+Examples of in-scope problems:
+
+* the MCP server (`127.0.0.1:29980`) or the relay accepting requests it should reject (browser
+  origins, DNS rebinding, another user);
+* path traversal or code execution from a project folder, a design-system or library package, or
+  an imported Figma, Excalidraw or SVG file;
+* the updater or the agent integrations running something the person did not approve;
+* secrets (an Anthropic key, relay tokens) written to disk unprotected or sent anywhere
+  unexpected.
+
+PaperCraft is local-first: it opens no network port beyond the loopback MCP server unless you
+share a project through a relay you run.

THIRD_PARTY.md

@@ -62,3 +62,15 @@ SOFTWARE.
 
 Inter 4.1 by Rasmus Andersson — SIL Open Font License 1.1 (`assets/fonts/OFL.txt`). Regular,
 Medium, SemiBold, Bold, Italic and Bold Italic are bundled unmodified.
+
+Interface fonts, SIL Open Font License 1.1, Latin subsets as served by Google Fonts, unmodified
+(Regular, Medium, SemiBold): Geist (Vercel), Figtree (Erik Kennedy), DM Sans (Colophon Foundry,
+Jonny Pinhorn), Nunito (Vernon Adams, Jacques Le Bailly), Quicksand (Andrew Paglinawan),
+Fredoka (Milena Brandão, Hafontia), and Varela Round (Joe Prince; Regular only).
+
+## Agent logos
+
+`assets/agents/*.svg` are from LobeHub Icons (`@lobehub/icons-static-svg` 1.80.0,
+https://github.com/lobehub/lobe-icons), MIT License, Copyright (c) LobeHub. They are used
+unmodified to identify each coding agent in the agent picker. The marks are trademarks of
+their owners.

assets/agents/claude.svg

@@ -0,0 +1 @@
+<svg fill="currentColor" fill-rule="evenodd" height="1em" style="flex:none;line-height:1" viewBox="0 0 24 24" width="1em" xmlns="http://www.w3.org/2000/svg"><title>Claude</title><path d="M4.709 15.955l4.72-2.647.08-.23-.08-.128H9.2l-.79-.048-2.698-.073-2.339-.097-2.266-.122-.571-.121L0 11.784l.055-.352.48-.321.686.06 1.52.103 2.278.158 1.652.097 2.449.255h.389l.055-.157-.134-.098-.103-.097-2.358-1.596-2.552-1.688-1.336-.972-.724-.491-.364-.462-.158-1.008.656-.722.881.06.225.061.893.686 1.908 1.476 2.491 1.833.365.304.145-.103.019-.073-.164-.274-1.355-2.446-1.446-2.49-.644-1.032-.17-.619a2.97 2.97 0 01-.104-.729L6.283.134 6.696 0l.996.134.42.364.62 1.414 1.002 2.229 1.555 3.03.456.898.243.832.091.255h.158V9.01l.128-1.706.237-2.095.23-2.695.08-.76.376-.91.747-.492.584.28.48.685-.067.444-.286 1.851-.559 2.903-.364 1.942h.212l.243-.242.985-1.306 1.652-2.064.73-.82.85-.904.547-.431h1.033l.76 1.129-.34 1.166-1.064 1.347-.881 1.142-1.264 1.7-.79 1.36.073.11.188-.02 2.856-.606 1.543-.28 1.841-.315.833.388.091.395-.328.807-1.969.486-2.309.462-3.439.813-.042.03.049.061 1.549.146.662.036h1.622l3.02.225.79.522.474.638-.079.485-1.215.62-1.64-.389-3.829-.91-1.312-.329h-.182v.11l1.093 1.068 2.006 1.81 2.509 2.33.127.578-.322.455-.34-.049-2.205-1.657-.851-.747-1.926-1.62h-.128v.17l.444.649 2.345 3.521.122 1.08-.17.353-.608.213-.668-.122-1.374-1.925-1.415-2.167-1.143-1.943-.14.08-.674 7.254-.316.37-.729.28-.607-.461-.322-.747.322-1.476.389-1.924.315-1.53.286-1.9.17-.632-.012-.042-.14.018-1.434 1.967-2.18 2.945-1.726 1.845-.414.164-.717-.37.067-.662.401-.589 2.388-3.036 1.44-1.882.93-1.086-.006-.158h-.055L4.132 18.56l-1.13.146-.487-.456.061-.746.231-.243 1.908-1.312-.006.006z"></path></svg>

assets/agents/cline.svg

@@ -0,0 +1 @@
+<svg fill="currentColor" fill-rule="evenodd" height="1em" style="flex:none;line-height:1" viewBox="0 0 24 24" width="1em" xmlns="http://www.w3.org/2000/svg"><title>Cline</title><path d="M17.035 3.991c2.75 0 4.98 2.24 4.98 5.003v1.667l1.45 2.896a1.01 1.01 0 01-.002.909l-1.448 2.864v1.668c0 2.762-2.23 5.002-4.98 5.002H7.074c-2.751 0-4.98-2.24-4.98-5.002V17.33l-1.48-2.855a1.01 1.01 0 01-.003-.927l1.482-2.887V8.994c0-2.763 2.23-5.003 4.98-5.003h9.962zM8.265 9.6a2.274 2.274 0 00-2.274 2.274v4.042a2.274 2.274 0 004.547 0v-4.042A2.274 2.274 0 008.265 9.6zm7.326 0a2.274 2.274 0 00-2.274 2.274v4.042a2.274 2.274 0 104.548 0v-4.042A2.274 2.274 0 0015.59 9.6z"></path><path d="M12.054 5.558a2.779 2.779 0 100-5.558 2.779 2.779 0 000 5.558z"></path></svg>

assets/agents/cursor.svg

@@ -0,0 +1 @@
+<svg fill="currentColor" fill-rule="evenodd" height="1em" style="flex:none;line-height:1" viewBox="0 0 24 24" width="1em" xmlns="http://www.w3.org/2000/svg"><title>Cursor</title><path d="M22.106 5.68L12.5.135a.998.998 0 00-.998 0L1.893 5.68a.84.84 0 00-.419.726v11.186c0 .3.16.577.42.727l9.607 5.547a.999.999 0 00.998 0l9.608-5.547a.84.84 0 00.42-.727V6.407a.84.84 0 00-.42-.726zm-.603 1.176L12.228 22.92c-.063.108-.228.064-.228-.061V12.34a.59.59 0 00-.295-.51l-9.11-5.26c-.107-.062-.063-.228.062-.228h18.55c.264 0 .428.286.296.514z"></path></svg>

assets/agents/gemini.svg

@@ -0,0 +1 @@
+<svg fill="currentColor" fill-rule="evenodd" height="1em" style="flex:none;line-height:1" viewBox="0 0 24 24" width="1em" xmlns="http://www.w3.org/2000/svg"><title>Gemini</title><path d="M20.616 10.835a14.147 14.147 0 01-4.45-3.001 14.111 14.111 0 01-3.678-6.452.503.503 0 00-.975 0 14.134 14.134 0 01-3.679 6.452 14.155 14.155 0 01-4.45 3.001c-.65.28-1.318.505-2.002.678a.502.502 0 000 .975c.684.172 1.35.397 2.002.677a14.147 14.147 0 014.45 3.001 14.112 14.112 0 013.679 6.453.502.502 0 00.975 0c.172-.685.397-1.351.677-2.003a14.145 14.145 0 013.001-4.45 14.113 14.113 0 016.453-3.678.503.503 0 000-.975 13.245 13.245 0 01-2.003-.678z"></path></svg>

assets/agents/githubcopilot.svg

@@ -0,0 +1 @@
+<svg fill="currentColor" fill-rule="evenodd" height="1em" style="flex:none;line-height:1" viewBox="0 0 24 24" width="1em" xmlns="http://www.w3.org/2000/svg"><title>GithubCopilot</title><path d="M19.245 5.364c1.322 1.36 1.877 3.216 2.11 5.817.622 0 1.2.135 1.592.654l.73.964c.21.278.323.61.323.955v2.62c0 .339-.173.669-.453.868C20.239 19.602 16.157 21.5 12 21.5c-4.6 0-9.205-2.583-11.547-4.258-.28-.2-.452-.53-.453-.868v-2.62c0-.345.113-.679.321-.956l.73-.963c.392-.517.974-.654 1.593-.654l.029-.297c.25-2.446.81-4.213 2.082-5.52 2.461-2.54 5.71-2.851 7.146-2.864h.198c1.436.013 4.685.323 7.146 2.864zm-7.244 4.328c-.284 0-.613.016-.962.05-.123.447-.305.85-.57 1.108-1.05 1.023-2.316 1.18-2.994 1.18-.638 0-1.306-.13-1.851-.464-.516.165-1.012.403-1.044.996a65.882 65.882 0 00-.063 2.884l-.002.48c-.002.563-.005 1.126-.013 1.69.002.326.204.63.51.765 2.482 1.102 4.83 1.657 6.99 1.657 2.156 0 4.504-.555 6.985-1.657a.854.854 0 00.51-.766c.03-1.682.006-3.372-.076-5.053-.031-.596-.528-.83-1.046-.996-.546.333-1.212.464-1.85.464-.677 0-1.942-.157-2.993-1.18-.266-.258-.447-.661-.57-1.108-.32-.032-.64-.049-.96-.05zm-2.525 4.013c.539 0 .976.426.976.95v1.753c0 .525-.437.95-.976.95a.964.964 0 01-.976-.95v-1.752c0-.525.437-.951.976-.951zm5 0c.539 0 .976.426.976.95v1.753c0 .525-.437.95-.976.95a.964.964 0 01-.976-.95v-1.752c0-.525.437-.951.976-.951zM7.635 5.087c-1.05.102-1.935.438-2.385.906-.975 1.037-.765 3.668-.21 4.224.405.394 1.17.657 1.995.657h.09c.649-.013 1.785-.176 2.73-1.11.435-.41.705-1.433.675-2.47-.03-.834-.27-1.52-.63-1.813-.39-.336-1.275-.482-2.265-.394zm6.465.394c-.36.292-.6.98-.63 1.813-.03 1.037.24 2.06.675 2.47.968.957 2.136 1.104 2.776 1.11h.044c.825 0 1.59-.263 1.995-.657.555-.556.765-3.187-.21-4.224-.45-.468-1.335-.804-2.385-.906-.99-.088-1.875.058-2.265.394zM12 7.615c-.24 0-.525.015-.84.044.03.16.045.336.06.526l-.001.159a2.94 2.94 0 01-.014.25c.225-.022.425-.027.612-.028h.366c.187 0 .387.006.612.028-.015-.146-.015-.277-.015-.409.015-.19.03-.365.06-.526a9.29 9.29 0 00-.84-.044z"></path></svg>

assets/agents/goose.svg

@@ -0,0 +1 @@
+<svg fill="currentColor" fill-rule="evenodd" height="1em" style="flex:none;line-height:1" viewBox="0 0 24 24" width="1em" xmlns="http://www.w3.org/2000/svg"><title>Goose</title><path d="M21.595 23.61c1.167-.254 2.405-.944 2.405-.944l-2.167-1.784a12.124 12.124 0 01-2.695-3.131 12.127 12.127 0 00-3.97-4.049l-.794-.462a1.115 1.115 0 01-.488-.815.844.844 0 01.154-.575c.413-.582 2.548-3.115 2.94-3.44.503-.416 1.065-.762 1.586-1.159.074-.056.148-.112.221-.17.003-.002.007-.004.009-.007.167-.131.325-.272.45-.438.453-.524.563-.988.59-1.193-.061-.197-.244-.639-.753-1.148.319.02.705.272 1.056.569.235-.376.481-.773.727-1.171.165-.266-.08-.465-.086-.471h-.001V3.22c-.007-.007-.206-.25-.471-.086-.567.35-1.134.702-1.639 1.021 0 0-.597-.012-1.305.599a2.464 2.464 0 00-.438.45l-.007.009c-.058.072-.114.147-.17.221-.397.521-.743 1.083-1.16 1.587-.323.391-2.857 2.526-3.44 2.94a.842.842 0 01-.574.153 1.115 1.115 0 01-.815-.488l-.462-.794a12.123 12.123 0 00-4.049-3.97 12.133 12.133 0 01-3.13-2.695L1.332 0S.643 1.238.39 2.405c.352.428 1.27 1.49 2.34 2.302C1.58 4.167.73 3.75.06 3.4c-.103.765-.063 1.92.043 2.816.726.317 1.961.806 3.219 1.066-1.006.236-2.11.278-2.961.262.15.554.358 1.119.64 1.688.119.263.25.52.39.77.452.125 2.222.383 3.164.171l-2.51.897a27.776 27.776 0 002.544 2.726c2.031-1.092 2.494-1.241 4.018-2.238-2.467 2.008-3.108 2.828-3.8 3.67l-.483.678c-.25.351-.469.725-.65 1.117-.61 1.31-1.47 4.1-1.47 4.1-.154.486.202.842.674.674 0 0 2.79-.861 4.1-1.47.392-.182.766-.4 1.118-.65l.677-.483c.227-.187.453-.37.701-.586 0 0 1.705 2.02 3.458 3.349l.896-2.511c-.211.942.046 2.712.17 3.163.252.142.509.272.772.392.569.28 1.134.49 1.688.64-.016-.853.026-1.956.261-2.962.26 1.258.75 2.493 1.067 3.219.895.106 2.051.146 2.816.043a73.87 73.87 0 01-1.308-2.67c.811 1.07 1.874 1.988 2.302 2.34h-.001z"></path></svg>

assets/agents/kimi.svg

@@ -0,0 +1 @@
+<svg fill="currentColor" fill-rule="evenodd" height="1em" style="flex:none;line-height:1" viewBox="0 0 24 24" width="1em" xmlns="http://www.w3.org/2000/svg"><title>Kimi</title><path d="M21.846 0a1.923 1.923 0 110 3.846H20.15a.226.226 0 01-.227-.226V1.923C19.923.861 20.784 0 21.846 0z"></path><path d="M11.065 11.199l7.257-7.2c.137-.136.06-.41-.116-.41H14.3a.164.164 0 00-.117.051l-7.82 7.756c-.122.12-.302.013-.302-.179V3.82c0-.127-.083-.23-.185-.23H3.186c-.103 0-.186.103-.186.23V19.77c0 .128.083.23.186.23h2.69c.103 0 .186-.102.186-.23v-3.25c0-.069.025-.135.069-.178l2.424-2.406a.158.158 0 01.205-.023l6.484 4.772a7.677 7.677 0 003.453 1.283c.108.012.2-.095.2-.23v-3.06c0-.117-.07-.212-.164-.227a5.028 5.028 0 01-2.027-.807l-5.613-4.064c-.117-.078-.132-.279-.028-.381z"></path></svg>

assets/agents/mistral.svg

@@ -0,0 +1 @@
+<svg fill="currentColor" fill-rule="evenodd" height="1em" style="flex:none;line-height:1" viewBox="0 0 24 24" width="1em" xmlns="http://www.w3.org/2000/svg"><title>Mistral</title><path clip-rule="evenodd" d="M3.428 3.4h3.429v3.428h3.429v3.429h-.002 3.431V6.828h3.427V3.4h3.43v13.714H24v3.429H13.714v-3.428h-3.428v-3.429h-3.43v3.428h3.43v3.429H0v-3.429h3.428V3.4zm10.286 13.715h3.428v-3.429h-3.427v3.429z"></path></svg>

assets/agents/openai.svg

@@ -0,0 +1 @@
+<svg fill="currentColor" fill-rule="evenodd" height="1em" style="flex:none;line-height:1" viewBox="0 0 24 24" width="1em" xmlns="http://www.w3.org/2000/svg"><title>OpenAI</title><path d="M9.205 8.658v-2.26c0-.19.072-.333.238-.428l4.543-2.616c.619-.357 1.356-.523 2.117-.523 2.854 0 4.662 2.212 4.662 4.566 0 .167 0 .357-.024.547l-4.71-2.759a.797.797 0 00-.856 0l-5.97 3.473zm10.609 8.8V12.06c0-.333-.143-.57-.429-.737l-5.97-3.473 1.95-1.118a.433.433 0 01.476 0l4.543 2.617c1.309.76 2.189 2.378 2.189 3.948 0 1.808-1.07 3.473-2.76 4.163zM7.802 12.703l-1.95-1.142c-.167-.095-.239-.238-.239-.428V5.899c0-2.545 1.95-4.472 4.591-4.472 1 0 1.927.333 2.712.928L8.23 5.067c-.285.166-.428.404-.428.737v6.898zM12 15.128l-2.795-1.57v-3.33L12 8.658l2.795 1.57v3.33L12 15.128zm1.796 7.23c-1 0-1.927-.332-2.712-.927l4.686-2.712c.285-.166.428-.404.428-.737v-6.898l1.974 1.142c.167.095.238.238.238.428v5.233c0 2.545-1.974 4.472-4.614 4.472zm-5.637-5.303l-4.544-2.617c-1.308-.761-2.188-2.378-2.188-3.948A4.482 4.482 0 014.21 6.327v5.423c0 .333.143.571.428.738l5.947 3.449-1.95 1.118a.432.432 0 01-.476 0zm-.262 3.9c-2.688 0-4.662-2.021-4.662-4.519 0-.19.024-.38.047-.57l4.686 2.71c.286.167.571.167.856 0l5.97-3.448v2.26c0 .19-.07.333-.237.428l-4.543 2.616c-.619.357-1.356.523-2.117.523zm5.899 2.83a5.947 5.947 0 005.827-4.756C22.287 18.339 24 15.84 24 13.296c0-1.665-.713-3.282-1.998-4.448.119-.5.19-.999.19-1.498 0-3.401-2.759-5.947-5.946-5.947-.642 0-1.26.095-1.88.31A5.962 5.962 0 0010.205 0a5.947 5.947 0 00-5.827 4.757C1.713 5.447 0 7.945 0 10.49c0 1.666.713 3.283 1.998 4.448-.119.5-.19 1-.19 1.499 0 3.401 2.759 5.946 5.946 5.946.642 0 1.26-.095 1.88-.309a5.96 5.96 0 004.162 1.713z"></path></svg>

assets/agents/qwen.svg

@@ -0,0 +1 @@
+<svg fill="currentColor" fill-rule="evenodd" height="1em" style="flex:none;line-height:1" viewBox="0 0 24 24" width="1em" xmlns="http://www.w3.org/2000/svg"><title>Qwen</title><path d="M12.604 1.34c.393.69.784 1.382 1.174 2.075a.18.18 0 00.157.091h5.552c.174 0 .322.11.446.327l1.454 2.57c.19.337.24.478.024.837-.26.43-.513.864-.76 1.3l-.367.658c-.106.196-.223.28-.04.512l2.652 4.637c.172.301.111.494-.043.77-.437.785-.882 1.564-1.335 2.34-.159.272-.352.375-.68.37-.777-.016-1.552-.01-2.327.016a.099.099 0 00-.081.05 575.097 575.097 0 01-2.705 4.74c-.169.293-.38.363-.725.364-.997.003-2.002.004-3.017.002a.537.537 0 01-.465-.271l-1.335-2.323a.09.09 0 00-.083-.049H4.982c-.285.03-.553-.001-.805-.092l-1.603-2.77a.543.543 0 01-.002-.54l1.207-2.12a.198.198 0 000-.197 550.951 550.951 0 01-1.875-3.272l-.79-1.395c-.16-.31-.173-.496.095-.965.465-.813.927-1.625 1.387-2.436.132-.234.304-.334.584-.335a338.3 338.3 0 012.589-.001.124.124 0 00.107-.063l2.806-4.895a.488.488 0 01.422-.246c.524-.001 1.053 0 1.583-.006L11.704 1c.341-.003.724.032.9.34zm-3.432.403a.06.06 0 00-.052.03L6.254 6.788a.157.157 0 01-.135.078H3.253c-.056 0-.07.025-.041.074l5.81 10.156c.025.042.013.062-.034.063l-2.795.015a.218.218 0 00-.2.116l-1.32 2.31c-.044.078-.021.118.068.118l5.716.008c.046 0 .08.02.104.061l1.403 2.454c.046.081.092.082.139 0l5.006-8.76.783-1.382a.055.055 0 01.096 0l1.424 2.53a.122.122 0 00.107.062l2.763-.02a.04.04 0 00.035-.02.041.041 0 000-.04l-2.9-5.086a.108.108 0 010-.113l.293-.507 1.12-1.977c.024-.041.012-.062-.035-.062H9.2c-.059 0-.073-.026-.043-.077l1.434-2.505a.107.107 0 000-.114L9.225 1.774a.06.06 0 00-.053-.031zm6.29 8.02c.046 0 .058.02.034.06l-.832 1.465-2.613 4.585a.056.056 0 01-.05.029.058.058 0 01-.05-.029L8.498 9.841c-.02-.034-.01-.052.028-.054l.216-.012 6.722-.012z"></path></svg>

assets/agents/tencent.svg

@@ -0,0 +1 @@
+<svg fill="currentColor" fill-rule="evenodd" height="1em" style="flex:none;line-height:1" viewBox="0 0 24 24" width="1em" xmlns="http://www.w3.org/2000/svg"><title>Tencent</title><path d="M9.976 1L24 9.8l-10.587.015L10.723 23H5.489L8.18 9.8H3.244L1 5.4h8.077L9.976 1z"></path></svg>

docs/agents.md

@@ -1,6 +1,6 @@
 # Driving PaperCraft with agents
 
-PaperCraft exposes one set of 70 tools three ways. They all run the same code inside the app, so an agent sees what you see and every call is one undo step.
+PaperCraft exposes one set of 88 tools three ways. They all run the same code inside the app, so an agent sees what you see and every call is one undo step.
 
 | Way | Use it when | Needs the app running |
 |---|---|---|
@@ -108,6 +108,18 @@ write_html {
 EOF
 ```
 
+## Checking only what changed
+
+On a big page a full `lint_design` after every edit repeats the same output, and a `get_node_info` call per layer is slow (about 53 s for 397 layers). Check the change, then check everything once.
+
+* Every write tool result includes `rev`, the document revision after the call. `get_basic_info` reports the current `rev`. Reads never change it.
+* `get_changes {since, page?}` returns `{rev, since, truncated, changes: [{page, ids}]}`: what the edits since `since` touched. `truncated: true` means the log no longer reaches that far back, so do a full pass.
+* `lint_design {changedOnly: true}` lints since this client's last lint; `{since: rev}` lints since a revision you name. A scoped lint checks the touched layers plus their ancestors, descendants, siblings and every layer bound to a changed variable, and reports its coverage in `covered`, for example `{checked: 12, total: 397, since: 40, partial: true}`. Plain `lint_design` is a full pass (`partial: false`). The `overflow` rule flags a layer that extends past its parent or clipping artboard (scroll frames are excluded).
+* `get_bounds {nodeIds?, pageId?, depth?}` returns `columns` `[id, parent, x, y, w, h, absX, absY, clip]` and one row per layer for a subtree in one call (at most 2000 rows; then `truncated` and `continueWith`, the nodeIds for the next call). Use it instead of looping `get_node_info`.
+* Always finish with one full `lint_design` (no arguments) and a screenshot per artboard in each theme mode before reporting. A partial lint speeds up the loop; it does not replace that pass.
+
+In the app, read-only calls no longer draw per-layer outlines or keep the "Working" pill lit for long. The agent workflow, with an example, is in [incremental-checks.md](../skills/papercraft/references/incremental-checks.md).
+
 ## Design-system tools
 
 * Variables: `get_variables` and `set_variables` take collections, groups (`color/brand/primary`), types (`color`, `number`, `string`, `boolean`), `mode`, `alias`, `description` and `hidden`; the old `{"name":"#hex"}` call still works and lands in the first collection. `create_collection` makes a collection with modes, `delete_variables` removes by name (refuses aliased ones unless `force`), `bind_variable` binds or detaches a field of layers (`stroke`, `text-color`, `width`, `height`, `gap`, `padding`, `radius`, `font-size`, `line-height`, `opacity`, `visible`).

docs/design-system.md

@@ -93,6 +93,8 @@ Fill-based sets (Phosphor, Material) follow variables; Lucide is stroke-based an
 | `layer-name` | warning | default names (Frame, Rectangle, Group...) on layers with children |
 | `hard-coded-color` | warning, info | a literal color that equals a variable (warning), or a literal used repeatedly when variables exist (info) |
 
+| `overflow` | error | a layer extending past its artboard or clipping parent (by how many px, on which side), or text taller than its box. Scrolling frames and layers pinned in them are exempt. Never auto-fixed by `fix: true`: resize, move or let the parent grow. `get_bounds` returns every rect in one call |
+
 Instances are skipped (their main component is linted). The rules are conventions, not law: pass `scale` to match your own type scale and ignore `info` items you disagree with. Lint does not judge taste; always look at `get_screenshot` too.
 
 ## Libraries

packaging/windows/package.ps1

@@ -59,7 +59,7 @@ function Get-PeHeader([string] $Path) {
   return @{ Machine = [BitConverter]::ToUInt16($bytes, $pe + 4); Subsystem = [BitConverter]::ToUInt16($bytes, $pe + 0x5C) }
 }
 $Machine = switch ($Arch) { 'x64' { 0x8664 } 'x86' { 0x14C } 'arm64' { 0xAA64 } }
-foreach ($name in @('papercraft.exe', 'papercraft-cli.exe', 'papercraft-mcp.exe')) {
+foreach ($name in @('papercraft.exe', 'papercraft-cli.exe', 'papercraft-mcp.exe', 'papercraft-relay.exe')) {
   $exePath = Join-Path $Bin $name
   if (Test-Path $exePath) {
     $h = Get-PeHeader $exePath
@@ -71,13 +71,13 @@ foreach ($name in @('papercraft.exe', 'papercraft-cli.exe', 'papercraft-mcp.exe'
 $Stage = Join-Path $TargetDir "windows-package\$Arch"
 Remove-Item -Recurse -Force $Stage -ErrorAction SilentlyContinue
 New-Item -ItemType Directory -Force -Path $Stage | Out-Null
-Copy-Item (Join-Path $Bin 'papercraft.exe'), (Join-Path $Bin 'papercraft-cli.exe'), (Join-Path $Bin 'papercraft-mcp.exe') $Stage
+Copy-Item (Join-Path $Bin 'papercraft.exe'), (Join-Path $Bin 'papercraft-cli.exe'), (Join-Path $Bin 'papercraft-mcp.exe'), (Join-Path $Bin 'papercraft-relay.exe') $Stage
 foreach ($f in 'LICENSE-MIT', 'LICENSE-APACHE', 'ATTRIBUTION.md', 'README.md') {
   $p = Join-Path $Root $f
   if (Test-Path $p) { Copy-Item $p $Stage }
 }
 
-& (Join-Path $PSScriptRoot 'sign.ps1') (Join-Path $Stage 'papercraft.exe') (Join-Path $Stage 'papercraft-cli.exe') (Join-Path $Stage 'papercraft-mcp.exe')
+& (Join-Path $PSScriptRoot 'sign.ps1') (Join-Path $Stage 'papercraft.exe') (Join-Path $Stage 'papercraft-cli.exe') (Join-Path $Stage 'papercraft-mcp.exe') (Join-Path $Stage 'papercraft-relay.exe')
 
 # ---- MSI ---------------------------------------------------------------------------------------
 $Msi = Join-Path $Dist "papercraft-$Version-windows-$Arch.msi"
@@ -119,9 +119,22 @@ $CliZip = Join-Path $Dist "papercraft-cli-$Version-windows-$Arch.zip"
 Remove-Item -Force $CliZip -ErrorAction SilentlyContinue
 Compress-Archive -Path $CliPortable -DestinationPath $CliZip
 
+# ---- relay zip ---------------------------------------------------------------------------------
+$RelayPortable = Join-Path $TargetDir "windows-package\papercraft-relay-$Version-windows-$Arch"
+Remove-Item -Recurse -Force $RelayPortable -ErrorAction SilentlyContinue
+New-Item -ItemType Directory -Force -Path $RelayPortable | Out-Null
+Copy-Item (Join-Path $Stage 'papercraft-relay.exe') $RelayPortable
+foreach ($f in 'README.md', 'LICENSE', 'LICENSE-MIT', 'LICENSE-APACHE', 'ATTRIBUTION.md') {
+  $p = Join-Path $Root $f
+  if (Test-Path $p) { Copy-Item $p $RelayPortable }
+}
+$RelayZip = Join-Path $Dist "papercraft-relay-$Version-windows-$Arch.zip"
+Remove-Item -Force $RelayZip -ErrorAction SilentlyContinue
+Compress-Archive -Path $RelayPortable -DestinationPath $RelayZip
+
 # Smoke test
 Invoke-Native 'papercraft-cli --help' { & (Join-Path $Stage 'papercraft-cli.exe') --help | Out-Null }
 
-$artifacts = @($Zip, $CliZip)
+$artifacts = @($Zip, $CliZip, $RelayZip)
 if (Test-Path $Msi) { $artifacts += $Msi }
 Get-Item $artifacts | Format-Table Name, Length

skills/papercraft-critique/SKILL.md

@@ -1,180 +1,110 @@
 ---
 name: papercraft-critique
-description: Pre-emit critique gate for work built in PaperCraft. Five panels (designer, critic, brand, accessibility, copy) score a screen 0-10 against PaperCraft's own objective evidence (lint_design, verify_code, get_screenshot, get_design_spec, get_variables), the weighted composite must reach 8.0, and a failed gate ships the best round instead of the last one. Use when an agent is about to hand over a PaperCraft screen and wants a tool-backed review instead of a self-praise.
+description: Critique finished PaperCraft work the way a design team does - against the person's objective, through independent reviewers (the person's vision, UX heuristics, flow across screens, QA states, visual, accessibility, copy, an end user from the audience), each finding rated 0-4 and backed by tool evidence, then fixed, reported and, when the person approves, kept as a lesson. Use when finish_working_on_nodes offers a critique, when asked to review or critique a design, or before handing over a screen or flow.
 ---
 
 # papercraft-critique
 
-A gate, not a compliment. Before a screen leaves the app it goes through five panels. Each panel is a rubric pass over the same artifact, and each panel may only cite what a PaperCraft tool actually returned. The panels produce five scores, the scores produce one composite, and the composite decides whether the work ships. Mechanics live in the `papercraft` skill, taste in `papercraft-design`; this skill is the gate.
+A critique judges a design against what it is for, not against taste. The tool `critique_design`
+hands you the evidence and the reviewers; this skill is how to run them. Mechanics live in the
+`papercraft` skill, taste in `papercraft-design`. Per-reviewer checklists:
+[personas.md](references/personas.md).
 
-Reference: [panels.md](references/panels.md) (what each panel inspects, which tool backs it, its 0–10 bands).
+## 1. When
 
-## 1. When the gate runs
+* `finish_working_on_nodes` returns `next`: ask the person (`ask_user`) whether to critique now.
+* The person asks "review this", "is it ready?", "critique it".
+* Before handing over a whole screen or flow. Not for one component, an early draft or a copy tweak.
 
-Run it when the resolver (section 2) says on, or when the request is a review of finished work:
+## 2. Objective first
 
-* a whole screen is about to be handed over: landing page, dashboard, sign-in, settings, an onboarding flow, a whiteboard plan;
-* a redesign of an existing screen, after the edits and a clean `lint_design`;
-* the user asked "does this look right?", "review this", "critique it", "is it ready to ship?".
+Critique without an objective is opinion. Before judging, have:
 
-Do not run it for: a single component or icon, an exploratory draft before a direction is chosen (the `papercraft-design` section 0 step), or a one-line copy tweak. The gate costs a lint and a screenshot per round; spend it on work that is finished.
+* **Objective**: what the work must achieve ("a returning customer reorders in two taps").
+* **Audience**: who uses it, in what context (phone, in a hurry, first visit, low vision).
+* **Top tasks**: the two to five things people come to do.
 
-If the gate is on for a run, it must produce a status. Never skip it silently: report `Degraded` with the reason.
+Take them from the brief, the spec, the person's notes (`get_feedback`) and references. Missing?
+Ask with `ask_user` and pass them to `critique_design {objective, audience}`.
 
-## 2. Enable resolver
+## 3. The reviewers
 
-Four levels, highest priority first. Take the first level that gives an explicit answer; "unset" falls through to the next one. A higher level saying *off* is final — a lower level cannot turn the gate back on.
-
-| Order | Level | PaperCraft equivalent | How to read it |
-|---|---|---|---|
-| 1 | Per-task policy | the instruction the agent was given for this run | "run the critique gate before you finish", "review this screen" |
-| 2 | Per-project setting | a toggle stored in the project's own metadata | **not implemented today** — PaperCraft has no project-level flag. Treat this level as unset and fall through to the environment flag or the per-task instruction |
-| 3 | Environment flag | `PAPERCRAFT_CRITIQUE_ENABLED` | `1` / `true` / `always` = on, `0` / `false` / `never` = off, unset = fall through |
-| 4 | Rollout phase | the release phase of the skill itself | off by default: the gate ships disabled until a run or a project turns it on |
-
-So today the gate turns on in one of two ways: the user asks for it in the run's instructions, or `PAPERCRAFT_CRITIQUE_ENABLED=1` is in the environment. A future project setting — stored with the project, not with the user — would sit between those two and win over the environment, so a project could opt in permanently without an env var.
-
-## 3. Order of operations
-
-Objective checks first, subjective panels second. A panel never scores above evidence that contradicts it.
-
-One round is: **evidence → repair → judge → score**.
-
-1. **Snapshot.** Note the `pageId` and the artboard `nodeId` under review and keep them for the whole gate. A page switch between rounds invalidates the evidence.
-2. **Evidence.** `lint_design` (`nodeId`, `pageId`, no `fix` yet) for the raw findings — the payload counts `errors`, `warnings` and `info`, groups them in `byRule`, and lists each issue with its `rule`, `severity`, `node`, `message` and `fix`; `get_screenshot` of the same node (`scale: 2` to read small text); `get_variables` for the token set and the active mode; `get_design_spec` (`nodeId`, `target`) when the design is headed for code. If there is code to check, `verify_code` (`nodeId`, `target`, `code`).
-3. **Repair the hard evidence.** Fix every `lint_design` error and warning and re-run the lint until it is clean; fix every `verify_code` violation until `passed` is true. A panel cannot be scored on a design that still carries a lint error.
-4. **Judge the five panels** on the evidence from steps 2–3 plus the screenshot. Every finding cites the tool result or the screenshot region behind it.
-5. **Score.** Five scores 0–10, then the composite (section 5). Composite ≥ 8.0 → status `Shipped`, stop, `finish_working_on_nodes`.
-6. **Otherwise fix and go again.** Take the findings in composite-impact order, fix them, run round N+1. Maximum 3 rounds.
-7. **Ship the best round** if round 3 is still below the threshold (section 6).
-
-The panels are rubric passes by the agent that holds the tools: one agent, five passes, five different rubrics. A runtime that can spawn subagents may run the panels in parallel, but the evidence vetoes, the composite and the round counter belong to the coordinator.
-
-## 4. Hard evidence vetoes a panel
-
-`lint_design` and `verify_code` are not suggestions. Each finding belongs to one panel, and that panel cannot score above the band its evidence forces.
-
-| Evidence | Rule | Owner panel | Cap |
-|---|---|---|---|
-| `lint_design` error | `contrast` | Accessibility (the Critic reads it too) | 3.9 |
-| `lint_design` warning | `text-size` (under 12px) | Accessibility | 6.9 |
-| `lint_design` warning | `spacing-grid` (off the 4px grid) | Designer | 6.9 |
-| `lint_design` warning | `touch-target` (under 44px) | Accessibility | 6.9 |
-| `lint_design` warning | `layer-name` (default names) | Designer | 6.9 |
-| `lint_design` warning | `hard-coded-color` | Brand | 6.9 |
-| `lint_design` info | `type-scale` | Designer | none — must be listed |
-| `verify_code` error | `missing-text` | Copy | 3.9 |
-| `verify_code` error | `hardcoded-color` | Brand | 3.9 |
-| `verify_code` error | `forbidden-absolute` | Designer | 3.9 |
-| `verify_code` error | `missing-layout` | Designer | 3.9 |
-| `verify_code` warning | `missing-component` | Brand | 6.9 |
-| `verify_code` warning | `spacing-drift` | Designer | 6.9 |
-
-An error caps the owning panel at 3.9 (Blocker band), a warning at 6.9 (Weak band), an `info` item caps nothing but must appear in the panel's notes. `hard-coded-color` arrives in both flavours: a warning when the color equals a variable that exists, an info when it is a literal used several times — the warning caps Brand, the info does not. The cap lifts as soon as the finding is gone; the next round re-scores the panel freely.
-
-A finding is evidence for its owner and a hint for the others: `contrast` also informs the Critic, `spacing-grid` also informs the Brand (was it the token or the layout?), but only the owner is capped.
-
-## 5. The panels and the composite
-
-| Panel | Judges | Weight |
+| Persona | Asks | Method |
 |---|---|---|
-| Designer | layout, composition, hierarchy, spacing rhythm, type scale in use | **0 in v1** — it still scores and its findings still drive the next round |
-| Critic | does it meet the brief; contrast, weight, readability | 0.4 |
-| Brand | token compliance, on-brand color, voice | 0.2 |
-| Accessibility | WCAG, focus rings, semantic structure, alt text | 0.2 |
-| Copy | voice, tone, terseness, error-message quality | 0.2 |
+| `vision` | Does it achieve the objective, as the person imagined it? | Objective, element, effect, why (Connor and Irizarry) |
+| `ux` | Can people use it without help? | Nielsen's 10 heuristics |
+| `flow` | Do the screens make one coherent journey per task? | Task walkthrough across screens, 4 questions per step |
+| `qa` | What breaks with real data and states? | State and edge-case matrix, pass/fail/n.a. |
+| `visual` | Does the eye land right, does it hold together? | Hierarchy, balance, contrast, gestalt, rhythm, tokens |
+| `accessibility` | Can everyone use it? | W3C POUR applied to a design |
+| `copy` | Is every word clear and specific? | Plain language, labels, errors, empty states |
+| `end-user` | Where would this user get stuck or give up? | Persona walkthrough of the top task |
 
-```
-composite = critic x 0.4 + brand x 0.2 + accessibility x 0.2 + copy x 0.2
-```
+`vision` always runs: the person's intent is the yardstick for the others. Pick the rest with
+`personas` (default: all). The person's own words outrank any reviewer.
 
-The weights sum to 1.0, so the composite is also 0–10. The Designer carries weight 0 in v1 on purpose: it is the panel most likely to argue with itself, so its score is reported and its findings are acted on, but it does not move the composite.
+## 4. Independence
 
-Each panel scores 0–10 in half-point steps. The composite is the weighted sum, rounded to two decimals.
+Several reviewers find far more than one, but only when they work apart (Nielsen: one
+evaluator finds about a third of the problems, three to five most of them). Reviewers who
+discuss or debate converge and amplify each other's bias.
 
-| Composite | Verdict |
+* **With subagents**: one subagent per persona, given only its persona brief, the objective and
+  the evidence. No reviewer sees another's findings before rating.
+* **Alone**: one pass per persona, in order, writing that persona's findings before reading the
+  next brief. Do not revise earlier personas' findings during later passes.
+* **You coordinate**: you merge and judge; you never let reviewers argue a finding out.
+
+## 5. Evidence
+
+From `critique_design`: lint (fix every error and warning first), the `flow` graph (arrows between
+screens, `deadEnds`, `unreached`), the lessons. Then `get_screenshot` each artboard at scale 1
+(2 for small text) in every variable mode, `get_bounds` for overflow, `get_feedback` for the
+person's notes. Every finding cites one of these: a tool result or a screenshot region. No
+evidence, no finding.
+
+## 6. A finding
+
+`persona`, `heuristic or check`, `element` (layer name), `seen` (the observation), `effect` (on
+the objective), `evidence`, `severity`, `suggestion`. Keep the observation and the suggestion
+apart: critique is analysis, not brainstorming. Each persona also names at least one thing that
+works and should stay.
+
+Severity (Nielsen), from frequency, impact and persistence:
+
+| | |
 |---|---|
-| ≥ 8.0 | Ship |
-| < 8.0 | Not shippable as is: fix and re-run, or ship the best round after round 3 |
+| 0 | not a problem |
+| 1 | cosmetic: fix if time allows |
+| 2 | minor: low priority |
+| 3 | major: fix before handing over |
+| 4 | catastrophe: blocks the task, fix now |
 
-The band legend is the same for every panel:
+Every broken lesson (`lessons`) is a finding of at least 3.
 
-| Band | Range | Means |
-|---|---|---|
-| Blocker | 0.0–2.9 | Broken: the panel's own evidence is violated. Cannot ship |
-| Poor | 3.0–4.9 | Works against the brief or the brand; ships visible damage |
-| Weak | 5.0–6.9 | Passable but noticeably off; expect a second round |
-| Acceptable | 7.0–7.9 | No blocker, but a reviewer would ask for one change |
-| Good | 8.0–9.4 | Ships as is |
-| Excellent | 9.5–10.0 | Reference quality for this project |
+## 7. Merge, fix, report
 
-What each panel inspects, which tool backs it and where its scores land: [panels.md](references/panels.md).
+1. **Merge** into one list: join duplicates, count the personas that found each (two or more is
+   confirmed), severity is the mean of their independent ratings.
+2. **Fix** every 3 and 4 with the smallest edit (`update_styles`, `set_text_content`), then check
+   that finding again with the same evidence. The work is ready when no 3 or 4 is open and lint is
+   clean. Three fix rounds at most; then hand over with the open findings stated.
+3. **Report** to the person: what works, then findings by severity, each with what was seen, the
+   evidence, the suggestion and whether it was fixed. Phrase open ones as questions about the
+   objective ("How does a first-time user find Reorder from here?"), not verdicts.
 
-## 6. Rounds and the fallback
+## 8. Lessons
 
-* At most **3 rounds** per gate. The counter is per gate, not per panel.
-* A round ends when the composite is computed.
-* Rounds 2 and 3 exist to fix what the panels found. Fix in composite-impact order: the panel with the largest `weight x (10 - score)` first.
-* **`fallbackPolicy: ship_best`.** If the third round is still below 8.0, the status is `Below threshold` and what ships is the best round, not the last one. Best = highest composite; a tie goes to the earlier round (fewer changes). A later round edited the canvas, so put the canvas back into the best round's state before handing over — undo back to it, or re-apply that round's fix list in order.
-* Ship the best round's artifact and report the failing score. `Below threshold` is a status, not a licence to hide the number.
+Ask the person with `ask_user` which findings to remember, one question per finding: for every
+project, for this project, or not. Save only what they approve, with
+`design_lessons {add: {rule, why, scope}}`: the rule is one line written as an instruction
+("Screens keep their device height; the main column scrolls"), `why` is what went wrong. Never
+save a lesson the person did not approve, and never save praise. Lessons come back in
+`get_basic_info` and in the next `critique_design`; `design_lessons {remove: "L3"}` drops one.
 
-## 7. Status vocabulary
+## Sources
 
-Every gate ends with exactly one status.
-
-| Status | When | What ships |
-|---|---|---|
-| `Shipped` | composite ≥ 8.0 | the reviewed artifact, unchanged |
-| `Below threshold` | still < 8.0 after round 3 | the best-scoring round's artifact (`ship_best`), with the score reported |
-| `Timed out` | the gate ran out of its budget (rounds or minutes) before a verdict | the best round so far, with the timeout stated |
-| `Interrupted` | the user or the session stopped the gate mid-run | the last complete round's artifact |
-| `Degraded` | a panel could not be judged properly (section 8) | the artifact, but the verdict is provisional and the reason is named |
-
-`Degraded` outranks `Shipped`: a degraded panel is capped at 6.9, so a degraded run reports `Degraded`, not `Shipped`, even when the composite clears 8.0.
-
-## 8. Degraded reasons
-
-A panel that cannot be judged on real evidence is not scored as if it were fine. It is capped at 6.9, the composite is computed with the cap, and the run reports `Degraded` with the reason and the panel it hit.
-
-| Reason | Cause | Handling |
-|---|---|---|
-| `malformed_block` | a tool returned something the gate could not parse (lint payload in an unexpected shape, a truncated screenshot answer) | retry the tool once; if it still fails, judge the panel on the evidence you do have and name the missing part |
-| `oversize_block` | the evidence was too big to read whole (a screenshot scaled down past legibility, a tree deeper than the context, a lint payload whose `truncated` flag is set) | narrow the scope: screenshot or lint a subtree, split the screen into regions and judge region by region |
-| `adapter_unsupported` | the requested target or format is not supported here (a `verify_code` target the project does not build) | drop that check; the panel falls back to the screenshot plus the design rules |
-| `protocol_version_mismatch` | the MCP server exposes a different tool set than the gate expects (a tool renamed, an argument changed) | stop using the broken tool, finish what you can, report `Degraded`; do not guess the schema |
-| `missing_artifact` | the thing under review is gone (artboard deleted, page switched, stale node id) | re-snapshot with `get_basic_info` and restart the gate; if the artifact is truly gone, report `Degraded` |
-
-Degradation is a report, not an excuse: name the reason, the panel and the evidence you lost.
-
-## 9. What the gate reports
-
-End the gate with the status, the numbers and the findings, in that order:
-
-```
-Critique gate - Sign in (page p1, artboard 3fa9c1:7)
-Round 2 of 3 - composite 8.44 / threshold 8.00 - status Shipped
-Designer 7.5 (weight 0) | Critic 8.5 | Brand 8.5 | Accessibility 8.5 | Copy 8.2
-Composite = 8.5x0.4 + 8.5x0.2 + 8.5x0.2 + 8.2x0.2 = 8.44
-```
-
-Then, per finding: the panel, what was seen, the evidence behind it (tool and finding, or the region of the screenshot), the fix, and whether it was fixed in this round or is still open.
-
-Machine-readable form, when the caller wants JSON:
-
-```json
-{
-  "status": "Shipped",
-  "threshold": 8.0,
-  "composite": 8.44,
-  "round": 2,
-  "rounds": [{ "round": 1, "composite": 7.35 }, { "round": 2, "composite": 8.44 }],
-  "scores": { "designer": 7.5, "critic": 8.5, "brand": 8.5, "accessibility": 8.5, "copy": 8.2 },
-  "weights": { "designer": 0.0, "critic": 0.4, "brand": 0.2, "accessibility": 0.2, "copy": 0.2 },
-  "degraded": [],
-  "findings": [{ "panel": "critic", "evidence": "get_screenshot: headline at 16px over a photo", "severity": "warning", "state": "fixed" }]
-}
-```
-
-## 10. Attribution
-
-The five-panel critique contract — the roles, the weights, the composite, the 8.0 threshold, the three rounds and the `ship_best` fallback — is inspired by OpenDesign's Critique Theater (https://github.com/nexu-io/open-design, Apache-2.0). The contract is re-implemented here in PaperCraft's own words and against PaperCraft's own tools; no text was copied.
+Adam Connor and Aaron Irizarry, *Discussing Design* (objective, element, effect, rationale);
+Nielsen Norman Group: 10 usability heuristics, severity ratings, cognitive walkthroughs, design
+critiques, visual design principles; W3C WAI accessibility principles (POUR); work on panels of
+independent LLM judges (debate amplifies bias, a coordinating judge resists it).

skills/papercraft-critique/references/panels.md

@@ -1,182 +0,0 @@
-# Panel rubrics
-
-Five panels, one artifact, one set of evidence. A panel is a pass with a fixed rubric: what it inspects, which tool output backs it, what it does **not** judge, and the band each finding lands in. The panels share the band legend in [../SKILL.md](../SKILL.md) (Blocker 0–2.9, Poor 3–4.9, Weak 5–6.9, Acceptable 7–7.9, Good 8–9.4, Excellent 9.5–10).
-
-## How to run one panel
-
-1. Read the evidence you were handed: the lint payload, the screenshot, the design spec, the variables, the code result.
-2. Write findings. Every finding cites its evidence — the lint rule and node, the region of the screenshot, the spec's MUST rule, the `verify_code` violation.
-3. Score the panel 0–10. The score is the panel's verdict on the whole screen, not an average of its findings: two serious defects on one region cost more than two trivial ones on two regions, but a screen with three medium defects is not "Good" either.
-4. Apply the caps. Hard evidence caps the owning panel (SKILL.md section 4); degraded evidence caps it at 6.9 (SKILL.md section 8).
-
-Evidence a panel may not use: taste, guesses about a user's preferences, or a claim about something no tool showed. When a panel wants to judge what no tool exposes — whether an image is meaningful, whether a flow makes sense — it raises the question as an open item instead of scoring it as a defect.
-
-Tool arguments used below are the current names. Note that `lint_design`'s `scale` is the list of allowed font sizes, not a zoom; the zoom argument of `get_screenshot` is `scale: 1 | 2`.
-
----
-
-## Designer — weight 0 in v1
-
-**Judges:** layout and composition, alignment, spacing rhythm, hierarchy, the type scale in use, how things are grouped, screen states, overflow, density.
-
-**Evidence it uses**
-
-| Tool | How |
-|---|---|
-| `get_screenshot` (`nodeId`, `scale: 2`) | the primary evidence: alignment, edges, rhythm, hierarchy, clipping, empty areas |
-| `lint_design` (`nodeId`, `pageId`) | `spacing-grid`, `type-scale`, `layer-name` findings |
-| `get_design_spec` (`nodeId`, `target`) | flow and sizing (`fixed`, `hug`, `fill`), grouping, where the spacing rules were broken |
-| `get_tree_summary` (`nodeId`, `depth`) | structure depth, unnamed frames, accidental nesting |
-
-**Does not judge:** contrast and WCAG (Accessibility), token and palette choices (Brand), wording (Copy).
-
-**Bands**
-
-| Band | What the Designer saw |
-|---|---|
-| 0.0–2.9 | Broken layout: frames overlap, content sits outside the artboard, text is clipped, the screen reads as a pile |
-| 3.0–4.9 | Poor composition: everything on the default grid, equal weight everywhere, no grouping, ragged edges |
-| 5.0–6.9 | Weak: spacing off the 4px grid in places, sizes off the type scale, mixed grouping (space *and* containers everywhere), a state missing |
-| 7.0–7.9 | Acceptable: coherent, but one region is crowded or one rhythm is broken |
-| 8.0–9.4 | Good: clear hierarchy, aligned to a few strong edges, consistent rhythm, states present |
-| 9.5–10.0 | Excellent: deliberate rhythm, one memorable idea, whitespace used as a material |
-
-**Fixes that move the score:** snap spacing to the 4/8 scale (`lint_design` with `fix: true`), pull one size step per level, give each group either a container or space — not both, align to one left edge, add the missing empty/loading/error state.
-
----
-
-## Critic — weight 0.4
-
-**Judges:** whether the screen meets the brief (the request this run is executing), whether visual weight matches the priority, readability as a human experiences it, and whether the real cases are covered.
-
-**Evidence it uses**
-
-| Tool | How |
-|---|---|
-| the brief | the user's request and the `papercraft-design` section 0 direction, read against the screenshot |
-| `get_screenshot` (`nodeId`, `scale: 2`) | one primary action, reading order, what is above the fold, legibility by eye |
-| `lint_design` (`nodeId`, `pageId`) | `contrast`, `text-size`, `type-scale` findings as the objective part of readability |
-| `get_design_spec` (`nodeId`, `target`) | what the screen actually contains, against what was asked for |
-| `verify_code` (`nodeId`, `target`, `code`) | when the design is code-bound: whether the implementation kept the intent |
-
-**Does not judge:** which palette (Brand), line-level wording (Copy), implementation details beyond fidelity to the design.
-
-**Bands**
-
-| Band | What the Critic saw |
-|---|---|
-| 0.0–2.9 | Misses the brief: wrong screen or wrong content, the primary action is absent or ambiguous |
-| 3.0–4.9 | Fights the brief: right elements, wrong order or emphasis, or hard to read (contrast errors, tiny type) |
-| 5.0–6.9 | Weak: it does the job, but the weight is flat and something important sits below the fold or is buried |
-| 7.0–7.9 | Acceptable: meets the brief; one area stays unclear or the priority is not obvious |
-| 8.0–9.4 | Good: the brief is met, the primary action is obvious, readability is solid |
-| 9.5–10.0 | Excellent: unmistakable hierarchy, the screen reads in one pass, the edge cases are covered |
-
-**Fixes that move the score:** make one thing clearly primary and quiet the rest, move the important content up, cut a competing element, re-read the brief line by line and check each requirement against the screenshot.
-
----
-
-## Brand — weight 0.2
-
-**Judges:** token compliance, on-brand color, semantic color use, mode coverage, product voice consistency, component reuse.
-
-**Evidence it uses**
-
-| Tool | How |
-|---|---|
-| `get_variables` (`pageId`, `format`) | the variables, tokens, active `mode` and available `modes` — the reference palette |
-| `lint_design` (`nodeId`, `pageId`) | `hard-coded-color` findings |
-| `get_computed_styles` (`nodeIds`) / `find_nodes` (`filters`) | fills and text colors that are not following a variable |
-| `get_design_spec` (`nodeId`, `target`) | which tokens the design already binds |
-| `get_components` / `get_tree_summary` | components built and instanced versus copies |
-| `verify_code` (`nodeId`, `target`, `code`) | `hardcoded-color`, `missing-component` in the implementation |
-
-**Does not judge:** composition (Designer), wording line by line (Copy), whether the layout serves the brief (Critic).
-
-**Bands**
-
-| Band | What the Brand saw |
-|---|---|
-| 0.0–2.9 | Off-system: hard-coded colors where tokens belong, a foreign palette, no modes |
-| 3.0–4.9 | Off-brand: technically on-token but the accent is used everywhere, or the screens read as different products |
-| 5.0–6.9 | Weak: one or two hard-coded colors, the accent covers much of the screen, components copied instead of instanced |
-| 7.0–7.9 | Acceptable: on-system, with one token or component inconsistency |
-| 8.0–9.4 | Good: every color is a token, the accent marks the primary action only, modes defined and checked, components reused |
-| 9.5–10.0 | Excellent: coherent across screens and modes, the palette carries meaning |
-
-**Fixes that move the score:** `lint_design` with `fix: true` relinks hard-coded colors that match a variable, add the missing variable before using the color, cut accent back to the primary action, build the repeated part once and place instances, check the second mode with `set_variable_mode`.
-
----
-
-## Accessibility — weight 0.2
-
-**Judges:** WCAG contrast, the text-size floor, touch-target size, focus and hover states, semantic structure, alt text, and signalling that does not rely on color alone.
-
-**Evidence it uses**
-
-| Tool | How |
-|---|---|
-| `lint_design` (`nodeId`, `pageId`) | `contrast`, `text-size`, `touch-target` findings |
-| `get_screenshot` (`nodeId`, `scale: 2`) | whether a visible focus or hover state was designed at all, and how the error state reads |
-| `get_design_spec` (`nodeId`, `target`) | which text is a title, how the screen is grouped, what each control is |
-| `find_nodes` (`textValue`, `filters`) | image and icon nodes, unlabeled icon buttons |
-| `get_tree_summary` (`nodeId`, `depth`) | semantic structure: heading levels, groups, control order |
-
-**Does not judge:** visual taste (Designer), palette taste (Brand), voice (Copy).
-
-**Bands**
-
-| Band | What Accessibility saw |
-|---|---|
-| 0.0–2.9 | Fails WCAG: contrast errors, text under 12px, targets under 44px, meaning carried by color alone |
-| 3.0–4.9 | Poor: borderline contrast, unlabeled controls, an error state that is red text and nothing else |
-| 5.0–6.9 | Weak: passes on the desktop artboard but fails on the mobile one, one image without alt text |
-| 7.0–7.9 | Acceptable: compliant baseline, one gap (no visible focus state, one icon-only button) |
-| 8.0–9.4 | Good: WCAG clean, targets pass, semantics and labels present, focus and hover states designed |
-| 9.5–10.0 | Excellent: every state specified, sensible keyboard order, no meaning by color alone |
-
-**Fixes that move the score:** fix the color, not the check, until `lint_design` reports no contrast error, name interactive layers `Button…` / `Tab /…` so the target rule can see them and grow them to 44px, pair every error color with an icon or a word, design the focus and hover variants as components, give every image an alt text.
-
-PaperCraft has no focus-ring or alt-text checker: judge those from the design itself (a `Button / Focused` variant, alt text in the spec) and report what is missing as a gap, not as a tool finding.
-
----
-
-## Copy — weight 0.2
-
-**Judges:** voice and tone against the product's voice, terseness, labels and microcopy, error-message quality, empty states, placeholders versus labels, the absence of filler.
-
-**Evidence it uses**
-
-| Tool | How |
-|---|---|
-| `get_design_spec` (`nodeId`, `target`) | the authoritative copy: every text node's content, in order |
-| `get_screenshot` (`nodeId`, `scale: 2`) | how the copy reads in context: line breaks, truncation, all-caps abuse |
-| `find_nodes` (`textValue`) | repeated strings, leftover placeholders, "Lorem ipsum", inconsistent labels for the same action |
-| `verify_code` (`nodeId`, `target`, `code`) | `missing-text` — copy that was lost between the design and the code |
-
-**Does not judge:** typography and layout (Designer), color (Brand), whether the screen meets the brief (Critic).
-
-**Bands**
-
-| Band | What Copy saw |
-|---|---|
-| 0.0–2.9 | Wrong: placeholder text, lorem ipsum, or copy that contradicts the brief |
-| 3.0–4.9 | Poor: filler adjectives, two voices on one screen, errors that blame the user |
-| 5.0–6.9 | Weak: wordy, mixed formality, vague labels ("Submit" where "Save changes" is meant) |
-| 7.0–7.9 | Acceptable: clear but plain; one error message says only "Error" |
-| 8.0–9.4 | Good: terse, one voice, every action labeled with a verb, errors say what happened and what to do next |
-| 9.5–10.0 | Excellent: reads like a product that shipped, not like a mockup |
-
-**Fixes that move the score:** cut every word that does not inform, give each action a verb label ("Save changes", not "OK"), write errors as *what happened + what to do next*, fill empty states with an explanation and the next action, replace placeholder copy with real content, keep one formality level per screen.
-
-PaperCraft has no spell-checker or copy linter: the copy panel reads the spec and the screenshot, and it flags what a human reviewer would flag — it does not invent grammar rules.
-
----
-
-## Scoring discipline
-
-* Half-point steps only: 7.5, 8.0, 8.5. Never 8.37.
-* The score is a verdict on the screen, not an average of findings.
-* A panel that finds nothing wrong and cites no evidence scores 7.0–7.9, not 10. A 10 means the screen is a reference for the next one.
-* Caps bind: hard evidence (SKILL.md section 4) and degraded evidence (section 8) are applied after the verdict, never negotiated with.
-* No panel may raise another panel's score. If the Critic likes the hierarchy, that stays a Designer finding.

skills/papercraft-critique/references/personas.md

@@ -0,0 +1,110 @@
+# Reviewer checklists
+
+Each reviewer works from its own list, alone, and cites evidence for every finding. Mark each
+item pass, fail or n/a; a state or screen that was never designed is an open question, not a pass.
+
+## vision: the person's vision
+
+For each key element on each screen, four questions (Connor and Irizarry):
+
+1. **Objective**: which part of the objective is this element for?
+2. **Element**: which elements serve it?
+3. **Effect**: do they achieve it, for this audience?
+4. **Why** or why not?
+
+Also: everything the brief, references and feedback notes asked for is there; nothing contradicts
+an open or resolved note (`get_feedback`); the tone matches the references. Unknown product facts
+are questions for the person, never guesses.
+
+## ux: usability heuristics (Nielsen)
+
+1. Visibility of system status: progress, saving, selection shown at once.
+2. Match with the real world: the users' words and order, not the system's.
+3. User control and freedom: a marked exit, undo, cancel.
+4. Consistency and standards: one word and one look per thing, platform conventions.
+5. Error prevention: risky actions confirmed, impossible choices removed.
+6. Recognition rather than recall: options visible, no remembering across screens.
+7. Flexibility and efficiency: shortcuts for experts that novices need not see.
+8. Aesthetic and minimalist design: nothing that competes with what matters.
+9. Recognize, diagnose, recover from errors: plain language, the problem, the fix.
+10. Help and documentation: needed rarely, and then where the task is.
+
+## flow: coherent journeys
+
+Walk each top task across screens (the `flow` graph when arrows connect screens, else the screen
+order and names; ask the person when the intended order is unclear). At each step, the four
+walkthrough questions: will they try to do this, will they notice the control, will they connect
+it to their goal, will they see progress afterwards?
+
+* Every task has an entry point (including first run and empty state) and a clear end
+  (success screen or state).
+* Every screen has a way forward and a way back or out; no dead ends (`deadEnds`), no screen
+  nothing leads to (`unreached`) unless it is an entry.
+* Each action that can fail has its error state; each destructive one a confirmation and undo.
+* Navigation, back and primary actions sit in the same place with the same labels on every screen.
+* What the user entered or chose shows on the following screens (the cart count, the name typed).
+* Steps a user must remember between screens are shown instead (recognition over recall).
+* The number of steps fits the objective ("two taps" means two).
+
+## qa: states and edge cases
+
+Per screen and component, pass, fail or n/a:
+
+* States: default, hover, focus, pressed, disabled, selected, loading, empty, error, success.
+* Content: the longest realistic text and names, minimum content, zero, one and many items,
+  missing images and avatars, large numbers, special characters.
+* Modes and sizes: every variable mode (screenshot each); the narrow and wide screen sizes when the
+  design has them.
+* Layout: nothing overflows or clips (`get_bounds`, lint `overflow`), screens keep their device
+  height and scroll inside, fixed bars stay fixed.
+* Consistency: repeated pieces are instances of the same component (lint `not-an-instance`).
+
+## visual
+
+* One focal point per screen; the primary action is the most prominent control.
+* Scale and hierarchy: size, weight and colour follow importance.
+* Balance and alignment: shared edges, a steady grid.
+* Gestalt proximity: related items closer together than unrelated ones.
+* Rhythm: spacing from the 4px scale, the same gaps for the same relationships.
+* Type: sizes on the scale, at most three levels per screen.
+* Tokens: every colour a variable, consistent radii, components reused.
+
+## accessibility (W3C POUR, for a design)
+
+**Perceivable**
+* Text contrast 4.5:1, 3:1 for large text (18px, or 14px bold) and for control borders and icons.
+* Colour is never the only signal (errors also have an icon or text; links are underlined or bold).
+* Text is real text, not pictures of text; icons that act have a label or tooltip.
+* The layout holds at 320px wide and with text at 200% (a narrow artboard shows it).
+
+**Operable**
+* Touch targets 44px (24px minimum with spacing).
+* A visible focus state is designed for every interactive component.
+* Headings, a page title and a visible current location (active nav item).
+* Destructive actions confirmed or undoable; every gesture has a button alternative.
+* Nothing flashes; motion can be reduced.
+
+**Understandable**
+* Fields keep a visible label (a placeholder alone disappears).
+* Errors say what went wrong and how to fix it, next to the field.
+* Navigation and labels are the same across screens.
+* Plain language; abbreviations explained.
+
+**Robust**
+* Controls are named for their role (layer names, code links to real components), so the code
+  hand-off keeps them buttons and inputs, not divs.
+
+## copy
+
+* The users' words, not internal jargon; verbs on buttons ("Save changes", not "OK").
+* No placeholder or lorem text, no "Item 1".
+* Errors: what happened and what to do. Empty states: what this is and the first action.
+* Neutral wording about people whose gender is unknown (their name, or they).
+* Consistent terms: one word per concept across all screens.
+
+## end-user: a walkthrough as the audience
+
+Take the `audience` (else ask). Write as that person, in the first person, for each top task:
+what I see first, what I think it does, what I try, where I hesitate, and the first point where I
+would give up. One persona per run; launch another critique with a different `audience` for a
+second user type.

skills/papercraft-design/SKILL.md

@@ -33,7 +33,7 @@ Allowed spacing values: **4, 8, 12, 16, 24, 32, 48, 64** (and 96 for page sectio
 ## 2. Tokens first (variables)
 
 * All colors are variables (`var(--name)`), named by role: `bg`, `surface`, `border`, `text`, `text-muted`, `accent`, `on-accent`, `success`, `warning`, `danger`. Two to three surface levels at most (`bg` < `surface` < `surface-2`).
-* Define at least two modes if the product may be dark or light (`set_variables` with `mode`), and check both: lint contrast in each mode after `set_variable_mode`.
+* Define at least two modes if the product may be dark or light (`set_variables` with `mode`), and check both: lint contrast in each mode after `set_variable_mode`, or look with `get_screenshot {mode}` without switching. Themes are modes, never copies: one artboard per screen, never a light and a dark duplicate (`lint_design` flags them as `theme-copy`).
 * Semantic colors carry meaning only: red means error or destructive, green means success. Do not use them decoratively.
 * If a color you need is not a variable, add the variable, then use it. `lint_design` reports hard-coded colors that equal a variable.
 * Spacing, radius and type sizes are number variables (`space/md`, `radius/sm`, `font/body`): define them once, in a collection of their own, and bind fields with `bind_variable`. Keep the values on the lists in this skill. Group names with `/` and alias semantic names to base ones (`color/button/bg` to `color/brand/primary`).
@@ -105,7 +105,7 @@ Run it before `finish_working_on_nodes`:
 1. Direction written down; the screen has one memorable idea and one primary action.
 2. Every color is a variable; both modes checked if there are two.
 3. Spacing only 4, 8, 12, 16, 24, 32, 48, 64, 96; type only from the scale; radii from one family.
-4. `lint_design` has zero errors and zero warnings, and the `info` items were considered.
+4. A full `lint_design` (no arguments) has zero errors and zero warnings, and the `info` items were considered. Between edits, lint only what changed: see `papercraft/references/incremental-checks.md`.
 5. Screenshot at scale 2 looked at: hierarchy, alignment, wrapping, clipping, empty areas, contrast by eye.
 6. Interactive things at least 44px on touch and named `Button…` / `Tab /…`.
 7. Repeated parts are components; states exist for every interactive component and for empty, loading and error screens.

skills/papercraft/SKILL.md

@@ -17,7 +17,7 @@ papercraft-cli call get_basic_info      # fails with exit 1 if the app is not ru
 
 * **Check the project is the right one.** `get_basic_info` returns `fileName` and `path`. Build only in a project that belongs to the work (a NotesCraft design file is for NotesCraft screens, not for redesigning PaperCraft). For a different product: `create_file {name}`, then `open_file {fileId}`, and say so. `open_file` swaps the project the user is looking at, so tell them. Pass `fileId` on later calls when more than one project is in play.
 * Not running: ask the user to start PaperCraft and open a project (or `create_file` then `open_file`). `PAPERCRAFT_MCP_PORT` must match if the port was changed. Do not try to launch the GUI yourself unless asked.
-* Read `get_basic_info` (pages, artboards, sizes, fonts), then `get_selection` (what the user is looking at) and `get_variables` and `get_components`. Reuse what exists before creating anything.
+* Read `get_basic_info` (pages, artboards, sizes, fonts, and `lessons`: the person's rules from past critiques; follow every one), then `get_selection` (what the user is looking at) and `get_variables` and `get_components`. Reuse what exists before creating anything.
 * `pageId` defaults to the page the user is viewing, which can change between calls: pass it explicitly. Node ids look like `3fa9c1:14`; never show them to the user.
 * App closed (server, CI)? `papercraft-cli call --offline ... --project <name>` runs the same tools on the project store and saves after every editing call; `papercraft-cli shell` keeps one session for many calls and reads scripts from stdin. It is refused while the app has that project open. See `docs/agents.md`.
 * With MCP tools you do not need the CLI; with a shell, `papercraft-cli list` and `papercraft-cli schema <tool>` give the schemas on demand. Pass big JSON on stdin: `... | papercraft-cli call write_html -`.
@@ -33,8 +33,10 @@ papercraft-cli call get_basic_info      # fails with exit 1 if the app is not ru
 3. **Build in small steps.** `create_artboard`, then one `write_html` per visual group (header, card, row) so the user sees progress. Name every layer with `layer-name`.
 4. **Look.** `get_screenshot` of the artboard after each group or two. Scale 2 to read small text. Read it as a designer: hierarchy, alignment, spacing rhythm, clipping, wrapping.
 5. **Lint.** `lint_design` on the artboard. Fix every error and warning; consider the `info` items. Run it again until errors and warnings are zero.
+   Between edits, lint only what changed: keep the `rev` each write returns and run `lint_design {changedOnly: true}` (or `{since: rev}`). `get_changes {since}` shows what an edit touched; `get_bounds` measures a whole subtree in one call instead of looping `get_node_info`.
+   Always finish with one full `lint_design` (no `since` or `changedOnly`: `covered.partial` is false) and a screenshot per artboard in each theme mode before reporting. Details: [incremental-checks.md](references/incremental-checks.md).
 6. **Fix with the smallest edit.** `update_styles` and `set_text_content` on the existing nodes, not a rewrite. Rewrite a group with `write_html` mode `replace` only when its structure is wrong.
-7. **Finish.** `finish_working_on_nodes` (saves). Tell the user what you made in a sentence or two, with artboard names, not ids.
+7. **Finish.** `finish_working_on_nodes` (saves). Tell the user what you made in a sentence or two, with artboard names, not ids. When its result has `next`, offer a critique with `ask_user`; on yes run `critique_design` and follow its steps (the `papercraft-critique` skill has the full gate). Keep a finding as a lesson (`design_lessons {add}`) only when the person approved it.
 
 Lint passes are necessary, not sufficient: contrast and grids say nothing about composition. The screenshot is the real test.
 
@@ -44,8 +46,12 @@ Lessons from redesigning a 3-page, 130-screen project with up to six agents at o
 
 * **Split by section, not by page.** Give each agent named sections (frame ids) and forbid the rest. New sections go below the current lowest one; re-read positions right before creating, since another agent may have just added one.
 * **Section layout**: a section frame holds a title and rows of screen slots (a route label above a fixed-size screen). Keep 640 px between screens and rows and 1600 px between sections, so notes fit beside screens. Stack sections in one column.
+* **See what the others changed** before building on their work: `get_changes {since: <your last rev>, exclude: "self"}` lists layers by the client that changed them. `truncated: true` means re-read everything.
+* **Name yourself and fence your area.** With the CLI pass `--as <name>` (or `PAPERCRAFT_AGENT`), so writes, conflicts and claims carry your name. `claim_nodes {ids, note}` the sections you will rewrite; others' writes there are refused until you `finish_working_on_nodes` or `release_claims`. A denial names the holder: work elsewhere, never wait in a loop.
+* **Writes report conflicts.** A result with a `swarm` block lists layers another agent changed since you last looked: read them with `get_changes` before going on. Pass `ifRev: <your last rev>` to have the write refused instead (`"error": "conflict"`).
+* **Undo takes back only your own steps** (`undo`, scope `mine`); it is refused with `undo_blocked` when someone changed the same layers since. Fix forward then; `scope: "page"` undoes whoever was last.
 * **Recreate, then delete.** Build the new screen next to the old one, finish it, then delete the old one, and record the deleted ids and names in the report. A cleanup agent once deleted buttons and lost icons by editing in place.
-* **Reuse the design system across pages**: `create_instance` / `swap_instance` / `<x-paper-instance>` take a main from any page and stay linked. Never `import_components` to use a component: that copies mains onto the page, and instances made from the copies stop following the design system. `lint_design` flags hand-made look-alikes as `not-an-instance` (with the component key to use).
+* **Reuse the design system across pages**: `create_instance` / `swap_instance` / `<x-paper-instance>` take a main from any page and stay linked. Never `import_components` to use a component: that copies mains onto the page, and instances made from the copies stop following the design system. `lint_design` flags hand-made look-alikes as `not-an-instance` (a different icon is a different component); fix with `write_html` mode replace and the `<x-paper-instance>` it names.
 * **QA pass after a build** (screen by screen at scale 1, one call at a time): text layers with stale fixed widths clip labels ("In prog", "New sess"): set `width: fit-content`. Sidebars and panels fixed at 900 px stop short on taller screens: make them fill the height and let the screen hug with a 900 px minimum. Tags and chips overflowing their box, cards overlapping buttons, footers not pinned, leftover `Text` / `Frame` names, gendered copy about people whose gender is unknown (use their name or neutral wording).
 * **Report per agent** in `specs/<feature>/<agent>-report.md`: what changed (ids), why (playbook rule ids from `playbook search`), open questions. Unknown product facts are written as questions for the team, never invented.
 
@@ -89,7 +95,7 @@ For a screen with dozens of parts, drive the CLI from a short Python helper (`ca
 ```
 
 Artboards: mobile 390×844, tablet 768×1024, desktop 1440×900, large desktop 2560×1440 (a 1440p display; ask which the user uses and design that first). A narrow window (1280×800) is its own artboard: collapse the sidebar to an icon rail, make secondary actions icon-only with a tooltip, keep one labelled primary action.
-Dot-grid canvas (no pattern fill exists): one `<svg>` with a single path of tiny round-capped dashes, absolute at 0,0 inside the canvas frame: `<svg style="position:absolute;left:0px;top:0px" width="W" height="H" viewBox="0 0 W H"><path d="M16 16h0.01M48 16h0.01..." stroke="var(--surface-2)" stroke-width="2.5" stroke-linecap="round" fill="none"/></svg>`. One vector layer, about 3,000 dots at a 32px step. Its colour is frozen at write time. Create with `height:"fit-content"` when the content decides the height. Replace margin with `gap` and `padding`.
+Dot-grid canvas (no pattern fill exists): one `<svg>` with a single path of tiny round-capped dashes, absolute at 0,0 inside the canvas frame: `<svg style="position:absolute;left:0px;top:0px" width="W" height="H" viewBox="0 0 W H"><path d="M16 16h0.01M48 16h0.01..." stroke="var(--surface-2)" stroke-width="2.5" stroke-linecap="round" fill="none"/></svg>`. One vector layer, about 3,000 dots at a 32px step. Its colour is frozen at write time. A screen keeps its device's size; at a device width (390, 1440...) `height:"fit-content"` becomes the device height. Content taller than the screen scrolls by itself: the main column under a fixed sidebar and header, else the screen (write_html says which). Pass `overflow:"visible"` to let a board grow (a landing page drawn in full). Replace margin with `gap` and `padding`.
 
 Full flows: [recipes.md](references/recipes.md).
 
@@ -100,9 +106,11 @@ Full flows: [recipes.md](references/recipes.md).
 | Know the project, pages, artboards | `get_basic_info`, `get_tree_summary`, `get_children` |
 | Know what is selected | `get_selection` |
 | Inspect one node | `get_node_info`, `get_computed_styles`, `get_jsx` |
+| Sizes and positions of a subtree | `get_bounds` (one call, `columns` + `rows`; `continueWith` when `truncated`) |
+| What changed since a revision | `get_changes {since}` (`exclude: "self"` for other agents' edits) |
 | Find nodes by text or style | `find_nodes` (text contains the phrase, any case, every page) |
 | Read all copy in a subtree | `get_tree_summary {nodeId, fullText: true}` (depth counts from the node: rows under a "Screens" frame need depth 3) |
-| See it | `get_screenshot` (`nodeId`, `scale` 1 or 2, `annotations: true` to include notes) |
+| See it | `get_screenshot` (`nodeId`, `scale` 1 or 2, `annotations: true` to include notes, `mode` to preview a theme without switching) |
 | Show the user something | `set_viewport` (page switch, fit, zoom) |
 | Document rules on the design | `annotate`, `get_annotation_template`, `get_annotations`, `update_annotation`, `delete_annotations` |
 | New screen | `create_artboard` (`width` and `height` required) |
@@ -111,17 +119,23 @@ Full flows: [recipes.md](references/recipes.md).
 | Whiteboard shapes, sticky notes, arrows | `create_shape` |
 | Copy, move, delete | `duplicate_nodes`, `move_nodes`, `delete_nodes` |
 | Tokens | `get_variables` (`format` css, json or tailwind), `set_variables` (`collection`, `type`, `mode`, `alias`), `create_collection`, `delete_variables`, `set_variable_mode`, `bind_variable` |
-| Reuse | `create_component`, `create_instance`, `swap_instance`, `get_components`, `<x-paper-instance>` |
+| Reuse | `create_component`, `create_instance`, `swap_instance` (also a nested badge inside a row instance: a swap that survives main edits), `get_components`, `<x-paper-instance>` |
+| Component properties | One component with properties instead of one per state: `set_component_props` (`text`, `bool`, `icon`, `enum` options in the overrides format; templates `text`, `active` for tab bars and navs, `status` with [{value, color}]), then `set_instance_props {nodeIds, values}` or `<x-paper-instance component="Badge" props='{"Status":"Rejeitada"}'/>`; `get_components` lists them |
+| Merge per-state components | `merge_variants {componentIds, name}` turns `Tab bar / Hoje`, `Tab bar / Lojas`... into one `Tab bar` with an enum, moves every instance and deletes the emptied variants |
+| Prototype | `set_prototype_links {links:[{nodeId, to}]}`: back arrows, rows and tabs go to their screens in Present mode |
+| Screens | Fixed size (390x844, 1440x900...); content longer than the screen scrolls by itself (the main column under a fixed sidebar and header, else the screen), or set `overflow: auto` on the frame that should scroll; it keeps its size and the overflow scrolls on the canvas and in Present (inspector: Scroll overflow; page: Screens scroll) |
+| Project | `rename_file {name}` (open project stays open), `move_nodes {toPageId}` keeps instances linked and notes attached |
 | Shared libraries | `publish_library`, `list_libraries`, `enable_library`, `update_library`, `disable_library` |
 | Icons | `search_icons`, `<x-paper-icon name="set:name">`; CLI: `papercraft-cli icons add\|list\|search` |
-| Design in a library's look, hand off its code | `apply_ui_kit` (shadcn, antd, reactbits, egui), then `<x-paper-instance>` of its components; `set_code_link` for a component of your own; `get_jsx` / `get_design_spec` then write `<Button variant="outline">` instead of divs |
+| Design in a library's look, hand off its code | `apply_ui_kit` (shadcn, mui, mantine, bootstrap, chakra: ~48 components and 5 screen layouts each, re-colour through their variables; antd, reactbits, egui), then `<x-paper-instance>` of its components; `set_code_link` for a component of your own; `get_jsx` / `get_design_spec` then write `<Button variant="outline">` instead of divs |
 | Avatars, more icons, photos, flags, QR | `<x-plugin use="avataaars\|dicebear\|iconify\|picsum\|flags\|qr" …/>` inside `write_html` (plugins the user turned on) |
 | References and art | `fetch_reference_images`, `zoom_image`, `generate_image` (when the user turned image generation on) |
 | Ask the user | `ask_user` (clickable answers; end your turn after it) |
+| Hand work to the helper agent | `delegate` (`role` qa, read or build, a self-contained `task`; only when Settings, Chat, Helper is set) |
 | Design rules (design-playbook) | `design_rules` (`query` or `rule` id; needs the `playbook` CLI; cite ids in the report) |
 | Report a PaperCraft problem | `report_issue` (a draft the user sends; synthetic repro only) |
-| Check quality | `lint_design` |
-| Export | `export` (PNG, SVG, PDF to files), `export_combined_pdf` |
+| Check quality | `lint_design` (`changedOnly: true` or `since` between edits, a full pass at the end; `overflow` flags layers past their artboard or clipping parent) |
+| Export | `export` (PNG, SVG, PDF to files), `export_combined_pdf`, `export_presentation` (a client deck: cover, contents, a slide per screen) |
 | Point at things for the user | `select_nodes` (`zoom: true`) |
 | Take back | `undo`, `redo` |
 | Save | `finish_working_on_nodes` |
@@ -154,7 +168,7 @@ Full flows: [recipes.md](references/recipes.md).
 | `papercraft-cli` exits 1, "isn't running" | The app is closed, no project is open, or the port differs. Start it and open a project; check `PAPERCRAFT_MCP_PORT`. |
 | Call fails with an unknown node id | The id is from another page or was deleted. Re-read with `get_children`; pass `pageId`. |
 | `write_html` reports `ignoredStyles` | You used a CSS property that has no equivalent (`margin`, `box-shadow`, `transform`...). Replace it, see [html-subset.md](references/html-subset.md). |
-| Content is cut off | The artboard height is fixed. `update_styles` with `height: "fit-content"` or a larger number. |
+| Content is cut off | A frame inside the screen clips it (`overflow: hidden`, or a fixed height under a hugging parent). Give the column that should scroll `overflow: auto`; for a board that should grow, `overflow: "visible"` and `height: "fit-content"`. |
 | A color did not change with the theme | It was written as hex, or it is a stroke or gradient. Use `var(--name)` on fills and text; strokes need `update_styles` after a mode switch. |
 | `create_instance` fails | Wrong `componentId` / `componentKey` (read `get_components`). Mains on other pages and enabled libraries work; no import needed. |
 | A page is full of copied components at y=0 | Something imported mains onto the page (`import_components`, or old `write_html` builds). Swap their instances to the design-system mains (`swap_instance {componentKey}`), check a screenshot, then delete the unused copies. |

skills/papercraft/references/compact-workflow.md

@@ -37,6 +37,6 @@ How to keep designs small, keep design and code in step, and spend few tokens do
 
 ## Sharing and several agents
 
-* Several agents may work on one open project through one MCP server: calls run one at a time, each is one undo step, so they do not corrupt each other. Give each agent its own page or artboard prefix and say so in the brief, so they do not restyle each other's nodes.
+* Several agents may work on one open project through one MCP server: calls run one at a time, each is one undo step, so they do not corrupt each other. Give each agent its own page or artboard prefix and say so in the brief, so they do not restyle each other's nodes. Each agent names itself (`papercraft-cli --as <name>`), claims what it rewrites (`claim_nodes`), reads the conflicts its writes report, and undoes only its own steps.
 * Several people on a shared project: pages sync as files and are merged when both sides changed the same page (nodes by id, child lists as sets). Edits to different nodes both survive; the same property changed twice keeps the local value. Ask people to keep a page per person when restyling the same frame.
 * While an agent works the app shows an animated "working" pill and a ring around the canvas; call `finish_working_on_nodes` when done so it stops.