chore: add project configuration and tooling setup

[RedStar071]

🔗 Linked issue

N/A

🧭 Context

This PR establishes foundational project configuration and development tooling to improve code quality, consistency, and automation across the repository.

📚 Description

This change introduces several configuration files to standardize development practices and enable automated code review and quality checks:

1. CodeRabbit Configuration (.coderabbit.yaml): Enables automated code reviews with security scanning (gitleaks, OSV scanner), linting tools (actionlint, yamllint, shellcheck, dotenvLint), and pre-merge checks for PR titles and descriptions.

2. EditorConfig (.editorconfig): Standardizes editor settings across the project, defining:

   • UTF-8 encoding and LF line endings for all files
   • Tab indentation (4 spaces) for JavaScript/TypeScript
   • Space indentation (2 spaces) for YAML files
   • Markdown files preserve trailing whitespace

3. NPM Deprecation Config (.npm-deprecaterc.yml): Marks packages matching the pattern *next* as deprecated, specifically targeting @wolfstar/plugin-api.

4. Enhanced .gitignore: Expanded to comprehensively cover:

   • IDE artifacts (VS, IntelliJ)
   • Build outputs and artifacts
   • Environment files with proper examples
   • Package manager caches (pnpm)
   • Test and coverage artifacts
   • Compressed archives

5. Workflow Updates: Updated GitHub Actions to use latest versions:

   • mscharley/dependency-changesets-action: v1.1.9 → v1.2.4
   • zizmorcore/zizmor-action: v0.5.6 → v0.5.7

Key changes

File	Change
.coderabbit.yaml	New: Automated code review configuration
.editorconfig	New: Editor formatting standards
.npm-deprecaterc.yml	New: Package deprecation rules
.gitignore	Enhanced: Comprehensive ignore patterns
.github/workflows/renovate-changeset.yml	Updated: Action version bump
.github/workflows/zizmor.yml	Updated: Action version bump

Type of Change

• New feature (non-breaking change which adds functionality)
• Bug fix (non-breaking change which fixes an issue)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation change
• Workflow / CI change

Pre-flight Checklist

• My code follows the code style of this project
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• I have updated the documentation accordingly
• I added a changeset with pnpm changeset (or pnpm changeset add --empty if no release is needed)

Note: No changeset needed as this is a configuration-only change with no impact on package releases.

https://claude.ai/code/session_01JD3ER4x3yvZMWGRpwPqXvP

---

^{Need help on this PR? Tag /codesmith with what you need. Autofix is enabled.}

Confidence Score: 5/5

Safe to merge with minimal risk.

The changes are limited to repository configuration and pinned workflow action updates, with no accepted functional, workflow-breaking, or security issues found.

No files require special attention.

T-Rex Logs

What T-Rex did

• I ran the lint checks and confirmed all matched files use the correct format.
• I ran the type checker and confirmed one task succeeded out of one, with exit code 0.
• I executed the plugin API tests and verified the results show all tests pass, with 3 test files and 20 tests passing, exit code 0.
• I performed the plugin API build and verified the build completed with exit code 0.
• I validated configuration status and YAML parsing, confirming no changesets to bump and that YAML/configs parsed or read with exit code 0.

_{Ran code and verified through T-Rex}

_{Reviews (2): Last reviewed commit: "fix: revert unintended reformat caused b..." | Re-trigger Greptile}