Let Rambler walk to and use named nearby switches

[benceruleanlu]

Problem

Rambler can only use a world switch when the player is already pointing at it and the switch is immediately reachable. That prevents natural requests such as "press the red-light button" or "turn on the lamp" from working at ordinary conversational distance.

Acceptance criteria

• Bounded turn context exposes only active, companion-usable nearby primary interactions with exact stable IDs and natural game-object names.
• The model can select a uniquely named nearby switch without direct gaze; current gaze remains an exact fallback.
• Rambler walks to the same frozen switch, visibly aligns, and revalidates component identity, companion conditions, reach, blockers, and host authority immediately before acting.
• Navigation does not delete a safe route or commit a recovery jump across unsupported ground.
• The authoritative switch state changes and is confirmed on the same tracked object.
• No nearest-object fallback, client command, or silent retargeting is introduced.
• Runtime logs expose discovery, exact target resolution, approach, authority request, and confirmation.

Implementation is in progress on bl/follow-route-shortcuts; visual QA of the Level 1 red-light control remains required.

[benceruleanlu]

Implemented and merged to main in 39ae267. The deployed 0.13.0 artifact is SHA-256 16122C41C404B9476410A3F2377B9DF59ACC5C38BCF816B8DF77C1B7743C44E8. Startup on Big Walk 1.4.10 build 2608201131 is clean; exact nearby-switch discovery, grounded approach, authority activation, and same-state confirmation are pending consolidated in-game QA.

[benceruleanlu]

0.13.0's first deployed spoken turn ended in a native CoreCLR access violation. Because the deleted minidump prevents attribution to one exact wrapper, commit c7bbc01 fail-closes all newly added speech-time interaction surfaces in 0.13.1: ambient CastableTarget scanning is removed, utterance-boundary peck candidate capture is disabled, and interact_with_object is not exposed to the model.

The exact-target interaction implementation remains dormant in source for isolated reintroduction after ordinary spoken-turn stability is proven. This issue remains open; named nearby switch use is intentionally unavailable in 0.13.1 rather than risking another whole-process crash.

[benceruleanlu]

2026-08-23 handoff update: the blocker is broader than carried/crane interaction.

Latest Level 1 start-area reproduction used an ordinary nearby button with no carrying involved. The human and companion were within arm's reach, the human looked directly at the button, and the human could press it manually.

Exact trace:

• WORLD_REFERENCE_CAPTURED for castable instance 1216508
• Human-reference structural scan: outcomes=1, constructible=1
• Frozen exact switch: switch:local:1251484
• Context resolution selected the same exact switch
• interact_with_object failed immediately with diagnosticError=interaction_conditions_changed
• No interaction job, approach, native authority dispatch, or receipt occurred

This disproves the previous carry-only diagnosis and does not establish a raycast failure. The likely first seam to inspect is actor-dependent CastableTarget.GetCastableOutcome rematerialization after successful structural capture.

Accumulated work is preserved as draft stack #52:

1. Generalize companion action and interaction runtime #49 — runtime architecture (base main)
2. Add deterministic action protocol verification #50 — deterministic protocol verification (base Generalize companion action and interaction runtime #49; 23/23 checks pass)
3. Document the unresolved interaction handoff #51 — exact handoff, documentation, and the deployed 0.17.0 artifact (base Add deterministic action protocol verification #50)

Do not mark this issue fixed until an ordinary nearby button reaches native authority, confirms the exact switch receipt, and passes in-game QA.

[benceruleanlu]

Fixed by f4a59c1, which removed the actor-filtered outcome revalidation; commit records two runtime-confirmed switch interactions. Closing as part of the roadmap reset.