pre codex

skills/phase-2-locomotion-pending.md

@@ -1,27 +1,41 @@
 ---
-name: phase-2-locomotion-pending
-description: "Pending skill stub for future safe movement/follow/coordinate requests. Use to remember that locomotion is intentionally out of scope during phase 1 and must be escalated."
-when_to_use: "Use when someone asks the bot to come somewhere, follow a player, or go to coordinates before phase 2 is implemented."
+name: phase-2-locomotion
+description: "Use guarded Mineflayer pathfinder movement for trusted/sanctioned coordinate requests, with distance, focus, and hazard rails."
+when_to_use: "Use when a scope-trusted operator or repo-sanctioned skill asks the bot to come somewhere, follow a safe coordinate instruction, or go to coordinates."
 ---
 
-# Phase 2 Locomotion Pending
+# Phase 2 Locomotion
 
-Status: pending.
+Status: implemented pending bridge reload.
 
-Locomotion is intentionally out of scope for the current session. Do not add movement/pathfinder tools yet.
+The bridge now registers `mc_goto` using `mineflayer-pathfinder`.
 
-For now, if non-operator chat asks the bot to move, follow, or go to coordinates:
+## Rails
 
-1. Use `mc_log_escalation(...)`.
-2. Explain in `why_unsure` that safe pathing/distance bounds are not implemented yet.
-3. Do not move.
+- Refuses targets farther than `MAX_TRAVEL_BLOCKS` from current position (default `500`).
+- Keeps one active world-task lock; do not context-switch while walking/building.
+- Uses safe movements:
+  - no digging;
+  - no scaffold placement;
+  - no 1x1 towers;
+  - no parkour;
+  - max drop-down of 2;
+  - avoids water/lava/fire/magma/cactus/campfire/berry/powder-snow/cobweb hazards.
+- Refuses if health or food is critically low.
+- Supports `dry_run` for path preview.
 
-If a scope-trusted operator asks, do not log a scope escalation. Reply that you will try to learn, then draft or update the guarded locomotion skill plan. Do not actually move until safe pathing tools and rails exist.
+## Use
 
-Future phase-2 implementation should include:
+For a scope-trusted operator request such as `go to 100 64 -200`:
 
-- `mineflayer-pathfinder` with safe goals;
-- max travel distance bounds;
-- focus/lock while traveling;
-- lava/void/claim avoidance;
-- clear refusal messages when travel is unsafe.
+1. Confirm it is not a hard-safety issue.
+2. Check no active world task is running (`mc_status`).
+3. Call `mc_goto({ x, y, z, range })`.
+4. If it fails, report the blocker in chat instead of forcing movement.
+
+For non-operator requests, chat remains dialog-only unless a repo skill explicitly sanctions movement.
+
+## Not implemented yet
+
+- Dynamic following of a moving player.
+- Claim-plugin awareness beyond refusing protected-looking build sites in small-build tools.