feat: ak sync on project state #355

Why

Sync converges one project to its declared state (design: Sync, status, uninstall).

In scope

Read project.json and local.json; ensure pinned tools; re-render unchanged projections; report edited files with a per-file result (applied, held or failed, D04); re-check Codex exceptions; write health history and state/status.json; add to the project index.

Out of scope

--all (#356).

Acceptance criteria

• Sync never self-updates or touches another project
• An edited file is reported, not overwritten

Dependencies

Blocked by: #343, #345

Blocks: #356, #357, #358, #359, #387, #449

Plan

• Release: 4.0.0-beta.3
• Size: size:M · Workstream: ws:project-scope
• Epic: feat: project-scope P5, sync, status, uninstall and the command folds (epic) #300
• Card: P5-01 in the card inventory
• Sources: Design (docs(plans): project-scoped management design and its prerequisites #289) Sync, status, uninstall; v5 impact review (docs(plans): v4 GA master plan, supersession ledger and v5 registers #290) D04

Verification

• Contract test from test: contract tests with the current violations as baseline #328