CodeRabbit Generated Unit Tests: Add unit tests for PR changes

[coderabbitai]

Unit test generation was requested by @four-bytes-robby.

• fix: reset _busPromise on publish failure to allow reconnect #146 (comment)

The following files were modified:

• test/status.test.ts

---

Summary by cubic

Adds test/status.test.ts to validate bus reconnection behavior in status updates. The tests confirm _busPromise resets on publish failure, reconnects only when needed, handles session-scoped writes, keeps in-memory state updated even on failure, and safely handles publish-then-connect failures.

^{Written for commit 35f0e45. Summary will update on new commits.}

[coderabbitai]

Important

Review skipped

This PR was authored by the user configured for CodeRabbit reviews. CodeRabbit does not review PRs authored by this user. It's recommended to use a dedicated user account to post CodeRabbit review feedback.

Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 3ba96ff6-321c-4f34-829a-86657626961f

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[four-bytes-robby]

Validation: closing as not planned

CI: 2 test failures — mock.module("@four-bytes/opencode-plugin-lib") is not being hoisted correctly in CI, causing BusClient.connect() to never be called.

Line	Test	Expected	Got
232	does NOT re-connect after a successful publish	1	0
137	re-connects on every repeated publish failure	3	2

Root cause: The mock doesn't intercept the real module import in CI's Bun version. The underlying behavior (#146 — _busPromise reset) is already merged to main and working.

Closing as not planned. Tests would need a different mock strategy to be CI-reliable.

[four-bytes-robby]

Closing as not planned — tests fail due to mock.module() hoisting issue in CI (2/6 tests fail). Underlying fix #146 already merged. See validation comment for details.