truf-server/openspec/changes/resolve-ambiguous-key-providers/tasks.md

1. Routing And Candidate Extraction

• 1.1 Extend provider evidence and persisted hints to include ZAI and weak-context generic-key ambiguity.
• 1.2 Route ambiguous findings to one deduplicated provider_resolver candidate while preserving direct strong-provider candidates.
• 1.3 Add bounded ZAI key formats and ZaiGLM service extraction.

2. Resolver And ZAI Checker

• 2.1 Implement shared deterministic provider resolution with match, no-match, and retry outcomes.
• 2.2 Add the PostgreSQL provider_resolver checker and legacy ambiguous-candidate delegation.
• 2.3 Add the ZAI /models authentication checker with global/China endpoint and business-code classification.
• 2.4 Require a bounded ZAI generation/billing probe before assigning VALID, while preserving authenticated non-alive outcomes.
• 2.5 Pin the ZAI usability probe to glm-5.2 without model-list fallback.

3. Transactional Persistence And Runtime

• 3.1 Reassign a positively matched resolver candidate to the canonical provider credential during fenced completion.
• 3.2 Register resolver and ZAI services, capabilities, status projections, configuration, and lifecycle runtime behavior.

4. Verification

• 4.1 Add extraction, route ordering, short-circuit, retry, ZAI classification, and service-reassignment regression tests.
• 4.2 Run targeted and existing keycheck/scanner test suites with bytecode writes disabled.
• 4.3 Restart the supervised runtime and verify READY status plus live resolver/ZAI queue behavior.
• 4.4 Add regression coverage for successful generation, no-balance, limited, restricted, and inconclusive ZAI probes.
• 4.5 Run the affected suites and verify the supervised runtime plus one live ZAI recheck.
• 4.6 Verify the fixed glm-5.2 target with regression tests and one live recheck.