feat: MemoryProof memory assurance v1

[Hughhhhcoder]

What this ships

• Rebrand ForgetProof as MemoryProof while keeping v0.1 compatibility readers and binary.
• Add the Erasure and Isolation suites with stable scenario/protocol/evidence contracts.
• Add deterministic clean, leaky, over-delete, and isolation reference scenarios.
• Complete Mem0, Letta, and Zep adapters with ownership guards and local mock contract coverage.
• Add bilingual English-first README/docs, generated hero visual, offline reports, public evidence bundles, and static matrix.
• Add multi-platform release workflow, multi-architecture GHCR build with SBOM/provenance, Docker Action, Pages, CodeQL, Scorecard, and Dependabot.

Verification

• Rust fmt, clippy, workspace tests
• Python adapter tests and compilation
• Reference PASS/FAIL assertions and SHA-256 tamper verification
• Mem0/Letta/Zep local mock contract scenarios

The checked-in provider bundles are explicitly labeled local mock contract evidence; they are not claims about hosted provider behavior.

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.