feat(tui): quota sidebar with Profile and Quota sections

.github/workflows/compliance-close.yml

@@ -9,13 +9,17 @@ on:
 permissions:
   contents: read
   issues: write
-  pull-requests: write
 
 jobs:
+  # Issues only: the PR half of this mechanism (pr-standards.yml's check-compliance
+  # job, the only thing that ever applied needs:compliance to a pull request) was
+  # removed as part of dropping the upstream community-PR-governance workflows this
+  # fork doesn't use (see .github/workflows/pr-standards.yml's removal). The only
+  # remaining producer of this label, duplicate-issues.yml, labels issues only.
   close-non-compliant:
     runs-on: ubuntu-latest
     steps:
-      - name: Close non-compliant issues and PRs after 2 hours
+      - name: Close non-compliant issues after 2 hours
         uses: actions/github-script@f28e40c7f34bde8b3046d885e986cb6290c5673b # v7.1.0
         with:
           script: |
@@ -27,18 +31,16 @@ jobs:
               per_page: 100,
             });
 
-            if (items.length === 0) {
-              core.info('No open issues/PRs with needs:compliance label');
+            const issues = items.filter((item) => !item.pull_request);
+            if (issues.length === 0) {
+              core.info('No open issues with needs:compliance label');
               return;
             }
 
             const now = Date.now();
             const twoHours = 2 * 60 * 60 * 1000;
 
-            for (const item of items) {
-              const isPR = !!item.pull_request;
-              const kind = isPR ? 'PR' : 'issue';
-
+            for (const item of issues) {
               const { data: comments } = await github.rest.issues.listComments({
                 owner: context.repo.owner,
                 repo: context.repo.repo,
@@ -50,13 +52,11 @@ jobs:
 
               const commentAge = now - new Date(complianceComment.created_at).getTime();
               if (commentAge < twoHours) {
-                core.info(`${kind} #${item.number} still within 2-hour window (${Math.round(commentAge / 60000)}m elapsed)`);
+                core.info(`Issue #${item.number} still within 2-hour window (${Math.round(commentAge / 60000)}m elapsed)`);
                 continue;
               }
 
-              const closeMessage = isPR
-                ? 'This pull request has been automatically closed because it was not updated to meet our [contributing guidelines](../blob/dev/CONTRIBUTING.md) within the 2-hour window.\n\nFeel free to open a new pull request that follows our guidelines.'
-                : 'This issue has been automatically closed because it was not updated to meet our [contributing guidelines](../blob/dev/CONTRIBUTING.md) within the 2-hour window.\n\nFeel free to open a new issue that follows our issue templates.';
+              const closeMessage = 'This issue has been automatically closed because it was not updated to meet our [contributing guidelines](../blob/main/CONTRIBUTING.md) within the 2-hour window.\n\nFeel free to open a new issue that follows our issue templates.';
 
               await github.rest.issues.createComment({
                 owner: context.repo.owner,
@@ -74,22 +74,13 @@ jobs:
                 });
               } catch (e) {}
 
-              if (isPR) {
-                await github.rest.pulls.update({
-                  owner: context.repo.owner,
-                  repo: context.repo.repo,
-                  pull_number: item.number,
-                  state: 'closed',
-                });
-              } else {
-                await github.rest.issues.update({
-                  owner: context.repo.owner,
-                  repo: context.repo.repo,
-                  issue_number: item.number,
-                  state: 'closed',
-                  state_reason: 'not_planned',
-                });
-              }
+              await github.rest.issues.update({
+                owner: context.repo.owner,
+                repo: context.repo.repo,
+                issue_number: item.number,
+                state: 'closed',
+                state_reason: 'not_planned',
+              });
 
-              core.info(`Closed non-compliant ${kind} #${item.number} after 2-hour window`);
+              core.info(`Closed non-compliant issue #${item.number} after 2-hour window`);
             }

.github/workflows/cz-test.yml

@@ -0,0 +1,77 @@
+name: cz-test
+
+# Runs cz-cli's OWN unit tests and typecheck. Distinct from `test.yml`, which
+# only covers upstream opencode packages (turbo.json's `test` task names
+# opencode/@opencode-ai/{core,app,ui,session-ui} exclusively — cz-cli,
+# clickzetta-sdk and clickzetta-ai-gateway are not in that list and are never
+# exercised there) and which is stuck queued forever on this fork because
+# `blacksmith-*` runners were never provisioned for clickzetta/cz-cli. This
+# workflow uses GitHub-hosted runners so it actually executes.
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+  workflow_dispatch:
+
+concurrency:
+  group: ${{ github.workflow }}-${{ github.event.pull_request.number || github.ref }}
+  cancel-in-progress: true
+
+permissions:
+  contents: read
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5 # v4.3.1
+
+      - name: Setup Bun
+        uses: ./.github/actions/setup-bun
+
+      - name: Typecheck cz-cli
+        working-directory: packages/cz-cli
+        run: bun run typecheck
+
+      - name: Run cz-cli unit tests
+        working-directory: packages/cz-cli
+        # test script runs with --isolate: several suites (e.g.
+        # analytics-agent-session-commands.test.ts) mock.module() their own src,
+        # which bun's default shared-process test run leaks across files sharing
+        # that process — a later network-boundary suite (task-condition-flow,
+        # task-merge) that expects the REAL module then reads this file's fixture
+        # data instead. --isolate gives each file its own global object so a
+        # leaked mock cannot reach another file at all.
+        #
+        # analytics-agent-session-commands.test.ts ALSO restores its mocks in its
+        # own afterAll (see the comment there). That is not redundant with
+        # --isolate: it fixes the one suite that leaked, while --isolate is the
+        # unconditional guarantee for every suite that has not been fixed the same
+        # way, or will not remember to be. Keep both — the per-file fix is cheap
+        # insurance against exactly this suite regressing if --isolate is ever
+        # removed for its cost (a fresh global per file is slower, and it can also
+        # hide a REAL cross-file coupling that would still bite in the shipped
+        # binary, where every test file's module cache is shared).
+        #
+        # Intent, confirmed: --isolate is the PRIMARY guarantee for the whole
+        # suite (every file, not just the one known leaker), accepted as a
+        # change to the shared local/CI test contract, not a CI-only knob. The
+        # afterAll restore and the two test-only resets added alongside it
+        # (clearUnservedHostForTest, clearUserNameCacheForTest in
+        # tui-quota-data.ts) are deliberately kept as belt-and-suspenders on top
+        # of it, per the reasoning above and in each of those call sites.
+        run: bun run test
+
+      # UPSTREAM-PATCHES.md's re-baseline checklist points at these three files
+      # as the enforcement for their respective ledger entries (7, 9), but they
+      # live inside upstream packages and are only named by test.yml's
+      # @opencode-ai/core#test / opencode#test turbo tasks — the workflow stuck
+      # queued forever on unprovisioned blacksmith-* runners. Run them directly
+      # here so the ledger's claim is actually backed by a green check on this
+      # fork, without pulling every upstream package's suite into this workflow.
+      - name: Run cz-owned tests inside upstream packages
+        run: |
+          (cd packages/core && bun test test/model-selection.test.ts)
+          (cd packages/opencode && bun test test/provider/clickzetta-discovery.test.ts test/provider/clickzetta-context-limit.test.ts)