mason-gallery

Discuss and get approval before edits for ambiguous, architectural, or multi-file changes.

Create ordinary task-branch commits; use git-mainline-squash for final archive squashes.

Create and integrate Rezics worktrees using the main/archive workflow.

Apply a code-first plan — route each durable item to its home in code (types/tests/comments), then make the source document disposable. No validation CLI, no state machine. Use when implementing a plan/proposal.

Thinking partner for exploring ideas, investigating the rezics codebase, and clarifying requirements before a plan exists. Use when the user wants to think something through. Never implements.

Propose a code-first plan — a single markdown file with context, durable constraints/decisions, and a task checklist. No spec files. Use when the user wants to turn an idea into actionable, implementable work.