Question: is the plugin registry still accepting community submissions? #71

Question: is the plugin registry still accepting community submissions?

This is a process question, not a re-pitch. I have two PRs open (#69, #70) that have received no review, and I noticed the review queue looks stalled generally rather than specific to my submissions.

What I'm seeing:

• Last commit to main: 2026-09-21 (feat(dynamic-workflow): tamper-evident integrity ledger for repair_cache and events #48).
• No review on feat(plugins): add BoozeLee/awesome-mcode-local-skill #69 or feat(plugins): add BoozeLee/omarchy-audit #70, both open since 2026-10-02.
• Other open PRs with substantial discussion and no review: feat(mcode-island): add sub-step progress fields to status.json (v0.4.0) #62 (11 comments), fix(dynamic-workflow): fail loud on executor failure; extract unambiguous JSON from prose #57 (4), Add Plugin: html2video-for-mcode #41 (38).

What I'd like to know:

1. Is community Plugin submission still being accepted, or is review paused while the registry is reorganised?
2. If it's active, roughly what should a contributor expect in review latency? CONTRIBUTING.md describes what review covers but names no reviewer or target, and GOVERNANCE.md notes the project "may introduce additional reviewer and maintainer roles as contribution volume grows" — so I can't tell whether review is expected to be staffed or best-effort.
3. If my two PRs are fine as they are, no reply is needed — I just don't want them to sit indefinitely if something is expected from the contributor (a rebase onto main, a different manifest shape, splitting the Skill and the MCP server into two PRs, and so on).

For context on my two PRs, both are small and self-contained, and each ships its own verification evidence in the description:

• feat(plugins): add BoozeLee/awesome-mcode-local-skill #69 — four project Skills packaged for the registry. Includes a copyable example, expected result, requirements, and network/data sections.
• feat(plugins): add BoozeLee/omarchy-audit #70 — a dependency-free stdio MCP server plus a Skill for static security triage of an Omarchy checkout. Passes npm run validate (OK plugin BoozeLee/omarchy-audit, 29 hosted Plugins validated). It's a triage tool, not a security fix, and isn't aimed at any bounty.

If the answer is that the queue is simply backed up, I'm happy to wait. I just didn't want to assume the repo was dormant by design versus by circumstance.

Thanks for reading.