Skip to content

Epic: performance and SQLite source-of-truth cleanup #138

Description

@ApocDev

Implement the July 2026 performance audit as targeted changes.

  • Remove unsafe project-data process caches and fix connection lifecycle
  • Make solved block projections explicitly valid/stale in SQLite
  • Eliminate duplicate editor solves and move module suggestions off the hot path
  • Reuse solves during whole-factory rebalance and bulk recomputation
  • Batch recipe browser, TURD, dependency, and assistant query paths
  • Consolidate multi-write mutations and conversation persistence
  • Centralize SQLite pragmas/index maintenance and reduce polling/RPC churn
  • Verify with focused benchmarks, vp check/test/build, and docs updates

The governing constraint is that SQLite remains the project source of truth; request-scoped batching is acceptable, but project data must not depend on opaque process-cache invalidation.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area: dataData-dump import, synthetic recipes, cost analysisarea: plannerProduction block / planning modelarea: webWeb UI (React/TanStack/vite-plus)enhancementNew feature or requestepicTracks a group of related issues (parent of sub-issues)

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions