Protect memory blocks from agent writes

[NarwhalChen]

Summary

• add a persisted read-only flag to memory blocks, defaulting legacy blocks to writable
• reject primary-agent and subconscious updates to protected blocks at the store boundary while preserving existing versioning and write-ahead serialization
• expose label, version, and protection state in Agent Work with Protect and Unlock controls without copying memory content into the renderer

Boundaries

• provider-native sessions continue to own provider history
• renderer and Dexie continue to own channel transcripts
• restricted memory curator remains text-only with no shell, CUA, or general MCP access
• no additional write queue was introduced

Verification

• pnpm --filter @convera/app test -- --reporter=dot: 564 passed, 1 skipped
• full repository pre-push formatting, lint, and test hooks passed
• pnpm --filter @convera/app exec tsc --noEmit --skipLibCheck
• Node 22 automation:prepare
• real Electron isolated-profile Protect to Unlock to Protect flow; readOnly true persisted at version 4
• no real provider invoked

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
foxyfox-docs	Error		Aug 2, 2026 12:47pm

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
foxyfox-website	Skipped		Aug 2, 2026 12:47pm