Base branch: main Branch: maggie/redesign-decisions-and-comments Depends on: None

## Goal Give decisions and resolved comments a coherent, high-quality sidecar design while preserving the distinct durable record states.

## Context From Planning - The current decisions and resolved-comment specimens in `/design-audit#surfaces` both need a proper design pass. - They share sidecar-card foundations and provenance, but questions, accepted comments, resolved history, deliberately empty links, and orphaned links must remain semantically distinct. - This is a human-reviewed design task rather than a mechanical restyle.

## Current Behavior Questionnaires and comment threads share `SidecarCard`, but information hierarchy, provenance, actions, settled treatment, history disclosure, and empty/orphaned records remain visually weak. Existing behavior carefully distinguishes pending, linked, deliberately empty, and orphaned relationships.

## Desired Behavior Design a small sidecar record system that makes open work, settled decisions, provenance, related prose, and exceptional relationship states immediately legible without fragmenting the product into unrelated card styles.

## Acceptance Criteria - [ ] The design audit covers outstanding questionnaire, answered questionnaire, open comment, accepted comment, resolved history, deliberately empty relation, orphaned relation, focused/related-prose, disabled, and narrow layouts. - [ ] Questions and comments share card anatomy/tokens where their semantics match and remain distinct where actions differ. - [ ] Provenance, primary content, contextual quote, related-prose state, and actions have a clear reading order. - [ ] Pending, linked, deliberately empty, and orphaned states remain visibly and programmatically distinct. - [ ] Existing accept/dismiss confirmation, frozen accepted threads, resolved-history disclosure, focus handoff, related-prose highlight/pin, and record authority remain unchanged. - [ ] Maggie approves the audit specimens before production migration.

## Verification Commands - `bun run types` - `bun run ci` - `bun test packages/editor` - `bun run e2e`

## Primary Surfaces - `/design-audit#surfaces` - Decisions rail and questionnaire cards in `packages/editor` - Comment thread cards, `SidecarCard`, and provenance

## Expected PR Checks - Repo required checks

## Report Requirements - State inventory and annotated before/after screenshots - Shared anatomy/token decisions - Browser evidence for focus, disclosure, and related-prose behavior - Any deliberately deferred states

## Implementation Notes - Records own decisions; rendered document projections are not authority. - Preserve the four relationship states: pending, linked, deliberately empty, and orphaned. - Empty means intentional absence; orphaned means the former target cannot be recovered safely. - Keep one shared foundation without forcing question-owned controls into comment-owned action slots.

## Stop Conditions - A visual treatment obscures the difference between empty and orphaned relationships. - The design requires changing record authority, anchoring, or questionnaire/comment workflows.