fix build/distribution spec: npm deps not workspace, align configs with sibling projects, resolve review issues

- Replace workspace:* deps with published npm semver ranges (^0.34.49, ^0.1.0)
- Expand package.json: add description, publishConfig, scripts, engines,
  devDependencies, conditional exports with types/default for import+require
- Fix tsup entry names (path-prefixed like ujsx), add target: es2022,
  remove splitting:true (not used by sibling projects)
- Align tsconfig with sibling projects: add lib, noUncheckedIndexedAccess,
  noUnusedLocals, noUnusedParameters, erasableSyntaxOnly, etc.
- Expand vitest.config.ts with include, coverage, and path alias
- Clarify @preact/signals-core as direct dep (not just transitive via ujsx)
- Clarify @alkdev/pubsub is a consumer dependency, not flowgraph's dep
- Fix edge key convention: document composite key format for call graph's
  multi-edge-type scenario (triggered + depends_on between same pair)
- Align OperationEdgeAttrs field naming: use detail+mismatches consistently
  instead of compatibilityDetail
- Add InvalidInputError to error hierarchy (referenced in flowgraph-api but
  was missing)
- Fix undefined attrs.category reference in reactive-execution.md
- Remove internal drafting note from host-configs.md
- Fix ReactiveHostConfig constructor signature inconsistency across docs
- Constrain TemplateEdgeAttrs.edgeType to sequential|conditional only

docs/architecture/host-configs.md

@@ -48,17 +48,13 @@ When ujsx's reconciler calls `HostConfig.createInstance(tag, props, ...)`, the `
 ### Type Parameters
 
 ```typescript
-const graphologyHost: HostConfig<WorkflowTag, Graph, GraphContext>
+const graphologyHost: HostConfig<WorkflowTag, GraphNode, GraphContext>
 ```
 
 - **TTag**: `WorkflowTag`
-- **Instance**: `Graph` (the graphology `DirectedGraph` instance — every element creates a subgraph reference)
+- **Instance**: `GraphNode` (a logical representation of what each template node becomes in the graph)
 - **RootCtx**: `GraphContext` (the root context carrying the graph and metadata)
 
-Wait — this needs refinement. In graphology, instances aren't subgraphs. Let me reconsider.
-
-Actually, the GraphologyHostConfig's `Instance` type is a logical representation of what each template node becomes:
-
 ```typescript
 interface GraphNode {
   key: string;           // The graphology node key