FE-566: Generic knowledge layer schema and sidebar projection

[lunelson]

feat: surface framing items through the generic knowledge seam

feat: project dependency relationships through the entity seam

[linear]

FE-566 Generic knowledge layer schema and sidebar projection

Introduce the broader semantic layer (framing, constraint, decision, assumption, requirement, criterion) with generic provenance and graph edges, then project it into the sidebar without regressing current reads.

Acceptance

• Project state can load and display generic knowledge items and edges from the active path
• Existing resume and hydration behavior stays intact

[lunelson]

• FE-580: Collapse remaining shared transport and review-status type duplication #45
• FE-579: Greenfield/brownfield first-screen + exploration #44
• FE-545: Local-first storage; npx distribution #43
• FE-578: UI refinements; design adaptations & alignments #42
• FE-543: Expanded rich fixture scenarios + reviews + replannings #41
• FE-574: Knowledge workspace review surface + lifecycle API #39
• FE-573: Project dashboard workflow state #38
• FE-542: Criteria-review mode #37
• FE-568: Requirements-review mode #36
• FE-540: Design mode: commitment and exploration #35
• FE-572: Canonical knowledge model foundation + cutover seam #34
• FE-539: Explicit phase outcomes and scope closure #33
• FE-567: Phase-aware observer extraction #32
• FE-566: Generic knowledge layer schema and sidebar projection #28 👈 (View in Graphite)
• FE-564: Flexible turn-response model #27
• FE-559: Migrate: @anthropic-ai/claude-agent-sdk query() -> @anthropic-ai/sdk client.messages.stream() #25
• FE-538: Entity sidebar (read-only) #24
• FE-537: Observer agent + entity persistence #23
• FE-558: UI foundation: shadcn/ui + Tailwind 4 + AI Elements #22
• FE-557: Spike: observer extraction fidelity #21
• FE-556: Structured interview: client UI #20
• FE-555: Parts-based persistence + context builders #19
• FE-554: Structured interview: scope phase #17
• FE-553: Multi-project routing #16
• FE-541: Rich chat UI with tool calls and reasoning rendering #15
• FE-552: Drizzle ORM and core extraction #14
• FE-544: Turn tree schema and API #13
• FE-535: SQLite foundation and project persistence #11
• FE-534: Walking skeleton SDK to SSE to React #10
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[augmentcode]

🤖 Augment PR Summary

Summary: This PR introduces a generic knowledge-item persistence seam and projects the expanded entity model into the workspace sidebar without regressing existing decision/assumption reads.

Changes:

• Adds new DB tables + migration: knowledge_item and turn_knowledge_item for generic knowledge kinds with turn provenance.
• Extends getEntitiesForProject and GET /api/projects/:id/entities to return kind-specific collections (framing, constraints, requirements, criteria) plus a typed relationships[] dependency projection.
• Updates workspace durable entity state to hydrate/refresh the expanded entity snapshot/query payload.
• Expands EntitySidebar with new tabs for generic knowledge kinds and renders dependency “Depends on” lists for decisions/assumptions.
• Adds/updates server + client tests covering generic kind projection, relationship hydration, and sidebar rendering.

Technical Notes: Dependency edges are projected from legacy parent-link tables into a unified depends_on relationship read model while decision/assumption writes remain on legacy tables.

_{🤖 Was this summary useful? React with 👍 or 👎}

[augmentcode]

Review completed. 3 suggestions posted.

Comment augment review to trigger a new review at any time.

[augmentcode]

filter((content) => Boolean(content)) will drop valid empty-string content, which could cause some dependency labels to silently disappear if an entity’s content is ''. If empty strings are possible here, filtering only null/undefined would avoid that edge case.

Severity: low

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}

[augmentcode]

Using the dependency label (entity content) as the React key can collide when multiple dependencies share the same text, which can lead to incorrect list reconciliation/rendering. A stable key derived from the relationship’s identity would avoid content-based collisions.

Other locations where this applies: src/client/components/EntitySidebar.tsx:191

Severity: medium

Other Locations

• src/client/components/EntitySidebar.tsx:191

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}

[augmentcode]

createKnowledgeItem takes kind: KnowledgeKind, which currently includes legacy kinds like 'decision' and 'assumption'; that makes it easy to accidentally write those into knowledge_item while the migration plan keeps them in dedicated tables. Narrowing the accepted kinds for this API would reduce the risk of split-brain entity storage during the transition.

Severity: medium

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}

[lunelson]

Merge activity

• Apr 10, 11:44 AM UTC: A user started a stack merge that includes this pull request via Graphite.
• Apr 10, 11:45 AM UTC: @lunelson merged this pull request with Graphite.