✨ - Browser extension H6 search notifications and personal work management #707

Is there an existing issue or feature request for this?

• I have searched the existing issues and feature requests.

What area does this improvement affect?

New Feature

What actions does this improvement affect?

Issue, Pull Request, Commit

Description of the idea or improvement

H6 — Search, notifications and personal work management. Part of the complete product from merged PR #699 and milestone GitHub browser extension — complete product. Implementation order does not reduce product scope or the 803-case acceptance floor.

Catalog ownership: SEARCH, NOTIFY, WORK; 24 required capabilities, 91 distinct mandatory catalog case IDs. Implement every feature record in specs/browser-extension/features/SEARCH.v1.json, specs/browser-extension/features/NOTIFY.v1.json, specs/browser-extension/features/WORK.v1.json.

Implement every SEARCH, NOTIFY and WORK catalog record using bounded loaded-scope searches and explicitly authored personal state. Include attention lists, saved views, repository work organization and opt-in monitoring within catalog limits. No browser history grant, hosted telemetry, hidden polling or automatic connected reads. Optional contextMenus/alarms and Chrome/Firefox notifications require explicit user gesture; Safari uses the accessible center/toolbar channel and never requests unsupported notifications. Honor quiet hours, deduplication, quotas, session revocation, denied grants and explicit channel choices.

Normative baseline: specs/github-browser-extension.md, specs/github-browser-extension-functional-catalog.md, specs/github-browser-extension-platforms-and-delivery.md, specs/github-browser-extension-action-integration.md, specs/github-browser-extension-control-center-and-setup.md, and the versioned structured schemas/catalog. Follow specs/README.md and _template.md; update owning SDDs, current catalog evidence, tests and user docs in the implementation PR. Before starting, refine exact current-code acceptance and prerequisite evidence through the Action's pre-branch SDD flow.

Tests and acceptance: Own all family cases; exercise pagination/partial scope, scheduler suspension, denied/unsupported permissions, local versus OS attention channels, quiet-hour boundaries, duplicate/out-of-order events, private-data persistence/export and settings migrations. Measure bounded requests and retained resources; matrix reruns are not new case IDs.

All new pure evidence/eligibility/intent/approval policies require 100% branches; other new modules require at least 95% statements/90% branches with changed executable lines covered. Modules at most 220 lines/Svelte components 90 unless reviewed decomposition exception. Add risk-derived cases beyond the baseline where needed; every required behavior maps to executable evidence and docs. Full product acceptance remains all 150 functions/all three desktop targets, not this issue alone.

Current limitations or challenges

PR #699 specifies the product; this milestone's behavior is not implemented merely because the specifications or earlier engineering increments exist. Dependencies: H2 (#703), H3 (#704). Use the roadmap's linked issues to verify those dependencies before starting; do not advertise future features, runtime compatibility or store approval as already verified.

Expected impact

Search, notifications and personal work management becomes a complete, tested and documented part of the original premium GitHub productivity application. Users receive observable outcomes, safe defaults and useful failure/recovery paths across Chrome, Firefox and Safari, with explicit source/freshness/permission boundaries where applicable.

Alternatives considered

Reject reduced catalog scope, copied implementation/assets, speculative compatibility claims, placeholder acceptance, duplicate Action authority and weaker existing test gates. Deliver in reviewable increments while retaining the complete accepted product contract.

Version of copilot

Published Action 3.10.5; develop baseline includes merged #699. Extension versions independently; future implementation selects and locks compatible dependencies using primary documentation.

Additional context or comments

Backlog milestone. Do not add in-progress or create a branch until its dependencies are ready and it is deliberately started. The Action owns admission/SDD/remote branch lifecycle. PRs link their issue and include actual test/browser/docs receipts; merge/deploy/store publication is not implied. First active increment: #702.