Provider data pipeline: registry tiers, generated model catalogue, maintenance jobs, RFC-0033 - #176

Closed

cunninghamcard-bit wants to merge 13 commits into

arcships:masterfrom

cunninghamcard-bit:provider-data-pipeline

Commits on Sep 3, 2026

docs(rfc): add RFC-0033 code convergence plan
cunninghamcard-bit
committed
1f6ce38
docs(rfc): update RFC-0033 defect list after the #164/#165 review round
cunninghamcard-bit
committed
e7359a4

Commits on Sep 4, 2026

docs(rfc): correct the RFC-0033 A1 row after the scripts audit (#168)
cunninghamcard-bit
committed
37301ab
docs(rfc): add RFC-0033 §4.1 provider maintenance flow and §8.6 auth layer
cunninghamcard-bit
committed
7ab8553
docs(rfc): link RFC-0033 §4.1/§8.6 to tracking issues #168–#175
cunninghamcard-bit
committed
4c67470
feat(providers): add an evidence tier to every registry row
cunninghamcard-bit
committed
e92cfa1
docs(providers): show tiers in providers.md and gate it in --check
cunninghamcard-bit
committed
e3b0748
feat(providers): generate the L2 model catalogue under data/models/
cunninghamcard-bit
committed
7ca16ca
feat(scripts): add sync_registry.py and probe_registry.py, drop two ad-hoc scanners
cunninghamcard-bit
committed
28b5421
ci: gate the two new generators and schedule the maintenance jobs
cunninghamcard-bit
committed
ac16721
docs: document the four-layer provider model and the new generators
cunninghamcard-bit
committed
28cfd43
fix(scripts): send a User-Agent when fetching models.dev
cunninghamcard-bit
committed
da485ca
docs(rfc): rewrite RFC-0033 §4.1 as the four-layer provider data pipeline; exclude data/ from the crate
cunninghamcard-bit
committed
e8332df