Update skills: playstore MCP, code-review path, verify-resolved-issues

[ydesgagn]

Summary

Refreshes several plugin components to reflect new MCP server choices and improved workflows. The playstore skill now uses the maintained play-store-mcp server (launched via uvx) instead of the unmaintained npx package, and its tool list and credentials env var are updated to match. The code-review-deep command moves its report output from the repo root to docs/code-review.md, with stricter markdown-lint rules so the generated report passes markdownlint-cli2 cleanly. The work-issue command makes worktree usage opt-in (auto-detected from the repo) so it doesn't impose worktrees on teams that don't already use them. A new verify-resolved-issues skill audits issues parked in "resolved/fixed/done" but not yet closed, verifies the fix actually exists in the codebase, and either closes them with a summary or kicks them back to the resolver.

Key changes:

• skills/playstore/SKILL.md + .mcp.json: switch to uvx play-store-mcp; update MCP tool table (get_vitals_overview, get_vitals_metrics, list_apps, etc.); rename credentials env var to GOOGLE_APPLICATION_CREDENTIALS
• commands/code-review-deep.md: report path moves from CODE_REVIEW_REPORT.md to docs/code-review.md; add markdown-lint compliance rules (MD012/MD031/MD032/MD033/MD040/MD047); replace <details>/<summary> collapsibles with plain bulleted lists
• commands/work-issue.md: detect existing worktree usage and split step 3 / cleanup into Path A (plain branch, default) and Path B (worktree)
• skills/verify-resolved-issues/SKILL.md: new skill for auditing resolved-but-not-closed issues across GitHub and Jira with dry-run-by-default safety
• README.md: update skills table entries for playstore and add a row for verify-resolved-issues
• .gitignore: ignore generated docs/code-review.md

Types of changes

• Bugfix (fixes an issue)
• New feature (adds functionality)
• Refactoring (improves code without changing functionality)
• Breaking change (incompatible changes)
• Build or security update (updates dependencies, libraries, or security patches)
• Code style or documentation update (formatting, renaming, or documentation changes)
• Other (please describe):

Checklist

• Unit tests added to validate my fix/feature
• I have manually tested my change
• I did not add automation test. Why ?: Plugin content is markdown/JSON; no executable test harness in this repo.
• Database changes requiring migration with downtime or reprocessing of existing data
• The SOUP file lists the risk Level, requirements and verification reasoning associated with each library
• readme.md includes sections on introduction, installation, usage, and contributing
• docs/architecture.md includes sections on the architecture diagram, software units, software of unknown provenance, critical algorithms and risk controls related to PII and security
• Impact on PII, privacy regulations (CCPA/GDPR/PIPEDA), CIS benchmarks or security (availability/confidentiality/integrity); management must be notified