docs(agent-memory): consolidate PR #95 content, move to top-level Memory section

Major restructure of the Agent Memory docs to address user feedback:

1. Promote Agent Memory to its own top-level section in the sidebar.
   New 'Memory (Research Preview)' group sits inside the Agents topic
   between Getting started and Warp Agents for top-of-list visibility.

2. Move the page from agent-platform/capabilities/agent-memory/ to
   agent-platform/agent-memory/ to match the new section's IA. The
   '/agent-platform/capabilities/agent-memory' URL now redirects to
   '/agent-platform/agent-memory/' via vercel.json.

3. Add '(Research Preview)' marker to the sidebar label, matching the
   page title and the existing Settings Sync (Beta) precedent.

4. Replace 'workspace' with 'team' in user-facing copy. The
   implementation-layer WORKSPACE enum is internal and unaffected.

5. Consolidate PR #95 (hyc/memory-waitlist) content into the page.
   PR #95 had been opened separately as a marketing/waitlist rewrite
   from another conversation. Taking its richer body (8 capability
   bullets, dedicated sections for Personal/team stores, Automatic
   memory from conversations with Sparse/Reasoned/Reversible
   sub-bullets, How agents retrieve memories with the
   Vector+BM25+Reranking pipeline, Attaching memory to agents
   covering identity-level and run-level attachments, and Built for
   teams), stronger CTAs (bold-link waitlist CTA after hero + 'Ready
   to give your agents memory?' closer), and richer 5-link related
   pages. Restores the research-preview caution callout that PR #95
   had dropped, keeps the (Research Preview) title, and uses 'team'
   throughout. PR #95 will be closed in a follow-up.

6. Use generic 'agents' / 'your agents' / 'Warp agents' framing
   throughout. Memory is gated to cloud agents today but will work
   for local agents going forward, so the docs don't specify cloud
   vs local. The research-preview caution carries any 'behavior may
   change before GA' hedge.

7. Capability claims (deletion safety, per-store instructions,
   versioned history, hybrid semantic+keyword search) all match
   the QUALITY-585 and QUALITY-536 specs.

Files touched:
- src/content/docs/agent-platform/agent-memory/index.mdx (new)
- src/content/docs/agent-platform/capabilities/agent-memory/index.mdx (deleted)
- src/content/docs/agent-platform/capabilities/index.mdx (Agent Memory bullet removed)
- src/content/docs/agent-platform/capabilities/skills.mdx (link URL updated)
- src/sidebar.ts (new Memory group)
- vercel.json (old URL redirect)

Validation:
- style_lint --changed: only the known pre-existing false positive on
  skills.mdx:414 Suggested Skills from Agent Memory header (both
  'Skills' and 'Agent Memory' are proper feature names per AGENTS.md).
- check_links --internal-only: 0 broken across 319 files and 2,422
  internal links. New URL resolves cleanly.

Co-Authored-By: Oz <oz-agent@warp.dev>

Author: hongyi-chen

src/content/docs/agent-platform/agent-memory/index.mdx

@@ -0,0 +1,88 @@
+---
+title: Agent Memory (Research Preview)
+description: >-
+  Agent Memory gives your Warp agents persistent, searchable memory across
+  conversations, so they remember team conventions, past decisions, and what
+  you taught them.
+sidebar:
+  label: "Agent Memory (Research Preview)"
+---
+:::caution
+Agent Memory is in **research preview** and is enabled per team for design partners. [Join the waitlist](https://warp.dev/oz/agent-memory#waitlist) to request access for your team.
+:::
+
+Agent Memory is a persistent, cross-conversation memory layer for Warp agents. Instead of starting from scratch every run, your agents recall durable knowledge — team conventions, past decisions, deployment outcomes, your preferences — and apply it to the work in front of them. Each run begins further along than the last.
+
+[**Join the Agent Memory waitlist →**](https://warp.dev/oz/agent-memory#waitlist)
+
+## What you get with Agent Memory
+
+* **Durable knowledge across conversations** — Agents remember what happened in previous runs and surface it as context for the current task.
+* **Personal and team memory stores** — Keep memories private to you, or share them across your team so every teammate and agent draws from the same well of knowledge.
+* **Automatic memory from conversations** — Warp extracts facts, learnings, and outcomes from finished conversations and writes them as memories, with a recorded reason for every change.
+* **Hybrid semantic and keyword search** — Memory retrieval combines vector similarity and full-text search, reranked for relevance, so the right memory surfaces even when wording shifts.
+* **Versioned history** — Every memory keeps its full version history. Older content is always recoverable, and updates record why the change was made.
+* **Per-agent access control and instructions** — Attach memory stores to an agent identity with read-only or read-write access, and write per-store instructions that tell the agent how and when to use each store.
+* **Cross-harness persistence** — Memories live on Warp, not inside any single agent harness, so the same knowledge follows your work across harnesses and triggers.
+* **Safe by default** — Memory stores in active use can't be accidentally deleted, so shared team knowledge can't disappear out from under live agents.
+
+## Personal and team memory stores
+
+A memory store is a named container for memories. Stores are owned by either a person or a team.
+
+* **Personal stores** capture knowledge that's yours: preferences, working notes, individual patterns. Your agents draw from your personal store automatically.
+* **Team stores** capture shared knowledge: deployment runbooks, code review conventions, customer specifics, on-call procedures. Every team member and every agent the team authorizes can read from the same store.
+
+Use multiple stores to keep contexts clean. A deploy bot has its own store for past deployments, a PR review bot has its own store for team conventions, and a customer-success agent has its own store for account histories.
+
+## Automatic memory from conversations
+
+You don't have to remember to save things. When a conversation finishes, Warp runs a memory synthesis pass that extracts durable facts, learnings, and outcomes from what happened, then writes them as memories.
+
+* **Sparse by design.** Routine work produces nothing. Only meaningful, reusable knowledge becomes a memory.
+* **Reasoned.** Every create, update, or delete records the reason — so future you can see why a memory exists.
+* **Reversible.** Synthesis can merge new knowledge into existing memories, supersede outdated ones, or tombstone memories that no longer hold. Older versions remain in history if you need to look back.
+
+You can also explicitly tell Warp to remember something during a conversation, and it lands in the right store with the right context.
+
+## How agents retrieve memories
+
+When an agent starts a task, Warp searches its accessible memory stores for relevant context and injects what it finds. The retrieval pipeline runs every query through:
+
+1. **Vector search** for semantic similarity, even when the agent's wording doesn't match the memory's wording exactly.
+2. **Keyword (BM25) search** for exact terms, names, IDs, and identifiers that matter to your work.
+3. **Reranking** to score the combined results and pick the few most relevant memories for the task.
+
+The agent sees those memories alongside the rest of its context, just like rules and Codebase Context. You don't have to write retrieval queries or pre-load memory by hand.
+
+## Attaching memory to your agents
+
+You decide which agents can read from which stores.
+
+* **Attach a store to an agent identity** to give a named agent durable access across every one of its runs. Pair it with **read-only** or **read-write** access and free-form **instructions** that tell the agent how to use the store — for example, "Reference this store for team naming conventions" or "Write a new memory after each successful deployment."
+* **Attach a store to a single run** when you want to augment one task without changing the agent's permanent setup. Run-level attachments are additive on top of the agent identity's stores, and they win on conflict if you want to override access or instructions for that run.
+
+Instructions matter. They're how you turn raw storage into a useful tool — the difference between an agent that "has memory" and an agent that knows what to remember and when.
+
+## Built for teams
+
+Agent Memory is designed to be shared.
+
+* **Team-owned stores** are accessible to every member of the team and to the agents the team authorizes, so the whole team builds on the same knowledge base.
+* **Personal stores** stay private. Your memories are yours.
+* **Authorization is explicit.** Stores have to be attached to an agent before that agent can read or write. Nothing is implicit, and you can audit which agents touch which stores.
+* **Deletion safety.** A store with active agent attachments can't be deleted. If you try, Warp tells you which agents are still using it, so shared memory can't quietly vanish.
+
+## Ready to give your agents memory?
+
+Stop watching agents re-learn the same things every run. With Agent Memory, what your agents learn today makes them sharper tomorrow.
+
+[**Join the Agent Memory waitlist →**](https://warp.dev/oz/agent-memory#waitlist)
+
+## Related pages
+
+* [Codebase Context](/agent-platform/capabilities/codebase-context/) — Let agents understand your codebase through semantic indexing.
+* [Rules](/agent-platform/capabilities/rules/) — Define global and project-level guidelines that shape agent behavior.
+* [Skills](/agent-platform/capabilities/skills/) — Reusable, scoped instructions that teach agents how to perform specific tasks.
+* [Agent profiles and permissions](/agent-platform/capabilities/agent-profiles-permissions/) — Control what permissions and autonomy agents have.
+* [Cloud agents overview](/agent-platform/cloud-agents/overview/) — Run background agents with team-wide observability.

src/content/docs/agent-platform/capabilities/agent-memory/index.mdx

@@ -21,7 +21,6 @@ Understanding these capabilities helps you get the most out of agents by configu
 * [Computer Use](/agent-platform/capabilities/computer-use/) - Let agents interact with desktop environments by taking screenshots, clicking, typing, and controlling the GUI.
 * [MCP](/agent-platform/capabilities/mcp/) - Connect external data sources and tools to Warp's agents via the Model Context Protocol.
 * [Codebase Context](/agent-platform/capabilities/codebase-context/) - Let agents understand your codebase through semantic indexing of your Git-tracked files.
-* [Agent Memory](/agent-platform/capabilities/agent-memory/) - Persistent, cross-harness memory layer that lets cloud agents carry context from one run to the next (research preview).
 * [Agent Profiles & Permissions](/agent-platform/capabilities/agent-profiles-permissions/) - Control what permissions and autonomy agents have to run commands and apply changes.
 * [Web Search](/agent-platform/capabilities/web-search/) - Allow agents to search the web for up-to-date information.
 

src/content/docs/agent-platform/capabilities/index.mdx

@@ -413,7 +413,7 @@ These same skills also appear as suggested agents in the [Oz web app](/agent-pla
 
 ## Suggested Skills from Agent Memory
 
-Promoting recurring patterns from [Agent Memory](/agent-platform/capabilities/agent-memory/) into reviewable skill drafts is in design as part of the research preview. See the Agent Memory page for current status.
+Promoting recurring patterns from [Agent Memory](/agent-platform/agent-memory/) into reviewable skill drafts is in design as part of the research preview. See the Agent Memory page for current status.
 
 ## Invoking skills with a prompt
 

src/content/docs/agent-platform/capabilities/skills.mdx

@@ -246,6 +246,12 @@ export const sidebarTopics: StarlightSidebarTopicsUserConfig = [
 						'agent-platform/getting-started/faqs',
 					],
 				},
+				{
+					label: 'Memory (Research Preview)',
+					items: [
+						{ slug: 'agent-platform/agent-memory', label: 'Agent Memory' },
+					],
+				},
 				{
 					label: 'Warp Agents',
 					items: [

src/sidebar.ts

@@ -9572,6 +9572,11 @@
       "source": "/oz",
       "destination": "/agent-platform/cloud-agents/overview/",
       "statusCode": 308
+    },
+    {
+      "source": "/agent-platform/capabilities/agent-memory",
+      "destination": "/agent-platform/agent-memory/",
+      "statusCode": 308
     }
   ]
 }