[vinayagg]

What broke

Thread execution lacks a compact durable brief, and learned team outcomes remain isolated on individual desktops. Retaining whole final answers can also carry unsupported or outdated claims into later work.

Why

Execution context, reusable knowledge, and authoritative task state need distinct persistence and sharing rules.

What changed

• Add durable thread briefs, bounded prompt context, and context-aware helper delegation.
• Replace blanket final-answer retention with source-backed knowledge proposals, conservative automatic learning, and chat corrections. Keep unsupported proposals private to their thread.
• Synchronize curated knowledge over existing encrypted peer connections using durable offline queues, revisions, conflict receipts, and deletion tombstones. Preserve continuity across team-owner transfers.
• Track assignment dependencies, blockers, execution status, and explicit handoff acceptance separately.
• Keep personal preferences account-local and allow company knowledge to be published to selected teams in the same organization, with correction and deletion propagation.
• Add knowledge-management controls, local-index configuration, regression coverage, and architecture documentation in docs/local-memory.md.

Tested

• 41 focused memory, context, synchronization, UI, runner, activity, instructions, team, and store tests pass.
• TypeScript checking, desktop and hosted UI builds, page-fetch checks, file-lock tests, AI connection tests, and subscription tests pass.
• The broader client run reports 249 passes and 23 network-related failures: 20 fail with sandbox listen EPERM; three WebRTC failures reproduce on unchanged source. Consequently, the complete npm run check cannot pass in this environment.
• Live synchronization between two real desktops remains unverified. Synchronization waits for the team owner's desktop to be online; offline changes remain queued locally.

Not touched

No server API, cloud memory database, or Rust changes. Existing explicitly configured Hindsight endpoints remain supported. Legacy outcomes remain local and unverified rather than being automatically published to teammates.