Skip to content

docs: state the content-boundary rules in AGENTS.md - #47

Merged
Pigbibi merged 1 commit into
mainfrom
chore/content-boundary
Oct 31, 2026
Merged

Pigbibi merged 1 commit into
mainfrom
chore/content-boundary

Conversation

@Pigbibi

@Pigbibi Pigbibi commented Oct 31, 2026

Copy link
Copy Markdown
Contributor

The Do not section gains four rules, between content-boundary markers so the
block is one copy that can be checked and replaced rather than a paragraph that
drifts per repository.

They exist because nothing else reaches an agent before it writes. The checkers
run afterwards and read Markdown only, so a real bucket name typed into a
workflow, a fixture or a contracts.py passes every layer we have.

The four are written as instructions rather than principles: which placeholder
to use, where the real value comes from, why a hash is not anonymisation, and
how to tell whether a change leaked.

scripts/check_style.py now requires the block, so deleting it fails the build
instead of quietly returning the repository to the state this change fixes.
scripts/test_style.py pins that requirement, and both files plus the
.gitignore block are the organisation's canonical copies.

@Pigbibi
Pigbibi merged commit cc3d2a7 into main Oct 31, 2026
3 checks passed
@Pigbibi
Pigbibi deleted the chore/content-boundary branch October 31, 2026 07:18
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.

1 participant