docs(open_feature): make scoped agent guidance discoverable#6029
Merged
leoromanovsky merged 4 commits intoJul 14, 2026
Conversation
Contributor
|
👋 Hey @DataDog/ruby-guild, please fill "Change log entry" section in the pull request description. If changes need to be present in CHANGELOG.md you can state it this way **Change log entry**
Yes. A brief summary to be placed into the CHANGELOG.md(possible answers Yes/Yep/Yeah) Or you can opt out like that **Change log entry**
None.(possible answers No/Nope/None) Visited at: 2026-07-13 15:42:26 UTC |
🎉 All green!🧪 All tests passed 🎯 Code Coverage (details) 🔗 Commit SHA: b811b5b | Docs | Datadog PR Page | Give us feedback! |
leoromanovsky
commented
Jul 13, 2026
leoromanovsky
marked this pull request as ready for review
July 13, 2026 17:14
TonyCTHsu
approved these changes
Jul 14, 2026
leoromanovsky
deleted the
leo.romanovsky/open-feature-agents-customer-review
branch
July 14, 2026 15:06
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.
AI-generated: This PR includes a small AI-generated, repository-local Codex eval runner and fixtures.
Motivation
The scoped OpenFeature guide shipped in #5968 and was refined in #5989. However, after #5910 had merged
mastercontaining that guide, human review still had to explicitly redirect the contributor toAGENTS.md. A contributor should discover applicable guidance before beginning OpenFeature work, including during contribution-rotation handoffs.We turned that suspicion into a red eval before relying on a documentation change. Three fresh-session awareness cases cover OpenFeature work under
lib/,spec/, andsig/; running them against the exact pre-PR commit,7df73817ee, produced:The nested guide was discovered for work under
lib/, but not for the sibling spec and signature trees it claims to govern. That failing evidence is the motivation for this change.Changes
The root
AGENTS.mdnow explicitly routes OpenFeature code, spec, and signature work tolib/datadog/open_feature/AGENTS.md. A lightweight runner starts fresh, read-only Codex sessions and asserts that they identify both the root and scoped instruction files. The scoped guide's content is unchanged.Decisions
This first phase proves discovery only; it does not rewrite the scoped guide or test individual lint conventions. The evals remain dependency-free, manual, ephemeral, read-only, and outside CI and LLMObs for now.
Next steps
The stacked follow-up #6034 adds a writable content-adherence eval proving that agents find and run the configured RuboCop rules, then independently verifies that the resulting code is lint-clean. It depends on #6032 making the root RuboCop workflow operational and keeps individual rules in executable configuration rather than duplicating them in
AGENTS.md.Validation
Running the same cases on this PR produces:
The runner also passes Ruby syntax, JSON parsing, and
git diff --check.Impact
Future OpenFeature contributors and their tools should have the scoped guide in context before changing code, specs, or signatures. This should reduce guidance-related review churn while leaving human reviewers focused on architecture and APM customer needs.
Change log entry
None.