fix: treat HTTP 202 Accepted as valid response (#75)

## Summary

- Fix `server action rename` incorrectly treating HTTP 202 response as
an error
- Add HTTP 202 to list of acceptable "no content" status codes alongside
204
   - Add test case for HTTP 202 Accepted response handling

Author: nats

src/binarylane/console/runners/command.py

@@ -108,9 +108,9 @@ def response(self, status_code: int, received: Any) -> None:
         if status_code == 401:
             self.error(ExitCode.TOKEN, 'Unable to authenticate with API - please run "bl configure" to get started.')
 
-        # If no response is available, report an API error (unless it is `204 No Content`)
+        # If no response is available, report an API error (unless it is `202 Accepted` or `204 No Content`)
         if received is None:
-            if status_code != 204:
+            if status_code not in (202, 204):
                 self.error(ExitCode.API, f"HTTP {status_code}")
             return
 

tests/runners/test_command_runner.py

@@ -100,6 +100,16 @@ def test_response_handles_nocontent(capsys: CaptureFixture[str]) -> None:
     assert captured.err == "" and captured.out == ""
 
 
+def test_response_handles_accepted(capsys: CaptureFixture[str]) -> None:
+    """HTTP 202 Accepted with no body should not be treated as an error."""
+    runner = TypeRunner(CommandRunner)
+
+    runner.test.response(202, None)
+
+    captured = capsys.readouterr()
+    assert captured.err == "" and captured.out == ""
+
+
 def test_response_handles_ok(capsys: CaptureFixture[str]) -> None:
     runner = TypeRunner(CommandRunner)