feat: expose the IMF registry from interscript/ml - #48
Merged
Conversation
The IMF runtime (models.yaml resolution over GitHub Releases with
sha256 sidecar verification) ships in the package but was unreachable
— the exports map blocks deep imports into dist/ml/imf. Consumers
now get it as `import { imf } from "interscript/ml"`.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
interscript@3.1.0 ships the IMF runtime but no public path to it —
the package exports map blocks deep imports (dist/ml/imf/*), so
verified Release-pinned model resolution was only reachable from
inside the repo. This re-exports it as a namespace from ./ml:
import { imf } from "interscript/ml"
await imf.resolve("ara-diac-1.0")
Additive surface, no behavior change elsewhere; 245 tests green.
Version 3.2.0.