Check F - No-Disposition Guard Recheck

Verdict: NO_DISPOSITION_GUARD_NEEDS_FIX

The revised guard semantics are correct: active text fails on removed disposition/STUB constructs; fenced historical text is report-only; packages may not consume superseded text. No old disposition model was found active under another name.

However, the guard depends on the currently unpinned ACTIVE_AUTHORITY classification. Until Check E is fixed, a mutable classification/body can bypass the guard after review. T1 must bind G-LEGACY-NO-DISPOSITION-AUTHORITY and G-NO-SUPERSEDED-CONSUMPTION to the exact content-addressed approval envelope and fail closed on all drift.