# Release: Time's Up v2.5.2

**Release Date:** 2026-04-19
**Status:** Draft
**Manifest Version:** 3

## Release Summary

v2.5.2 drops the `system.memory` permission to unblock Chrome Web Store uploads and reduce the install-time permission prompt. No user-visible behavior change.

## What Changed

### Remove `system.memory` Permission

v2.5.0 added `system.memory` to read OS total/available memory as part of Diagnostics snapshots. The Chrome Web Store review flagged it for a required justification, and on review the signal turned out to be weak:

- The values were never shown in the Diagnostics UI — they only appeared in the raw JSON export.
- OS-wide memory tells you nothing about whether the extension specifically is consuming memory. Per-process data requires Chrome's Task Manager, not this API.
- Per-extension health is already covered by existing signals that need no permission: `performance.memory.usedJSHeapSize`, `tabCount`, `storageBytes`, `swUptimeMs`, and the error ring buffer.

**Changes:**
- `manifest.json` — removed `"system.memory"` from the permissions array.
- `extension/diagnostics.js` — removed the `chrome.system.memory.getInfo()` block from `recordSnapshot`. The remaining snapshot fields (`ts`, `tickCount`, `swUptimeMs`, `tabCount`, `storageBytes`, `jsHeapUsed`) are unchanged.
- `requirements/core/FEAT-003-observability.md` — updated Technical Notes and Edge Cases to reflect removal.

## Migration Notes

No user action required. Existing `diagnostics_snapshots` entries with `osMemAvailable` / `osMemTotal` fields remain in storage; they simply won't grow with new entries. Clearing diagnostics removes them.