AGENTS.md: point at CLAUDE.md and stop pointing outside this repository Same defect CLAUDE.md carried and the same fix. This file linked to ../_standards/STANDARDS.md and described a collection of nineteen plugins, neither of which exists for anyone who has this repository and nothing else -- which is everyone who clones it, and, until plugin_deploy.sh was corrected, everyone who downloaded the zip. It is a signpost, so it now signposts the one file that is here.
CLAUDE.md: make it stand on its own in this repository This file ships. The deploy rsync copies $SRC_DIR/*, which skips dotfiles -- so .claude/ and .github/ never leave -- but CLAUDE.md is not a dotfile and is not excluded, so it goes to wordpress.org with every release and lands in the zip every user downloads. Anyone reading it has this repository and nothing else. It did not read that way. It pointed at a standards document in a parent folder that is not part of this repository, cited section numbers from it, named sibling plugins as though the reader had them, and dated its own claims -- including claims about which tests were last green, which are wrong the moment they change and which CI answers properly anyway. The test applied: could someone who cloned only this repository act on every line? Where the answer was no, the substance is restated here and the citation dropped. Nothing is lost by removing the pointers, because anyone working across the whole set is told to read the shared documents first regardless. What stays: what the plugin is, its data, its traps and why, its own commit hashes -- which do resolve here -- its hook and API names, and how to run its tests. Test *status* is replaced by how to run them.
CLAUDE.md: say what the e2e suite's state actually is The 'twelve suites _standards/RESUME.md lists as never run to green' pointed at a list that file no longer carries -- item 1 closed on 2026-08-05 and the list went with it. Eight plugins carried the reference, so eight had a cross-reference to nothing. Replaced with the state of this plugin's own suite, counted rather than copied, and explicit about which specs were actually run on 2026-08-05 and which were not. A suite nobody has run in one go still says so.
Tests: the migration assertion passes now, and the comment says so The comment above it still read "This assertion currently fails, and it is right to". The fix landed -- migrate() and write() pass the explicit default, and the branch that adds the row is taken on the admin path -- so the comment was telling the next reader to wave through a real regression. Rewritten to say what the assertion pins rather than what it once caught: this is the admin_init path, opening the settings screen is what makes it that path, and a migration test that does not register the setting first is testing WP-CLI. The explanation of the original defect is kept, because the shape is worth recognising, but it is now in the past tense and ends in a warning not to weaken the test to the reactivation path. Verified rather than assumed: all 6 tests in upgrade.spec.js pass.