ultra-changelisted

# Reconcile first, then write down what this Change commits to A Change connects research, plan, implementation, verification, review, and delivery. Reconcile first so new intent does not bury an existing specification/code conflict. ## Before you start 1. Read `references/change-contract.md` and apply its **Active Change authority resolution** before reading any active `intent.md`, relying on a current `change_id`, or creating or writing a Change. Continue only from its positively observed stable zero-or-one result; return its typed repair for any other result. With one active Change, read `.ultra/tasks.json`, then only its unfinished `context_file` values. Update the same `change_id`; never open a second active Change. 2. Read `.ultra/project-brief.md`, `CONTEXT.md`, relevant `.ultra/decisions/`, and `.ultra/north-star.md` for raw provenance, accepted language, and direction. 3. Grep archive and abandoned Changes that touched this area. Prefer archived `delivery.md`; otherwise read `archive-summary.md`, `verification.md`, `intent.md`, and remaining Markdown. Read abandoned Changes as history of rejected boundaries and reusable evidence, never current intent. A missing `delivery.md` does not mean no history; repeated modules are an architecture signal. ## Whether this skill applies at all | Situation | Where it goes | |---|---| | No active Change, and a new bounded request exists | Here — create one stable id | | One active Change needs its