Skip to content

docs(build): add Consumer column to BUILD_CAPABILITIES table#29

Merged
Jammy2211 merged 1 commit into
mainfrom
docs/build-capabilities-consumer-column
Jul 8, 2026
Merged

docs(build): add Consumer column to BUILD_CAPABILITIES table#29
Jammy2211 merged 1 commit into
mainfrom
docs/build-capabilities-consumer-column

Conversation

@Jammy2211

Copy link
Copy Markdown
Contributor

Adds a Consumer today column to the Build Agent capabilities table so the execution/health boundary is visible in the table itself.

  • run/run_python/run_all/script_matrix/aggregate_resultsHeart (workspace-validation.yml / health_release.sh); these are a latent build-mode seam, Heart is the live consumer.
  • generate_release_notes/bump_colab_urlsrelease.yml; generate dual (deploy + Heart); repro_command → triage.
  • Note added explaining the Mode (allowlist) vs Consumer (live driver) split.

🤖 Generated with Claude Code

Make the execution/health boundary visible in the capabilities table: a new
"Consumer today" column records who actually drives each capability, alongside
the existing Build Agent mode allowlist.

The workspace full-run flow (run/run_python/run_all/script_matrix/
aggregate_results) migrated out of release.yml into PyAutoHeart's
workspace-validation.yml, which calls the PyAutoBuild primitives directly.
Nothing routes them through `pyauto-brain build run_*` today, so those
build-mode allowlist entries are a latent seam with Heart as the live consumer.
Note added to explain the Mode-vs-Consumer split.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings July 8, 2026 11:00
@Jammy2211 Jammy2211 merged commit c6f5359 into main Jul 8, 2026
1 check passed
@Jammy2211 Jammy2211 deleted the docs/build-capabilities-consumer-column branch July 8, 2026 11:00

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the Build Agent’s capability audit to make the execution/health boundary explicit by documenting who actually consumes each PyAutoBuild capability today, alongside the existing allowlisted Build Agent modes.

Changes:

  • Adds a Consumer today column to the BUILD_CAPABILITIES.md table.
  • Adds an explanatory note clarifying Mode (allowlist) vs Consumer (live driver), especially around the run* surface.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment on lines +34 to +36
report → issue flow moved **out of `release.yml` into PyAutoHeart's
`workspace-validation.yml`** (see `PyAutoBuild/docs/internals.md` and the
`release.yml` comment recording the removed `run_scripts` / `run_notebooks` /
Comment on lines +22 to +23
| `run_python` | Execute Python scripts in a workspace folder. | build | **Heart** `workspace-validation.yml` · `health_release.sh` |
| `run_all` | Run scripts across one or more workspaces, produce summary reports. | build | **Heart** `health_release.sh` + readiness checks |
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants