Altar / Shell — first conversation entry #10

Planning representation replaced — 6 November 2026. Remaining acceptance is consolidated into #11. This closure does not mean the capability is complete or cancelled. The original scope and evidence below remain preserved; current selected work starts at #52.

Serve a usable Bridge entry point with the shared UI foundations needed for a first conversation.

Checklist

• Serve the static Svelte client through Litestar; Bridge direct links and refresh resolve correctly.
• Show application/source identity and a clear Bridge entry; expose other destinations as they become usable.
• Handle authentication, loading, empty, API failure and connection-loss states visibly.
• Preserve session selection and drafts during supported navigation without exposing credentials.
• Verify keyboard focus, narrow-screen layout and the existing LychD Dark appearance.
• Document one reproducible frontend/backend development and test path; fixtures are clearly distinguished from live acceptance.

Starting point: shared layout; delivery boundary. Extend the existing shell.

Part of: #9, first-conversation slice with #11. Full five-screen navigation is not a closure prerequisite.
Reference: Frontend (ADR 15).

Development aid: #53 owns the isolated contributor backend/fixture path; it is not a prerequisite for work using the existing tests.

Next contribution: Verify one Bridge shell journey through loading, API failure and retry, including keyboard focus and draft preservation. Use existing fixtures and generated contracts; record frontend check/build results. #53’s launcher is not required.
Verification: Component/build checks without GPU; real backend journey for integration. Shared contribution and touched-docs rules: #52.

Delivery review — 12 October 2026

Published source: a913bff.

The shell preserves explicit session selection, per-session drafts and uncertain request identities across instrument navigation; read retry and late-response fencing have component evidence. CONTRIBUTING documents the disposable protected backend and source-client path. Browser login/credential reuse, direct-link refresh, keyboard focus and narrow-screen layout still need the named journey; component checks do not qualify those physical browser behaviors.

Delivery evidence · Source/test 1 · Source/test 2