feat(providerroutes): path-prefix routing + model_map + N:M compat matrix

[damonleelcx]

pkg — providerroutes engine (shared)

• Path-prefix routing + model_map.
• N:M compat matrix (protocol × provider) + registry digest.

Shared engine consumed by aikey-proxy and the control plane.

Part of the model-mapping-egress-v1.0.4 feature (7 repos)

pkg · aikey-proxy · aikey-cli · aikey-config-tool · aikey-control · aikey-control-master (→ develop-v1.0.4) and roadmap20260320 (docs → main).

Verification status (honest)

• ✅ Live GLM L2 mapping — client claude-opus-4-8 → mapped glm-4.6 → GLM served → restored (streaming too); all TestLive_* pass with the real key.
• ✅ Request-chain attribution — verified live: provider=zhipu (declared anthropic → attributed zhipu), protocol=anthropic, base_url open.bigmodel.cn/api/anthropic, real message_id + token usage.
• ✅ aikey use two-axis summary + provider(s) mislabel fix — verified live against the real binary (new tests/e2e_use_two_axis_live.rs); PROTOCOL and PROVIDER render as separate columns (anthropic | zhipu(GLM)).
• ✅ All test suites green (proxy full, cli 1084 lib, dbmigrate fixture-matrix, both web bundles).
• ⚠️ Not yet verified — P7 infra (Windows/阿里云 three-env, fault injection) is blocked; L1/L3/L4 live-DB + real-backend browser render remain stub-only.

🤖 Generated with Claude Code

[damonleelcx]

🔬 Live evidence — path-prefix routing + model_map resolved against the real vendor

Run on Aliyun cn-shenzhen + macOS + Windows Server 2025, branch feature/model-mapping-egress-v1.0.4, real GLM/zhipu key.

The embedded registry built from provider_fingerprint.yaml was exercised end-to-end through aikey-proxy:

• (host, path_prefix) routing — open.bigmodel.cn + /api/anthropic resolved to protocol=anthropic, provider=zhipu, base_url=https://open.bigmodel.cn/api/anthropic (the N:M compat row), not the sibling /api/paas (openai_compatible) or /api/coding/paas/v4 rows.
• model_map — ResolveModel(zhipu, "claude-opus-4-8") → "glm-4.6", and the real GLM endpoint served glm-4.6 (proving the map reached the vendor, not just a local rewrite).
• truthful attribution — LookupByBaseURL flipped the declared anthropic to the real zhipu for the usage record.

/v1/diagnostics/pipeline exposes the registry provenance measured live:

{"registry":{"digest":"d190c3562312","route_rows":21,"providers_with_model_map":["zhipu"]}}

Full L1/L2 persisted-row assertions + three-env matrix + tc/netem fault injection are in the aikey-proxy PR. Cross-language parity gate (7.5) and the N:M compatibility-matrix form-validation (7.5c) were not independently exercised this run.