ltcai 11.5.1 → 11.6.0

package/docs/CHANGELOG.md

@@ -4,6 +4,135 @@ The top entry is either the current unreleased main-branch work or the current
 release line. Older entries are historical and may describe behavior as it
 existed at that release.
 
+## [11.6.0] - 2026-08-15 — One Door
+
+### Added
+- **하나의 제품 서버**: `lattice-host`가 **네이티브 420 오퍼레이션 /
+  41 라우트 패밀리**를 원래 경로에 서빙합니다. `mount_table()`이 아홉
+  크레이트의 `MOUNTED` 합집합이고, `(method, path)` 중복은 axum 생성자
+  패닉이 아니라 라우터 생성 **전** 단언으로 실패합니다.
+- **네이티브 KG write 엔진**(`lattice_core::graph_write`): ingest,
+  curation, provenance, taxonomy, 벡터 큐. 32단계 행 단위 패리티 골든과
+  `sqlite_master` 67객체 스키마 대조로 못박혔습니다.
+- **Python 순수 연산 시임 9종**(`/worker/*`): embed, parse, render×4,
+  asr, multimodal/describe, extract. `LATTICEAI_AGENT_TOOL_SEAM` 게이트
+  뒤에 있으며 인증이 디코드보다 먼저 실행됩니다.
+- **HTTP 골든 재생 스위트**: 커밋된 12개 픽스처의 **1,487 케이스**를
+  네이티브 라우트에 재생해 상태줄과 본문을 대조합니다.
+- `rust/fixtures/worker_allowlist.json` — 게이트웨이 프록시 allowlist의
+  단일 출처(**28 라우트**). Python 쪽 `tests/unit/test_worker_allowlist.py`
+  6종이 집합/바이트/결정성/그리디 컨버터/그룹 라벨/"네이티브는 없음"을
+  단언합니다.
+- `pdf` extra (`reportlab`) — `POST /worker/render/pdf`가 지연 임포트하던
+  선언되지 않은 의존성. 없으면 500이 아니라 "렌더러 사용 불가"입니다.
+
+### Changed
+- **Python은 AI 워커입니다.** `create_app`은 사라졌고
+  `latticeai.worker_app:create_worker_app`이 이 패키지가 만드는 유일한
+  애플리케이션이며 **28 라우트**만 서빙합니다. 부트스트랩 10단계 → 7단계,
+  `RuntimeContext` 191 필드 → 47.
+- 그래프 테이블 **17개**의 소유자가 WORKER → RUST_PLATFORM. 단일 writer
+  불변식이 주석이 아니라 테스트입니다.
+- 변경 제안 스테이징·승인·적용이 인프로세스가 되었습니다. 루프는 Review
+  Center와 **같은 문서 핸들**(`GovernanceState`)로 스테이징하고, 적용은
+  네이티브 `write_file`과 같은 샌드박스를 지납니다. unified diff는 CPython
+  `difflib`를 이식한 `pydiff`(`autojunk` 포함)가 만듭니다.
+- 워커 감독자가 uvicorn 팩토리로 기동합니다 —
+  `python -m uvicorn latticeai.worker_app:create_worker_app --factory`.
+  모듈 형태(`-m latticeai.worker_app`)는 `__main__` 가드가 없어 임포트하고
+  즉시 종료합니다.
+- 잡 스케줄러가 `GraphWriter`를 받아 네이티브로 드레인합니다. 이전에는
+  워커에서 이미 사라진 `POST /api/index/drain`을 매 tick 때리고 백오프만
+  쌓았습니다.
+- 공개 릴리스 히스토리와 보안 지원 하한이 **11.0.0**으로 상향
+  (README 표 · `RELEASE_NOTES.md` · `SECURITY.md` · 해당 테스트 동시 수정).
+
+### Removed
+- **Telegram 브리지** — 워커가 된 플랫폼 코드와 함께 삭제.
+  `latticeai.integrations.telegram_bot`은 임포트 불가 목록에 있습니다.
+- **SSO OIDC 로그인/콜백 플로우** — 워커는 `/auth/*`를 마운트하지
+  않습니다. 설정 표면은 유지되고 패스워드 로그인은 네이티브입니다.
+- Python **298 파일 / 73,617줄**. 의존성 `authlib`, `cryptography`,
+  `watchdog`, `psycopg[binary]`와 extras `ann`/`hnsw`/`postgres`.
+- `POST /worker/chat/record-turn`, `POST /agent/change-proposal` —
+  둘 다 네이티브 경로가 대체했습니다.
+
+### Fixed
+- KG write 4건: `kgv2_*` 뷰만 충돌 시 `type`을 갱신하던 문제,
+  `sort_keys` 없는 직렬화 2곳, 기본 JSON 구분자로 해시되던 `edge:`/
+  `event:` id.
+- 리댁션 2건: `Authorization: Bearer …`가 실제로는 리댁션되지 않던 문제,
+  아무것도 거절하지 않던 텔레그램 토큰 lookahead.
+- 변경 제안 종류 화이트리스트가 `"reorganization"`과 비교해 **모든 폴더
+  재구성 제안이 승인 불가**였던 문제(실제 상수는 `"folder_reorganization"`).
+- `serde_json/preserve_order` 피처 통합으로 제품 빌드에서 `Map`이 삽입
+  순서로 순회해 `sort_keys=True`를 자처하던 덤프가 정렬되지 않은
+  `metadata_json`을 쓰던 문제(읽으면 같고 해시는 다름).
+- FastAPI ≥ 0.140에서 `include_router`가 더 이상 평탄화하지 않아 워커
+  라우트 필터가 라우트를 0개로 보던 문제 — 휠에서 부팅 자체가 실패하고
+  있었습니다.
+
+### Known issues
+- 그대로 이식한 오라클 버그 3건(`/api/command/search` knowledge 그룹 항상
+  비어 있음 · 리뷰 스누즈 offset-aware 500 · 제안 이중 거절 500),
+  업로드 추출 UTF-8 전용, 공급 벡터 1차 노드 한정, 네이티브 도구의 사용자
+  훅 미발화, `sanitize_write_content` 미적용, 워커 원점으로 남은 seam 호출
+  3건. 전문은 [RELEASE_NOTES_v11.6.0.md](../RELEASE_NOTES_v11.6.0.md).
+
+## [11.5.2] - 2026-08-12 — Tight Ship
+
+### Added
+- `POST /api/search/graph` — 세 번째 검색 채널의 라우트. 허용 목록에는
+  있었지만 도달 경로가 없었습니다(감사 산출).
+- `GET /api/ingestion/multimodal` — FEATURE_STATUS가 사용자 표면으로
+  기술하던 멀티모달 상태 조회를 실제 라우트에 배선.
+- 골든 신규 2계열(코퍼스 총 **251 파일**): 실제 `/chat`이 호출하는
+  `build_recent_chat_context`를 못박는 `recent_chat`, 그리고
+  `document_targets`/`agent_profiles` 헬퍼 97행.
+- 재발 금지 가드: `latticeai/` 아래 `sys.modules[__name__]` shim 패턴
+  금지(legacy-debt 게이트 확장).
+- `scripts/bump_version.py`가 rust workspace **여섯 크레이트 전부**를
+  두 Cargo.lock에서 동기화합니다(11.5.0 이후 Phase 2/3/4 크레이트 세
+  개가 매 bump마다 스테일로 남아 테스트 실행이 트리를 더럽혔습니다).
+
+### Changed
+- **워크스페이스 선택자 통합(동작 변경, 의도됨)**: chat/agent/upload/
+  computer-use/admin의 축자 재구현이 정본 규칙을 사용합니다 — 헤더와
+  쿼리가 불일치하면 조용히 헤더를 택하는 대신 **403**.
+- 임베더 byte-identical 쌍을 골든에 못박힌 사본으로 단일화(두 쓰기
+  경로 사이의 조용한 벡터 드리프트가 실패 양식이었습니다).
+- sha256 헬퍼·SSE 프레임 빌더(출력 byte-identical)·데이터 디렉터리
+  기본값·모드 서비스 삼형제·모듈 임포트 프로브를 각각 한 곳으로.
+- Rust byte-identical 사본 7건 통합(통째로 복사돼 있던 `clock.rs` 포함).
+  `lattice-agent`의 독립 `pystr`는 의도된 경계로 유지.
+- `recent_chat` 골든이 실제 발산을 잡아냄: Python의 `limit=0` 꼬리
+  슬라이스는 전부를 남기는데 Rust는 빈 결과를 돌려주고 있었습니다.
+  **Python이 기준**이며 Rust를 수정했습니다.
+
+### Fixed
+- **프록시 리다이렉트**: 3xx가 `Set-Cookie`·`Location`을 온전히 달고
+  통과합니다. 초대 게이트의 막다른 길, SSO 로그인이 조용히 인증되지
+  않던 문제, 딥링크 12개의 프래그먼트 분실이 함께 해소됩니다. 내부
+  워커 오리진을 가리키는 절대 `Location`은 게이트웨이 오리진으로
+  재작성됩니다.
+- **네이티브 레인 posture 게이팅(fail-closed)**: `/rust/*`와
+  `/host/status|jobs`는 워커가 인증을 요구하는 상태에서 그래프 전체를
+  무인증으로 서빙하고 있었습니다. posture가 닫힘/알 수 없음이면 401.
+- **프록시 신원**: `X-Forwarded-For/Proto/Host`가 홉을 건너가고, 루프백
+  또는 `LATTICEAI_TRUSTED_PROXIES` 피어에서 온 것만 존중됩니다.
+  `--no-spawn` CSRF 거절과 내부 워커 포트를 적어 보내던 초대 링크·
+  권한 알림·SSO 리다이렉트 URL이 고쳐집니다.
+- 수퍼바이저가 CSRF 오리진과 나란히 CORS 오리진도 주입합니다.
+- 존재하지 않는 WebSocket 엔드포인트를 가리키던 CSP `ws://` 항목 제거.
+- 게이트웨이 바인드 실패 시 Tauri 셸이 죽은 오리진으로 이동하지 않습니다.
+
+### Removed
+- 이사 간 모듈 shim 6종, 배선된 적 없는 멀티모달 스트리밍 시임,
+  호출자 0 심볼 약 27개(삭제마다 테스트 수술 동반), 소비자 없는
+  `metadata_for` 인터페이스(ABC + 구현 4곳), 죽은 측정 스크립트,
+  그리고 npm tarball에 아직 실려 나가던 **레거시 Electron 셸**
+  (Tauri가 대체) — 약 1,100줄.
+
 ## [11.5.1] - 2026-08-12 — Rust Full Loop
 
 ### Added

package/docs/COMMUNITY_AND_PLUGINS.md

@@ -1,6 +1,6 @@
 # Community And Plugins
 
-Current release: **11.5.1 — Rust Full Loop**.
+Current release: **11.6.0 — One Door**.
 
 LatticeAI defines the path from a strong local-first framework (8.4.0
 action-aware baseline, 8.5.0 registry+DI hardening, 8.6.0 capture/navigation

package/docs/DEVELOPMENT.md

@@ -3,12 +3,13 @@
 > **Status: canonical** — current contributor guidance, kept in sync with the
 > current release.
 
-Current release: **11.5.1 — Rust Full Loop**.
+Current release: **11.6.0 — One Door**.
 
 This document is for contributors working on the local-first Digital Brain
-codebase. Product positioning and quick start stay in `README.md`; release
-history is intentionally limited to 8.0.0-9.9.0 in `docs/CHANGELOG.md` and
-`RELEASE.md`.
+codebase. Product positioning and quick start stay in `README.md`; supported
+release history is 11.0.0 and later in `docs/CHANGELOG.md` and `RELEASE.md`
+(11.6.0 rebuilt the product server in Rust, so `SECURITY.md` supports only
+11.x).
 
 ## Product Contract
 
@@ -20,8 +21,9 @@ Engineering work should preserve these boundaries:
 - the Brain is the durable asset;
 - models are replaceable voices;
 - SQLite is the live local Brain store;
-- PostgreSQL scale/migration tooling, Docker, cloud models, downloads, update checks, Telegram, and
-  Brain Network are opt-in;
+- Docker, cloud models, downloads, update checks and Brain Network are opt-in
+  (the PostgreSQL scale/migration tooling and the Telegram bridge left the tree
+  in 11.6.0 with the platform code that became the AI worker);
 - import-only paths must not initialize MLX/GPU, write files, or make network
   calls;
 - normal Brain use must stay separate from Admin/operator controls.

package/docs/ENTERPRISE.md

@@ -21,7 +21,8 @@ boundary honest (Community is never crippled to upsell Enterprise).
 
 ## The extension seam
 
-The seam lives in [`latticeai/core/enterprise.py`](../latticeai/core/enterprise.py):
+The seam moved to Rust with the product server in 11.6.0 and now lives in
+[`rust/lattice-platform/src/admin/enterprise.rs`](../rust/lattice-platform/src/admin/enterprise.rs):
 
 - `Edition` — `community` (default) or `enterprise`.
 - `EnterpriseCapability` — the enum of reserved capabilities (below).

package/docs/HYBRID_CLOUD_KG_STREAMING.md

@@ -43,10 +43,14 @@ POST /api/network-boundary/policy
 Users approve cloud-derived memory growth in the existing Review Center.
 
 ### Multimodal / video
-`latticeai/services/multimodal_streaming.py`:
-- Same `NetworkBoundaryMode.CLOUD_ALLOWED` gate
-- Additional `allow_multimodal` policy flag
-- Adapter protocol for future Runway/Luma/Veo-compatible providers
+There is no cloud multi-modal *streaming* path. A `multimodal_streaming` module
+was written to a provider-adapter shape and never wired to a provider or a
+route; 11.5.2 deleted it rather than keep a design sketch reading as a feature.
+
+Multi-modal ingestion itself is local and unrelated to this document's cloud
+boundary — see `lattice_brain/ingestion/routing.py` and the `allow_multimodal`
+gate. If a cloud video provider ever lands, the module is recoverable from git
+history (`latticeai/services/multimodal_streaming.py`, removed in 11.5.2).
 
 ### UI
 `NetworkBoundaryPanel` (React) + `GET /api/network-boundary/ui-state`:

package/docs/MULTI_AGENT_RUNTIME.md

@@ -2,14 +2,21 @@
 
 The Multi-Agent Runtime is the **orchestration layer** introduced in v2.0.0 and
 operationalized in v2.2.0. It sits
-*above* the v1.x single-agent state machine ([`SingleAgentRuntime`](../latticeai/core/agent/runtime.py))
+*above* the single-agent state machine, which since 11.6.0 is the Rust loop
+orchestrator ([`lattice_agent::agentloop`](../rust/lattice-agent/src/agentloop/mod.rs))
 and coordinates a pipeline of named **roles** that hand off work to one another,
 retry on a failing review, and emit a fully observable, replayable timeline.
 
-- **Source of truth:** `latticeai/core/multi_agent.py`
-- **HTTP surface:** `latticeai/api/agents.py`
-- **Persistence / Knowledge Graph integration:** `latticeai/core/workspace_os.py`
-  (`WorkspaceOSStore.record_agent_run`, `replay_agent_run`, `list_handoffs`)
+- **Source of truth:** `rust/lattice-platform/src/agents.rs` (the orchestration
+  routes) over `rust/lattice-agent/src/agentloop/` (the state machine)
+- **HTTP surface:** the `agents` family, mounted by `lattice-platform`
+- **Persistence:** `rust/lattice-platform/src/review_queue.rs` — the same
+  `workspace_os.json` document the Review Center reads
+
+> **Moved in 11.6.0.** The Python modules this page used to name
+> (`lattice_brain/runtime/multi_agent.py`, `latticeai/api/agents.py`,
+> `latticeai/core/workspace_os.py`) were deleted when the product server became
+> Rust. The behaviour described below is served natively.
 
 ```python
 MULTI_AGENT_VERSION = "2.2.0"

package/docs/ONBOARDING.md

@@ -1,6 +1,6 @@
 # Lattice AI Onboarding
 
-Current release: **11.5.1 — Rust Full Loop**.
+Current release: **11.6.0 — One Door**.
 
 The first-run goal is a five-minute path from "I opened the app" to "my Brain
 has a source, a question, and proof." This page is the product contract behind

package/docs/OPERATIONS.md

@@ -1,4 +1,4 @@
-# Lattice AI — Operations Guide (v11.5.1)
+# Lattice AI — Operations Guide (v11.6.0)
 
 > **Status: canonical** — kept in sync with the current release. Storage layout
 > below reflects the SQLite live Brain store and workspace scoping, not the
@@ -136,8 +136,11 @@ pip install --upgrade ltcai
 - [ ] `CSRF_TRUSTED_ORIGINS` 화이트리스트 설정
 - [ ] `ALLOWED_COMMANDS` 검토 — python3/node 등 불필요한 실행 도구 제거
 - [ ] 방화벽으로 4825 포트를 프록시만 접근 허용
-- [ ] Telegram 활성화 시 `LATTICEAI_TELEGRAM_ALLOWED_CHAT_IDS`와
-  `LATTICEAI_SERVER_SESSION_TOKEN` 설정
+> **11.6.0 변경**: Telegram 브리지가 제거되어 `LATTICEAI_TELEGRAM_*`는 더 이상
+> 읽히지 않습니다. SSO OIDC 로그인/콜백 플로우도 함께 제거되었습니다 — 설정
+> 표면은 남아 있고 패스워드 로그인은 네이티브(`lattice-auth`)입니다. 외부 OIDC
+> 공급자로 사용자를 인증하던 배포는 해당 플로우가 이식될 때까지 11.5.2에
+> 머무르십시오.
 
 ## 8. 사용자 데이터 격리
 

package/docs/REALTIME_COLLABORATION.md

@@ -5,7 +5,7 @@ Realtime Collaboration is the subsystem that gives a Lattice AI workspace a live
 workspace-scoped execution observability for agents, handoffs, reviews,
 workflows, plugins, retries, and failures. It is delivered over Server-Sent
 Events (SSE) by an in-process pub/sub bus, the
-[`RealtimeBus`](../latticeai/core/realtime.py).
+[`RealtimeBus`](../rust/lattice-platform/src/realtime.rs), native since 11.6.0.
 
 The design goal is to surface "what is happening in the workspace right now"
 (workspaces created, graphs indexed, agents and workflows run, plugins enabled,

package/docs/TRUST_MODEL.md

@@ -1,6 +1,6 @@
 # Lattice AI Trust Model
 
-Current release: **11.5.1 — Rust Full Loop**.
+Current release: **11.6.0 — One Door**.
 
 Lattice AI is local-first, explicit about external communication, and honest
 when a capability is unavailable.

package/docs/WHY_LATTICE.md

@@ -1,6 +1,6 @@
 # Why Lattice AI Exists
 
-Current release: **11.5.1 — Rust Full Loop**.
+Current release: **11.6.0 — One Door**.
 
 **Lattice AI is a local-first Digital Brain that keeps your knowledge durable
 across any AI model.**

package/docs/WORKFLOW_DESIGNER.md

@@ -8,9 +8,10 @@ node to an injected *runner* that calls the real tool registry, skill registry,
 plugin registry, or multi-agent orchestrator.
 
 The execution model lives in
-[`latticeai/core/workflow_engine.py`](../latticeai/core/workflow_engine.py)
+[`rust/lattice-platform/src/workflow_designer/definition.rs`](../rust/lattice-platform/src/workflow_designer/definition.rs)
 (pure logic with injected runners) and the HTTP surface lives in
-[`latticeai/api/workflow_designer.py`](../latticeai/api/workflow_designer.py).
+[`rust/lattice-platform/src/workflow_designer/handlers.rs`](../rust/lattice-platform/src/workflow_designer/handlers.rs).
+Both moved from Python in 11.6.0.
 Persistence reuses the existing `WorkspaceOSStore`, so pre-2.0 workflow history
 is preserved.
 

package/docs/architecture.md

@@ -7,10 +7,10 @@
 > are intentionally frozen at that point in time.
 
 > v3.6.0 — **Knowledge Graph First.** Every data source converges into the graph
-> through one unified ingestion pipeline (`latticeai/services/ingestion.py`), with
+> through one unified ingestion pipeline (`lattice_brain/ingestion/pipeline.py`), with
 > formalized entities/relationships (`docs/kg-schema.md`), browser/web inputs,
 > per-node provenance, and local export/import/backup
-> (`latticeai/services/kg_portability.py`). The agent ecosystem, long-term memory,
+> (`lattice_brain/portability/`). The agent ecosystem, long-term memory,
 > and skills/hooks/tool/MCP registries are all operable from `/app`. Enterprise
 > controls remain future work.
 
@@ -158,8 +158,8 @@ Basic mode and advanced mode have the same feature access.
 | `knowledge_graph.py` | Graph storage, extraction, local folder knowledge graph context |
 | `latticeai/core/context_builder.py` | Graph context for generation |
 | `latticeai/core/workspace_os.py` | Workspace state, timeline, snapshots, durable context |
-| `latticeai/core/multi_agent.py` | Planner/executor/reviewer/researcher orchestration |
-| `latticeai/core/workflow_engine.py` | Workflow definitions and run history |
+| `lattice_brain/runtime/multi_agent.py` | Planner/executor/reviewer/researcher orchestration |
+| `lattice_brain/workflow.py` | Workflow definitions and run history |
 | `latticeai/core/plugins.py` | Plugin manifest, registry, permission boundary |
 | `latticeai/core/security.py` | Local security primitives |
 

package/docs/kg-schema.md

@@ -1,6 +1,6 @@
 # Knowledge Graph Schema
 
-Current release: **11.5.1 — Rust Full Loop**.
+Current release: **11.6.0 — One Door**.
 
 명세 출처: `lattice_ai_full_spec.pptx` 슬라이드 20·21·22
 구현: `lattice_brain/graph/schema.py`

package/docs/v11.5.2_TIGHT_SHIP_PLAN.md

@@ -0,0 +1,144 @@
+# v11.5.2 — Tight Ship (design plan)
+
+Three audits ran against the settled v11.5.1 tree: AUDIT-A (Rust↔Python
+duplication map), AUDIT-B (dead code and no-longer-needed tests, arc-level
+verified against the 100% line+branch gate), AUDIT-C (live front-door parity:
+Rust gateway vs. direct Python worker, 192-endpoint sweep plus targeted
+batteries). This plan is the design synthesis; implementation is delegated in
+two waves. Nothing in this release changes the migration's final form: Python
+remains the AI Worker and the sole client-facing implementation of every
+`/api/*` route; the Rust surface stays pinned by parity goldens.
+
+## Audit verdicts that shape the release
+
+1. **Cross-boundary duplication is all by design.** Every Rust module's Python
+   twin either serves a live route in Python-direct mode or feeds a parity
+   golden. Zero cross-boundary deletions. The real duplication is intra-Python
+   and intra-Rust.
+2. **The dead code is pre-Rust debt.** Six moved-module shims with zero
+   non-test importers, one never-wired streaming seam, and 27 zero-caller
+   symbols whose only callers are their own tests ("dead code wearing a
+   test" — invisible to the coverage gate by construction).
+3. **The 183 `test_cov_wp*` files are all load-bearing.** Ten look deletable
+   by line analysis and are collectively sole owners of 79 branch arcs. The
+   seven coverage-redundant feature-test files carry behavioural regression
+   value and are deliberately kept.
+4. **The front door has seven real gaps (G1–G7)**, one of which (Set-Cookie
+   destroyed on proxied redirects) makes the invite gate a hard dead-end and
+   silently breaks SSO login.
+
+## Workstream 1 — deletions (paired, gate-preserving)
+
+- Six moved-module shims: `latticeai/core/{graph_curator,hooks,multi_agent,workflow_engine}.py`,
+  `latticeai/services/{ingestion,kg_portability}.py` + the shim-existence
+  tests + their `[tool.mypy] files` entries.
+- `latticeai/services/multimodal_streaming.py` (never wired; restorable from
+  git if a provider ever lands).
+- 25 of AUDIT-B's 27 dead symbols, with per-test surgery on the enumerated
+  collateral lines so `fail_under = 100` (lines AND branch arcs) holds.
+  Decisions on the three flagged items: `delete_conversation` **stays**
+  (public store API, exercised as a fixture by the read-equivalence suite);
+  `propose_file_delete` **goes together with** the now-uncreatable
+  `file_delete` limb of `approve()`; `multimodal_status` **is wired, not
+  deleted** (Workstream 3) — FEATURE_STATUS already documents it as
+  user-facing behaviour.
+- `metadata_for` interface method (declared on the vector-index ABC,
+  implemented four times, called zero times) — removed from ABC and all
+  four implementations.
+- `scripts/measure_brain_home_fill.mjs`, `tests/fixtures/filegen/` (12 unread
+  data files), and the legacy `desktop/electron/` shell (hardcodes 4825,
+  injects none of the safety flags, superseded by Tauri) after verifying it is
+  not referenced by any release artifact or workflow.
+- A new guard extends the legacy-shim gate inward: no
+  `sys.modules[__name__] = _impl` shim may exist under `latticeai/` again.
+
+## Workstream 2 — consolidation (behaviour-preserving unless stated)
+
+Python (the canonical copy is named; the direction always keeps
+`lattice_brain` import-free of `latticeai`):
+
+- **Embedder pair**: `latticeai/core/local_embeddings.py` is byte-identical to
+  the golden-pinned `lattice_brain/embeddings.py`. The unpinned copy is
+  deleted and importers rewired — silent vector drift between two write paths
+  was the failure mode.
+- **`workspace_scope_from_request`**: the four verbatim re-derivations
+  (`chat_helpers`, `upload_service`, `computer_use`, `admin`) import the
+  canonical `api/workspace_scope.py`. Behaviour change, intended: the copies
+  silently preferred the header where the canonical rule 403s on
+  disagreement.
+- `_default_data_dir` ×4 → `core/config.py`; sha256-hex ×6 → one helper;
+  SSE frame builders ×5 → one `sse_frame` (byte-identical output);
+  `model_runtime/engines.py` delegator/dead-fragment cleanup;
+  the AST-identical mode-service triplet → a `JsonBackedModeService` base;
+  module-importability ×4 → one helper (`find_spec` default, real-import
+  `strict=True` kept where native-lib load failures matter, e.g. mlx);
+  `parse_iso` → `lattice_brain/utils` (the golden-pinned copy);
+  `_detect_gpu`/`_detect_cpu` → `setup/wizard/detect.py`; the small ×2
+  helpers and the workspace-store mixin where mechanical.
+
+Rust: `gateway/clock.rs` (wholesale copy) deleted in favour of
+`lattice_retrieval::routes::naive_local_now`; `brain_not_found` shared;
+`haystack`/`json_opt` lifted into `shape.rs`; `in_set`/`bad_request` lifted
+within `lattice-agent`; `is_py_space`/`round3` shared from `lattice-core` into
+`lattice-ingest`. `lattice-agent`'s independent `pystr` stays — its
+zero-dependency isolation is a deliberate boundary.
+
+Deliberately **not** done in a patch release: splitting the three oversized
+route factories (`create_workspace_router` 706 lines et al.) — recorded as
+future work, not silently dropped.
+
+## Workstream 3 — front-door and feature gaps
+
+- **G1/G4 (redirects)**: the proxy gets its own reqwest client with redirect
+  following disabled; 3xx responses pass through with their `Set-Cookie` and
+  `Location` intact; absolute `Location` values naming the internal worker
+  origin are rewritten to the request's gateway origin. Fixes the invite
+  gate, SSO login, and the twelve legacy deep links.
+- **G2/G3 (native-lane auth)**: the native `/rust/*` and `/host/*` lanes
+  mirror Python's `trusted_local_owner` posture exactly. The worker's health
+  payload gains the posture facts; the gateway caches them from its existing
+  health polling and **fails closed** (posture unknown → native lanes refuse).
+  With `LATTICEAI_REQUIRE_AUTH=true` the native lanes answer 401 with a
+  machine-readable reason instead of serving the graph unauthenticated (G2)
+  or dying mid-loop on a seam 401 (G3). FEATURE_STATUS states the boundary:
+  the native lanes are an open-posture, single-local-owner surface in 11.5.2.
+- **G5/G7 (proxied identity)**: the proxy adds `X-Forwarded-For/Proto/Host`;
+  the worker computes its effective external origin from `X-Forwarded-Host`
+  only when the direct peer is loopback or listed in
+  `LATTICEAI_TRUSTED_PROXIES`. CSRF's `Origin == Host` fallback and the three
+  absolute-URL producers (admin invite link, permission notifications, SSO
+  redirect default) use it. Threat model note: browsers cannot set
+  `X-Forwarded-Host`, and a local non-browser caller could already forge
+  `Origin`, so this widens nothing.
+- **G6 (CORS)**: the supervisor injects `LATTICEAI_CORS_ALLOWED_ORIGINS` with
+  the gateway origins, mirroring the CSRF injection — the browser extension
+  and any cross-origin local client work through the front door.
+- **Feature gaps surfaced by the audits**: `graph_search` gains its missing
+  route (`POST /api/search/graph` — it was allow-listed but unreachable);
+  `multimodal_status` is wired to the route FEATURE_STATUS describes; the
+  `recent_chat` context seam is investigated and either wired into the live
+  assembler or the golden amended to match reality (whichever the original
+  intent supports — the current state, a golden pinning behaviour the product
+  never executes, is the one option that stays wrong); `tools/documents.py`
+  and `core/agent_profiles.py` — live `/agent` hot-path twins with no golden —
+  enter the fixture generators.
+- Small honest fixes: stale `ws://` removed from both CSPs (no WebSocket
+  endpoint exists); the Tauri shell no longer navigates to a dead origin when
+  the gateway fails to bind.
+
+Recorded, not fixed (with reasons): no request timeout on the proxy hop (a
+blanket timeout would kill long-lived SSE; the 15-minute model endpoints rely
+on the current behaviour), `request.is_disconnected()` seeing the gateway's
+socket (inherent to proxying), per-IP buckets collapsing on loopback (the
+gateway is loopback-only; the direct topology behaved identically).
+
+## Release mechanics
+
+Both waves verified on the settled tree (dev 3.14 + fresh-resolve 3.11) before
+the machinery runs: bump to 11.5.2 (Cargo.lock joins the sync so the suite
+stops dirtying the tree), OpenAPI regenerated (new routes), release theme
+"Tight Ship", OPERATIONS title, screen-claims entry (backend-only:
+all thirteen measured, none gated), release notes / CHANGELOG / README /
+extension README, screenshots + GIF re-shot at 11.5.2, ARCHITECTURE System
+Map labels updated (proxy semantics, posture-gated native lanes), DMG via
+release:artifacts, tag + GitHub Release, main push, CI green.