Finish shared UI composition and honest loading, unavailable, and recovery states #29597

Problem

The UI canonicalization inventory records wrappers that duplicate canonical atoms, while the zero-debt compliance baseline can still hide those entries after wrapper reclassification. The route migration also left concrete ownership defects: four FramedPage views retained an outer workspace gutter, Automations reserved composer clearance twice, Managed Cloud pages could lose their scroll owner, and Relationships rebuilt shared content-state presentation.

The molecular review procedure is also not fail-closed against signature-preserving member drift, stale JSON output, mutable atomic-debt decisions, or unrelated behavioral-test evidence.

Acceptance criteria

• Migrate every maintained caller of the obsolete Brand button/card, LockOn, extension badge, and Cloud text-input wrappers to canonical atoms; delete obsolete exports, stories, and helpers.
• Keep only domain adapters that delegate atomic paint and semantics to canonical components.
• Give Database, Memories, Tasks, Automations, and default Managed Cloud pages exactly one gutter, scroll, and composer-clearance owner.
• Render Relationships loading, error, empty, and no-results states through canonical ContentState.
• Bind molecular decisions to exact members and rendered composition fingerprints; reject non-final workflows.
• Track and validate both generated molecular artifacts.
• Preserve atomic consolidation resolutions in an exact ledger so relabeling, deletion, or reintroduction cannot hide debt.
• Require two maintained consumers, a rendered story, and an owner-bound behavioral test before declaring a canonical molecule.
• Pass focused UI/plugin tests, typecheck, builds, ownership audits, desktop/mobile browser smoke, and independent adversarial review.

Evidence plan

• Before/after desktop and mobile captures of the affected framed route.
• MP4 walkthrough of the current route behavior.
• Frontend console/network logs.
• Exact commands and outcomes for focused tests, builds, audits, and known repository-wide baseline blockers.