feat!: remove the manifest-based provisioner — IMF registry only (4.0.0) - #50
Merged
Conversation
Breaking: the manifest APIs (loadManifest, resolveManifestEntry, artifactUrls, sidecarFilenames, setInlineManifest, setManifestUrl, setModelBase, getModelBase) are gone from interscript/ml, and provisionModel now requires an explicit url. Models resolve through the IMF registry (GitHub Releases index, sha256-verified) or an explicit url. The interpreter's secryst funcall now loads IMF models by id via imf.IMFModel.load — no map in the corpus uses it today, so the runtime path is dormant but now correct.
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.
Completes the deprecation begun in 3.3.0 — the 4.0 decision.
Breaking changes (public surface):
setInlineManifest, setManifestUrl, setModelBase, getModelBase removed
from interscript/ml
imf.resolve guidance
Replacement: the IMF registry (imf, shipped in 3.2.0) — models.yaml on
GitHub Releases with sha256 sidecar verification.
Runtime unification:
imf.IMFModel.load (tests drive it through transliterateAsync with a
local index; unknown ids surface RegistryError)
provisioning); rababa untouched (own registry, the one live ML map)
Note: secryst funcalls load the model per call (no cache yet) — fine
while no map uses secryst; caching lands with the first secryst map.
237 tests green, tsc clean, prettier clean. Version 4.0.0.