Add native React scoped Memory example

[blove]

The Memory example previously used one shared global store namespace and republished cached observations. It now captures a validated browser scope for each conversation and reads the actual store before the agent, each model call, and terminal confirmation. Angular keeps its existing presentation while using the same scoped backend.

Adds an experimental native React Memory example to the canonical website Docs, Code, and Run views. Teach and Recall fill unsent drafts; explicit Send creates an owned conversation. New conversations retain the browser scope, literal memory contents remain visible, and read-only historical restoration requires matching complete checkpoint reads. Storage changes and failed reads prevent false saved confirmation.

Validation: native unit tests 111; Angular 44; registry 101; full website 1705; CI scope 285; Scripts 499 passed with five existing skips; compiled Python 11; private fixture 28; native browser 16; Angular browser 6 plus lifecycle 3; website browser 7. TypeScript, installed builds, source/built package boundaries, and diff checks passed. Native lint reports 0 errors/72 warnings. Fresh desktop/mobile images were inspected. The parity inventory was regenerated on the clean source commit and its check passed. Runtime audits recognize the exact scoped Memory provider and compiled fixture while retaining generic protections and auditing excluded tests when production imports them.

The browser scope is a logical partition, not authentication. Checkpoints describe historical read-time observations; concurrent conversations may update the same file. Public deployment and bounded live teach/recall verification follow the ordinary merge and deployment checks.

[vercel]

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

Project	Deployment	Actions	Updated
threadplane	Ready	Preview	Oct 12, 2026 9:31pm UTC