Issue #182: resolve marketplace install pending state

[NWYLZW]

Root cause and user impact

Marketplace install selection was split across consumers instead of being owned by a shared route-level controller. Overlapping actions could therefore disagree about the active selection, while catalog refreshes and plugin runtime updates could race the pending state. Users could see an install remain pending, target the wrong selection, or fail to recover cleanly after an error.

What changed

• Introduced a shared, route-owned marketplace selection controller.
• Deduplicated actions by the exact scope + marketplace + plugin + target identity.
• Added explicit failure handling and retry behavior.
• Protected selection state from catalog-refresh and plugin-runtime races.
• Updated marketplace consumers and focused regression coverage for selection, refresh authority, and pending-state behavior.

Validation

Passed:

• dprint
• ESLint
• diff review
• static review

Not run because the dependency-backed validation environment was unavailable:

• Vitest
• typecheck
• build
• browser validation

Closes #182

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
oneworks-dev	Ready	Preview	Jul 30, 2026 6:00am

[github-actions]

Experience Review

Before merge, make sure the PR body contains this completed checklist:

## Experience Review
- [x] 已判断是否需要沉淀经验
- [x] 如需要，已运行 `$post-task-experience-review`
- [x] reviewer PASS 后才进入 merge

Checklist to confirm:

• Decide whether this PR produced reusable project experience.
• If experience should be captured, run $post-task-experience-review.
• Merge only after the independent reviewer reports PASS.

[NWYLZW]

Superseded by #334, which rebuilt the reviewed Issue #182 scope on exact main 25161a7 and passed all exact-head required checks before merging normally as 3a36626. Issue #182 is closed. Closing this draft unmerged for audit continuity; its branch is intentionally preserved.