ltcai 4.0.1 → 4.2.0

package/docs/V4_2_VALIDATION_REPORT.md

@@ -0,0 +1,89 @@
+# Lattice AI v4.2.0 — Validation Report
+
+Date: 2026-06-12
+Commit under validation: v4.2.0 release commit on `main` after `v4.1.0`
+
+## Result
+
+v4.2.0 validation passed for the implemented Brain Core package, storage
+abstraction, SQLite default runtime, encrypted archives, generated OpenAPI
+client, frontend/system controls, Docker-backed Postgres/pgvector migration,
+desktop check, and release artifacts.
+
+## Commands
+
+| Check | Command | Result |
+| --- | --- | --- |
+| OpenAPI generation | `npm run frontend:openapi` | PASS — 313 paths |
+| Python compile | `npm run check:python` | PASS — 235 modules |
+| Ruff | `node scripts/run_python.mjs -m ruff check .` | PASS |
+| Unit tests | `npm run test:unit -- --tb=short` | PASS — 593 passed, 2 warnings |
+| Live Postgres migration | `LTCAI_LIVE_POSTGRES_DOCKER_CONSENT=1 node scripts/run_python.mjs -m pytest tests/integration/test_v42_postgres_migration_live.py -v --tb=short` | PASS |
+| Live integration | `LTCAI_TEST_BASE_URL=http://127.0.0.1:8899 npm run test:integration -- --tb=short` | PASS — 9 passed, 1 skipped |
+| Frontend lint | `npm run lint` | PASS |
+| TypeScript + VS Code extension build | `npm run typecheck` | PASS |
+| Vite app build | `npm run build:assets` | PASS |
+| Playwright visual/offline suite | `npx playwright test tests/visual/v3.spec.js` | PASS — 12 passed |
+| Tauri desktop check | `npm run desktop:tauri:check` | PASS |
+| Release artifacts | `npm run release:artifacts` | PASS |
+| Artifact validation | `npm run release:validate` | PASS |
+| Wheel smoke | `node scripts/run_python.mjs scripts/wheel_smoke.py --wheel dist/ltcai-4.2.0-py3-none-any.whl` | PASS |
+| npm dry-run | `npm pack --dry-run` | PASS |
+
+## Storage-Specific Coverage
+
+- `test_v42_brain_storage.py` validates:
+  - `lattice_brain` package exports a working Knowledge Graph store.
+  - `BrainCore` constructs SQLite graph and durable conversation stores.
+  - default storage is SQLite.
+  - explicit Postgres without DSN fails honestly.
+  - SQLite-to-Postgres migration planning preserves all user tables and
+    idempotence keys, including rowid-less FTS5 shadow tables with primary
+    keys.
+  - Docker setup does not start without explicit consent.
+  - encrypted `.latticebrain` archives round-trip DB + blobs.
+  - portability service exposes storage status, dry-run migration, and archives.
+- `test_v42_postgres_migration_live.py` validates the explicit-consent Docker
+  path with `pgvector/pgvector:pg16`:
+  - live pgvector Postgres starts through `DockerPostgresWizard`.
+  - v4 SQLite brain data copies without source mutation.
+  - table row counts match after migration.
+  - rerunning migration is idempotent.
+  - pgvector extension and vector distance ordering work.
+  - explicit Postgres runtime paths fail closed instead of falling back to
+    SQLite.
+  - the test Compose stack is torn down with volumes after validation.
+- Existing vector tests continue to validate real local vector search.
+- Existing portability tests continue to validate JSON export/import and ZIP
+  backup/restore.
+
+## Generated Artifacts
+
+- `dist/ltcai-4.2.0-py3-none-any.whl`
+- `dist/ltcai-4.2.0.tar.gz`
+- `dist/ltcai-4.2.0.vsix`
+- `ltcai-4.2.0.tgz`
+
+## Warnings
+
+- Vite reports the main app chunk is larger than 500 kB; build succeeds.
+- Tauri/Rust reports transitive `block v0.1.6` future-incompatibility warning;
+  cargo check succeeds.
+- Release validation warns that older artifacts remain in `dist/`; exact
+  v4.2.0 artifact validation passes and publish docs require exact filenames.
+- Wheel smoke in a clean venv reports MLX unavailable; expected when optional
+  local MLX runtime is not installed. `/health` still reports version `4.2.0`.
+
+## Docker/Postgres Validation
+
+Owner granted explicit Docker consent for the v4.2.0 Postgres/pgvector
+migration test. Docker was used only for this validation path. The live test
+started a local `pgvector/pgvector:pg16` Postgres service, migrated a seeded v4
+SQLite brain database, verified row counts, idempotence, pgvector distance
+search, fail-closed Postgres behavior, and then removed the test Compose stack
+and volumes. SQLite remains the default and fully validated runtime.
+
+## External Registries
+
+No PyPI, npm Registry, VS Code Marketplace, Open VSX, or other external
+registry publish command was run.

package/docs/V4_DIGITAL_BRAIN_RECOVERY.md

@@ -5,24 +5,27 @@
 > completed analysis. **Update this file before ending any phase and before any
 > likely session/context/usage limit.**
 >
-> Last updated: 2026-06-12 — v4.0.1 maintenance release prep; T9 remainder remains closed
+> Last updated: 2026-06-12 — v4.2.0 Brain Core/storage release; Remaining Gaps remain empty
 
 ---
 
-## 0. RC STATUS (final)
-
-**v4.0.1 packages the `main` commits after tag `v4.0.0`; implementation gaps are empty.**
-Latest verified implementation milestone: T9 remainder closed with full unit coverage
-(`585 passed`), ruff, Python compile, `npm run lint`, `npm run build:assets`,
-Playwright v3 visual coverage, Python sdist/wheel build, installed-wheel smoke,
-and `npm pack --dry-run`.
-The v4.0.1 release process builds and validates artifacts for GitHub Release
-attachment only. It does not publish to PyPI, npm Registry, VS Code Marketplace,
-Open VSX, or production deployment targets.
-v4.0.1 validation completed: Python compile, ruff, 585 unit tests, 9 live
-integration tests, frontend lint, VS Code typecheck, 16 Playwright visual tests,
-Python wheel/sdist build, npm tgz build, VSIX build, release artifact
-validation, wheel smoke, and npm pack dry-run all passed.
+## 0. RELEASE STATUS (v4.2.0)
+
+**v4.2.0 extracts Brain Core into `lattice_brain` and adds the pluggable
+storage layer on top of `main` after v4.1.0; implementation gaps remain empty.**
+Latest implementation milestone: FastAPI now constructs the Knowledge Graph and
+durable conversation runtime through `lattice_brain.BrainCore`. The new
+`lattice_brain.storage` package provides `StorageEngine`, `SQLiteEngine`,
+`PostgresEngine`, explicit-consent Docker Postgres setup, SQLite-to-Postgres
+migration tooling, sqlite-vec capability reporting with honest cosine fallback,
+and encrypted `.latticebrain` archive create/restore. Owner-granted Docker
+validation covered live `pgvector/pgvector:pg16` migration integrity,
+rowid-less FTS5 shadow tables, idempotent reruns, pgvector distance search,
+and fail-closed Postgres behavior.
+The v4.2.0 release process builds validated artifacts, tags `v4.2.0`, and
+creates a GitHub Release only. It does not publish to PyPI, npm Registry,
+VS Code Marketplace, Open VSX, or deploy to production targets.
+v4.2.0 validation report: `docs/V4_2_VALIDATION_REPORT.md`.
 Remaining implementation gaps: **none**.
 Owner-only blockers: pptx history rewrite (requires force-push/owner decision)
 and consent-gated production embedder provisioning (silent default download is
@@ -30,11 +33,13 @@ not permitted).
 
 ## Remaining Gaps
 
-None. The T9 remainder was closed on main with legacy page deletion, `/app`
-parity views, token-native account UI, en/ko i18n, approval/run inbox,
-workflow-trigger controls, Brain Network UI, chat context-trace panel, and
-Knowledge Graph provenance coverage surfaced in the SPA. Owner-only blockers
-above are intentionally not implementation gaps.
+None. v4.2.0 closes the backend Brain Core/storage rebuild on top of the
+already-empty v4.1.0 gap list: `lattice_brain` is the independent package
+boundary, SQLite remains the default engine, Postgres/pgvector is opt-in and
+honestly unavailable when dependencies or DSN are missing, Docker setup is
+consent-gated, migration planning is non-destructive, and encrypted
+`.latticebrain` archives round-trip the SQLite brain DB plus blobs. Owner-only
+blockers above are intentionally not implementation gaps.
 
 ## 1. Program Charter (from the user's v4.0.0 directive)
 
@@ -220,9 +225,9 @@ Track log (update at every track boundary):
   and KG provenance coverage. en/ko i18n runtime backs routes, shell, and new
   parity views; `scripts/lint_v3.mjs` gates it. Visual coverage moved to the
   v3 surface and legacy-page specs were retired.
-- T9-canvas agent left static/v3/js/views/graph-canvas.js (509 lines,
-  node --check passes) but NEVER rewired knowledge-graph.js — file kept
-  uncommitted in tree; integration outstanding.
+- Superseded note: an early T9-canvas handoff left a static v3 graph-canvas file
+  unrewired, but this is no longer active work. v4.1.0 removed `static/v3` and
+  replaced the graph surface with the React/Vite/Cytoscape Brain view.
 - NOTE: The old T3d queue is closed. T9 parity surfaces remain active with
   full contracts in this file + the plan.
   - **T3e**: docs/kg-schema.md regenerated from enums.
@@ -278,9 +283,9 @@ the canonical Phase A record.**
      services, 27 API routers + `server_app.py` at 1,554 lines). Legacy root
      modules ~6,720 lines incl. `knowledge_graph.py` **4,633 lines**,
      `kg_schema.py` 521, `llm_router.py` 775, `mcp_registry.py` 791.
-   - Frontend: `/app` v3 SPA (`static/v3/`, token-native) is primary; legacy
-     static HTML pages were later removed and compatibility routes redirect
-     into `/app`.
+  - Historical frontend baseline: `/app` static v3 SPA (`static/v3/`,
+     token-native) was primary at v3.6.0. v4.1.0 later replaced it with the
+     React/Vite SPA in `frontend/` and `static/app/`.
    - Repo root clutter: ~30 `ltcai-*.tgz` tarballs, `ltcai-0.3.1/` extracted copy,
      logs, `chat_history.json`, 15MB pptx — most likely untracked; verify with
      `git ls-files` before cleaning.

package/frontend/index.html

@@ -0,0 +1,24 @@
+<!doctype html>
+<html lang="en">
+  <head>
+    <meta charset="UTF-8" />
+    <meta name="viewport" content="width=device-width, initial-scale=1.0, viewport-fit=cover" />
+    <meta name="color-scheme" content="dark light" />
+    <title>Lattice AI · Digital Brain</title>
+    <link rel="manifest" href="/manifest.json" />
+    <link rel="icon" type="image/png" sizes="32x32" href="/icons/favicon-32.png" />
+    <script>
+      (function () {
+        try {
+          var theme = localStorage.getItem("lattice.theme");
+          if (theme === "light" || theme === "dark") document.documentElement.dataset.theme = theme;
+        } catch (e) {}
+      })();
+    </script>
+  </head>
+  <body>
+    <div id="root"></div>
+    <noscript>Lattice AI requires JavaScript for the local Digital Brain desktop shell.</noscript>
+    <script type="module" src="/src/main.tsx"></script>
+  </body>
+</html>