[P0][M] `autorio`：對齊已暴露 operations 與已實作 task states / autorio: align exposed operations with implemented task states

[VladChang]

中文標題

autorio：對齊已暴露 operations 與已實作 task states

English Title

autorio: align exposed operations with implemented task states

Metadata

• Priority: P0
• Size: M
• Repo labels: enhancement, help wanted
• Suggested labels: priority:P0, size:M, area:autorio

Summary

autorio currently exposes operations that are not fully backed by the runtime state machine.

Problem

attack_nearest_enemy is exposed through remote.add_interface, but there is no corresponding attack execution loop in on_tick.

research_technology starts research immediately, but it is not consistently tracked through the same task lifecycle as other queued operations.

This makes the agent believe some actions are available and observable when they are not.

Proposed Change

Audit every exposed operation in autorio_operations and ensure each one is either:

• fully implemented in the task queue and tick loop
• explicitly removed from the public interface until implemented

Acceptance Criteria

• Every exposed operation can be executed end-to-end from the agent side.
• No operation can be queued without a matching runtime handler.
• Task completion and failure behavior is consistent across all operations.

References

• https://github.com/moeru-ai/airi-factorio/blob/main/packages/autorio/src/control.ts
• https://github.com/moeru-ai/airi-factorio/blob/main/packages/autorio/src/task_manager.ts
• https://github.com/moeru-ai/airi-factorio/blob/main/packages/autorio/src/types.ts

[NJX-njx]

Hi, I'd like to work on this issue. I've identified the gaps:

1. attack_nearest_enemy: Creates a task with TaskStates.ATTACKING but the on_tick handler has no branch for it — task gets stuck. I'll implement a full state_attacking function using existing utilities (get_nearest_entity, get_direction, find_entities_filtered).

2. research_technology: Calls force.add_research() directly without task_manager.add_task(), bypassing the task lifecycle. The existing state_researching handler is unreachable. I'll refactor it to follow the same pattern as other operations. Also fixing a return value bug on line 255 ([true, 'Cannot start...'] should be [false, ...]).

Will submit a PR shortly.