Remove dated ops logs and stale planning records

.gitignore

@@ -58,3 +58,6 @@ functions/.env.*
 
 # Personal Claude Code permissions with absolute local paths
 .claude/settings.local.json
+
+# Generated by the periodic repo-scout agent
+NEXT-STEPS.md

README.md

@@ -4,7 +4,7 @@ MetaCortex is a serverless MCP memory service backed by Firestore vector search
 
 ## Status and roadmap
 
-MetaCortex is already released (repository tag `v0.3.0`). This checkout contains a reconciled local baseline; publication and production deployment are separate operations. See the [baseline record](docs/operations/2026-10-01-adoption-baseline.md), [unified roadmap](metacortexplan.md), and [immediate next steps](NEXT-STEPS.md).
+MetaCortex is already released (repository tag `v0.3.0`). This checkout contains a reconciled local baseline; publication and production deployment are separate operations. See the [unified roadmap](metacortexplan.md).
 
 The browser setup wizard, owner login/OAuth, management dashboard, and ChatGPT extension are planned, not available in this baseline. Software is MIT-licensed; owners pay their own Firebase/model usage and agent subscriptions. One installation holds one owner's shared corpus; profiles do not provide tenant isolation.
 

docs/ARCHITECTURE.md

@@ -2,7 +2,7 @@
 
 ## Current implementation
 
-MetaCortex is an already-released, serverless user-memory service: Express and the MCP SDK run in Firebase Cloud Functions 2nd Gen; Firestore stores canonical memories and vectors. The [roadmap](../metacortexplan.md) is authoritative for future work. The [baseline record](operations/2026-10-01-adoption-baseline.md) distinguishes local integration from deployment evidence.
+MetaCortex is an already-released, serverless user-memory service: Express and the MCP SDK run in Firebase Cloud Functions 2nd Gen; Firestore stores canonical memories and vectors. The [roadmap](../metacortexplan.md) is authoritative for future work.
 
 ```mermaid
 flowchart TD

docs/DEPLOYMENT.md

@@ -1,6 +1,6 @@
 # Deployment and operator playbook
 
-This guide describes the current local baseline, not the planned browser installer. See the [unified roadmap](../metacortexplan.md), [baseline evidence](operations/2026-10-01-adoption-baseline.md), and [security boundaries](SECURITY.md). MetaCortex is already released. Card 66 subsequently deployed on 2026-10-03 UTC; see the [rollout record](operations/2026-10-03-card66-rollout.md).
+This guide describes the current local baseline, not the planned browser installer. See the [unified roadmap](../metacortexplan.md) and [security boundaries](SECURITY.md). MetaCortex is already released.
 
 ## Current contract
 
@@ -82,7 +82,7 @@ firebase deploy --project <alias> --only functions
 
 The Functions predeploy hook builds the source. The alias selects `.env.<alias>`; passing a raw project ID may load a different dotenv file. Always verify effective non-secret settings.
 
-Existing production Secret Manager migration is complete: [card-23 record](operations/2026-09-09-secret-migration.md). Do not repeat the plaintext migration or rotate credentials merely because deployment docs changed.
+Existing production Secret Manager migration completed on 2026-09-09. Do not repeat the plaintext migration or rotate credentials merely because deployment docs changed.
 
 ## TTL and retention
 

docs/SECURITY.md

@@ -7,7 +7,7 @@ This document describes current implementation and accepted policy. Planned cont
 - Dedicated client tokens, tool allowlists, readable-state allowlists, and per-profile origin rules.
 - Separate admin endpoint and three-tool ordinary-agent profiles; `list_context` requires an explicit grant.
 - Firestore rules deny direct client access to memory, audit, fingerprint, and evaluation collections. Admin SDK access uses IAM.
-- Runtime secrets are bound through Secret Manager. The [2026-09-09 migration](operations/2026-09-09-secret-migration.md) is complete; it did not rotate credentials.
+- Runtime secrets are bound through Secret Manager. The 2026-09-09 migration is complete; it did not rotate credentials.
 - Requests have a 1 MB JSON limit, including base64 image input. Raw image assets are not stored.
 - Full retrieval-query telemetry is opt-in. Audit summaries can still include a query preview and error metadata; treat them as private data.