atm-bd 0.17.3__tar.gz

atm_bd-0.17.3/.gitignore

@@ -0,0 +1,2 @@
+/src/atm_bd_console/_build_identity.py
+/src/atm_bd_console/_skills/

atm_bd-0.17.3/CONTRACT.md

@@ -0,0 +1,46 @@
+# bh-1 Type Contract
+
+The canonical frozen contract is the `atm-bh-1` bead design. Its declarations
+are synchronized with the field orders below.
+
+The positional field order in `types.py` is part of the current contract:
+
+- `Sprint`: `id`, `title`, `layer`, `branch`, `target`, `stack`, `depends_on`, `closed`, `findings`.
+- `Inputs`: `now`, `lead`, `repo`, `interval_s`, `phase`, `members`, `tasks`, `worktrees`, `remotes`, `merges`, `prs`, `gh`, `task_beads`.
+- `PhaseFile`: `phase`, `root_id`, `label`, `sprints`, `depends_on`, `lead`, `templates`.
+
+`Inputs.interval_s` is always `Config.interval_s`; the bh-9 runner builds
+`Inputs` from `Config`. Do not add other `Config` mirrors to `Inputs`.
+
+`Config.notification_sender` is the validated `member@team` sender for plain
+notifications, defaulting to `atm-bd@tool` and overridden only by `tool_identity`
+in the repository YAML. It is appended with a default so
+existing callers remain compatible; assignment identity remains `Config.lead`.
+
+`RepoConfig.reviewers_round1` is part of the `RepoConfig` declaration in that
+design and remains in its listed position before `plans_dir`.
+
+The parallel sprint branches (bh-3 through bh-10) were rebased above the bh-1
+contract layer and carry this field order. New fields must be supplied by
+keyword in constructors from here on; existing fields and signatures are not
+being changed except for the phase-settings update below.
+
+## Phase settings (ANC023)
+
+`PhaseFile.lead` is the validated nonempty phase TOML identity;
+`Config.lead` is its resolved runtime value, refreshed each tick. Console
+launches accept `--phase` and no longer accept `--as`. Neither environment
+identity nor repository YAML supplies a fallback lead.
+
+`PhaseFile.templates` maps exactly `dev`, `dev_fix`, `fix`, `sanity`, `qa`,
+`plan_review`, and `review` to existing repository-relative files within
+`.claude/skills/atm-bd-orchestration/templates/`. Missing or invalid lead and
+template values return `Err(ConfigInvalid)` naming `lead` or
+`templates.<purpose>` before launch effects.
+
+`dispatch_spec(context, templates)` takes this validated mapping explicitly.
+The runner binds it to the existing one-argument `SpecFn`; the pure model's
+signature is unchanged. Only sanity and QA dispatch are supported, using the
+matching purpose key and the existing repository-configured recipient.
+`DispatchSpec.template` carries the exact configured relative path to ATM's
+`--template` argument. New `PhaseFile` fields are supplied by keyword.

atm_bd-0.17.3/PKG-INFO

@@ -0,0 +1,172 @@
+Metadata-Version: 2.4
+Name: atm-bd
+Version: 0.17.3
+Summary: ATM and Beads orchestration console, cron runner, and bundled skills
+Project-URL: Repository, https://github.com/randlee/atm-bd-orchestration
+Project-URL: Issues, https://github.com/randlee/atm-bd-orchestration/issues
+Author: Rand Lee
+License-Expression: MIT
+Requires-Python: >=3.11
+Requires-Dist: pydantic
+Requires-Dist: pyyaml
+Requires-Dist: rich<16,>=15.0.0
+Requires-Dist: sc-compose<2,>=1.7.0
+Requires-Dist: sc-observability<2,>=1.5.0
+Requires-Dist: textual<9,>=8.2.8
+Description-Content-Type: text/markdown
+
+# atm-bd
+
+`atm-bd` provides a terminal dashboard and single-tick cron runner for ATM and
+Beads orchestration. It also bundles the orchestration skills for installation
+into a repository.
+
+## Development validation
+
+From the repository root, `just lint` runs the console's lint and type gates.
+Pyright checks only `apps/atm-bd-console/src`, including the enum matches whose
+`assert_never` fallbacks make missing cases type errors. `tests/` is not included in the static type-check gate;
+the test suite is validated by pytest at runtime. Ruff checks both `src` and `tests`.
+The GitHub Actions console source type-check step uses the same scope.
+
+Run the checks directly from `apps/atm-bd-console`:
+
+```bash
+uv run --frozen pytest -q
+uv run --frozen --group dev ruff check src tests
+uv run --frozen pyright src
+```
+
+## Installation and prerequisites
+
+Install the package with `uv tool install atm-bd` (Python 3.11 or newer).
+The console and cron commands operate on a configured repository and require
+the `atm`, `bd`, and `git` executables on `PATH`. The Status graph also uses
+`mmdflux` when available.
+
+Before running `atm-bd skill`, install the `sc-compose` CLI and ensure the
+host `python3` on `PATH` can import `pydantic`, `yaml` (PyYAML), and the
+`sc-compose` Python wheel. The CLI, host wheel, and the wheel in the atm-bd
+environment must have matching versions within the bundled manifest's range;
+the installer checks these requirements before writing files. The host Python
+dependencies can be installed with `python3 -m pip install pydantic pyyaml
+'sc-compose>=1.7.0,<2'`; install the matching `sc-compose` CLI separately.
+
+From the repository root, run `atm-bd skill` to install the bundled skills
+without fetching a release. It reports the bundled source ref, commit SHA,
+and app version. Use `atm-bd skill --help` for release and destination options.
+
+## Console operational logs
+
+## Launch settings
+
+Run `atm-bd console --phase bh` from the repository root. For one cron tick,
+use `atm-bd cron --phase bh`; add `--dry-run` to preview actions.
+The phase file `.atm-bd/phase-bh.toml` supplies the assignment identity and
+template paths:
+
+```toml
+plan = "docs/plans/phase-bh.jsonl"
+root = "atm-phase-bh"
+integration_branch = "integrate/phase-bh"
+lead = "solar"
+
+[templates]
+dev = ".claude/skills/atm-bd-orchestration/templates/dev-template.xml.j2"
+dev_fix = ".claude/skills/atm-bd-orchestration/templates/dev-fix.xml.j2"
+fix = ".claude/skills/atm-bd-orchestration/templates/fix-assignment.xml.j2"
+sanity = ".claude/skills/atm-bd-orchestration/templates/dev-sanity-template.xml.j2"
+qa = ".claude/skills/atm-bd-orchestration/templates/qa-template.xml.j2"
+plan_review = ".claude/skills/atm-bd-orchestration/templates/plan-review-template.xml.j2"
+review = ".claude/skills/atm-bd-orchestration/templates/review-template.xml.j2"
+```
+
+All seven purposes are required. Each value must name an existing file under
+the installed template directory, relative to the repository root. Missing,
+empty, unknown, or invalid settings produce `config_invalid` naming the key
+before the console starts. Console `--as` is removed; `lead` is read only from
+the phase file, with no environment or repository YAML fallback. Each tick
+reloads these phase settings. Team and sanity/QA recipients still come from
+`.atm.toml` and `.claude/project/atm-bd-orchestration.yaml`, respectively.
+
+The console automatically assigns ready sanity and QA work using
+`templates.sanity` and `templates.qa`. It passes the configured path to
+`atm task assign --template` and the phase lead to ATM's `--as`. The other
+purposes support orchestration workflows and do not enable additional console
+dispatch kinds.
+
+Plain notifications use `atm-bd@tool` by default, independently of the lead
+used for assignments. The skill installer provisions the default tool identity.
+To use another sender, set `tool_identity: "member@team"` in
+`.claude/project/atm-bd-orchestration.yaml` and provision that identity in ATM.
+Environment variables and command-line flags do not select the sender; ATM
+subprocess identity and team are set from the selected sender. Failed sends
+remain visible in snapshot errors and cron error lines. Task assignments remain
+local to the lead's team (cross-team assignments are tracked by atm-core #1870).
+
+## Dispatch verification
+
+Ready sanity and QA assignments require a successful merge check for their
+branch and target. Missing results, missing targets, timeouts, and unsupported
+git commands hold assignment with an actionable problem until verification
+succeeds. The persisted merge states remain `clean` (verified), `conflict`, and
+`error` (verification unavailable); a failed probe replaces any cached clean
+result. PR and CI status never hold assignment.
+
+Each tick with a ready assignment candidate refreshes origin before pinning a
+commit. A fetch or remote-ref read failure appears in the snapshot and logs,
+holds assignment, and clears eligible cached refs so recovery retries safely.
+`--no-fetch` explicitly skips refresh and permits the saved remote refs, while
+still requiring a successful current merge check.
+
+## Operational events
+
+The console owns one `sc-observability` logger for its repository for the life
+of the process. All ticks reuse it, including stopped and failed ticks. Logs
+live under `.atm-bd/atm-bd/logs/`; the console sink is disabled. Each
+tick flushes admitted events before saving its snapshot. Logger construction,
+event admission and flush failures appear in the snapshot's Errors section
+and in headless error output. They do not change whether a dispatch succeeded.
+After repairing a logger construction failure, restart the process to retry
+initialization.
+
+Each proposed assignment, send or batch has an `action` event containing
+`effect`, `recipient`, all `task_ids`, `outcome`, and the complete typed delivery
+`error` (or null). Outcomes are `sent`, `failed <error kind>`, and `dry_run`.
+Dry runs never deliver an ATM effect. Events cover every action even when the
+dashboard's recent-action list retains only five. A logging error means the
+operational log may be incomplete; use the snapshot's delivery outcomes and
+Errors section to investigate. Source reads and git fetch/merge probes record
+their operation, outcome and typed error, with team, task IDs or branch context
+where available. `hold` events record the task, recipient and hold reason;
+they do not introduce additional dispatch rules.
+
+The phase's `.atm-bd/atm-bd/<root>/actions.jsonl` is an append-only
+journal. Assignment/send entries record attempts, followed by a `hold` entry
+on failure; `dry_run` entries record previews. An attempt entry alone is not
+proof of delivery. Operational `action` events carry the explicit outcome.
+
+## Retention and rotation
+
+The console does not enforce an age or size retention limit on either the
+operational log directory or `actions.jsonl`. Both require operator-managed
+rotation. Check their disk usage daily; archive at least weekly or when either
+reaches 100 MiB. Keep compressed archives for 30 days unless the project's
+audit policy requires longer. These are maintenance recommendations, not
+automatic limits.
+
+To rotate safely:
+
+1. Pause cron launches and stop every console using the repository. Logs are
+   shared across its phases, so stopping just one phase is insufficient.
+2. Move the entire `logs/` directory and each phase's `actions.jsonl` to a
+   timestamped archive outside the runtime directory. Compress the archive and
+   expire archives older than the chosen retention window.
+3. Leave `state.json`, `snapshot.json`, `merge.json`, `prs.json`, and lock files
+   in place. They are current runtime data, not log archives.
+4. Restart the consoles and resume cron. The logger recreates its directory;
+   the next action recreates `actions.jsonl`. Check the next snapshot for
+   logging or journal write errors.
+
+Do not truncate or rename active logs while writers are running. A scheduled
+rotation job must coordinate the same stop/archive/restart sequence.

atm_bd-0.17.3/README.md

@@ -0,0 +1,155 @@
+# atm-bd
+
+`atm-bd` provides a terminal dashboard and single-tick cron runner for ATM and
+Beads orchestration. It also bundles the orchestration skills for installation
+into a repository.
+
+## Development validation
+
+From the repository root, `just lint` runs the console's lint and type gates.
+Pyright checks only `apps/atm-bd-console/src`, including the enum matches whose
+`assert_never` fallbacks make missing cases type errors. `tests/` is not included in the static type-check gate;
+the test suite is validated by pytest at runtime. Ruff checks both `src` and `tests`.
+The GitHub Actions console source type-check step uses the same scope.
+
+Run the checks directly from `apps/atm-bd-console`:
+
+```bash
+uv run --frozen pytest -q
+uv run --frozen --group dev ruff check src tests
+uv run --frozen pyright src
+```
+
+## Installation and prerequisites
+
+Install the package with `uv tool install atm-bd` (Python 3.11 or newer).
+The console and cron commands operate on a configured repository and require
+the `atm`, `bd`, and `git` executables on `PATH`. The Status graph also uses
+`mmdflux` when available.
+
+Before running `atm-bd skill`, install the `sc-compose` CLI and ensure the
+host `python3` on `PATH` can import `pydantic`, `yaml` (PyYAML), and the
+`sc-compose` Python wheel. The CLI, host wheel, and the wheel in the atm-bd
+environment must have matching versions within the bundled manifest's range;
+the installer checks these requirements before writing files. The host Python
+dependencies can be installed with `python3 -m pip install pydantic pyyaml
+'sc-compose>=1.7.0,<2'`; install the matching `sc-compose` CLI separately.
+
+From the repository root, run `atm-bd skill` to install the bundled skills
+without fetching a release. It reports the bundled source ref, commit SHA,
+and app version. Use `atm-bd skill --help` for release and destination options.
+
+## Console operational logs
+
+## Launch settings
+
+Run `atm-bd console --phase bh` from the repository root. For one cron tick,
+use `atm-bd cron --phase bh`; add `--dry-run` to preview actions.
+The phase file `.atm-bd/phase-bh.toml` supplies the assignment identity and
+template paths:
+
+```toml
+plan = "docs/plans/phase-bh.jsonl"
+root = "atm-phase-bh"
+integration_branch = "integrate/phase-bh"
+lead = "solar"
+
+[templates]
+dev = ".claude/skills/atm-bd-orchestration/templates/dev-template.xml.j2"
+dev_fix = ".claude/skills/atm-bd-orchestration/templates/dev-fix.xml.j2"
+fix = ".claude/skills/atm-bd-orchestration/templates/fix-assignment.xml.j2"
+sanity = ".claude/skills/atm-bd-orchestration/templates/dev-sanity-template.xml.j2"
+qa = ".claude/skills/atm-bd-orchestration/templates/qa-template.xml.j2"
+plan_review = ".claude/skills/atm-bd-orchestration/templates/plan-review-template.xml.j2"
+review = ".claude/skills/atm-bd-orchestration/templates/review-template.xml.j2"
+```
+
+All seven purposes are required. Each value must name an existing file under
+the installed template directory, relative to the repository root. Missing,
+empty, unknown, or invalid settings produce `config_invalid` naming the key
+before the console starts. Console `--as` is removed; `lead` is read only from
+the phase file, with no environment or repository YAML fallback. Each tick
+reloads these phase settings. Team and sanity/QA recipients still come from
+`.atm.toml` and `.claude/project/atm-bd-orchestration.yaml`, respectively.
+
+The console automatically assigns ready sanity and QA work using
+`templates.sanity` and `templates.qa`. It passes the configured path to
+`atm task assign --template` and the phase lead to ATM's `--as`. The other
+purposes support orchestration workflows and do not enable additional console
+dispatch kinds.
+
+Plain notifications use `atm-bd@tool` by default, independently of the lead
+used for assignments. The skill installer provisions the default tool identity.
+To use another sender, set `tool_identity: "member@team"` in
+`.claude/project/atm-bd-orchestration.yaml` and provision that identity in ATM.
+Environment variables and command-line flags do not select the sender; ATM
+subprocess identity and team are set from the selected sender. Failed sends
+remain visible in snapshot errors and cron error lines. Task assignments remain
+local to the lead's team (cross-team assignments are tracked by atm-core #1870).
+
+## Dispatch verification
+
+Ready sanity and QA assignments require a successful merge check for their
+branch and target. Missing results, missing targets, timeouts, and unsupported
+git commands hold assignment with an actionable problem until verification
+succeeds. The persisted merge states remain `clean` (verified), `conflict`, and
+`error` (verification unavailable); a failed probe replaces any cached clean
+result. PR and CI status never hold assignment.
+
+Each tick with a ready assignment candidate refreshes origin before pinning a
+commit. A fetch or remote-ref read failure appears in the snapshot and logs,
+holds assignment, and clears eligible cached refs so recovery retries safely.
+`--no-fetch` explicitly skips refresh and permits the saved remote refs, while
+still requiring a successful current merge check.
+
+## Operational events
+
+The console owns one `sc-observability` logger for its repository for the life
+of the process. All ticks reuse it, including stopped and failed ticks. Logs
+live under `.atm-bd/atm-bd/logs/`; the console sink is disabled. Each
+tick flushes admitted events before saving its snapshot. Logger construction,
+event admission and flush failures appear in the snapshot's Errors section
+and in headless error output. They do not change whether a dispatch succeeded.
+After repairing a logger construction failure, restart the process to retry
+initialization.
+
+Each proposed assignment, send or batch has an `action` event containing
+`effect`, `recipient`, all `task_ids`, `outcome`, and the complete typed delivery
+`error` (or null). Outcomes are `sent`, `failed <error kind>`, and `dry_run`.
+Dry runs never deliver an ATM effect. Events cover every action even when the
+dashboard's recent-action list retains only five. A logging error means the
+operational log may be incomplete; use the snapshot's delivery outcomes and
+Errors section to investigate. Source reads and git fetch/merge probes record
+their operation, outcome and typed error, with team, task IDs or branch context
+where available. `hold` events record the task, recipient and hold reason;
+they do not introduce additional dispatch rules.
+
+The phase's `.atm-bd/atm-bd/<root>/actions.jsonl` is an append-only
+journal. Assignment/send entries record attempts, followed by a `hold` entry
+on failure; `dry_run` entries record previews. An attempt entry alone is not
+proof of delivery. Operational `action` events carry the explicit outcome.
+
+## Retention and rotation
+
+The console does not enforce an age or size retention limit on either the
+operational log directory or `actions.jsonl`. Both require operator-managed
+rotation. Check their disk usage daily; archive at least weekly or when either
+reaches 100 MiB. Keep compressed archives for 30 days unless the project's
+audit policy requires longer. These are maintenance recommendations, not
+automatic limits.
+
+To rotate safely:
+
+1. Pause cron launches and stop every console using the repository. Logs are
+   shared across its phases, so stopping just one phase is insufficient.
+2. Move the entire `logs/` directory and each phase's `actions.jsonl` to a
+   timestamped archive outside the runtime directory. Compress the archive and
+   expire archives older than the chosen retention window.
+3. Leave `state.json`, `snapshot.json`, `merge.json`, `prs.json`, and lock files
+   in place. They are current runtime data, not log archives.
+4. Restart the consoles and resume cron. The logger recreates its directory;
+   the next action recreates `actions.jsonl`. Check the next snapshot for
+   logging or journal write errors.
+
+Do not truncate or rename active logs while writers are running. A scheduled
+rotation job must coordinate the same stop/archive/restart sequence.

atm_bd-0.17.3/hatch_build.py

@@ -0,0 +1,67 @@
+from __future__ import annotations
+
+import re
+import subprocess
+import tomllib
+from pathlib import Path
+
+from hatchling.builders.hooks.plugin.interface import BuildHookInterface
+
+
+class CustomBuildHook(BuildHookInterface):
+    def initialize(self, version: str, build_data: dict[str, object]) -> None:
+        package = Path(self.root).resolve()
+        root = package.parents[1]
+        output = package / "src" / "atm_bd_console" / "_build_identity.py"
+        self._generated_identity = False
+        package_version = tomllib.loads((package / "pyproject.toml").read_text())["project"]["version"]
+        if (package / "PKG-INFO").is_file() and output.is_file():
+            if not re.search(r"^COMMIT = (['\"])[0-9a-f]{40}\1$", output.read_text(), re.MULTILINE):
+                raise RuntimeError(f"cannot reuse console identity: {output} has no valid 40-hex COMMIT")
+            self._include_identity(output, build_data)
+            self._include_skills(package, root, build_data)
+            return
+        try:
+            toplevel = subprocess.check_output(
+                ["git", "-C", root, "rev-parse", "--show-toplevel"], text=True, stderr=subprocess.PIPE
+            ).strip()
+        except FileNotFoundError as error:
+            raise RuntimeError("cannot build console identity: git executable is missing") from error
+        except (OSError, subprocess.CalledProcessError) as error:
+            raise RuntimeError("cannot build console identity: source is not a console checkout") from error
+        if Path(toplevel).resolve() != root or not (root / "apps/atm-bd-console" / "pyproject.toml").is_file():
+            raise RuntimeError("cannot build console identity: source is not a console checkout")
+        try:
+            shallow = subprocess.check_output(["git", "-C", root, "rev-parse", "--is-shallow-repository"], text=True).strip()
+            if shallow != "false":
+                raise RuntimeError("cannot build console identity: checkout is shallow")
+            revision = subprocess.check_output(["git", "-C", root, "rev-parse", "--short", "HEAD"], text=True).strip()
+            commit = subprocess.check_output(["git", "-C", root, "rev-parse", "HEAD"], text=True).strip()
+            count = subprocess.check_output(["git", "-C", root, "rev-list", "--count", "HEAD"], text=True).strip()
+            dirty = subprocess.check_output(["git", "-C", root, "status", "--porcelain", "--", ".", ":!.ok"], text=True).strip()
+        except (OSError, subprocess.CalledProcessError) as error:
+            raise RuntimeError("cannot build console identity: git command failed") from error
+        major, minor, _patch = package_version.split(".", 2)
+        identity = f"{major}.{minor}.{count}+g{revision}{'-dirty' if dirty else ''}"
+        self._include_skills(package, root, build_data)
+        output.write_text(f'IDENTITY = {identity!r}\nCOMMIT = {commit!r}\n')
+        self._generated_identity = True
+        self._include_identity(output, build_data)
+
+    def _include_identity(self, output: Path, build_data: dict[str, object]) -> None:
+        destination = "atm_bd_console/_build_identity.py" if self.target_name == "wheel" else "src/atm_bd_console/_build_identity.py"
+        build_data["force_include"][str(output)] = destination
+
+    def _include_skills(self, package: Path, root: Path, build_data: dict[str, object]) -> None:
+        plugin = root / "plugins" / "atm-bd-orchestration"
+        bundled = package / "src" / "atm_bd_console" / "_skills"
+        # An sdist must use its own contents, never a coincidental adjacent checkout.
+        source = bundled if (package / "PKG-INFO").is_file() else (plugin if plugin.is_dir() else bundled)
+        if not source.is_dir():
+            raise RuntimeError(f"cannot bundle skills: neither {plugin} nor {bundled} exists")
+        destination = "atm_bd_console/_skills" if self.target_name == "wheel" else "src/atm_bd_console/_skills"
+        build_data["force_include"][str(source)] = destination
+
+    def finalize(self, version: str, build_data: dict[str, object], artifact_path: str) -> None:
+        if self._generated_identity:
+            (Path(self.root) / "src" / "atm_bd_console" / "_build_identity.py").unlink(missing_ok=True)

atm_bd-0.17.3/pyproject.toml

@@ -0,0 +1,36 @@
+[project]
+name = "atm-bd"
+version = "0.17.3"
+description = "ATM and Beads orchestration console, cron runner, and bundled skills"
+readme = "README.md"
+license = "MIT"
+authors = [{ name = "Rand Lee" }]
+requires-python = ">=3.11"
+dependencies = ["rich>=15.0.0,<16", "textual>=8.2.8,<9", "sc-observability>=1.5.0,<2", "pyyaml", "pydantic", "sc-compose>=1.7.0,<2"]
+
+[project.urls]
+Repository = "https://github.com/randlee/atm-bd-orchestration"
+Issues = "https://github.com/randlee/atm-bd-orchestration/issues"
+
+[project.scripts]
+atm-bd = "atm_bd_console.cli:main"
+
+[dependency-groups]
+dev = ["pytest", "ruff", "pyright", "hatchling==1.31.0"]
+
+[build-system]
+requires = ["hatchling==1.31.0"]
+build-backend = "hatchling.build"
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/atm_bd_console"]
+
+[tool.hatch.build.targets.wheel.hooks.custom]
+
+[tool.hatch.build.targets.sdist.hooks.custom]
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]
+
+[tool.ruff]
+line-length = 120

atm_bd-0.17.3/src/atm_bd_console/__init__.py

@@ -0,0 +1,3 @@
+"""Shared contract for the ATM bead dashboard."""
+
+__version__ = "0.17.3"

atm_bd-0.17.3/src/atm_bd_console/_build_identity.py

@@ -0,0 +1,2 @@
+IDENTITY = '0.17.599+g5ff0a67'
+COMMIT = '5ff0a67fe6e046393e833faf72cd5eabb40fb520'

atm_bd-0.17.3/src/atm_bd_console/_skills/.claude-plugin/plugin.json

@@ -0,0 +1,17 @@
+{
+  "name": "atm-bd-orchestration",
+  "description": "Bead-driven phase orchestration for ATM agent teams: atm-beads (the plan as a beads graph), atm-bd-orchestration (dispatch, dev-sanity, QA and stack landing from bd ready) and sprint-report (status tables and DAGs from live beads), plus the dev-sanity agents they name.",
+  "version": "0.16.0",
+  "author": {
+    "name": "randlee"
+  },
+  "license": "MIT",
+  "keywords": [
+    "atm",
+    "beads",
+    "orchestration",
+    "sprint",
+    "qa",
+    "gh-stack"
+  ]
+}