release-readinesslisted

# Release Readiness ## Purpose Prevent publishing a skills repo with inconsistent metadata, stale docs, or unverified adapters. ## Preserves Operational release judgment. ## Required Evidence - Release target and version. - Changed files since last release or tag. - Adapter manifests, license files, changelog, and README. - Gate results and known limitations. ## Failure Signs - Version appears in one manifest but not another. - Release notes claim behavior not backed by files or checks. - Publishing is recommended without adapter or license review. ## When To Use - A tag, package, plugin, or public release is planned. - Runtime adapter metadata changed. - License, changelog, README, or install instructions changed. - A release candidate needs a final readiness decision. ## When Not To Use - No publish, tag, or distribution action is planned. - The task is only checking a single PR; use diff-interrogation. - The task is adding a skill; use skill-authoring-gate first. ## Inputs Expected - Target version and release scope. - Diff or commit range. - Manifest, license, changelog, README, and adapter files. - Results from prod-gate and optional scans. ## Output Expected ```md Release target: Version surfaces: Public docs: Adapters: License and notices: Checks: Blockers: Release decision: ``` ## Process 1. Identify every version and distribution metadata surface. 2. Check changelog, README, catalog, license, and notice files for accurate release claims. 3. Verify a