Docs: WASM sub-project plans (registry v2, scholar plugin, v0.3.0) - #579
Conversation
…ect B) Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
…t D) Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
Copilot review overview
🟡 Changes recommended
The new plan docs contain a few internally inconsistent or likely-non-compiling code/test snippets (notably in fetch pagination/testing and go-pdk error APIs) that should be corrected to avoid misleading future implementers.
Get a fresh assessment by requesting another Copilot review.
Review effort: Lite
Findings: 1
Open (4)
What changed in this PR
This PR adds implementation-plan documentation for the next phase of the WebAssembly plugin ecosystem: a v2 WASM-only plugin directory contract, a new Scholar Publications WASM plugin project plan, and a goblog v0.3.0 plan to remove the compiled-in scholar plugin in favor of the directory-installed WASM plugin.
Changes:
- Add a detailed implementation plan for the Scholar Publications WASM plugin (settings, caching, fetch/render logic, jobs, packaging).
- Add an implementation plan for goblog v0.3.0 to remove the compiled-in scholar plugin and hide “unowned” pages until a plugin claims the page type again.
- Add an implementation plan for registry contract v2 (WASM-only, validate release assets, include runtime/allowed_hosts in the index) and hello v2 as the first WASM plugin.
| File | Description |
|---|---|
| docs/superpowers/plans/2026-09-19-scholar-wasm-plugin.md | Plan for implementing the Scholar Publications WASM plugin, including Go code snippets, tests, caching, jobs, and packaging. |
| docs/superpowers/plans/2026-09-19-goblog-v0.3.0-scholar-removal.md | Plan for removing the compiled-in scholar plugin in goblog and changing behavior for plugin-owned/unowned page types. |
| docs/superpowers/plans/2026-09-18-wasm-registry-v2.md | Plan for moving the plugin directory to a WASM-only contract and updating hello to a WASM release-asset-based plugin. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
| // maxPages bounds pagination; 10 pages × 100 papers is far beyond any article_limit. | ||
| const maxPages = 10 | ||
|
|
There was a problem hiding this comment.
Documented in 5fd63b5: article_limit is clamped to maxArticleLimit (500) in parseIntSetting — the plan now carries the clamp the shipped plugin has — so maxPages*pageSize = 1000 is the most a fetch needs; authors beyond that get the newest 1000 sorted and truncated.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
… clamp and run_job gating notes Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>


Plans for spec §3–5 of the WebAssembly plugin design, now implemented in goblogplatform/plugins#5, goblog-plugin-hello (v2.0.0), goblog-plugin-scholar#1, goblog#578 and compscidr/iac#627.
🤖 Generated with Claude Code