Repository navigation
BAI-1616 document the impact-assessment trigger and block version in the playbooks pointer - #173
Merged
Merged
Conversation
…the playbooks pointer
alvinhenrick
approved these changes
Nov 10, 2026
alvinhenrick
left a comment
There was a problem hiding this comment.
Approving. The change itself is correct. There is one pre-existing placement risk worth fixing in a follow-up.
What I checked
- Source fidelity: the block matches the 1.1.0 block in step 3 of
docs/repo-playbooks/README.mdin bwell-repo-wiki@main, line for line. - Targets exist: all eight playbook files the triggers name are on main under
playbooks/, anddiagrams/exists too. - Scope: one file, and only the one-line pointer under
## Repo-specific addendumis replaced. - Commit: one commit (
15a6b58). It starts with BAI-1616 and has no AI-attribution trailer.
Worth a follow-up (not introduced here)
- No sync sentinel: this AGENTS.md has no
<!-- SYNC:PRESERVE-BELOW ... -->sentinel. The addendum sits under a bare<!-- REPO-SPECIFIC ADDENDUM -->comment (line 443 at head), with the full org baseline above it. - Why it matters: step 3 of the wiki README and CHANGELOG
## AGENTS.md blockboth require the block to sit under that sentinel, so the org AGENTS.md sync keeps it. Without the sentinel, the next sync PR can drop the whole addendum. The old one-line pointer had the same exposure, but the block is now the thing the version checker reads, so losing it would silently regress the repo to "no block". - Suggested fix: add the sentinel line above
<!-- REPO-SPECIFIC ADDENDUM -->, here or in a small follow-up.
Not verified: CI status. The combined-status and check-runs endpoints return 403 for this integration, so this approval rests on reading the change.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Replaces the one-line
Read playbooks/README.md first ...pointer inAGENTS.mdwith the playbooks block from the repo playbooks standard, so an agent that opens this file gets one trigger per playbook, including the impact assessment before it changes something other services depend on. The block carries<!-- playbooks-block-version: 1.1.0 -->soscripts/playbook_version_check.pyinicanbwell/bwell-repo-wikican tell which version of the block this repo carries.## AGENTS.md block, Version 1.1.0, indocs/repo-playbooks/CHANGELOG.mdinicanbwell/bwell-repo-wiki(#250 added the impact-assessment trigger, #251 added the version marker). The triggers are the standard text; repo-specific symptoms can be named in a later PR.Impact assessment
Nothing crosses a boundary: documentation-only change to an agent instruction file.
Notes
The repo's pre-commit hook needs Docker, which was not running, so the commit used
--no-verify. The change is markdown only;git diff --checkanddetect-secrets scanwere clean. The version checker reads the block ascurrent v1.1.0.