caokit 0.3.0.dev0__py3-none-any.whl

caokit-0.3.0.dev0.dist-info/METADATA

@@ -0,0 +1,382 @@
+Metadata-Version: 2.4
+Name: caokit
+Version: 0.3.0.dev0
+Summary: Chain-of-command agent company kit for CAO (cli-agent-orchestrator)
+Author: Armando Zubillaga
+License-Expression: MIT
+Project-URL: Homepage, https://github.com/ajzpiv97/cao-kit
+Project-URL: Repository, https://github.com/ajzpiv97/cao-kit
+Project-URL: Changelog, https://github.com/ajzpiv97/cao-kit/blob/main/CHANGELOG.md
+Project-URL: Issues, https://github.com/ajzpiv97/cao-kit/issues
+Keywords: ai-agents,multi-agent,agent-orchestration,claude-code,coding-agents,cli,tmux
+Classifier: Development Status :: 4 - Beta
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: MacOS
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Software Development
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Dynamic: license-file
+
+<p align="center">
+  <img src="https://raw.githubusercontent.com/ajzpiv97/cao-kit/main/docs/logo.svg" width="140" height="140" alt="caokit logo: a general's star above three double-chevron units"/>
+</p>
+
+<h1 align="center">caokit</h1>
+
+<p align="center">
+  <b>Command a swarm of coding agents from one terminal.</b>
+</p>
+
+<p align="center">
+  <a href="https://github.com/ajzpiv97/cao-kit/actions/workflows/ci.yml"><img src="https://github.com/ajzpiv97/cao-kit/actions/workflows/ci.yml/badge.svg?branch=main" alt="CI"/></a>
+  <a href="https://github.com/ajzpiv97/cao-kit/tags"><img src="https://img.shields.io/github/v/tag/ajzpiv97/cao-kit?label=version&color=blue" alt="Version"/></a>
+  <a href="https://github.com/ajzpiv97/cao-kit/blob/main/LICENSE"><img src="https://img.shields.io/badge/License-MIT-blue" alt="License: MIT"/></a>
+  <a href="https://github.com/ajzpiv97/cao-kit/blob/main/pyproject.toml"><img src="https://img.shields.io/badge/Python-3.11%2B-3776AB?logo=python&logoColor=white" alt="Python 3.11+"/></a>
+  <img src="https://img.shields.io/badge/Platform-macOS-lightgrey?logo=apple" alt="Platform: macOS"/>
+  <a href="https://github.com/awslabs/cli-agent-orchestrator"><img src="https://img.shields.io/badge/CAO-2.5.4-FF9900" alt="CAO 2.5.4"/></a>
+</p>
+
+You talk to **one** commanding agent, the *General* (Claude Code by default). It drafts task files,
+waits for your approval, then delegates to specialist coding-agent CLIs through
+[CAO](https://github.com/awslabs/cli-agent-orchestrator) (`cli-agent-orchestrator`).
+
+- **One agent to talk to.** The General takes the goal, writes the task file, dispatches an engineer,
+  a scout and an inspector, and reports back. You approve plans and accept results.
+- **Review comes from a different vendor.** Claude implements and Antigravity inspects Claude's code,
+  re-running the task's validation commands itself. caokit refuses a roster where author and reviewer
+  share a provider unless you opt in.
+- **Your subscriptions, your machine.** It drives the CLIs you already pay for, holds no credentials,
+  and no agent may merge, push or deploy. The human commits.
+
+**Get started.** Needs macOS, `tmux`, `uv`, CAO 2.5.4, `claude` and `agy` ([full install](#install)):
+
+```bash
+uv tool install git+https://github.com/ajzpiv97/cao-kit
+caokit doctor                  # checks CLIs, auth, CAO version and the server
+caokit company create          # pick a tool and model per role
+caokit install                 # install the profiles into CAO
+caokit init /path/to/repo      # scaffold .company/ in your project
+caokit server                  # terminal A: leave running
+caokit launch /path/to/repo    # terminal B: talk to the General
+```
+
+The kit is generic: it assumes no particular project, language or stack. A project brings its
+own validation commands (test/CI command) and its own rules.
+
+- **Platform:** macOS (Apple Silicon tested), tmux backend.
+- **CAO:** exactly **2.5.4**, installed with `uv tool`.
+- **Status:** validated end to end with a Claude + Antigravity roster (see [Validation](#validation)).
+
+**Contents:** [Install](#install) · [Quick start](#quick-start) · [Roles](#roles) ·
+[Task workflow](#task-workflow) · [Working with the General](#working-with-the-general) ·
+[Commands](#commands) · [Configuration](#configuration) · [Worktrees](#worktrees-one-per-task) ·
+[Safety model](#safety-model) · [Validation](#validation) · [Developing caokit](#developing-caokit)
+
+---
+
+## Install
+
+You need `git`, `tmux`, `uv`, `python3` (3.11+), CAO (`cao`, `cao-server`, `cao-mcp-server`),
+`claude` and `agy`.
+
+```bash
+brew install tmux uv
+uv tool install 'cli-agent-orchestrator==2.5.4'
+curl -fsSL https://claude.ai/install.sh | bash
+curl -fsSL https://antigravity.google/cli/install.sh | bash
+uv tool install git+https://github.com/ajzpiv97/cao-kit   # or, from a checkout: uv tool install --from . caokit
+caokit doctor                                             # CLIs, auth, CAO version, single CAO install, server, roster
+```
+
+- Log in to `claude` and `agy` **directly, outside CAO**, once (send one harmless prompt each), so
+  no login screen appears inside an orchestrated terminal. `agy models` lists the exact model IDs.
+- Change the CAO version only with `uv tool install --force 'cli-agent-orchestrator==X'`, never
+  `uv tool upgrade` or `cao update`.
+- After pulling new changes to a checkout, reinstall with `uv tool install --force --from . caokit`.
+
+## Quick start
+
+```bash
+caokit company create --general claude:sonnet --engineer claude:opus \
+    --scout antigravity:gemini-3.8-flash-medium --inspector antigravity:gemini-4-argon-high
+caokit install                         # render and install the profiles into CAO
+caokit init /path/to/repo              # scaffold .company/, ROSTER.md, merge .gitignore
+caokit server                          # terminal A: start cao-server (leave running)
+caokit launch /path/to/repo            # terminal B: start the General in this project
+```
+
+`caokit company create` with no role flags asks for a tool and model per role and offers the
+recommended one.
+
+For a hands-off smoke test instead of talking to the General, launch the scaffolded TASK-0001:
+
+```bash
+caokit launch /path/to/repo --headless --auto-approve --prompt-file /path/to/repo/.company/prompts/first-run.md
+caokit status /path/to/repo           # watch the workers
+```
+
+Expect artifacts under `.company/` (`artifacts/`, `research/`, `reviews/`, `decisions/`) and no
+application-source changes.
+
+## Roles
+
+| Role | Default tool | Job | Tool limits |
+|---|---|---|---|
+| `general` | Claude Code, `permissionMode: auto` | Single entry point: task intake, dispatch, acceptance procedure, synthesis | Native: no Bash, Agent/Task, Monitor, web. Read, list and write plus `cao-mcp-server` |
+| `engineer` | Claude Code | Implements; runs **only** the task's authorised validation commands | Web blocked. `execute_bash` also unlocks Claude's Agent/Task tools, so "no subagents" is instruction-only |
+| `scout` | Antigravity (`gemini-3.8-flash-medium`) | Research; does not build | Advisory only |
+| `inspector` | Antigravity (`gemini-4-argon-high`) | Independent review; re-runs the authorised commands | Advisory only |
+
+Why this split: **Claude implements, Antigravity inspects Claude's code.** Claude's tool limits are
+enforced natively by CAO. Antigravity's are **advisory**: CAO launches it with
+`--dangerously-skip-permissions`, so review must come from a different tool and model vendor than
+the author.
+
+Any role can be bound to any active tool (`caokit company create`). A soft-enforcement tool as
+`engineer` or `general` needs an explicit opt-in (see [Policy](#policy)) because nothing then stops
+it writing anywhere. Codex is parked (see [Parked: Codex](#parked-codex)).
+
+Keep `fs_write` in the General's profile. CAO's validator warns that it is "not recognised", but
+that is a gap in its own vocabulary check, and removing it would block the General's `.company/`
+writes.
+
+## Task workflow
+
+1. **Intake.** You state the goal. The General writes `.company/tasks/TASK-NNNN-<slug>.md` from the
+   template, then takes one of two paths:
+   - **Fast path**, for a clear task that needs at most two agents and meets no plan-path trigger:
+     the General records `APPROVED` under the pre-authorised rule and dispatches without stopping.
+     You review the output afterwards.
+   - **Plan path**, for anything else: `State: PROPOSED`, a Team plan with a per-agent cost
+     estimate, draft acceptance checks marked "human must confirm", then the General **stops** for
+     your approval. Triggers are auth or secrets, data deletion or migration, new dependencies,
+     anything external, ambiguity, or more than two agents. In Claude Code's plan mode approval is
+     always forced.
+2. **Approval.** Only your explicit approval moves a plan-path task to `APPROVED`, logged in
+   `DECISIONS.md`. You own the acceptance checks and the allowed-path review.
+3. **Clarification.** Workers ask the General with `send_message`; the General answers from the task
+   file and repository if it can, and otherwise asks you. It does not guess.
+4. **Authorised validation commands.** The engineer and inspector run exactly the commands the task
+   lists and nothing else (no `rm`/cleanup, installs, network, or state-changing git). Both write a
+   **Commands run** section with real output. The inspector re-runs the commands itself.
+5. **Acceptance procedure.** The General diffs every reported command against the allowlist and flags
+   extras as a **contract breach**. It never accepts silently.
+6. **Accept.** Only your "accept" moves a task to `ACCEPTED`. Then run `caokit tasks archive`.
+
+Task files are the audit trail. Contracts live in `.company/contracts/` and are tracked by git; the
+rest of `.company/` is git-ignored.
+
+## Working with the General
+
+- `caokit launch` **without** `--headless` attaches you to the General's Claude Code inside tmux.
+  Workers are other tmux windows: `Ctrl-b w` lists them, `Ctrl-b d` detaches (the session keeps running).
+- Web UI with live terminals: `http://127.0.0.1:9889/` (root path only). `cao tui` also exists.
+- **Don't type into the General while it is mid-turn.** Worker reports queue and are delivered when it
+  is idle. For check-ins use `caokit send "<msg>"`.
+- Session names get a `cao-` prefix (project `proja` becomes `cao-proja`).
+- Never use `cao launch --yolo` and never `allowedTools: ["*"]`: both bypass restrictions.
+
+## Commands
+
+Destructive commands (`uninstall`, `tasks prune`, `reset`) are dry runs unless you pass `--yes`.
+
+**Setup**
+
+| Command | Purpose |
+|---|---|
+| `caokit doctor` | Check CLIs, auth, CAO version, a single CAO install (uv tool only), the server and its web UI, and the roster |
+| `caokit company create [--general\|--engineer\|--scout\|--inspector TOOL[:MODEL]] [--force]` | Write `caokit.toml` (role to tool and model), with every guardrail checked; `--force` overwrites an existing file |
+| `caokit install [--project REPO]` | Render, validate, install and byte-verify profiles; `--replace-legacy` / `--remove-legacy` for old copies |
+| `caokit uninstall [--project REPO] [--yes]` | Remove a roster's profiles from CAO. Leftover `agent-context` copies are moved to a backup, not deleted |
+| `caokit init REPO [--name P] [--override ROLE=TOOL[:MODEL]] [--force-project]` | Scaffold `.company/` in a git repo; `--name` namespaces its profiles; `--force-project` overwrites an existing project file |
+| `caokit reset [--yes]` | Back up CAO's state, reinstall CAO 2.5.4 and the profiles |
+
+**Running a session**
+
+| Command | Purpose |
+|---|---|
+| `caokit server` | Run `cao-server` (tmux backend) in the foreground |
+| `caokit launch [REPO]` | Start the project's General; `--prompt-file F`, `--headless`, `--auto-approve`, `--async` |
+| `caokit status [REPO]` | Show sessions and workers |
+| `caokit send MESSAGE [--repo REPO] [--timeout S]` | Message the General (waits up to 600 s by default) |
+| `caokit stop [REPO]` | Shut the session down |
+
+**Tasks and worktrees**
+
+| Command | Purpose |
+|---|---|
+| `caokit tasks [list] [REPO]` | Open tasks and what blocks them (`--all` includes finished ones) |
+| `caokit tasks archive [REPO] [--delete]` | Move `ACCEPTED`, `CANCELLED` and `FAILED` tasks to `.company/tasks/archive/`; `--delete` removes them instead |
+| `caokit tasks policy [REPO] [--keep-archived-days N] [--worktrees on\|off]` | Set how long a project keeps archived tasks, and whether each task gets its own worktree |
+| `caokit tasks prune [REPO] [--days N] [--yes]` | Delete archived tasks older than the policy |
+| `caokit tasks schedule [REPO] [--install\|--remove] [--at HH:MM]` | Print, add or remove the daily cron entry that archives and prunes |
+| `caokit worktrees [REPO]` | List the `cao/*` task branches and checkouts, with unmerged commits |
+
+## Configuration
+
+Config lives in `~/.config/caokit/caokit.toml` (`$CAOKIT_HOME` or `--config` to override). Roles are
+tool-agnostic; concrete CAO profiles are named `<role>-<tool>` (CAO allows only `[A-Za-z0-9_-]`).
+
+### Per-project setups
+
+CAO's profile store is machine-global (profiles are not looked up in a project directory), so two
+projects sharing `engineer-claude` would overwrite each other's model. Give a project its own
+namespaced profiles:
+
+```bash
+caokit init ~/proj-a --name proja                          # same roster as the user-level config
+caokit init ~/proj-b --name projb --override engineer=:sonnet --override scout=claude:haiku
+caokit install --project ~/proj-a                          # installs proja_general-claude, proja_engineer-claude, ...
+caokit install --project ~/proj-b
+caokit launch ~/proj-a                                     # session cao-proja
+```
+
+- Two layers: the user-level `caokit.toml`, then the project's `.company/caokit.toml` (git-ignored) with a
+  `[project] name`, optional `[policy]`, `[tasks]`, and per-role `tool`/`model` overrides.
+- Override forms: `role=tool`, `role=tool:model`, `role=:model` (keep the tool). Changing a role's tool
+  without a model drops the user-level model (a model ID from one tool means nothing to another).
+- Names are `<project>_<role>-<tool>`; the project is 1-24 lowercase letters, digits or `-`.
+- All guardrails (cross-provider inspection, soft-tool opt-ins, model validation) re-run on the merged config.
+- Without `--name`, `init` uses shared `<role>-<tool>` profiles, and the session is named after the directory.
+- Each project is its own CAO session; one `cao-server` serves them all.
+- Remove a project's profiles with `caokit uninstall --project ~/proj-a --yes` (it touches only that project's names).
+
+### Policy
+
+| Setting | Where | Effect |
+|---|---|---|
+| `allow_soft_engineer` | `[policy]` / `--allow-soft-engineer` | Lets a soft-enforcement tool (Antigravity) be the engineer |
+| `allow_soft_general` | `[policy]` / `--allow-soft-general` | Lets a soft-enforcement tool be the General. CAO cannot deny its tools, so it could write anywhere and run commands. Prompt rules are all that hold it back |
+| `allow_single_provider` | `[policy]` / `--allow-single-provider` | Downgrades the cross-provider inspection rule to a warning |
+| `keep_archived_days` | project `[tasks]` | `tasks prune` deletes archived tasks older than this; unset keeps them forever |
+
+### Keeping and pruning finished tasks
+
+`caokit tasks archive` moves finished tasks out of the active folder and stamps the archive date.
+Archived tasks are kept until the project's policy says otherwise:
+
+```bash
+caokit tasks policy ~/proj-a --keep-archived-days 90     # per project, stored in .company/caokit.toml
+caokit tasks prune ~/proj-a                              # dry run: lists archived tasks older than 90 days
+caokit tasks prune ~/proj-a --yes                        # deletes them
+caokit tasks schedule ~/proj-a                           # prints the daily cron line
+caokit tasks schedule ~/proj-a --install --at 03:17      # adds it to your crontab (only its own line)
+```
+
+Scheduling uses cron. `--install` refuses until a retention policy exists, replaces only the line
+for that project, and `--remove` takes it out again. cron runs with a minimal environment, so the line
+uses the absolute path to `caokit`. On macOS cron may need Full Disk Access to read your project folder.
+
+## Worktrees: one per task
+
+```bash
+caokit tasks policy /path/to/repo --worktrees on   # needs a git repo root with a commit
+caokit install                                     # reinstall profiles so the roles carry the rules
+caokit worktrees /path/to/repo                     # list the task branches CAO left behind
+```
+
+With it on, the General dispatches each source-changing engineer through CAO's `use_worktree`: a private checkout at
+`<repo>/.cao/worktrees/<terminal-id>` on branch `cao/<terminal-id>`, cut from HEAD. What to know:
+
+- The engineer **commits on its own branch** (the only git write any worker may do, and only there). CAO deletes the
+  checkout, with anything uncommitted, when the terminal is deleted; a committed branch survives.
+- The General keeps the engineer's terminal until the task is accepted or cancelled, and sends rework to the same
+  terminal, so one task is one worktree.
+- The inspector reviews and re-runs the validation commands inside that checkout (`cd <worktree> && ...`).
+- **You merge**: `git merge cao/<id>`, then `git branch -d cao/<id>`. caokit never merges or deletes branches.
+- A new worktree starts from the last commit, so uncommitted changes in your main checkout are not in it.
+- `.company/` is git-ignored, so agents read and write it at the project root, not in the checkout.
+- **Git-ignored files are not in the checkout** (`node_modules`, `.venv`, `.env`, build caches), and CAO deletes them
+  with it. Have the task's authorised commands start with your install step (`npm ci`, `pnpm install --frozen-lockfile`,
+  `uv sync`); pnpm and uv share a global store, so that is cheap. Do not symlink the main `node_modules` in: parallel
+  engineers would write into one shared tree. CAO has no setup hook, so caokit does not run the install for you yet.
+
+## Safety model
+
+- Claude roles: CAO deny-lists (native) plus `permissionMode: auto`.
+- Antigravity: restrictions are **advisory**; treat its profile as guidance, not a boundary.
+- No path-level enforcement: any agent with write access can write anywhere in the repo. Turn on
+  [worktrees](#worktrees-one-per-task) so each writing task gets its own git worktree, and inspect
+  `git diff` afterwards.
+- No role may deploy, merge, push, contact third parties, use production credentials, change billing,
+  or run destructive git. The human commits.
+- Human approval is required for plan-path tasks, acceptance, merges, pushes, deployments, secrets,
+  dependency changes and destructive actions.
+- The kit holds no credentials by design.
+
+## Validation
+
+Last run on the `caokit` path: PASS with 13 checks passing and 1 manual (read the synthesis). About
+122k fresh Claude tokens (input, output and cache writes), plus about 1.0M cache reads. Antigravity
+leaves no token data, so its share is not counted.
+
+The proof harness is `scripts/95-validate-e2e.sh`. It builds a throwaway repo (`taskly` sample app)
+under `validation/`, runs `caokit init --name e2e` and `caokit install --project`, launches TASK-0001
+with `caokit launch`, polls the CAO API, collects evidence and writes `evidence/ACCEPTANCE.md` with a
+PASS/FAIL verdict and `evidence/token-usage.md`. Knobs:
+`TIMEOUT_MIN=60 POLL_SEC=15 AUTO_NUDGE=1 STALL_MIN=10 KEEP_SESSION=0 FORCE_REPLACE=0 SKIP_AGY_MODELS=0`.
+It needs Python 3.11+. `validation/` is local run evidence and is not committed.
+
+## Developing caokit
+
+```bash
+export PYTHONPATH=src
+uvx ruff check src tests && uvx ruff format --check src tests   # lint + format (Google docstrings enforced)
+uvx mypy                                                          # strict types for src, lenient for tests
+python3 -B -m unittest discover -s tests -t .                    # unit tests (a real-cao test runs if `cao` is installed)
+```
+
+CI (`.github/workflows/ci.yml`) runs the same four checks on macOS with Python 3.11 and 3.13 for
+every push to `main` and every pull request.
+
+Ruff and mypy both target Python 3.11, the minimum (`requires-python = ">=3.11"`); caokit has no
+runtime dependencies. `uv tool install` fetches a suitable interpreter, so the system Python does
+not matter.
+
+### Releasing
+
+Versions follow PEP 440 and are bumped with [`bump-my-version`](https://github.com/callowayproject/bump-my-version),
+which rewrites the version in `pyproject.toml` and `src/caokit/__init__.py`, commits and tags `vX.Y.Z`:
+
+```bash
+uvx bump-my-version show-bump          # preview what each bump would produce
+uvx bump-my-version bump minor         # 0.2.2 -> 0.3.0.dev0   (start a new version)
+uvx bump-my-version bump pre_n         # 0.3.0.dev0 -> 0.3.0.dev1
+uvx bump-my-version bump pre_l         # 0.3.0.dev1 -> 0.3.0.rc0, and again -> 0.3.0
+git push origin main --follow-tags
+gh release create vX.Y.Z --notes "..." # add --prerelease for dev and rc versions
+```
+
+Publishing the GitHub release runs `.github/workflows/release.yml`, which checks the tag against the
+package version, builds, and uploads to PyPI. Update `CHANGELOG.md` before bumping.
+
+`scripts/95-validate-e2e.sh` (the harness above) and `scripts/token_usage.py` (Claude token use per
+session) are development tools for this repo, not part of the installed CLI.
+
+## Parked: Codex
+
+Codex was removed after every CAO failure turned out to be Codex-specific (MCP approval denied,
+inherited `xhigh` reasoning, config drift). Its adapter is kept as metadata only and cannot be
+selected. If Codex returns, the `send_message` callback needs:
+
+```yaml
+codexConfig:
+  mcp_servers.cao-mcp-server.tools.send_message.approval_mode: "approve"
+```
+
+and an explicit `model_reasoning_effort`. Codex 0.134+ reads `~/.codex/NAME.config.toml` files.
+The old Codex profile files are in git history.
+
+## More
+
+[`TROUBLESHOOTING.md`](https://github.com/ajzpiv97/cao-kit/blob/main/TROUBLESHOOTING.md), [`SOURCES.md`](https://github.com/ajzpiv97/cao-kit/blob/main/SOURCES.md), [`CHANGELOG.md`](https://github.com/ajzpiv97/cao-kit/blob/main/CHANGELOG.md).
+
+## License
+
+MIT, see [`LICENSE`](https://github.com/ajzpiv97/cao-kit/blob/main/LICENSE).

caokit-0.3.0.dev0.dist-info/RECORD

@@ -0,0 +1,46 @@
+caokit/__init__.py,sha256=FgUgXPGa5BzOTDn7Uo_9BdSYCwC_sI7DbbOJoTMSASk,86
+caokit/adapters.py,sha256=U0k5FR-Njogrl3Rt8nVlW9lWKa2JK1Ip71rmn6D1z3A,9883
+caokit/cli.py,sha256=LATXhIMVXtA8QaF3WOOIGn9tfuoOjZ3IMee4BKmlEB8,26680
+caokit/company.py,sha256=fWMfdxMHzYNZQp9KUaRUNPDTnNXqR3gL0WEfchNfjmY,4327
+caokit/config.py,sha256=15FLl0TfvAogQRoxzyMJGxiEHtUaO0q7GZK3CY9DqDI,6769
+caokit/doctor.py,sha256=w9D5uBDpCuoQV_tLj_HLyoNDT0pjnGcfkhH_PnrEVFQ,9952
+caokit/gitignore.py,sha256=aLoGrgEU5ePctn18hcDJYcnwHFA6bKEkFB-IdFwZs1w,1468
+caokit/init_project.py,sha256=t-sV7G9Sa4KaNcM212j1oCQAU0c00BPU-jMU1GQlc3w,7337
+caokit/install.py,sha256=rbs1ebwNp48HTNgs__YayVude1sSikXk9GifrUUdB9Q,9132
+caokit/launch.py,sha256=x3-GcqEjYu6nN44EK5KMv8j0-lEzUTVuYozH43AB-WA,3955
+caokit/project.py,sha256=j6Asx4YbUHcp9OzVgjvXDR3DTZJRZx9wkwDVSL40zQM,12822
+caokit/render.py,sha256=Rikr9X0bg1sX8v0167Ha9otyUA2I-bJrwta7JmvEcYo,4640
+caokit/reset.py,sha256=yCYYAABgc7XFfp8x90K6B8EHcTvj76BancyMKuYMC0M,7685
+caokit/roster.py,sha256=0dUTpleln9RERZBXEe6jNH852p2kWqI_qDYHHFlV3sI,3975
+caokit/schedule.py,sha256=CnmfmR5b3ARdmazW0d_gXiTwm_mz0Kho9xcbCPk48hQ,3510
+caokit/stack.py,sha256=jBgRHI0AMoYRRun7DMgjrBGrM18DMw_pgIzOGTzfM1s,4346
+caokit/tasks.py,sha256=NyiKWQzKhanJZTRUuQxMqbqVfg06RNGOfDHuBeutKJs,5814
+caokit/worktrees.py,sha256=tGW5cZKDeftIcIC6msbSgZmHRGh_9x1Y2zKTBAAtp1Q,4181
+caokit/data/adapters/antigravity.toml,sha256=7vMSRprpztBaraJPOxx2_COVHZXs6xe306zx1z_wDsA,1055
+caokit/data/adapters/claude.toml,sha256=WAaBIMLJN6yZZUpdwytQipFeZY4aTsIY2lh-sBesfjM,763
+caokit/data/adapters/codex.toml,sha256=pgxFRQKBRjBbNS4a04NUnn359A0qYZSr5U3e0gRzN3M,527
+caokit/data/roles/engineer.md,sha256=cWh7ufcGXNALzOn2uRgAM-LwvHBAn_vj9T4XjRGjFwA,4056
+caokit/data/roles/general.md,sha256=mzdh0dVmN7LB7H_YZuq4qBZkULEro_KIJWa4YJT1CjY,15082
+caokit/data/roles/inspector.md,sha256=3dkBR4U_T2eHBuHjsFw9_Di9fKBixcvSwUiXYtrdzP0,3362
+caokit/data/roles/scout.md,sha256=ttwGTKyAUK_Pb83DIFDMFp3iw9DqHi2cubsIg361FFo,2197
+caokit/data/scaffold/company/BACKLOG.md,sha256=uRn68jIxo7bZkusiLP0ZF-kWbi0v5esyL84k6tAuQEQ,188
+caokit/data/scaffold/company/COMPANY.md,sha256=Nv1nz16cog9NvOzeHkbp_QyjMbdxc_ll-3SP_5qXywE,1221
+caokit/data/scaffold/company/DECISIONS.md,sha256=gpEyOiWEdIDiWCLIBg1HYDR0XNpDRlkpb8_0A3eBwbs,204
+caokit/data/scaffold/company/README.md,sha256=P5uDDIGuVAeuRXkylDlR-Pks8i6KnWlEkassNkQCBTQ,512
+caokit/data/scaffold/company/TEAM.md,sha256=qXrUswdPUsYZUw7lei_2yRJEIiP7YioimmR0RCWKX9o,272
+caokit/data/scaffold/company/contracts/ARTIFACT_CONTRACT.md,sha256=U8tMhDG2iOdhmSlYewOBBRmNIzg9qd5-zJTG7O39PIo,895
+caokit/data/scaffold/company/contracts/COMMUNICATION_CONTRACT.md,sha256=xz04cwCmkOiTxlpX5q1f9UbCVDXUBZOsMq_qwUJLuL0,1243
+caokit/data/scaffold/company/contracts/COMPANY_CONTRACT.md,sha256=pg8023YkZWpHXfl5UB5EV0hl4YXuiijginP5fuHTn4w,1472
+caokit/data/scaffold/company/contracts/REVIEW_CONTRACT.md,sha256=XBEM2_65C1ARv6dIV6mwC7McBuMKj-a7kN3pJD2jG0w,993
+caokit/data/scaffold/company/contracts/SAFETY_CONTRACT.md,sha256=Y6H5lAb00KdRUPZNfCbgR2QNPDn0Ms_VeSnsJqMEH98,1850
+caokit/data/scaffold/company/contracts/STATE_CONTRACT.md,sha256=SHKk_Gh_VUVeX3TZp46I7hvaa7eex-RPq_CdwzFpWA0,1172
+caokit/data/scaffold/company/contracts/TASK_CONTRACT.md,sha256=aemZwi4itGP7k1BNWHk7a23WXRekVAhvhq3iRh7NUbU,1361
+caokit/data/scaffold/company/prompts/first-run.md,sha256=9dUz2GJFFzIbX5VW8KJRgsZHq0IY3-l4JSiGoGWL-H4,1718
+caokit/data/scaffold/company/tasks/TASK-0001-smoke-test.md,sha256=fXkwJ8Mnfv_JgWDG7gSreWCpbaYeb7Jub7gCzPaKBBg,3369
+caokit/data/scaffold/company/tasks/TASK_TEMPLATE.md,sha256=-uRwKub_O0cWJL_KjziMMfOSrLuae1G0sAtsXytK8AU,2378
+caokit-0.3.0.dev0.dist-info/licenses/LICENSE,sha256=bs1ZmsX4vV7FiTIVbuGYtiQWBslJLs7pNch_OdQjUH0,1074
+caokit-0.3.0.dev0.dist-info/METADATA,sha256=hwPOqBeHmYqRpddp1qTvdqDrjqbI-hL9lwpx4nJEb1s,22355
+caokit-0.3.0.dev0.dist-info/WHEEL,sha256=mOdXR9C3wMVov7cSY8PY-XCzo3SmmWCHvGQr5csJoao,91
+caokit-0.3.0.dev0.dist-info/entry_points.txt,sha256=5WhsDx9lAeNgP3L7gnifxJVUeO6EYIdPSVpa_BKiAqs,43
+caokit-0.3.0.dev0.dist-info/top_level.txt,sha256=_FZta-3NDKTb2TjR2cnlTYIm7kZkDIJZmxtXXsfaW-Y,7
+caokit-0.3.0.dev0.dist-info/RECORD,,

caokit-0.3.0.dev0.dist-info/WHEEL

@@ -0,0 +1,5 @@
+Wheel-Version: 1.0
+Generator: setuptools (84.2.1)
+Root-Is-Purelib: true
+Tag: py3-none-any
+

caokit-0.3.0.dev0.dist-info/entry_points.txt

@@ -0,0 +1,2 @@
+[console_scripts]
+caokit = caokit.cli:main

caokit-0.3.0.dev0.dist-info/licenses/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Armando Zubillaga
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

caokit-0.3.0.dev0.dist-info/top_level.txt

@@ -0,0 +1 @@
+caokit