WA-NEW-014: Plugin modernization inventory + tracking plan

[kitcommerce]

Fixes #638

What

• Adds an initial inventory of workarea-commerce/* plugin repos (workarea-*) with coarse category + risk/complexity triage.
• Captures repo link, default branch, and last updated date.

Tracking recommendation

• Keep notes/WA-NEW-014.md as the canonical index.
• For each plugin, open a single modernization umbrella issue in that plugin repo (label: modernization) with a standard checklist.
• Use WA-NEW-014: Establish plugin modernization inventory + tracking (workarea-commerce/*) #638 (or a dedicated tracking issue in workarea) to link to those per-plugin umbrella issues.
• Optionally, aggregate umbrella issues in an org-level GitHub Project ("Plugin Modernization").

Follow-ups

• Refine category/risk/complexity as we triage each plugin (this is intentionally a lightweight starting point).

[kitcommerce]

Dispatcher Build Gate Summary (local)

• rubocop (diff-only): N/A (no Ruby files changed)
• brakeman: skipped (per repo build gate config; disabled)
• tests: N/A (notes-only change)

Labeled .

[kitcommerce]

(FYI: my previous comment dropped the literal label name due to shell parsing. Confirming PR is labeled gate:build-passed.)

[kitcommerce]

Simplicity Review

Verdict: PASS_WITH_NOTES (LOW)

The doc is already fairly minimal for a 117-repo inventory and proposes a pragmatic tracking loop (canonical index → per-plugin umbrella issue → single central tracking issue, with Projects optional).

Notes / Suggestions

• Define an explicit minimal umbrella-issue template to keep tracking uniform and reduce per-plugin decision-making (e.g., Target Ruby/Rails, CI green, release + changelog, upgrade notes).
• Reduce maintenance burden of the 117-row markdown table: consider CSV/JSON source with generated markdown, or trim fields to the minimum and move subjective Risk/Complexity into per-plugin umbrella issues. Also add a snapshot date + update cadence line.
• Label strategy: make only one label required (e.g., modernization); keep optional labels only if there’s a concrete workflow.
• Scope clarity: explicitly note Risk/Complexity are initial guesses for prioritization (or omit them from the inventory table).