feat(usai-catalog): carry verified capability metadata through a catalog refresh #576

🤖: AI agent (First Mate), filing on behalf of @mogul.

Goal

A refresh of the USAi catalog must not erase verified reasoning / inputModalities values.

Problem

#541 (data PR #575) commits verified inputModalities for 12 models, with an evidence file. The refresh entrypoint in #573 rebuilds catalog.json from the live feeds, and the builder drops capability values unless the unverified --include-capabilities copy is requested. A plain refresh after #575 would therefore silently remove the verified values (and a refresh using --include-capabilities would replace them with unverified upstream values). The PR body and README of #575 flag this; nothing enforces it yet.

Scope

• Treat verified capability values as curated overlay data keyed by model id: carry them forward on refresh, as recommendations are already carried forward.
• Drop a model's values only when the model leaves the feed, and report that as drift.
• Never enable the unverified models.dev copy path by default; if --include-capabilities is used, do not let it overwrite a verified value without an explicit, visible conflict.
• Keep sources.capabilitiesVerified (the release reminder) consistent when values are carried forward.
• Report added, changed and dropped capability values as drift in --check mode.

Acceptance

Offline fixtures show that a refresh preserves verified values, drops values for removed models, reports changes as drift, and refuses to overwrite a verified value from the unverified path.

Trigger

After #575 (the data change for #541) and #573 (the refresh entrypoint) merge. Child slice of #419.

AI-assisted tracker entry (OpenCode). Human review required.