docs(tdx-hydro): adjudicate remaining strictness corrections

[CooperBigFoot]

Criterion

The adjudicator treats every endpoint pairing at or below the inclusive 0.001 tolerance equally. For each outstanding refusal, it derives the successor upstream endpoint as 1 - established_successor_downstream_endpoint_index and collects the sorted distinct current endpoint indexes admitted against that successor endpoint. A singleton set selects correction_required; an empty or two-index set selects no_correction_required. Either valid outcome was executable before the landed records were evaluated.

Measured result

The landed records select correction_required for both processing basins:

• 2020003440, 817894 -> 819270: candidate current endpoint indexes [0], selected endpoint 0.
• 2020071190, 1307547 -> 1308923: candidate current endpoint indexes [0], selected endpoint 0.

The top-level selected set is ["2020003440", "2020071190"]. The determination records the general future correction shape and sets milestone_disposition to follow_up_runtime_node_required. Milestone 7 therefore needs a separately planned runtime implementation node.

Exact-zero and nearest-distance preferences were unused. The selector depends only on the admitted pairing relation.
Dedicated fixtures prove that an exact-zero pairing cannot collapse a two-candidate set and that a singleton candidate at endpoint 1 selects endpoint 1.

Gates

• cargo fmt --check: passed.
• cargo clippy --workspace --all-targets -- -D warnings: passed.
• cargo check --workspace --all-targets: passed.
• cargo test --workspace: passed.
• cargo build --workspace: passed.
• HFX_BINARY="$(pwd -P)/target/debug/hfx" uv run --project adapters/tdx-hydro python adapters/tdx-hydro/test_build_adapter.py: passed, 130 tests.

Scope

This is a decision-only change. It does not alter adapter behavior, versions, verdicts, tolerance bands, guards, schemas, the specification, or release files. No acquired-source compilation, compiled basin output, cloud activity, provisioning, S3 access, NGA contact, source-defect reporting, assembly, teardown, release work, tag, push, or PR creation occurred. Both evidence trees remained content-unread and metadata-identical. The 2020071190 superseded prior estimate remains recorded unchanged.