Repository navigation
docs(agents): align AGENTS.md with fleet standard v1.1 - #1484
Merged
Merged
Conversation
🔍 Cora AI Code Review✅ No issues found. Code looks good! Review powered by cora-code · BYOK · MIT |
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.
What
Align AGENTS.md with the fleet AGENTS.md standard v1.1: (1) add the session-start continuity ritual (read team knowledge rooms, save decisions back, handoff entries); (2) replace the explicit attribution-ban paragraph with a neutral pointer to the ecosystem message standard (the policy text now lives in the internal standard doc, not in repo-visible files).
Why
Owner decision 2026-10-15: the attribution rule is fleet-wide and must not be spelled out in repositories; enforcement moves to tooling. AGENTS.md files carry only the session ritual and workflow guidance.
Testing