docs(planning): log the AME feature-surface research todo - #145
Merged
Conversation
The 2026-08-01 prior-art spike read Admin Menu Editor architecturally, scoped to Phase 20's questions — identity, apply model, submenu targeting, hook order, storage. Those findings shipped as COMPAT-04/07/14. It never examined AME as a product. Its whole feature-facing output is one "market signals" section, and all four gaps it named are now spent: import/export is queued, reparenting is out of scope, per-role deny shipped, and inline editing UX is the premise rather than a gap. The one artifact meant to say what to build next has nothing unclaimed left in it — and after Phases 27/28 there is no milestone. The todo scopes a second pass over AME free/Pro/add-ons as a product, sorting each feature into have-it / deliberately-not / already-queued / unclaimed / anti-feature. Deliverable is a NOTE on the 19-FEASIBILITY-NOTE model, and "nothing worth adopting" is written in as a legitimate verdict so the pass is not padded to justify itself. Constraints are pre-loaded so a finding gets rejected in the note rather than by a later phase: cosmetic-only, the two-icon budget from DECISION-settings-surface, borrow-patterns-not-code, and editing-happens-on-the-menu. New candidates rank against the existing queue — losing to something already queued is a finding too. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
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
todos/pending/2026-08-10-ame-feature-surface-research.mdand its STATE.md pointer.Why
The 2026-08-01 prior-art spike read Admin Menu Editor architecturally, scoped to Phase 20's questions — identity, apply model, submenu targeting, hook order, storage. Those findings shipped as COMPAT-04/07/14.
It never examined AME as a product. Its entire feature-facing output is one "market signals" section, and all four gaps it named are now spent:
2026-07-03-config-presets-export-import— unplannedSPEC.mdv1, gated on highlightingThe one artifact meant to say what to build next has nothing unclaimed left in it — and after Phases 27/28 there is no milestone.
What the todo scopes
A second pass over AME free / Pro / add-ons (including the free build's
modules/, which the prior read skipped), sorting each feature into have-it / deliberately-not / already-queued / unclaimed / anti-feature. Deliverable is a NOTE on the19-FEASIBILITY-NOTE.mdmodel, and "nothing worth adopting" is written in as a legitimate verdict so the pass is not padded to justify itself.Constraints are pre-loaded so a finding gets rejected in the note rather than by a later phase: cosmetic-only (with
SPEC.mditem 7's IN TENSION flag called out), the two-icon budget fromDECISION-settings-surface.md, borrow-patterns-not-code, and editing-happens-on-the-menu. New candidates rank against the existing queue — losing to something already queued is a finding too.Architecture is explicitly out of scope, as is other prior art ("Wider Admin Menu" / "Hide Admin Menu" belong to
SPEC.mditems 9 and 10).Risk
Planning docs only. No plugin code, no tests affected.
🤖 Generated with Claude Code