project-loop-harness 0.5.0__tar.gz → 0.5.2__tar.gz

{project_loop_harness-0.5.0 → project_loop_harness-0.5.2}/MANIFEST.in

@@ -5,7 +5,7 @@ include Makefile
 recursive-include agent-tasks *.md
 recursive-include docs *.md
 recursive-include scripts *.py
-recursive-include tests *.py *.json
+recursive-include tests *.py *.json *.md
 
 prune .claude
 prune .codex

project_loop_harness-0.5.2/PKG-INFO

@@ -0,0 +1,230 @@
+Metadata-Version: 2.4
+Name: project-loop-harness
+Version: 0.5.2
+Summary: Local control plane for agentic project development loops
+Author: Project Loop Harness Contributors
+License: MIT
+Project-URL: Homepage, https://github.com/mocchalera/project-loop-harness
+Project-URL: Repository, https://github.com/mocchalera/project-loop-harness
+Project-URL: Issues, https://github.com/mocchalera/project-loop-harness/issues
+Project-URL: Documentation, https://github.com/mocchalera/project-loop-harness/tree/main/docs
+Keywords: agents,codex,claude-code,sqlite,dashboard,workflow
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Programming Language :: Python :: 3.10
+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.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Provides-Extra: dev
+Requires-Dist: build>=1; extra == "dev"
+Requires-Dist: pytest>=8; extra == "dev"
+Requires-Dist: ruff>=0.6; extra == "dev"
+Requires-Dist: setuptools>=69; extra == "dev"
+Requires-Dist: wheel; extra == "dev"
+Provides-Extra: mcp-test
+Requires-Dist: mcp==1.28.1; extra == "mcp-test"
+Dynamic: license-file
+
+# Project Loop Harness
+
+> Turn a coding agent's “done” into reviewable evidence, residual risk, and a
+> resumable next step.
+
+![Project Loop Harness completion dashboard](docs/assets/v0.5.0-demo/dashboard-ja.png)
+
+## Understand it in 30 seconds
+
+Coding agents can produce changes quickly. They are less reliable at preserving
+project state, proving completion, stopping at human decisions, and handing work
+to another session or model.
+
+Project Loop Harness (`pcl`) gives Codex, Claude Code, and similar agents one
+local, model-neutral loop:
+
+```text
+intent → bounded work → checks → copied evidence → completion packet → next step
+```
+
+- SQLite keeps current state; JSONL keeps an auditable event projection.
+- Tests, artifacts, reviews, and completion packets preserve what “done” means.
+- Agents continue routine safe work; humans decide product, permission, security,
+  destructive, and external-service questions.
+- The runtime does not call an LLM or depend on one agent vendor.
+
+It is for people coordinating coding agents, not another chat wrapper.
+
+## Get first value in five minutes
+
+Install the runtime with either tool:
+
+```bash
+pipx install project-loop-harness
+# or: uv tool install project-loop-harness
+```
+
+Inspect the adoption plan before writing anything, then initialize:
+
+```bash
+cd /path/to/your-project
+pcl init --dry-run --json
+pcl init
+pcl doctor --strict
+```
+
+`pcl init` detects common Python and Node project metadata and safe verification
+commands. It retains existing `AGENTS.md`, `CLAUDE.md`, `.gitignore`, and
+`pcl.yaml` content. `--force` may replace generated templates, but it does not
+replace existing project-instruction content.
+
+Now tell the coding agent the outcome—not a sequence of `pcl` commands:
+
+```text
+Read AGENTS.md, CLAUDE.md if present, and pcl.yaml. Use the Project Control
+Loop. Start this goal: <describe the outcome>. Continue every agent-safe next
+action, run the configured checks, preserve evidence, emit a completion packet,
+and close the goal. Do not ask me to run routine pcl commands. Stop only for a
+genuine human decision or external blocker.
+```
+
+The agent owns `pcl start → implementation → finish → close`. The operator uses
+the CLI for setup, review, and deliberate maintenance.
+
+Want to see the result before adopting it? Run the isolated
+[3-minute public-package demo](examples/v0.5.0-adoption-demo/README.md).
+
+## What the operator needs to remember
+
+| Moment | Command | Purpose |
+| --- | --- | --- |
+| Adopt | `pcl init --dry-run --json`, then `pcl init` | Inspect and install local policy/state |
+| Start | `pcl start "<outcome>"` | Preserve literal intent as Goal and Task |
+| Orient | `pcl next --json` or `pcl resume` | Continue or hand off safely |
+| Verify | `pcl finish --emit-packet --goal G-XXXX` | Rerun checks and pin evidence |
+| Review | `pcl render` | Generate the human dashboard |
+
+Most other commands are an agent-facing and maintainer-facing reference surface.
+Start with the five moments above.
+
+## What it is—and is not
+
+```text
+Skill          = instructions for agents
+pcl CLI        = guarded local runtime and state machine
+project.db     = current normalized loop memory
+events.jsonl   = derived append-only audit projection
+dashboard.html = generated human view, never machine state
+Plugin / MCP   = optional integration wrappers, never the runtime
+```
+
+Project Loop Harness is local-only by default. Initialization enables no
+telemetry, cloud sync, provider call, production access, or automatic GitHub
+write. It is not a hosted orchestration service, a sandbox, or proof that an
+agent understood the code.
+
+Agents must not edit `.project-loop/project.db`, `.project-loop/events.jsonl`, or
+generated dashboard HTML. State mutations go through `pcl`; machine context
+comes from JSON commands, evidence paths, reports, or `dashboard-data.json`.
+
+The protected and internal compatibility surfaces are documented in the
+[Alpha Stability Policy](docs/stability-policy.md).
+
+## Install and inspect in more detail
+
+Use a project virtual environment instead of a global tool install when that is
+the repository convention:
+
+```bash
+python -m pip install project-loop-harness
+python -m pcl --version
+```
+
+For unreleased work, pin a tag or commit:
+
+```bash
+pipx install "git+https://github.com/mocchalera/project-loop-harness.git@<tag-or-commit>"
+```
+
+After initialization:
+
+```bash
+pcl validate --strict
+pcl render --json
+pcl update check       # explicit, cached, advisory only
+```
+
+Use `pcl update command` to print the appropriate manual upgrade command. Set
+`PCL_NO_VERSION_CHECK=1` to disable version checks.
+
+## The proof boundary
+
+A release, download, clone, dashboard, or passing internal demo is output
+evidence—not adoption evidence. v0.5.2 is being judged by observed first use in
+real repositories: time to healthy setup, time to a verified completion packet,
+maintainer interventions, safety violations, and voluntary reuse.
+
+The frozen cohort method and success thresholds live in
+[v0.5.2 Adoption Proof](docs/adoption-proof-v0.5.2.md). Until those observations
+exist, the project does not claim external adoption.
+
+## Documentation
+
+- [Adoption Guide](docs/adoption-guide.md) — coexistence, distribution, and the
+  first real repository.
+- [3-minute demo](examples/v0.5.0-adoption-demo/README.md) — reproducible public
+  package path to `COMPLETED_VERIFIED`.
+- [Golden Path](docs/golden-path.md) — complete direct and workflow examples.
+- [Architecture](docs/architecture.md) — state, events, evidence, and execution
+  boundaries.
+- [CLI Guide](docs/command-guide.md) — task-oriented command discovery.
+- [Recovery Playbook](docs/recovery-playbook.md) — safe diagnosis and repair.
+- [MCP compatibility](docs/mcp-compatibility.md) — optional client boundary.
+- [Security](SECURITY.md) and [Contributing](CONTRIBUTING.md).
+
+Advanced contracts stay in `docs/`: completion packets, evidence sets,
+completion policy, context packs, code context, workflow execution, Council
+Profile, trace/resume, reports, migrations, and dashboard data.
+
+## Local development
+
+```bash
+python -m venv .venv
+source .venv/bin/activate
+python -m pip install -e '.[dev]'
+ruff check .
+pytest
+PYTHONPATH=src python -m pcl --help
+```
+
+When working in a linked worktree, prefer `PYTHONPATH=src python -m pcl` or a
+worktree-local virtual environment instead of repointing a shared executable.
+
+Before release, verify both install artifacts:
+
+```bash
+python -m build --outdir /tmp/pcl-release-dist --sdist --wheel
+python scripts/verify_sdist_contracts.py --dist-dir /tmp/pcl-release-dist
+pytest tests/test_distribution.py
+```
+
+## Safety and current scope
+
+The first production milestone deliberately excludes:
+
+- hosted backends and cloud synchronization;
+- production database access;
+- autonomous destructive operations;
+- automatic external notifications or repository writes;
+- telemetry collection;
+- dynamic workflows before static contracts are stable.
+
+The current release is alpha software. Prefer pinned versions for team use,
+inspect the dry-run plan, keep human gates human, and preserve evidence for every
+terminal claim.

project_loop_harness-0.5.2/README.md

@@ -0,0 +1,195 @@
+# Project Loop Harness
+
+> Turn a coding agent's “done” into reviewable evidence, residual risk, and a
+> resumable next step.
+
+![Project Loop Harness completion dashboard](docs/assets/v0.5.0-demo/dashboard-ja.png)
+
+## Understand it in 30 seconds
+
+Coding agents can produce changes quickly. They are less reliable at preserving
+project state, proving completion, stopping at human decisions, and handing work
+to another session or model.
+
+Project Loop Harness (`pcl`) gives Codex, Claude Code, and similar agents one
+local, model-neutral loop:
+
+```text
+intent → bounded work → checks → copied evidence → completion packet → next step
+```
+
+- SQLite keeps current state; JSONL keeps an auditable event projection.
+- Tests, artifacts, reviews, and completion packets preserve what “done” means.
+- Agents continue routine safe work; humans decide product, permission, security,
+  destructive, and external-service questions.
+- The runtime does not call an LLM or depend on one agent vendor.
+
+It is for people coordinating coding agents, not another chat wrapper.
+
+## Get first value in five minutes
+
+Install the runtime with either tool:
+
+```bash
+pipx install project-loop-harness
+# or: uv tool install project-loop-harness
+```
+
+Inspect the adoption plan before writing anything, then initialize:
+
+```bash
+cd /path/to/your-project
+pcl init --dry-run --json
+pcl init
+pcl doctor --strict
+```
+
+`pcl init` detects common Python and Node project metadata and safe verification
+commands. It retains existing `AGENTS.md`, `CLAUDE.md`, `.gitignore`, and
+`pcl.yaml` content. `--force` may replace generated templates, but it does not
+replace existing project-instruction content.
+
+Now tell the coding agent the outcome—not a sequence of `pcl` commands:
+
+```text
+Read AGENTS.md, CLAUDE.md if present, and pcl.yaml. Use the Project Control
+Loop. Start this goal: <describe the outcome>. Continue every agent-safe next
+action, run the configured checks, preserve evidence, emit a completion packet,
+and close the goal. Do not ask me to run routine pcl commands. Stop only for a
+genuine human decision or external blocker.
+```
+
+The agent owns `pcl start → implementation → finish → close`. The operator uses
+the CLI for setup, review, and deliberate maintenance.
+
+Want to see the result before adopting it? Run the isolated
+[3-minute public-package demo](examples/v0.5.0-adoption-demo/README.md).
+
+## What the operator needs to remember
+
+| Moment | Command | Purpose |
+| --- | --- | --- |
+| Adopt | `pcl init --dry-run --json`, then `pcl init` | Inspect and install local policy/state |
+| Start | `pcl start "<outcome>"` | Preserve literal intent as Goal and Task |
+| Orient | `pcl next --json` or `pcl resume` | Continue or hand off safely |
+| Verify | `pcl finish --emit-packet --goal G-XXXX` | Rerun checks and pin evidence |
+| Review | `pcl render` | Generate the human dashboard |
+
+Most other commands are an agent-facing and maintainer-facing reference surface.
+Start with the five moments above.
+
+## What it is—and is not
+
+```text
+Skill          = instructions for agents
+pcl CLI        = guarded local runtime and state machine
+project.db     = current normalized loop memory
+events.jsonl   = derived append-only audit projection
+dashboard.html = generated human view, never machine state
+Plugin / MCP   = optional integration wrappers, never the runtime
+```
+
+Project Loop Harness is local-only by default. Initialization enables no
+telemetry, cloud sync, provider call, production access, or automatic GitHub
+write. It is not a hosted orchestration service, a sandbox, or proof that an
+agent understood the code.
+
+Agents must not edit `.project-loop/project.db`, `.project-loop/events.jsonl`, or
+generated dashboard HTML. State mutations go through `pcl`; machine context
+comes from JSON commands, evidence paths, reports, or `dashboard-data.json`.
+
+The protected and internal compatibility surfaces are documented in the
+[Alpha Stability Policy](docs/stability-policy.md).
+
+## Install and inspect in more detail
+
+Use a project virtual environment instead of a global tool install when that is
+the repository convention:
+
+```bash
+python -m pip install project-loop-harness
+python -m pcl --version
+```
+
+For unreleased work, pin a tag or commit:
+
+```bash
+pipx install "git+https://github.com/mocchalera/project-loop-harness.git@<tag-or-commit>"
+```
+
+After initialization:
+
+```bash
+pcl validate --strict
+pcl render --json
+pcl update check       # explicit, cached, advisory only
+```
+
+Use `pcl update command` to print the appropriate manual upgrade command. Set
+`PCL_NO_VERSION_CHECK=1` to disable version checks.
+
+## The proof boundary
+
+A release, download, clone, dashboard, or passing internal demo is output
+evidence—not adoption evidence. v0.5.2 is being judged by observed first use in
+real repositories: time to healthy setup, time to a verified completion packet,
+maintainer interventions, safety violations, and voluntary reuse.
+
+The frozen cohort method and success thresholds live in
+[v0.5.2 Adoption Proof](docs/adoption-proof-v0.5.2.md). Until those observations
+exist, the project does not claim external adoption.
+
+## Documentation
+
+- [Adoption Guide](docs/adoption-guide.md) — coexistence, distribution, and the
+  first real repository.
+- [3-minute demo](examples/v0.5.0-adoption-demo/README.md) — reproducible public
+  package path to `COMPLETED_VERIFIED`.
+- [Golden Path](docs/golden-path.md) — complete direct and workflow examples.
+- [Architecture](docs/architecture.md) — state, events, evidence, and execution
+  boundaries.
+- [CLI Guide](docs/command-guide.md) — task-oriented command discovery.
+- [Recovery Playbook](docs/recovery-playbook.md) — safe diagnosis and repair.
+- [MCP compatibility](docs/mcp-compatibility.md) — optional client boundary.
+- [Security](SECURITY.md) and [Contributing](CONTRIBUTING.md).
+
+Advanced contracts stay in `docs/`: completion packets, evidence sets,
+completion policy, context packs, code context, workflow execution, Council
+Profile, trace/resume, reports, migrations, and dashboard data.
+
+## Local development
+
+```bash
+python -m venv .venv
+source .venv/bin/activate
+python -m pip install -e '.[dev]'
+ruff check .
+pytest
+PYTHONPATH=src python -m pcl --help
+```
+
+When working in a linked worktree, prefer `PYTHONPATH=src python -m pcl` or a
+worktree-local virtual environment instead of repointing a shared executable.
+
+Before release, verify both install artifacts:
+
+```bash
+python -m build --outdir /tmp/pcl-release-dist --sdist --wheel
+python scripts/verify_sdist_contracts.py --dist-dir /tmp/pcl-release-dist
+pytest tests/test_distribution.py
+```
+
+## Safety and current scope
+
+The first production milestone deliberately excludes:
+
+- hosted backends and cloud synchronization;
+- production database access;
+- autonomous destructive operations;
+- automatic external notifications or repository writes;
+- telemetry collection;
+- dynamic workflows before static contracts are stable.
+
+The current release is alpha software. Prefer pinned versions for team use,
+inspect the dry-run plan, keep human gates human, and preserve evidence for every
+terminal claim.

project_loop_harness-0.5.2/agent-tasks/0174-v050-publication-closeout.md

@@ -0,0 +1,55 @@
+# 0174: v0.5.0 publication closeout
+
+- **Status:** Done; public release independently verified
+- **Milestone:** v0.5.0 Adoption / Distribution
+- **Priority:** P0
+- **Size:** S
+- **Dependency:** 0173 local release preparation
+- **DB schema:** remains 8
+- **Evidence:** `docs/evidence/0174-v050-publication-verification.md`
+
+## Goal
+
+Close the v0.5.0 publication record after the separately authorized release by
+independently verifying the immutable public surfaces and synchronizing only
+the repository's current factual documentation.
+
+## Scope
+
+1. Confirm that annotated tag `v0.5.0`, remote `main`, and the GitHub Actions
+   release run resolve to release commit
+   `6bfe9b4a5c5b651c7a4f5c7f4771e65cfa75fdb8`.
+2. Confirm that the GitHub Release is public and that Actions run `29334828358`
+   completed the build and PyPI publication jobs successfully.
+3. Confirm PyPI metadata, artifact hashes, and a clean public-wheel install,
+   initialization, validation, and render smoke.
+4. Record the results in a reviewable docs evidence file and minimally sync the
+   task indexes, roadmap, implementation plan, and v0.5.0 release notes.
+
+## Invariants
+
+- 0173 remains unchanged as the historical local-RC preparation record.
+- This closeout performs no push, tag, GitHub Release, PyPI, pipx, launch-post,
+  or other external mutation.
+- No source, test, dependency, database, schema, `.claude`, `.project-loop`, or
+  `pcl.yaml` change is in scope.
+- Public verification uses only read-only Git/GitHub/PyPI requests and an
+  isolated temporary installation.
+
+## Acceptance
+
+1. The public tag and release workflow resolve to the 0173 release commit.
+2. The GitHub Release is published, non-draft, and non-prerelease.
+3. Actions run `29334828358` is complete/success and its PyPI job succeeded.
+4. PyPI reports version `0.5.0`, non-yanked wheel and sdist files, and the
+   independently downloaded wheel matches the published SHA-256.
+5. A clean environment imports the PyPI package as `0.5.0` and completes init,
+   non-strict doctor, strict validation, and render smoke.
+6. `git diff --check` and repository-local Markdown link/integrity checks pass,
+   and the final commit contains only the intended documentation files.
+
+## Non-goals
+
+- Repeating or modifying the release operation.
+- Preparing or posting launch announcements.
+- Repairing historical task records or Project Loop local state.

project_loop_harness-0.5.2/agent-tasks/0175-maintainer-entry-hardening.md

@@ -0,0 +1,56 @@
+# 0175: Maintainer entry hardening
+
+- **Status:** Done; implemented and verified
+- **Milestone:** Post-v0.5.0 maintainability
+- **Priority:** P1
+- **Size:** S
+- **Dependency:** 0174 publication closeout and first-channel external launch
+- **DB schema:** remains 8
+- **Evidence:** `docs/evidence/0178-maintainer-entry-hardening.md`
+
+## Goal
+
+Make source-checkout verification identify the recurring wrong-worktree or
+stale-editable-install trap, and freeze the observable CLI contract before any
+large command-module refactor.
+
+## Scope
+
+1. When `pcl doctor` is run against the `project-loop-harness` source checkout,
+   compare the running `pcl` package root with `<checkout>/src/pcl`.
+2. Emit a structured `development_runtime_source_mismatch` finding containing
+   both paths and a source-pinned retry command when they differ.
+3. Keep ordinary adopted projects and a matching source checkout quiet.
+4. Document the behavior that future `cli.py` / `commands.py` extraction must
+   preserve, the staged extraction order, and the green-test gate for each
+   slice.
+5. Synchronize the post-launch priority and task indexes.
+
+## Invariants
+
+- The diagnostic is factual; it does not rewrite an editable install or choose
+  a worktree for the maintainer.
+- No dependency, schema, migration, raw SQL, telemetry, hosted service, or
+  automatic external write is added.
+- Normal `pcl validate` remains unaffected; the maintainer diagnostic belongs
+  to `pcl doctor` configuration advice.
+- Existing commands, output keys, typed errors, exit codes, events, mutation
+  boundaries, and Skill examples do not change in this slice.
+- The CLI split itself is not implemented here.
+
+## Acceptance
+
+1. A source checkout run from another package root emits one structured warning
+   with the running root, expected root, and deterministic retry command.
+2. A matching source checkout and an ordinary initialized project emit no such
+   finding.
+3. Targeted tests, full `ruff`, full `pytest`, strict PCL validation, and render
+   pass.
+4. The split plan freezes observable behavior and provides bounded extraction
+   gates before code movement.
+
+## Non-goals
+
+- Repointing pipx, venv, or global Python environments.
+- Splitting `cli.py` or `commands.py` in this task.
+- v0.5.1 Trace work, event-log compaction, provider execution, or a release.

project_loop_harness-0.5.2/agent-tasks/0176-scale-baseline-event-log-policy.md

@@ -0,0 +1,34 @@
+# 0176: Scale baseline and event-log policy
+
+- **Status:** Done; documentation/fixture slice only
+- **Milestone:** Post-v0.5.0 maintainability
+- **Priority:** P2
+- **Size:** S
+- **Dependency:** 0175 maintainer entry hardening
+- **DB schema:** remains 8
+- **Evidence:** `E-0375` (`docs/evidence/0176-scale-baseline-event-log-policy.md`)
+
+## Goal
+
+Measure the current file/event footprint, establish advisory scale bands, and
+document safe future rotation/compaction boundaries before any runtime policy
+is implemented.
+
+## Scope
+
+1. Record a dated repository snapshot with file sizes, event counts, entity
+   counts, and the SQLite/JSONL relationship.
+2. Add a deterministic synthetic benchmark manifest for smoke, maintainer, and
+   growth workloads.
+3. Document rotation and compaction invariants, recovery requirements, and
+   explicit non-goals.
+4. Add a small contract test that proves the fixture remains ordered and
+   non-enforcing.
+
+## Invariants
+
+- No runtime rotation or compaction is implemented.
+- No schema, dependency, telemetry, provider, or release change is made.
+- SQLite remains authoritative; JSONL remains a rebuildable projection.
+- Thresholds are advisory design inputs, not SLOs or automatic gates.
+- The fixture contains synthetic, deterministic data only.

project_loop_harness-0.5.2/agent-tasks/0177-advisory-checkpoint-routing.md

@@ -0,0 +1,58 @@
+# 0177: Advisory checkpoint routing
+
+- **Status:** Complete
+- **Milestone:** v0.5.1 Operator Friction
+- **Priority:** P0
+- **Size:** S
+- **DB schema:** no change
+- **Human approval:** approved in Cockpit after dogfooding the five-Feature gate
+
+## User problem
+
+The fixed five-Feature checkpoint is labeled non-blocking, but `pcl next`
+returns it before normal Task and Goal continuation and marks it as a human
+decision. In routine use this creates a ceremonial approval every five small
+Features and trains the operator to dismiss governance prompts.
+
+## Product outcome
+
+Keep the five-Feature cadence as a visible integration-review reminder without
+stopping normal work by default. Projects that need the old strict behavior can
+opt into it explicitly, and projects that do not want cadence reminders can
+turn them off.
+
+## Scope
+
+1. Add a schema-free top-level `checkpoint` configuration section:
+   - `mode: advisory | blocking | off`, default `advisory`;
+   - `feature_interval`, default `5`, minimum `1`.
+2. Keep `pcl checkpoint status` event-backed and expose the resolved mode and
+   whether the recommendation requires a human.
+3. In `advisory` mode, keep the recommendation visible but let `pcl next`
+   return the normal Task or Goal action.
+4. In `blocking` mode, preserve the existing `checkpoint_review` human gate.
+5. In `off` mode, suppress the cadence recommendation.
+6. Show an advisory checkpoint as a non-blocking, non-human low-severity
+   dashboard attention item.
+7. Reject invalid checkpoint configuration through typed CLI errors and
+   validation diagnostics.
+
+## Acceptance
+
+1. Five completed Features plus a ready Task returns `work_on_task` under the
+   default configuration while checkpoint status remains recommended.
+2. The same state returns the human-gated `checkpoint_review` with
+   `mode: blocking`.
+3. `mode: off` reports no checkpoint recommendation.
+4. A configured `feature_interval` replaces the built-in cadence.
+5. The dashboard shows advisory checkpoint attention outside the human
+   decision queue.
+6. Focused tests, lint, full tests, strict validation, render, and completion
+   packet closure pass.
+
+## Non-goals
+
+- Changing release, security, data, destructive-operation, repeated-failure,
+  Story approval, or Verification human gates.
+- Database migrations or dependency additions.
+- Automatically recording or dismissing a checkpoint.