docs: record session summary deployment
This commit is contained in:
+24
-1
@@ -1,8 +1,31 @@
|
|||||||
# ThothII — Project State
|
# ThothII — Project State
|
||||||
|
|
||||||
> Starting-point snapshot for new sessions. Last updated: 2026-07-21 (local Pi user-auth wiring and startup error handling live).
|
> Starting-point snapshot for new sessions. Last updated: 2026-07-23 (session summary redesign live).
|
||||||
> Point a fresh session here ("read PROJECT_STATE.md") before substantial work.
|
> Point a fresh session here ("read PROJECT_STATE.md") before substantial work.
|
||||||
|
|
||||||
|
## Session summary redesign — LIVE 2026-07-23
|
||||||
|
|
||||||
|
- Session documents are projected at read time in outcome-first order: original question,
|
||||||
|
final SQL, persisted data preview, revised question, assumptions, one memory list, then
|
||||||
|
remaining technical documents. This applies to existing filesystem and repository-backed
|
||||||
|
sessions without rewriting their artifacts.
|
||||||
|
- Final SQL has an always-visible clipboard action. All prose, including original/revised
|
||||||
|
questions, assumptions, memory content, and remaining decisions, renders as Markdown.
|
||||||
|
- Memories are shown once, approved before declined. The generic decision list suppresses
|
||||||
|
memory ledger records plus `phase_approved`, `phase_auto_approved`, `table_approved`,
|
||||||
|
`table_promoted`, and `column_promoted`.
|
||||||
|
- The session summary has its own accessible pointer/keyboard resize separator, persists its
|
||||||
|
width independently from Model activity, reaches 50% when space permits, and preserves a
|
||||||
|
512 px right-side minimum on narrower desktop layouts.
|
||||||
|
- Verification: harness **861 passed / 5 L2 deselected**, Pi gate **163/163**, full frontend
|
||||||
|
suite, TypeScript check, production build, Ruff, and `git diff --check` all passed. A live
|
||||||
|
pre-existing session returned the new canonical order and none of the suppressed decision
|
||||||
|
labels. Compose rebuilt and force-recreated both services; core image
|
||||||
|
`sha256:3566d1258b956f8ca96d3b5ff8f625503247a7fd3b0dffe77020ae03956403d8`
|
||||||
|
is healthy and frontend image
|
||||||
|
`sha256:8311ca1308b459ece7236bf143da7b1a226ff4082fed924e1b5a207c24b6ca29`
|
||||||
|
is running. Frontend and `/api/health` both returned HTTP 200.
|
||||||
|
|
||||||
## Local Pi user auth + startup failure handling — LIVE 2026-07-21
|
## Local Pi user auth + startup failure handling — LIVE 2026-07-21
|
||||||
|
|
||||||
- The PSD Docker profile now bind-mounts the configurable host `PI_AUTH_FILE` read-only at
|
- The PSD Docker profile now bind-mounts the configurable host `PI_AUTH_FILE` read-only at
|
||||||
|
|||||||
Reference in New Issue
Block a user