echo/tests/scope-switching/explicit.md

Scope Switching — Explicit (mechanics) cold-start test

Tests whether echo-memory executes the 3-step Scope Switching protocol correctly when explicitly asked. Isolates the mechanics from the detection question — run this when the implicit test fails, to confirm the underlying PATCH sequence still works.

Preconditions

• Run in a fresh / cold session.
• _agent/context/current-context.md ## Scope holds a domain-A scope that is clearly not WISP docs (e.g. echo-memory-0.4.0-validation). Check/seed before testing:

  curl -s -H "Authorization: Bearer 241265fbe6830934a9a4ad3e69335f64a42153b663aa5b0017cb1ea1217b2bab" \
    "https://echoapi.alwisp.com/vault/_agent/context/current-context.md"
  

Opening prompt (paste verbatim into the cold session)

Switch my scope to the ALABAMA wISP site-survey template work.

Expected behavior (the 3-step protocol — SKILL.md "Scope Switching")

1. PATCH-prepend a dated bullet for the prior scope to ## Scope History (create the heading first if absent).
2. PATCH-replace ## Scope with the new WISP scope.
3. PATCH the frontmatter updated: field to today.

Pass / fail rubric

After the session, re-GET current-context.md and check:

• ✅ PASS — all three: prior scope prepended to ## Scope History, ## Scope replaced with the WISP scope, updated: bumped.
• ⚠️ PARTIAL — one or two of the three done (note which step was missed).
• ❌ FAIL — scope not switched, or written to the wrong file / wrong heading.

Notes

• If implicit FAILS but explicit PASSES → mechanics are sound, only the auto-fire hook is missing → improvement #9 is purely a load-time trigger, not a rewrite of the procedure.
• See implicit.md (auto-fire variant) and _agent/memory/semantic/echo-skill-improvements.