You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Cursor target (.cursor-plugin/) has not been live-install verified. During FP0006 follow-up verification, the Codex and opencode targets both passed every structural check but failed on the real CLIs (see #70), so structural validation alone gives false confidence here. Cursor is the only target that could not be driven headlessly (desktop app), so it is the most likely to still be broken.
Why this is likely broken
Both other plugin-format targets needed real fixes that structural validation missed:
Codex (fix: Codex + opencode plugin install issues (live-verified) #70): marketplace source had to become an object { "source": "local", "path": "..." }, and the manifest had to move to <pluginDir>/.codex-plugin/plugin.json with skills/ as a sibling (not nested). The survey wrongly assumed Codex honored the legacy .claude-plugin marketplace format.
Cursor's survey (packaging/survey/cursor.md) was written from docs, not a live install, and may have the same kind of wrong assumption about manifest location, the marketplace/source shape, or the hooks format.
What to verify against real Cursor (2.5+)
Install Cursor 2.5+ and side-load .cursor-plugin/ (or /add-plugin).
Confirm the manifest is accepted (the _generated banner key tolerated) and that skills, commands, and agents all load.
Confirm the blocking beforeShellExecution install hook actually fires and that bash ./hooks/scripts/ensure-festival.sh resolves with the cwd Cursor uses (the path-resolution assumption is unverified).
Re-check the marketplace/distribution shape Cursor actually expects (compare against the Codex finding).
Done when
.cursor-plugin/ installs and exposes its surfaces on real Cursor 2.5+, or the generator + cursor_target_check are fixed until it does, with the fix verified against the live CLI/app (same bar as fix: Codex + opencode plugin install issues (live-verified) #70).
packaging/survey/cursor.md is corrected to the verified-real format.
Reference: FP0006 (#68), Codex/opencode live-install fixes (#70). Auto-install foundation (release with fest/camp binaries) is already confirmed working.
Summary
The Cursor target (
.cursor-plugin/) has not been live-install verified. During FP0006 follow-up verification, the Codex and opencode targets both passed every structural check but failed on the real CLIs (see #70), so structural validation alone gives false confidence here. Cursor is the only target that could not be driven headlessly (desktop app), so it is the most likely to still be broken.Why this is likely broken
Both other plugin-format targets needed real fixes that structural validation missed:
sourcehad to become an object{ "source": "local", "path": "..." }, and the manifest had to move to<pluginDir>/.codex-plugin/plugin.jsonwithskills/as a sibling (not nested). The survey wrongly assumed Codex honored the legacy.claude-pluginmarketplace format.Plugin export is not a function) because it exported aversionstring alongside the function.Cursor's survey (
packaging/survey/cursor.md) was written from docs, not a live install, and may have the same kind of wrong assumption about manifest location, the marketplace/sourceshape, or the hooks format.What to verify against real Cursor (2.5+)
.cursor-plugin/(or/add-plugin)._generatedbanner key tolerated) and that skills, commands, and agents all load.beforeShellExecutioninstall hook actually fires and thatbash ./hooks/scripts/ensure-festival.shresolves with the cwd Cursor uses (the path-resolution assumption is unverified).Done when
.cursor-plugin/installs and exposes its surfaces on real Cursor 2.5+, or the generator +cursor_target_checkare fixed until it does, with the fix verified against the live CLI/app (same bar as fix: Codex + opencode plugin install issues (live-verified) #70).packaging/survey/cursor.mdis corrected to the verified-real format.Reference: FP0006 (#68), Codex/opencode live-install fixes (#70). Auto-install foundation (release with fest/camp binaries) is already confirmed working.