chore(snapshot): update canonical snapshot

[github-actions]

User description

Automated update of canonical snapshot generated from Linguist. Please review and merge.

---

PR Type

Other

---

Description

• Updates canonical snapshot.json with latest Linguist data

• Automated snapshot generation and synchronization

---

Diagram Walkthrough

flowchart LR
  Linguist["Linguist Data Source"] -- "generate snapshot" --> Snapshot["canonical/snapshot.json"]

Loading

File Walkthrough

	Relevant files
Configuration changes	snapshot.json Update canonical snapshot data                                                      canonical/snapshot.json Complete snapshot file update with latest Linguist canonical data Automated generation from upstream Linguist repository +14104/-0

---

[qodo-code-review]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
⚪	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: 🏷️ Diff not provided: The PR diff content for canonical/snapshot.json was not available, so it cannot be verified whether any critical actions or related audit logging behavior was introduced or impacted. Referred Code [ { Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: 🏷️ Diff not provided: The PR diff content was not available, so naming and self-documentation quality of any newly introduced identifiers or structures cannot be reviewed. Referred Code [ { Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: 🏷️ Diff not provided: The PR diff content was not available, so it cannot be determined whether any new failure points were introduced without appropriate error handling or edge case management. Referred Code [ { Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: 🏷️ Diff not provided: The PR diff content was not available, so it cannot be verified whether any user-facing error messages or error details could expose internal information. Referred Code [ { Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: 🏷️ Diff not provided: The PR diff content was not available, so it cannot be verified whether any new logging was added or whether any logged content could include sensitive data. Referred Code [ { Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: 🏷️ Diff not provided: The PR diff content was not available, so it cannot be verified whether any external inputs are handled securely or whether the snapshot content introduces sensitive data exposure risks. Referred Code [ { Learn more about managing compliance generic rules or creating your own custom rules

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[qodo-code-review]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
High-level	Optimize the snapshot to reduce repository bloat The large snapshot.json file contains many fields with default values, causing repository bloat. To optimize, modify the generation script to omit these default fields and have the consuming code handle them instead. Examples: canonical/snapshot.json [2-18] { "id": "1c enterprise", "name": "1C Enterprise", "extensions": [ "bsl", "os" ], "aliases": [], "tree_sitter_language": null, "rca_supported": false, ... (clipped 7 lines) Solution Walkthrough: Before: [ { "id": "1c enterprise", "name": "1C Enterprise", "extensions": ["bsl", "os"], "aliases": [], "tree_sitter_language": null, "rca_supported": false, "ast_grep_supported": true, "mime_types": [], "family": null, "is_compiled": false, "language_type": "programming", "pattern_signatures": null }, ... ] After: // Generation script omits fields with default values. // Consuming code applies defaults (e.g., rca_supported: false). [ { "id": "1c enterprise", "name": "1C Enterprise", "extensions": ["bsl", "os"], "language_type": "programming" }, ... ] Suggestion importance[1-10]: 9 __ Why: The suggestion correctly identifies that the large snapshot.json file will cause repository bloat and proposes a valid optimization by omitting default values, which significantly improves long-term maintainability.	High
More

[qodo-code-review]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
🟢	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
⚪	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Diff not available: The PR diff content for canonical/snapshot.json is not provided (token budget limitation), so it cannot be verified whether any critical actions or audit trail requirements are impacted by this snapshot update. Referred Code [ { Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Content not reviewable: The added/changed snapshot content is not visible in the provided diff, so naming/readability characteristics of any newly introduced fields/keys cannot be evaluated. Referred Code [ { Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Sensitive data risk: Because the snapshot file contents are not included in the diff, it cannot be verified that the generated snapshot does not contain sensitive data (PII/secrets) that might later be logged or exposed by consumers of this file. Referred Code [ { Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Data handling unknown: The snapshot content is not available for review, so it cannot be validated whether externally-sourced Linguist data included in canonical/snapshot.json is appropriately sanitized and free of unsafe/secret material. Referred Code [ { Learn more about managing compliance generic rules or creating your own custom rules

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[github-actions]

✅ Gemini Bot Review: Approved

Confidence: 98.0%
Reasoning: The PR updates a generated snapshot file and includes minor, low-risk refinements to a CI workflow for parsing bot responses.

[qodo-code-review]

PR Code Suggestions ✨

No code suggestions found for the PR.