docs: record final semantic verification

This commit is contained in:
2026-08-09 00:31:24 +02:00
parent fb95be3e62
commit b622295614
+11 -9
View File
@@ -1,6 +1,6 @@
# ThothII — Project State
> Starting-point snapshot for new sessions. Last updated: 2026-08-08 (final review fix round 1).
> Starting-point snapshot for new sessions. Last updated: 2026-08-08 (final verification).
> Point a fresh session here ("read PROJECT_STATE.md") before substantial work.
## Internal Qdrant + Ollama semantic infrastructure — LIVE 2026-08-08
@@ -37,7 +37,7 @@
volume resolution, and cleanup removes the lock only when its ownership labels still match.
- **Verification recorded for Task 13 final audit.** On Apple M4 Pro
(`Darwin 25.5.0`, Docker Server `29.6.2 linux/arm64`), harness pytest passed
**819 passed / 4 deselected**; backend Vitest passed **464/464** plus TypeScript and build;
**827 passed / 4 deselected**; backend Vitest passed **477/477** plus TypeScript and build;
frontend Vitest passed **374/374** plus TypeScript and build; `git diff --check` passed.
Deployment contracts passed:
`test-default-compose.sh`, `test-unified-compose.sh`, `test-internal-semantic-compose.sh`,
@@ -68,13 +68,15 @@
schema-v3 operator manual or supported runtime deployment path retains external vector or
embedding endpoint coupling.
- **Final review fix verification.** Backend Vitest passed **477/477** plus TypeScript and build;
harness pytest passed **824 passed / 4 deselected** with the existing 74 warnings; touched Python
files are Ruff-clean. The deterministic backup/restore safety test proves lock ownership,
backup–backup and backup–restore contention, rollback, and cleanup. Internal semantic Compose
and no-deployment-coupling contracts pass. A fresh one-shot unified deployment smoke reached its
pre-existing `thothctl` bad-candidate rollback scenario and failed there before backup/restore;
its exact resource-cleanup proof passed, so this run is recorded as a limitation, not as a
successful revalidation of the earlier Task 13 unified-smoke result.
harness pytest passed **827 passed / 4 deselected** with the existing 74 warnings; touched Python
files are Ruff-clean. The complete `thothctl` Go suite, deterministic backup/restore safety test,
internal semantic Compose contract, no-deployment-coupling gate, CPU/offline semantic smoke, and
unified deployment smoke all pass on `fb95be3`. The intermittent `thothctl` rollback failure was
traced to Docker Desktop alternating equivalent bind sources between `/private/...` and
`/host_mnt/private/...`; the persistence fingerprint now normalizes only the known macOS Docker
Desktop aliases while retaining distinct Linux `/host_mnt` paths. The rollback-only smoke passed
twice consecutively after the fix, and the subsequent full unified smoke passed with exact
cleanup.
## Historical snapshots and archived reference notes