Cache and log hardening - phase 0 of the #189 data-minimization track #313
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "phase-0-leak-hygiene"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Research for #189 identified twelve cache/log leak surfaces that are independent of any architecture choice. This PR closes them (phase 0); the direction itself (refs-only cards, content on demand) stays in #189.
At the transport edge:
In the application:
In the browser:
Docs: security.md gains a section on response caching, browser storage, access logs and the shared-workstation scenario; deployment.md gains WAGGLE_LOG_LEVEL (never DEBUG in production) and WAGGLE_SYNC_LOG_RETENTION_DAYS.
Gates: 1970 backend tests at 100% coverage, 1177 vitest, vue-tsc + build, pinned pre-commit across all files, full e2e suite locally green after rebase.
04d7582faa746cd3c0fe746cd3c0fe65cda0de6365cda0de6344367ba48644367ba486bc7fea65c7bc7fea65c753f612b96453f612b964ff2ceeabfa