[codex] Cover stale termmeta semantic references#174
Merged
Conversation
Merged
adamziel
added a commit
that referenced
this pull request
May 16, 2026
## Release `v0.1.22` Version bump and release metadata update for `v0.1.22`. **Changelog draft:** * Document v0.1.21 release gate evidence ([#162](#162)) * Cover taxonomy menu reference validation ([#163](#163)) * Cover navigation block reference validation ([#164](#164)) * Cover media filesize drift validation ([#165](#165)) * Cover generated media filesize drift validation ([#166](#166)) * Cover missing media metadata validation ([#167](#167)) * Cover stale post_parent semantic references ([#168](#168)) * Cover stale term parent semantic references ([#169](#169)) * Cover stale post author semantic references ([#170](#170)) * Cover stale menu parent semantic references ([#171](#171)) * Cover stale usermeta semantic references ([#172](#172)) * Cover stale postmeta semantic references ([#173](#173)) * Cover stale termmeta semantic references ([#174](#174)) * Cover stale term taxonomy semantic references ([#175](#175)) **Full changelog:** v0.1.21...release/v0.1.22 ## Next steps 1. **Review** the changes in this pull request. 2. **Push** any additional edits to this branch (`release/v0.1.22`). 3. **Merge** this pull request to publish `v0.1.22`. Merging will automatically build ForkPress binaries, create a GitHub release, and update the Homebrew formula.
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.
What it does
Adds a focused WordPress semantic validator regression for
wp_termmeta.term_idreferences. The fixture covers a source branch deleting a term while the target edits scalar and JSON termmeta rows that still point at that term.Rationale
wp_termmeta.term_idis the ownership edge from term metadata to its WordPress term. A row-level merge can preserve target metadata edits and apply the source term delete, but that leaves orphaned term metadata unless a semantic validator reports the stale owner for review.Implementation
The new discovered validator scans termmeta rows with
term_id > 0, verifies the referenced term row still exists, and emitsplugin-wp-termmeta-missing-termfindings. The test asserts that the term delete remains staged, target scalar and JSON metadata edits remain visible, and plugin audit output identifies the missing term, staleterm_idfield, and JSON metadata row.The merge reliability matrix now records termmeta owner coverage alongside existing taxonomy relationship/parent, postmeta, usermeta, menu, media, comment, and option reference coverage.
Testing instructions