Assumption echoes discard asked and erase name corrections on resubmission #38

tools/validate_client_contract.py:read_assumption keeps kind, binding_ref, text and refs, but discards asked, which the OpenAPI snapshot released in #35 adds to name-correction assumptions. Both reading_echo and resubmit_entry use this reader.

The pinned API’s _held_name_corrections drops an echoed correction without asked. Choosing another part’s reading therefore silently removes an existing correction warning.

This reproduces the lost field:

from tools.validate_client_contract import read_assumption

item = {
    "kind": "name_corrected",
    "binding_ref": "where:",
    "text": '"Germny" read as Germany',
    "refs": ["country/DEU"],
    "asked": "Germny",
}
assert read_assumption(item)["asked"] == "Germny"  # raises KeyError

Done when

• Assumption echoes preserve a valid asked value.
• A scenario covers a name correction surviving a choice or resubmission.
• The contract documentation describes how clients read and echo asked.