Tally selected-ledger qualification rejects the observed Education responder

[lamemustafa]

Evidence

A redacted local run through Bridge's real TallyClient accepted discovery, scoped identity bootstrap, and the documented standard ledger catalog, but qualify_selected_ledgers rejected the custom selected-ledger response. No company name, GUID, ledger value, raw XML, or response was retained or logged.

Impact

The richer selected-ledger capability remains Unknown on the observed Education endpoint even though the baseline read path works.

Acceptance criteria

• Reproduce against a sanitized simulator fixture that captures only structural response differences.
• Preserve strict schema, company-context, and stable-identity validation; do not weaken the qualifier merely to admit this responder.
• Correct the request/parser/profile contract and add regression coverage for the observed structural shape.
• Re-run a redacted local Education read and report only capability status/buckets.
• No raw Tally data, credentials, or local paths in commits, issues, fixtures, logs, or PRs.

Root cause

Not yet isolated; the result is an actual app-method failure, not a hand-authored XML probe.