Conversation
Update dependencies and fix OAuth handling
Fix serialization of Cursor hook matcher to use matcher field
* Point public docs and install URLs at capa.sh * Point installer scripts and websiteUrl at capa.sh * Point installer scripts and websiteUrl at capa.sh * Point installer scripts and websiteUrl at capa.sh * Point installer scripts and websiteUrl at capa.sh * Update claude-plugins bundled adapter pin after capa.sh URL change
manager.view() was cloning giuseppe-trisciuoglio/developer-kit via inspectPlugin, which often exceeded bun's 5s timeout on main CI. Co-authored-by: Antonio Zaitoun <antonio@zaitoun.dev>
Drop the process-wide getOrCreateSnapshot spy (it can leak into parallel files on Windows) and view through loadClaudeMarketplaceAdapter without a db so inspectPlugin is not attached. Retry SQLite temp-dir cleanup on Windows after close. Co-authored-by: Antonio Zaitoun <antonio@zaitoun.dev>
…meout-d748 Keep marketplace fixture tests offline so main CI stays green
PR Summary by QodoMigrate public links to capa.sh and keep marketplace tests offline
AI Description
Diagram
High-Level Assessment
Files changed (14)
|
Code Review by Qodo
1. Manager view path untested
|
| const adapter = loadClaudeMarketplaceAdapter(slug); | ||
| const detail = await adapter.view({ |
There was a problem hiding this comment.
1. Manager view path untested 🐞 Bug ⚙ Maintainability
The marketplace fixture test now calls the adapter directly, so it no longer verifies that the DB-backed registry can be viewed through RegistryManager.view, including loader resolution and timeout behavior. Regressions in the actual registry view path can therefore pass while this test remains green.
Agent Prompt
## Issue description
The marketplace fixture test bypasses `RegistryManager.view` by constructing and invoking an adapter directly. Keep the fixture offline while exercising the same manager-backed path used by the registry view handler.
## Issue Context
`RegistryManager.view` resolves the DB-loaded adapter and applies timeout handling, while the route handler delegates to that method. The direct adapter call validates marketplace parsing but cannot catch failures in manager loading or route integration.
## Fix Focus Areas
- src/server/__tests__/registries-routes.test.ts[541-592]
- src/shared/registries/manager.ts[100-112]
- src/server/registries-routes.ts[383-405]
ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools
Updating develop with main