Add the Atrium Intelligence Catalog

[eamirian]

What changed

• adds a domain-neutral onboarding presentation contract for source groups, domain/topic labels, and starter questions
• lets the resource plane admit and project multiple onboarding profiles in one product scope
• makes Atrium enumerate admitted profiles, deduplicate them by identity, and always offer the Core-owned Custom Intelligence path
• adds the five-step intent → evidence → focus → review → build experience
• updates the product reference lock and roadmap without changing the 0.9 Collaborative Intelligence release gate

Why

Atrium should begin with the outcome—World Intelligence, Marketing Intelligence, or a custom intelligence system—without asking users to understand packages, ontologies, agents, or ACE architecture. Domain names remain outside the Core kernel; domain repositories contribute inert profiles through the existing authenticated resource plane.

Safety and boundaries

Selecting a starting point grants no installation, source connection, monitor, activation, or execution authority. Existing Builder and approval boundaries remain the only route to live work. Durable sessions render only for the current admitted product profile.

Validation

• Core projection tests: 3 passed
• Canvas unit suite: 305 passed
• Atrium browser acceptance: 3 passed
• TypeScript production build: passed
• visual QA: World / Marketing / Custom catalog, evidence selection, and review states inspected

Coordinated domain work

World and Marketing profiles are separate companion PRs in their owning repositories. They are external consumers, not copied into Core.