WA-NEW-014: Establish plugin modernization inventory + tracking (workarea-commerce/*) #638
Description
Context
Workarea modernization will extend beyond workarea-commerce/workarea to many workarea-commerce/* plugins. Workarea is currently the only active Rails/Ruby/ES/Mongoid project family, so we need a repeatable way to track plugin upgrades.
Goal
Create a concrete inventory of plugin repos and a tracking plan (issues + board) so dependency upgrades can be rolled out consistently without requiring downstream client code changes.
Scope
- Enumerate
workarea-commerce/*repos that are Rails/Ruby/Workarea plugins (exclude archived where appropriate) - Categorize by risk/complexity (e.g., adds models, ES queries, admin UI, background jobs)
- For each repo, create a placeholder tracking issue (or a per-repo mini-epic) describing the upgrade work needed
- Decide how we want to track multi-repo work in the existing Workarea — SDLC project board vs a separate board
Acceptance Criteria
- A checked-in inventory list (markdown) with repo names + purpose + priority
- A set of GitHub issues created to represent the plugin upgrade queue
- Clear guidance on how the dispatcher should route items into project board + labels
Notes
- Cross-project policy/config changes should be discussed in the multi-project channel; this issue is about the Workarea ecosystem execution plan.