cut-releaselisted

# Release a Foundry plugin edition Use this workflow only for an explicit release request. Establish the plugin, edition and intended version from that request and the current repository state. If the edition is ambiguous, resolve it before writing metadata. Running in a particular assistant does not by itself choose the edition being released. ## Sources of truth | Edition | Plugin metadata | Catalog | Version owner | | --- | --- | --- | --- | | Claude | `<plugin>/.claude-plugin/plugin.json` on Claude | `.claude-plugin/marketplace.json` in Foundry | the Claude catalog entry | | Codex | `<plugin>/.codex-plugin/plugin.json` on Codex | `.agents/plugins/marketplace.json` in Foundry | the native plugin manifest | Both catalog entries identify the plugin repository, platform ref and full validated commit SHA. Claude's version and source.sha move together. A Codex release updates its native version and then pins that exact integrated commit; do not introduce a Claude-style version field into the Codex catalog. Hush/Codex is not installable until its package and validation exist. Do not create a release or add it to the catalog merely because the branch exists. ## Prepare a reviewable release 1. Locate Foundry and the intended plugin checkout. Check its branch, HEAD, working tree and published refs. Confirm its physical working directory with `git rev-parse --show-toplevel`; worktree-list output alone can identify a submodule's gitdir instead. Preserve other working