chore: synchronize reviewed local changes

[sebastianspicker]

Publishes the reviewed local repository changes while preserving the existing commit history. Local-only maintenance artifacts remain ignored and are not included.

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 complexity · 0 duplication

Metric	Results
Complexity	0
Duplication	0

View in Codacy

AI Reviewer: first review requested successfully. AI can make mistakes. Always validate suggestions.

_{TIP This summary will be updated as you push new changes.}

[codacy-production]

Pull Request Overview

This pull request synchronizes local repository changes with the remote, focusing on the introduction of a comprehensive Codacy static analysis configuration and dependency updates. While the project remains up to standards, the introduction of multiple configuration files—specifically .codacy/codacy.yaml and .codacy/codacy.config.json—alongside the existing root-level configuration creates fragmentation that may lead to maintenance difficulties and conflicting analysis results.

A significant issue is the size and redundancy within the new .codacy/codacy.config.json. The configuration contains thousands of explicit file exclusions that are already covered by broader glob patterns defined later in the same file. Additionally, the PR description is relatively vague, providing little context for why specific dependency pinning strategies or linter rules were modified, which complicates the review of these mixed concerns.

About this PR

• The PR description 'synchronize reviewed local changes' is vague and provides limited context on the reasoning behind specific dependency version changes or linter rule updates. Furthermore, the PR mixes unrelated concerns by combining static analysis tool configuration with dependency version upgrades and workspace-level overrides in a single set of changes.

Test suggestions

• Verify that .gitignore correctly allows .codacy config files while ignoring other potential local artifacts in that directory.
• Verify that the project builds and existing tests pass with the upgraded pytest and vite versions.
• Confirm the Codacy configuration file (.codacy/codacy.config.json) is parseable and valid according to Codacy's schema.
• Verify that transitive overrides for fast-uri, nanoid, postcss, and undici solve target dependency issues without breaking the build.

Prompt proposal for missing tests

Consider implementing these tests if applicable:
1. Verify that the project builds and existing tests pass with the upgraded pytest and vite versions.
2. Confirm the Codacy configuration file (.codacy/codacy.config.json) is parseable and valid according to Codacy's schema.
3. Verify that transitive overrides for fast-uri, nanoid, postcss, and undici solve target dependency issues without breaking the build.

_{TIP Improve review quality by adding custom instructions
TIP How was this review? Give us feedback}

[codacy-production]

_{🟡 MEDIUM RISK}

Multiple configuration files for the same analysis tool suite are being introduced (.codacy/codacy.yaml and .codacy/codacy.config.json in addition to the root-level .codacy.yaml). This fragmentation makes it difficult to manage settings. It is recommended to consolidate these configurations into the root-level file to ensure consistent results.

[codacy-production]

_{🟡 MEDIUM RISK}

Suggestion: The exclude array contains thousands of specific file paths that are redundant because they are already covered by broader glob patterns such as data/**/*.json, example/**/*.json, and test/**/*.test.ts. This significantly increases the configuration size and complicates maintenance. Consider removing these individual entries in favor of the existing glob patterns.