Memoria del browser

Outcome: Complete the task with Memoria del browser (Browser Storage). User context: Un'app offline tiene le bozze in IndexedDB e una scelta di visualizzazione in localStorage. Si sincronizza dopo la riconnessione. Technical concept or control: Memoria del browser (Browser Storage). Why it fits: Usalo per bozze recuperabili, dati offline, cache o scelte locali. Abbina l'API ai dati. Do not use it when: Non conservare segreti o registri aziendali unici in archiviazione leggibile da script. Pianifica per lo sgombero e i dispositivi condivisi. Engineering requirements: Define inputs, outputs, contracts, and rules that must always hold. Set authorization and input checks. Define failures, timeouts, retries, one-time effects, data moves, and compatibility limits. Operations: Add useful signals and logs that hide sensitive data. Set capacity limits and write an operator guide. Test recovery and rollback. Acceptance criteria: Contract and failure-path tests pass. Data and authorization rules still hold during retries and partial failures. Check performance limits, monitoring, recovery, and rollback. Evidence and limits (evidence boundary): Nessun singolo standard ufficiale controlla l'intero termine. Il suo significato può cambiare tra team, piattaforme o framework. Unknowns to confirm: Where the code runs, data stores, traffic shape, consistency needs, and the security boundary. Also confirm the compatibility period, service goals, and rollback limits.