graphban-cli 0.1.0__tar.gz

graphban_cli-0.1.0/.gitignore

@@ -0,0 +1,62 @@
+# Python
+__pycache__/
+*.py[cod]
+backend/.venv/
+backend/*.db
+backend/.pytest.db
+# Bare too: pytest writes it to whatever directory it is invoked from, and a 0.7 MB
+# SQLite file reached main from the repo ROOT, where the backend-scoped line above
+# did not cover it (GRPH-428's branch, merged as #267). It fails
+# `test_no_tracked_control_bytes` on main and therefore on every PR built against it.
+.pytest.db
+.pytest.db-journal
+# The concurrency lock GRPH-554 added sits beside the database it guards, and xdist gives
+# each worker its own — so the pattern has to cover `.pytest_gw3.db.lock` as well as the
+# bare one. Untracked litter in `git status` is how a real change gets missed in the noise.
+*.db.lock
+# Same trap, same fix: scripts/docs_completeness.py opens a throwaway SQLite
+# database in whatever directory it is run from (GRPH-475).
+.docscheck.db
+.docscheck.db-journal
+backend/.pytest_cache/
+# graphban-fleet is a separate distribution with its own venv (PRD-22 D-e). `uv` drops a
+# self-ignoring .gitignore inside .venv/, but naming it here means the repo does not
+# depend on that convenience holding.
+fleet/.venv/
+fleet/.pytest_cache/
+*.egg-info/
+
+# Node
+web/node_modules/
+web/dist/
+web/.vite/
+web/*.tsbuildinfo
+
+# Env
+.env
+.env.local
+
+# Drive sync target (runtime data / mounted volume)
+sync/
+
+# Compose apply helper socket dir (docker-compose default mount)
+.graphban-apply/
+
+# Packed native/GitHub release trees (scripts/graphban_release.py publish)
+dist-release/
+
+# OS / editor
+.DS_Store
+
+# Tooling
+.serena/
+
+# Cursor MCP config — holds a real API key; copy .cursor/mcp.json.example instead
+.cursor/mcp.json
+
+# Project MCP config — holds a real API key
+.mcp.json
+
+# Cursor claim manifest — per-session runtime state (see .cursor/hooks/README.md)
+.cursor/graphban-claim.json
+.cursor/agentledger-claim.json

graphban_cli-0.1.0/LICENSE

@@ -0,0 +1,201 @@
+                              Apache License
+                        Version 2.0, January 2004
+                     http://www.apache.org/licenses/
+
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+1. Definitions.
+
+   "License" shall mean the terms and conditions for use, reproduction,
+   and distribution as defined by Sections 1 through 9 of this document.
+
+   "Licensor" shall mean the copyright owner or entity authorized by
+   the copyright owner that is granting the License.
+
+   "Legal Entity" shall mean the union of the acting entity and all
+   other entities that control, are controlled by, or are under common
+   control with that entity. For the purposes of this definition,
+   "control" means (i) the power, direct or indirect, to cause the
+   direction or management of such entity, whether by contract or
+   otherwise, or (ii) ownership of fifty percent (50%) or more of the
+   outstanding shares, or (iii) beneficial ownership of such entity.
+
+   "You" (or "Your") shall mean an individual or Legal Entity
+   exercising permissions granted by this License.
+
+   "Source" form shall mean the preferred form for making modifications,
+   including but not limited to software source code, documentation
+   source, and configuration files.
+
+   "Object" form shall mean any form resulting from mechanical
+   transformation or translation of a Source form, including but
+   not limited to compiled object code, generated documentation,
+   and conversions to other media types.
+
+   "Work" shall mean the work of authorship, whether in Source or
+   Object form, made available under the License, as indicated by a
+   copyright notice that is included in or attached to the work
+   (an example is provided in the Appendix below).
+
+   "Derivative Works" shall mean any work, whether in Source or Object
+   form, that is based on (or derived from) the Work and for which the
+   editorial revisions, annotations, elaborations, or other modifications
+   represent, as a whole, an original work of authorship. For the purposes
+   of this License, Derivative Works shall not include works that remain
+   separable from, or merely link (or bind by name) to the interfaces of,
+   the Work and Derivative Works thereof.
+
+   "Contribution" shall mean any work of authorship, including
+   the original version of the Work and any modifications or additions
+   to that Work or Derivative Works thereof, that is intentionally
+   submitted to Licensor for inclusion in the Work by the copyright owner
+   or by an individual or Legal Entity authorized to submit on behalf of
+   the copyright owner. For the purposes of this definition, "submitted"
+   means any form of electronic, verbal, or written communication sent
+   to the Licensor or its representatives, including but not limited to
+   communication on electronic mailing lists, source code control systems,
+   and issue tracking systems that are managed by, or on behalf of, the
+   Licensor for the purpose of discussing and improving the Work, but
+   excluding communication that is conspicuously marked or otherwise
+   designated in writing by the copyright owner as "Not a Contribution."
+
+   "Contributor" shall mean Licensor and any individual or Legal Entity
+   on behalf of whom a Contribution has been received by Licensor and
+   subsequently incorporated within the Work.
+
+2. Grant of Copyright License. Subject to the terms and conditions of
+   this License, each Contributor hereby grants to You a perpetual,
+   worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+   copyright license to reproduce, prepare Derivative Works of,
+   publicly display, publicly perform, sublicense, and distribute the
+   Work and such Derivative Works in Source or Object form.
+
+3. Grant of Patent License. Subject to the terms and conditions of
+   this License, each Contributor hereby grants to You a perpetual,
+   worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+   (except as stated in this section) patent license to make, have made,
+   use, offer to sell, sell, import, and otherwise transfer the Work,
+   where such license applies only to those patent claims licensable
+   by such Contributor that are necessarily infringed by their
+   Contribution(s) alone or by combination of their Contribution(s)
+   with the Work to which such Contribution(s) was submitted. If You
+   institute patent litigation against any entity (including a
+   cross-claim or counterclaim in a lawsuit) alleging that the Work
+   or a Contribution incorporated within the Work constitutes direct
+   or contributory patent infringement, then any patent licenses
+   granted to You under this License for that Work shall terminate
+   as of the date such litigation is filed.
+
+4. Redistribution. You may reproduce and distribute copies of the
+   Work or Derivative Works thereof in any medium, with or without
+   modifications, and in Source or Object form, provided that You
+   meet the following conditions:
+
+   (a) You must give any other recipients of the Work or
+       Derivative Works a copy of this License; and
+
+   (b) You must cause any modified files to carry prominent notices
+       stating that You changed the files; and
+
+   (c) You must retain, in the Source form of any Derivative Works
+       that You distribute, all copyright, patent, trademark, and
+       attribution notices from the Source form of the Work,
+       excluding those notices that do not pertain to any part of
+       the Derivative Works; and
+
+   (d) If the Work includes a "NOTICE" text file as part of its
+       distribution, then any Derivative Works that You distribute must
+       include a readable copy of the attribution notices contained
+       within such NOTICE file, excluding those notices that do not
+       pertain to any part of the Derivative Works, in at least one
+       of the following places: within a NOTICE text file distributed
+       as part of the Derivative Works; within the Source form or
+       documentation, if provided along with the Derivative Works; or,
+       within a display generated by the Derivative Works, if and
+       wherever such third-party notices normally appear. The contents
+       of the NOTICE file are for informational purposes only and
+       do not modify the License. You may add Your own attribution
+       notices within Derivative Works that You distribute, alongside
+       or as an addendum to the NOTICE text from the Work, provided
+       that such additional attribution notices cannot be construed
+       as modifying the License.
+
+   You may add Your own copyright statement to Your modifications and
+   may provide additional or different license terms and conditions
+   for use, reproduction, or distribution of Your modifications, or
+   for any such Derivative Works as a whole, provided Your use,
+   reproduction, and distribution of the Work otherwise complies with
+   the conditions stated in this License.
+
+5. Submission of Contributions. Unless You explicitly state otherwise,
+   any Contribution intentionally submitted for inclusion in the Work
+   by You to the Licensor shall be under the terms and conditions of
+   this License, without any additional terms or conditions.
+   Notwithstanding the above, nothing herein shall supersede or modify
+   the terms of any separate license agreement you may have executed
+   with Licensor regarding such Contributions.
+
+6. Trademarks. This License does not grant permission to use the trade
+   names, trademarks, service marks, or product names of the Licensor,
+   except as required for reasonable and customary use in describing the
+   origin of the Work and reproducing the content of the NOTICE file.
+
+7. Disclaimer of Warranty. Unless required by applicable law or
+   agreed to in writing, Licensor provides the Work (and each
+   Contributor provides its Contributions) on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+   implied, including, without limitation, any warranties or conditions
+   of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+   PARTICULAR PURPOSE. You are solely responsible for determining the
+   appropriateness of using or redistributing the Work and assume any
+   risks associated with Your exercise of permissions under this License.
+
+8. Limitation of Liability. In no event and under no legal theory,
+   whether in tort (including negligence), contract, or otherwise,
+   unless required by applicable law (such as deliberate and grossly
+   negligent acts) or agreed to in writing, shall any Contributor be
+   liable to You for damages, including any direct, indirect, special,
+   incidental, or consequential damages of any character arising as a
+   result of this License or out of the use or inability to use the
+   Work (including but not limited to damages for loss of goodwill,
+   work stoppage, computer failure or malfunction, or any and all
+   other commercial damages or losses), even if such Contributor
+   has been advised of the possibility of such damages.
+
+9. Accepting Warranty or Additional Liability. While redistributing
+   the Work or Derivative Works thereof, You may choose to offer,
+   and charge a fee for, acceptance of support, warranty, indemnity,
+   or other liability obligations and/or rights consistent with this
+   License. However, in accepting such obligations, You may act only
+   on Your own behalf and on Your sole responsibility, not on behalf
+   of any other Contributor, and only if You agree to indemnify,
+   defend, and hold each Contributor harmless for any liability
+   incurred by, or claims asserted against, such Contributor by reason
+   of your accepting any such warranty or additional liability.
+
+END OF TERMS AND CONDITIONS
+
+APPENDIX: How to apply the Apache License to your work.
+
+   To apply the Apache License to your work, attach the following
+   boilerplate notice, with the fields enclosed by brackets "[]"
+   replaced with your own identifying information. (Don't include
+   the brackets!)  The text should be enclosed in the appropriate
+   comment syntax for the file format. We also recommend that a
+   file or class name and description of purpose be included on the
+   same "printed page" as the copyright notice for easier
+   identification within third-party archives.
+
+Copyright 2026 Ascme Labs
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.

graphban_cli-0.1.0/PKG-INFO

@@ -0,0 +1,135 @@
+Metadata-Version: 2.5
+Name: graphban-cli
+Version: 0.1.0
+Summary: gban — a Graphban client for the human at a terminal
+Project-URL: Homepage, https://github.com/asc-me/graphban
+Project-URL: Repository, https://github.com/asc-me/graphban
+Project-URL: Documentation, https://github.com/asc-me/graphban/blob/main/cli/README.md
+License-Expression: Apache-2.0
+License-File: LICENSE
+Requires-Python: >=3.12
+Provides-Extra: dev
+Requires-Dist: pytest-cov>=5.0; extra == 'dev'
+Requires-Dist: pytest>=8.0; extra == 'dev'
+Description-Content-Type: text/markdown
+
+# graphban-cli
+
+**`gban`** — the client for a human at a terminal.
+
+Five surfaces existed before this and none of them was for a person at a shell prompt:
+`graphban` talks to the database from inside the container, `gbfleet` supervises processes,
+`gbagent` is a spawned child, the web app is a browser, and `/api/mcp` is for agents. Issuing
+a seat, seeing why an agent is stuck, or re-tasking one meant opening a browser.
+
+Specified by [PRD-40](https://github.com/asc-me/graphban/blob/main/docs/prd-40-gb-cli.md).
+
+## Install
+
+Not on PyPI yet, so it installs from the repository. `uv tool install` puts it on your PATH
+in its own environment, which is what you want for a CLI:
+
+```bash
+uv tool install "git+https://github.com/asc-me/graphban.git#subdirectory=cli"
+```
+
+Add `gbfleet` too if you run waves — it is a separate package, and `gban fleet` hands off to it:
+
+```bash
+uv tool install "git+https://github.com/asc-me/graphban.git#subdirectory=fleet"
+```
+
+`uv tool update-shell` once, if uv says the bin directory is not on your PATH. Upgrade either
+with `uv tool upgrade graphban-cli` (or `--all`); reinstalling from the same URL also works,
+since the spec is a branch rather than a pin.
+
+With pip instead, into an environment you already have:
+
+```bash
+pip install "graphban-cli @ git+https://github.com/asc-me/graphban.git#subdirectory=cli"
+```
+
+`gban` pulls **nothing**: `client.py` is `urllib.request` throughout, and the install lands
+exactly one distribution. `gbfleet` brings httpx and its four transitive dependencies, which
+is why they are separate packages and not one.
+
+```bash
+gban login --server https://cloud.agentldgr.dev
+gban doctor                       # both halves: the ledger, and the local fleet
+gban agents                       # the roster, and why an agent is stuck
+gban agents role SA-A4 planner    # what used to need a browser
+gban seats issue worker worker planner                  # one entry per agent
+gban keys                                               # which key is that agent on
+gban fleet up --seats-file seats.txt --adapter claude   # hands off to gbfleet
+```
+
+`seats issue` takes **one role per agent, repeats included**, because that is the server's
+own shape: two agents on one seat share a session and cannot review each other. Each code is
+printed once and written nowhere — a CLI that helpfully saved them would invent a second
+credential at rest that no route and no test knows about.
+
+`agents` prints what an agent was **last refused, and why**. That line is the reason the verb
+exists: a roster saying "idle worker" for an agent being told no on every call it makes is
+what made the Super-Arc diagnosis take a database query.
+
+`agents role` re-tasks a live agent **within its credential's ceiling** and never past it. A
+role the key does not permit is the server's refusal, printed in the server's own words;
+widening a ceiling means minting a different credential, and keeping those two acts apart is
+the point of having a ceiling. It lands on the agent's next poll.
+
+## `gban login` wants a real terminal
+
+It refuses without one, rather than prompting. `getpass` falls back to a plain **echoing**
+read when it cannot turn echo off — it warns, but the warning arrives after the person has
+decided to type — so a login through a pipe, a heredoc or an editor's command runner would
+put the password in the scrollback. There is no non-interactive login yet (PRD-40 open
+question 2: an API key cannot reach the JWT routes, so CI would need a service session).
+
+## Why not `gb`
+
+Because `gb` is already `git branch` on a large share of developer machines, and **an alias
+beats a binary on `PATH`**. The deployed walk hit it on the very first command and got git's
+usage text; nothing inside the process can detect that, because by the time `gb` would have
+run, the alias did not.
+
+It is not one alias but a whole namespace. oh-my-zsh's git plugin — which is where most of
+these come from — defines sixteen `gb*` aliases and ten `grb*`, so `gb`, `gba`, `grb` and
+`gbl` are all spoken for. `gban` is outside it, still short, and still says which product it
+belongs to.
+
+## Licence — Apache-2.0, deliberately not the repository's FSL-1.1
+
+The repository is [FSL-1.1-Apache-2.0](https://github.com/asc-me/graphban/blob/main/LICENSE.md). This directory is
+[Apache-2.0](https://github.com/asc-me/graphban/blob/main/cli/LICENSE), for the reasons PRD-22 §8 gives for `fleet/` — every one of which
+applies here identically. `gban` is inert without a Graphban server and holds no authority of
+its own, so FSL's Competing Use clause protects the server and protects nothing here. It is a
+laptop-installed developer CLI, which is exactly the kind of dependency that has to clear a
+corporate licence policy scanner.
+
+## Why it is in this repository
+
+**Not a second repository**, for the reason [`fleet/README.md`](https://github.com/asc-me/graphban/blob/main/fleet/README.md) gives for
+the supervisor, with more force: the client↔server contract has no schema anywhere, and a
+cross-repo break would present as absence reading clean — `gban` still runs, nothing errors, the
+verb quietly stops meaning what it said. The evidence is recent and specific: `ROLES` lost
+`reviewer` in one PR while another added a test naming it, and CI caught the pair inside
+seventeen minutes because both lived in one repository. Split across two, that lands as a bug
+report from somebody whose `gban agents role ... reviewer` started refusing.
+
+**Not inside `backend/`**, because `graphban-api` pulls fastapi, sqlalchemy, pgvector, psycopg,
+alembic, redis and cryptography, and this installs on a laptop. `tests/test_packaging.py`
+derives its forbidden set from the backend's own dependency list rather than a denylist
+somebody maintains.
+
+## What it is not
+
+It is **not a second web app**: no board, no PRD editor, no search. Every verb is either
+something a human currently opens a browser for, or a diagnosis nothing else gives.
+
+It is **not `graphban`**, which talks to the local database from inside the container and
+stays exactly as it is. Mixing "against the DB in the container" and "over HTTP from a laptop"
+into one command is an ambiguity that ends with somebody purging the wrong instance.
+
+It **holds no state the server does not** and computes nothing the server computes. Every verb
+is one endpoint, called once (PRD-40 D11); an ordering between two calls would be a rule, and
+a rule in the client is a second definition of something the server already enforces.

graphban_cli-0.1.0/README.md

@@ -0,0 +1,120 @@
+# graphban-cli
+
+**`gban`** — the client for a human at a terminal.
+
+Five surfaces existed before this and none of them was for a person at a shell prompt:
+`graphban` talks to the database from inside the container, `gbfleet` supervises processes,
+`gbagent` is a spawned child, the web app is a browser, and `/api/mcp` is for agents. Issuing
+a seat, seeing why an agent is stuck, or re-tasking one meant opening a browser.
+
+Specified by [PRD-40](https://github.com/asc-me/graphban/blob/main/docs/prd-40-gb-cli.md).
+
+## Install
+
+Not on PyPI yet, so it installs from the repository. `uv tool install` puts it on your PATH
+in its own environment, which is what you want for a CLI:
+
+```bash
+uv tool install "git+https://github.com/asc-me/graphban.git#subdirectory=cli"
+```
+
+Add `gbfleet` too if you run waves — it is a separate package, and `gban fleet` hands off to it:
+
+```bash
+uv tool install "git+https://github.com/asc-me/graphban.git#subdirectory=fleet"
+```
+
+`uv tool update-shell` once, if uv says the bin directory is not on your PATH. Upgrade either
+with `uv tool upgrade graphban-cli` (or `--all`); reinstalling from the same URL also works,
+since the spec is a branch rather than a pin.
+
+With pip instead, into an environment you already have:
+
+```bash
+pip install "graphban-cli @ git+https://github.com/asc-me/graphban.git#subdirectory=cli"
+```
+
+`gban` pulls **nothing**: `client.py` is `urllib.request` throughout, and the install lands
+exactly one distribution. `gbfleet` brings httpx and its four transitive dependencies, which
+is why they are separate packages and not one.
+
+```bash
+gban login --server https://cloud.agentldgr.dev
+gban doctor                       # both halves: the ledger, and the local fleet
+gban agents                       # the roster, and why an agent is stuck
+gban agents role SA-A4 planner    # what used to need a browser
+gban seats issue worker worker planner                  # one entry per agent
+gban keys                                               # which key is that agent on
+gban fleet up --seats-file seats.txt --adapter claude   # hands off to gbfleet
+```
+
+`seats issue` takes **one role per agent, repeats included**, because that is the server's
+own shape: two agents on one seat share a session and cannot review each other. Each code is
+printed once and written nowhere — a CLI that helpfully saved them would invent a second
+credential at rest that no route and no test knows about.
+
+`agents` prints what an agent was **last refused, and why**. That line is the reason the verb
+exists: a roster saying "idle worker" for an agent being told no on every call it makes is
+what made the Super-Arc diagnosis take a database query.
+
+`agents role` re-tasks a live agent **within its credential's ceiling** and never past it. A
+role the key does not permit is the server's refusal, printed in the server's own words;
+widening a ceiling means minting a different credential, and keeping those two acts apart is
+the point of having a ceiling. It lands on the agent's next poll.
+
+## `gban login` wants a real terminal
+
+It refuses without one, rather than prompting. `getpass` falls back to a plain **echoing**
+read when it cannot turn echo off — it warns, but the warning arrives after the person has
+decided to type — so a login through a pipe, a heredoc or an editor's command runner would
+put the password in the scrollback. There is no non-interactive login yet (PRD-40 open
+question 2: an API key cannot reach the JWT routes, so CI would need a service session).
+
+## Why not `gb`
+
+Because `gb` is already `git branch` on a large share of developer machines, and **an alias
+beats a binary on `PATH`**. The deployed walk hit it on the very first command and got git's
+usage text; nothing inside the process can detect that, because by the time `gb` would have
+run, the alias did not.
+
+It is not one alias but a whole namespace. oh-my-zsh's git plugin — which is where most of
+these come from — defines sixteen `gb*` aliases and ten `grb*`, so `gb`, `gba`, `grb` and
+`gbl` are all spoken for. `gban` is outside it, still short, and still says which product it
+belongs to.
+
+## Licence — Apache-2.0, deliberately not the repository's FSL-1.1
+
+The repository is [FSL-1.1-Apache-2.0](https://github.com/asc-me/graphban/blob/main/LICENSE.md). This directory is
+[Apache-2.0](https://github.com/asc-me/graphban/blob/main/cli/LICENSE), for the reasons PRD-22 §8 gives for `fleet/` — every one of which
+applies here identically. `gban` is inert without a Graphban server and holds no authority of
+its own, so FSL's Competing Use clause protects the server and protects nothing here. It is a
+laptop-installed developer CLI, which is exactly the kind of dependency that has to clear a
+corporate licence policy scanner.
+
+## Why it is in this repository
+
+**Not a second repository**, for the reason [`fleet/README.md`](https://github.com/asc-me/graphban/blob/main/fleet/README.md) gives for
+the supervisor, with more force: the client↔server contract has no schema anywhere, and a
+cross-repo break would present as absence reading clean — `gban` still runs, nothing errors, the
+verb quietly stops meaning what it said. The evidence is recent and specific: `ROLES` lost
+`reviewer` in one PR while another added a test naming it, and CI caught the pair inside
+seventeen minutes because both lived in one repository. Split across two, that lands as a bug
+report from somebody whose `gban agents role ... reviewer` started refusing.
+
+**Not inside `backend/`**, because `graphban-api` pulls fastapi, sqlalchemy, pgvector, psycopg,
+alembic, redis and cryptography, and this installs on a laptop. `tests/test_packaging.py`
+derives its forbidden set from the backend's own dependency list rather than a denylist
+somebody maintains.
+
+## What it is not
+
+It is **not a second web app**: no board, no PRD editor, no search. Every verb is either
+something a human currently opens a browser for, or a diagnosis nothing else gives.
+
+It is **not `graphban`**, which talks to the local database from inside the container and
+stays exactly as it is. Mixing "against the DB in the container" and "over HTTP from a laptop"
+into one command is an ambiguity that ends with somebody purging the wrong instance.
+
+It **holds no state the server does not** and computes nothing the server computes. Every verb
+is one endpoint, called once (PRD-40 D11); an ordering between two calls would be a rule, and
+a rule in the client is a second definition of something the server already enforces.

graphban_cli-0.1.0/pyproject.toml

@@ -0,0 +1,45 @@
+[project]
+name = "graphban-cli"
+version = "0.1.0"
+description = "gban — a Graphban client for the human at a terminal"
+readme = "README.md"
+requires-python = ">=3.12"
+# Apache-2.0, deliberately not the repository's FSL-1.1, for the reasons PRD-22 §8 gives for
+# `fleet/` — every one of which applies here identically. `gban` is inert without a Graphban
+# server and holds no authority of its own, so FSL's Competing Use clause protects the server
+# and protects nothing in this directory. It is also a laptop-installed developer CLI, which
+# is precisely the kind of dependency that has to clear a corporate licence policy scanner.
+license = "Apache-2.0"
+license-files = ["LICENSE"]
+
+# PRD-40 D1/D2: HTTP-only, and that is a REQUIREMENT rather than a preference. `graphban-api`
+# pulls fastapi, sqlalchemy, pgvector, psycopg, alembic, redis and cryptography, and this
+# installs on a laptop. `tests/test_packaging.py` derives the forbidden set from the backend's
+# own list, the way `fleet/` already does, because the only thing keeping a dependency list
+# thin is something that objects when it is not.
+dependencies = []  # stdlib only: client.py is urllib.request throughout (GRPH-782)
+
+[project.urls]
+# So the PyPI page links back. Without these it is a name, a summary and nothing to check.
+Homepage = "https://github.com/asc-me/graphban"
+Repository = "https://github.com/asc-me/graphban"
+Documentation = "https://github.com/asc-me/graphban/blob/main/cli/README.md"
+
+[project.scripts]
+# `graphban` and `agentledger` are claimed by backend/, `gbfleet` and `gbagent` by fleet/.
+# `gban` is short because it is the one a person types constantly.
+gban = "gban.cli:main"
+
+[project.optional-dependencies]
+dev = ["pytest>=8.0", "pytest-cov>=5.0"]
+
+[build-system]
+requires = ["hatchling"]
+build-backend = "hatchling.build"
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/gban"]
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]
+pythonpath = ["src", "tests"]