Pivot to text-first column-stack workspace + merge-with-review across AI artifacts

Workspace
- Pivot from "set of open panes" to a Finder-style miller column stack:
  TopBar / LeftSidebar / [section → entity → entity ...] / pinned text editor.
  openPanesStore is now an ordered Column[] with pushFrom / closeFrom /
  setStack; only one top-level section is rooted at a time.
- New entity column panes: Term, Block, Association, Constraint,
  Requirement, Finding. Click-through navigation truncates deeper
  columns automatically.
- LeftSidebar surfaces a pending-count chip per section (single-glance
  navigation cue) and spins its analyze ↻ via SVG Spinner whenever the
  LLM is working — including server-initiated runs caught by the runs
  poll, not just user-triggered ones.

Analyze pipeline + persistence
- Unified `concepts` pass (taxonomy + glossary in one LLM call) replaces
  the two-pass setup. Server still accepts ?section=taxonomy|glossary
  and normalizes them for back-compat.
- model / requirements / detection (assumptions, risks, inconsistencies)
  + cross-layer validation rules (X1–X4: stale term link, unlinked
  formalism, undefined linked term, prose-only term).
- Persistence: NarrativeDocument, ModelSnapshot, ChangelogEntry,
  TaxonomyTerm, RequirementEntry, Finding, AnalysisRun. Re-runs MERGE
  instead of replace: gentle update on existing items, suggested on new,
  deprecated on missing — same idiom for every artifact kind. User pins
  preserve "kept" decisions across re-analyses.
- Migrations: pivot_text_first, add_requirement_linked_term,
  term_review_state, review_state_for_reqs_and_findings,
  add_term_definition_pinned.

Concept ↔ ontology integration
- linkedTermId on Block / Association / Constraint / Requirement.
  PromoteToolbar lets the user formalize a concept inline: + Block /
  + Association / + Constraint / + Requirement, all routed through
  applyOps so undo/redo and SSE work for free.
- decideElement op for in-canvas keep/discard on review-pending model
  elements.

User-authored definitions
- TermColumn definition is click-to-edit. Save (Cmd-Enter / blur),
  Cancel (Esc), Reset to AI suggestion when pinned.
- definitionPinned flag on TaxonomyTerm: future Analyze runs leave the
  user's text alone. setTermDefinition repo function + POST
  /api/projects/[id]/terms/[termId]/definition endpoint.
- mergeTaxonomySuggestion + applyGlossaryDefinitions both pin-aware.

UX/UI
- StatusChip: single component for all state idioms (suggested,
  deprecated, accepted, dismissed, resolved, severity, validation code,
  confidence, warn). Replaces 5+ ad-hoc badge classes.
- PaneControls (PaneViewTabs + PaneFilterChip): separates view-mode
  toggles from filter chips so toggling Pending no longer flips you off
  the current view.
- PaneEmpty: unified empty-state with title + hint + action.
- PaneDrawer: collapsible groups for Pending / Discarded review; cards
  group as Kept (top) → Pending (bottom drawer) → Discarded (Findings
  only, hidden when empty). Restore action recovers dismissed/resolved
  findings.
- ConceptCard unifies Tree and A–Z views in Concepts; only Tree parents
  carry the chevron (no empty placeholder offset).
- Type + spacing tokens (--text-xs..xl, --space-1..6, --lh-tight/ui/
  prose, --radius-*) replace every ad-hoc value.
- Buttons standardized to body sans 500 (was a mishmash of mono / display).
- Card shells unified across Concepts / Requirements / Findings.

Cleanup
- Removed: LeftRail, FindingsPanel, IssuesPanel, SocratesDock,
  ProposalCard, SlashMenu, SlashExtension, slashSuggestion,
  CanvasHeader, TaxonomyPane, GlossaryPane, TermDetail (popover; now
  TermColumn).
- Section ids in openPanesStore: dropped taxonomy/glossary, added
  concepts. localStorage migration runs on hydrate.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

apps/web/components/editor/StatusChip.tsx

@@ -0,0 +1,89 @@
+// StatusChip — the single visual idiom for any "this thing has a state"
+// signal in the workspace. Replaces the five ad-hoc chips that grew over
+// time: term-badge-new / term-badge-deprecated / finding-sev / finding-code /
+// req-flag / EntityColumns ReviewBadge.
+//
+// Variants are picked from a tiny vocabulary so the visual rhythm is
+// consistent across surfaces: review state (suggested / accepted /
+// deprecated / dismissed / resolved), severity (low / medium / high), or a
+// validation code (S1, M2, X3, …) rendered as `code`.
+//
+// Usage:
+//   <StatusChip variant="suggested" />          // "NEW"
+//   <StatusChip variant="deprecated" />         // "DEPRECATED"
+//   <StatusChip variant="severity" value="high" />
+//   <StatusChip variant="code" value="X3" />
+//   <StatusChip variant="confidence" value={0.87} />
+//   <StatusChip variant="warn" label="unsupported" />
+//
+// CSS lives in styles/base.css under .status-chip; tone is one of:
+//   accent   — review-pending / NEW / suggestion
+//   muted    — neutral / deprecated / code
+//   warn     — risky / high-severity / unsupported
+//   ok       — confirmed / resolved
+//   info     — informational / confidence
+
+"use client";
+
+export type StatusTone = "accent" | "muted" | "warn" | "ok" | "info";
+
+export type StatusChipProps =
+  | { variant: "suggested"; title?: string }
+  | { variant: "accepted"; title?: string }
+  | { variant: "deprecated"; title?: string }
+  | { variant: "dismissed"; title?: string }
+  | { variant: "resolved"; title?: string }
+  | { variant: "severity"; value: "low" | "medium" | "high"; title?: string }
+  | { variant: "code"; value: string; title?: string }
+  | { variant: "confidence"; value: number; title?: string }
+  | { variant: "warn"; label: string; title?: string }
+  | { variant: "ok"; label: string; title?: string }
+  | { variant: "muted"; label: string; title?: string };
+
+/** Single-axis style picker. Every visual decision flows through this fn so
+ *  designers can tweak one place. */
+function styleFor(props: StatusChipProps): { tone: StatusTone; label: string } {
+  switch (props.variant) {
+    case "suggested":
+      return { tone: "accent", label: "NEW" };
+    case "accepted":
+      return { tone: "ok", label: "KEPT" };
+    case "deprecated":
+      return { tone: "muted", label: "DEPRECATED" };
+    case "dismissed":
+      return { tone: "muted", label: "DISMISSED" };
+    case "resolved":
+      return { tone: "ok", label: "RESOLVED" };
+    case "severity":
+      return {
+        tone: props.value === "high" ? "warn" : props.value === "medium" ? "info" : "muted",
+        label: props.value.toUpperCase(),
+      };
+    case "code":
+      return { tone: "muted", label: props.value };
+    case "confidence":
+      return {
+        tone: props.value >= 0.75 ? "ok" : props.value >= 0.4 ? "info" : "muted",
+        label: `${Math.round(props.value * 100)}%`,
+      };
+    case "warn":
+      return { tone: "warn", label: props.label };
+    case "ok":
+      return { tone: "ok", label: props.label };
+    case "muted":
+      return { tone: "muted", label: props.label };
+  }
+}
+
+export function StatusChip(props: StatusChipProps) {
+  const { tone, label } = styleFor(props);
+  return (
+    <span
+      className={`status-chip status-chip-${tone}`}
+      title={props.title}
+      aria-label={props.title ?? label}
+    >
+      {label}
+    </span>
+  );
+}