[efraespada]

Define a complete desktop GitHub productivity extension: 150 required capabilities across 12 families, a packaged local control center, comprehensive Copilot Action integration and shared setup. The contract requires the complete catalog and quality gates before product acceptance; implementation order does not reduce its scope.

The maintainer's current scope clarification supersedes the initial MVP restrictions in #694. The complete catalog, optional independently authorized user-write roles and native human-submitted implementation/sync/release/deployment handoffs are intentional requirements; the read role and Action/maintainer authority boundaries remain intact.

What changed

• Five coordinated SDDs cover native GitHub tools, the full functional catalog, Action evidence/commands/operations, Chrome/Firefox/Safari delivery, and the local configuration/setup application.
• The catalog includes navigation, code/diffs, reviews, issues/discussions, search, notifications/opt-in alerts, Actions/checks, releases, workspaces, 24 Copilot integration functions, 14 local-center functions and 18 setup functions.
• Reuse browser-safe original Svelte setup presentation/contracts while the existing CLI engine retains credentials, permission audits, current plan approval, provider effects and cleanup. The proposed nonsecret broker cannot proxy the protected web API or acquire Apply authority.
• Preserve the v1 evidence contract and add a closed v2 catalog for the 21 documented command names. Optional regular triage/run writes have independent least-privilege roles and exact reviewed intents; managed refs, policy, merge/deploy and privileged setup remain authoritative handoffs.
• Define optional selected-repository Checks/Commit statuses read grants and canonical check/annotation sources, with native subset fallbacks, explicit unavailable states and no independent merge/approval claim.
• Partition the complete catalog into 12 fixed local family files, with closed index/aggregate schemas, identity/path checks and bounded file sizes; this restores the patches omitted by GitHub's comparison without weakening the Action's progress gate.
• Define 803 distinct future acceptance cases (96 core, 659 feature, 48 center/setup), real-browser/OS evidence, four locales, WCAG 2.2 AA/human UX gates, performance/privacy/security requirements and complete docs.
• Add executable schema/catalog/traceability checks and 19 actual contract-regression tests to the specification commands. Correct the primary SDD publication inventory to create relative to the PR base, reject duplicate traceability rows, distinguish single-operation recovery from bulk outcomes, reconcile notification test traceability and define supported attention channels per browser (Safari toolbar/center; Chrome/Firefox optional OS alerts).

Validation

• Specification/catalog generation and validation pass for all 22 capabilities; the complete 150-feature/21-command/803-case inventory is checked automatically.
• Nineteen contract tests pass, including malformed/duplicate/deferred/incomplete-browser cases and weakened command authorization.
• Five schemas compile; six positive documents validate; the designated invalid-head fixture rejects.
• Documentation validation passes (110 pages/routes), typecheck and whitespace checks pass. The primary SDD's strict consistency check passes against the immutable PR base.
• Normal commit hooks pass: build, lint and 715 Jest suites (12,107 tests passed; 35 skipped), alongside the 19 new specification-contract tests.

This PR delivers specifications, schema fixtures and specification-validation tooling. Extension runtime implementation, execution of the 803 future product cases, real-browser acceptance and store publication are not claimed as completed.

Closes #694

[vypbot]

Current status: All findings originating in this review are resolved.
Last reconciled on 52992df. See aggregate Bugbot status.

🤖 Bugbot review snapshot

Bugbot reported 1 potential problem when commit 535b547 was analyzed. This snapshot is historical; use the status block above for current state. 1 finding is linked to changed code.

Findings

• info: Mark the primary specification as created — specs/github-browser-extension.md:609

[vypbot]

Bugbot: review complete

Current status: No active findings on 52992df.

Pull request · Verified commit · Workflow run

[vypbot]

Copilot approval · Human review needed

Status: Evidence passed; a human reviewer must decide.
Completed: 1/1 observed checks succeeded; Bugbot complete.
Action required: Ask a human reviewer to decide.
Impact: No new approval is confirmed for this revision.
See checks

Technical evidence

Revision: 52992df7de4e; base: c78f75c9d1d1; reason: recommend-mode.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 94.19%. Comparing base (274db40) to head (52992df).
⚠️ Report is 1658 commits behind head on develop.

Additional details and impacted files

@@             Coverage Diff             @@
##           develop     #699      +/-   ##
===========================================
+ Coverage    90.94%   94.19%   +3.24%     
===========================================
  Files          135      976     +841     
  Lines         6251    31741   +25490     
  Branches      1338     9321    +7983     
===========================================
+ Hits          5685    29897   +24212     
- Misses         172      702     +530     
- Partials       394     1142     +748     

see 1043 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[vypbot]

Current status: All findings originating in this review are resolved.
Last reconciled on 52992df. See aggregate Bugbot status.

🤖 Bugbot review snapshot

Bugbot reported 3 potential problems when commit 68d25b0 was analyzed. This snapshot is historical; use the status block above for current state. 3 findings are linked to changed code.

Findings

• medium: Alert monitoring conflicts with the permission ban — specs/github-browser-extension-platforms-and-delivery.md:403
• low: Notification traceability reports the wrong case count — specs/github-browser-extension-functional-catalog.md:398
• low: CAT-NOTIFY case count is inconsistent — specs/github-browser-extension-functional-catalog.md:399

[efraespada]

/copilot recheck

Re-evaluate the two current scope findings against the maintainer's latest complete-product direction, recorded at #694 (comment) and explained in both review replies. The initial issue-body MVP exclusions are superseded. The required deliverable is the complete five-SDD/150-feature contract, with all 21 documented command names, native human-submitted implementation/sync/release/deployment handoffs and separately opted-in closed user-write operations. Read sessions never escalate; Action/maintainer authority, managed refs, merge/deploy and privileged setup remain protected. Removing or deferring those required functions would contradict the current scope. Review the actual permission/intent/provenance safeguards in the current SDDs; classify the obsolete-MVP objections using the latest maintainer clarification. This request is review-only and does not request file changes, a merge or deployment.

[vypbot]

Request could not be completed

Impact: The operation did not accept the supplied input.

Action: Correct the input and retry.

Retained state: No new state or external effect was created.

Error code: validation.invalid-input

Retryable: No

Reference: cb3dbecc-7ba6-4704-afcf-d62d4d75c6c9

[efraespada]

/copilot recheck