# Wave 14: The outbox keeps every change, and the sign-in limit cannot destroy it **Items:** `D26`, `D27`, `B5` (finish), `BL-061` **Depends on:** wave 13 merged (it is, except T13.1). Independent of wave 15. **Decision record:** `docs/waves/decisions-2026-10-17.md` (D26 and D27 are **proposed**; they need Matt's OK, see "Open questions") **Unblocks:** `T13.1` (idle timeout). T13.1 must not reach `main` before T14.1 and T14.2 are done. **Branch rule:** one task for each pull request. Cut each branch from `main`. ## Why this wave exists The outbox in `html/project-data.js` queues each save in `localStorage` and sends it later. A crew in the field can work with no signal, and the changes go out when the network returns. The code was checked on 2026-10-17 against the 8 hour session limit (D25) and the idle timeout that T13.1 adds. It has four faults that lose or hide work. They are small now. The idle timeout would make them common. | # | Fault | Where | Result | |---|---|---|---| | 1 | A `401` (session ended) or `403` is treated like any other `4xx`. The change is marked **dead** and is never sent again. | `project-data.js`, `flush()` | A crew that works past the session limit, or past an idle timeout, comes back online and every queued change is rejected for good. The badge says "rejected by the project". The change is not lost from the device, but nothing can send it. | | 2 | `qWrite()` swallows a storage error. | `project-data.js`, `qWrite()` | If the device storage is full, a change is **not queued and nobody is told**. | | 3 | The queue belongs to the browser, not to a person. A queued change has no owner. | `project-data.js`, `enqueue()` | On a shared device, person B signs in and the queue of person A is sent under the name of person B. | | 4 | The offline sign-in window is a fixed 12 hours in the browser. | `auth-guard.js`, around line 183 | It does not follow `AUTH_SESSION_HOURS` (8 since D25). It also slides: every online page load resets it. The browser and the server disagree about when the session ends. | Also: the sync badge sits over page controls (`BL-061`) and cannot be used with a keyboard or a finger. The badge is a `div` with `pointer-events:none`. A badge that must ask a person to sign in again needs a real link or button. ## Rules for this wave - Do not use a `div` with `onclick` (`CLAUDE.md`, accessibility). The sign-in action is an `` or a `