Nodal Analytics 1.7.2

This release includes all changes since 1.6.4: the ACF 0.3 migration,
merge-based approval, adversarial-review fixes and customer workflow relocation.
Versions 1.7.0 and 1.7.1 were superseded before publication.

• Move customer approval and drift workflows into the context template so they
  no longer execute in the package source repository. Fresh scaffolds and support
  upgrades still install both workflows under .github/workflows/ in customer
  repositories, with their existing approval and freshness behavior unchanged.

• Correct adversarial-review regressions in CI revision identity and skip exits,
  clearance inheritance, post-merge freshness, deterministic/clean exports, scoped
  governed consumption, dbt lineage, method literals, merge approval history,
  notebook rollback, routing, simulation and numeric snapshot row keys.

• Replace authored definition approval with protected human-reviewed merge and
  revision-bound live authority checks. Keep branch testing explicitly unapproved.

• Persist stale blocks independently of repair PRs; propagate through dependencies
  and require reviewed, checked, revision-specific clearance with retained history.

• Migrate shipped legacy content with owner-authorized admission, preserve review
  history, separate result verification, and verify exports against approved sources.

• Adopt ACF 0.3 per-metric YAML, shared fragments, aliases and families, review
  history, explicit blockers, ratio policies and cross-domain dependencies.
  Retire ACF 0.2 and legacy metric layouts immediately; provide a one-time,
  comment-preserving YAML converter with backups and conflict protection.

• Add governed methods, static notebook import, and independent notebook/method
  execution comparisons with separate human confirmation and revision checks.

• Match questions structurally and report definition, slicing and verification
  coverage separately. Add negative seeds, reviewed variants and resumable
  observed-demand interviews; keep answer keys out of answer generation.

• Add encrypted approved SQL, customer-controlled regression execution,
  dependency-aware drift review proposals, gated seed re-grading and optional
  semantic warnings. Missing capabilities are reported, never counted as passes.

• Preserve quick simulated-analyst runs and resume, with private draft-capture
  summaries and no fabricated approval or execution evidence. Update package
  guidance and scaffolds, and add a complete fictional ACF 0.3 worked example.

• Report incoming authoring-template differences during support upgrades while
  preserving customer instructions, configuration, evidence and lineage baseline.

• Add behavioral evals for family choices, method fidelity, open-decision blockers
  and missing-data declines, retaining the should-not-fire control and ablation.

• Live host, warehouse, dashboard and customer notebook acceptance remains an
  opt-in maintainer check; offline tests do not establish those results.

Upgrade notes:

• Existing context repositories need an explicit ACF 0.3 migration and support
  upgrade; updating the plugin alone does not migrate authored context. Back up
  existing content and review the conversion before merging. Admission of legacy
  drafts requires each repository owner's authorization.
• Production consumers require the protected approval branch, governance state,
  workflow identity and trusted live reader described in
  GOVERNANCE.md. Conversion alone grants no live approval.
• ACF_BRANCH_TEST=1 permits local testing of proposed context only. Remove it
  for production use and verify approval and freshness through the live authority.

Validation: all 37 direct test files passed, along with package validation, payload synchronization and repository/isolated-skill scaffold checks. The maintainer reported successful manual Claude/Codex and simulated-analyst testing. Live production governance, warehouse/dashboard/notebook acceptance and the full behavioral ablation suite are not claimed by these checks.

Includes #65, #66 and #67.