docs: add repository agent constraints - #2
Merged
Conversation
Document CI-only script boundaries, release sequencing, and persistent-data migration and test requirements for automated contributors.
sljeff
marked this pull request as ready for review
July 29, 2026 17:25
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
AGENTS.mdcontaining durable agent constraints onlyScope
This intentionally contains no project overview, directory guide, architecture description, feature list, or copied tool-version pins. It changes agent guidance only; it does not trigger a release or change runtime behavior.
Validation
lib/models/helper.dartgit diff --checkand a sensitive-pattern scan on the new fileFollow-up found during the audit
The repository already has a 3 → 4 migration, but it has no automated migration coverage, and the current
onUpgradepath does not awaitdb.execute. This PR documents the required invariant without mixing a runtime refactor into the policy change; migration fixtures/tests and awaited execution should be a separate focused change.