jira-cli-toolkit 2.5.1rc1__tar.gz → 2.5.2__tar.gz

{jira_cli_toolkit-2.5.1rc1 → jira_cli_toolkit-2.5.2}/.gitignore

@@ -11,3 +11,4 @@ node_modules/
 web/dist/
 web/test-results/
 web/playwright-report/
+dist-ssr/

{jira_cli_toolkit-2.5.1rc1 → jira_cli_toolkit-2.5.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: jira-cli-toolkit
-Version: 2.5.1rc1
+Version: 2.5.2
 Summary: General-purpose Jira Cloud CLI with a friendly terminal UI
 Project-URL: Repository, https://github.com/User17745/jira-cli-toolkit
 Project-URL: Issues, https://github.com/User17745/jira-cli-toolkit/issues
@@ -15,10 +15,10 @@ Requires-Dist: requests>=2.31
 Requires-Dist: rich>=13
 Description-Content-Type: text/markdown
 
-<a href="https://user17745.github.io/jira-cli-toolkit/"><img src="docs/assets/cli-toolkit-cover-illustrated.png" alt="CLI Toolkit for Jira — independent terminal tools for Jira Cloud, with current issue, project and sprint command examples" width="100%" /></a>
+<a href="https://user17745.github.io/jira-cli-toolkit/"><img src="https://raw.githubusercontent.com/User17745/jira-cli-toolkit/main/docs/assets/cli-toolkit-cover-illustrated.png" alt="CLI Toolkit for Jira — independent terminal tools for Jira Cloud, with current issue, project and sprint command examples" width="100%" /></a>
 
 <p align="center">
-  <a href="LICENSE"><img alt="License: AGPL v3 only" src="https://img.shields.io/badge/license-AGPL%20v3%20only-087f75?style=flat-square" /></a>
+  <a href="https://github.com/User17745/jira-cli-toolkit/blob/main/LICENSE"><img alt="License: AGPL v3 only" src="https://img.shields.io/badge/license-AGPL%20v3%20only-087f75?style=flat-square" /></a>
   <a href="https://github.com/User17745/jira-cli-toolkit/releases/latest"><img alt="Latest release" src="https://img.shields.io/github/v/release/User17745/jira-cli-toolkit?style=flat-square&color=087f75" /></a>
   <a href="https://github.com/User17745/jira-cli-toolkit/actions/workflows/ci.yml"><img alt="CLI tests" src="https://img.shields.io/github/actions/workflow/status/User17745/jira-cli-toolkit/ci.yml?branch=main&style=flat-square&label=tests" /></a>
   <a href="https://github.com/User17745/jira-cli-toolkit/actions/workflows/release.yml"><img alt="Native builds" src="https://img.shields.io/github/actions/workflow/status/User17745/jira-cli-toolkit/release.yml?branch=main&style=flat-square&label=native%20builds" /></a>
@@ -33,7 +33,7 @@ Description-Content-Type: text/markdown
 
 Independent project. Not affiliated with, endorsed by, or sponsored by Atlassian. Jira is a trademark of Atlassian.
 
-[Website](https://user17745.github.io/jira-cli-toolkit/) · [Command reference](docs/usage.md) · [Latest release](https://github.com/User17745/jira-cli-toolkit/releases/latest) · [Migration guides](docs/migration/upgrade-to-v2.md)
+[Website](https://user17745.github.io/jira-cli-toolkit/) · [Command reference](https://github.com/User17745/jira-cli-toolkit/blob/main/docs/usage.md) · [Latest release](https://github.com/User17745/jira-cli-toolkit/releases/latest) · [Migration guides](https://github.com/User17745/jira-cli-toolkit/blob/main/docs/migration/upgrade-to-v2.md)
 
 ## Get started
 
@@ -48,6 +48,13 @@ export PATH="$HOME/.local/bin:$PATH"
 
 macOS **15+**, Apple Silicon or Intel. Installs to `~/.local/bin/jira`.
 
+Or with [Homebrew](https://brew.sh), which also handles upgrades:
+
+```bash
+brew install user17745/tap/jira-cli-toolkit
+brew upgrade jira-cli-toolkit
+```
+
 ### Linux
 
 ```bash
@@ -55,7 +62,7 @@ curl -fsSL https://raw.githubusercontent.com/User17745/jira-cli-toolkit/main/scr
 export PATH="$HOME/.local/bin:$PATH"
 ```
 
-Linux **x86_64, glibc 2.39+** (for example Ubuntu 24.04+). Installs to `~/.local/bin/jira`. `curl` and `sha256sum` or `shasum` are required. On older systems, musl or unsupported native architectures, use the verified Python wheel instead.
+Linux **x86_64, glibc 2.39+** (for example Ubuntu 24.04+). Installs to `~/.local/bin/jira`. `curl` and `sha256sum` or `shasum` are required. Homebrew on Linux x86_64 works too (`brew install user17745/tap/jira-cli-toolkit`). On older systems, musl or unsupported native architectures, use the Python package instead: `pipx install jira-cli-toolkit`.
 
 ### Windows
 
@@ -67,9 +74,9 @@ irm https://raw.githubusercontent.com/User17745/jira-cli-toolkit/main/scripts/in
 
 Windows **10+ x86_64**, PowerShell **5.1+**. Installs to `%LOCALAPPDATA%\JiraCLI\bin\jira.exe` and adds that directory to your user PATH. Open a new terminal if needed.
 
-**Prefer manual installation?** [Open the latest release](https://github.com/User17745/jira-cli-toolkit/releases/latest) and choose a matching binary or Python wheel. The [installation guide](docs/migration/upgrade-to-v2.md) explains verification and pipx/uv/Python installation. From 2.5.1 the Python package is also on PyPI as `jira-cli-toolkit`: `pipx install jira-cli-toolkit`, then `pipx upgrade jira-cli-toolkit`. Installations made before 2.5.1 are tracked as `jsup`; switch once with `pipx uninstall jsup` and `pipx install jira-cli-toolkit` (configuration and saved credentials are kept).
+**Prefer manual installation?** [Open the latest release](https://github.com/User17745/jira-cli-toolkit/releases/latest) and choose a matching binary or Python wheel. The [installation guide](https://github.com/User17745/jira-cli-toolkit/blob/main/docs/migration/upgrade-to-v2.md) explains verification and pipx/uv/Python installation. From 2.5.1 the Python package is also on PyPI as `jira-cli-toolkit`: `pipx install jira-cli-toolkit`, then `pipx upgrade jira-cli-toolkit`. Installations made before 2.5.1 are tracked as `jsup`; switch once with `pipx uninstall jsup` and `pipx install jira-cli-toolkit` (configuration and saved credentials are kept).
 
-**Already installed?** Use [the migration guide](docs/migration/upgrade-to-v2.md). Installers refuse to replace existing CLI commands or managed shims. Custom paths and pinned versions are documented in [installer options](docs/install.md).
+**Already installed?** Use [the migration guide](https://github.com/User17745/jira-cli-toolkit/blob/main/docs/migration/upgrade-to-v2.md). Installers refuse to replace existing CLI commands or managed shims. Custom paths and pinned versions are documented in [installer options](https://github.com/User17745/jira-cli-toolkit/blob/main/docs/install.md).
 
 ### Connect your account
 
@@ -97,7 +104,7 @@ Replace `ENG` with your project key. Guided login explains how to [create an Atl
 | List boards and sprints | `jira board list -p ENG` · `jira sprint list --board 123` |
 | Inspect project fields | `jira project fields -p ENG --type Bug` |
 
-Issue types, fields, transitions and board operations follow your project’s metadata and permissions. The CLI also supports assignment, relationships, attachments, comment maintenance, components, templates, CSV and shell completion. [Explore the full reference](docs/usage.md).
+Issue types, fields, transitions and board operations follow your project’s metadata and permissions. The CLI also supports assignment, relationships, attachments, comment maintenance, components, templates, CSV and shell completion. [Explore the full reference](https://github.com/User17745/jira-cli-toolkit/blob/main/docs/usage.md).
 
 Help works without credentials or a network connection:
 
@@ -115,7 +122,7 @@ jira issue comment --help
 - **Explicit alternatives:** scripts can supply a complete environment identity. POSIX `--storage file` is a separate mode-0600 plaintext opt-in, never an automatic fallback.
 - **Recovery:** API tokens cannot refresh automatically. Replace an invalid/revoked/expired token with `auth login`; the CLI never replays a write automatically after recovery.
 
-Native stores can require interactive approval. Linux wallets are interactive-only; scripted macOS access suppresses approval dialogs and fails with recovery instructions if approval is needed. [Read the authentication details](docs/usage.md#guided-authentication-and-profiles).
+Native stores can require interactive approval. Linux wallets are interactive-only; scripted macOS access suppresses approval dialogs and fails with recovery instructions if approval is needed. [Read the authentication details](https://github.com/User17745/jira-cli-toolkit/blob/main/docs/usage.md#guided-authentication-and-profiles).
 
 ## Automation and agents
 
@@ -128,7 +135,7 @@ jira completion zsh
 
 JSON preserves API field structures, CSV supports selected columns, and `--no-input` makes missing input explicit. Destructive commands still need `--yes` in scripts. Runtime errors are structured on stdout for grouped commands; diagnostics and usage errors use stderr. Exit codes: **0** success/help, **1** API/network failure, **2** input/config/file errors, **130** interruption.
 
-Templates are declarative JSON with declared variables, not executable hooks. The example callback template has explicit defaults that must fit your project; ordinary creation adds no support-specific fields. [Read scripting and template details](docs/usage.md).
+Templates are declarative JSON with declared variables, not executable hooks. The example callback template has explicit defaults that must fit your project; ordinary creation adds no support-specific fields. [Read scripting and template details](https://github.com/User17745/jira-cli-toolkit/blob/main/docs/usage.md).
 
 ### Any REST endpoint, without a token in the command
 
@@ -141,7 +148,7 @@ jira api /rest/api/3/project/search --query maxResults=20
 jira api /rest/agile/1.0/board/12/sprint --profile work | jq '.values[].name'
 ```
 
-Response bodies go to stdout exactly as Jira returns them; failures are a JSON object on stderr. Requests stay on your site: no absolute URLs, no redirects, and auth headers can't be overridden. Writes are never retried. For unattended agents, approve keychain access once and give the agent a least-privilege account. [Read the API, discovery and agent setup guide](docs/usage.md#calling-any-rest-endpoint).
+Response bodies go to stdout exactly as Jira returns them; failures are a JSON object on stderr. Requests stay on your site: no absolute URLs, no redirects, and auth headers can't be overridden. Writes are never retried. For unattended agents, approve keychain access once and give the agent a least-privilege account. [Read the API, discovery and agent setup guide](https://github.com/User17745/jira-cli-toolkit/blob/main/docs/usage.md#calling-any-rest-endpoint).
 
 ## Explicit updates and releases
 
@@ -153,9 +160,9 @@ jira update --yes
 
 Standalone updates select a compatible GitHub Release binary, verify its manifest/hash/size, validate version/help, and retain a `.previous` backup. Windows completes replacement through a separate helper. Config and credentials stay untouched; ordinary commands never auto-update.
 
-For pipx/uv/Python installations, `update` gives instructions for the owning manager. Public downloads need no Jira token; an optional GitHub token can increase API rate limits. [Update, verification and rollback details](docs/migration/upgrade-to-v2.md).
+For pipx/uv/Python installations, `update` gives instructions for the owning manager. Public downloads need no Jira token; an optional GitHub token can increase API rate limits. [Update, verification and rollback details](https://github.com/User17745/jira-cli-toolkit/blob/main/docs/migration/upgrade-to-v2.md).
 
-Releases contain wheel/sdist, macOS arm64/x86_64, Linux x86_64 and Windows x86_64 binaries, manifest and checksums. Current native OS requirements are listed above and in the manifest. Independent attestation verification, signing and notarization remain [release-hardening work](docs/sprints/v2-upgrade/roadmap.md#remaining-work-after-v21).
+Releases contain wheel/sdist, macOS arm64/x86_64, Linux x86_64 and Windows x86_64 binaries, manifest and checksums. Current native OS requirements are listed above and in the manifest. Independent attestation verification, signing and notarization remain [release-hardening work](https://github.com/User17745/jira-cli-toolkit/blob/main/docs/sprints/v2-upgrade/roadmap.md#remaining-work-after-v21).
 
 ## Migrating from old commands
 
@@ -167,7 +174,7 @@ Releases contain wheel/sdist, macOS arm64/x86_64, Linux x86_64 and Windows x86_6
 | `jsup issue-show ENG-42` | `jira issue view ENG-42` |
 | `jsup issue-move ENG-42 --to Done` | `jira issue transition ENG-42 --to Done` |
 
-Read the [installation/credential migration guide](docs/migration/upgrade-to-v2.md) and the [complete developer command migration](docs/migration/legacy-commands.md). Existing migrated profiles need no second credential migration when updating from v2.0.
+Read the [installation/credential migration guide](https://github.com/User17745/jira-cli-toolkit/blob/main/docs/migration/upgrade-to-v2.md) and the [complete developer command migration](https://github.com/User17745/jira-cli-toolkit/blob/main/docs/migration/legacy-commands.md). Existing migrated profiles need no second credential migration when updating from v2.0.
 
 ## Development
 
@@ -189,13 +196,13 @@ npm run build
 npm test
 ```
 
-[Website development and browser checks](web/README.md) · [Installer development](docs/install.md) · [Release acceptance](docs/sprints/v2-upgrade/acceptance.md)
+[Website development and browser checks](https://github.com/User17745/jira-cli-toolkit/blob/main/web/README.md) · [Installer development](https://github.com/User17745/jira-cli-toolkit/blob/main/docs/install.md) · [Release acceptance](https://github.com/User17745/jira-cli-toolkit/blob/main/docs/sprints/v2-upgrade/acceptance.md)
 
 ## Scope and next steps
 
 The current release supports standard **Jira Cloud** issues and applicable Software boards/sprints, and any Jira Cloud REST endpoint through `jira api`, including Service Management. Service Management convenience commands and Data Center remain future work. Required-field discovery cannot describe every app-specific workflow validator; Jira remains authoritative.
 
-Original project code is licensed under **AGPL-3.0-only**. [See completed milestones and remaining work](docs/sprints/v2-upgrade/roadmap.md).
+Original project code is licensed under **AGPL-3.0-only**. [See completed milestones and remaining work](https://github.com/User17745/jira-cli-toolkit/blob/main/docs/sprints/v2-upgrade/roadmap.md).
 
 ## Independent project and intellectual property notice
 
@@ -207,6 +214,6 @@ No infringement of third-party trademarks, copyrights, patents, or other intelle
 
 ## License
 
-Copyright © 2026 Abhishek Aggarwal. Original project code is licensed under the **GNU Affero General Public License, version 3 only (AGPL-3.0-only)**. You may redistribute and modify it under that license. It is provided **without warranty**, including any implied warranty of merchantability or fitness for a particular purpose. See [LICENSE](LICENSE) for the complete terms and [NOTICE](NOTICE) for the project notice.
+Copyright © 2026 Abhishek Aggarwal. Original project code is licensed under the **GNU Affero General Public License, version 3 only (AGPL-3.0-only)**. You may redistribute and modify it under that license. It is provided **without warranty**, including any implied warranty of merchantability or fitness for a particular purpose. See [LICENSE](https://github.com/User17745/jira-cli-toolkit/blob/main/LICENSE) for the complete terms and [NOTICE](https://github.com/User17745/jira-cli-toolkit/blob/main/NOTICE) for the project notice.
 
-Third-party components and assets retain their own copyright notices and applicable license terms; preserve those notices when redistributing them. This does not remove applicable AGPL obligations for covered combined works. The project license does not grant rights to third-party trademarks. [Website third-party notices](web/public/third-party-notices.txt) are included separately.
+Third-party components and assets retain their own copyright notices and applicable license terms; preserve those notices when redistributing them. This does not remove applicable AGPL obligations for covered combined works. The project license does not grant rights to third-party trademarks. [Website third-party notices](https://github.com/User17745/jira-cli-toolkit/blob/main/web/public/third-party-notices.txt) are included separately.

{jira_cli_toolkit-2.5.1rc1 → jira_cli_toolkit-2.5.2}/README.md

@@ -1,7 +1,7 @@
-<a href="https://user17745.github.io/jira-cli-toolkit/"><img src="docs/assets/cli-toolkit-cover-illustrated.png" alt="CLI Toolkit for Jira — independent terminal tools for Jira Cloud, with current issue, project and sprint command examples" width="100%" /></a>
+<a href="https://user17745.github.io/jira-cli-toolkit/"><img src="https://raw.githubusercontent.com/User17745/jira-cli-toolkit/main/docs/assets/cli-toolkit-cover-illustrated.png" alt="CLI Toolkit for Jira — independent terminal tools for Jira Cloud, with current issue, project and sprint command examples" width="100%" /></a>
 
 <p align="center">
-  <a href="LICENSE"><img alt="License: AGPL v3 only" src="https://img.shields.io/badge/license-AGPL%20v3%20only-087f75?style=flat-square" /></a>
+  <a href="https://github.com/User17745/jira-cli-toolkit/blob/main/LICENSE"><img alt="License: AGPL v3 only" src="https://img.shields.io/badge/license-AGPL%20v3%20only-087f75?style=flat-square" /></a>
   <a href="https://github.com/User17745/jira-cli-toolkit/releases/latest"><img alt="Latest release" src="https://img.shields.io/github/v/release/User17745/jira-cli-toolkit?style=flat-square&color=087f75" /></a>
   <a href="https://github.com/User17745/jira-cli-toolkit/actions/workflows/ci.yml"><img alt="CLI tests" src="https://img.shields.io/github/actions/workflow/status/User17745/jira-cli-toolkit/ci.yml?branch=main&style=flat-square&label=tests" /></a>
   <a href="https://github.com/User17745/jira-cli-toolkit/actions/workflows/release.yml"><img alt="Native builds" src="https://img.shields.io/github/actions/workflow/status/User17745/jira-cli-toolkit/release.yml?branch=main&style=flat-square&label=native%20builds" /></a>
@@ -16,7 +16,7 @@
 
 Independent project. Not affiliated with, endorsed by, or sponsored by Atlassian. Jira is a trademark of Atlassian.
 
-[Website](https://user17745.github.io/jira-cli-toolkit/) · [Command reference](docs/usage.md) · [Latest release](https://github.com/User17745/jira-cli-toolkit/releases/latest) · [Migration guides](docs/migration/upgrade-to-v2.md)
+[Website](https://user17745.github.io/jira-cli-toolkit/) · [Command reference](https://github.com/User17745/jira-cli-toolkit/blob/main/docs/usage.md) · [Latest release](https://github.com/User17745/jira-cli-toolkit/releases/latest) · [Migration guides](https://github.com/User17745/jira-cli-toolkit/blob/main/docs/migration/upgrade-to-v2.md)
 
 ## Get started
 
@@ -31,6 +31,13 @@ export PATH="$HOME/.local/bin:$PATH"
 
 macOS **15+**, Apple Silicon or Intel. Installs to `~/.local/bin/jira`.
 
+Or with [Homebrew](https://brew.sh), which also handles upgrades:
+
+```bash
+brew install user17745/tap/jira-cli-toolkit
+brew upgrade jira-cli-toolkit
+```
+
 ### Linux
 
 ```bash
@@ -38,7 +45,7 @@ curl -fsSL https://raw.githubusercontent.com/User17745/jira-cli-toolkit/main/scr
 export PATH="$HOME/.local/bin:$PATH"
 ```
 
-Linux **x86_64, glibc 2.39+** (for example Ubuntu 24.04+). Installs to `~/.local/bin/jira`. `curl` and `sha256sum` or `shasum` are required. On older systems, musl or unsupported native architectures, use the verified Python wheel instead.
+Linux **x86_64, glibc 2.39+** (for example Ubuntu 24.04+). Installs to `~/.local/bin/jira`. `curl` and `sha256sum` or `shasum` are required. Homebrew on Linux x86_64 works too (`brew install user17745/tap/jira-cli-toolkit`). On older systems, musl or unsupported native architectures, use the Python package instead: `pipx install jira-cli-toolkit`.
 
 ### Windows
 
@@ -50,9 +57,9 @@ irm https://raw.githubusercontent.com/User17745/jira-cli-toolkit/main/scripts/in
 
 Windows **10+ x86_64**, PowerShell **5.1+**. Installs to `%LOCALAPPDATA%\JiraCLI\bin\jira.exe` and adds that directory to your user PATH. Open a new terminal if needed.
 
-**Prefer manual installation?** [Open the latest release](https://github.com/User17745/jira-cli-toolkit/releases/latest) and choose a matching binary or Python wheel. The [installation guide](docs/migration/upgrade-to-v2.md) explains verification and pipx/uv/Python installation. From 2.5.1 the Python package is also on PyPI as `jira-cli-toolkit`: `pipx install jira-cli-toolkit`, then `pipx upgrade jira-cli-toolkit`. Installations made before 2.5.1 are tracked as `jsup`; switch once with `pipx uninstall jsup` and `pipx install jira-cli-toolkit` (configuration and saved credentials are kept).
+**Prefer manual installation?** [Open the latest release](https://github.com/User17745/jira-cli-toolkit/releases/latest) and choose a matching binary or Python wheel. The [installation guide](https://github.com/User17745/jira-cli-toolkit/blob/main/docs/migration/upgrade-to-v2.md) explains verification and pipx/uv/Python installation. From 2.5.1 the Python package is also on PyPI as `jira-cli-toolkit`: `pipx install jira-cli-toolkit`, then `pipx upgrade jira-cli-toolkit`. Installations made before 2.5.1 are tracked as `jsup`; switch once with `pipx uninstall jsup` and `pipx install jira-cli-toolkit` (configuration and saved credentials are kept).
 
-**Already installed?** Use [the migration guide](docs/migration/upgrade-to-v2.md). Installers refuse to replace existing CLI commands or managed shims. Custom paths and pinned versions are documented in [installer options](docs/install.md).
+**Already installed?** Use [the migration guide](https://github.com/User17745/jira-cli-toolkit/blob/main/docs/migration/upgrade-to-v2.md). Installers refuse to replace existing CLI commands or managed shims. Custom paths and pinned versions are documented in [installer options](https://github.com/User17745/jira-cli-toolkit/blob/main/docs/install.md).
 
 ### Connect your account
 
@@ -80,7 +87,7 @@ Replace `ENG` with your project key. Guided login explains how to [create an Atl
 | List boards and sprints | `jira board list -p ENG` · `jira sprint list --board 123` |
 | Inspect project fields | `jira project fields -p ENG --type Bug` |
 
-Issue types, fields, transitions and board operations follow your project’s metadata and permissions. The CLI also supports assignment, relationships, attachments, comment maintenance, components, templates, CSV and shell completion. [Explore the full reference](docs/usage.md).
+Issue types, fields, transitions and board operations follow your project’s metadata and permissions. The CLI also supports assignment, relationships, attachments, comment maintenance, components, templates, CSV and shell completion. [Explore the full reference](https://github.com/User17745/jira-cli-toolkit/blob/main/docs/usage.md).
 
 Help works without credentials or a network connection:
 
@@ -98,7 +105,7 @@ jira issue comment --help
 - **Explicit alternatives:** scripts can supply a complete environment identity. POSIX `--storage file` is a separate mode-0600 plaintext opt-in, never an automatic fallback.
 - **Recovery:** API tokens cannot refresh automatically. Replace an invalid/revoked/expired token with `auth login`; the CLI never replays a write automatically after recovery.
 
-Native stores can require interactive approval. Linux wallets are interactive-only; scripted macOS access suppresses approval dialogs and fails with recovery instructions if approval is needed. [Read the authentication details](docs/usage.md#guided-authentication-and-profiles).
+Native stores can require interactive approval. Linux wallets are interactive-only; scripted macOS access suppresses approval dialogs and fails with recovery instructions if approval is needed. [Read the authentication details](https://github.com/User17745/jira-cli-toolkit/blob/main/docs/usage.md#guided-authentication-and-profiles).
 
 ## Automation and agents
 
@@ -111,7 +118,7 @@ jira completion zsh
 
 JSON preserves API field structures, CSV supports selected columns, and `--no-input` makes missing input explicit. Destructive commands still need `--yes` in scripts. Runtime errors are structured on stdout for grouped commands; diagnostics and usage errors use stderr. Exit codes: **0** success/help, **1** API/network failure, **2** input/config/file errors, **130** interruption.
 
-Templates are declarative JSON with declared variables, not executable hooks. The example callback template has explicit defaults that must fit your project; ordinary creation adds no support-specific fields. [Read scripting and template details](docs/usage.md).
+Templates are declarative JSON with declared variables, not executable hooks. The example callback template has explicit defaults that must fit your project; ordinary creation adds no support-specific fields. [Read scripting and template details](https://github.com/User17745/jira-cli-toolkit/blob/main/docs/usage.md).
 
 ### Any REST endpoint, without a token in the command
 
@@ -124,7 +131,7 @@ jira api /rest/api/3/project/search --query maxResults=20
 jira api /rest/agile/1.0/board/12/sprint --profile work | jq '.values[].name'
 ```
 
-Response bodies go to stdout exactly as Jira returns them; failures are a JSON object on stderr. Requests stay on your site: no absolute URLs, no redirects, and auth headers can't be overridden. Writes are never retried. For unattended agents, approve keychain access once and give the agent a least-privilege account. [Read the API, discovery and agent setup guide](docs/usage.md#calling-any-rest-endpoint).
+Response bodies go to stdout exactly as Jira returns them; failures are a JSON object on stderr. Requests stay on your site: no absolute URLs, no redirects, and auth headers can't be overridden. Writes are never retried. For unattended agents, approve keychain access once and give the agent a least-privilege account. [Read the API, discovery and agent setup guide](https://github.com/User17745/jira-cli-toolkit/blob/main/docs/usage.md#calling-any-rest-endpoint).
 
 ## Explicit updates and releases
 
@@ -136,9 +143,9 @@ jira update --yes
 
 Standalone updates select a compatible GitHub Release binary, verify its manifest/hash/size, validate version/help, and retain a `.previous` backup. Windows completes replacement through a separate helper. Config and credentials stay untouched; ordinary commands never auto-update.
 
-For pipx/uv/Python installations, `update` gives instructions for the owning manager. Public downloads need no Jira token; an optional GitHub token can increase API rate limits. [Update, verification and rollback details](docs/migration/upgrade-to-v2.md).
+For pipx/uv/Python installations, `update` gives instructions for the owning manager. Public downloads need no Jira token; an optional GitHub token can increase API rate limits. [Update, verification and rollback details](https://github.com/User17745/jira-cli-toolkit/blob/main/docs/migration/upgrade-to-v2.md).
 
-Releases contain wheel/sdist, macOS arm64/x86_64, Linux x86_64 and Windows x86_64 binaries, manifest and checksums. Current native OS requirements are listed above and in the manifest. Independent attestation verification, signing and notarization remain [release-hardening work](docs/sprints/v2-upgrade/roadmap.md#remaining-work-after-v21).
+Releases contain wheel/sdist, macOS arm64/x86_64, Linux x86_64 and Windows x86_64 binaries, manifest and checksums. Current native OS requirements are listed above and in the manifest. Independent attestation verification, signing and notarization remain [release-hardening work](https://github.com/User17745/jira-cli-toolkit/blob/main/docs/sprints/v2-upgrade/roadmap.md#remaining-work-after-v21).
 
 ## Migrating from old commands
 
@@ -150,7 +157,7 @@ Releases contain wheel/sdist, macOS arm64/x86_64, Linux x86_64 and Windows x86_6
 | `jsup issue-show ENG-42` | `jira issue view ENG-42` |
 | `jsup issue-move ENG-42 --to Done` | `jira issue transition ENG-42 --to Done` |
 
-Read the [installation/credential migration guide](docs/migration/upgrade-to-v2.md) and the [complete developer command migration](docs/migration/legacy-commands.md). Existing migrated profiles need no second credential migration when updating from v2.0.
+Read the [installation/credential migration guide](https://github.com/User17745/jira-cli-toolkit/blob/main/docs/migration/upgrade-to-v2.md) and the [complete developer command migration](https://github.com/User17745/jira-cli-toolkit/blob/main/docs/migration/legacy-commands.md). Existing migrated profiles need no second credential migration when updating from v2.0.
 
 ## Development
 
@@ -172,13 +179,13 @@ npm run build
 npm test
 ```
 
-[Website development and browser checks](web/README.md) · [Installer development](docs/install.md) · [Release acceptance](docs/sprints/v2-upgrade/acceptance.md)
+[Website development and browser checks](https://github.com/User17745/jira-cli-toolkit/blob/main/web/README.md) · [Installer development](https://github.com/User17745/jira-cli-toolkit/blob/main/docs/install.md) · [Release acceptance](https://github.com/User17745/jira-cli-toolkit/blob/main/docs/sprints/v2-upgrade/acceptance.md)
 
 ## Scope and next steps
 
 The current release supports standard **Jira Cloud** issues and applicable Software boards/sprints, and any Jira Cloud REST endpoint through `jira api`, including Service Management. Service Management convenience commands and Data Center remain future work. Required-field discovery cannot describe every app-specific workflow validator; Jira remains authoritative.
 
-Original project code is licensed under **AGPL-3.0-only**. [See completed milestones and remaining work](docs/sprints/v2-upgrade/roadmap.md).
+Original project code is licensed under **AGPL-3.0-only**. [See completed milestones and remaining work](https://github.com/User17745/jira-cli-toolkit/blob/main/docs/sprints/v2-upgrade/roadmap.md).
 
 ## Independent project and intellectual property notice
 
@@ -190,6 +197,6 @@ No infringement of third-party trademarks, copyrights, patents, or other intelle
 
 ## License
 
-Copyright © 2026 Abhishek Aggarwal. Original project code is licensed under the **GNU Affero General Public License, version 3 only (AGPL-3.0-only)**. You may redistribute and modify it under that license. It is provided **without warranty**, including any implied warranty of merchantability or fitness for a particular purpose. See [LICENSE](LICENSE) for the complete terms and [NOTICE](NOTICE) for the project notice.
+Copyright © 2026 Abhishek Aggarwal. Original project code is licensed under the **GNU Affero General Public License, version 3 only (AGPL-3.0-only)**. You may redistribute and modify it under that license. It is provided **without warranty**, including any implied warranty of merchantability or fitness for a particular purpose. See [LICENSE](https://github.com/User17745/jira-cli-toolkit/blob/main/LICENSE) for the complete terms and [NOTICE](https://github.com/User17745/jira-cli-toolkit/blob/main/NOTICE) for the project notice.
 
-Third-party components and assets retain their own copyright notices and applicable license terms; preserve those notices when redistributing them. This does not remove applicable AGPL obligations for covered combined works. The project license does not grant rights to third-party trademarks. [Website third-party notices](web/public/third-party-notices.txt) are included separately.
+Third-party components and assets retain their own copyright notices and applicable license terms; preserve those notices when redistributing them. This does not remove applicable AGPL obligations for covered combined works. The project license does not grant rights to third-party trademarks. [Website third-party notices](https://github.com/User17745/jira-cli-toolkit/blob/main/web/public/third-party-notices.txt) are included separately.

{jira_cli_toolkit-2.5.1rc1 → jira_cli_toolkit-2.5.2}/docs/releases/2.5.md

@@ -1,3 +1,8 @@
+## What's new in 2.5.2
+
+- **Homebrew:** `brew install user17745/tap/jira-cli-toolkit` on macOS (Apple Silicon and Intel) and Linux x86_64, upgraded with `brew upgrade jira-cli-toolkit`. `jira update` recognizes a Homebrew installation and points to `brew upgrade` instead of replacing its files.
+- **PyPI page:** the README's images and links now work on PyPI.
+
 ## What's new in 2.5.1
 
 - **On PyPI:** `pipx install jira-cli-toolkit`, then `pipx upgrade jira-cli-toolkit`. The package was previously named `jsup`; a pipx or uv installation made before 2.5.1 switches once with `pipx uninstall jsup` and `pipx install jira-cli-toolkit` (configuration and saved credentials are kept). `jira update` gives package-manager users the exact command.

{jira_cli_toolkit-2.5.1rc1 → jira_cli_toolkit-2.5.2}/docs/usage.md

@@ -215,7 +215,7 @@ A selected `--profile` owns its full site/account identity. Complete identity fl
 
 **Updating a 2.1.0 standalone binary:** run `jira update --yes --json`. Without `--json`, 2.1.0 replaces itself successfully but then crashes while printing the result (`zlib.error … incorrect header check`); the update has still completed, and `jira --version` shows the new version. From 2.5, the updater loads everything it needs before replacing the executable.
 
-The repository and release downloads are public. The updater works without GitHub login; an optional `GH_TOKEN` or authenticated `gh` account can raise API rate limits. Jira tokens are never used for GitHub. Package installations receive an exact-version command for their owning pipx, uv or Python environment, such as `pipx install --force 'jira-cli-toolkit==2.5.1'`; the updater does not overwrite manager shims. From 2.5.1 the package is on PyPI as `jira-cli-toolkit`, so `pipx upgrade jira-cli-toolkit` also works. Installations made before 2.5.1 use the package's old name, `jsup`; the updater says so and gives the one-time switch for pipx, uv or pip (uninstall `jsup`, then install `jira-cli-toolkit`), which keeps configuration and saved credentials. Don't install both side by side: they ship the same module. To install offline, download the release wheel, verify its manifest checksum, and pass its path to the same command. Version 0.2.0 needs this one-time bootstrap before it gains an update command.
+The repository and release downloads are public. The updater works without GitHub login; an optional `GH_TOKEN` or authenticated `gh` account can raise API rate limits. Jira tokens are never used for GitHub. Homebrew installations (`brew install user17745/tap/jira-cli-toolkit`) are upgraded with `brew upgrade jira-cli-toolkit`; `jira update` says so instead of replacing files Homebrew owns. The tap checks for new GitHub releases daily. Package installations receive an exact-version command for their owning pipx, uv or Python environment, such as `pipx install --force 'jira-cli-toolkit==2.5.1'`; the updater does not overwrite manager shims. From 2.5.1 the package is on PyPI as `jira-cli-toolkit`, so `pipx upgrade jira-cli-toolkit` also works. Installations made before 2.5.1 use the package's old name, `jsup`; the updater says so and gives the one-time switch for pipx, uv or pip (uninstall `jsup`, then install `jira-cli-toolkit`), which keeps configuration and saved credentials. Don't install both side by side: they ship the same module. To install offline, download the release wheel, verify its manifest checksum, and pass its path to the same command. Version 0.2.0 needs this one-time bootstrap before it gains an update command.
 
 If pipx’s uv backend refuses force installation because the venv exists, adding `--backend pip` does not switch that existing environment in pipx 1.14.0. Download and verify the wheel, run `pipx uninstall jsup`, then `pipx install --backend pip /path/to/jsup.whl`. The [migration guide](sprints/v2-upgrade/migration.md) explains this recovery and preservation of saved credentials. Manager detection uses installation receipts, including custom pipx/uv directories.
 

{jira_cli_toolkit-2.5.1rc1 → jira_cli_toolkit-2.5.2}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "jira-cli-toolkit"
-version = "2.5.1rc1"
+version = "2.5.2"
 description = "General-purpose Jira Cloud CLI with a friendly terminal UI"
 readme = "README.md"
 license = "AGPL-3.0-only"

{jira_cli_toolkit-2.5.1rc1 → jira_cli_toolkit-2.5.2}/src/jsup/__init__.py

@@ -4,4 +4,4 @@ from .client import Jira, JiraError, adf, adf_to_text
 
 __all__ = ["CONFIG_PATH", "get_config", "init_config", "show_config",
            "Jira", "JiraError", "adf", "adf_to_text"]
-__version__ = "2.5.1rc1"
+__version__ = "2.5.2"

{jira_cli_toolkit-2.5.1rc1 → jira_cli_toolkit-2.5.2}/src/jsup/update.py

@@ -44,7 +44,8 @@ def _distribution():
 
 def installation():
     if getattr(sys,'frozen',False):
-        method='standalone'
+        # Homebrew owns files under its Cellar; replacing them would break `brew upgrade`.
+        method='homebrew' if '/Cellar/' in str(Path(sys.executable).resolve()).replace('\\','/') else 'standalone'
     else:
         prefix=Path(sys.prefix)
         executable=str(Path(sys.executable).absolute()).replace('\\','/')
@@ -55,7 +56,7 @@ def installation():
         else:
             method='python'
     arch={'amd64':'x86_64','x86_64':'x86_64','aarch64':'arm64','arm64':'arm64'}.get(platform.machine().lower(),platform.machine().lower())
-    return dict(version=__version__,method=method,distribution=None if method=='standalone' else _distribution(),os={'Darwin':'macos','Linux':'linux','Windows':'windows'}.get(platform.system(),'unsupported'),
+    return dict(version=__version__,method=method,distribution=None if method in ('standalone','homebrew') else _distribution(),os={'Darwin':'macos','Linux':'linux','Windows':'windows'}.get(platform.system(),'unsupported'),
                 arch=arch,executable=str(Path(sys.executable).resolve()),python=sys.version.split()[0])
 
 
@@ -261,6 +262,10 @@ def apply_windows_update(values):
 def handle(args):
     installed=installation()
     if args.info: return installed
+    if args.version and installed['method']=='homebrew':
+        # The tap only offers its latest stable release; brew can't install another one.
+        raise UpdateError(f'Homebrew installs follow the tap\'s latest stable release; run brew upgrade {DISTRIBUTION}. '
+                          f'For a specific version, use that release\'s binary or pipx install \'{DISTRIBUTION}==VERSION\'.')
     try: requested=Version(args.version.removeprefix('v')) if args.version else None
     except InvalidVersion: raise UpdateError('Use a valid release version.') from None
     if requested and requested.is_prerelease and not args.prerelease:
@@ -285,6 +290,10 @@ def handle(args):
             available=version!=Version(__version__)
             result={**installed,'available_version':str(version),'update_available':available,'release_url':release.get('html_url'),'updated':False}
             if args.check or not available: return result
+            if installed['method']=='homebrew':
+                result.update(instructions=f'brew upgrade {DISTRIBUTION}',
+                              note='Homebrew manages this installation; the tap picks up new releases within a day.')
+                return result
             if installed['method']!='standalone':
                 wheel=next((a for a in manifest['artifacts'] if a.get('kind')=='wheel'),None)
                 if not wheel: raise UpdateError('Release has no Python wheel for this installation.')

{jira_cli_toolkit-2.5.1rc1 → jira_cli_toolkit-2.5.2}/tests/test_update.py

@@ -89,6 +89,29 @@ class UpdateTests(unittest.TestCase):
                 self.assertNotIn('migration',result)
         self.assertEqual(self.api.download.call_count,3)
 
+    def test_homebrew_installs_are_upgraded_by_brew_not_replaced(self):
+        self.installed.update(method='homebrew',distribution=None)
+        with patch.object(update,'replace_binary') as replace:
+            result=update.handle(args(check=False))
+        replace.assert_not_called()
+        self.assertEqual(result['instructions'],'brew upgrade jira-cli-toolkit')
+        self.assertFalse(result['updated'])
+
+    def test_homebrew_installs_reject_explicit_versions(self):
+        self.installed.update(method='homebrew',distribution=None)
+        with self.assertRaisesRegex(update.UpdateError,'latest stable release'):
+            update.handle(args(check=False,version='2.0.0'))
+        self.api.release.assert_not_called()
+
+    def test_frozen_binaries_in_a_homebrew_cellar_are_detected(self):
+        patch.stopall()  # setUp stubs installation(); this test needs the real one
+        with patch.object(update.sys,'frozen',True,create=True), \
+                patch.object(update.sys,'executable','/opt/homebrew/Cellar/jira-cli-toolkit/2.5.2/bin/jira'):
+            self.assertEqual(update.installation()['method'],'homebrew')
+        with patch.object(update.sys,'frozen',True,create=True), \
+                patch.object(update.sys,'executable','/Users/me/.local/bin/jira'):
+            self.assertEqual(update.installation()['method'],'standalone')
+
     def test_installs_tracked_as_jsup_get_a_one_time_switch(self):
         self.installed.update(method='pipx',distribution='jsup')
         result=update.handle(args(check=False))

{jira_cli_toolkit-2.5.1rc1 → jira_cli_toolkit-2.5.2}/uv.lock

@@ -433,7 +433,7 @@ wheels = [
 
 [[package]]
 name = "jira-cli-toolkit"
-version = "2.5.1rc1"
+version = "2.5.2"
 source = { editable = "." }
 dependencies = [
     { name = "keyring" },

{jira_cli_toolkit-2.5.1rc1 → jira_cli_toolkit-2.5.2}/web/package.json

@@ -5,7 +5,7 @@
   "type": "module",
   "scripts": {
     "dev": "vite",
-    "build": "tsc -b && vite build",
+    "build": "tsc -b && vite build && vite build --ssr src/entry-server.tsx --outDir dist-ssr && node scripts/prerender.mjs",
     "lint": "oxlint",
     "preview": "vite preview",
     "test": "playwright test"

jira_cli_toolkit-2.5.2/web/public/llms.txt

@@ -0,0 +1,48 @@
+# CLI Toolkit for Jira
+
+> An independent command-line tool for Jira Cloud, built so AI agents can drive Jira: plan roadmaps into sprints, write standup digests, and update issues as code merges. The command is `jira`. It runs with the user's own Jira permissions and API token, on macOS, Linux and Windows. Not affiliated with Atlassian. Open source under AGPL-3.0-only.
+
+Key facts for agents:
+
+- Install once per machine, then sign in from a human-run terminal: `jira auth login --profile work`. Tokens go to the OS credential store. Never ask the user for their API token.
+- Each profile is one Jira account. Add more with another `--profile NAME`, switch with `jira profile use NAME`, or pass `--profile NAME` to a single command.
+- Before the first Jira task, check access with `jira auth status --json --no-input`.
+- Add `--json --no-input` to every command and read results from stdout. Errors are JSON too.
+- Exit codes: 0 success, 1 Jira or network error, 2 invalid input or configuration, 130 interrupted.
+- Look before writing: `jira project fields KEY --type TYPE` lists required fields, and `jira issue transitions ISSUE` lists valid moves.
+- `jira help <command>` prints the real help for any command, offline and without credentials.
+- For anything without a dedicated command, `jira api <path> --spec` shows an endpoint's permissions, scopes and body schema; then `jira api <path>` calls it with the saved profile.
+- Destructive commands need `--yes` in scripts. Writes are never retried automatically.
+
+Install:
+
+- macOS and Linux: `curl -fsSL https://raw.githubusercontent.com/User17745/jira-cli-toolkit/main/scripts/install.sh | bash`, then `export PATH="$HOME/.local/bin:$PATH"`
+- Windows (PowerShell): `irm https://raw.githubusercontent.com/User17745/jira-cli-toolkit/main/scripts/install.ps1 | iex`
+
+Everyday commands:
+
+- `jira context use --project ENG` sets the default project
+- `jira issue list --open` lists open issues; add `--jql '...'` for your own query, `--csv --columns key,summary,status` for CSV
+- `jira issue view ENG-42` shows one issue
+- `jira issue create -p ENG --type Bug --summary "Fix login"` creates an issue
+- `jira issue edit ENG-42 --summary "..."` edits one
+- `jira issue transition ENG-42 --to "In Progress"` moves it through its workflow
+- `jira issue assign ENG-42 --user me` assigns it
+- `jira issue comment add ENG-42 -m "Review started"` comments
+- `jira board list -p ENG` and `jira sprint list --board 123` list boards and sprints
+
+## Docs
+
+- [README](https://github.com/User17745/jira-cli-toolkit/blob/main/README.md): overview, installation, everyday workflows, authentication and automation
+- [Command reference and usage guide](https://github.com/User17745/jira-cli-toolkit/blob/main/docs/usage.md): every command, profiles, scripting, templates and output formats
+- [Setting up an agent or script](https://github.com/User17745/jira-cli-toolkit/blob/main/docs/usage.md#setting-up-an-agent-or-script-once): one-time sign-in, keychain approval and headless options
+- [Calling any REST endpoint](https://github.com/User17745/jira-cli-toolkit/blob/main/docs/usage.md#calling-any-rest-endpoint): `jira api`, `--spec` lookups and safety limits
+- [Installer options](https://github.com/User17745/jira-cli-toolkit/blob/main/docs/install.md): custom paths and pinned versions
+- [Upgrading and migration](https://github.com/User17745/jira-cli-toolkit/blob/main/docs/migration/upgrade-to-v2.md): manual installs, verification, and moving from `jsup`
+
+## Optional
+
+- [Latest release](https://github.com/User17745/jira-cli-toolkit/releases/latest): native binaries and the Python wheel
+- [Source code](https://github.com/User17745/jira-cli-toolkit)
+- [License (AGPL-3.0-only)](https://github.com/User17745/jira-cli-toolkit/blob/main/LICENSE)
+- [Report an issue](https://github.com/User17745/jira-cli-toolkit/issues)

jira_cli_toolkit-2.5.2/web/public/robots.txt

@@ -0,0 +1,4 @@
+User-agent: *
+Allow: /
+
+Sitemap: https://jira.abhishekaggarwal.com/sitemap.xml

jira_cli_toolkit-2.5.2/web/public/sitemap.xml

@@ -0,0 +1,4 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
+  <url><loc>https://jira.abhishekaggarwal.com/</loc></url>
+</urlset>

jira_cli_toolkit-2.5.2/web/scripts/prerender.mjs

@@ -0,0 +1,11 @@
+// Renders the page into dist/index.html after `vite build --ssr`, then removes the server bundle.
+import { readFile, rm, writeFile } from 'node:fs/promises'
+
+const server = new URL('../dist-ssr/', import.meta.url)
+const page = new URL('../dist/index.html', import.meta.url)
+const { render } = await import(new URL('entry-server.js', server).href)
+const html = await readFile(page, 'utf8')
+const empty = '<div id="root"></div>'
+if (!html.includes(empty)) throw new Error('dist/index.html has no empty #root to prerender into')
+await writeFile(page, html.replace(empty, `<div id="root">${render()}</div>`))
+await rm(server, { recursive: true, force: true })

{jira_cli_toolkit-2.5.1rc1 → jira_cli_toolkit-2.5.2}/web/src/App.css

@@ -109,3 +109,8 @@ body { -webkit-font-smoothing: antialiased; }
 /* The logo's green; dark text keeps it readable in both themes. */
 .brand-button { background: #4ade80; color: #0a0a0a; }
 .brand-button:hover { background: #22c55e; }
+
+/* Install panels stack in one cell; hidden ones keep their space but can't be seen, focused or read. */
+.install-panels { display: grid; grid-template-columns: minmax(0, 1fr); }
+.install-panels > * { grid-area: 1 / 1; }
+.install-panels > [hidden] { display: block; visibility: hidden; }

{jira_cli_toolkit-2.5.1rc1 → jira_cli_toolkit-2.5.2}/web/src/App.tsx

@@ -1,4 +1,4 @@
-import { Fragment, useMemo, useRef, useState } from 'react'
+import { Fragment, useEffect, useMemo, useRef, useState } from 'react'
 import { ArrowRight, Check, ChevronRight, Copy, CornerDownLeft, Play, Search } from 'lucide-react'
 import { buttonVariants } from '@/components/ui/button'
 import { Input } from '@/components/ui/input'
@@ -120,7 +120,9 @@ function CopyButton({ text, label, done = 'Command copied to clipboard.' }: { te
 }
 
 function Install() {
-  const [os, setOS] = useState<OS>(() => /Win/i.test(navigator.userAgent) ? 'windows' : /Linux/i.test(navigator.userAgent) ? 'linux' : 'macos')
+  // The page is prerendered for macOS, then switches to the visitor's system once it hydrates.
+  const [os, setOS] = useState<OS>('macos')
+  useEffect(() => setOS(/Win/i.test(navigator.userAgent) ? 'windows' : /Linux/i.test(navigator.userAgent) ? 'linux' : 'macos'), [])
   return <section id="get-started" aria-labelledby="install-title" className="rounded-xl border bg-card p-4 shadow-xs sm:p-5">
     <Tabs value={os} onValueChange={value => setOS(value as OS)} className="gap-3">
       <div className="flex flex-wrap items-center justify-between gap-3">
@@ -129,7 +131,9 @@ function Install() {
           {(Object.keys(platforms) as OS[]).map(key => <TabsTrigger key={key} value={key} className="px-3">{platforms[key].name}</TabsTrigger>)}
         </TabsList>
       </div>
-      {(Object.keys(platforms) as OS[]).map(key => <TabsContent value={key} key={key}>
+      {/* All panels share one grid cell, so the card keeps its height whichever system is chosen. */}
+      <div className="install-panels">
+      {(Object.keys(platforms) as OS[]).map(key => <TabsContent value={key} key={key} keepMounted>
         {/* Each line gets a prompt drawn by CSS, so the copied and displayed text stay identical. */}
         <div className="install-code relative rounded-lg border border-[#262626] bg-[#0a0a0a] text-[#ededed]">
           <pre tabIndex={0} data-prompt={platforms[key].shell === 'PowerShell' ? 'PS>' : '$'} aria-label={`${platforms[key].shell} command`}
@@ -138,6 +142,7 @@ function Install() {
         </div>
         <p className="mt-2.5 text-[13px] text-muted-foreground">{platforms[key].note} The installer verifies release checksums first.</p>
       </TabsContent>)}
+      </div>
     </Tabs>
     <p className="mt-3 flex flex-wrap gap-x-5 gap-y-1 text-sm">
       <a {...external} className="link" href={latest}>Prefer a manual install?</a>
@@ -229,8 +234,9 @@ function UseCases({ onPlay, playing }: { onPlay: (id: ScenarioId) => void; playi
             <ul className="flex flex-wrap gap-1.5">{u.commands.map(c => <li key={c} className="max-w-full"><code className="inline-code">{c}</code></li>)}</ul>
           </div>
         </div>
-        <button type="button" className={cn(buttonVariants(), 'mt-6 gap-2')} onClick={() => onPlay(u.id)} data-active={playing === u.id} aria-label={`Play the ${u.persona.toLowerCase()} replay in the sandbox`}>
-          <Play className="size-4" aria-hidden="true" />{playing === u.id ? 'Replaying…' : 'Play again in the sandbox'}
+        <button type="button" className={cn(buttonVariants(), 'mt-6 gap-2')} onClick={() => onPlay(u.id)} data-active={playing === u.id}>
+          {/* Accessible names start with the visible text, so voice control can target what people see. */}
+          <Play className="size-4" aria-hidden="true" />{playing === u.id ? 'Replaying…' : 'Play again in the sandbox'}<span className="sr-only">: {u.persona.toLowerCase()}</span>
         </button>
         {u.id === 'merge' && <div className="mt-8">
           <p className="mb-3 text-sm text-muted-foreground">No agent in the loop? The same two commands run from CI after every merge.</p>
@@ -335,10 +341,10 @@ function App() {
     <AsciiField />
     <header className="sticky top-0 z-30 border-b bg-background/80 backdrop-blur-md">
       <div className="mx-auto flex h-14 max-w-[1440px] items-center gap-3 px-3 sm:gap-6 sm:px-6">
-        <a className="flex items-center gap-2 whitespace-nowrap" href="#" aria-label="CLI Toolkit for Jira home">
+        <a className="flex items-center gap-2 whitespace-nowrap" href="#">
           <BrandMark />
-          <span className="font-semibold tracking-tight">CLI Toolkit</span>
-          <span className="text-sm text-muted-foreground">for Jira</span>
+          <span className="font-semibold tracking-tight">CLI Toolkit</span>{' '}
+          <span className="text-sm text-muted-foreground">for Jira</span><span className="sr-only"> home</span>
         </a>
         <nav aria-label="Main navigation" className="hidden items-center gap-5 text-sm text-muted-foreground md:flex">
           <a className="hover:text-foreground" href="#use-cases">Use cases</a>
@@ -391,10 +397,10 @@ function App() {
             <span className="example-label">The sandbox terminal runs on sample data from an example site. Nothing reaches Jira.</span> Pick a command, or type your own.
           </SectionHead>
           <ul className="divide-y overflow-hidden rounded-xl border">{examples.map(e => <li key={e.command}>
-            <button type="button" onClick={() => run(e.command)} data-active={active === e.command} aria-label={`Run ${e.command}`}
+            <button type="button" onClick={() => run(e.command)} data-active={active === e.command}
               className="group flex w-full items-center gap-4 px-4 py-3 text-left transition-colors hover:bg-muted/60 focus-visible:bg-muted/60 focus-visible:outline-none data-[active=true]:bg-muted">
               <span className="min-w-0 flex-1">
-                <code className="block font-mono text-[13px] font-medium break-words">{e.command}</code>
+                <span className="sr-only">Run </span><code className="block font-mono text-[13px] font-medium break-words">{e.command}</code>{' '}
                 <span className="block text-sm text-muted-foreground">{e.does}</span>
               </span>
               <Kbd className="opacity-60 group-hover:opacity-100 group-data-[active=true]:opacity-100"><CornerDownLeft aria-hidden="true" /></Kbd>