Add weekly-dev-report skill, LSP bundling, and skill quality fixes

[ydesgagn]

Summary

Adds the weekly-dev-report skill, bundles LSP server configurations for 13 languages so they auto-register on plugin install, and fixes a batch of correctness, security, and lint issues across existing skills and commands.

Key changes:

• Add new weekly-dev-report skill (Jira sprint + GitHub activity report with per-dev achievability ratings, stuck-ticket flags, and worklog audit)
• Add lspServers block to plugin.json for 13 languages (TypeScript, Python, Ruby, Go, Bash, Rust, YAML, Swift, PHP, Kotlin, Java, C/C++, Perl)
• Expand .mcp.json with additional MCP server configurations and fix tilde expansion in Playwright user-data path
• README: add LSP setup section with per-OS install instructions and weekly-dev-report skill row
• Add frontmatter (description, argument-hint, allowed-tools) to code-review-deep and work-issue commands
• Fix wrong/non-existent MCP tool names in analyze-db, query-db, aws (e.g., mcp__mongodb__listDatabases → list-databases, mcp__aws__execute_api → aws___call_aws)
• Fix MySQL password leakage via process listings — replaced all --password= flags with the MYSQL_PWD env var pattern
• Fix loco skill: distinguish 404 vs real errors when checking key existence; redact secret values from env | grep output
• Fix weekly-dev-report jq off-by-one filter bug (index() != null) and remove hardcoded DEV- prefix
• Make Jira config-path lookup robust across platforms in sprint-summary and weekly-dev-report
• Fix BSD/GNU date portability in the aws skill
• Remove invalid Bash(DEFAULT_BRANCH=:*) permission from create-pr
• Replace mcp__github__search_repositories (search-only) with mcp__github__get_file_contents in three review-* skills
• Trim unused tool grants and replace hardcoded recipient email in weekly-dev-report with WEEKLY_DEV_REPORT_TO env var
• Fix markdownlint MD060/MD032 violations (table alignment, list spacing); all linters now pass

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 ?: skills/commands are markdown specs; this repo has no automated test framework. Verified via linters and the plugin-validator agent.
• 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