develop-kilin-viewerlisted

# Develop the Kilin Viewer Change the attached local Viewer while preserving its self-contained delivery model, evidence security, and accessible interaction contracts. ## Establish the Viewer boundary 1. Confirm the repository root, current branch, and working-tree state. Preserve unrelated changes. 2. Read `AGENTS.md`, `packages/cli/docs/agents/system-design.md`, and the Viewer sections of: - `packages/cli/docs/v1/architecture.md`; - `packages/cli/docs/v1/cli.md`; - `packages/cli/docs/v1/decisions.md`; - `packages/cli/docs/v1/testing.md`. 3. Inspect `packages/cli/src/ui/contracts.ts`, `client.ts`, and `assets.ts` before proposing a UI change. 4. Inspect `packages/cli/src/application/viewer.ts` and `packages/cli/src/infrastructure/viewer-server.ts` when data or route behavior is involved. 5. Reproduce interaction or rendering defects in a browser when practical. If the main change alters a versioned DTO, lifecycle vocabulary, stored state, or public command contract, use `evolve-kilin-contract` instead. ## Preserve the delivery architecture The Viewer is static HTML, CSS, and a no-framework DOM client served by the CLI: - keep `client.ts` and `assets.ts` self-contained; - do not add a bundler, frontend workspace, framework, or browser build; - treat `contracts.ts` as the presentation DTO boundary; - keep application projection logic outside the DOM client; - do not make the Viewer start runs, edit workflows, or become a public API. The attached View