Synthetic tool labels must bind hidden prerequisites

A tool schema may state a runtime prerequisite that a compact training example does not expose. Distinguish literal history claims such as “tool X succeeded” from backend-state invariants such as “a resolved entity exists.” Enumerate all registered entry paths at a pinned revision because alternate resume or lookup paths may establish the same state without calling the named tool.

Inspect the exact training projection. If it omits prior tool results and backend state, node identity and a schema assertion are not observable witnesses. Hold the row unless the representation carries an authenticated state witness or the target is valid from visible input alone.

Fail-closed runtime validation is defense in depth; it does not make a hidden-state training label truthful. This establishes representation fidelity, not model quality or deployment state.