Repository navigation
CLI: chtypes resolve <line> prints the build and manifest digest a line resolves to, without installing #493
Description
Activity
Planned after 2.0.0, as a 2.1.0 candidate. This is additive: binding-level API or CLI, no ABI change. The v2 lock freezes the ABI fingerprint, not the binding surface, so additions like this ship as 2.x minor releases, as 1.1.0 did for 1.x. It stays off the 2.0.0 critical path.
Correction: this moves BEFORE the v2 lock. It is no longer a 2.1.0 candidate. The rule now: every applicable item lands before the ABI locks, even one that looks ABI-neutral, because doing it can reveal an ABI need (a fetch-only call may want a C-ABI entry or argument). It is scheduled after the registry-lock fix (#491) and the production fetch channel, which touch the same code.
Ask (from a downstream consumer).
chtypes resolve <line>, in every binding's CLI. It asks the registry what a line (or a floating tag) currently resolves to and prints the build id and manifest digest, verified and machine-readable, without downloading a layer.curlagainst the OCI API), re-implementing a piece of the fetch contract outside the SDK.--jsonform, in the same flat stylechtypes listuses, so one parser reads all four CLIs;--offlineby answering from the cache;fetch.🤖 Generated with Claude Code