ultra-initlisted

# Create the skeleton and capture only the initial project outline Initialization establishes places for later authority and records raw owner intake. It does not validate the problem, establish a North Star, build a product or architecture baseline, settle domain language, choose a Change, or start another public workflow. ## Before you start 1. If `.ultra/changes/active/` exists, resolve at most one active `change_id`. Read `.ultra/tasks.json` if it exists, plus the `context_file` and closing `## Resume Note` of unfinished tasks matching that id. Historical unfinished rows do not turn a partial skeleton into current work. A partial `.ultra/` is recovery work. 2. Read `.ultra/project-brief.md`, `.ultra/north-star.md`, `CONTEXT.md`, and relevant `.ultra/decisions/` when they exist. Preserve accepted authority byte-for-byte. 3. Establish the repository root, Git state, and whether meaningful code or maintained documentation exists from the filesystem. Do not ask the owner for those facts. ## Definition of done - `.ultra/project-brief.md` contains raw owner intake: one line, a broad outline, explicit inputs already supplied, and open questions handed to Research. - For a new skeleton, a structurally complete North Star v2 with status `unresearched` and the three specification skeletons exist. Init does not populate `FP-*`, `NS-*`, or `HC-*`; recovery preserves any populated authority, and Init does not create `CONTEXT.md`. - Every packaged path was r