Clean up Memory Recall repository and product identity

[rebel0789]

What changed

• made Memory Recall the canonical name across repository guidance, CLI help, web/API surfaces, protocol metadata, Rust docs, generated reports, and consumer examples
• preserved oaf commands, URIs, task IDs, package scopes, and server keys where they are compatibility contracts
• marked 1.1.0 honestly as an unreleased release candidate and restored the missing 1.0.4/1.0.5 changelog trail
• ignored local .scratch/ review artifacts and regenerated repository/release provenance
• added regression coverage for canonical naming and current public product surfaces

Why

The rename had reached the primary product shell, but canonical repository metadata, CLI topic banners, generated memory copy, API/schema titles, and release evidence could still revive the retired product name. That made GitHub and installed-package truth inconsistent.

User and developer impact

New output consistently says Memory Recall. Existing oaf compatibility entrypoints and protocol identifiers continue to work. This does not publish memory-recall@1.1.0 or enable external writes, models, adapters, or network defaults.

Root cause

The rebrand was handled as several surface edits rather than a tested canonical identity boundary. Generated release evidence also retained the old 655-test snapshot after four new regressions were added.

Verification

• npm run ci: 969 repository files checked, 182/182 protocol fixtures, 659/659 Node tests, 144/144 evaluations
• npm run consumer:smoke: package, first-run Recall Map, temp-HOME install, real MCP client, and Control API flows passed
• npm run consumer:browser-smoke: desktop/mobile Recall Map, handoff, harness, Token Saver, memory, and graph flows passed
• npm pack --dry-run --json: memory-recall@1.1.0 package dry-run succeeded
• npm audit --omit=dev: 0 vulnerabilities

Repository cleanup completed separately

• removed obsolete merged, closed-review, superseded, and unsafe remote branches
• closed stale PR [codex] Rust breadth, setup, and governed graph surface #7 with its unresolved read-only/provenance/setup/ingest findings documented
• enabled squash-only merges, automatic merged-branch deletion, Dependabot security updates, secret scanning, and push protection
• restored GitHub release v1.0.5 at the exact git commit recorded by npm

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: c688180f10

ℹ️ About Codex in GitHub

Your team has set up Codex to 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 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Keep project status schema-valid

With PROJECT_STATUS.json now declaring memory-recall, any consumer that validates this canonical status file against packages/protocol/schemas/project-status.schema.json rejects it because the schema still has project.const set to open-agent-fabric; I confirmed the repo's validateJsonSchema reports a $.project const failure. Please update the governing schema/fixtures or keep a compatibility value so the status document remains schema-valid.

Useful? React with 👍 / 👎.