test: verify portable workspace registry end to end

PROJECT_STATE.md

@@ -3,6 +3,32 @@
 > 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.
 
+## Portable Git workspace registry — source integration (2026-08-04)
+
+- **Source of truth and scope.** The canonical workspace repository is a generic Git remote,
+  configured only by `THT_WORKSPACE_GIT_REMOTE` and `THT_WORKSPACE_GIT_BRANCH` (there is no
+  committed PSD/Chirone remote or branch default). Both a local Docker installation and a server
+  persist its checkout, validated snapshots, state, and locks at `/data/workspace-registry`.
+  Connector endpoints, transport choices, and secret-file paths remain local bindings; secret
+  contents are never stored in Git, API responses, browser storage, diagnostics, or bundles.
+- **Migration and session safety.** Schema-v2 descriptors are operational; legacy descriptors are
+  visible as `migration_required` until migrated by the documented operator workflow. New sessions
+  persist workspace ID and immutable Git revision. Resume resolves that historical snapshot, while
+  retention preserves every revision referenced by an open, closed, or failed unarchived manifest.
+  Reconciliation runs only with a complete local installation list or an administrator's complete
+  server list, never from a remote user's partial view.
+- **Operator manuals.** Follow [the local manual](docs/install/local-workspace-registry.md) for
+  macOS/Windows/Linux Docker Desktop deployment and [the server manual](docs/install/server-workspace-registry.md)
+  for Gitea-compatible remotes, reverse proxy, migration, backup, and recovery. The release
+  workflow is Git review/push → installation pull → validate → local diagnostic test → browser-local
+  workspace/model/reasoning selection → revision-pinned session.
+- **Verification recorded for this source branch.** `git diff --check` passed; backend Vitest
+  **365/365** and TypeScript passed; frontend Vitest **398/398** and TypeScript passed; the
+  harness document regression passed **10/10**. `./scripts/workspace-registry-smoke.sh`, both
+  installation-document verifier profiles, and a final unrestricted full harness run remain the
+  release commands to execute in the deployment environment; the local long-running harness run
+  was intentionally cancelled before it produced a final result.
+
 ## Session summary redesign — LIVE 2026-07-23
 
 - Session documents are projected at read time in outcome-first order: original question,