[NyxID Assistant][UC5 Evidence] Pin voice contracts and materialize typed reservation and Calendar postconditions

[eanz17]

Product mismatch

Aevatar conformance currently pins NyxID 47f2e0086c6c2117f644f8559d871a01d2a61982, which predates the Twilio/ElevenLabs catalog merge b0c7b880f5fc6f7460538cc0ede07812f203fe2e.

The new overlays are not sufficient by themselves:

• Twilio create_call uses a request media type the current catalog materializer rejects;
• ElevenLabs get_convai_signed_url is an HTTP GET whose overlay marks it non-read-only, while Aevatar currently derives read-only classification from the HTTP method;
• provider responses are open JSON objects, and free-form transcripts cannot author reservation or cleanup truth;
• UC5 also requires an exact Google Calendar create plus authoritative read-back.

A generic success receipt cannot prove that a call completed, a reservation was held or released, an allergy constraint was acknowledged, or the intended calendar event exists.

Scope

Extend the conformance source of truth and the generalized verification path with the exact provider contracts and typed evidence required by UC5. Provider-specific mapping stays in adapter/extension boundaries; the generic chat task consumes closed Protobuf outcomes.

Acceptance

• the conformance source pins an exact NyxID revision containing feat: seed ElevenLabs and Twilio catalog services with OpenAPI discovery ChronoAIProject/NyxID#1454 and records hashes for the Twilio/ElevenLabs overlays and relevant proxy contract sources;
• the generated manifest pins exact method, path, request media type, response media type, safety/read-only classification, and operation-contract digest for create_call, get_call, get_convai_signed_url, get_convai_conversation, calendar_create_event, and calendar_list_events;
• CI regenerates those descriptors and fails on NyxID revision, overlay, media-type, safety-classification, or digest drift;
• Aevatar consumes the published operation safety contract rather than treating GET as intrinsically read-only; get_convai_signed_url is never exposed as an ordinary model-visible read;
• the deployed canary records the observed root catalog digest and exact endpoint digests separately;
• Protobuf contracts represent an opaque prepared voice-channel reference, call observation, conversation observation, reservation observation, calendar observation, governed transcript artifact reference, and their correlation identities;
• signed URL material is classified as sensitive and is never part of a public or durable result contract;
• call verification correlates operation key, CallSid, conversation ID, target-safe identity, expected purpose, and terminal provider state;
• reservation verification has closed typed outcomes for held, kept, released, declined, expired, unavailable, and uncertain, and carries the confirmed time, party size, deposit/card requirement, dietary acknowledgement, and exact evidence references when applicable;
• transcript content is stored as a governed artifact with digest and provenance; actor state carries only the typed verdict and artifact reference, never free-form transcript truth;
• Calendar completion requires the exact created event identity and a post-write calendar_list_events read that matches calendar, time, party/context, and expected event identity;
• generalized verification returns the closed effect outcomes applied, not_applied, unavailable, or uncertain; a call receipt alone cannot produce applied, and missing or mismatched evidence cannot produce success;
• verification reads carry externalEffect=not_applied and confirm their owning effect step rather than pretending to create a second effect;
• no core control value is carried in a generic metadata bag;
• canon and adversarial fixtures cover unknown fields, drift, mismatched IDs, partial evidence, signed-result leakage, transcript mismatch, release ambiguity, Calendar duplicates, and replay.

Dependencies

Builds on the generalized verification contract #3305 and conformance harness #3313. Blocks #3490 production activation, #3491 authoritative obligation transitions, and the UC5 end-to-end journey.

This is successor work and must not be added to Milestone 42.