Skip to content

LA-08: Preserve model state through catalogue and Runtime updates #102

Open

Description

@andersalm

Part of #84.

Owner: Anders (@andersalm).

Source work depends on LA-07 (#101) and fixture engine/catalogue identities. Integrated update work uses UP-03 (#109). Record the source/core and updater-integration results separately.

Done means

Release acceptance: Each exposed feature works clearly from start to end, including recovery. Keep unfinished or confusing features hidden until their complete journey passes. Hiding a feature does not complete its task; source checks alone do not establish installed acceptance.

After 0.8.0 catalogue delivery scope

This issue owns the consumer's first model-catalogue trust configuration, signed successors and saved-state behavior. #105 owns producer signing/publication; #150 supplies reusable disposable fixtures. Models and their catalogue remain separate from Runtime releases after #236/#242.

  • An empty ordinary Home obtains the intended model list through the existing signed catalogue and Content path with an explicit trusted publisher/head binding. Unconfigured and unavailable states remain distinguishable; files left from an old install supply no authority by themselves.
  • Store/preserve the catalogue trust and retained-model state independently of Runtime release replacement. Verify first configuration, successor, bad signature/CID, removed/incompatible entry, offline/restart and interrupted configuration on isolated fixture Homes.
  • Reuse the same verified catalogue format and Content acquisition for fixtures and production. Bind model selection to the complete package CID and preserve historical run identities when the engine/offer changes.
  • Record source/core acceptance separately from the UP-03: Restart and recover safely #109/UP-07: Accept updates on Mac, Linux and Jetson #113 signed-update and supported Undo rows. A Runtime update preserves existing downloaded models and the independent catalogue pin.

Keep durable catalogue/distribution docs aligned with the independent model path and remove their old release-pin and competing task-status instructions. Define and test this interface before final publication. Early #150 fixture setup can exercise it while this task waits for #101; its fixture receipt is preparation evidence rather than completion of this issue.

Any added route or capability follows the scoped approval recorded under #173; prefer the existing typed operations and narrowly bound grants.

Acceptance record

Candidate and checks: see #84.

Activity

  1. added this to the 0.7.1 milestone on Sep 29, 2026
  2. self-assigned this
    on Sep 29, 2026
  3. andersalm commented on Sep 29, 2026

    @andersalm
    ContributorAuthor

    Retained catalogue regression case: withdraw an offer while its provider remains alive. Preserve the model CID binding and refuse the withdrawn selection, while separately authorized offers remain usable. Record the result on the exact update candidate.

  4. andersalm commented on Oct 8, 2026

    @andersalm
    ContributorAuthor

    From #113 (8 Oct): proving that already-downloaded model bytes, Keep and selection survive a Runtime update and Undo is this issue's job. No test Home has a model yet; check it on the first Home with a prepared model when Local AI resumes.

  5. andersalm commented on Oct 14, 2026

    @andersalm
    ContributorAuthor

    Ticked item 3 (engine replacement keeps the saved CID) with #348's tests model_startup_binding_rebuilds_only_verified_engine_successors and the restored-CID test. Items 2 and 6 stay open for the 15→16 update run (#84 Remaining, #113); items 1, 4 and 5 moved to 0.8.1 in #379.

  6. modified the milestones: 0.8.0, After 0.8.0 on Oct 15, 2026
  7. andersalm commented on Oct 15, 2026

    @andersalm
    ContributorAuthor

    Moved to After 0.8.0 (audit 15 Oct): item 3 done; items 1, 4, 5 are in #379. Items 2 and 6 can be ticked from the alpha.18 to alpha.19 System update run if that Home has SmolLM2 kept and selected (#93 item 5).

  8. andersalm commented on Oct 19, 2026

    @andersalm
    ContributorAuthor

    The lines here marked "Moved to 0.8.1 (#379)" are tracked only in #379; tick them there, not here. This issue keeps its other open lines, so it stays open.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions