---
type: topic-doc
area: release
visibility: public
last_memory_sync: 2026-07-04T03:35:18.210566+00:00
---
# Release
## Current model
- COE-461 contributed: PR #164: Expose memory graph DTOs and endpoints (merge `762cec5`)
- COE-464 contributed: PR #165: Derive OKF memory graph metrics and communities (merge `7d58035`)
- COE-465 contributed: PR #166: Add shared frontend graph package (merge `21281d0`)
- COE-467 contributed: PR #171: Add Knowledge Graph renderer (merge `1337903`)
- COE-468 contributed: PR #169: Add Knowledge Graph inspector surface (merge `960541a`)
- COE-469 contributed: PR #170: Wire live memory graph privacy gates (merge `11ac876`)
## Important invariants
- Preserve the behavior described in the recent captured changes unless current code and tests show it has changed.
- Use capsule source refs to inspect the original PR or Linear issue when context is ambiguous.
## Operational flow
- No generated diagram requested for this sync.
## Known gotchas
- No area-specific gotchas were inferred from the selected memory.
## Recent changes
- COE-461: Memory Graph DTOs And Gateway Endpoints
- COE-464: Graph Extraction, Metrics, And Community Pipeline
- COE-465: Shared Graph Frontend Package And Reducers
- COE-467: Three.js Graph Renderer And Worker Layouts
- COE-468: Concept Inspector, Search, Filters, And Accessibility Fallback
- COE-469: Live Memory Graph Integration And Privacy Gates
- COE-471: Graph Scale, Visual Regression, And Web/Desktop Hardening
- COE-498: Tree-sitter Provider Skeleton And Rust Parsing
- COE-499: Memory Context AST Provider Integration
- COE-500: Query Packs For Supported Agent Languages
- COE-501: Code Intelligence Persistence And Ingestion
- COE-502: Read-Only AST MCP And CLI Tools
- COE-503: Code Intelligence Performance Docs And Hardening
- COE-505: Add scheduler-side Codex stdio interrupt channel
- COE-520: Route desktop Knowledge Graph through native gateway commands
- COE-521: Workflow Target Branch Model And Init Customization
- COE-522: Init Target Branch Prompt And Flag
- COE-523: Update Workflow Settings Mode
- COE-524: Template Docs And Settings Hardening
- COE-525: Desktop Installer Contract And Release Metadata
- COE-526: Desktop Release Bundle Pipeline
- COE-527: Source Build Fallback And Prerequisites
- COE-528: App Download Install And Launch Flow
- COE-529: Desktop Auto-Update Flow
- COE-530: Installer Docs And End-To-End Validation
- COE-531: Workspace Shell Graph Hero And Surface State
- COE-532: Symbol Identity Container Chain And Code Read Model
- COE-533: Code Graph DTOs Gateway Routes And Native Commands
- COE-534: Code Graph Frontend Surface Adapters And Inspector
- COE-535: Run Diff Symbol Navigation And Code Overlay
- COE-536: Cross Graph Code Memory And Work Chips
- COE-537: Code Graph Scale Accessibility And Parity Hardening
- COE-540: Canonical Codex Thread Reuse And Workspace Retention
- COE-541: Durable Codex Thread Archive And Debug Recovery
- COE-542: Target Branch Code Index And Revision Snapshots
- COE-543: Workspace Code Overlay And Composite Graph
- COE-544: Indexed Agent Code Context And Retrieval
- COE-545: Edge Delta And Module Topology Diff
- COE-546: Code Graph Bootstrap UX And End-To-End Validation
- COE-547: Central Multi-Repository Config And Safe Migration
- COE-548: Canonical Repository Binding And Task Propagation
- COE-549: Verified Checkouts Instructions And Harness Envelopes
- COE-550: Per-Instance Memory Catalog And Source Migration
- COE-551: Scoped Cross-Repository Memory And Leaf Overlays
- COE-553: Parent Execution Roots And Child Workspace Reuse
- COE-554: Restart-Safe Parent Integration Controller
- COE-555: Parent Repair Review And Merge Lifecycle
- COE-556: Bottom-Up Subtree Cleanup And Recovery
- COE-562: Implement artifact validation and digest primitives
- COE-563: Implement task-packet admission and freeze tooling
- COE-564: Implement verifier execution and outcome records
- COE-565: Implement isolated workspace materialization
- COE-566: Implement configurable run matrices and scheduling
- COE-567: Implement run lifecycle and process-protocol primitives
- COE-608: ACP Profiles And Executable Protocol Client
- COE-609: ACP Session Ownership And Durable Recovery
- COE-610: ACP Client Callbacks And Session Configuration
- COE-611: ACP Execution Routing And Worker Integration
- COE-612: ACP Operator Requests And Response Routing
- COE-613: ACP Extensions And Harness Operations
- COE-615: ACP Runtime Conformance And Live Qualification
## Source refs
- COE-461
- COE-464
- COE-465
- COE-467
- COE-468
- COE-469
- COE-471
- COE-498
- COE-499
- COE-500
- COE-501
- COE-502
- COE-503
- COE-505
- COE-520
- COE-521
- COE-522
- COE-523
- COE-524
- COE-525
- COE-526
- COE-527
- COE-528
- COE-529
- COE-530
- COE-531
- COE-532
- COE-533
- COE-534
- COE-535
- COE-536
- COE-537
- COE-540
- COE-541
- COE-542
- COE-543
- COE-544
- COE-545
- COE-546
- COE-547
- COE-548
- COE-549
- COE-550
- COE-551
- COE-553
- COE-554
- COE-555
- COE-556
- COE-562
- COE-563
- COE-564
- COE-565
- COE-566
- COE-567
- COE-608
- COE-609
- COE-610
- COE-611
- COE-612
- COE-613
- COE-615
## 3.0.0 multi-repository and ACP release boundary
Version 3.0.0 includes explicit `project_set` routing and a production local
ACP v1 worker route. Existing `legacy_single` routing remains available. The
[multi-repository guide](multi-repository.md), [ACP guide](acp.md), and
[3.0 upgrade guide](migration-3.0.0.md) explain selection and recovery for
operators new to these paths.
Before shipping the multi-repository route for a project set, run
`scripts/hermetic_multi_repo_lifecycle.sh` against the selected config at a
clean commit, then run the opt-in disposable live gate. Record the same commit
and selected config SHA-256 in both artifacts, verify exact-head CI, and check
that teardown left no disposable resources. The procedure and bounded rollout
conditions are in [multi-repository rollout](multi-repository-rollout.md).
Before claiming an ACP vendor profile is qualified, check the executable
version and login, then run the authenticated tracked-issue and restoration
tests in [ACP live qualification](acp-live-qualification.md). Profile preflight
alone does not prove authentication or optional protocol support. The pinned
Cursor and Devin runs qualified `session/load`; neither advertised
`session/resume` in that run.
Keep the root crate, desktop package, Tauri metadata, and both Cargo lockfiles
at `3.0.0`. The root `package-lock.json` must record the desktop package at
the same version. Run the default bundled-mode Clippy and tests, frontend
build, and the desktop parity guard before tagging or publishing:
```bash
npm run package:release --workspace=@opensymphony/desktop -- --dry-run
```
The dry run checks desktop version parity without writing release assets.
## 2.11 Rust toolchain boundary
OpenSymphony 2.11.0 requires Rust 1.97.1 for the root CLI and desktop crate and
uses Cargo Resolver 3. The repository toolchain, package `rust-version`, Clippy
MSRV, CI toolchain, and desktop metadata must remain aligned.
Users upgrading from a CLI older than 2.11 may need to bypass an older
checkout-local toolchain override:
```bash
rustup update stable
cargo +stable install opensymphony --locked
```
## M12.9 Code Graph desktop release gate
The Code Graph follow-on is release-ready only when the web and packaged
desktop shells use the production HTTP/native adapters and the empty-database
index action is present in the installed bundle. Before publishing, verify
that the root crate and desktop metadata remain in lock-step across
`Cargo.toml`, `apps/desktop/package.json`, `apps/desktop/src-tauri/Cargo.toml`,
`apps/desktop/src-tauri/Cargo.lock`, `apps/desktop/src-tauri/tauri.conf.json`,
and the root `package-lock.json`.
Use the default bundled-mode checks plus the package parity guard:
```bash
cargo clippy --all-targets -- -D warnings
cargo test
npm run build --workspace=@opensymphony/desktop
npm run package:release --workspace=@opensymphony/desktop -- --dry-run
```
The dry run must pass without creating a release archive. The desktop smoke
must launch the packaged bundle against a real gateway and verify repository
indexing, progress/error/retry rendering, completion refresh, and target
revision provenance; fixture mode is only a visualization-workbench check.