Skip to content

LA-07: Make model state and recovery clear #101

Open

Description

@andersalm

Part of #84.

Owner: Anders (@andersalm).

Depends on LA-06 (#100). Marketplace, System and Assistant show the same state and a useful next action.

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.

Common state and recovery contract

Use the shared Runtime projection for content retention and execution readiness. #100 owns lifecycle/history/replay source repair, and #98 owns journal resource bounds; this issue verifies visible recovery and consistent user controls against those results.

Align the shared management CID validation with the existing canonical selection rule, and regenerate its intentional vendored copies. #208 supplies model-contract parity through the current vendor gate. Keep docs release-neutral and the current work/acceptance in these issues.

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 model recovery checks:

    • Identify the original conversation, draft and run. Assert roles and expected content, and prove that recovery causes no new dispatch.
    • Fixtures use the real run/event response shapes. Distinguish confirmed cancellation from unknown settlement; an HTTP cancel response alone does not prove backend settlement.
    • Give acquisition a total deadline and bounded holder attempts. Exercise late valid holders and cancellation during a stalled read. Keep download cancellation separate from uncertain inference settlement.

    These are reusable test lessons. The historical remote-services review findings were repaired in their later handoff; they are not being reopened without a current reproduction.

  4. andersalm commented on Oct 14, 2026

    @andersalm
    ContributorAuthor

    Ticked Stop (item 3, alpha.16 shows "Stopped" with Retry: #84 (comment)) and bounded request history (contract item 3) with #348's named tests. Item 5 (UI checks on named targets) stays open: Linux x86/ARM pass, Mac and Jetson runs pending. Items 1, 2, 4 and contract 1, 2, 4, 5 moved to 0.8.1 in #379.

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

    @andersalm
    ContributorAuthor

    Moved to After 0.8.0 (audit 15 Oct): item 3 and contract item 3 done; items 1, 2, 4 and contract items 1, 2, 4, 5 are in #379. Item 5 duplicates #84 Done means 1.

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