docs: rename the memory kit field to agentContext

Rename the spec.yaml memory: field to agentContext: across the spec
reference, overview, and tutorial, and update the section heading,
anchor, and cross-links. The memory file artifact and kits-memory/
directory keep their names.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: dvdksn

content/manuals/ai/sandboxes/customize/build-an-agent.md

@@ -85,7 +85,7 @@ agent:
 ```
 
 - `aiFilename: AGENTS.md` tells the sandbox to create `AGENTS.md` at launch
-  and append the [`memory`](#prime-amp-with-memory) block to it. Amp reads
+  and append the [`agentContext`](#prime-amp-with-memory) block to it. Amp reads
   this file for instructions.
 - `entrypoint.run` runs `amp` in "YOLO-mode" when the sandbox starts. Adjust if
   you want to pass different args on startup.
@@ -153,12 +153,12 @@ pick any name.
 
 ## Prime Amp with memory
 
-The `memory` field appends markdown to `AGENTS.md` at sandbox creation.
+The `agentContext` field appends markdown to `AGENTS.md` at sandbox creation.
 Use it to tell Amp about the sandbox environment so it knows the
 conventions when it starts.
 
 ```yaml
-memory: |
+agentContext: |
   ## Sandbox environment
 
   You are running inside a Docker sandbox. The workspace is mounted at
@@ -204,7 +204,7 @@ commands:
       user: "1000"
       description: Install Amp
 
-memory: |
+agentContext: |
   ## Sandbox environment
 
   You are running inside a Docker sandbox. The workspace is mounted at
@@ -282,7 +282,7 @@ Two loops help:
 - Edit the spec and re-run `sbx run --kit ./amp/ amp` to pick up changes.
   Remove the sandbox first (`sbx rm <name>`) for a clean start.
 
-Flesh out the `memory` block as you refine how Amp should behave in the
+Flesh out the `agentContext` block as you refine how Amp should behave in the
 sandbox.
 
 ## Publish
@@ -311,7 +311,7 @@ the same decisions for your agent:
   placeholder. If it accepts the env var as-is, declare
   `environment.proxyManaged` in the kit and skip the user-side step.
 
-The rest — memory block, network-policy iteration, packaging — is the
+The rest — agent-context block, network-policy iteration, packaging — is the
 same regardless of agent.
 
 ## Remove the stored secret

content/manuals/ai/sandboxes/customize/kit-reference.md

@@ -1,7 +1,7 @@
 ---
 title: Kit spec reference
 linkTitle: Spec reference
-description: Field-by-field reference for a kit's spec.yaml — credentials, network rules, environment, commands, files, memory, and the agent block.
+description: Field-by-field reference for a kit's spec.yaml — credentials, network rules, environment, commands, files, agent context, and the agent block.
 keywords: sandboxes, sbx, kits, spec.yaml, reference, schema, fields
 weight: 22
 ---
@@ -264,10 +264,10 @@ Parent directories are created automatically. Existing files are
 overwritten. Absolute paths and path-traversal sequences (`../../`) are
 rejected.
 
-## Memory
+## Agent context
 
 ```yaml
-memory: |
+agentContext: |
   <markdown>
 ```
 
@@ -283,10 +283,10 @@ sandbox, not to the workspace itself. For a workspace mounted at
 `/Users/you/AGENTS.md` (or whatever `aiFilename` is set to). It exists
 only inside the sandbox. Nothing is written to the host.
 
-When several loaded kits declare `memory:` blocks, the content is split
+When several loaded kits declare `agentContext:` blocks, the content is split
 across files instead of being concatenated into the main one:
 
-- Each kit's memory is written to `<kit-name>.md` in a sibling
+- Each kit's agent context is written to `<kit-name>.md` in a sibling
   `kits-memory/` directory next to the main memory file.
 - The main memory file gets a `## Kits` section listing every kit with
   a pointer to its file. The section is delimited by
@@ -306,12 +306,12 @@ agent:
     args: [<arg>, ...]
 ```
 
-| Field                   | Required | Description                                                                                    |
-| ----------------------- | -------- | ---------------------------------------------------------------------------------------------- |
-| `agent.image`           | Yes      | Docker image reference. See [Base image requirements](#base-image-requirements).               |
-| `agent.aiFilename`      | No       | Memory filename (for example, `AGENTS.md`). Appends top-level [`memory`](#memory) at creation. |
-| `agent.entrypoint.run`  | No       | Command and args as a string array. Replaces the image's entrypoint.                           |
-| `agent.entrypoint.args` | No       | Args appended to the image's existing entrypoint.                                              |
+| Field                   | Required | Description                                                                                                 |
+| ----------------------- | -------- | ----------------------------------------------------------------------------------------------------------- |
+| `agent.image`           | Yes      | Docker image reference. See [Base image requirements](#base-image-requirements).                            |
+| `agent.aiFilename`      | No       | Memory filename (for example, `AGENTS.md`). Appends top-level [`agentContext`](#agent-context) at creation. |
+| `agent.entrypoint.run`  | No       | Command and args as a string array. Replaces the image's entrypoint.                                        |
+| `agent.entrypoint.args` | No       | Args appended to the image's existing entrypoint.                                                           |
 
 ### Base image requirements
 

content/manuals/ai/sandboxes/customize/kits.md

@@ -203,16 +203,16 @@ the agent project conventions, usage tips for a tool the kit installs,
 or other guidance that should be in scope when the sandbox runs.
 
 ```yaml
-memory: |
+agentContext: |
   Ruff is installed. Run `ruff check` before committing.
   Shared config lives at `/workspace/ruff.toml`.
 ```
 
-Both mixin and agent kits can declare `memory:`. The content is written
+Both mixin and agent kits can declare `agentContext:`. The content is written
 only when the active agent kit sets [`agent.aiFilename`](kit-reference.md#agent-block),
 which determines the memory file's name.
 
-When more than one loaded kit declares a `memory:` block, each kit's
+When more than one loaded kit declares an `agentContext:` block, each kit's
 content is written to its own `<kit-name>.md` file under a sibling
 `kits-memory/` directory. The main memory file gets a `## Kits` section
 that points to each kit file:
@@ -227,7 +227,7 @@ that points to each kit file:
     └── git-ssh-sign.md
 ```
 
-See [`memory`](kit-reference.md#memory) in the spec reference for the full field schema.
+See [`agentContext`](kit-reference.md#agent-context) in the spec reference for the full field schema.
 
 ### Define an agent
 
@@ -460,7 +460,7 @@ Docker credential store, so pushing to a private registry requires a prior
 
 For a field-by-field reference of every `spec.yaml` block — top-level
 fields, credentials, network, environment, commands, static files,
-memory, and the agent block — see [Kit spec reference](kit-reference.md).
+agent context, and the agent block — see [Kit spec reference](kit-reference.md).
 
 ## Debugging