feat(den): manage Marketplace Plugin assignments

[reachjalil]

Summary

• load active Plugins as assignment candidates on a Marketplace detail page
• let Den administrators assign an existing Plugin to an exact Marketplace
• confirm relationship removal without deleting or archiving the global Plugin
• refresh resolved Marketplace detail and list state after mutations
• preserve admin gating, organization scope, and exact Marketplace/Plugin identifiers

User impact

Marketplace composition is now manageable from Den. Assignment and removal are clearly relationship operations; removing a Plugin from one Marketplace never mutates the Plugin itself.

Focused verification

• 3 focused Marketplace assignment tests passed
• 21 focused assertions passed
• Den Web TypeScript typecheck passed
• exact three-file candidate diff check passed

Proof status

The original candidate reached the real Den proof runtime, but managed OpenCode readiness stalled before an authenticated browser assertion could complete. A later exact-SHA verifier passed checkout/base/evaluator checks and failed closed because the generic legacy suite had no dedicated Den Marketplace-assignment meal. No browser assertion is being claimed as passed. This remains a draft pending that exact real-app flow.

Delivery budget lineage

• the first bounded run started at $4, 25 active minutes, and 125,000 model tokens
• authorized follow-up grants raised its effective runtime/token capacity while retaining the $80 hard dollar ceiling
• replacement runs used the same bounded outcome with an $80 ceiling
• the portfolio audit recorded $331.48 of conservative reservations across the retries; that is not confirmed provider spend
• final rebase, confirmation UX, and local verification used $0 additional Line Cook/provider budget

Review boundary

The product candidate is durable and locally verified. Keep this PR in draft until the dedicated Den Marketplace assignment flow passes against the exact head.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
openwork-landing	Ready	Preview, Comment, Open in v0	Jul 26, 2026 1:26pm

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
openwork-diagnostics	Skipped		Jul 26, 2026 1:26pm

[vercel]

@reachjalil is attempting to deploy a commit to the Different AI Team on Vercel.

A member of the Team first needs to authorize it.

[reachjalil]

CI triage note: the shared OpenWork Linux/macOS suite currently fails on apps/server/src/opencode-plugins/openwork-capabilities-knowledge.test.ts, which expects Settings > Connect while current dev documentation correctly says Settings > OpenWork Connect. I reproduced the same failure locally from the current dev base; this PR does not modify that test or documentation. The focused candidate checks listed in the PR body pass. Vercel authorization contexts are also external project-access gates, not feature test failures.