Release: dev → main (wagl v0.2.0)

[GoZumie]

Release v0.2.0

Merges all recall quality phases (5–9) plus vec0.so static linking fix (v0.1.1) into main.

See the phase4-recall-quality PR for the detailed changelog.

PR Review by Greptile

Greptile Summary

This release (v0.2.0) merges phases 5–9 of the recall quality initiative plus the critical sqlite-vec static linking fix from v0.1.1.

Major additions:

• Static sqlite-vec linking — Eliminates external .so dependency via sqlite3_auto_extension with OnceLock for thread-safe one-time registration
• Memory graph (Phase 5) — Adds edges, pathways (derived_from), connections (related_to), link/neighbors commands, and document reconstruction
• Intent awareness (Phase 6.5) — Term/alias mappings for canonical concepts with org/person context; enables intent-aware recall expansion
• People & trust (Phase 5.5) — -5 to +5 trust scoring with lock capability and adjustment tracking
• Observability (Phase 6) — stats, gc, decay, audit-quality commands; salience decay with configurable half-life
• Canonical memory (Phase 4/7) — canon commands (get/set/list), recall context packs, reconcile for quality checks, sleep reflection, morning briefs
• HTTP server (Phase 9.1) — Axum-based REST API with multi-agent namespace isolation (agent:<id> tags)
• WebSocket streaming (Phase 9.3) — Real-time memory event broadcasts to subscribers
• Transcript ingestion (Phase 8) — Imports OpenClaw sessions with regex-based credential redaction, size policy, and idempotent deduplication

Documentation:

• New: MEMORY_DOCTRINE.md, CANONICALS.md, WORKFLOWS.md, OPENCLAW_INTEGRATION.md
• Updated: sqlite-vec.md (reflects static linking), README.md (acknowledges sqlite-vec)

All changes are well-structured, include proper error handling, and maintain backward compatibility. The static linking fix significantly improves deployment ergonomics.

Confidence Score: 5/5

• This release is safe to merge with no critical issues identified
• All code is well-structured with proper error handling, thread safety (OnceLock), credential redaction, idempotent operations, and comprehensive documentation. The static linking fix eliminates a deployment pain point. The feature additions follow consistent patterns and maintain backward compatibility.
• No files require special attention

Important Files Changed

Filename	Overview
crates/db/src/vector_ext.rs	Replaces dynamic .so loading with static linking via sqlite3_auto_extension; uses OnceLock for thread-safe one-time registration
crates/server/src/lib.rs	New HTTP server with Axum providing REST API + WebSocket streaming for memory events; includes multi-agent namespace isolation
crates/db/src/lib.rs	Adds memory graph (edges), intent tracking, people/trust management, stats/observability APIs; splits schema init into smaller batches for better error diagnosis
crates/cli/src/main.rs	Adds 11 new commands (canon, recall, reconcile, audit-quality, sleep, trust, link, neighbors, intent, serve, ingest, reconstruct, decay, morning, gc, stats) implementing phases 5-9
crates/cli/src/ingest_cmd.rs	New transcript importer with regex-based redaction (secrets, tokens, credentials), size policy enforcement, and idempotent deduplication
crates/core/src/types.rs	Adds MemoryEdge, IntentItem, and MemoryHint (compact 51-byte binary format) types for graph and intent features
README.md	Documents static linking of sqlite-vec (no external .so required) and adds acknowledgements section
docs/sqlite-vec.md	Updated to reflect static linking approach; removes manual build instructions and .so path configuration
crates/db/Cargo.toml	Adds sqlite-vec (v0.1.7-alpha.10) and libsql-ffi (v0.5) dependencies for static linking
crates/server/Cargo.toml	New server crate with Axum, tower-http CORS, and tokio-stream dependencies

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    CLI[wagl CLI<br/>main.rs]
    Server[HTTP Server<br/>Axum + WebSocket]
    DB[(MemoryDb<br/>libSQL)]
    Vec[sqlite-vec<br/>static linked]
    
    CLI -->|put/query/recall| DB
    CLI -->|wagl serve| Server
    Server -->|REST API| DB
    Server -->|WebSocket events| Agents[External Agents]
    DB -->|vector search| Vec
    
    subgraph "New Phase 5-9 Features"
        Graph[Memory Graph<br/>edges/pathways]
        Intent[Intent System<br/>term mappings]
        Trust[People & Trust<br/>-5 to +5 scale]
        Ingest[Transcript Ingest<br/>redaction + dedupe]
        Canon[Canonical Memory<br/>single source of truth]
    end
    
    DB --> Graph
    DB --> Intent
    DB --> Trust
    CLI -->|wagl ingest| Ingest
    Ingest --> DB
    CLI -->|wagl canon| Canon
    Canon --> DB
    
    style Vec fill:#e1f5ff
    style Server fill:#fff4e1
    style Graph fill:#e8f5e9
    style Intent fill:#e8f5e9
    style Trust fill:#e8f5e9
    style Ingest fill:#e8f5e9
    style Canon fill:#e8f5e9

Loading

_{Last reviewed commit: e9d8a8b}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 18e1669965

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: e9d8a8b1fa

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[GoZumie]

@ChrisCompton ready for your review and merge approval