kane-cli run "<objective>" --agent fails with "AP stuck — step file not found" (inline objective not used for authoring)

[komal-lt]

Summary

kane-cli run "<objective>" --agent --headless fails immediately after the first navigation with reason: "AP determined agent is stuck — no viable actions remain" / reason_code: stuck.ap_stuck. The run_end summary says the goal "wasn't provided" and that "the next recorded steps (Steps 2 and 3) could not be loaded ('step file not found')" — i.e. it looked for recorded step files instead of authoring from the inline objective.

Severity

S2

kane-cli version

0.4.0

Repro

kane-cli run "Open https://test-manager.lambdatest.com, log in with {{KANE_TEST_USER}}/{{KANE_TEST_PASSWORD}}, verify the dashboard loads; fail if still on login." \
  --env prod --agent --headless --max-steps 20 --timeout 300

Actual

exit 1; run_end status:failed, reason_code: stuck.ap_stuck; summary: "goal wasn't provided … step file not found". Only the initial navigate happened. (A TMS report URL was still generated.)

Expected

Inline run "<objective>" should author from the provided objective in --agent mode, not require pre-recorded step files.