Post-1.0 recurring distribution across agent marketplaces and directories

[BaseInfinity]

Goal

After the 1.0 harness release is certified, establish a recurring distribution program that makes the full Codex SDLC harness discoverable wherever supported agent workflows are credibly listed. This is broader than npm and broader than one plugin portal.

Present the product accurately as a Codex-first SDLC harness: installation and safe updates, repo-local lifecycle contracts, proof and review gates, guarded delivery, recovery, and release workflows. Do not undersell it as a small prompt or single skill.

Relationship to existing work

• Submit Codex SDLC Wizard to the universal Plugins Directory #66 remains the first-party Plugins Directory submission and its portal-specific acceptance work.
• Publish and verify codex-sdlc-wizard 1.0.0 #88 remains the 1.0.0 release gate.
• Rename wizard → harness, and inherit the checklist claude-sdlc-harness paid for #101 decides whether the public identity changes from codex-sdlc-wizard to codex-sdlc-harness before additional directory submissions.
• This issue is the recurring umbrella for broader distribution after 1.0.

Recurring distribution cycle

Run this checklist after 1.0 and again after meaningful major capability, compatibility, packaging, or naming changes:

• Inventory credible native marketplaces for every actually supported host.
• Inventory reputable third-party plugin, skill, agent, workflow, and package directories.
• Include Universal Agent Plugins as an initial candidate: https://github.com/777genius/universal-agent-plugins/blob/main/registry/README.md#submit-an-external-package
• Record each candidate, owner, submission route, package format, trust level, maintenance activity, and supported hosts.
• Confirm the canonical product name and repository after Rename wizard → harness, and inherit the checklist claude-sdlc-harness paid for #101; update or migrate older listings without creating competing identities.
• Reuse one canonical release artifact and documentation contract; do not fork weaker marketplace-specific implementations.
• Validate the exact published version on each claimed host before submission and after approval.
• Keep Codex CLI canonical. Treat Desktop, Work, other agents, and portable formats as additive support that must be proven rather than assumed.
• Publish accurate compatibility, install, update, support, privacy, license, and security information.
• Capture listing URLs, submission status, screenshots/evidence, version, and last verification date.
• Re-audit existing listings after major releases and periodically discover new credible directories.
• Remove or correct stale, abandoned, misleading, duplicated, or unsafe listings.

Scope and safety

• Submit only after 1.0 is released and the relevant host/package path is tested.
• Favor maintained, transparent directories with review or validation over indiscriminate promotion.
• Never claim compatibility merely because a package format is accepted.
• No submission may weaken the CLI workflow, SDLC contract, safety gates, or update-preservation behavior.

Completion model

This issue intentionally stays open as the recurring distribution ledger until the project adopts a dedicated recurring tracker. Individual marketplace submissions may use linked child issues or checklists and close independently.