Skip to content

feat(imf): persist verified models in the browser Cache API - #52

Merged
ronaldtse merged 1 commit into
mainfrom
feat/imf-cache-api
Aug 28, 2026
Merged

feat(imf): persist verified models in the browser Cache API#52
ronaldtse merged 1 commit into
mainfrom
feat/imf-cache-api

Conversation

@ronaldtse

Copy link
Copy Markdown
Contributor

The browser tier needs download-once semantics to be usable: the
registry now persists sha256-verified zips in the Cache API
(interscript-imf-models-v1). Every use re-verifies against the index

  • the cache is storage, not trust; tampered/stale entries are deleted
    and refetched. Node path untouched. TDD: stubbed caches + a browser
    host simulation (no Node fs) over a local HTTP channel that dies
    mid-test to prove the cached copy serves, then corrupts it to prove
    refetch. 238 green, tsc/lint clean. Version 4.1.0.

Browsers kept verified bytes in memory only — every page reload
redownloaded the whole model. The registry now stores verified zips
in a named Cache and re-verifies the sha256 against the index on
every use; corrupted entries are deleted and refetched. Node hosts
are unchanged (filesystem cache). Download-once per browser.
@ronaldtse
ronaldtse merged commit a64d168 into main Aug 28, 2026
7 of 8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant