Initialize the canvas workspace.

Workflow

1. Load Canvas Workspace State

Read the workspace manifest and directory structure:

Read canvas/package.json
Glob canvas/src/**/*.ts
Glob canvas/tests/**/*.test.ts

Report: package name, version, script targets, and how many source files and test files exist.

2. Report Phase Completion

Check which Phase 1–5 artifacts exist:

Use Bash: test -f canvas/src/types/scl.ts && echo PHASE1_OK || echo PHASE1_MISSING

For each phase, report: COMPLETE or MISSING.

3. Load Boundary Rules

Read .claude/AGENT-BOUNDARIES.md — specifically the Canvas Path-Gating section and the canvas-renderer subagent constraints.

Confirm the active write scope: canvas/ paths only.

Prohibited write targets:

• cards/ — workout card content (card-generator territory)
• html/ — legacy HTML scaffold (separate phase)
• web/ — web application layer (Phase 4/5)
• middle-math/ — computation engine (separate workspace)

4. Report Current State

Output a summary in this format:

Canvas Workspace State
======================
Package: [name@version]
Source files: [count]
Test files: [count]

Phase completion:
  Phase 1 (types):     [COMPLETE | MISSING]
  Phase 2 (weights):   [COMPLETE | MISSING]
  Phase 3 (rendering): [COMPLETE | MISSING]
  Phase 4 (tokens):    [COMPLETE | MISSING]
  Phase 5 (pipeline):  [COMPLETE | MISSING]

canvas/components/ contents:
  [list files or "empty — ready for canvas-renderer"]

Active agent scope: canvas/ only
Prohibited: cards/, html/, web/, middle-math/

If $ARGUMENTS is provided, focus the report on the named phase (e.g., "5" → show Phase 5 details).