Checks H-I - Final Hardcode / PG-First Native Driven Recheck

Hardcode verdict: HARDCODE_FINAL_NEEDS_FIX

PG-native verdict: PG_NATIVE_FINAL_NEEDS_FIX

Runtime design remains PG-first/native/driven and no runtime name/pattern/owner/CASE/relkind/prokind/manual-history policy was reintroduced. Previously accepted typed-set separation and PostgreSQL authority primitives remain intact.

The remaining disguised-hardcode risk is construction-document authority: prose-interpreted active scopes/field semantics and a circular detached anchor permit verifier-dependent authority. Until canonical extraction and non-circular anchoring are exact, the document authority is not fully content-addressed/fail-closed.

T1 must fix this without adding a runtime authority surface, readiness gate, #20 column, catalog family, or eighth runtime hash contract.