security(contract): verify upgrade artifacts and rollback behavior

[arisu6804]

Problem

An unauthorized or incompatible upgrade can corrupt stream schedules and supply accounting.

Objective

Deliver a production-quality improvement to contract upgrade authorization and artifact checks that creates measurable value for correctness, security, reliability, performance, or maintainability.

Implementation scope

• Require governed authorization, verify approved artifact identity, emit upgrade metadata, and guarantee failure before state mutation.

Acceptance criteria

• Unauthorized and mismatched artifacts are rejected; successful upgrades are auditable; rollback and compatibility behavior are tested.

Required validation

• Authorization, hash mismatch, state-preservation, event, and rollback tests.
• Existing tests and CI remain passing.
• Add regression coverage for the original failure mode.
• Do not weaken, delete, or skip unrelated tests to obtain a green build.

PR quality bar

• Keep the PR focused and explain design tradeoffs, compatibility impact, and test evidence.
• Avoid typo-only, documentation-only, cosmetic-only, or unrelated refactor submissions.

Out of scope

• Broad rewrites not required by the acceptance criteria.
• Changes to unrelated services, contracts, or user flows.