Track unusable upstream v0.16.1 release packaging

[leehack]

Packaging gap

Upstream LiteRT-LM v0.16.1 resolves to the same source commit as v0.16.0 (924e79c91542761242244e4f1651851f822e4cbb) but publishes only litert_lm_main.macos_arm64. It omits the official CLiteRTLM.xcframework.zip and CLiteRTLM_mac.xcframework.zip assets required by the current companion packaging contract.

Primary evidence:

• https://github.com/google-ai-edge/LiteRT-LM/releases/tag/v0.16.1
• https://github.com/google-ai-edge/LiteRT-LM/releases/tag/v0.16.0

Required handling

• Keep v0.16.1 classified as detected but not consumable/publishable.
• Report the same-commit and missing-asset reasons in detector evidence.
• Do not republish or repin merely for the version label.
• Re-evaluate when upstream publishes a distinct compatible release or restores complete official artifacts.
• Retain v0.16.0-native.2 as the latest consumable companion release until a separately approved candidate passes the full platform and real-model gates.

This tracks an upstream packaging/correctness blocker; it does not authorize a workaround release.