claude respawn reports a bad job name before checking the background service

claude respawn <prefix> restarts a background job that you pick by the first few letters of its name. Claude Code now checks those letters before it tries to reach the background service that runs jobs. If no job matches, or more than one does, you now see "No job matching" or "Ambiguous prefix", even when the background service is unavailable. Before, the unavailable-service error came first and hid the problem with the prefix. Running it with --all works as before.