git:20261029.1ce630b to git:20261030.739dc49

# Pixelbolt

To **use** Pixelbolt for artwork, start with [the pixel art skill](skills/pixel-art/SKILL.md) and [the quick start](docs/agent-quick-start.md), then [the authoring guide](docs/agent-guide.md) and [schema.json](schema.json) as needed. [llms.txt](llms.txt) indexes the public documentation; [README.md](README.md) includes CLI and MCP setup. The instructions below apply when **contributing to the toolkit**.

This is an agent-first pixel art toolkit. Keep the core and runtime free of dependencies. Use standard Node.js APIs for the CLI, PNG/APNG encoding, ZIP and the local server. No build step is required.

- `src/core.js`: browser-compatible recipe validation/rasterization/atlas packing, inspection (contact sheets, palette-key grids) and revision comparison.

- `src/craft.js`: browser-compatible pixel-art helpers shared by the renderer, patches and compilers: ordered, noise and value-noise dither, De-Corner/De-Stray cleanup, RotSprite-style rotation, rewrite rules, easing, seeded hashing and engine-independent trigonometry. Keep new randomness seeded and new maths polynomial so output stays identical across JavaScript engines.

- `src/font.js`: browser-compatible built-in pixel font (printable ASCII, western European accented letters, common symbols) and text layout for the `text` drawing operation. Glyph changes change rendered pixels, so treat them as format changes: regenerate examples and review.

- `src/fx.js`: browser-compatible `pixelforge-fx` compiler that bakes seeded particle emitters into ordinary recipes.

- `src/shapes.js`: browser-compatible shape layers for `pixelforge-fx` (ring, slash, beam, bolt, glyph, star, burst, stream): intensity fields in frame windows, plus the fx compiler's blob particles, cut into palette bands by named looks with lit and shade bands from the field's fall toward a light, then cleanup and outline, baked into one grid per frame. Same determinism rules as `craft.js` (its own polynomial `atan2Deg`); the golden hashes in `test/shapes.test.js` change with any change to its output, so regenerate them deliberately.

- `src/wave.js`: browser-compatible `pixelforge-wave` compiler for looping coherent radial/directional fields. Sum signed sources before palette mapping; use craft trigonometry and fixed arithmetic. `scripts/wave-presets.mjs` supplies the reviewed examples; `showcase/waves/build.mjs --check` and its golden hashes protect their pixels. This is an art tool, not an obstacle or water solver.

- `src/fluid.js`: browser-compatible `pixelforge-fluid` compiler: stable-fluids gases and FLIP/APIC liquids on a one-cell-per-pixel grid, with implicit stress-form viscosity, yield stress and adhesion, baked into palette `grid` operations. Same determinism rules as `craft.js` (only + − × ÷ and sqrt, seeded hashing, fixed steps and iterations); the golden hashes in `test/fluid.test.js` and the GIFs from `showcase/fluid/build.mjs` change with any change to its output, so regenerate both deliberately.

- `src/patch.js`: browser-compatible targeted recipe edits and canvas-coordinate painting addressed by error-style paths.

- `src/autotile.js`: browser-compatible blob/cardinal neighbour masks, template quarter layout and tilemap legends (variants, weights, neighbour rules), shared by scene tilemaps, the recipe `tilemap` operation and the autotile compiler in `src/authoring.js`. It imports `craft.js`, so copies of it (Tidewatch's game) need both.

- `src/pose-geometry.js`: deterministic joint angles and integer two-bone reach; `src/motions.js`: rig/template expansion into editable poses; `src/motion.js`: advisory contact, slide, ground, pose-spread and loop review with bounded images.

- `src/authoring.js`: browser-compatible compilers whose output is an ordinary recipe: poses, autotile templates and normal passes derived from a colour recipe (`compileNormals`; deterministic, no trigonometry).

- `src/resolve.js`: Node-side resolution of shared palette files, scene asset references and a normals source's recipe; the renderer itself never reads files.

- `src/revisions.js`: immutable on-disk MCP recipe snapshots under the configured output directory.

- `src/export.js`, `src/png.js`: deterministic file exports.

- `src/gif.js`: browser-compatible GIF89a export for sharing, used by the CLI, MCP and studio. Exact colours only: it never quantizes or dithers, and reports what GIF cannot keep (partial alpha, sub-10 ms timing) instead of hiding it. `framesGIF` writes frames made elsewhere at a frame rate, with a colour table per frame when the loop needs more than 256 colours.

- `src/godot.js`: browser-compatible Godot 4 `SpriteFrames`, `CanvasTexture` (a lit scene asset's colour pass with its normal pass flipped to +Y up) and, for autotile sets (frames found by `autotileFrames` in `src/autotile.js`), `TileSet` resources (`.tres`) written from atlas metadata, laid out as Godot 4.5+ saves them; the bundle, MCP `saveAs` and scene exports use it. `node scripts/verify-godot.mjs` loads exports in a real headless Godot 4 and checks regions, margins, pixels, timing and playback, and paints maps with Godot's terrain painter, which must pick the tiles Pixelbolt's tilemap does, and checks a lit asset's CanvasTexture (`--render` also lights it in a Godot window, which needs a desktop); run it after changing a `.tres`, the atlas, normal passes or autotile masks.

- `src/frame-folder.js`: Node-side reading of a folder of numbered PNG frames for `gif-frames`: number order, gaps, other files and mixed sequences are reported, not guessed. It reads the folder and never writes to it.

- `src/sequence.js`: numbered PNG frames for video editors, from recipes and scenes: exact frame-rate fractions, whole-number enlargement onto a video-sized canvas (contained, or covering it and cropped), a sidecar and the ffmpeg command for an alpha video. It encodes no video itself; keep it that way.

- `src/mcp.js`, `src/server.js`: agent and studio interfaces. MCP tool calls run one at a time in a worker thread (`src/mcp-worker.js`, `createToolRunner`), so a call past the time or memory limit, or one the client cancels, is stopped without stopping the server; only `ping` and cancellations skip the queue. Keep tool code free of state between calls other than files on disk.

- `src/check.js`: the `check` in `pixel_render` and `render` replies: what an export delivered (frame size, frames, loops, colours, transparency, GIF size) against the user's `expect`, each mismatch with the call that fixes it. Read-only.

- `src/runtime.js`: exported Canvas animation player.

- `src/share.js`: browser-compatible share links (the recipe in a playground URL's fragment) and recipes inside PNGs (a compressed iTXt chunk, keyword `pixelbolt-recipe`). It has no static imports, so the playground serves a byte-identical copy as `playground/share.js`; `test/share.test.js` keeps the two equal.

- `src/skill.js`: Node-side `pixelbolt skill install`: the pixel art skill on its own in a skills folder (`~/.claude/skills` by default), its commands rewritten to `npx -y pixelbolt@<version>` and the guides, schemas, examples and licence copied beside it, with a SHA-256 manifest so a changed copy is never replaced without `--force`. It never changes `skills/pixel-art/SKILL.md`, which the package and the plugin ship as written; when that skill cites a new guide, add it to `DOCS`.

- `playground/`: the browser playground for the project site, not in the npm package. Static files: it loads the engine from jsDelivr at the version pinned in `playground/app.js`, renders in a module worker with a time limit, and every PNG it exports carries its recipe. `playground/render.js` takes the engine as an argument, so Node renders exactly what the page renders. `node scripts/deploy-playground.mjs <gh-pages checkout>` prepares the site change (see `playground/DEPLOY.md`); it never pushes. `playground/fluids/` is the live fluid toy: `createLiveFluid` driven by the pointer, GIFs of the last seconds, and links that replay a visitor's pokes frame for frame; `fluids/lib.js` holds its presets and link format, and its `TOY_VERSION` stays equal to the playground's pin.

- `packaging/`: launcher scripts, START HERE and notices for the portable builds: `common/` for every system (START HERE.txt is one text with `#if windows|macos|linux` blocks), `windows/` batch files, `unix/` shell scripts for macOS and Linux, `macos/` double-click `.command` files. `scripts/build-studio.mjs` packs them with the `npm pack` file list and the pinned official Node.js runtime into a reproducible archive per target under `dist/`; `scripts/verify-studio.mjs` tests a built archive on its own system.

- `scripts/qa-studio.mjs`: walks the studio in an installed Edge or Chrome, headless with a throwaway profile, over the DevTools protocol with Node's own WebSocket. No browser-automation dependency; run it after studio changes. Packaging adds nothing to `package.json`'s dependencies or `files`, and its scripts only print or serve: they never edit a user's configuration.

- `schema.json`, `poses.schema.json`, `scene.schema.json`, `autotile.schema.json`, `fx.schema.json`, `fluid.schema.json`, `wave.schema.json`, `normals.schema.json`: generated with `node scripts/generate-schema.js`.

- `examples/`: generated with `node scripts/generate-examples.js`.

Run `npm test` after functional changes. Tests and the studio walk never assert how long something takes, since a busy CI runner would fail them with nothing broken: hold the work instead (a count such as `renderProject`'s `stats`), and give a speed target a `budget` case in `scripts/bench.mjs`, which CI reports without failing. Keep the schema, authoring reference and runtime validation aligned. Keep what an agent reads on connect small: MCP tool schemas describe a recipe and each option briefly (the server validates them, and the guide topic explains every option), `pixel_help` returns the short quick start, and longer references are its topics; a test caps both. Binary export changes should also be checked with an independent image decoder. Do not replace the text-first workflow with a UI-only drawing tool.

Never silently overwrite source recipes or generated assets. MCP renders create unique folders. The preview server must stay on loopback with an explicit asset allowlist and no arbitrary file-writing endpoints.

## Commit and push workflow

The repository owner authorizes agents working on this project to commit completed changes and push directly to `main` by default. After reviewing the diff and passing the relevant checks (including `npm test` for functional changes), commit and push without asking for routine confirmation or opening a pull request. This is the standing workflow for this small project unless the user requests a different approach.

Before committing, inspect existing uncommitted changes and preserve them. Include changes from other agents when the user has authorized combining that work; otherwise leave unrelated work untouched. Fetch before pushing and integrate upstream changes without discarding local work. Never force-push, rewrite published history, reset away changes or delete branches as part of this authorization. Report the resulting commit and push status; if pushing fails, explain the concrete blocker.