docs(planning): add v1.5 research todo — analyze Admin Menu Editor prior art#97
Merged
Merged
Conversation
…ior art Capture a first-class research spike to study Jānis Elsts' Admin Menu Editor (w-shadow, 300k+ installs) for how it handles Maestro's tricky parts — menu identity/slug drift, replay against the live $menu/$submenu globals, submenu targeting without a stable id, per-role/per-user cosmetic hiding, separators, and third-party menu items. Framed as an adopt/avoid/differentiate analysis feeding v1.5 scoping; pairs with the two existing AME-referencing todos. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: b3b8fa361c
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Addresses Codex P2 on PR #97: the new v1.5 research spike was not surfaced in STATE.md's `Pending Todos` session-continuity index, so planning could miss or duplicate it. Add it alongside the two existing 2026-07-03 v1.5 candidates. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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
Adds a v1.5-candidate research todo to
.planning/todos/pending/: study Jānis Elsts' Admin Menu Editor (w-shadow, 300k+ installs, ~10+ yrs) for prior art on Maestro's tricky parts.This is the GSD roadmap-backlog capture mechanism — same as PR #85 ("capture v1.5 candidate todos"). It sits alongside the two existing pending todos that already reference Admin Menu Editor.
Scope of the captured spike (adopt / avoid / differentiate)
Slug::normalize()+Orderingresilience)$menu/$submenuglobals;admin_menuhook ordering; coexistence with other menu-filtering plugins.wp-submenuDOM-join is the fragile part)Deliverable is a short findings note feeding v1.5 scoping — no plugin code.
Risk
Planning-doc only. No runtime, test, or build changes.
🤖 Generated with Claude Code