switchroom 0.15.37 → 0.15.38

package/telegram-plugin/uat/scenarios/jtbd-memory-survives-restart-dm.test.ts

@@ -1,7 +1,7 @@
 /**
  * JTBD scenario — memory survives across restart (the "fleet differentiator").
  *
- * Serves: `reference/remember-across-sessions.md` — the JTBD says:
+ * Serves: `reference/jobs/remember-across-sessions.md` — the JTBD says:
  *
  *   *Outcome:* The agent brings back relevant facts, preferences,
  *   decisions, and open threads from past conversations, in the right

package/telegram-plugin/uat/scenarios/jtbd-rapid-followup-dm.test.ts

@@ -2,7 +2,7 @@
  * JTBD scenario — rapid follow-ups (steering vs queued classification).
  *
  * Live contract codified in `_shared/telegram-style.md.hbs` and
- * `reference/steer-or-queue-mid-flight.md` (default-flip commits
+ * `reference/jobs/steer-or-queue-mid-flight.md` (default-flip commits
  * `4fff90bf` + `597a58af`, 2026-04-17):
  *
  * - A mid-turn follow-up with NO prefix is `queued="true"` — new

package/telegram-plugin/uat/scenarios/jtbd-reflective-status-reaction-dm.test.ts

@@ -2,7 +2,7 @@
  * JTBD scenario — reflective status reaction (#1713).
  *
  * Serves the JTBD "know what my agent is actually doing" (see
- * `reference/know-what-my-agent-is-doing.md`). The status reaction on
+ * `reference/jobs/know-what-my-agent-is-doing.md`). The status reaction on
  * the user's inbound is the *primary* ambient liveness signal — the
  * user reads it as "what is the agent doing right now". When it
  * collapses straight to 👍 mid-turn, the signal evaporates and the

package/telegram-plugin/uat/scenarios/jtbd-wake-audit-content-dm.test.ts

@@ -1,7 +1,7 @@
 /**
  * JTBD scenario — wake-audit content visibility post-restart.
  *
- * Serves: `reference/restart-and-know-what-im-running.md` — the JTBD:
+ * Serves: `reference/jobs/restart-and-know-what-im-running.md` — the JTBD:
  *
  *   *Outcome:* After any restart, the user is told what config is live.
  *   Model, tools, skills, memory backend, auth state. **No need to ask.**