feat: rebuild Ask Agent as an evidence workspace (v2.18.0)

CHANGELOG.d/2.18.0-ask-agent-evidence-workspace.md

@@ -0,0 +1,12 @@
+## Added
+
+- Rebuilt the Global Ask destination as a responsive evidence workspace with a
+  dedicated semantic composer, explicit empty/loading/error/answer states,
+  separated Event Lineage and citation evidence, and answer focus management.
+- Added Storybook scenes for empty, loading, answered, unavailable, and phone
+  layouts while preserving stale-session recovery and cited-post navigation.
+
+## Fixed
+
+- Replaced the unrelated Keyman-link button treatment in the Ask chatbox and
+  prevented Enter during IME composition from submitting a partial question.

docs/adr/0127-ask-agent-evidence-workspace.md

@@ -0,0 +1,71 @@
+# ADR 0127 — Ask Agent evidence workspace and composer contract
+
+**Decision status:** Accepted
+**Date:** 2026-08-21
+**Figma File ID:** `1Su3lDRmiZdcUs47t1QwIX`
+**Figma desktop frame:** `11:2` (`Ask Agent / Desktop / Answered`)
+**Figma mobile frame:** `11:3` (`Ask Agent / Mobile / Answered`)
+**Figma primary-action component set:** `21:10` (`Controls / Primary Button`)
+**Stack placement:** This change is a direct child of PR #264 head `39f21261052a9d2ae82c4b851a54831eaf909805`.
+
+## Context
+
+The stacked buyer surface already provided authorized Global Ask, durable
+session recovery, cited-post navigation, and Event Lineage focus continuity.
+The visible Ask Agent screen, however, remained a generic content section: the
+composer reused a Keyman link-style button, the answer, timeline, citations,
+and evidence facts shared one undifferentiated card, and the screen had no
+component or Storybook state boundary of its own.
+
+The project UI/UX Standard Guide v3.0 requires a clearly differentiated focused
+input, visible action controls, responsive PC/tablet/phone behavior, and a
+mobile layout that places the primary action within the content flow. ADR 0002
+also established the safe Figma file above as the public design-system boundary
+and forbids copying confidential source-organization material.
+
+## Decision
+
+1. Extract the destination into `AskAgentWorkspace`, with a stateful controller
+   and a presentational `AskAgentWorkspaceView`.
+2. Use a semantic form and a visually primary Ask button. Enter submits,
+   Shift+Enter inserts a line break, and an IME composition Enter never submits.
+3. Separate composer, pending/error/empty state, answer, Event Lineage timeline,
+   and cited evidence into explicit regions. A completed answer receives focus.
+4. Keep every existing security and truth boundary: only the authenticated
+   `/api/ask` contract is called, stale sessions retry once without the expired
+   identifier, previous evidence is hidden while a replacement answer is
+   pending, and source actions retain the #263/#264 Event Lineage handoff.
+5. Reuse the current UI/UX-standard button, focus, color, radius, and spacing
+   tokens. Define responsive breakpoints at 1024px and 768px; the phone state
+   uses a single column and a full-width primary action.
+6. Keep editable answered-state desktop and mobile specifications in the Figma
+   frames recorded above. Implement the repeated Ask action as the token-bound
+   Figma component set recorded above, with Default, Hover, Disabled, and
+   Loading variants and desktop/mobile instances.
+7. Inventory Empty, Loading, Answered, Unavailable, and Phone Answered
+   executable scenes in Storybook so state and edge-event review remains
+   coupled to the production component.
+
+## Consequences
+
+- Ask Agent is no longer coupled to the post-popup or Keyman control styles.
+- Future streaming, follow-up history, or source comparison can evolve inside a
+  bounded component without expanding `App.tsx`.
+- The component preserves the exact accessible labels relied on by existing
+  integration tests and downstream stacked PRs.
+- Figma and CSS share named color, radius, and spacing concepts while Storybook
+  remains the executable source for loading, unavailable, and responsive states.
+- The Figma frames and primary-action component carry shared implementation,
+  Storybook, PR, parent-stack, exact-head, and ADR traceability metadata.
+- This ADR does not claim the unmerged stack is protected-main behavior.
+
+## Verification
+
+- Focused controller, keyboard, session recovery, source navigation, and design
+  token/breakpoint contract tests.
+- Existing App-level citation, timeline, stale-session, pending-answer, and
+  Event Lineage focus regressions.
+- Frontend lint, production build, complete Vitest suite, and Storybook build.
+- Desktop and mobile Figma screenshots checked for clipping, overflow, action
+  prominence, source-evidence hierarchy, and component-instance consistency.
+- Responsive and focus-visible CSS review against the UI/UX guide.