feat(runtime): survival-bot pivot — MC chat is dialog-only (Phase 0) (#12)

Phase 0 of plans/autonomous-survival-bot-prd.md: change the product
direction from operator-driven remote control to autonomous survival
resident. MC chat is dialog-only for everyone, including
OPERATOR_USERNAMES — commands like come/follow/build/pause/stop are
recorded in the diary but not dispatched. TUI remains the only local
control plane.

Runtime changes:
- Remove operatorGoalReflex from reflex.js (the come-here chat command).
- Replace handleOperatorChat in bot.js with a dialog-only handleChat
  that answers greetings/status questions and records command-like
  verbs (en+ru) without dispatching them.
- Default MC_VERSION to "auto" in runtime/config.js; mineflayer
  receives `false` to trigger version auto-detection.
- Update auto-escalation prompt's reflex chain summary.

Docs:
- AGENTS.md: product pivot notice up top; chat-driven scope-trust is
  flagged as legacy/Pi-only.
- README.md / docs/runtime.md: replace operator-chat command list with
  dialog-only description; update reflex chain summary.
- docs/roadmap.md: Phase 2/3 marked superseded by the PRD where they
  assumed chat-driven control.

Co-authored-by: Yuriy Mayatnikov <mayatnikov@me.com>
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

AGENTS.md

@@ -5,10 +5,24 @@
 > the hybrid one under [`runtime/`](./runtime/) — a script-driven reflex loop
 > with Pi invoked only on demand. See [`docs/runtime.md`](./docs/runtime.md)
 > for the new architecture. The principles below still apply to both modes:
-> tool catalog, safety rules, operator-trust model, and memory protocol are
-> shared. When you (the agent, in Pi-only mode) propose new code, prefer
-> writing it as a reflex/action in `runtime/` over an extension in
-> `extensions/` — the hybrid runtime is where new work lands going forward.
+> tool catalog, safety rules, and memory protocol are shared. When you (the
+> agent, in Pi-only mode) propose new code, prefer writing it as a
+> reflex/action in `runtime/` over an extension in `extensions/` — the
+> hybrid runtime is where new work lands going forward.
+
+> **Product pivot (2026-05-25, Phase 0).** The bot is no longer a remote
+> control for operators or players. It is becoming a self-sufficient survival
+> resident of the configured Minecraft server. **Minecraft chat is
+> dialog-only.** Nobody — including names listed in `OPERATOR_USERNAMES` —
+> can drive the bot via chat: `come`, `follow`, `pause`, `stop`, `build`,
+> `give` and similar verbs are recorded but not dispatched. The TUI (or any
+> future Telegram bridge) is the only local control plane for actions; the
+> repo (file edits, skills, runtime code, proposals) is the trusted
+> long-term control channel. The full plan lives in
+> `plans/autonomous-survival-bot-prd.md` (local-only, gitignored). Sections
+> below that still describe chat-driven scope-trust apply only to the
+> Pi-only runtime's legacy behaviour — treat them as historical context, not
+> as a description of current behaviour.
 
 You are **pepa-pi-bot**: a universal, autonomous Minecraft player living inside the [Pi](https://pi.dev) runtime.