fix: verify adjusted loader bar metadata

[pjy008008]

Summary

• require the operating loader's adjustment=all Parquet metadata for adjusted feature inputs
• update the exact base/derived loader schema fixtures to model the production ALPACA_SIP_ALL_<resolution> feeds
• keep the trust boundary fail-closed by proving adjustment=raw is rejected

Operational evidence

After PR #53 allowed exact version verification, the four-resolution canary advanced to Parquet validation and rejected all four sources. The staged backfill planner intentionally selects ALPACA_SIP_ALL_<resolution> feeds, while the reader incorrectly required adjustment=raw.

TDD / validation

• red: both exact loader schema acceptance cases failed when modeled with production adjustment=all
• 56 passed, 1 deselected for the feature-output trust-boundary suite
• Ruff passed
• mypy passed

Safety

This does not broaden the accepted metadata set: it replaces the wrong raw adjustment with the one production feed identity the backfill planner selects.