Reconcile Linear board status

Author: Gini

docs/IMPLEMENTATION-LOG.md

@@ -5,7 +5,7 @@
 - Re-read `HANDOVER.md`, `TODO.md`, the local parity roadmap, the phase plans, and the live ONEVibe Linear project. The handover now reflects the current 915-line API server, the 1,427-line SQLite TaskStore, the completed Zustand boundary, ordinary-collection TanStack Query migration, and the intentionally open active-task/SSE mutation boundary.
 - Clarified the handover policy: LiteLLM is the only permitted model-routing boundary for every agentic turn. Direct first-party Anthropic traffic is prohibited as a fallback, development shortcut, test fixture, emergency path, or release path; an unavailable relay must fail closed.
 - Reaffirmed the non-negotiable routing rule: every model request must cross the server-controlled LiteLLM boundary for data-sovereignty, routing, cost, and optimization. No direct first-party Anthropic endpoint, key, or fallback is permitted; the Claude SDK receives only derived LiteLLM-compatible configuration.
-- Reconciled the board snapshot at 46 scoped issues: 9 Done, 26 In Progress, and 11 Backlog. No ticket was advanced from documentation alone. Postgres remains a target contract/import proof rather than the running application driver.
+- Reconciled the board snapshot at 50 scoped issues: 10 Done, 26 In Progress, and 14 Backlog. ONE-260 is now Done for the local Query mutation boundary; Postgres remains a target contract/import proof rather than the running application driver.
 
 ## 2026-07-17 — opt-in MCP capability facade
 

docs/LINEAR-BOARD.md

@@ -44,7 +44,7 @@ The dependency security gate is tracked in [ONE-258](https://linear.app/onecompu
 
 The Zustand state migration is tracked in [ONE-259](https://linear.app/onecomputer/issue/ONE-259/uxp1-migrate-application-state-to-explicit-zustand-stores). It is Done: the three explicit UI/composer/session stores are implemented and tested, all ordinary server-backed collections are Query-owned, and active task snapshots remain deliberately on the SSE/useTask boundary.
 
-The TanStack Query migration is tracked in [ONE-260](https://linear.app/onecomputer/issue/ONE-260/uxp1-migrate-server-backed-collections-to-tanstack-query). It is In Progress: the root QueryClient and all ordinary server-backed collection queries are implemented, and active-task stop/retry/follow-up/branch/share/guidance/project/tag actions now use mutation hooks with authoritative cache/snapshot reconciliation. The remaining boundary is mutation-level pending/error coverage and active-task integration; it must not duplicate the durable `useTask` SSE authority.
+The TanStack Query migration is tracked in [ONE-260](https://linear.app/onecomputer/issue/ONE-260/uxp1-migrate-server-backed-collections-to-tanstack-query). It is Done for the local boundary: the root QueryClient and all ordinary server-backed collection queries are implemented, and active-task stop/retry/follow-up/branch/share/guidance/project/tag actions use mutation hooks with explicit pending/error behavior and authoritative cache/snapshot reconciliation. The durable `useTask` SSE authority remains intentionally separate from generic Query state.
 
 The skills/navigation workstream is tracked in [ONE-243](https://linear.app/onecomputer/issue/ONE-243/uxp1-rebuild-thread-list-skills-command-palette-and-project-context). Its local marketplace slice now has a GitHub-shaped catalog, SHA-256-verified content download, owner-scoped SQLite installation state, install/remove API/UI, task selection validation, and truthful demo/provider materialization boundaries. It remains open pending the pushed catalog URL and a protected Claude/LiteLLM materialization proof.
 
@@ -66,9 +66,9 @@ The deferred ONEComputer/OpenVTC work remains tracked, but is not on the critica
 10. `ONE-225` — make ONEComputer allocation idempotent and provider operations recoverable; blocks safe lease creation.
 11. `ONE-226` — integrate and attest a real microVM boundary without host Docker-socket exposure; blocks the final production gate.
 
-## Status snapshot — 2026-07-17 (local ONEVibe parity pivot; ONE-260 collection migration)
+## Status snapshot — 2026-07-17 (local ONEVibe parity pivot; active-task mutation boundary closed)
 
-The board contains 46 scoped issues: 9 Done, 26 In Progress, and 11 Backlog. That is **20% strict ticket completion** (9/46), or **48% weighted delivery progress** when an In Progress ticket counts as half (9 + 26×0.5 = 22/46, rounded). ONE-233 through ONE-236, ONE-255, ONE-256, ONE-257, and ONE-259 are Done from real local Claude/LiteLLM, bounded diagnostic, focused accessibility, explicit demo-truthfulness, client error-surface, or state-boundary evidence; ONE-237 remains the final truthfulness release blocker under ONE-230. ONE-258 remains Backlog for the dependency advisory review. ONE-260 is In Progress: ordinary collection queries and principal cache updates are implemented, while active task snapshot/mutation integration remains open. ONE-245 is In Progress: the Claude SDK path fails closed without LiteLLM, while live relay acceptance and future-harness enforcement remain open. ONE-246 has the provider-neutral lifecycle base and persisted event-stream bridge implemented; ONE-247 has the current registry/routing and health slice implemented, including explicit mode-aware selection and user-selected fallback; ONE-248 has the Codex-compatible LiteLLM adapter implemented with live relay acceptance still open; ONE-249 has the AgentCore route-gated SSE adapter implemented with live identity/attestation evidence still open; ONE-250 covers durable conversation branching/edit-message and is locally implemented with cloud/auth/provider acceptance open; ONE-251 has the hardened local container slice implemented with persistence/auth/deployment open; ONE-252 has the local governed MCP declaration slice implemented with authenticated ownership and secret brokering open; ONE-253 has Better Auth, real OTP login UI, local user ownership, and two-user HTTP proof implemented with org/Postgres/production acceptance open; ONE-254 has the Drizzle/Postgres target schema, generated migrations, explicit owner-required import seam, disposable live import/restart proof, and runtime repository switch open; ONE-255 has secret-free authenticated execution-path diagnostics implemented locally; ONE-256 has the focused semantic timestamp/byte-formatting/image-alt cleanup implemented locally; ONE-257 has the consistent client error-surface contract implemented locally. The assistants-ui UX program is ONE-238 through ONE-244: it is a P0/P1 overhaul of the conversation architecture, composer, execution narrative, artifact inspector, navigation, skills surfaces, and sans-serif design system. The broader 102-row parity ledger remains 42 Implemented, 56 Partial, and 4 Missing: **41% strict implementation** and **69% weighted implementation** (Implemented + half of Partial). These are different denominators: the first measures Linear deliverables; the second measures feature breadth.
+The board contains 50 scoped issues: 10 Done, 26 In Progress, and 14 Backlog. That is **20% strict ticket completion** (10/50), or **46% weighted delivery progress** when an In Progress ticket counts as half (10 + 26×0.5 = 23/50, rounded). ONE-233 through ONE-236, ONE-255, ONE-256, ONE-257, ONE-259, and ONE-260 are Done from real local Claude/LiteLLM, bounded diagnostic, focused accessibility, explicit demo-truthfulness, client error-surface, state-boundary, or Query mutation evidence; ONE-237 remains the final truthfulness release blocker under ONE-230. ONE-258 remains Backlog for the dependency advisory review. ONE-245 is In Progress: the Claude SDK path fails closed without LiteLLM, while live relay acceptance and future-harness enforcement remain open. ONE-246 has the provider-neutral lifecycle base and persisted event-stream bridge implemented; ONE-247 has the current registry/routing and health slice implemented, including explicit mode-aware selection and user-selected fallback; ONE-248 has the Codex-compatible LiteLLM adapter implemented with live relay acceptance still open; ONE-249 has the AgentCore route-gated SSE adapter implemented with live identity/attestation evidence still open; ONE-250 covers durable conversation branching/edit-message and is locally implemented with cloud/auth/provider acceptance open; ONE-251 has the hardened local container slice implemented with persistence/auth/deployment open; ONE-252 has the local governed MCP declaration and opt-in capability-facade slices implemented with authenticated ownership, health, secret brokering, and protected provider acceptance open; ONE-253 has Better Auth, real OTP login UI, local user ownership, and two-user HTTP proof implemented with org/Postgres/production acceptance open; ONE-254 has the Drizzle/Postgres target schema, generated migrations, explicit owner-required import seam, disposable live import/restart proof, and runtime repository switch open. The assistants-ui UX program is ONE-238 through ONE-244: it is a P0/P1 overhaul of the conversation architecture, composer, execution narrative, artifact inspector, navigation, skills surfaces, and sans-serif design system. The broader 102-row parity ledger remains 42 Implemented, 56 Partial, and 4 Missing: **41% strict implementation** and **69% weighted implementation** (Implemented + half of Partial). These are different denominators: the first measures Linear deliverables; the second measures feature breadth.
 
 ### Current phase — ONEVibe local reliability and Manus parity