Expand OutpostRunner routes and improve OutpostFighter recovery

[Wellwisher533]

Summary

• add 27 shared OutpostRunner route files across Cantha and Nightfall and update 6 existing Tyria routes
• use one mechanic-aware route executor for Outpost Runner v2 and Outpost Fighter, including extended portal crossings, blessings, dialogue sequences, and Junundu transitions
• keep Outpost Fighter in Normal Mode, stop automatic resign-on-wipe behavior, and resume from the nearest forward route waypoint after resurrection
• include the reliable interaction controller required by route mechanics

Route fixes included

• Beacon's Perch / Camp Rankor / Deldrimor War Camp / Granite Citadel / Copperhammer Mines portal extensions and route corrections
• Elona Reach to Seeker's Passage wall-avoidance correction
• Thunderhead Keep to Marhan's Grotto, Kodonur Crossroads to Rilohn Refuge, Echovald Forest, Jade Sea, Shing Jea, Desolation, Kourna, Realm of Torment, and Vabbi additions
• Basalt Grotto Wurm Spoor regrouping and safe natural Junundu dismount behavior

Verification

• 60 focused Outpost route and fighter recovery tests pass
• 47 focused reliable interaction tests pass
• 152 Python files in the affected runtime scope compile successfully
• git diff --check passes
• Pyright was unavailable in the local environment

Runtime status

Several corrected routes were validated during live gameplay while they were developed. The consolidated latest-upstream PR candidate has offline verification; broad end-to-end in-game validation of every added route is still pending.

[apoguita]

Verdict for the original request: Request changes — PR #115 adds library-owned movement and interaction behavior, but still bypasses library owners and leaves the new coordination path incomplete.

[BLOCKER] The reliable-interaction ownership guard is missing at runtime

Py4GWCoreLib/routines_src/reliable_interaction.py:386, :409, and :1437 import Py4GWCoreLib.routines_src.shared_command_coordination, but that module does not exist in the repository or in this PR. The broad exception handlers silently convert the missing owner into “no coordination.”

As a result, movement ownership and auxiliary-action deferral are not enforced by the library. The added tests hide this by injecting a fake coordination module into sys.modules, so they do not prove the real runtime wiring.

Required direction:

1. Add and integrate the actual coordination owner in Py4GWCoreLib, or route this behavior through the existing library coordination mechanism.
2. Do not silently disable a required control-plane feature when its owner cannot be imported.
3. Add a real import/runtime check proving that ownership is acquired, refreshed, released, and observed by the route boundary.

The current implementation is an optional no-op fallback, not a library-controlled action path.

[HIGH] The route helper bypasses the public movement owner

Sources/aC_Scripts/OutpostRunner/route_mechanics.py:91 calls the private coroutine bot.Move._coro_follow_path_and_exit_map(...).

This bypasses the public FollowPathAndExitMap(...) surface, including its yield-step registration, counters, and supported resume-key path. The route departure is therefore governed by a script reaching into a private implementation instead of by the library’s movement owner.

Required direction:

1. Replace the private call with the supported public movement API.
2. If the route boundary needs behavior not provided by that API, add that capability to Py4GWCoreLib and expose it through a supported public surface.
3. Verify that route departure preserves normal state registration, recovery, and resume behavior.

The current implementation is a script-side bypass of the movement control plane.

[HIGH] Reusable interaction ownership is duplicated in the script

Sources/aC_Scripts/OutpostRunner/route_mechanics.py:243-268 introduces _RouteInteractionRuntime, including its own HeroAI pause and restore state handling.

That duplicates behavior already owned by Py4GWCoreLib/botting_src/subclases_src/INTERACT_src.py and DIALOGS_src.py. The script now decides how shared automation state is paused and restored, creating a second interaction-control path outside the library owner.

Required direction:

1. Move the reusable runtime adapter and pause/restore ownership into the existing library interaction owner, or extend the new core interaction owner to use that existing mechanism.
2. Leave route_mechanics.py responsible only for route-specific data and postconditions.
3. Prove that interaction, movement cancellation, HeroAI pause state, and restoration behave consistently for other library consumers.

The current implementation places reusable library behavior in a script helper instead of integrating it into the owning library layer.

[HIGH] The new core module does not satisfy the required type contract

The strict Pyright check reports 23 errors in the newly added Py4GWCoreLib/routines_src/reliable_interaction.py, including unresolved imports, optional-value access, invalid argument types, a redeclaration, and a protocol signature mismatch.

Required direction:

1. Resolve all Pyright errors in the new library module.
2. Ensure the coordination import and protocol contracts match the actual library owners.
3. Re-run the strict changed-Python check before approval.

Scope note: the route data files and private bot orchestration are not findings by themselves. They matter here only where they introduce reusable behavior, bypass a library owner, or expose a library-contract failure.