twitter-patch/AGENTS.md

Agent Instructions

Release-managed files

Agents must never create, edit, delete, restore, regenerate, format, resolve conflicts in, or stage files managed by the release pipeline.

Protected files:

• CHANGELOG.md
• gradle.properties
• patches-bundle.json
• patches-list.json
• README.md

These files are generated, updated, and committed exclusively by semantic-release. Manual changes or conflict resolutions cause divergence from the release commit and create pull or rebase conflicts.

When a task requires different generated content, change only the source, generator, or release configuration responsible for producing it. Leave every protected file untouched and tell the user that the next release must regenerate it.

If a protected file is conflicted, do not resolve, restore, or stage it. Stop and report the conflict to the user.

Do not run release or generation commands that modify protected files, including npx semantic-release, ./gradlew generatePatchesList, or .gitea/scripts/generate_patches_readme.py. A dry run is allowed only when it is proven not to write any protected file.