chore(deps-dev): bump @types/chrome from 0.2.2 to 0.2.5

[dependabot]

Summary

Updates the compile-time Chrome extension API declarations from 0.2.2 to 0.2.5.

Root Cause / Decision Record

• Dependabot's dependency-only body does not satisfy Pack's gated PR evidence contract.
• The update changes no runtime package, manifest, permission, host, network, or storage behavior.
• Pack CI passed for head f85659c; this body records the remaining review-gate work.

Scope

• Runtime: none.
• Tests: existing compile/type-check coverage only.
• Docs/governance: PR evidence and review disposition only.
• Explicitly out of scope: extension behavior, portal automation, permissions, release claims, and full-year work.

Pack Workflow Preflight

• Local pnpm workflow:preflight was not run on the Dependabot head; Pack CI is the current head evidence.
• This PR is opened from a Pack branch, not master.
• The current master Pack AGENTS guidance was reviewed.
• PR body keeps the required Pack privacy/review/verification checklist visible.

Sanchika Adoption Gate

• This PR does not consume @sanchika/* packages or copied Sanchika guidance.
• This PR does not import ../sanchika, sanchika/packages/*/src, or parent source paths.

Privacy And Data-Flow Impact

• No new browser permissions.
• No new host permissions.
• No new network calls.
• No analytics, telemetry, ads, or session replay.
• No credential, OTP, CAPTCHA, cookie, token, GST file, or taxpayer-data capture.
• Public copy and privacy declarations are unchanged.

Sensitive Surface Review

• Current tab / portal target binding is unchanged.
• Download completion remains evidence-backed and fail-closed.
• Ambiguous side-effect delivery cannot be reported as confirmed success.
• Service-worker durability impact is unchanged.
• Real taxpayer data, local paths, raw URLs/referrers, and portal HTML are absent from the diff.

Chrome Web Store Impact

• This PR does not expand beyond the existing Chrome Web Store V0 listing.
• Full fiscal year remains source-build alpha and is not part of the Chrome Web Store V0 listing.
• Store copy, README status, Privacy QA, and reviewer instructions are unchanged because user-facing behavior is unchanged.
• CI ZIP creation, provenance, and protected publishing remain release evidence, not manual store-submission sign-off.
• PR title uses Conventional Commits.

Verification

• Pack CI passed for head f85659c.
• Conventional PR Title passed for head f85659c.
• Review threads are empty.
• Review findings gate must rerun after this body update.
• Current-head automated review is requested below.
• Local full-suite/browser-host validation is not required for this declaration-only change; CI remains authoritative.
• git diff --check passed in CI.

Artifact Evidence

• CI run: Pack CI run 450, passed.
• ZIP artifact: not applicable; no release artifact was produced.
• ZIP SHA-256: not applicable.
• Clean source/tag or head SHA: f85659c.

PR Review Follow-Up

• Review findings gate completed for the updated body.
• Autogenerated Codex/bot review completed for the latest head SHA.
• Inline review threads are empty.
• No source commits were pushed after the recorded head.
• No follow-up PRs are implicit.

Thread/comment	Disposition	Commit or evidence
No inline threads	outdated	GraphQL reviewThreads is empty for head f85659c

Screenshots

Not applicable: compile-time declaration-only change.

DCO

• Dependabot commit trailer state is not used as merge evidence; repository DCO enforcement is not currently present.

[dependabot]

Labels

The following labels could not be found: dependencies, triage. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[lamemustafa]

@codex review

Requesting a fresh review of the current Dependabot head after adding the required Pack evidence and disposition register. The dependency diff itself is unchanged.

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Another round soon, please!

Reviewed commit: f85659c48e

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".