Always enforce strict publish-controller contracts and review hygiene

For publish-controller changes, require implementation and tests to honor documented canonical formats and security boundaries exactly. Validate that values consumed by workflows come only from the authoritative canonical header, reject malformed inputs rather than silently continuing, preserve unrelated issue-body bytes during narrow updates, and cover failure paths with regressions. Check workflow details such as required action versions, cleanup of temporary files, and shell error propagation. Treat documentation/code parity, generated-artifact freshness, and absence of unrelated diff churn as merge requirements; do not accept passing happy-path tests as sufficient when contract violations or missing failure-path coverage remain.