[Reconciliation][P2] Align legacy marketplace metadata and declare plugin maintenance ownership #352

Parent workstream: #323
Epic: #318

Priority: P2 · Audit findings: SP-07, SP-08

Outcome and problem

The standalone marketplace README installs an unregistered recoup-catalog-deals identifier. Its platform/content versions disagree across host registries and actual child manifests. At the same time, the consolidated Skills repo describes one authoring tree while the separate marketplace still gives independent plugin-authoring guidance without a clear support/parity policy. Separate package families may coexist, but their maintenance and migration responsibilities must be explicit.

Scope and ownership

• Owning repositories: recoupable/marketplace, recoupable/skills, and the four registered standalone plugin repositories.
• Correct install names and align per-host registry versions with the selected child releases; reconcile the platform gitlink with the intended external source.
• Declare each standalone package maintained, legacy-with-support, or migration-only, with an owning source and upgrade path.
• Align AGENTS/README authoring guidance with that decision and add missing child instructions or correct the registry's claim that each child has them.
• Add validation for registry/child name, version, source and install-example agreement; define generation/parity checks if more than one maintained distribution shares behavior.

Planning is tracked in Mono. Implementation and release PRs belong in the owning repositories under their current branch rules.

Acceptance criteria

• Every documented install identifier exists in the referenced marketplace; recoup-catalog-deals is removed or an explicitly supported alias is implemented.
• Claude/Codex/Cursor child versions and both marketplace versions describe the same selected release; pinned source refs match the release policy.
• A maintainer can determine the owning repository for a new capability and where a shared bug fix must propagate from maintained instructions alone.
• Each legacy package has an explicit support/migration statement; no package is removed or silently substituted merely to eliminate duplication.
• A failing fixture demonstrates detection of a mismatched name/version/source, and all registry JSON/manifests validate.
• At least one documented install path is verified with the selected package/release; other host verification remains explicitly recorded rather than inferred.

Evidence and existing work

Baseline: October 10, 2026 audit of July 10–October 10 merges. Recheck current source and existing tracker comments before implementation. Source findings do not establish authenticated production behavior.

• Source evidence 1
• Source evidence 2
• Source evidence 3
• Source evidence 4
• Source evidence 5
• Source evidence 6
• Source evidence 7

Related existing work:

• fix: publish catalog plugin 0.3.1 without Stop hook marketplace#13 — catalog 0.3.1 release already reconciled.
• fix: remove catalog Stop reviewer (0.3.1) recoup-catalogs-plugin#5 — catalog Stop-hook fix already merged; preserve it.
• Rename package to recoup-plugin skills#182 — consolidated recoup-plugin identity migration.

Continue or reconcile the linked implementation work; this ticket owns the stated audit correction and does not replace the original feature tracker.