This directory explains the product as a browser client, how to work on it, and why its durable boundaries exist. Start with the shortest document that answers your question.
| Document | Purpose |
|---|---|
| Getting started | Connect, choose a Workspace, start a Session, or use the fixture. |
| Product scope | Supported workflows, product principles, and explicit non-goals. |
| Deployment contract | Build identity, hosting, security headers, health, and rollback. |
| Troubleshooting | Connection, recovery, onboarding, and command diagnostics. |
| Security policy | Supported versions and private vulnerability reporting. |
| Document | Purpose |
|---|---|
| Architecture | Runtime ownership, dependency direction, state, and extension boundaries. |
| Protocol integration | Capability negotiation, projections, Core pins, and compatibility gates. |
| ADR index | Accepted decisions, grouped by concern. |
| Product shell ADR | Authentication, Workspace/Session navigation, and controls. |
| Session navigation ADR | Confirmed Session refs and background turn ownership. |
| Contributing | Development workflow and review expectations. |
| Testing | Unit, browser, contract, runtime, and deployment verification. |
| Releasing | Immutable publication, provenance, and rollback procedure. |
| Agent guide | Non-negotiable repository rules for coding agents. |
- Frontend baseline — interaction, motion, and usability acceptance rules, with TasteSkill and 21st.dev references.
- September 2026 product audit — reproduced issues, implemented repairs, browser evidence, and remaining Core limits.
- Follow-up usability and recovery audit — uncertain turn recovery, saved conversations, mobile controls, and modal focus.
- Final audit and repairs — final runtime, keyboard, long-history, resource-failure and production verification.
- Changelog — release-level user and operator changes.
- Third-party notices — copied or adapted source
- Production dependency licenses — generated license material for the shipped JavaScript graph attribution, including the DSH visual reference.
- Release history — immutable archives, checksums, and release notes.
- Guides describe the current system. Update them in the same change as the behavior they document.
- ADRs record durable decisions and rejected alternatives. Do not rewrite an accepted decision to make history look current; supersede it with a new ADR.
- Machine-readable compatibility truth belongs in
packages/client/contract-source.jsonandpackages/client/core-runtime.json, not in prose version claims. - Security-sensitive examples must not contain real tokens, API keys, private repository paths, or credential-bearing WebSocket URLs.