Repository navigation
docs: rewrite the agent docs and fix the last test isolation leaks - #3425
Merged
Merged
Conversation
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.
Why
The agent docs, rules and skills still described the old test system: shards, gate jobs, the quarantine file and lint-as-tests. A 10-iteration soak of the Unit plan also found four tests that leak state past their case.
Change
.shared; each pairing test gets its own, so the rate limiter no longer carries over.scripts/clean-test-residue.shlists what older test runs left behind. Dry run unless--apply.Verified
Unit plan, 10 iterations with
-run-tests-until-failure: 0 failures. A Unit run leaves no new EphemeralDefaults dirs.verify.sh agent-docspasses.Not in this PR
verify.sh docsfails, the same as on main.