Wayfinder: Codex repository marketplace distribution

[ericjuta]

Destination

A clean checkout of askgina/plugins is directly installable through the Codex/ChatGPT repository marketplace without a preparatory build. The checked-in marketplace entry resolves to a self-contained OpenAI plugin source containing .codex-plugin/plugin.json, the canonical Ask Gina skills, MCP configuration, and assets.

Repository marketplace support keeps one editable skill source, preserves clean generated host artifacts, and does not change or imply authorization for OpenAI universal-directory submission, MCP deployment, package publication, installation, or release.

The route ends with an implementation-ready plan backed by an actual Codex marketplace installation proof and exact source, generation, conformance, and verification contracts.

Notes

• Repo/personal marketplaces are authoring, testing, and private-distribution catalogs separate from OpenAI's universal public directory.
• .claude-plugin/marketplace.json is a Claude-specific listing. Its legacy-compatible discovery path does not make its entry or source OpenAI-ready.
• plugins/ask-gina/targets/openai/ currently contains OpenAI metadata and assets but intentionally has no committed skills/; it is therefore not a directly loadable marketplace source.
• dist/ is ignored generated evidence. A marketplace entry pointing there would not support installation from a clean remote checkout.
• Canonical skills live under plugins/ask-gina/skills/; committed target skill copies and symlink-dependent sources remain prohibited.
• Prototype Prototype: prove clean-checkout Codex marketplace installation #21 proved that plugins/ask-gina/ can serve as the directly loadable Codex plugin root while the generated OpenAI target remains lean. The production migration boundary still belongs to the remaining tickets.
• Existing target conformance, archive security, public-boundary checks, artifact receipts, and clean verification remain authoritative.
• This map is planning-only. It grants no implementation, publication, installation, release, or deployment authority.
• After map closeout, the user explicitly authorized implementing and shipping the locked repository-marketplace change through merge and production proof. Universal-directory submission and MCP deployment remain unauthorized and out of scope.

Decisions so far

• Repository marketplace distribution contract locked; see Grill: lock Codex repository marketplace contract #22.
• Clean-checkout Codex marketplace installation and lean generated artifact proven; see Prototype: prove clean-checkout Codex marketplace installation #21.
• Canonical OpenAI source layout, generator/packer materialization, caller migrations, and lean artifact isolation specified; see Specify canonical OpenAI source and target generation migration #20.
• Marketplace conformance, isolated Codex smoke, authentication boundaries, and manual ChatGPT verification specified; see Specify Codex marketplace conformance and install verification #24.
• Final ordered implementation plan, CI/manual gates, post-merge remote proof, rollback, cleanup, and authority boundary locked; see Assemble Codex repository marketplace implementation plan #23.

Not yet specified

None beyond the ticketed frontier. New fog may surface from the remaining specification work and must be charted only when it can be stated sharply.

Out of scope

• OpenAI universal-directory submission or submission-portal work.
• MCP service behavior, deployment, OAuth implementation, or production credentials.
• Publishing npm packages, GitHub releases, or other remote distribution artifacts unless the destination is explicitly redrawn.
• New Ask Gina skills or product capabilities.
• Installing or enabling the plugin for users.
• Implementing the mapped change during charting.

[ericjuta]

Destination reached. Tickets #22, #21, #20, #24, and #23 lock the contract, prototype evidence, source migration, verification contract, and ordered implementation plan. The user separately authorized implementation through merge and repository-marketplace production proof; universal-directory submission and MCP deployment remain out of scope.

[ericjuta]

Implementation closeout (2026-08-26): PR #28 merged to main as e5f1deacaf388747741b427d48f8713183e57419. Main CI run https://github.com/askgina/plugins/actions/runs/33016327886 passed, including the authenticated Codex remote marketplace add/list/install/remove smoke against that exact immutable SHA. The repository remains private; #24 records the least-privilege clone-authentication update and the delivery owner's explicit waiver of the initial ChatGPT Desktop check. Accordingly, this closeout proves private repository-marketplace installation through Codex CLI but does not claim ChatGPT Desktop installation, OAuth connection, live tool execution, universal-directory publication, MCP deployment, or end-user release.

[ericjuta]

Security closeout amendment (2026-08-26): post-merge review identified that #28's ensuring finalizer could still launch plugin remove / marketplace remove after repository credential-file deletion failed. PR #29 fixes the trust-boundary ordering and is merged to main as 21484b15698a532d546af413b2441cf9cd8272e1. Main CI https://github.com/askgina/plugins/actions/runs/33017864779 passed, including the immutable-revision marketplace smoke and the injected deletion-failure regression. This supersedes the affected credential-isolation claim in the earlier closeout comment; the remaining Desktop/OAuth/live-tool limitations are unchanged.