Web: quota recovery can delete the project registry

Description

The web persistence quota-recovery path evicts the largest opencode.* localStorage entries first. It does not protect opencode.global.dat:server, which stores the server list, open projects, last project, and recently closed projects.

When another persisted value hits the browser quota, recovery can delete this registry. After the next reload—especially noticeable in mobile/PWA browsers—the server is reconstructed from startup configuration, but projects disappear from the sidebar and must be added again. Replacing the registry itself can also delete the old value before a failed retry.

Reproduction

1. Store a relatively large value at opencode.global.dat:server.
2. Fill localStorage close to quota with another evictable opencode.* value.
3. Persist a new value that triggers QuotaExceededError.
4. Observe quota recovery remove the server registry as the largest candidate.
5. Reload and observe the project list is gone.

Expected behavior

Quota recovery must preserve the server/project registry. If a registry replacement cannot be stored, the previous registry should remain intact.

Notes

This is an application-owned data-loss path independent of browser/OS origin-wide storage purging.