aw-spec-cli 0.1.4 → 0.1.5

package/assets/docs/domainspecs/UIVisualization/clean-architecture.domain.md

@@ -1,87 +0,0 @@
-# Clean Architecture — UI Visualization Domain
-
-> Front-end layering for the visualization app. NON-NEGOTIABLE.
-> Commands: `/aw-spec-plan`, `/aw-spec-tasks`, `/aw-spec-implement`.
-
-## Dependency direction
-
-Dependencies flow **inward only**, toward the generic chart library:
-
-```
-Page (app/*/page.tsx)
-      │  composes
-      ▼
-Adapter (components/charts/<Domain>Chart.tsx)   ── maps domain data → generic props
-      │  depends on
-      ▼
-Generic Chart (components/charts/generic/*)      ← innermost ring; depends on nothing domain-specific
-      ▲
-      │  provides data (never imports a chart)
-Data Layer (lib/*, store/*)
-```
-
-The **generic chart library** is the innermost ring — every layer may depend on it; it depends on
-nothing but `PlotlyChart` + the shared palette/theme.
-
-## Layer responsibilities
-
-- **Page** (`app/*/page.tsx`) — route surface. Reads data from the store, lays out the chart card,
-  passes props to an adapter (or directly to a generic chart). MUST NOT contain Plotly trace
-  construction.
-- **Adapter** (`components/charts/<Domain>Chart.tsx`) — translates a **project/domain type**
-  (e.g. `Compound[]`, `TrialArm[]`) into a generic chart's props. The **only** place domain
-  vocabulary meets a chart (see [[component-contracts.domain]]).
-- **Generic chart** (`components/charts/generic/*`) — builds Plotly traces/layout from
-  **caller-supplied data, labels, colours**. Domain-agnostic and reusable across projects.
-- **Data layer** (`lib/*`, `store/*`) — types, parsing, formatting, state. Feeds data **into**
-  pages; MUST NOT import chart components.
-
-## Forbidden patterns
-
-- Domain logic, project types, or hard-coded domain labels inside `components/charts/generic/`.
-- A page constructing Plotly `data`/`layout` arrays directly (that belongs in a chart/adapter).
-- A generic chart importing from `lib/sample-data`, the store, or any `app/*` route.
-- The data layer importing a chart component (inversion of the dependency rule).
-
-## Canonical example (agent reference)
-
-The adapter is the dependency seam — the **page** depends on the **adapter**, the **adapter**
-depends on the **generic chart**; the generic chart knows nothing about the domain:
-
-```tsx
-// Page — app/compounds/page.tsx  (composition only)
-'use client'
-import CompoundScatterPlot from '@/components/charts/CompoundScatterPlot'
-import { useDataStore } from '@/store/data-store'
-
-export default function CompoundsPage() {
-  const { compounds } = useDataStore()
-  return <CompoundScatterPlot compounds={compounds} />
-}
-
-// Adapter — components/charts/CompoundScatterPlot.tsx  (domain → generic props)
-'use client'
-import { BubbleChart } from '@/components/charts/generic'
-import type { Compound } from '@/lib/types/pharma'
-
-export default function CompoundScatterPlot({ compounds }: { compounds: Compound[] }) {
-  const targets = [...new Set(compounds.map(c => c.target))]
-  return (
-    <BubbleChart
-      series={targets.map(t => ({
-        seriesLabel: t,
-        points: compounds.filter(c => c.target === t).map(c => ({
-          x: c.molecularWeight, y: Math.log10(c.ic50_nM),
-          size: c.selectivityRatio, label: c.name,
-        })),
-      }))}
-      xLabel="Molecular Weight (Da)" yLabel="log₁₀(IC₅₀, nM)" sizeLabel="Selectivity"
-    />
-  )
-}
-```
-
-## Related
-- [[component-contracts.domain]] — adapter prop contract
-- [[charting-standards.domain]] — the `PlotlyChart` base + theme the generic ring depends on
-- [[folder-structure.domain]] · [[state-management.domain]]

package/assets/docs/domainspecs/UIVisualization/coding-standards.domain.md

@@ -1,47 +0,0 @@
-# Coding Standards — UI Visualization Domain
-
-> TypeScript / React / Next.js conventions for the viz front-end. NON-NEGOTIABLE.
-> Commands: `/aw-spec-plan`, `/aw-spec-tasks`, `/aw-spec-implement`, `/aw-spec-analyze`.
-
-## TypeScript
-
-- `strict: true`. No implicit `any`; for Plotly's loose trace objects use a single
-  `as never[]` / `Record<string, unknown>` at the wrapper boundary, never sprinkled through code.
-- Data contracts are `interface`s in `lib/types/`; chart prop types are exported from each
-  generic chart and re-exported from `generic/index.ts`.
-- Prefer `type` unions for closed sets (`'sample' | 'excel' | 'api'`).
-
-## React / Next.js
-
-- Any component using hooks, Plotly, the store, or browser APIs is a **Client Component**
-  (`'use client'`). Pages that only compose may still be client when they read the store.
-- Charts and Plotly are **never** in Server Components (SSR-unsafe — see [[charting-standards.domain]]).
-- Keep render pure: no `set`/fetch in render bodies; mutations go through store actions
-  (see [[state-management.domain]]).
-- Memoise large derived datasets (`useMemo`) before passing to a chart so the wrapper's
-  `JSON.stringify` diff stays cheap.
-
-## Naming & layout
-
-- Generic charts: PascalCase noun (`Heatmap`, `BubbleChart`). Adapters: domain concept
-  (`CompoundScatterPlot`). Routes: kebab-case folder (`dose-response/`).
-- One component per file; co-locate a route's page in `app/<route>/page.tsx`.
-- Import charts from the barrel: `import { Heatmap } from '@/components/charts/generic'`.
-
-## Styling
-
-- Tailwind utility classes + the shared `cn()` helper (`clsx`). Theme tokens (glass, gradient,
-  accent) come from `globals.css` / `tailwind.config.ts` — don't inline ad-hoc colours that
-  fight the chart theme.
-- Chart text/grid colour comes from `BASE_LAYOUT`, not per-page overrides.
-
-## Forbidden patterns
-
-- `plotly.js` imported anywhere except inside `PlotlyChart`'s `useEffect`.
-- Domain strings/types inside `components/charts/generic/`.
-- A component calling Zustand `set` directly (use a named action).
-- Fixed pixel chart heights in page cards (use `fillHeight`).
-
-## Related
-- [[charting-standards.domain]] · [[component-contracts.domain]] · [[state-management.domain]] ·
-  [[testing.domain]]

package/assets/docs/domainspecs/UIVisualization/comandrulemap.md

@@ -1,130 +0,0 @@
-# UI Visualization Domain — Command → Rule-File Map
-
-Per-AW-Spec-command list of the **UIVisualization domain** rule files in this folder.
-Technology standards already auto-load inside each command; the files below are the
-domain-specific ones to load **in addition** for a data-visualization front-end project.
-
-- All paths are workspace-relative and live in this folder: `docs/domainspecs/UIVisualization/`.
-- A skill reads this file and loads every path under the matching command heading.
-- `/aw-spec-select-domain UIVisualization` selects this folder as active.
-
----
-
-## ⚠️ Chart-selection rule (applies to every command below)
-
-The `chart-*.md` files are **conditional**. Load the **core** rule files unconditionally; load a
-`chart-<name>.md` **only if that chart is in the developer's selection** (see
-[[domain-requirements]] → *Chart Selection*).
-
-- If the requirement says **"all plots" / "all charts" / "all"** → load **all 10** `chart-*` files.
-- If it names a subset → load only those `chart-*` files (match via the selection-token table in
-  [[domain-requirements]]).
-- If selection is **unspecified** → `/aw-spec-specify` / `/aw-spec-clarify` MUST ask which charts
-  before planning; do not assume "all".
-
-The 10 chart files: `chart-heatmap.md` · `chart-bubble.md` · `chart-scurve.md` ·
-`chart-survival.md` · `chart-volcano.md` · `chart-dimred.md` · `chart-parallel.md` ·
-`chart-violin.md` · `chart-network.md` · `chart-trellis.md`.
-
----
-
-## /aw-spec-constitution
-- docs/domainspecs/UIVisualization/domain-requirements.md
-
-## /aw-spec-specify
-- docs/domainspecs/UIVisualization/domain-requirements.md
-- docs/domainspecs/UIVisualization/ui-viz-terms.md
-- docs/domainspecs/UIVisualization/component-contracts.domain.md
-- docs/domainspecs/UIVisualization/data-source.domain.md
-- (+ selected) docs/domainspecs/UIVisualization/chart-<name>.md   ← per selection, or ask
-
-## /aw-spec-clarify
-- docs/domainspecs/UIVisualization/domain-requirements.md
-- docs/domainspecs/UIVisualization/ui-viz-terms.md
-- docs/domainspecs/UIVisualization/component-contracts.domain.md
-- (resolve the chart selection here if not yet specified)
-
-## /aw-spec-plan
-- docs/domainspecs/UIVisualization/folder-structure.domain.md
-- docs/domainspecs/UIVisualization/clean-architecture.domain.md
-- docs/domainspecs/UIVisualization/state-management.domain.md
-- docs/domainspecs/UIVisualization/data-source.domain.md
-- docs/domainspecs/UIVisualization/charting-standards.domain.md
-- docs/domainspecs/UIVisualization/component-contracts.domain.md
-- docs/domainspecs/UIVisualization/coding-standards.domain.md
-- docs/domainspecs/UIVisualization/testing.domain.md
-- (+ selected) docs/domainspecs/UIVisualization/chart-<name>.md   ← one per selected chart
-
-## /aw-spec-tasks
-- docs/domainspecs/UIVisualization/folder-structure.domain.md
-- docs/domainspecs/UIVisualization/clean-architecture.domain.md
-- docs/domainspecs/UIVisualization/component-contracts.domain.md
-- docs/domainspecs/UIVisualization/charting-standards.domain.md
-- docs/domainspecs/UIVisualization/state-management.domain.md
-- docs/domainspecs/UIVisualization/data-source.domain.md
-- docs/domainspecs/UIVisualization/coding-standards.domain.md
-- (+ selected) docs/domainspecs/UIVisualization/chart-<name>.md
-
-## /aw-spec-analyze
-- docs/domainspecs/UIVisualization/clean-architecture.domain.md
-- docs/domainspecs/UIVisualization/component-contracts.domain.md
-- docs/domainspecs/UIVisualization/charting-standards.domain.md
-- docs/domainspecs/UIVisualization/coding-standards.domain.md
-- (+ selected) docs/domainspecs/UIVisualization/chart-<name>.md
-
-## /aw-spec-implement
-- docs/domainspecs/UIVisualization/folder-structure.domain.md
-- docs/domainspecs/UIVisualization/clean-architecture.domain.md
-- docs/domainspecs/UIVisualization/state-management.domain.md
-- docs/domainspecs/UIVisualization/data-source.domain.md
-- docs/domainspecs/UIVisualization/charting-standards.domain.md
-- docs/domainspecs/UIVisualization/component-contracts.domain.md
-- docs/domainspecs/UIVisualization/coding-standards.domain.md
-- docs/domainspecs/UIVisualization/testing.domain.md
-- (+ selected) docs/domainspecs/UIVisualization/chart-<name>.md   ← one per selected chart
-
-## /aw-spec-fast-implement
-
-> Fast path collapsing plan + tasks + analyze + implement into one pass. Deduplicated union of
-> those headings. Load **once** for the whole pass — do not reload per phase.
-
-- docs/domainspecs/UIVisualization/folder-structure.domain.md
-- docs/domainspecs/UIVisualization/clean-architecture.domain.md
-- docs/domainspecs/UIVisualization/state-management.domain.md
-- docs/domainspecs/UIVisualization/data-source.domain.md
-- docs/domainspecs/UIVisualization/charting-standards.domain.md
-- docs/domainspecs/UIVisualization/component-contracts.domain.md
-- docs/domainspecs/UIVisualization/coding-standards.domain.md
-- docs/domainspecs/UIVisualization/testing.domain.md
-- (+ selected) docs/domainspecs/UIVisualization/chart-<name>.md
-
-## /aw-spec-minimal-implementation
-
-> Single-step set — the per-domain knob. Loads the core charting rules + the selected chart files
-> to implement in one pass. For an audited build use `## /aw-spec-fast-implement`.
-
-- docs/domainspecs/UIVisualization/domain-requirements.md
-- docs/domainspecs/UIVisualization/folder-structure.domain.md
-- docs/domainspecs/UIVisualization/clean-architecture.domain.md
-- docs/domainspecs/UIVisualization/charting-standards.domain.md
-- docs/domainspecs/UIVisualization/component-contracts.domain.md
-- docs/domainspecs/UIVisualization/state-management.domain.md
-- (+ selected) docs/domainspecs/UIVisualization/chart-<name>.md
-
----
-
-## Quick reference (command → core file count, excluding per-chart)
-
-| Command | Core domain rule files | + per selected chart |
-|---|---|---|
-| /aw-spec-constitution | 1 | — |
-| /aw-spec-specify | 4 | 1 each |
-| /aw-spec-clarify | 3 | resolve selection |
-| /aw-spec-plan | 8 | 1 each |
-| /aw-spec-tasks | 7 | 1 each |
-| /aw-spec-analyze | 4 | 1 each |
-| /aw-spec-implement | 8 | 1 each |
-| /aw-spec-fast-implement | 8 | 1 each |
-| /aw-spec-minimal-implementation | 6 | 1 each |
-
-> "all plots" = +10 chart files. A 3-chart project = +3.

package/assets/docs/domainspecs/UIVisualization/component-contracts.domain.md

@@ -1,67 +0,0 @@
-# Component Contracts (Adapters) — UI Visualization Domain
-
-> The props-driven contract and the adapter pattern. NON-NEGOTIABLE.
-> Commands: `/aw-spec-plan`, `/aw-spec-tasks`, `/aw-spec-implement`.
-
-## Props-driven, domain-agnostic
-
-Every generic chart is **fully data-driven**: the caller supplies data, labels, colours, axis
-types, and thresholds. A generic chart has **no** knowledge of the domain — the same `BubbleChart`
-serves drug potency, portfolio risk, and product effort/impact.
-
-Contract for a generic chart's props:
-- **Data first** — required positional-feel props (`matrix`, `series`, `curves`, `arms`,
-  `points`, `panels`, `nodes`/`edges`, `groups`, `dimensions`/`traces`).
-- **Labels explicit** — axis/legend/unit labels are required where the chart can't sensibly
-  default them; never hard-code a domain word.
-- **Colours optional** — default from the shared palette; accept overrides per series.
-- **`height?` optional** — omit for responsive fill (see [[charting-standards.domain]]).
-- **`meta`/`metadata`** — open `Record<string,…>` for tooltip enrichment, never typed to a domain.
-
-## The adapter pattern
-
-A **thin adapter** is the only place domain types meet a chart. It maps a project type into the
-generic chart's props and adds domain labels/colours. Adapters live in `components/charts/`
-(NOT in `generic/`).
-
-```tsx
-// Adapter: domain TrialArm[] → SurvivalCurveChart
-'use client'
-import { SurvivalCurveChart } from '@/components/charts/generic'
-import type { TrialArm } from '@/lib/types/pharma'
-
-export default function KaplanMeierChart({ arms, height }: { arms: TrialArm[]; height?: number }) {
-  return (
-    <SurvivalCurveChart
-      arms={arms.map(a => ({
-        label: a.name, color: a.color, medianTime: a.medianSurvival,
-        points: a.points.map(p => ({ time: p.time, survival: p.survival,
-          ciLower: p.ciLower, ciUpper: p.ciUpper, nAtRisk: p.nAtRisk })),
-      }))}
-      timeLabel="Days" survivalLabel="Survival (%)" medianLabel="mOS"
-      curveType="OS" pValue="< 0.001" showCI height={height}
-    />
-  )
-}
-```
-
-## When to skip the adapter
-
-If a page already holds data in a generic shape (or the project is itself generic), call the
-generic chart directly from the page with inline props — no adapter needed. Adapters exist to
-keep **domain vocabulary out of pages** and **out of the generic ring**.
-
-## Rules
-
-- One adapter per (domain-type → chart) pairing; name it for the domain concept
-  (`CompoundScatterPlot`, `BiomarkerHeatmap`), not the chart.
-- Adapters are **pure mapping** — no data fetching, no store mutation; they receive data as props.
-- Never widen a generic chart's props with a domain field — add the field to `meta`/`metadata`
-  instead, or map it to an existing generic prop.
-- Keep generic props **serialisable** (numbers, strings, arrays) so re-render diffing stays cheap
-  (see [[charting-standards.domain]]).
-
-## Related
-- [[charting-standards.domain]] — the base every chart builds on
-- [[clean-architecture.domain]] — adapter is the dependency seam
-- All `chart-*` files specify each chart's exact prop contract.

package/assets/docs/domainspecs/UIVisualization/data-source.domain.md

@@ -1,68 +0,0 @@
-# Data Source Abstraction — UI Visualization Domain
-
-> How chart data enters the app. NON-NEGOTIABLE.
-> Commands: `/aw-spec-plan`, `/aw-spec-tasks`, `/aw-spec-implement`.
-
-## Three source modes, one contract
-
-The same dataset shape feeds the charts regardless of origin — the **repository/specification**
-analog for the front-end:
-
-| Mode | Phase | Origin | Wiring |
-|---|---|---|---|
-| `sample` | 1 | hard-coded `lib/sample-data` | default; renders on first paint |
-| `excel`  | 1 | client-side `.xlsx` upload (SheetJS) | `ExcelDropZone` → parser → `loadExcel` command |
-| `api`    | 2 | REST endpoint | `ApiDataSource` → `loadExcel`-shaped result |
-
-Charts never know the source — they consume the store dataset. Swapping `sample`→`excel`→`api`
-changes **no chart code** (see [[clean-architecture.domain]], [[state-management.domain]]).
-
-## Excel ingest
-
-- Parsing is **client-side only** (no server) via dynamic `import('xlsx')`.
-- A generic parser returns raw rows per sheet (`Record<string, ParsedWorkbook>`); a
-  **project parser** maps those rows into the domain dataset and dispatches `loadExcel`.
-- The drop-zone validates extension (`.xlsx/.xls`), shows parse state, and reports row counts.
-- Sheet/column names are a **documented contract** shipped with the template
-  (`public/sample-data.xlsx` is the canonical example).
-
-## Canonical example (agent reference)
-
-```ts
-// lib/excel/parse-excel.ts — generic: workbook → rows per sheet
-import type { ExcelRow } from '@/lib/types'
-export type ParsedWorkbook = Record<string, ExcelRow[]>
-
-export async function parseExcelFile(file: File): Promise<ParsedWorkbook> {
-  const XLSX = await import('xlsx')
-  const wb = XLSX.read(await file.arrayBuffer(), { type: 'array' })
-  return Object.fromEntries(
-    wb.SheetNames.map(n => [n, XLSX.utils.sheet_to_json<ExcelRow>(wb.Sheets[n], { defval: null })]),
-  )
-}
-```
-
-```tsx
-// ExcelDropZone wires parse → command
-const wb = await parseExcelFile(file)          // generic rows
-const dataset = mapWorkbookToDomain(wb)        // project mapping
-loadExcel(dataset)                             // store command (see [[state-management.domain]])
-```
-
-## Phase-2 API source (forward contract)
-
-- Add `lib/data-source/ApiDataSource.ts` that fetches and returns the **same dataset shape** the
-  Excel mapper produces, then calls `loadExcel` (or `setSourceMode('api', …)`).
-- Set `NEXT_PUBLIC_API_URL`; no chart or adapter changes.
-
-## Rules
-
-- No server-side Excel handling in Phase 1; keep ingest in the browser.
-- The dataset shape is the single contract between source and charts — version it deliberately.
-- Never parse domain meaning inside `components/charts/generic/` — mapping lives in the project
-  parser / adapter (see [[component-contracts.domain]]).
-
-## Related
-- [[state-management.domain]] — `loadExcel` command
-- [[component-contracts.domain]] — adapters consume the dataset
-- [[clean-architecture.domain]]

package/assets/docs/domainspecs/UIVisualization/domain-requirements.md

@@ -1,110 +0,0 @@
-# DOMAIN REQUIREMENTS (project-specific)
-
-> Project-specific input for the **UI Data-Visualization** domain, **updated independently per
-> project**. The engineering constitution stays domain-agnostic and supreme; this file holds the
-> per-project chart enumeration and the headline tech profile. Detailed charting *rules* are
-> expanded in the sibling files in this folder.
->
-> This domain targets a **Next.js / React / Plotly** front-end (not the .NET backend). It composes
-> with the technology base where applicable and overrides the runtime/stack sections below.
->
-> Replace `<SampleProjectName>` and trim the **Chart Selection** list to the charts the project
-> actually needs.
-
-=====================================================================
-[DOMAIN: Chart Catalog / Features]
-=====================================================================
-The visualization domain is organised as **one feature per chart type**. Each chart is a
-**domain-agnostic, props-driven component** in the generic library, optionally wrapped by a thin
-**adapter** that maps project data into its props (see [[clean-architecture.domain]],
-[[component-contracts.domain]]). The 10 built-in charts:
-
-- **Heatmap** — value matrix, colour-mapped by intensity. See [[chart-heatmap]].
-- **BubbleChart** — multi-dimensional scatter (x · y · size · colour). See [[chart-bubble]].
-- **SCurveChart** — sigmoidal / logistic growth with inflection markers. See [[chart-scurve]].
-- **SurvivalCurveChart** — Kaplan-Meier step curves with CI shading. See [[chart-survival]].
-- **VolcanoPlot** — magnitude vs. significance with threshold quadrants. See [[chart-volcano]].
-- **DimRedPlot** — 2-D scatter of PCA / t-SNE / UMAP coordinates. See [[chart-dimred]].
-- **ParallelCoordinatesPlot** — multi-axis polylines, one per observation. See [[chart-parallel]].
-- **ViolinPlot** — KDE distribution + box per group. See [[chart-violin]].
-- **NetworkGraph** — node-edge graph with built-in spring layout. See [[chart-network]].
-- **TrellisGrid** — small multiples, same chart type per panel. See [[chart-trellis]].
-
-=====================================================================
-[DOMAIN: Chart Selection — REQUIRED INPUT]
-=====================================================================
-> **The developer specifies which charts the project needs when giving the requirement.**
-
-- The requirement names a **subset** of the catalog (e.g. *"Heatmap, Volcano and Survival"*) or
-  says **"all plots"** to include every chart.
-- A skill reads the selection and loads **only** the matching `chart-*` rule files
-  (see [[comandrulemap]]). Unselected charts are **not** scaffolded — their page route, adapter,
-  nav entry, and example data are omitted.
-- Selection keywords are case-insensitive and accept either the **component name**
-  (`BubbleChart`) or the **friendly name** (`Bubble`, `bubble chart`). "all" / "all plots" /
-  "all charts" select the full catalog.
-- Default when unspecified: **ask the developer**; do not assume "all".
-
-| Selection token (any) | Rule file | Component |
-|---|---|---|
-| heatmap | [[chart-heatmap]] | `Heatmap` |
-| bubble · bubble chart | [[chart-bubble]] | `BubbleChart` |
-| s-curve · scurve · sigmoid · dose-response | [[chart-scurve]] | `SCurveChart` |
-| survival · kaplan-meier · km · retention | [[chart-survival]] | `SurvivalCurveChart` |
-| volcano | [[chart-volcano]] | `VolcanoPlot` |
-| dimred · pca · tsne · umap · dimensionality | [[chart-dimred]] | `DimRedPlot` |
-| parallel · parallel-coords · parcoords | [[chart-parallel]] | `ParallelCoordinatesPlot` |
-| violin · distribution | [[chart-violin]] | `ViolinPlot` |
-| network · graph · node-edge | [[chart-network]] | `NetworkGraph` |
-| trellis · facet · small-multiples | [[chart-trellis]] | `TrellisGrid` |
-
-=====================================================================
-[DOMAIN: subsection pointers]
-=====================================================================
-[DOMAIN: Folder Structure Profile]        -> docs/domainspecs/UIVisualization/folder-structure.domain.md
-[DOMAIN: Clean Architecture / Layering]   -> docs/domainspecs/UIVisualization/clean-architecture.domain.md
-[DOMAIN: State / Data Flow (CQRS analog)] -> docs/domainspecs/UIVisualization/state-management.domain.md
-[DOMAIN: Data Source Abstraction]         -> docs/domainspecs/UIVisualization/data-source.domain.md
-[DOMAIN: Charting Standards (base wrap)]  -> docs/domainspecs/UIVisualization/charting-standards.domain.md
-[DOMAIN: Component Contracts (adapters)]  -> docs/domainspecs/UIVisualization/component-contracts.domain.md
-[DOMAIN: Coding Standards Profile]        -> docs/domainspecs/UIVisualization/coding-standards.domain.md
-[DOMAIN: Testing Profile]                 -> docs/domainspecs/UIVisualization/testing.domain.md
-[DOMAIN: Ubiquitous Language]             -> docs/domainspecs/UIVisualization/ui-viz-terms.md
-[DOMAIN: Per-chart rules]                 -> docs/domainspecs/UIVisualization/chart-<name>.md (load per selection)
-
-=====================================================================
-[DOMAIN: Tech Profile (overrides technology stack section)]
-=====================================================================
-- **Framework:** Next.js 16 (App Router, Turbopack); React 19; TypeScript 5 strict.
-- **Charting:** Plotly.js (`plotly.js-dist-min`) loaded via a single SSR-safe base wrapper
-  (`PlotlyChart`) using dynamic import (see [[charting-standards.domain]]).
-- **State:** Zustand 5 (see [[state-management.domain]]).
-- **Data ingest:** SheetJS (`xlsx`) client-side; optional REST `ApiDataSource` for Phase 2
-  (see [[data-source.domain]]).
-- **Styling:** Tailwind CSS 3 + dark "glass" theme (see [[charting-standards.domain]]).
-- **Scaffold source:** `templates/AppWeaver.UI.Visualization` (generic) and
-  `templates/features/UIVisualization.PharmaReference` (reference); packed under
-  `docs/UI.Visualization/` (see PACKAGING.md there).
-
-=====================================================================
-[DOMAIN: Platform Topology]
-=====================================================================
-- Target runtime: static-export or Node SSR (Vercel, container, or any static host). No backend
-  required for Phase 1 — charts render from sample/Excel data fully client-side.
-- Phase 2 wires a REST API behind the `data-source` abstraction with **zero chart changes**
-  (see [[data-source.domain]]).
-- Performance targets: first chart interactive < 1.5 s on a warm cache; a single Plotly chart
-  re-render < 100 ms for typical (≤ 5k-point) datasets.
-
-=====================================================================
-[DOMAIN: Governance Overrides]
-=====================================================================
-- The **generic chart library is closed for domain logic** — additions/edits there require review
-  by a UI Principal Engineer (no project- or domain-specific code in `components/charts/generic/`).
-- New chart types beyond the 10-chart catalog require a constitution amendment + a new
-  `chart-<name>.md` rule file authored to the same contract.
-
-## Related
-- [[folder-structure.domain]] · [[clean-architecture.domain]] · [[state-management.domain]] ·
-  [[data-source.domain]] · [[charting-standards.domain]] · [[component-contracts.domain]] ·
-  [[coding-standards.domain]] · [[testing.domain]] · [[ui-viz-terms]] · [[comandrulemap]]

package/assets/docs/domainspecs/UIVisualization/folder-structure.domain.md

@@ -1,55 +0,0 @@
-# Folder Structure — UI Visualization Domain
-
-> Next.js App-Router layout for the visualization front-end. NON-NEGOTIABLE.
-> Commands: `/aw-spec-plan`, `/aw-spec-tasks`, `/aw-spec-implement`. Replace `<SampleProjectName>`.
-
-## Layout
-
-```
-<SampleProjectName>/                         (sentinel: AppWeaver.UI.Visualization)
-  package.json · tsconfig.json · next.config.ts · tailwind.config.ts
-  public/                                     static assets + sample-data.xlsx
-  scripts/                                    generate-sample-excel.mjs (optional)
-  src/
-    app/                                      App Router — one route folder per SELECTED chart
-      layout.tsx                              root layout: <TopNav/> + bg-mesh
-      globals.css                             theme tokens, glass/gradient classes, animations
-      page.tsx                                catalog/dashboard landing
-      <chart-route>/page.tsx                  e.g. heatmap/ bubble/ volcano/ … (only selected)
-    components/
-      charts/
-        PlotlyChart.tsx                       SSR-safe Plotly base wrapper  (see [[charting-standards.domain]])
-        generic/                              ← DOMAIN-AGNOSTIC chart library (closed to domain logic)
-          index.ts                            barrel export
-          Heatmap.tsx · BubbleChart.tsx · SCurveChart.tsx · SurvivalCurveChart.tsx
-          VolcanoPlot.tsx · DimRedPlot.tsx · ParallelCoordinatesPlot.tsx
-          ViolinPlot.tsx · NetworkGraph.tsx · TrellisGrid.tsx
-        <DomainAdapter>.tsx                   thin adapters (project-specific)  (see [[component-contracts.domain]])
-      layout/TopNav.tsx                       horizontal tab nav (one tab per selected chart)
-      excel-loader/ExcelDropZone.tsx          drag-drop ingest  (see [[data-source.domain]])
-      data-table/ · ui/                       optional supporting components
-    lib/
-      types/                                  shared + domain data types
-      utils.ts                                cn(), formatters, curve generators
-      excel/                                  workbook parser  (see [[data-source.domain]])
-    store/
-      data-store.ts                           Zustand store  (see [[state-management.domain]])
-```
-
-## Rules
-
-- The **generic chart library** lives only in `components/charts/generic/` and is
-  **domain-agnostic** — no project types, no business logic, no hard-coded labels
-  (see [[clean-architecture.domain]], [[component-contracts.domain]]).
-- **One route folder per selected chart** under `src/app/`; unselected charts have **no**
-  route, no nav tab, no example data (see [[domain-requirements]] chart-selection).
-- Domain **adapters** sit in `components/charts/` (NOT inside `generic/`) and map project data
-  to generic props.
-- Cross-cutting files (`PlotlyChart.tsx`, `globals.css`, `TopNav.tsx`, `data-store.ts`,
-  the base config files) MUST stay where the AppWeaver template places them.
-- `@/*` path alias maps to `./src/*` — import charts as
-  `@/components/charts/generic`.
-
-## Related
-- [[clean-architecture.domain]] · [[component-contracts.domain]] · [[charting-standards.domain]] ·
-  [[state-management.domain]] · [[data-source.domain]]

package/assets/docs/domainspecs/UIVisualization/state-management.domain.md

@@ -1,67 +0,0 @@
-# State Management (CQRS analog) — UI Visualization Domain
-
-> The front-end read/write separation. NON-NEGOTIABLE.
-> Commands: `/aw-spec-plan`, `/aw-spec-tasks`, `/aw-spec-implement`.
-
-## Read / write separation
-
-CQRS maps to the client store as **queries = selectors** and **commands = actions**:
-
-- **Queries (reads)** — components read slices of the Zustand store via the hook
-  (`const { compounds } = useDataStore()`). Reads are pure; no side effects in render.
-- **Commands (writes)** — every mutation is a **named store action**, never a raw `set` from a
-  component. Actions: `loadExcel(partial)`, `resetToSample()`, `toggleCurve(id)`,
-  `setSourceMode(mode, fileName)`.
-
-A component MUST NOT mutate store state directly — it dispatches an action, exactly as a backend
-endpoint dispatches a command via the mediator instead of touching the `DbContext`.
-
-## Store shape
-
-- A single `useDataStore` (Zustand) holds: the active **dataset** (the project's chart data), the
-  **source mode** (`'sample' | 'excel' | 'api'`), and any **view state** (e.g. selected series ids).
-- The store seeds from **sample data** so charts render on first paint with zero backend
-  (see [[data-source.domain]]).
-- Loading new data is a single command that swaps the dataset and flips `sourceMode` — charts
-  re-render reactively with no per-chart wiring.
-
-## Canonical example (agent reference)
-
-```ts
-// store/data-store.ts
-'use client'
-import { create } from 'zustand'
-import { SAMPLE } from '@/lib/sample-data'
-
-type SourceMode = 'sample' | 'excel' | 'api'
-
-interface DataStore {
-  dataset: typeof SAMPLE
-  sourceMode: SourceMode
-  // commands (writes) — the ONLY way to mutate
-  loadExcel: (partial: Partial<typeof SAMPLE>) => void
-  resetToSample: () => void
-}
-
-export const useDataStore = create<DataStore>((set) => ({
-  dataset: SAMPLE,
-  sourceMode: 'sample',
-  loadExcel: (partial) =>
-    set(s => ({ dataset: { ...s.dataset, ...partial }, sourceMode: 'excel' })),
-  resetToSample: () => set({ dataset: SAMPLE, sourceMode: 'sample' }),
-}))
-```
-
-## Rules
-
-- One store module (`store/data-store.ts`). Split into slices only when it exceeds ~150 lines.
-- Actions are the command surface — name them as verbs; keep them pure-ish (compute → `set`).
-- Cross-component data load may also broadcast a `window` `CustomEvent`
-  (`appweaver:excel-loaded`) — the front-end analog of a **domain event**.
-- No data fetching inside the store for Phase 1; the **data-source** layer owns ingest and hands
-  the result to a command (see [[data-source.domain]]).
-
-## Related
-- [[data-source.domain]] — where datasets come from
-- [[clean-architecture.domain]] — the data layer feeds pages, never imports charts
-- [[component-contracts.domain]]