feat: save search views and review unsubscribe actions#139

Current combined revision fa52cd0bb9a512826d5f1b4349cfbe71dd3fb8ec, based on Contacts 1597831218000b6852a8f6d1869caa2d1b7d88c4 and main e13e9401053b88b91ec03ba5042675e98740fc49. Linux, Node 24.22.1, synthetic data only.

• Final bounded npm test: 1523 passed, 0 failed, exit 0. This covers the complete combined stack on its exact revision.

• Final npm run build: exit 0; strict TypeScript and production bundles pass. Existing bundle-size advisory remains.

• Focused Contacts and saved-view integration: 3/3 pass, exit 0 before the unchanged-source phone-parent update.

• Synthetic missing-POSIX-API regression: reproduced before the fix; 3 rejection cases pass and the unsupported positive case skips after correction. POSIX runs all four cases. This corrects the earlier Windows fixture failure; current native Windows acceptance remains unknown.

• Isolated npm run check:desktop under Xvfb: exit 0, startup: passed, database opened, renderer loaded, isolated API and background close passed, packaged: false, Electron 44.9.3 on Linux x86_64. The owned process and fixed-port listener exited. The empty profile used the documented Linux local-key fallback with its visible warning; this is not system-keyring or installed acceptance proof.

• node scripts/check-commit-emails.mjs feat/contacts-page-imports..HEAD and full outgoing history check: exit 0; original authors and new commits use GitHub noreply identities.

• git diff --check and new local Markdown links pass. Tests/builds run serially with external memory and deadline containment.

• No real email, unsubscribe request or account change was made. Installed visuals, native passkey/browser handoff and live-provider acceptance remain unknown. No release performed.

• For application changes, npm test and npm run build pass; list the checks that apply to this change. Exact revision and results are above.

• No mail content, addresses, account names, credentials or local paths in the diff, fixtures, logs or screenshots. Fixtures contain only synthetic identities and example-domain destinations; no personal data is included.

• Documentation that this change makes wrong is updated in the same pull request.

• Task owner: screen for the original implementation; maintainer-directed readiness follow-up by pekth.
• Delivery owner (one writer): pekth's coding agent for this follow-up. Original commit authorship retained.
• Owned paths: saved-view and unsubscribe modules/tests under server/shared/src; App, search and reader integration; affected styles, changelog, KB and ADR 0099. The shared updater fixture correction is inherited from #140.
• Base branch and feature branch: main -> feat/saved-views-and-unsubscribe.
• Related issue or pull request: the two linked git.cafe issues; bottom PR #140.
• Coordination search completed; current owner confirmed: existing task and PR records inspected; readiness work stays on this PR. Foreign work preserved.

• Independent reviewer: separate coding agent. Current stacked source verdict: ship, no findings.
• Reviewed base and head revisions: 1597831218000b6852a8f6d1869caa2d1b7d88c4 to fa52cd0bb9a512826d5f1b4349cfbe71dd3fb8ec, tree e07202273bd86947b9a37c3e85762e77da50cfde.
• Required checks and approvals: local results above; forge state read back before handoff. No hosted run dispatched manually.
• Blocking feedback resolved: main and cross-PR conflicts resolved, ADR numbers distinct, Windows fixture corrected, final verification completed.
• Native, live-account or release proof still needed, if applicable: installed behavior and live-provider acceptance remain unknown. DKIM verification is not claimed; destinations are labeled as unauthenticated sender data.