ltcai 8.1.0 → 8.2.0

package/docs/HANDOVER_v3.6.0.md

@@ -1,46 +0,0 @@
-# Lattice AI v3.6.0 — Completion Record (Knowledge Graph First)
-
-**Status: ✅ RELEASED — 2026-06-10.** All planned scopes implemented, tested,
-committed, pushed, CI green, tagged, and published. No external publish/deploy.
-
-- **Tag:** `v3.6.0` → commit `3c85675`
-- **GitHub Release:** https://github.com/TaeSooPark-PTS/LatticeAI/releases/tag/v3.6.0
-  (published, not draft; assets: `ltcai-3.6.0-py3-none-any.whl`,
-  `ltcai-3.6.0.tar.gz`, `ltcai-3.6.0.tgz`, `ltcai-3.6.0.vsix`)
-- **CI:** main CI ✓, Visual Smoke ✓, release.yml (tag) ✓
-- **Tests:** unit 455 passing · lint 64/64 · check:python 153 (3.11/3.12/3.14) ·
-  release artifacts built + validated
-
-## Commits (v3.5.0 → v3.6.0)
-
-| Commit | Scope |
-|---|---|
-| `baa2bf6` | chore(audit) — v3.5.0 carry-over (0 blocking) |
-| `5a6a7d4` | feat(kg) — entities/relationships schema |
-| `135e81a` | feat(kg) — unified ingestion pipeline + provenance |
-| `b548885` | feat(browser) — browser/web ingestion + MV3 extension |
-| `39a7a0c` | feat(kg) — export/import/backup/restore |
-| `21cfb97` | fix(runtime) — hook coverage for ingestion paths |
-| `7009e39` | fix(ui) — Knowledge Graph as primary surface |
-| `fa89a84` | docs(philosophy) — Digital Brain Platform rewrite |
-| `aa011a5` | release: v3.6.0 (version bump) |
-| `3c85675` | fix(ci) — 3.11-compatible f-string (PEP 701 quote reuse) |
-
-## Carry-over audit result
-
-Zero blocking items. Settled postures preserved: Vercel landing-only, OIDC
-RSA-only, legacy `/account` `/admin` out of scope. The one honest v3.5.0 gap (KG
-ingestion not firing tool hooks) is **closed**. Full detail:
-`docs/CARRYOVER_AUDIT_v3.6.0.md`.
-
-## Key facts for future work
-
-- New seams: `latticeai/services/ingestion.py` (single write-side entrypoint),
-  `latticeai/services/kg_portability.py`, `latticeai/api/browser.py`,
-  `latticeai/api/portability.py`, provenance in `knowledge_graph.py`.
-- **Gotcha:** PEP 701 f-string quote reuse (`f'{x or ''}'`) compiles on 3.12+ but
-  is a SyntaxError on 3.11 — always run `python3.11 scripts/check_python.py`
-  before pushing (CI tests on 3.11 + 3.12).
-- Version canonical: `WORKSPACE_OS_VERSION`; mirrors enforced by
-  `test_version_consistency.py`.
-- Local tests need `.venv/bin/python` (system `python3` lacks fastapi).

package/docs/RUNTIME_HOOK_COVERAGE_v3.5.0.md

@@ -1,56 +0,0 @@
-# Runtime Hook Coverage — v3.5.0
-
-Every place Lattice AI executes a real tool or agent action, and whether it runs
-through the unified lifecycle. The single tool path is
-`dispatch_tool(hooks, name, args, run_fn)` in `latticeai/core/hooks.py`
-(`pre_tool → execute → post_tool`); the HTTP helper `_tool_response`
-(`latticeai/api/tools.py`) wraps it; uploads use the parallel
-`pre_upload/post_upload/pre_index/post_index` lifecycle
-(`latticeai/services/upload_service.py`); agent runs use `pre_run/post_run`.
-
-**Method.** Routers/services were enumerated by a 6-way parallel audit and then
-each genuine execution path was verified by reading the call site. A path is a
-*bypass* only if a real tool/agent action skips its lifecycle. Read-only metadata
-endpoints (status, list-permissions, config) execute no tool and are not bypasses.
-
-**Result.** All discovered tool/agent execution paths are covered. The four
-remaining "uncovered" rows are deliberate, documented design decisions (service
-maintenance ops + an action already inside the upload lifecycle), not gaps.
-
-## Tool / agent execution paths
-
-| Entrypoint | Execution | Lifecycle path | pre fired | post fired | Test |
-|---|---|---|---|---|---|
-| `POST /tools/list_dir`, `workspace_tree`, `write_file`, `search_files`, `todo_*`, `inspect_html`, `preview_url`, `create_*`, `read_document`, `knowledge_*`, `obsidian_*`, `network_status` | tool fn | `_tool_response`→`dispatch_tool` | yes (`pre_tool`) | yes (`post_tool`) | `test_hooks_dispatch`, `test_runtime_coverage` |
-| `POST /tools/read_file` | `read_file` (kwargs) | `_tool_response` (kwargs-aware) ✅v3.5.0 | yes | yes | `test_runtime_coverage` |
-| `POST /tools/edit_file` | `edit_file` (kwargs) | `_tool_response` ✅v3.5.0 | yes | yes | `test_runtime_coverage` |
-| `POST /tools/grep` | `grep` (kwargs) | `_tool_response` ✅v3.5.0 | yes | yes | `test_runtime_coverage` |
-| `POST /tools/clear_history` | `clear_history` | `_dispatch`→`dispatch_tool` ✅v3.5.0 | yes | yes | `test_runtime_coverage` |
-| `POST /tools/git_*`, `run_command`, `build_project`, `deploy_project` | tool fn | `_tool_response` | yes | yes | `test_route_compatibility` |
-| `POST /local/*` (list/read/write) | `local_*` | `tool_response` | yes | yes | `test_route_compatibility` |
-| `GET/POST /cu/*` (open_app/url/click/type/key/scroll/move/drag) | `computer_*` | `tool_response` | yes | yes | `test_runtime_coverage` |
-| `GET /cu/status`, `/cu/screenshot` | `computer_status/screenshot` | `_dispatch` ✅v3.5.0 | yes | yes | `test_runtime_coverage` |
-| `POST /cu/agent` (agent loop) | `execute_tool(name,args)` per step + Chrome shortcut | `_dispatch`→`dispatch_tool` ✅v3.5.0 | yes | yes | `test_runtime_coverage` |
-| `POST /agent/eval` | `execute_tool` per eval case | `dispatch_tool` ✅v3.5.0 | yes | yes | (covered via dispatch_tool) |
-| Single-agent runtime tool calls | `execute_tool` via `AgentDeps` | `core/agent.py`→`dispatch_tool` | yes | yes | `test_hooks_dispatch` |
-| Agent run (start→finish) | orchestrator run | `agent_runtime` `pre_run`/`post_run` | yes (`pre_run`) | yes (`post_run`) | `test_hooks_dispatch` |
-| Workflow tool node | `dispatch_tool` | `platform_runtime` | yes | yes | `test_hooks_dispatch` |
-| Workflow run (start→end) | engine run | `WorkflowEngine` `pre_workflow`/`post_workflow` | yes | yes | `test_hooks_dispatch` |
-| `POST /upload/document` | `process_uploaded_document` | upload lifecycle | `pre_upload` | `post_upload` | existing upload tests |
-| Document indexing (upload + folder watch) | embed/graph build | `pre_index`/`post_index` | yes | yes | existing |
-
-## Intentionally outside the tool lifecycle (documented, not gaps)
-
-| Entrypoint | Why not `pre_tool`/`post_tool` |
-|---|---|
-| `read_document` inside `process_uploaded_document` (`upload_service.py`) | Already inside the upload lifecycle (`pre_upload`→`post_upload`); wrapping it again would double-dispatch the same user action. |
-| `POST /api/memory/{prune,compact,rebuild,clear}` | Knowledge/memory **service** maintenance operations, not registry tools; they have their own audit events. Not part of the agent tool vocabulary. |
-| `clear_history` inside `core/agent.py` executor | Runs inside an agent run already bracketed by `pre_run`/`post_run`; not re-wrapped to avoid nested dispatch. |
-| Read-only status/config endpoints (`/tools/permissions`, `/obsidian/status`, model/catalog reads) | Execute no tool — nothing to gate. |
-
-## Summary
-
-- Genuine tool/agent execution paths discovered: **all enumerated routers + services**.
-- Bypasses found and closed in v3.5.0: **read_file, edit_file, grep, clear_history, computer-use agent loop (+ /cu/status, /cu/screenshot), skill-eval**.
-- Bypasses remaining: **none** (the four rows above are deliberate, documented design decisions).
-- Coverage of discovered tool/agent execution paths: **100%**.

package/docs/RUNTIME_HOOK_COVERAGE_v3.6.0.md

@@ -1,49 +0,0 @@
-# Runtime Hook Coverage — v3.6.0
-
-v3.6.0 makes the Knowledge Graph the primary architecture and adds new
-**ingestion** paths (web URL, browser tab, unified text/file pipeline) plus
-**portability** ops (export/import/backup/restore). This doc extends
-[`RUNTIME_HOOK_COVERAGE_v3.5.0.md`](./RUNTIME_HOOK_COVERAGE_v3.5.0.md) and records
-that the new data-mutating paths run through the unified lifecycle.
-
-The single tool path is `dispatch_tool(hooks, name, args, run_fn)` in
-`latticeai/core/hooks.py` (`pre_tool → execute → post_tool`). v3.5.0's one honest
-gap was that **KG ingestion did not fire hooks**. v3.6.0 closes it: every source
-now flows through `IngestionPipeline.ingest` (`latticeai/services/ingestion.py`),
-which wraps the store write in `dispatch_tool(..., source="ingestion")`.
-
-**Result.** All v3.5.0 coverage is preserved (no regression), and every new
-v3.6.0 ingestion path is covered. Portability admin/maintenance ops follow the
-v3.5.0 convention for service maintenance (own audit events), documented below.
-
-## New v3.6.0 execution paths
-
-| Entrypoint | Execution | Lifecycle path | pre fired | post fired | Test |
-|---|---|---|---|---|---|
-| `IngestionPipeline.ingest` (any source) | `ingest_source` / `ingest_document` | `dispatch_tool(name="kg_ingest.<type>", source="ingestion")` | yes (`pre_tool`) | yes (`post_tool`) | `test_ingestion_pipeline` |
-| `POST /api/browser/read-url` | fetch URL → `pipeline.ingest` (web_url) | pipeline → `dispatch_tool` | yes | yes | `test_browser_ingestion`, `test_runtime_coverage_v36` |
-| `POST /api/browser/ingest-current-tab` | sanitize → `pipeline.ingest` (browser_tab) | pipeline → `dispatch_tool` | yes | yes | `test_browser_ingestion`, `test_runtime_coverage_v36` |
-| Local file / upload via pipeline | `ingest_document` | pipeline → `dispatch_tool` | yes | yes | `test_ingestion_pipeline` |
-| Provenance write per ingestion | `record_provenance` | inside the bracketed `dispatch_tool` run_fn | (bracketed) | (bracketed) | `test_ingestion_pipeline` |
-
-A blocking `pre_tool` hook makes ingestion return `status="blocked"` (the
-`PermissionError` from `dispatch_tool` is caught and surfaced honestly), exactly
-mirroring how a blocked tool call is handled — verified in
-`test_runtime_coverage_v36` and `test_ingestion_pipeline`.
-
-## Intentionally outside the tool lifecycle (documented, not gaps)
-
-| Entrypoint | Why not `pre_tool`/`post_tool` |
-|---|---|
-| `POST /api/knowledge-graph/{export,export-file,backup,restore,import}` | Admin **portability/maintenance** operations over the whole machine-global graph, not agent-vocabulary tools. They are admin-gated (`require_admin`) and recorded via the platform audit trail — same convention as the v3.5.0 memory maintenance ops (`prune/compact/rebuild/clear`). Wrapping a whole-store backup in `pre_tool` would misrepresent it as a per-action agent tool. |
-| `read_document` inside upload (`upload_service.py`) | Already inside the `pre_upload`→`post_upload` lifecycle (unchanged from v3.5.0). |
-| `POST /api/memory/{prune,compact,rebuild,clear}` | Unchanged from v3.5.0 — service maintenance with own audit events. |
-| Read-only KG reads (`/knowledge-graph/{stats,graph,search,...}`, `/api/knowledge-graph/portability` status) | Execute no mutation — nothing to gate. |
-
-## Summary
-
-- v3.5.0 coverage of tool/agent execution paths: **100%, preserved** (no regression).
-- v3.6.0 gap closed: **KG ingestion now fires `pre_tool`/`post_tool`** via the unified pipeline (the one honest carry-over note from v3.5.0).
-- New ingestion paths (unified pipeline, `read-url`, `ingest-current-tab`): **covered**.
-- Portability admin ops: **documented as audit-gated maintenance**, consistent with the v3.5.0 convention — not bypasses.
-- Coverage of discovered mutating ingestion paths: **100%**.