feat: add business domain knowledge extraction and visualization

[Lum1104]

Summary

• Core types: Added domain/flow/step node types, contains_flow/flow_step/cross_domain edge types, DomainMeta interface, Zod schema updates with aliases and .passthrough(), plus saveDomainGraph/loadDomainGraph persistence and node ID normalization
• Dashboard: New domain graph view with DomainClusterNode, FlowNode, StepNode components, DomainGraphView with overview/detail modes (dagre LR layout), view mode toggle pill, domain-aware NodeInfo sidebar, and Vite dev server serving domain-graph.json
• Agent & Skill: domain-analyzer agent definition for LLM-driven domain extraction, /understand-domain skill with two analysis paths (derive from existing graph or lightweight scan)

Implements #61.

Test Plan

• Core: 390 tests pass (23 test files) including 15 new domain-specific tests
• Core build: Clean TypeScript compilation
• Dashboard build: 468 modules, 0 errors
• Manual: Run /understand-domain on a sample project and verify domain graph renders in dashboard
• Manual: Toggle between Domain and Structural views
• Manual: Click domain nodes to drill into flow/step detail view
• Manual: Verify NodeInfo sidebar shows domain-specific details

🤖 Generated with Claude Code

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 9e8b99bc9e

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Preserve domain graph state when setting structural graph

Dashboard fetches /knowledge-graph.json and /domain-graph.json in parallel, but setGraph unconditionally resets viewMode and clears domainGraph. If the domain graph arrives first (common when the structural graph is larger), a later structural response wipes it out, so the Domain toggle/view disappears until a full reload. This makes the new domain view nondeterministic based on response timing.

Useful? React with 👍 / 👎.

[Lum1104]

Code review

Found 3 issues:

1. Race condition: setGraph wipes domainGraph on parallel fetch — Both knowledge-graph.json and domain-graph.json are fetched in independent useEffect hooks on mount. If domain-graph.json resolves first, setDomainGraph stores it, but then setGraph runs and resets domainGraph: null (line 221), silently destroying the loaded domain graph. The view mode toggle disappears with no error.

Understand-Anything/understand-anything-plugin/packages/dashboard/src/store.ts

Lines 219 to 223 in 9e8b99b

	nodeHistory: [],
	viewMode: "structural" as const,
	domainGraph: null,
	activeDomainId: null,
	});

Fetch sites:

Understand-Anything/understand-anything-plugin/packages/dashboard/src/App.tsx

Lines 222 to 224 in 9e8b99b

	if (result.success && result.data) {
	setGraph(result.data);
	setGraphIssues(result.issues);

Understand-Anything/understand-anything-plugin/packages/dashboard/src/App.tsx

Lines 272 to 278 in 9e8b99b

	useEffect(() => {
	fetch(tokenUrl("/domain-graph.json", accessToken))
	.then((res) => {
	if (!res.ok) return null;
	return res.json();
	})
	.then((data: unknown) => {

2. workflow/action aliases silently repurposed — breaking change — workflow was previously aliased to "pipeline" (for CI/CD workflows) and is now changed to "flow" (a domain node type). Similarly action changed from "pipeline" to "step". Any existing LLM-generated graphs using "workflow" for CI/CD pipeline concepts will now silently produce "flow" nodes (business domain type) instead of "pipeline" nodes, corrupting structural knowledge graphs.

Understand-Anything/understand-anything-plugin/packages/core/src/schema.ts

Lines 53 to 57 in 9e8b99b

	business_domain: "domain",
	process: "flow",
	workflow: "flow",
	action: "step",
	task: "step",

3. Double-click handler fires twice on DomainClusterNode — Both the DomainClusterNode component's own onDoubleClick (line 31) and ReactFlow's onNodeDoubleClick callback (line 169) call navigateToDomain for the same event, causing the store action to execute twice per double-click.

Understand-Anything/understand-anything-plugin/packages/dashboard/src/components/DomainClusterNode.tsx

Lines 30 to 32 in 9e8b99b

	onClick={() => selectNode(data.domainId)}
	onDoubleClick={() => navigateToDomain(data.domainId)}
	>

Understand-Anything/understand-anything-plugin/packages/dashboard/src/components/DomainGraphView.tsx

Lines 169 to 175 in 9e8b99b

	const onNodeDoubleClick = useCallback(
	(_: React.MouseEvent, node: Node) => {
	if (node.type === "domain-cluster" && node.data && "domainId" in node.data) {
	navigateToDomain(node.data.domainId as string);
	}
	},
	[navigateToDomain],

🤖 Generated with Claude Code

_{- If this code review was useful, please react with 👍. Otherwise, react with 👎.}