Retire Project as user-facing concept — align CONTEXT.md with Amicode README / Armonia vision

[aarontrowbridge]

Important

Problem — CONTEXT.md defines Project as the user-facing unit of work (directory registered with amicode, dashboard switching, Session nested under Project). This conflicts with the Amicode README vision where the workspace is what you edit, ~/.amico is what the system manages, Amicode is the lens — users organize work via Armonia vaults, Problems (pulse-design units), Runs, and the pulse catalog. The opencode engine's "Add project" picker (screenshotted) leaks as a third "project" that users never need.

Approach — Retire Project from the user-facing model. Keep the opencode storage concept internally but hide it from docs/UI. Update CONTEXT.md: mark Project as internal/legacy storage detail (single workspace ↔ single checked-out Armonia root), make Session global/workspace-scoped, clarify Armonia ≠ Project, and note the dashboard no longer surfaces project switching. File a follow-up for the opencode fork to hide the picker entirely.

Scope — in: CONTEXT.md language + any README/AGENTS cross-refs that mention Project as user concept · out: opencode fork code change (tracked as follow-up), data migration

Acceptance Criteria

• CONTEXT.md no longer presents Project as the user-facing unit — Project is labeled internal/legacy or removed, Armonia/Workspace/Problem/Session read as the canonical taxonomy
• Session definition no longer says "bound to exactly one Project, never re-parented, nested under Project"
• CONTEXT.md guidance matches README studio table (solo→team→fleet) with no dashboard project-switching language

Constraints & Invariants

• No file paths or code in body (kept)
• Existing sessions/projects on disk keep working — doc change is posture, not storage migration