callai-cli 0.9.0__tar.gz

callai_cli-0.9.0/.python-version

@@ -0,0 +1 @@
+3.11

callai_cli-0.9.0/CHANGELOG.md

@@ -0,0 +1,265 @@
+# Changelog
+
+All notable changes to callai are documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [Unreleased]
+
+### Added
+
+- The banner shows both install commands (`pip install callai-cli`, `uv tool install callai-cli`), in one box
+  (option A, default) or as stacked chips (option B). See
+  [`src/tools/banner/CHANGELOG.md`](src/tools/banner/CHANGELOG.md).
+
+## [0.9.0] - 2026-11-04
+
+### Changed
+
+- `callai.__version__` comes from the installed `callai-cli` metadata, so `pyproject.toml` is the only place
+  the version is written. A source tree that isn't installed reports `0.0.0+unknown`; run
+  `uv sync --extra test --extra dev` after cloning.
+- Tests run on GitHub only on pushes to `master`, on manual dispatch, and on pull requests labelled
+  `ci::run-tests` (`run-tests-on-label.yml` calls `tests.yml`).
+- uv ignores packages released in the last 5 days (`[tool.uv] exclude-newer = "5 days"`).
+- callai now lives in its own repository, [sugatoray/callai](https://github.com/sugatoray/callai), imported
+  from `sugatoray/devx` (`src/experiments/expt_callai`) at 0.8.0. Paths and links in the docs, the HTML docs
+  builder and the project notes point at this repository; `pyproject.toml` gains `[project.urls]`.
+
+### Added
+
+- `make docs.html` header: a GitHub button (links to https://github.com/sugatoray/callai, no branch) next to the
+  light/dark toggle, and a magnifying-glass icon in the search box. On phones the icon replaces the
+  "Search the docs" placeholder text, which no longer fits.
+- `make docs.html` opens the landing page with the project banner: its HTML and CSS, without the editing
+  features, copied from `src/tools/banner/callai-banner.html` and scaled to the column width (live text, not an
+  image; the page stays at about 190 KB). `build_docs_html.py --banner PATH` picks another banner page, and
+  `--no-banner` leaves it out.
+- Packaging through uv: `make pkg.build` (sdist + wheel in `dist/`), `make pkg.publish` (needs
+  `UV_PUBLISH_TOKEN`; `PUBLISH_URL` for TestPyPI), and `make pkg.install.e`, `pkg.install.local` and
+  `pkg.install.pypi`. `MANIFEST.in` lists what the sdist ships. The wheel ships `py.typed`, and
+  `pyproject.toml` has more PyPI classifiers, including `Typing :: Typed`. `.editorconfig` added.
+- The docs are published on GitHub Pages: `.github/workflows/docs.yml` builds `make docs.html` and deploys it
+  on pushes to `master` that touch the docs, or by hand on any branch.
+- Agent skills for contributors (scrolls memory, `create-lib-docs`, `create-issues-update-pr`) from
+  [sugatoray/aiskills](https://github.com/sugatoray/aiskills), installed in `.agents/skills/` and pinned in
+  `skills-lock.json`.
+- A maintainer tool that builds the callai-cli banner (`make maint.banner`); see
+  [`src/tools/banner/CHANGELOG.md`](src/tools/banner/CHANGELOG.md). It is not packaged.
+- Tested on Python 3.11, 3.12, 3.13 and 3.14. `make test.matrix` runs the suite once per version, each in an
+  isolated environment that uv creates (set `PYTHON_VERSIONS` to choose); `make test` runs it on the
+  development Python, now pinned to 3.11 in `.python-version`. A GitHub Actions workflow
+  (`.github/workflows/tests.yml`) runs the same matrix plus ruff and interrogate. `pyproject.toml` lists the four versions as classifiers; `requires-python` stays
+  `>=3.11` (no upper cap).
+
+### Fixed
+
+- `test_old_tool_flag_is_gone` failed on Python 3.13, whose `--help` prints `-n, --name HARNESS_NAME`
+  instead of `-n HARNESS_NAME, --name HARNESS_NAME`. It now checks the parser's options directly. The
+  suite passes on 3.11 and 3.13.
+
+## [0.8.0] - 2026-11-01
+
+The docs as one HTML page. No changes to callai itself; nothing here breaks existing use.
+
+### Added
+
+- `make docs.html` bundles `docs/callai/` into one self-contained HTML page (`build/docs.html`): a tab per
+  docs section, a page list, an on-this-page outline, search, and a light/dark toggle. The builder and
+  template are in `docs/site/`; it fails if a page isn't linked from the docs' landing page.
+
+## [0.7.0] - 2026-11-01
+
+User documentation. No code changes; nothing here breaks existing use.
+
+### Added
+
+- User documentation in `docs/callai/` (32 pages), written with the `/create-lib-docs` skill (now published in [sugatoray/aiskills](https://github.com/sugatoray/aiskills)).
+  - **Sections:** Getting Started, an 8-step tutorial, 6 how-to guides, Concepts with a glossary,
+    a full reference (CLI, Python API, output formats, configuration, harnesses, every error message),
+    and a FAQ.
+  - **Diagrams:** 5 SVGs, each with a text equivalent.
+  - **For AI agents:** `llms.txt` and `llms-full.txt`.
+  - **Checks:** every example was run against the real harness CLIs connected to the stub model, and
+    the `--dry-run` examples are checked mechanically.
+
+## [0.6.0] - 2026-10-31
+
+Resume sessions, a Python API (`callai.run`), and fan-out to several harnesses with `-n a/b`, `-n a,b`
+or `-n all`. Nothing here breaks existing use.
+
+### Added
+
+- `--resume SESSION_ID` and `--continue`: continue a session (the `session_id` a run reported) or the
+  harness's most recent one, mapped to each harness's own flags (codex: `exec ... resume ID|--last`).
+  Checked with every harness against the stub model: the resumed request carries the earlier turns.
+  `--continue` is refused for hermes, which only continues its interactive sessions. No `-c` short
+  form, because `-c` is `--command`.
+- Python API: `callai.run(harness_name, prompt, *, model, cwd, timeout, permission, system_prompt,
+  extra_args, resume, continue_session, binary, on_event)` returns the `-o json` result; `on_event` gets
+  the `-o stream-json` events live. It reads no `CALLAI_*` variables or config file. `Result` and the
+  error classes are exported from `callai`. The CLI now runs harnesses through the same code.
+- Fan-out: `-n a/b/c` runs one prompt through several harnesses at the same time, `-n a,b,c` one after
+  another, `-n all` every installed harness at the same time. Everything is checked before anything
+  runs; `-n all` skips harnesses that refuse the options. Text output puts each answer under a
+  `== name ==` header, `-o json` gives `{"results": [...]}`, stream-json events carry `harness_name`.
+  One failure (or timeout) doesn't stop the others; the exit code is the first failure's; Ctrl-C
+  stops them all. `-o raw` and arguments after `--` need a single harness.
+
+## [0.5.0] - 2026-10-30
+
+`-o stream-json`: every harness's run as normalised JSON events, live. Nothing here breaks existing use.
+
+### Added
+
+- `-o stream-json`: one JSON event per line as the run happens: `start`, then `text`, `tool_use` and
+  `tool_result` mapped from each harness's own event stream, then `result` (the `-o json` object).
+  claude runs with `--output-format stream-json --verbose`, grok with `--output-format streaming-json`;
+  codex, opencode and pi already stream. hermes has no event stream, so it gives `start` and `result`.
+  Checked end to end with each harness (stub model, a real tool call) and live with claude.
+- `Adapter.stream_events(line, state)`, and `runner.run(on_stdout_line=...)` to see output as it arrives.
+- Conformance: `expected_events` in parse cases, `expected.stdout_events` in CLI cases, and
+  `stderr_file` for fake harnesses; 7 recorded stream fixtures and 5 CLI cases.
+
+### Fixed
+
+- Test fake harnesses write their call record atomically; a test polling for it could read it half-written.
+
+## [0.4.0] - 2026-10-30
+
+Adapters can set environment variables for the harness, so hermes now accepts `--system-prompt`.
+Nothing here breaks existing use.
+
+### Added
+
+- Adapters can set environment variables for the harness (`Adapter.build_env`, pure like
+  `build_argv`); they are added on top of callai's own environment.
+- hermes: `--system-prompt` now works, passed as `HERMES_EPHEMERAL_SYSTEM_PROMPT`. It was refused
+  before. Checked against hermes-agent 0.19.0 with the stub model: the text lands in the system message.
+- `--dry-run` shows those variables: as `NAME=value` before the command in text, and as an `"env"`
+  object in `-o json` (left out when there are none, so existing output is unchanged).
+- Conformance: `expected_env` in argv cases; `expected.harness_env` in CLI cases (the fake harness
+  now records its environment).
+
+## [0.3.0] - 2026-10-30
+
+Defaults from the environment and a config file, model aliases, and `--list-harnesses`. Nothing
+here breaks existing use.
+
+### Added
+
+- Config file `~/.config/callai/config.toml` (or `$XDG_CONFIG_HOME/callai/…`, or `CALLAI_CONFIG`):
+  `default_harness`, `model`, `timeout`, per-harness `binary` / `model` / `extra_args`, and model
+  aliases (`-m fast` → each harness's own model). Unknown keys are an error (exit 2).
+- `CALLAI_MODEL` and `CALLAI_TIMEOUT` environment defaults. Precedence: flag > `CALLAI_*` > config
+  file > built-in default.
+- `--list-harnesses`: each harness's binary, where it is on PATH and its version, or where to
+  install it (`-o json` for JSON).
+- Live smoke tests (`CALLAI_LIVE=all uv run pytest -m live`): each real harness answers a real model.
+- README: defaults and config file section.
+
+### Fixed
+
+- DESIGN.md said `--system-prompt` only warns where a harness lacks it; callai refuses it (exit 2).
+
+## [0.2.0] - 2026-10-30
+
+Names the harness consistently as `harness_name`, so it isn't confused with the harnesses' own
+`--tool(s)` flags or the tools a model calls. Every change below is breaking.
+
+### Changed
+
+- **Breaking:** the harness is chosen with `-n/--name HARNESS_NAME` instead of `-t/--tool`,
+  because several harnesses have their own `--tool`/`--tools` flags. `-t` and `--tool` are no
+  longer accepted (exit 2).
+- **Breaking:** the default-harness environment variable `CALLAI_TOOL` is now
+  `CALLAI_HARNESS_NAME`. A leftover `CALLAI_TOOL` is not used; if no harness is given, the usage
+  error says it was renamed.
+- **Breaking:** the `-o json` result key `tool` is now `harness_name` (same value, e.g.
+  `"claude-code"`). In the code, `Request.tool` and `Result.tool` are now `harness_name`, and the
+  conformance argv/parse cases name their harness in a `harness_name` field.
+- **Breaking:** `callai.adapters.TOOLS` is now `callai.adapters.HARNESS_NAMES`; usage errors say "harness"
+  (`unknown harness 'x'`, `no harness given: use -n/--name ...`).
+
+## [0.1.0] - 2026-10-30
+
+First release: `callai -t TOOL -p PROMPT` runs claude-code, codex, opencode, pi, grok and hermes.
+
+### Added
+
+- Initial scaffold copied from `expt_template`: `docs/` (with its own `docs/.scrolls/`
+  memory system), `.trash/`, and `src/`.
+- `docs/DESIGN.md`: design for the `callai` dispatcher CLI (CLI surface, adapter
+  architecture, normalised output, permissions, exit codes, test strategy).
+- `SCOPE.md`: language/distribution analysis and agreed roadmap (Python → TypeScript
+  port → optional Rust core with PyPI/npm thin wrappers).
+- `conformance/` language-agnostic test suite (argv, parse, CLI cases; recorded
+  claude fixtures) with a strict pytest loader in `src/tests/conformance.py`.
+- Python package skeleton: `pyproject.toml` (PyPI name `callai-cli`, Python ≥ 3.11,
+  stdlib-only), `callai --version`, `python -m callai`. Licensed Apache-2.0.
+- Core types: `Request`, `Completed`, `Result` (with the `-o json` schema), `UsageError`,
+  the `Adapter` base class and the tool registry.
+- `claude-code` adapter command line (`claude -p --output-format json … -- PROMPT`).
+- Full CLI (`-t`, `-p/-c/--prompt/--command`, `-m`, `-o text|json|raw`, `-C`, `--timeout`,
+  `--permission`, `--system-prompt`, `--dry-run`, `-v`, `--` passthrough, stdin prompts,
+  `CALLAI_TOOL`) and subprocess runner (process-group kill, exit codes 124/127/130).
+- `claude-code` output parsing: answer, error flag, session id, cost, token usage and the
+  model actually used, from `claude -p --output-format json`. **First working tool.**
+- `codex` adapter: `codex exec --json`, sandbox permission mapping, `--system-prompt` via
+  `developer_instructions`, JSONL event parsing.
+- `opencode` adapter: `opencode run --format json`, prompt passed so opencode doesn't quote it,
+  real error reasons from opencode's ERROR log, token/cost totals across steps. `read-only`/`auto`
+  permissions and `--system-prompt` are refused (opencode can't honour them).
+- `pi` adapter: `pi --mode json`, tool-allowlist permission mapping, `--system-prompt`,
+  model errors detected from `stopReason` (pi exits 0 on them), prompts starting with `@`
+  refused (pi would read them as files). Error text that the harness already printed on
+  stderr is no longer repeated.
+- `grok` adapter (xAI's Grok Build CLI): `grok --output-format json --single=PROMPT`, permission
+  mapping (read-only tools only / `--allow Write --allow Edit` / `bypassPermissions`),
+  `--system-prompt` via `--system-prompt-override`, token usage and the model actually used.
+  Prompts starting with `/` are refused (grok would run them as slash commands). A run where grok
+  refused a tool call (it cancels the turn but exits 0) or hit `--max-turns` is reported as a
+  failure, with grok's reason.
+- `hermes` adapter (Nous Research Hermes Agent): `hermes chat -Q --source tool --query=PROMPT`
+  (not `-z`, which approves every tool call), the answer separated from hermes's tool previews,
+  session id, `auto` = file tools only, `bypass` = `--yolo`. `read-only` and `--system-prompt` are
+  refused (hermes can't honour them from the command line). All six tools now work.
+- README usage section, with what each `--permission` level allows per harness.
+- `--permission bypass` prints a one-line warning on stderr before the harness runs.
+- Stub model speaks Anthropic Messages (`/v1/messages`, JSON and SSE, scripted `tool_use`), so the
+  permission probe covers claude-code too; its results are in DESIGN §7 and the README.
+- README caution: grok `auto`/`bypass` can write outside the working directory; how to opt in to
+  grok's `workspace` sandbox (needs bubblewrap on Linux), with examples.
+- Stub model `--tool-call`: scripts one tool call, so permission behaviour can be recorded.
+- `conformance/tools/permission_probe.py`: runs a harness at every `--permission` level with
+  scripted file-write and shell calls (inside and outside the working directory) and reports what
+  actually happened. Results are in DESIGN §7.
+- `Makefile`: `make install.harnesses` installs every supported harness CLI at its verified
+  version; `make install.<tool>` (claude-code, codex, opencode, pi, hermes, grok) installs one.
+- `conformance/tools/stub_llm_server.py`: local OpenAI-compatible model stub for recording
+  real harness output without network access.
+
+### Fixed
+
+- `callai -p TEXT` no longer hangs when stdin is a pipe that never closes (common when an agent
+  or script runs it): it waits 3 seconds for data (`CALLAI_STDIN_WAIT`), warns and runs with the
+  prompt alone, like `claude -p`. Usage errors are reported before stdin is read.
+- Harness output is captured byte-for-byte: `\r\n` line endings were translated to `\n`,
+  so `-o raw` wasn't the harness's real output.
+
+<!--
+## [x.y.z] - YYYY-MM-DD
+
+### Added
+- What was added, from a user's perspective.
+
+### Changed
+- What changed in existing behavior.
+
+### Fixed
+- What bug was fixed.
+
+### Removed
+- What was removed and why.
+-->

callai_cli-0.9.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 Sugato Ray
+
+   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.

callai_cli-0.9.0/MANIFEST.in

@@ -0,0 +1,21 @@
+include README.md
+include src/callai/py.typed  # marker file for PEP 561
+
+include CHANGELOG.md
+include LICENSE
+
+include MANIFEST.in
+include pyproject.toml
+include uv.lock
+include .python-version
+
+# Not listed on purpose: tests (src/tests), conformance/, docs/, build/, dist/, .github/, .agents/,
+# .claude/, Makefile, the agent/scrolls files. Without a VCS plugin (setuptools-scm) setuptools only
+# packs the files above plus the packages found in src/ (callai*), so they stay out of the sdist.
+# If a plugin is added later, restore `recursive-exclude` lines for them.
+
+# Maintainer tools (banner builder, its template, config and tests) never ship. Failsafe, kept on purpose:
+# setuptools doesn't pack src/tools today, so `uv build` warns "no previously-included ... matching";
+# these lines keep it out if a VCS plugin (setuptools-scm) or a package-find change ever pulls it in.
+prune src/tools
+recursive-exclude src/tools *