Agents updated for Vitest v4

[ejfine]

Why is this change necessary?

With Vitest v4 and the "projects" format, passing in positional arguments at the end of a pnpm script command didn't actually get passed to vitest. e.g. pnpm test-unit -- tests/unit/blah.spec.ts would still run the whole test suite, not just that one file

How does this change address the issue?

Updates Agents.md to tell it not to use the --

What side effects does this change have?

N/A

How is this change tested?

Downstream repos

Summary by CodeRabbit

• Chores
  • Updated multiple tooling dependency versions for compatibility and stability improvements.
  • Updated Bash command permissions configuration.
  • Updated testing documentation guidelines.

[coderabbitai]

📝 Walkthrough

Walkthrough

This PR updates tooling infrastructure: adds GitHub issue viewing permission for Claude, bumps multiple frontend and dependency versions (including Nuxt, Vue tooling, and KiotaBundle), and corrects a test command example by removing an unnecessary separator.

Changes

Maintenance and tooling updates

Layer / File(s)	Summary
Bash command permissions expansion .claude/settings/permissions/bash.jsonc	Adds Bash(gh issue view *) permission to the allow-list, enabling Claude to execute GitHub issue viewing commands.
Dependency version constraint updates extensions/context.py	Bumps ty_version to >=0.0.40, updates Nuxt/Vue-related packages (nuxt_ui_version, nuxt_version, vue_tsc_version, vue_router_version), advances vitest_version, and updates node_kiota_bundle_version to preview 1.0.0-preview.102.
Test command documentation update AGENTS.md	Adjusts the test command example by removing the -- separator after pnpm test-unit, keeping the same test path and --no-coverage options.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~4 minutes

Possibly related PRs

• LabAutomationAndScreening/copier-base-template#137: Updates to extensions/context.py version pins and AGENTS.md testing guidance overlap with shared tooling changes.
• LabAutomationAndScreening/copier-base-template#164: Modifies both .claude/settings/permissions/bash.jsonc and extensions/context.py version pinning for overlapping tooling dependencies.
• LabAutomationAndScreening/copier-base-template#163: Extends Bash gh command permissions in .claude/settings/permissions/bash.jsonc with related GitHub CLI allow-list changes.

Suggested reviewers

• idonaldson
• zendern

🚥 Pre-merge checks | ✅ 3 | ❌ 2

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.
Title check	⚠️ Warning	The title 'Agents updated for Vitest v4' is partially related to the changeset but misses the main objective, which is fixing Vitest v4 positional argument forwarding in test scripts.	Revise the title to better reflect the primary change, such as 'Fix positional argument forwarding in Vitest v4 test scripts' or 'Update test scripts for Vitest v4 compatibility'.

✅ Passed checks (3 passed)

Check name	Status	Explanation
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description check	✅ Passed	The pull request description covers all required template sections with substantive content addressing the Vitest v4 compatibility issue.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@template/copier_template_resources/`{% if template_uses_typescript
%}vitest-run.mjs{% endif %}:
- Line 31: The current noCoverage handling only removes the exact token
"--coverage" from fixed (see variables fixedFiltered, noCoverage, fixed), so
coverage variants like "--coverage=true" or "--coverage.enabled" remain; update
the logic that builds fixedFiltered to either remove any argument that starts
with "--coverage" or matches coverage-enabled patterns (e.g., prefix
"--coverage" or "--coverage."), or alternatively append explicit overrides like
"--coverage=false" and "--coverage.enabled=false" when noCoverage is true so all
Vitest coverage variants are disabled.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 2aafa482-ba5f-402c-8026-241c2fc83fa9

📥 Commits

Reviewing files that changed from the base of the PR and between 8b65dce and 4f7cf63.

📒 Files selected for processing (3)

• .claude/settings/permissions/bash.jsonc
• extensions/context.py
• template/copier_template_resources/{% if template_uses_typescript %}vitest-run.mjs{% endif %}

[zendern]

NIT we should update the PR description to match where we landed for the real fix.