agentbridge-cli 0.1.13__tar.gz → 0.1.14__tar.gz

{agentbridge_cli-0.1.13 → agentbridge_cli-0.1.14}/.codex/skills/build-release/SKILL.md

@@ -9,7 +9,7 @@ Use the repository-owned GitHub Actions workflow and PyPI Trusted Publishing.
 Do not create a local tag or upload with local credentials: pushing a new
 `pyproject.toml` version to `main` triggers `.github/workflows/release.yml`,
 which tests, scans, builds, creates `v<version>`, creates the GitHub Release,
-publishes `agentbridge-cli`, and attaches ad-hoc-signed arm64 and x86_64 DMGs.
+publishes `agentbridge-cli`, and attaches an ad-hoc-signed arm64 DMG.
 
 Use the next unused patch version unless the user requests another valid,
 unused semantic version. Treat an untagged version absent from PyPI as pending.
@@ -54,8 +54,8 @@ The preflight requires macOS. It checks consistent project and lock metadata, an
 unused PyPI version and tag, clean patch formatting, a frozen lock, Python 3.12
 and 3.13 tests, Ruff, Swift tests, a self-contained app/DMG build for the current
 Mac architecture, app signature and embedded-runtime smoke tests, wheel and
-sdist audits, and a wheel installation smoke test. CI builds both macOS
-architectures with ad-hoc signatures. Stop at the exact failed gate.
+sdist audits, and a wheel installation smoke test. CI builds the arm64 macOS
+artifact with an ad-hoc signature. Stop at the exact failed gate.
 
 4. Review and publish the release commit:
 
@@ -92,9 +92,7 @@ python3 .codex/skills/build-release/scripts/release_build.py wait-pypi --version
 gh release view v<version> --json url,tagName,assets
 ```
 
-Require both
-`AgentBridge-<version>-macos-arm64.dmg` and
-`AgentBridge-<version>-macos-x86_64.dmg` plus their `.sha256` files in the
+Require `AgentBridge-<version>-macos-arm64.dmg` and its `.sha256` file in the
 release assets. Do not report success until PyPI returns exact-version files and
 all required GitHub assets exist. If the workflow fails, inspect
 `gh run view <run-id> --log-failed` and report the failed gate before considering

{agentbridge_cli-0.1.13 → agentbridge_cli-0.1.14}/.codex/skills/build-release/scripts/release_build.py

@@ -313,8 +313,10 @@ def preflight_macos_app(version: str) -> dict[str, object]:
         raise SystemExit("the AgentBridge release preflight requires macOS for app validation")
 
     architecture = platform.machine()
-    if architecture not in {"arm64", "x86_64"}:
-        raise SystemExit(f"unsupported macOS release architecture: {architecture}")
+    if architecture != "arm64":
+        raise SystemExit(
+            f"unsupported macOS release architecture: {architecture}; AgentBridge requires arm64"
+        )
 
     run(["swift", "test", "--package-path", "macos"])
     run(["scripts/build_macos_app.sh"])

{agentbridge_cli-0.1.13 → agentbridge_cli-0.1.14}/.github/workflows/release.yml

@@ -214,8 +214,6 @@ jobs:
         include:
           - runner: macos-15
             architecture: arm64
-          - runner: macos-15-intel
-            architecture: x86_64
     runs-on: ${{ matrix.runner }}
     timeout-minutes: 30
     permissions:

{agentbridge_cli-0.1.13 → agentbridge_cli-0.1.14}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: agentbridge-cli
-Version: 0.1.13
+Version: 0.1.14
 Summary: Bridge OpenAI tools to Claude Code SDK, Codex CLI, and OpenRouter
 Project-URL: Homepage, https://github.com/tsilva/agentbridge
 Project-URL: Repository, https://github.com/tsilva/agentbridge
@@ -46,10 +46,10 @@ It supports streaming and non-streaming responses, image and PDF inputs where th
 
 ### macOS menu-bar app
 
-Download the DMG for your Mac architecture from the GitHub Release, drag
+On an Apple silicon Mac, download the arm64 DMG from the GitHub Release, drag
 `AgentBridge.app` to Applications, and open it. The app is ad-hoc signed rather
 than Apple-notarized, so on first launch macOS may require you to Control-click
-the app, choose **Open**, and confirm.
+the app, choose **Open**, and confirm. Intel Macs are not supported.
 
 You can also build the app locally on macOS 13 or later. This requires
 [uv](https://docs.astral.sh/uv/) and the Xcode Command Line Tools, but not an
@@ -185,8 +185,8 @@ Releases use the `Release` GitHub Actions workflow and PyPI Trusted Publishing
 for the `agentbridge-cli` project. The publisher is scoped to owner `tsilva`,
 repository `agentbridge`, workflow `release.yml`, and environment `pypi`; no
 PyPI API token is required. GitHub Releases contain the Python distributions
-plus ad-hoc-signed arm64 and x86_64 macOS DMGs and SHA-256 checksums. These DMGs
-are not Apple-notarized and require no Apple Developer credentials. Releases
+plus an ad-hoc-signed arm64 macOS DMG and SHA-256 checksum. The DMG is not
+Apple-notarized and requires no Apple Developer credentials. Releases
 through `0.1.10` remain available under the previous `agentbridge-py`
 distribution name.
 

{agentbridge_cli-0.1.13 → agentbridge_cli-0.1.14}/README.md

@@ -14,10 +14,10 @@ It supports streaming and non-streaming responses, image and PDF inputs where th
 
 ### macOS menu-bar app
 
-Download the DMG for your Mac architecture from the GitHub Release, drag
+On an Apple silicon Mac, download the arm64 DMG from the GitHub Release, drag
 `AgentBridge.app` to Applications, and open it. The app is ad-hoc signed rather
 than Apple-notarized, so on first launch macOS may require you to Control-click
-the app, choose **Open**, and confirm.
+the app, choose **Open**, and confirm. Intel Macs are not supported.
 
 You can also build the app locally on macOS 13 or later. This requires
 [uv](https://docs.astral.sh/uv/) and the Xcode Command Line Tools, but not an
@@ -153,8 +153,8 @@ Releases use the `Release` GitHub Actions workflow and PyPI Trusted Publishing
 for the `agentbridge-cli` project. The publisher is scoped to owner `tsilva`,
 repository `agentbridge`, workflow `release.yml`, and environment `pypi`; no
 PyPI API token is required. GitHub Releases contain the Python distributions
-plus ad-hoc-signed arm64 and x86_64 macOS DMGs and SHA-256 checksums. These DMGs
-are not Apple-notarized and require no Apple Developer credentials. Releases
+plus an ad-hoc-signed arm64 macOS DMG and SHA-256 checksum. The DMG is not
+Apple-notarized and requires no Apple Developer credentials. Releases
 through `0.1.10` remain available under the previous `agentbridge-py`
 distribution name.
 

agentbridge_cli-0.1.14/agentbridge/_build_info.py

@@ -0,0 +1 @@
+GIT_HASH = "0980cbb"

agentbridge_cli-0.1.14/design-qa.md

@@ -0,0 +1,55 @@
+# Design QA
+
+**Comparison target**
+
+- Source visual truth: `/var/folders/wz/x29jb7_x5rdc_5dcjr4qnhg00000gn/T/codex-clipboard-5d0ece7b-8e7b-489f-8d94-28b6877699ba.png`
+- Implementation screenshot: `/tmp/agentbridge-popover-neutral-20260829.png`
+- Combined comparison: `/tmp/agentbridge-popover-comparison-20260829.png`
+- State: connected, zero active requests, one worker, dark appearance.
+- Viewport: native macOS status popover at its fixed 350-point content width.
+- Source pixels: 818 × 404. Implementation pixels: 752 × 444. Both are native high-density captures; no density normalization was applied because this change is limited to the visible control colors rather than geometry.
+
+**Full-view comparison evidence**
+
+- The source shows the gear and Open Dashboard control inheriting the green brand tint.
+- The implementation shows both controls in the same neutral secondary-label palette used by the refresh row and supporting text.
+- The native screenshot API renders the vibrancy material with a pink capture artifact; this does not affect the visible verification that the two controls no longer use the green tint.
+
+**Focused region comparison evidence**
+
+- A separate crop was not needed: the settings icon and dashboard button are large and clearly readable in the combined full-view comparison.
+
+**Required fidelity surfaces**
+
+- Fonts and typography: unchanged.
+- Spacing and layout rhythm: unchanged.
+- Colors and visual tokens: the popover-wide control tint now uses the native secondary-label color. The logo, connected indicator, and activity fill retain their intentional brand/status colors.
+- Image quality and asset fidelity: unchanged; the existing native brand mark and SF Symbols remain in use.
+- Copy and content: unchanged.
+
+**Findings**
+
+- No actionable P0, P1, or P2 mismatches remain for the requested control-color change.
+
+**Open Questions**
+
+- None.
+
+**Implementation Checklist**
+
+- [x] Remove the green tint from popover controls.
+- [x] Preserve brand and semantic status colors.
+- [x] Build and run the native test suite.
+- [x] Capture and compare the rendered popover.
+
+**Comparison History**
+
+- Initial source finding: the settings icon and dashboard button inherited the green popover-wide tint.
+- Fix: changed the popover tint to the native secondary-label color.
+- Post-fix evidence: the combined comparison shows both controls rendered in neutral gray, with the brand and status colors preserved.
+
+**Follow-up Polish**
+
+- None.
+
+final result: passed

{agentbridge_cli-0.1.13 → agentbridge_cli-0.1.14}/macos/README.md

@@ -32,15 +32,15 @@ scripts/build_macos_app.sh
 
 The script builds the Swift executable, embeds a uv-managed Python 3.12 runtime
 and the locked AgentBridge dependencies, applies an ad-hoc signature for local
-use, and creates a DMG for the current Mac architecture under
-`build/macos/<architecture>/`. Building and running this local app does not
-require an Apple Developer account.
+use, and creates an arm64 DMG under `build/macos/arm64/`. Building and running
+this local app requires an Apple silicon Mac but does not require an Apple
+Developer account.
 
 Open the generated DMG and drag `AgentBridge.app` to Applications.
 
-GitHub Releases provide the same ad-hoc-signed DMG for arm64 and x86_64 Macs.
-They are not Apple-notarized, so macOS may require you to Control-click the app,
-choose **Open**, and confirm on first launch.
+GitHub Releases provide the same ad-hoc-signed DMG for Apple silicon Macs. It is
+not Apple-notarized, so macOS may require you to Control-click the app, choose
+**Open**, and confirm on first launch. Intel Macs are not supported.
 
 Mutable data stays outside the application bundle:
 

{agentbridge_cli-0.1.13 → agentbridge_cli-0.1.14}/macos/Sources/AgentBridgeMenuBar/StatusPopover.swift

@@ -32,12 +32,11 @@ struct StatusPopover: View {
         .padding(.bottom, 16)
         .frame(width: 350)
         .fixedSize(horizontal: false, vertical: true)
-        .tint(AgentBridgeBrand.fir)
+        .tint(secondaryTextColor)
     }
 
     private var header: some View {
         HStack(spacing: 8) {
-            AgentBridgeBrandMark(size: 24)
             Text("AgentBridge")
                 .font(.system(size: 17, weight: .bold))
             Spacer()

{agentbridge_cli-0.1.13 → agentbridge_cli-0.1.14}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "agentbridge-cli"
-version = "0.1.13"
+version = "0.1.14"
 description = "Bridge OpenAI tools to Claude Code SDK, Codex CLI, and OpenRouter"
 readme = "README.md"
 license = {text = "MIT"}

{agentbridge_cli-0.1.13 → agentbridge_cli-0.1.14}/scripts/build_macos_app.sh

@@ -23,11 +23,11 @@ with Path("pyproject.toml").open("rb") as file:
 PY
 )"
 
-case "${architecture}" in
-    arm64) artifact_architecture="arm64" ;;
-    x86_64) artifact_architecture="x86_64" ;;
-    *) echo "Unsupported macOS architecture: ${architecture}" >&2; exit 1 ;;
-esac
+if [[ "${architecture}" != "arm64" ]]; then
+    echo "Unsupported macOS architecture: ${architecture}; AgentBridge requires arm64" >&2
+    exit 1
+fi
+artifact_architecture="arm64"
 
 if [[ "${output_root}" != "${repository_root}"/build/macos/* ]]; then
     echo "Refusing to replace unexpected build directory: ${output_root}" >&2

{agentbridge_cli-0.1.13 → agentbridge_cli-0.1.14}/uv.lock

@@ -37,7 +37,7 @@ constraints = [
 
 [[package]]
 name = "agentbridge-cli"
-version = "0.1.13"
+version = "0.1.14"
 source = { editable = "." }
 dependencies = [
     { name = "claude-agent-sdk" },

agentbridge_cli-0.1.13/agentbridge/_build_info.py

@@ -1 +0,0 @@
-GIT_HASH = "6918a70"

agentbridge_cli-0.1.13/design-qa.md

@@ -1,58 +0,0 @@
-# Active-worker menu-bar badge and inactive brightness design QA
-
-## Evidence
-
-- Source visual truths:
-  - Badge proportions: `/var/folders/wz/x29jb7_x5rdc_5dcjr4qnhg00000gn/T/codex-clipboard-a88e73a8-8b49-415b-b2ef-9f289e13c5ea.png`
-  - Unfocused menu-bar brightness: `/var/folders/wz/x29jb7_x5rdc_5dcjr4qnhg00000gn/T/codex-clipboard-6c362e7b-d087-493b-8d8f-683607e7a420.png`
-  - Inner-arrow contrast: `/var/folders/wz/x29jb7_x5rdc_5dcjr4qnhg00000gn/T/codex-clipboard-7fb76339-7c5e-4568-98cf-3c91d8ad0f48.png`
-- Source pixels: 208 × 62 for the badge reference, 3232 × 76 for the unfocused menu-bar reference, and 260 × 58 for the inner-arrow reference, all at Retina density. Focused item crops retain their original 2× scale.
-- Implementation screenshots:
-  - Active state: `/Users/tsilva/repos/tsilva/agentbridge/design-qa/status-item-active-workers.png`
-  - Zero state: `/Users/tsilva/repos/tsilva/agentbridge/design-qa/status-item-no-workers.png`
-- Implementation pixels: 96 × 62 for a 48 × 31-point native AppKit fixture at 2× density.
-- Viewport: native macOS status-item button, 32 × 22 points inside a 48 × 31-point menu-bar crop.
-- Density normalization: the 64 × 62 source crop was centered on a 96 × 62 canvas without scaling so both sides retain 2× density.
-- State: dark, unfocused-style menu bar with 48 active workers for visual fidelity; running server with zero active workers for empty-state verification.
-- Combined comparisons:
-  - Badge proportions: `/Users/tsilva/repos/tsilva/agentbridge/design-qa/status-item-badge-comparison.png`
-  - Unfocused brightness: `/Users/tsilva/repos/tsilva/agentbridge/design-qa/status-item-inactive-comparison.png`
-  - Inner-arrow contrast before/after: `/Users/tsilva/repos/tsilva/agentbridge/design-qa/status-item-arrow-contrast-comparison.png`
-
-## Findings
-
-- No actionable P0/P1/P2 differences remain.
-- Fonts and typography: the badge uses a 7.5-point semibold native system font; the two-digit weight and density match the compact Telegram reference without crowding.
-- Spacing and layout rhythm: the 11-point capsule sits at the lower trailing edge of the existing icon, with the source-like overlap and enough of AgentBridge's mark remaining visible.
-- Colors and visual tokens: the badge uses the current semantic label color at 48% opacity and automatically reverses its number color for light and dark appearances. The main mark uses an appearance-aware label-color palette without template dimming, keeping it bright on an unfocused display like Telegram. Filled status symbols now use a contrasting secondary palette layer: translucent black arrows in dark appearance and translucent white detail in light appearance.
-- Image quality and asset fidelity: the existing SF Symbol remains native but is rendered as a non-template, appearance-aware image so AppKit does not mute it with inactive template tinting. The badge is rendered natively at Retina density with no raster replacement or custom icon asset.
-- Copy and content: the visible badge is the exact live active-worker number. The button tooltip and accessibility label include the same count with correct singular/plural wording.
-- Empty state: the zero-state rendering shows only the AgentBridge icon; no empty capsule or numeric badge remains.
-
-The full menu-bar reference establishes the inactive-display context and Telegram's brighter mark. The component capture is the complete implementation viewport for this isolated status item. Focused comparisons confirm capsule size, opacity, number weight, overlap, the brighter main-icon treatment, and clear separation between the outer circle and inner arrows.
-
-## Comparison History
-
-1. The first active-state rendering used a 14-point badge with wider padding. It obscured most of the circular AgentBridge symbol and was visibly larger and lighter than the Telegram badge.
-2. The badge was reduced to 11 points, its type and horizontal padding were tightened, and label opacity was lowered from 68% to 48%. The revised combined comparison shows matching compact proportions and tone, while the zero-state capture confirms complete badge removal.
-3. The inactive-display reference showed AppKit's template tint making AgentBridge materially dimmer than Telegram. The symbol now uses an appearance-aware palette and is explicitly non-template; the revised dark-appearance capture shows the bright main mark while retaining the subdued badge.
-4. The first bright non-template render gave the circle and arrows nearly identical light values, making the arrows hard to perceive. Filled symbols now use a two-color palette with 68%-opaque black inner detail in dark appearance; the before/after comparison shows clear arrow contrast. Outline-only stopped and transitional symbols retain a single semantic label color so they remain visible.
-
-## Implementation Checklist
-
-- [x] Observe live health-count changes in addition to server-phase changes.
-- [x] Show the exact active-worker count in a compact native badge.
-- [x] Hide the badge at zero.
-- [x] Keep the main icon bright instead of accepting inactive template dimming.
-- [x] Preserve appearance-aware light/dark coloring.
-- [x] Give filled symbols contrasting inner detail without darkening outline-only states.
-- [x] Preserve status-item click behavior.
-- [x] Include the count in tooltip and accessibility text.
-- [x] Verify active and zero states with Retina component captures.
-- [x] Pass Swift unit tests and a release build.
-
-## Follow-up Polish
-
-- None.
-
-final result: passed