Verification scope should follow the strongest available authority

When an ideal verification goal depends on an authority that is stale, incomplete, or unavailable, narrow the first release to the strongest supported contract. Complete the policy-matching contract, test corpus, endpoint authority, failure semantics, and mismatch presentation before claiming asset-level schedule verification. Return asset-level status as unknown unless a real vehicle-level authority and join keys are supplied.