Realign Foundry agent contract and current task to identity-first MVP

[mark-e-deyoung]

Purpose

Prevent new Foundry work from being steered by the completed Faster-Whisper/OCI PoC rather than the current deterministic-first model selection/acquisition architecture.

Changes

• AGENTS.md
  • replaces the warehouse-centric OCI assumption with provider/evidence-specific identity strength;
  • makes provider-native storage/cache ownership the default;
  • records the residual-uncertainty Generator–Validator rule;
  • clarifies public/private authority and qualification boundaries;
  • treats the earlier OCI PoC as a mechanism/specification donor rather than the current product boundary.
• CURRENT_TASK.md
  • changes the active task from completed BHADA Faster-Whisper PoC to issue Increment 1: capture metadata-only provider fixtures #12 metadata-only provider fixtures;
  • links MVP: resolve and observe external model identities #9 identity MVP, MVP vertical slice: deterministic-first model selection, placement, and acquisition proof #18 post-identity vertical slice, and Dependency: desktop-ui-cv architecture transition documents and first-consumer contract #19 first-consumer contract;
  • records the current critical path through desktop-ui-cv and the GO/NARROW/KILL gate;
  • explicitly defers future publishing Future architecture: model producer/publisher plane and multi-venue release adapters #20 and the old BHADA-local warehouse direction.

Scope

Documentation/control-plane only. No artifact downloads, provider credentials, model publication, runtime mutation, or implementation claims.

Why now

A fresh Foundry agent currently reads CURRENT_TASK.md saying the old OCI PoC is complete and further Foundry work should stop, while AGENTS.md states OCI registry digest is the authoritative artifact identity. Those statements conflict with the current architecture in #18/#19 and would likely cause architectural regression.

Related: #9, #12, #18, #19, #20.