Skip to content

Design durable completion proof across browser restart or extension update #121

Description

@lamemustafa

Context\n\nPR #117 deliberately ships only the checkpoint recovery path verified for an MV3 worker restart while chrome.storage.session remains available. Rounds 6 through 12 removed the broader durable-marker design because it required a per-target read and start boundary that were not independently proven.\n\n## Required before implementation\n\n- Per-target durable proof read\n- Fail-closed Start boundary for unavailable or ambiguous proof\n- Exact target-bound correlation and no repeated portal action\n- Dedicated live QA across a browser restart or extension update\n\n## Scope boundary\n\nDo not reintroduce durable proof in a popup summary or a global state fallback. This needs its own design, synthetic tests, and authenticated live evidence before any production path changes.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions