Fusion - the Fusion 360 Bridge

Automated daily verb run went red (2026-10-17, exit 1). Scorecard tail:

  bridge-lifecycle                       12 pass / 0 fail (15 manual, 0 skip)  green

45 PASS, 22 FAIL (80 manual-tier, 0 skipped) -> /home/adom/project/adom-desktop-fusion-bridge/tests/reports/verb-test-2026-10-17_1158.json
  FAIL: fusion_get_app_state - expected success, got error=Fusion is at the Autodesk sign-in screen (Signing in - Autodesk Fusion ), so the code=needs_signin
  FAIL: fusion_start - expected success, got error='fusion_start' did not respond within ab's 90s budget. code=timed_out
  FAIL: fusion_get_preferences - expected success, got error=Add-in request failed: http://127.0.0.1:8774/command: Connection Failed: Connect code=None; missing field 'current'
  FAIL: fusion_set_preference - expected success, got error=Fusion is at the Autodesk sign-in screen (Signing in - Autodesk Fusion ), so the code=None
  FAIL: fusion_assembly_bom - expected a BOM or the budget refusal, got error=Fusion is at the Autodesk sign-in screen (Signing in - Autod code=needs_signin
  FAIL: fusion_open_cloud_file - expected success, got error=Fusion is at the Autodesk sign-in screen (Signing in - Autodesk Fusion ), so the code=needs_signin
  FAIL: fusion_show_schematic - expected success, got error=Fusion is at the Autodesk sign-in screen (Signing in - Autodesk Fusion ), so the code=needs_signin
  FAIL: fusion_show_2d_board - expected success, got error=Fusion is at the Autodesk sign-in screen (Signing in - Autodesk Fusion ), so the code=needs_signin
  FAIL: fusion_board_info - expected success, got error=Fusion is at the Autodesk sign-in screen (Signing in - Autodesk Fusion ), so the code=needs_signin; missing field 'rawXml'
  FAIL: fusion_open_electronics - expected success, got error=Fusion is at the Autodesk sign-in screen (Signing in - Autodesk Fusion ), so the code=needs_signin; missing field 'isElectronics'
  FAIL: fusion_list_text_commands - expected success, got error=Fusion is at the Autodesk sign-in screen (Signing in - Autodesk Fusion ), so the code=needs_signin; missing field 'commands'
  FAIL: fusion_execute_text_command - expected success, got error=Fusion is at the Autodesk sign-in screen (Signing in - Autodesk Fusion ), so the code=needs_signin
  FAIL: fusion_show_3d_board - expected success, got error=Fusion is at the Autodesk sign-in screen (Signing in - Autodesk Fusion ), so the code=needs_signin
  FAIL: fusion_inspect_bodies - expected success, got error=Fusion is at the Autodesk sign-in screen (Signing in - Autodesk Fusion ), so the code=needs_signin; missing field 'bodies'; missing field 'units'
  FAIL: fusion_physical_properties - expected success, got error=Fusion is at the Autodesk sign-in screen (Signing in - Autodesk Fusion ), so the code=needs_signin
  FAIL: fusion_get_design_info - expected success, got error=Fusion is at the Autodesk sign-in screen (Signing in - Autodesk Fusion ), so the code=needs_signin
  FAIL: fusion_get_parameters - expected success, got error=Fusion is at the Autodesk sign-in screen (Signing in - Autodesk Fusion ), so the code=needs_signin
  FAIL: fusion_document_info - expected success, got error=Fusion is at the Autodesk sign-in screen (Signing in - Autodesk Fusion ), so the code=needs_signin
  FAIL: fusion_run_modeling_script#guard - expected errorCode=wrong_document got needs_signin (error=Fusion is at the Autodesk sign-in screen (Signing in - Autod)
  FAIL: fusion_assembly_bom#guard - expected errorCode=wrong_document got needs_signin (error=Fusion is at the Autodesk sign-in screen (Signing in - Autod)
  FAIL: fusion_run_modeling_script - expected success, got error=Fusion is at the Autodesk sign-in screen (Signing in - Autodesk Fusion ), so the code=needs_signin
  FAIL: fusion_addin_status - expected success, got error=The Adom add-in did not answer on port 8774. Fusion is running. code=addin_not_answering

Full log: tests/reports/daily-cron-2026-10-17.log on the dev container. Versions at run time are in the readiness line of the log. Triage per dev-skills/fusion-verb-tests: re-run the failing verbs with --only first, a startup race or relay flake re-passes; a repeat failure is the real finding.