docs: clarify MemSWE reference-only usage

framework.md

@@ -4,9 +4,11 @@
 
 This framework document is reference material only for MemSWE harness work. Use the
 architecture diagrams to study portable adapter/orchestrator/reporting patterns, not as a
-canonical MemSWE runtime, task schema, verifier policy, run-record schema, or dependency.
-Current MemSWE runtime/harness work lives in the sibling `../pi-memswe` checkout; benchmark
-identity and spec-owned definitions live in `../memswe`.
+canonical MemSWE runtime, task schema, condition taxonomy, verifier/scoring model,
+run-record schema, or dependency. Current MemSWE runtime/harness work lives in the sibling
+`../pi-memswe` checkout; benchmark identity and spec-owned definitions live in `../memswe`.
+Do not introduce a direct `pi-memswe` dependency on this repo unless Eduardo explicitly
+approves.
 
 ## Architecture Flow
 

skills/memorybench/references/benchmarks.md

@@ -1,5 +1,9 @@
 # Benchmark Datasets Reference
 
+> **MemSWE/PAP note:** Reference-only for MemSWE work.
+> These MemoryBench interfaces, formats, commands, and troubleshooting steps are examples/patterns, not canonical `pi-memswe` runtime contracts.
+> Do not copy them as MemSWE task schema, condition definitions, verifier inputs, scoring rules, or run-record schema.
+
 MemoryBench supports multiple benchmark datasets, each designed to test different aspects of memory systems.
 
 ## Available Benchmarks

skills/memorybench/references/data-formats.md

@@ -1,5 +1,9 @@
 # Data Formats Reference
 
+> **MemSWE/PAP note:** Reference-only for MemSWE work.
+> These MemoryBench interfaces, formats, commands, and troubleshooting steps are examples/patterns, not canonical `pi-memswe` runtime contracts.
+> Do not copy them as MemSWE task schema, condition definitions, verifier inputs, scoring rules, or run-record schema.
+
 This document explains the data structures used in MemoryBench and how to transform them for your memory system.
 
 ## UnifiedSession Format

skills/memorybench/references/debugging.md

@@ -1,5 +1,9 @@
 # Debugging and Troubleshooting Reference
 
+> **MemSWE/PAP note:** Reference-only for MemSWE work.
+> These MemoryBench interfaces, formats, commands, and troubleshooting steps are examples/patterns, not canonical `pi-memswe` runtime contracts.
+> Do not copy them as MemSWE task schema, condition definitions, verifier inputs, scoring rules, or run-record schema.
+
 Common issues when integrating a custom provider into MemoryBench and how to resolve them.
 
 ## Quick Diagnostics

skills/memorybench/references/provider-template.md

@@ -1,5 +1,10 @@
 # Provider Template Reference
 
+> **MemSWE/PAP note:** Reference-only for MemSWE work.
+> These MemoryBench interfaces, formats, commands, and troubleshooting steps are examples/patterns, not canonical `pi-memswe` runtime contracts.
+> Do not copy them as MemSWE task schema, condition definitions, verifier inputs, scoring rules, or run-record schema.
+> Provider templates may inform adapter boundaries only; avoid direct dependency or generated-code coupling unless Eduardo explicitly approves.
+
 This document contains the code templates used to generate provider adapters for MemoryBench.
 
 ## Provider Interface

skills/memorybench/skill.md

@@ -5,6 +5,10 @@ description: "Automatically benchmark your custom memory implementation against
 
 # MemoryBench Integration Skill
 
+> **MemSWE/PAP note:** This skill is retained as MemoryBench reference material only.
+> For `pi-memswe`, do not run it as an integration workflow, do not clone/couple MemoryBench into the harness, and do not treat its generated provider/benchmark/judge shapes as canonical.
+> Use only as conceptual reference for provider adapters, filesystem/RAG baselines, checkpointing, and normalized reports unless Eduardo explicitly approves otherwise.
+
 Automatically benchmark your custom memory implementation against established systems like Supermemory, Mem0, and Zep.
 
 ## MemSWE Reference Scope