Docs: plugin registry layout and plan (#552)

[compscidr]

Spec addendum and implementation plan for piece B of #552 — the registry and seed plugin repos:

• https://github.com/goblogplatform/goblog-plugin-hello (v1.0.0 released)
• https://github.com/goblogplatform/plugins (PR GitHub auth #1 pending; publishes https://goblogplatform.github.io/plugins/index.json)

🤖 Generated with Claude Code

[Copilot]

🟡 Changes recommended

The new docs contain an internal inconsistency around the seed plugin’s display_name (“Hello” vs “Hello (example)”) that could mislead implementers and submitters about the contract.

Get a fresh assessment by requesting another Copilot review.

Pull request overview

Adds a spec addendum and a detailed implementation plan for “piece B” of the plugin directory work (#552): the curated registry repo (goblogplatform/plugins) and the seed example plugin repo (goblogplatform/goblog-plugin-hello), including CI validation and GitHub Pages publishing shape.

Changes:

• Documented the concrete file/layout decisions for the registry + seed plugin repos in the plugin directory design spec.
• Added a step-by-step implementation plan (commands, code skeletons, tests, workflows, Pages go-live checklist) for building and publishing the registry output (index.json + per-plugin JSON).

File summaries

File	Description
docs/superpowers/specs/2026-09-14-plugin-directory-design.md	Adds “Piece B” concrete repository layouts and key decisions (registry structure, validation/publish behavior).
docs/superpowers/plans/2026-09-15-plugin-directory-registry.md	New end-to-end implementation plan for the registry and seed plugin repo, including CLI, tests, workflows, and go-live steps.

Review details

• Files reviewed: 2/2 changed files
• Comments generated: 2
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!