docs: fix drift in Google AntiGravity

[jack-arturo]

Routine docs-accuracy audit of src/content/docs/docs/platforms/antigravity.md (never previously reviewed — this page has no entry in scripts/file-doc-map.json, so no source change has ever flagged it).

Claim	Current state	Fix	Evidence
"Tagging convention" example recommends "tags": ["project-name", "antigravity", "YYYY-MM", "component-name"]	Two of those four tags are exactly what the shipped memory policy tells agents not to write. src/memory-policy/shared.ts is the generated-policy source of truth for every host template, and it states: "use automem, not project/automem; no lang/ prefixes, platform tags, or date-stamped tags" (L362), emits // bare strings; NO platform tag, NO [YYYY-MM] directly into the store example it generates (L462), and repeats it as a hard rule at L805. antigravity is a platform tag and YYYY-MM is the date-stamped form named in the rule.	Dropped both tags from the example and added a sentence stating the bare-tag rule and pointing at t_valid/t_invalid for shelf-life facts (the policy's own stated replacement, L468).	shared.ts#L362, shared.ts#L462, shared.ts#L805
Verification section: "Expected response includes: FalkorDB connection status / Qdrant connection status / Service version"	/health returns no version field of any kind. The handler builds a fixed dict of status, falkordb, qdrant, memory_count, vector_count, sync_status, vector_dimensions, enrichment, timestamp, graph — nothing carrying a service or package version. The MCP client agrees: the HealthStatus interface has status, backend, statistics, error and no version member, so check_database_health cannot surface one either.	Replaced the "Service version" bullet with the memory/vector counts and sync_status, and noted the two literal connection values (connected / disconnected).	health.py#L87-L110, types.ts#L148-L163

Spot-checked and correct, left untouched:

• All six tool names (store_memory, recall_memory, associate_memories, update_memory, delete_memory, check_database_health) match the tools array in src/index.ts (L468, L658, L1080, L1207, L1305, L1370).
• Package name @verygoodplugins/mcp-automem, the npx -y invocation, and the node /path/to/mcp-automem/dist/index.js local-build form all match package.json (main/bin both dist/index.js).
• AUTOMEM_API_URL / AUTOMEM_API_KEY are the correct env var names, and the "required for cloud, optional for local" split is accurate.
• Every path in "Related Platforms": Cursor ~/.cursor/mcp.json (cursor.ts#L150) + .cursor/rules/automem.mdc (cursor.ts#L244), Claude Code ~/.claude.json + ~/.claude/settings.json, Codex ~/.codex/config.toml.

Verified against: verygoodplugins/mcp-automem@946f9e5, verygoodplugins/automem@8ff266e

Questions

• The "Tool Naming" section opens with "AntiGravity prefixes MCP tools with the server name" and then lists six unprefixed names (store_memory, not memory_store_memory or similar) — the section contradicts itself. AntiGravity's prefixing behavior isn't derivable from either AutoMem repo, so I can't tell which half is wrong, and the page's own :::note already hedges that "the exact tool prefix format may vary". Left alone; a maintainer with AntiGravity installed could settle it in one look at the tool list.

Unverified

• Everything in "Installation" Step 1 and Step 3 (MCP Store panel, "Manage MCP Servers", "View raw config", reload behavior) — AntiGravity editor UI with no in-repo counterpart.
• The :::note claiming AutoMem is "not yet available in AntiGravity's MCP Store" — no way to check the store's catalog from here.

Follow-ups

Below the severity bar for this PR:

• The Available Memory Tools table describes delete_memory as "Permanently remove a memory", omitting its bulk-by-tag mode (tags: [...] deletes every memory matching any tag), and store_memory as single-item, omitting batch mode (memories: [...], ≤500). Completeness gaps rather than inaccuracies.
• "Configuring Agent Instructions" presents importance values (0.9 / 0.8 / 0.7 / 0.5–0.7) per memory type. These match the spirit of the shared policy but aren't drawn from any code constant, so they read as editorial guidance — not flagged as drift, but worth aligning with shared.ts if that policy is meant to be canonical everywhere.

---

Generated by Claude Code as part of the recurring automem-docs-review routine.

---

Generated by Claude Code

[cloudflare-workers-and-pages]

Deploying automem-website with    Cloudflare Pages

Latest commit:	75b3eca
Status:	✅  Deploy successful!
Preview URL:	https://f84d515a.automem-website.pages.dev
Branch Preview URL:	https://docs-audit-platforms-antigra.automem-website.pages.dev

View logs