Streamline release qualification

[Gandy2025]

Summary

• separate exact-candidate, payload, and third-party tool evidence scopes
• add a fast release profile that reuses compatible payload evidence for documentation-only candidates
• keep the complete dual-provider Gate for multi-seam behavior changes, supported-host/model changes, or incompatible payload evidence
• allow one exact-candidate authorization to cover the complete publication transaction
• reduce the tag-coordinate smoke to the minimum anonymous install/remove and identity checks needed before publication

Why

The previous policy invalidated all install and model evidence whenever any candidate commit changed. That made release-policy or documentation fixes trigger the same full dual-provider Gate as a behavior change, even when skills/run-with-first-tree was byte-identical.

This change keeps irreversible publication and behavior-risk checks strict while binding reusable evidence to the artifact and environment it actually proves.

Validation

• Python 3.10.20: skill validation; 91 tests (1 filesystem skip); five-case deterministic Floor; compileall
• Python 3.12.12: skill validation; 91 tests (1 filesystem skip); five-case deterministic Floor; compileall
• Ruff 0.16.2 check and format check
• Agent Skills validation 0.1.1
• skills@1.5.22 and skills@latest discovery (latest resolved to 1.5.22)
• git diff --check
• independent Standards and Spec reviews on final head: no findings

Release-safety notes

• The distributable Skill tree is unchanged from main: b090db09e1736d8cab33f4cf1b9d3eae73822166.
• The clean payload digest remains 01a8c19c149df7887074317d9c52542b1d72ea332e7fe7fb03a445fb5790c6da.
• No model session was rerun for this documentation/evaluator-only change.
• This PR does not change repository visibility, settings, tags, Releases, or publication state.