Repository navigation
Make the example screen runnable and verify the advertised plugin behavior #13
Description
Problem
At audited main ab137d8, my-plugin/plugin.json has a nav entry and script but no top-level screen entry, and the repository contains no screen.html. screen.js expects plugin-my-plugin and counter markup. README calls this a complete working example, but custom-checks passes without exercising it.
Scope
Provide a minimal working screen/settings/routes example suitable for copying and renaming. Resolve the visualization type declaration so it accurately describes the example; do not introduce a highway renderer unless it is actually needed.
Acceptance criteria
- Add screen markup and its manifest entry; demonstrate counter interaction and loading persisted settings.
- Verify the example mounts through the supported host screen contract.
- Add focused automated tests for GET defaults, valid subset POST/persistence, invalid or unknown values, malformed JSON, and the 16 KiB body limit.
- CI runs these tests and fails when required screen markup or manifest references are missing.
- Document exact setup and verification commands, and check the copy/rename instructions against the working example.
Out of scope
Automatic issue execution, auto-merge, and a full plugin framework.
Activity
pullfrog commentedon Oct 13, 2026
pullfrog commentedon Oct 13, 2026
Implemented a runnable example screen and automated verification for the advertised plugin behavior. PR: #16
What landed:
my-plugin/screen.html+"screen": "screen.html"and"type": "utility"inplugin.json— the screen now mounts through the Host contract (verified againstplugins/__init__.py'shas_screengate andplugin-loader.js's hardcoded/api/plugins/<id>/screen.htmlfetch).tests/+requirements-dev.txt— 19 pytest cases covering GET defaults, valid-subset POST/persistence, invalid/unknown values, malformed/non-object JSON, and the 16 KiB limit (Content-Length fast path and chunked-stream path); manifest/screen-contract tests fail when required markup or references go missing. Tests discover the plugin viaplugin.json, so they survive rename.custom-checks.ymlnow validates the screen reference/nav container and runspytest.my-pluginREADMEs,AGENTS.md,CLAUDE.md,CHANGELOG.md) updated with exact setup/verification commands and rename instructions covering every hard-codedPLUGIN_ID.Task list (8/8 completed)
big-pickle(free) ｜ 𝕏feat: make the example screen runnable and verify it in CI (#13)
pullfrog commentedon Oct 13, 2026
The implementation for issue #13 is already complete and merged (PR #16). The codebase has screen.html, updated plugin.json with screen entry and correct type, comprehensive tests (19 passing), CI workflow updated, and all docs are in place. No action needed.
big-pickle(free) ｜ 𝕏