fix: remove invalid glob from optionalPlugins; fix stale README links

[charliemeyer2000]

Summary

Follow-ups to the root-meta-plugin reorg (c54cabf / 4e763ea):

• "CognitionAI/**" in optionalPlugins is invalid and breaks the whole plugin. requiredPlugins/optionalPlugins entries are exact source refs — the runtime's spec parsing rejects any wildcard (manifest.rs: "spec parsing reuses source parsing, which rejects any wildcard, so no entry here can be a glob"), so the root manifest fails to parse and the meta-plugin is skipped at load with a warning, taking the entire baseline with it. Globs are only legal in forbiddenPlugins. Removed the entry.
• README: usacognition/plugin-template → CognitionAI/plugin-template (repo moved), and dropped the link to docs/governance.md (deleted in 4e763ea).

node scripts/validate-template.mjs passes.

Requested by: @charliemeyer2000

---

Devin Review

Status	Commit
🟢 Reviewed	a4ca0a7

[staging-devin-ai-integration]

Original prompt from charlie.meyer

SYSTEM:
=== BEGIN THREAD HISTORY (in #cmeyer-internal) ===
<most_recent_message>
Charlie Meyer (U0AS1R4CM5M) [ts=1785099102.637089]: @Devin help me build enablement materials for plugins. look at notion and C3: Git Plugin marketplace to undersatand what's going on, then help me underastand the state of how plugins work on cloud and local, what morgante is asking for, and then a plan to build this --action-model claude-fable-5-max

Let me search for those threads now.

Those results don't match what you're looking for. Let me search more specifically for mortgante (likely Marco Morgante or similar) talking about enablement materials for plugins with a GitHub repo example.

Got it — that's Morgante Pell. Let me search for his messages about enablement materials and plugins with a GitHub repo example.

Found one — now let me look for the second thread. The first one is from
<#C0B15442C4E>
(eng-plugins-rollout). Let me search for another message from Morgante about enablement/plugins with a usacognition repo example.

I'm clearly finding the same one thread. The second one may involve a
usacognition example repo specifically — let me check if there's another thread where Morgante shared one of those repos.

Let me check the thread on that first message and also look for the second thread — it may have been a reply in a thread rather than a top-level message, or it could be in a different channel.

I found one thread clearly. Now let me look more broadly — the second thread may involve a
usacognition example repo that Morgante shared, possibly in a different channel or as a reply.

I can see a reference in the search results to a second thread — Morgante's "Quick QA on plugins" thread from July 23 against <http://github.com/COG-GTM/plugins-marketplace|github.com/COG-GTM/plugins-marketplace>. Let me find that one.

Found both threads. Here they are:

Thread 1 — Tagging you for enablement materials ownership <https://cognition.enterprise.slack.com/arch... (2957 chars truncated...)

[staging-devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

⚙️ Control Options:

• Disable automatic comment, CI, and merge conflict monitoring

[staging-devin-ai-integration]

Devin Review found 1 potential issue.

Debug

Playground

[staging-devin-ai-integration]

🔍 Validator does not catch wildcard entries in required/optionalPlugins

The root cause of this PR (a glob string inside optionalPlugins) would not be caught by scripts/validate-template.mjs: the loop only walks plugins/*/.devin-plugin/plugin.json and never validates the root .devin-plugin/plugin.json, and the same-repo reference check at scripts/validate-template.mjs:95-112 skips non-object entries entirely. Adding a check that rejects string/glob entries in requiredPlugins/optionalPlugins and that includes the root manifest would prevent a regression of this exact failure, which silently disables the whole meta-plugin at load time.

---

Was this helpful? React with 👍 or 👎 to provide feedback.

Debug

Playground