[docs] charter: link the accepted BiDi support boundary record - #17928
Merged
Merged
Conversation
17670 was accepted on 2026-07-23; the charter states each decision is marked ADR pending until its record is accepted, at which point the charter links it.
This was referenced Aug 28, 2026
This was referenced Aug 31, 2026
This was referenced Sep 8, 2026
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
1 participant
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.
🔗 Related Issues
Follow-up to #17670 (accepted 2026-07-23) and the Selenium 5 charter, #17717.
💥 What does this PR do?
Links the accepted BiDi support boundary record from the Selenium 5 charter.
docs/plans/selenium-5.mdstill marked that decision_ADR pending_, butdocs/decisions/17670-bidi-implementation-boundaries.mdis on trunk withStatus: Accepted.The charter's own rule (line 16-18) says a decision is marked ADR pending "until its record is
accepted, at which point this charter is updated to link it" — so this is that update.
The other three required decisions (network async/event API, script and logging async/event API,
Selenium Manager released API) stay
_ADR pending_; their records are still open.🔧 Implementation Notes
Relative link to the record rather than to the PR, matching how the charter refers to in-repo
documents and so it keeps working for anyone reading the tree offline.
🤖 AI assistance
💡 Additional Considerations
Bookkeeping only — no behavior change. The charter will need the same edit for each remaining
record as it is accepted.
🔄 Types of changes