feat: expose the IMF registry from interscript/ml

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"`.

Author: ronaldtse

package.json

@@ -1,6 +1,6 @@
 {
   "name": "interscript",
-  "version": "3.1.0",
+  "version": "3.2.0",
   "description": "Interscript TypeScript runtime — interoperable script conversion",
   "type": "module",
   "main": "./dist/index.js",

src/ml/index.ts

@@ -46,6 +46,13 @@ export {
   type ManifestModelEntry,
 } from "./provision/manifest.js"
 
+/**
+ * The IMF v1 registry — models.yaml resolution over GitHub Releases
+ * (sha256-sidecar-verified). This is the canonical way to load models
+ * by id; `import { imf } from "interscript/ml"`.
+ */
+export * as imf from "./imf/index.js"
+
 // Side-effect: register built-in model kinds. Adding a new model kind
 // = adding a new import here. Order doesn't matter.
 import "./models/rababa/index.js"

test/imf.test.ts

@@ -212,6 +212,16 @@ describe("registry", () => {
       await expect(resolve("nope", url)).rejects.toThrow(/index sha256/)
     })
   })
+  it("the public ./ml surface re-exports the IMF registry", async () => {
+    const ml = await import("../src/ml/index.js")
+    const imf = (ml as { imf?: Record<string, unknown> }).imf
+    expect(imf).toBeDefined()
+    expect(typeof imf!["resolve"]).toBe("function")
+    expect(typeof imf!["IMFModel"]).toBe("function")
+    expect(imf!["DEFAULT_INDEX_URL"]).toMatch(
+      /github\.com\/interscript\/interscript-ml\/releases\/download\/index-v\d+\/models-index\.yaml/,
+    )
+  })
 })
 
 const e2eZip = process.env["SECRYST_E2E_ZIP"]