[Zorato]

Problem

Usage state and polling currently belong to Panel. When the host unmounts and remounts the panel, usage state resets to loading and a new refresh starts.

The existing refresh deadline does not prevent this reset.

Changes

• Move usage state, polling, and the countdown clock into plugin setup.
• Let Panel render shared state through accessors.
• Preserve in-flight refresh cycles across panel remounts.
• Retain the existing deadline, overlap protection, and error handling.
• Clear intervals, suppress late results, and unregister the slot during plugin cleanup.
• Extract refresh logic into a small module for focused tests.

This PR does not change credential resolution, sidebar layout, or pace indicators.

Behavior change

Polling now follows the plugin lifetime rather than the panel lifetime. It continues while the plugin is active, even when the panel is not mounted.

The deadline still ends the wait without cancelling the underlying load.

Verification

• npm test: 15 tests pass.
• npm run typecheck: passes for production sources.
• Four lifecycle tests exercise the actual plugin setup and slot callback with a fake host and the real OpenTUI renderer.
• All four lifecycle tests fail against the upstream implementation.
• Tests cover state retention, in-flight refresh retention, countdown updates, and cleanup.
• Eleven refresh tests cover deadlines, overlap protection, errors, and disposal.

Tests use synthetic responses, not live credentials or API requests. This reproduction demonstrates panel-remount behavior; it does not establish the cause of every reported loading issue.

[PentSec]

Approved. Moving state and polling into setup is the right call, and the lifecycle tests against the real renderer are convincing: they fail on upstream and pass here. Definition.setup returning a Cleanup is part of the public contract, so the design holds.

Two small notes, no changes required here:

• withDeadline uses undefined as the timeout sentinel, so a load that legitimately resolves undefined reads as a timeout. fetchUsage never does, but the module is generic and exported.
• The tests import type { Context } from "@opencode/plugin/tui", which is not exported (only Plugin.Context or the /tui/plugin subpath). It is erased at runtime, but it will fail once tests are typechecked.

We will wire a bun test job into CI on our side.