Skip to content

WordPress and GitHub Workbench follow-up - #1837

Open
accesswatch wants to merge 2 commits into
mainfrom
codex/workbench-combined-2026-11-10
Open

accesswatch wants to merge 2 commits into
mainfrom
codex/workbench-combined-2026-11-10

Conversation

@accesswatch

Copy link
Copy Markdown
Contributor

Summary

  • Route GitHub and WordPress management entry points to their Workbenches and remove the classic-window preference/fallback.
  • Add QAF field-type conversion previews, common Gravity Forms field conversion with full-form conflict checks and undo, and Paid Memberships Pro reads/ability support.
  • Add a small WordPress Practice Site blueprint and GitHub Markdown issue-template prefill/preview.
  • Import both accepted Workbench PRDs, align the implementation-status record and manuals, and regenerate HTML/EPUB artifacts.

Validation

  • Commit hooks passed: Ruff format/check, banned-pattern, dialog-button, module-size, announce-gap, and docs HTML/EPUB parity.
  • Editor diagnostics found no errors in the changed modules.
  • Unit tests and the live WordPress Playground were not run.

Remaining work

This commit records a substantial implementation increment; it does not complete every accepted PRD phase. GitHub coverage snapshot/gate, discussion/template builder work, Beyond Parity, Across Repositories/Repository Sets and the fourth sweep remain. WordPress Playground runtime smoke/credential handoff, remaining WP-R/W0-W8 items, live-site checks, and assistive-technology acceptance remain documented in docs/planning/workbench-implementation-status.md.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant