[Bugfix][Store] Support Dummy external buffer registration

.claude-plugin/marketplace.json

@@ -0,0 +1,42 @@
+{
+  "$schema": "https://json.schemastore.org/claude-code-marketplace.json",
+  "name": "mooncake",
+  "owner": {
+    "name": "Mooncake Team"
+  },
+  "metadata": {
+    "description": "Built-in Claude Code skills for working with Mooncake: deployment troubleshooting, local CI validation, and the Python API."
+  },
+  "plugins": [
+    {
+      "name": "mooncake-troubleshoot",
+      "source": {
+        "source": "git-subdir",
+        "url": "https://github.com/kvcache-ai/Mooncake.git",
+        "path": ".claude/skills/mooncake-troubleshoot"
+      },
+      "description": "Systematically diagnose Mooncake deployment and runtime issues (services, RDMA, env vars, connectivity, logs) and propose fixes.",
+      "homepage": "https://kvcache-ai.github.io/Mooncake/skills/mooncake-troubleshoot.html"
+    },
+    {
+      "name": "mooncake-ci-local",
+      "source": {
+        "source": "git-subdir",
+        "url": "https://github.com/kvcache-ai/Mooncake.git",
+        "path": ".claude/skills/mooncake-ci-local"
+      },
+      "description": "Run Mooncake pre-PR local validation via scripts/run_ci_test.sh, reproducing the reproducible parts of GitHub Actions.",
+      "homepage": "https://kvcache-ai.github.io/Mooncake/skills/mooncake-ci-local.html"
+    },
+    {
+      "name": "mooncake-api",
+      "source": {
+        "source": "git-subdir",
+        "url": "https://github.com/kvcache-ai/Mooncake.git",
+        "path": ".claude/skills/mooncake-api"
+      },
+      "description": "Work with the Mooncake Store, Transfer Engine, and EP/Backend Python APIs.",
+      "homepage": "https://kvcache-ai.github.io/Mooncake/skills/mooncake-api.html"
+    }
+  ]
+}

.claude/skills/mooncake-api/.claude-plugin/plugin.json

@@ -0,0 +1,12 @@
+{
+  "$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
+  "name": "mooncake-api",
+  "description": "Work with the Mooncake Store, Transfer Engine, and EP/Backend Python APIs.",
+  "author": {
+    "name": "Mooncake Team"
+  },
+  "homepage": "https://kvcache-ai.github.io/Mooncake/skills/mooncake-api.html",
+  "repository": "https://github.com/kvcache-ai/Mooncake",
+  "license": "Apache-2.0",
+  "keywords": ["mooncake", "python", "api", "transfer-engine", "store"]
+}

.claude/skills/mooncake-api/SKILL.md

@@ -1,4 +1,7 @@
-<!-- Let's perfect this skill together. -->
+---
+name: mooncake-api
+description: Help users work with the Mooncake Python APIs for distributed storage and high-performance data transfer. Use when working with Mooncake Store (distributed KV cache), Transfer Engine (RDMA/TCP transfers), service setup (master, metadata server), PyTorch tensors in the Store, zero-copy/buffer management, batch operations and replication, or Mooncake EP / Backend (Expert Parallelism). Trigger on questions about MooncakeDistributedStore, TransferEngine, put/get, put_tensor, register_buffer, ReplicateConfig, or the mooncake.store / mooncake.engine / mooncake.pg Python modules.
+---
 
 # Mooncake Python API Skill
 
@@ -16,6 +19,14 @@ Use this skill when users ask about:
 - Mooncake EP (Expert Parallelism) and Mooncake Backend
 - Troubleshooting Mooncake Python API issues
 
+## Routing Guidance
+
+- For most vLLM and SGLang users, start from `docs/source/getting_started/quick-start.md`.
+- For PD disaggregation, direct users to the SGLang/vLLM integration guides listed in Quick Start. Those guides own the serving-framework configuration.
+- For Mooncake Store integrations, direct users to the SGLang/vLLM Store setup guides listed in Quick Start. Do not duplicate `mooncake_master` startup commands in general API answers unless the user is working outside those frameworks.
+- For direct low-level Transfer Engine usage, use `docs/source/design/transfer-engine/index.md#using-transfer-engine-in-your-projects`.
+- For API signatures and method details, use the Python API references under `docs/source/python-api-reference/`.
+
 ## Core Components
 
 ### 1. Mooncake Store (Distributed KV Cache)
@@ -304,6 +315,7 @@ mooncake_master --default_kv_lease_ttl=5000
 - `MC_STORE_MEMCPY`: Enable local memcpy optimization (set to "1")
 - `MC_STORE_CLIENT_METRIC`: Enable client metrics (enabled by default)
 - `MC_YLT_LOG_LEVEL`: Log level (trace/debug/info/warn/error/critical)
+- `MOONCAKE_STORE_CHECKSUM`: Enable diagnostic object-level CRC-64 checks (set to "1" before creating any writer or reader client)
 
 ## Common Patterns
 
@@ -462,6 +474,17 @@ if result != 0:
     raise RuntimeError(f"Failed to register buffer: {result}")
 ```
 
+### Corrupted Data or Garbled Output
+```python
+# Set this before importing Mooncake or creating any Store client.
+import os
+os.environ["MOONCAKE_STORE_CHECKSUM"] = "1"
+
+from mooncake.store import MooncakeDistributedStore
+```
+
+Enable the switch on every writer and reader client process, then reproduce with full-object `put`/`upsert` and `get` operations. Treat `CHECKSUM_MISMATCH` (-801) as a failed read and do not use the destination buffer. Objects without checksum metadata and range reads are not verified. This mode scans object data, stages GPU buffers to host memory, and disables the local hot cache, so use it only for diagnosis.
+
 ### Service Connectivity
 ```bash
 # Check master is running
@@ -507,6 +530,8 @@ curl http://localhost:8080/metadata
 ## Documentation Links
 
 - Full API Reference: https://kvcache-ai.github.io/Mooncake/
+- Quick Start: docs/source/getting_started/quick-start.md
 - Mooncake Store: docs/source/python-api-reference/mooncake-store.md
 - Transfer Engine: docs/source/python-api-reference/transfer-engine.md
+- Transfer Engine direct usage: docs/source/design/transfer-engine/index.md#using-transfer-engine-in-your-projects
 - EP Backend: docs/source/python-api-reference/ep-backend.md

.claude/skills/mooncake-ci-local/.claude-plugin/plugin.json

@@ -0,0 +1,12 @@
+{
+  "$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
+  "name": "mooncake-ci-local",
+  "description": "Run Mooncake pre-PR local validation via scripts/run_ci_test.sh, reproducing the reproducible parts of GitHub Actions.",
+  "author": {
+    "name": "Mooncake Team"
+  },
+  "homepage": "https://kvcache-ai.github.io/Mooncake/skills/mooncake-ci-local.html",
+  "repository": "https://github.com/kvcache-ai/Mooncake",
+  "license": "Apache-2.0",
+  "keywords": ["mooncake", "ci", "validation", "pre-pr"]
+}

.claude/skills/mooncake-ci-local/SKILL.md

@@ -0,0 +1,159 @@
+---
+name: mooncake-ci-local
+description: Run Mooncake pre-PR local validation through scripts/run_ci_test.sh. Use this skill whenever the user wants to validate a branch before opening or submitting a PR, run local CI, run ci test, check changes before PR, reproduce GitHub Actions locally, or force a full pre-submit verification. Trigger on phrases like "提交 PR 前验证", "run ci test", "run local CI", "check my branch", "test before PR", "pre-submit validation", and "reproduce CI locally".
+---
+
+# Mooncake Pre-PR Local Validation
+
+Use `bash scripts/run_ci_test.sh` as the default entry point. This is the single local lane for PR-before-submit validation, and it already coordinates the reproducible parts of GitHub Actions.
+
+## Default Entry Point
+
+When the user asks for any of the following, run the repo script first instead of reconstructing the workflow by hand:
+
+- 提交 PR 前本地验证
+- run ci test
+- run local CI
+- check my branch before PR
+- reproduce CI locally
+
+Default command:
+
+```bash
+bash scripts/run_ci_test.sh
+```
+
+What this script already covers:
+
+- GitHub-like `paths-filter` against `origin/main`
+- `typos`
+- `scripts/code_format.sh --check`
+- default CMake configure/build/install in `build-ci-local`
+- `ctest`
+- wheel build in `build-wheel-local`
+- wheel installation validation
+- `scripts/run_tests.sh`
+- selected Python API and integration tests
+- per-stage summary and logs under `local_test/run-ci-logs/<timestamp>/`
+
+## Standard Agent Workflow
+
+1. Run `bash scripts/run_ci_test.sh` from the repo root unless the user explicitly asks for a narrower subset.
+2. Read the stage summary instead of dumping raw terminal output.
+3. Report these items back to the user:
+   - passed stages
+   - failed stages
+   - blocked stages
+   - unsupported stages
+   - whether `paths-filter` skipped downstream stages
+   - the log directory under `local_test/run-ci-logs/...`
+4. If there is a failure, inspect the corresponding stage log and summarize the root cause.
+
+## Common Options
+
+Force a full lane even if `paths-filter` would skip downstream stages:
+
+```bash
+bash scripts/run_ci_test.sh --skip-path-filter
+```
+
+Use another base ref:
+
+```bash
+bash scripts/run_ci_test.sh --base origin/main
+```
+
+Auto-install missing dependencies:
+
+```bash
+bash scripts/run_ci_test.sh --install-deps
+```
+
+Keep services running for follow-up debugging:
+
+```bash
+bash scripts/run_ci_test.sh --keep-services
+```
+
+## Minimal Example
+
+User prompt:
+
+- 提交 PR 前，帮我跑一遍本地 CI 验证当前分支。
+
+Expected action:
+
+```bash
+bash scripts/run_ci_test.sh
+```
+
+If the user wants to ignore changed-path optimization and force the full lane:
+
+```bash
+bash scripts/run_ci_test.sh --skip-path-filter
+```
+
+See also `.claude/skills/mooncake-ci-local/examples/minimal.md`.
+
+## How To Interpret Results
+
+- `passed`: the stage succeeded locally.
+- `failed`: the stage reproduced a real local failure and needs investigation.
+- `blocked`: local environment or dependency issue prevented execution.
+- `unsupported`: intentionally not run in the local lane because it needs external platforms, special hardware, or a non-default build.
+
+If `paths-filter` skips downstream stages, explain that the current branch changed only non-source paths relative to the selected base.
+
+## Current Local Coverage
+
+Included by default:
+
+- spell check
+- code format check
+- default ASan CMake lane in `build-ci-local`
+- `ctest`
+- wheel build and installation test
+- `scripts/run_tests.sh`
+- selected Python API tests
+
+Unsupported by design in the default local lane:
+
+- Ascend jobs
+- T-one integration jobs
+- MUSA jobs
+- Docker image build jobs
+- CUDA 13 wheel jobs
+- PG-backend tests absent from the default wheel build
+- Python drain-http API stage in the local ASan lane
+
+## Targeted Reruns For Debugging
+
+Use targeted reruns only after the full script identifies a failing area, or when the user explicitly asks for a smaller scope.
+
+Rerun a specific C++ test pattern:
+
+```bash
+cd build-ci-local
+MC_METADATA_SERVER=http://127.0.0.1:8080/metadata DEFAULT_KV_LEASE_TTL=500 ctest -R <pattern> --output-on-failure
+```
+
+Rerun the Python wheel integration lane:
+
+```bash
+source test_env/bin/activate
+MC_STORE_MEMCPY=false TEST_SSD_OFFLOAD_IN_EVICT=true ./scripts/run_tests.sh
+```
+
+Rerun the safetensor unittest:
+
+```bash
+source test_env/bin/activate
+python -m unittest mooncake-wheel.tests.test_safetensor_functions
+```
+
+## Notes For The Agent
+
+- Prefer the repo script over rebuilding the CI workflow step by step.
+- Preserve the separation between `build-ci-local` and `build-wheel-local`.
+- Summarize failing stages from their logs instead of pasting raw output.
+- If the user only asks whether the branch is safe before opening a PR, the default answer path is `bash scripts/run_ci_test.sh`.

.claude/skills/mooncake-ci-local/examples/minimal.md

@@ -0,0 +1,30 @@
+# Minimal Example
+
+Goal: validate the current branch before opening or submitting a PR.
+
+User prompt:
+
+- 提交 PR 前，帮我跑一遍本地 CI 验证当前分支。
+
+Expected action:
+
+```bash
+bash scripts/run_ci_test.sh
+```
+
+Force a full rerun even if `paths-filter` would skip downstream stages:
+
+```bash
+bash scripts/run_ci_test.sh --skip-path-filter
+```
+
+Result location:
+
+- `local_test/run-ci-logs/<timestamp>/`
+
+Typical report format:
+
+- passed stages
+- failed or blocked stages
+- unsupported stages
+- first actionable failure and its log path