oss-release-engineeringlisted

# OSS Release Engineering Make every release a promotion of one verified source identity and one retained artifact set. Encode identity in tags and manifests, reconcile each external target before mutation, and prove terminal state from target artifacts rather than workflow appearance. ## Operating contract - Inspect repository instructions, release scripts, workflow triggers, environments, package manifests, generated files, and current external state before editing. - Preserve unrelated dirty work. Never hide it with stash, checkout, reset, rebase, or mass formatting. - Define immutable identities before running CI: source SHA, tag, package name/version, artifact digest, deploy revision, and store build tuple. - Build a releasable artifact once. Promote that exact artifact through CI, deploy, registry, and TestFlight/App Store; never rebuild downstream. - Treat registry, deployment provider, GitHub Release, and store as independent state machines. - Reconcile before every retry. Classify state as absent, exact, conflicting, or unknown; mutate only when absent. - Verify terminal target state. A green workflow or uploader exit is intermediate evidence. - Record exact commands, workflow/run IDs, source SHA, artifact digests, target IDs, and URLs. All shell blocks are Bash unless labeled otherwise. Replace placeholders explicitly; do not let agents infer package paths, store apps, accounts, or environments from proximity. ## 1. Inventory release identities and targets Run