Regression: upgrade reports success while configured Lab runner remains stale

[chubes4]

Problem

homeboy upgrade upgraded the controller from 0.299.0 to 0.299.2 and returned overall success, while the configured homeboy-lab runner remained on 0.299.0:

{
  "new_version": "0.299.0",
  "previous_version": "0.299.0",
  "success": true,
  "upgraded": false,
  "recovery_commands": [
    "homeboy runner exec homeboy-lab -- homeboy upgrade --no-restart",
    "homeboy upgrade --force --upgrade-runner homeboy-lab"
  ]
}

The next Lab workflow failed first with daemon lease is not fresh. Recovery required a separate manual command:

homeboy runner refresh-homeboy homeboy-lab --ref v0.299.2 --reconnect

This reproduces the user-facing contract previously tracked in #5563 after its fix.

Context: browser verification for Automattic/blocks-engine#659.

Expected behavior

One homeboy upgrade invocation converges the controller, configured runner binary, and active runner daemon to the selected release before reporting success.

When a runner cannot converge, the top-level command reports a partial/failed state and performs the safe generated recovery itself when possible. Structured output distinguishes controller success from fleet convergence.

Acceptance criteria

• homeboy upgrade upgrades each selected configured runner to the controller release.
• The active daemon is refreshed/reconnected before completion.
• Overall success is false or partial when a selected runner reports upgraded: false.
• Before/after controller, configured runner, and active daemon identities are concise and explicit.
• A deterministic regression test covers the exact success: true, upgraded: false child result.

AI assistance

• AI assistance: Yes
• Tool: OpenCode with OpenAI GPT-5.6 Sol
• Used for: Capturing live command evidence, correlating the regression with upgrade-runner reports success without upgrading configured Lab runner #5563, and drafting this issue.

[chubes4]

Additional convergence/DX evidence today:

• homeboy upgrade --check reported controller 0.301.2, latest 0.304.0.
• homeboy upgrade --force --upgrade-runner homeboy-lab returned top-level success with summary Selected runners refreshed without promoting the initiating controller; both controller and runner remained 0.301.2, and the child reported upgraded: false.
• Reaching actual convergence required two separate commands: homeboy upgrade --force --skip-runners, then homeboy runner refresh-homeboy homeboy-lab --ref v0.304.0 --reconnect.

The targeted runner behavior is technically reflected in help, but the recovery guidance had prescribed the targeted form after a stale-daemon failure, and its successful envelope looked like convergence despite leaving the initiating controller stale. The command should render explicit partial scope and the exact next convergence command prominently, or provide one controller-plus-selected-runner operation.