Repository navigation
Description
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.
- A signed catalogue successor is checked through the existing catalogue path; invalid identity or signatures are rejected. Moved to 0.8.1 (0.8.1: Local AI recovery, catalogue and offline checks moved from 0.8.0 #379).
- Existing model bytes, selection, Keep choices and readable chats survive a supported update.
- After engine replacement, a saved model CID resolves to its current verified offer while historical runs keep their original identity. A changed model requires user selection. Drafts stay intact. Proof:
model_startup_binding_rebuilds_only_verified_engine_successors, restored CID test (source proof; installed update row stays in LA-08: Preserve model state through catalogue and Runtime updates #102-2) - Removed, changed or incompatible entries have a defined state and recovery action. Moved to 0.8.1 (0.8.1: Local AI recovery, catalogue and offline checks moved from 0.8.0 #379).
- Missing/corrupt catalogue, interrupted update and supported Undo cases pass. Moved to 0.8.1 (0.8.1: Local AI recovery, catalogue and offline checks moved from 0.8.0 #379).
- A Runtime update preserves existing model state. A separate catalogue delivery path follows after 0.8.0 under G4 AI on your device: Local AI on seed, Mac and Jetson #84/LA-11: Publish both Qwen packages and accept local AI #105.
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
andersalm commentedon Sep 29, 2026
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.
andersalm commentedon Oct 8, 2026
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.
andersalm commentedon Oct 14, 2026
Ticked item 3 (engine replacement keeps the saved CID) with #348's tests
model_startup_binding_rebuilds_only_verified_engine_successorsand 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.andersalm commentedon Oct 15, 2026
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).
andersalm commentedon Oct 19, 2026
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.