fix: resolve vitest module path resolution for #lib and #utils imports

[Copilot]

• Analyze the failed workflow run
• Apply Vitest 4 migration guide recommendations for module path resolution
• Add missing directory-to-index mappings for subpath imports:
  • #lib/i18n, #lib/schedule, #lib/structures/data
  • #lib/moderation/actions, #lib/moderation/common, #lib/moderation/managers/loggers
  • #utils/resolvers
• Add .ts extension to fallback path resolution for both #lib/* and #utils/* imports
• Run tests to verify fix works (all 281 tests pass)
• Run linting to fix any style issues

Note: The vite-tsconfig-paths plugin was evaluated but is not suitable for this project's subpath imports configuration. The explicit resolve.alias approach with customResolver follows the Vitest 4 migration guide's recommendation for handling complex alias patterns.

Original prompt

fix the failed workflow

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[RedStar071]

@copilot use the guide https://vitest.dev/guide/migration.html#vitest-4 for migration

[Copilot]

@copilot use the guide https://vitest.dev/guide/migration.html#vitest-4 for migration

Applied the Vitest 4 migration guide recommendations. The config uses explicit resolve.alias with customResolver for handling Node.js subpath imports (the vite-tsconfig-paths plugin doesn't fully support subpath import conditions). All paths use absolute resolution via resolve() from node:path with proper .ts extension for fallback file imports. Commit b2a6e3b.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• checkpoint.prisma.io
  • Triggering command: /usr/local/bin/node /usr/local/bin/node /home/REDACTED/work/wolfstar/wolfstar/node_modules/.pnpm/prisma@6.19.0_magicast@0.3.5_typescript@5.7.3/node_modules/prisma/build/child {"product":"prisma","version":"6.19.0","cli_install_type":"local","information":"","local_timestamp":"2025-11-28T23:10:52Z","project_hash":"fc198bae","cli_path":"/home/REDACTED/work/wolfstar/wolfstar/node_modules/prisma/build/index.js","cli_path_hash":"62ad (dns block)
• https://api.github.com//advisories
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node /home/REDACTED/work/_temp/ghcca-node/node/bin/node --enable-source-maps /home/REDACTED/work/_temp/copilot-developer-action-main/dist/index.js (http block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)