Set up and make your first change#

Contributions use the same complete quality policy as maintained prototypes. Start from the live task and current source, then verify the behavior you change rather than treating an illustrative architecture as implemented code.

Establish the workspace#

Read repository AGENTS.md, the foundation, shared glossary, and task-specific documentation. Exact toolchain pins live in .node-version, .nvmrc, and package.json; pnpm installs the project Node runtime without changing the machine's selection.

From a clean worktree:

pnpm worktree:setup
pnpm workflow:context
pnpm verify
git status --short

Workspace guidance describes clean builds, browser dependencies and supported commands. Setup/verification must leave tracked source unchanged. Use a separate worktree for concurrent changes.

Choose a small real change#

For example, improve an explanation next to an existing public workflow, or address a defined task against its observable acceptance criteria. Before editing implementation, inspect the issue's assignment, dependencies and exact prerequisite handoffs. Repository-agent claiming rules are in AFK implementation.

Change code, its relevant guide/reference, and the maintained example together when user-visible behavior changes. Keep public imports supported and optional UI loading intact. Architecture locates those boundaries.

Verify and hand off#

Run focused direct checks while working, then the complete pnpm verify gate on final committed clean source. Every change also needs automated browser verification and observed T3 evidence from its own worktree. Browser/worktree guidance explains source identity and screenshots.

A reviewable branch is not a merged or accepted change. Follow reliable development for acceptance mapping, inline PR screenshots, handoff validation and roadmap maintenance. Hosting, releases and merges require their existing authorization.