Merge remote issue-762 branch to resolve non-fast-forward push rejection

[itsmiso-ai]

Add Vitest code coverage support with @vitest/coverage-v8 dependency and coverage configuration in vitest.config.ts

Fixes#762

Opened by foreman on review GO (workload wl-misospace-dispatch-762).

Superseded by a newer automated review for this pull request.

[itsmiso-ai]

⚠️ This PR fix item has been marked as BLOCKED and needs human attention.

Reason: Failing check: npm audit (failure)

Latest note: foreman fix Workload prfix-misospace-dispatch-783 succeeded but PR is still not mergeable after 3/3 attempts

Posted automatically by Dispatch on 2026-08-18T02:15:06.995Z

Superseded by a newer automated review for this pull request.

[its-saffron]

AI Automated Review

Full PR review.

Analysis engine: dsv4f@https://litellm.jory.dev/v1 (openai) — primary route

Recommendation

Approve. This PR resolves issue PR 762 by adding the missing @vitest/coverage-v8 devDependency, wiring a coverage configuration with thresholds into vitest.config.ts, and adding a dedicated Coverage job to CI. All CI checks (including the new Coverage job) passed on the head commit, and the change is consistent with the repository's existing CI conventions.

Change-by-Change Findings

.github/workflows/ci.yaml

• Adds a coverage job that runs npm run test:coverage on ubuntu-latest, using the same pinned actions/checkout commit and the repository's shared ./.github/actions/setup-node action as the other jobs. This matches the existing CI structure and satisfies the issue's acceptance criterion that CI runs coverage on every push/PR.
• The job inherits the workflow-level permissions: contents: read and the DATABASE_URL env var, consistent with the test job.

package.json

• Adds @vitest/coverage-v8: ^4.1.8 to devDependencies. The installed lockfile version is 4.1.10, which exactly matches the vitest version already present (4.1.10), satisfying the package's peer dependency requirement (vitest: 4.1.10).
• The only other change is a cosmetic reflow of the overrides rationale comment (em-dash formatting); no override values changed.

package-lock.json

• Adds @vitest/coverage-v8@4.1.10 and its transitive dependencies (@bcoe/v8-coverage, ast-v8-to-istanbul, istanbul-lib-*, magicast, make-dir, supports-color, html-escaper, has-flag, std-env, js-tokens).
• The dev → devOptional flips on several @babel/* packages are a normal npm lockfile side effect of magicast (which is devOptional) depending on them; they do not change runtime behavior.
• No existing dependency versions were upgraded, so there is no breaking-change surface from this PR.

vitest.config.ts

• Adds a coverage block with provider: "v8", reporters text, html, json-summary, an include/exclude set scoped to src/**/*.{ts,tsx}, and thresholds (statements 75, branches 65, functions 70, lines 75).
• The thresholds are documented as being set below the measured baseline, which is a reasonable way to introduce a coverage gate without blocking on the current snapshot. The comment explicitly records the baseline numbers, which is good practice.
• The exclude list correctly omits test files, story files, __tests__ directories, and src/types/**.

Standards Compliance

The change follows the repository's AGENTS.md conventions:

• CI jobs use the shared ./.github/actions/setup-node action and pinned actions/checkout commit, consistent with the existing lint, typecheck, test, and build jobs.
• The new dependency is a devDependency only; no production dependencies or runtime behavior are affected.
• No secrets, environment files, or build output are committed.
• The test:coverage script already existed in package.json; this PR makes it functional rather than introducing a new script.

Linked Issue Fit

Issue PR 762 asked for:

1. npm run test:coverage completes and emits a coverage report — satisfied; the dependency is installed and the config is valid. The CI Coverage job passed, which exercises the script end-to-end.
2. @vitest/coverage-v8 listed in devDependencies — satisfied (^4.1.8 in package.json, 4.1.10 resolved in the lockfile).
3. CI runs coverage on every push/PR, or the script is removed — satisfied; a dedicated coverage job was added to .github/workflows/ci.yaml.

All acceptance criteria are met. The issue's expected files (package.json, vitest.config.ts, .github/workflows/ci.yaml) are exactly the files changed.

Tool Harness Findings

No tool harness findings were produced for this PR.

Unknowns or Needs Verification

• The coverage thresholds were set below the measured baseline, so the gate will not catch gradual coverage erosion until a metric drops below the threshold. This is a deliberate, documented tradeoff and not a blocker.
• The coverage CI job does not upload or publish the coverage report artifact; it only fails/succeeds on the threshold gate. If the team wants a browsable report, that would be a follow-up enhancement, not a requirement of the linked issue.

Must-Check Items

• Check for breaking API changes in updated dependencies: No existing dependency versions were upgraded in this PR. The only new dependency is @vitest/coverage-v8@4.1.10, which is a dev-only coverage provider that exactly matches the already-installed vitest@4.1.10 peer requirement. No breaking-change risk identified.
• Run full test suite after upgrade: The CI Tests job (npm run test) passed on the head commit, and the new Coverage job (npm run test:coverage) also passed. The full suite is green.

[itsmiso-ai]

Add Vitest code coverage support with @vitest/coverage-v8 dependency and coverage configuration in vitest.config.ts

Fixes#762

Opened by foreman on review GO (workload wl-misospace-dispatch-762).

Superseded by a newer automated review for this pull request.

[itsmiso-ai]

⚠️ This PR fix item has been marked as BLOCKED and needs human attention.

Reason: Failing check: npm audit (failure)

Latest note: foreman fix Workload prfix-misospace-dispatch-783 succeeded but PR is still not mergeable after 3/3 attempts

Posted automatically by Dispatch on 2026-08-18T02:15:06.995Z

Superseded by a newer automated review for this pull request.

[its-saffron]

AI Automated Review

Full PR review.

Analysis engine: dsv4f@https://litellm.jory.dev/v1 (openai) — primary route

Recommendation

Approve. This PR resolves issue PR 762 by adding the missing @vitest/coverage-v8 devDependency, wiring a coverage configuration with thresholds into vitest.config.ts, and adding a dedicated Coverage job to CI. All CI checks (including the new Coverage job) passed on the head commit, and the change is consistent with the repository's existing CI conventions.

Change-by-Change Findings

.github/workflows/ci.yaml

• Adds a coverage job that runs npm run test:coverage on ubuntu-latest, using the same pinned actions/checkout commit and the repository's shared ./.github/actions/setup-node action as the other jobs. This matches the existing CI structure and satisfies the issue's acceptance criterion that CI runs coverage on every push/PR.
• The job inherits the workflow-level permissions: contents: read and the DATABASE_URL env var, consistent with the test job.

package.json

• Adds @vitest/coverage-v8: ^4.1.8 to devDependencies. The installed lockfile version is 4.1.10, which exactly matches the vitest version already present (4.1.10), satisfying the package's peer dependency requirement (vitest: 4.1.10).
• The only other change is a cosmetic reflow of the overrides rationale comment (em-dash formatting); no override values changed.

package-lock.json

• Adds @vitest/coverage-v8@4.1.10 and its transitive dependencies (@bcoe/v8-coverage, ast-v8-to-istanbul, istanbul-lib-*, magicast, make-dir, supports-color, html-escaper, has-flag, std-env, js-tokens).
• The dev → devOptional flips on several @babel/* packages are a normal npm lockfile side effect of magicast (which is devOptional) depending on them; they do not change runtime behavior.
• No existing dependency versions were upgraded, so there is no breaking-change surface from this PR.

vitest.config.ts

• Adds a coverage block with provider: "v8", reporters text, html, json-summary, an include/exclude set scoped to src/**/*.{ts,tsx}, and thresholds (statements 75, branches 65, functions 70, lines 75).
• The thresholds are documented as being set below the measured baseline, which is a reasonable way to introduce a coverage gate without blocking on the current snapshot. The comment explicitly records the baseline numbers, which is good practice.
• The exclude list correctly omits test files, story files, __tests__ directories, and src/types/**.

Standards Compliance

The change follows the repository's AGENTS.md conventions:

• CI jobs use the shared ./.github/actions/setup-node action and pinned actions/checkout commit, consistent with the existing lint, typecheck, test, and build jobs.
• The new dependency is a devDependency only; no production dependencies or runtime behavior are affected.
• No secrets, environment files, or build output are committed.
• The test:coverage script already existed in package.json; this PR makes it functional rather than introducing a new script.

Linked Issue Fit

Issue PR 762 asked for:

1. npm run test:coverage completes and emits a coverage report — satisfied; the dependency is installed and the config is valid. The CI Coverage job passed, which exercises the script end-to-end.
2. @vitest/coverage-v8 listed in devDependencies — satisfied (^4.1.8 in package.json, 4.1.10 resolved in the lockfile).
3. CI runs coverage on every push/PR, or the script is removed — satisfied; a dedicated coverage job was added to .github/workflows/ci.yaml.

All acceptance criteria are met. The issue's expected files (package.json, vitest.config.ts, .github/workflows/ci.yaml) are exactly the files changed.

Tool Harness Findings

No tool harness findings were produced for this PR.

Unknowns or Needs Verification

• The coverage thresholds were set below the measured baseline, so the gate will not catch gradual coverage erosion until a metric drops below the threshold. This is a deliberate, documented tradeoff and not a blocker.
• The coverage CI job does not upload or publish the coverage report artifact; it only fails/succeeds on the threshold gate. If the team wants a browsable report, that would be a follow-up enhancement, not a requirement of the linked issue.

Must-Check Items

• Check for breaking API changes in updated dependencies: No existing dependency versions were upgraded in this PR. The only new dependency is @vitest/coverage-v8@4.1.10, which is a dev-only coverage provider that exactly matches the already-installed vitest@4.1.10 peer requirement. No breaking-change risk identified.
• Run full test suite after upgrade: The CI Tests job (npm run test) passed on the head commit, and the new Coverage job (npm run test:coverage) also passed. The full suite is green.

[itsmiso-ai]

Add Vitest code coverage support with @vitest/coverage-v8 dependency and coverage configuration in vitest.config.ts

Fixes#762

Opened by foreman on review GO (workload wl-misospace-dispatch-762).

Superseded by a newer automated review for this pull request.

[itsmiso-ai]

⚠️ This PR fix item has been marked as BLOCKED and needs human attention.

Reason: Failing check: npm audit (failure)

Latest note: foreman fix Workload prfix-misospace-dispatch-783 succeeded but PR is still not mergeable after 3/3 attempts

Posted automatically by Dispatch on 2026-08-18T02:15:06.995Z

Superseded by a newer automated review for this pull request.

[its-saffron]

AI Automated Review

Full PR review.

Analysis engine: dsv4f@https://litellm.jory.dev/v1 (openai) — primary route

Recommendation

Approve. This PR resolves issue PR 762 by adding the missing @vitest/coverage-v8 devDependency, wiring a coverage configuration with thresholds into vitest.config.ts, and adding a dedicated Coverage job to CI. All CI checks (including the new Coverage job) passed on the head commit, and the change is consistent with the repository's existing CI conventions.

Change-by-Change Findings

.github/workflows/ci.yaml

• Adds a coverage job that runs npm run test:coverage on ubuntu-latest, using the same pinned actions/checkout commit and the repository's shared ./.github/actions/setup-node action as the other jobs. This matches the existing CI structure and satisfies the issue's acceptance criterion that CI runs coverage on every push/PR.
• The job inherits the workflow-level permissions: contents: read and the DATABASE_URL env var, consistent with the test job.

package.json

• Adds @vitest/coverage-v8: ^4.1.8 to devDependencies. The installed lockfile version is 4.1.10, which exactly matches the vitest version already present (4.1.10), satisfying the package's peer dependency requirement (vitest: 4.1.10).
• The only other change is a cosmetic reflow of the overrides rationale comment (em-dash formatting); no override values changed.

package-lock.json

• Adds @vitest/coverage-v8@4.1.10 and its transitive dependencies (@bcoe/v8-coverage, ast-v8-to-istanbul, istanbul-lib-*, magicast, make-dir, supports-color, html-escaper, has-flag, std-env, js-tokens).
• The dev → devOptional flips on several @babel/* packages are a normal npm lockfile side effect of magicast (which is devOptional) depending on them; they do not change runtime behavior.
• No existing dependency versions were upgraded, so there is no breaking-change surface from this PR.

vitest.config.ts

• Adds a coverage block with provider: "v8", reporters text, html, json-summary, an include/exclude set scoped to src/**/*.{ts,tsx}, and thresholds (statements 75, branches 65, functions 70, lines 75).
• The thresholds are documented as being set below the measured baseline, which is a reasonable way to introduce a coverage gate without blocking on the current snapshot. The comment explicitly records the baseline numbers, which is good practice.
• The exclude list correctly omits test files, story files, __tests__ directories, and src/types/**.

Standards Compliance

The change follows the repository's AGENTS.md conventions:

• CI jobs use the shared ./.github/actions/setup-node action and pinned actions/checkout commit, consistent with the existing lint, typecheck, test, and build jobs.
• The new dependency is a devDependency only; no production dependencies or runtime behavior are affected.
• No secrets, environment files, or build output are committed.
• The test:coverage script already existed in package.json; this PR makes it functional rather than introducing a new script.

Linked Issue Fit

Issue PR 762 asked for:

1. npm run test:coverage completes and emits a coverage report — satisfied; the dependency is installed and the config is valid. The CI Coverage job passed, which exercises the script end-to-end.
2. @vitest/coverage-v8 listed in devDependencies — satisfied (^4.1.8 in package.json, 4.1.10 resolved in the lockfile).
3. CI runs coverage on every push/PR, or the script is removed — satisfied; a dedicated coverage job was added to .github/workflows/ci.yaml.

All acceptance criteria are met. The issue's expected files (package.json, vitest.config.ts, .github/workflows/ci.yaml) are exactly the files changed.

Tool Harness Findings

No tool harness findings were produced for this PR.

Unknowns or Needs Verification

• The coverage thresholds were set below the measured baseline, so the gate will not catch gradual coverage erosion until a metric drops below the threshold. This is a deliberate, documented tradeoff and not a blocker.
• The coverage CI job does not upload or publish the coverage report artifact; it only fails/succeeds on the threshold gate. If the team wants a browsable report, that would be a follow-up enhancement, not a requirement of the linked issue.

Must-Check Items

• Check for breaking API changes in updated dependencies: No existing dependency versions were upgraded in this PR. The only new dependency is @vitest/coverage-v8@4.1.10, which is a dev-only coverage provider that exactly matches the already-installed vitest@4.1.10 peer requirement. No breaking-change risk identified.
• Run full test suite after upgrade: The CI Tests job (npm run test) passed on the head commit, and the new Coverage job (npm run test:coverage) also passed. The full suite is green.

[itsmiso-ai]

Add Vitest code coverage support with @vitest/coverage-v8 dependency and coverage configuration in vitest.config.ts

Fixes#762

Opened by foreman on review GO (workload wl-misospace-dispatch-762).

Superseded by a newer automated review for this pull request.

[itsmiso-ai]

⚠️ This PR fix item has been marked as BLOCKED and needs human attention.

Reason: Failing check: npm audit (failure)

Latest note: foreman fix Workload prfix-misospace-dispatch-783 succeeded but PR is still not mergeable after 3/3 attempts

Posted automatically by Dispatch on 2026-08-18T02:15:06.995Z

Superseded by a newer automated review for this pull request.

[its-saffron]

AI Automated Review

Full PR review.

Analysis engine: dsv4f@https://litellm.jory.dev/v1 (openai) — primary route

Recommendation

Approve. This PR resolves issue PR 762 by adding the missing @vitest/coverage-v8 devDependency, wiring a coverage configuration with thresholds into vitest.config.ts, and adding a dedicated Coverage job to CI. All CI checks (including the new Coverage job) passed on the head commit, and the change is consistent with the repository's existing CI conventions.

Change-by-Change Findings

.github/workflows/ci.yaml

• Adds a coverage job that runs npm run test:coverage on ubuntu-latest, using the same pinned actions/checkout commit and the repository's shared ./.github/actions/setup-node action as the other jobs. This matches the existing CI structure and satisfies the issue's acceptance criterion that CI runs coverage on every push/PR.
• The job inherits the workflow-level permissions: contents: read and the DATABASE_URL env var, consistent with the test job.

package.json

• Adds @vitest/coverage-v8: ^4.1.8 to devDependencies. The installed lockfile version is 4.1.10, which exactly matches the vitest version already present (4.1.10), satisfying the package's peer dependency requirement (vitest: 4.1.10).
• The only other change is a cosmetic reflow of the overrides rationale comment (em-dash formatting); no override values changed.

package-lock.json

• Adds @vitest/coverage-v8@4.1.10 and its transitive dependencies (@bcoe/v8-coverage, ast-v8-to-istanbul, istanbul-lib-*, magicast, make-dir, supports-color, html-escaper, has-flag, std-env, js-tokens).
• The dev → devOptional flips on several @babel/* packages are a normal npm lockfile side effect of magicast (which is devOptional) depending on them; they do not change runtime behavior.
• No existing dependency versions were upgraded, so there is no breaking-change surface from this PR.

vitest.config.ts

• Adds a coverage block with provider: "v8", reporters text, html, json-summary, an include/exclude set scoped to src/**/*.{ts,tsx}, and thresholds (statements 75, branches 65, functions 70, lines 75).
• The thresholds are documented as being set below the measured baseline, which is a reasonable way to introduce a coverage gate without blocking on the current snapshot. The comment explicitly records the baseline numbers, which is good practice.
• The exclude list correctly omits test files, story files, __tests__ directories, and src/types/**.

Standards Compliance

The change follows the repository's AGENTS.md conventions:

• CI jobs use the shared ./.github/actions/setup-node action and pinned actions/checkout commit, consistent with the existing lint, typecheck, test, and build jobs.
• The new dependency is a devDependency only; no production dependencies or runtime behavior are affected.
• No secrets, environment files, or build output are committed.
• The test:coverage script already existed in package.json; this PR makes it functional rather than introducing a new script.

Linked Issue Fit

Issue PR 762 asked for:

1. npm run test:coverage completes and emits a coverage report — satisfied; the dependency is installed and the config is valid. The CI Coverage job passed, which exercises the script end-to-end.
2. @vitest/coverage-v8 listed in devDependencies — satisfied (^4.1.8 in package.json, 4.1.10 resolved in the lockfile).
3. CI runs coverage on every push/PR, or the script is removed — satisfied; a dedicated coverage job was added to .github/workflows/ci.yaml.

All acceptance criteria are met. The issue's expected files (package.json, vitest.config.ts, .github/workflows/ci.yaml) are exactly the files changed.

Tool Harness Findings

No tool harness findings were produced for this PR.

Unknowns or Needs Verification

• The coverage thresholds were set below the measured baseline, so the gate will not catch gradual coverage erosion until a metric drops below the threshold. This is a deliberate, documented tradeoff and not a blocker.
• The coverage CI job does not upload or publish the coverage report artifact; it only fails/succeeds on the threshold gate. If the team wants a browsable report, that would be a follow-up enhancement, not a requirement of the linked issue.

Must-Check Items

• Check for breaking API changes in updated dependencies: No existing dependency versions were upgraded in this PR. The only new dependency is @vitest/coverage-v8@4.1.10, which is a dev-only coverage provider that exactly matches the already-installed vitest@4.1.10 peer requirement. No breaking-change risk identified.
• Run full test suite after upgrade: The CI Tests job (npm run test) passed on the head commit, and the new Coverage job (npm run test:coverage) also passed. The full suite is green.

[itsmiso-ai]

Add Vitest code coverage support with @vitest/coverage-v8 dependency and coverage configuration in vitest.config.ts

Fixes#762

Opened by foreman on review GO (workload wl-misospace-dispatch-762).

Superseded by a newer automated review for this pull request.

[itsmiso-ai]

⚠️ This PR fix item has been marked as BLOCKED and needs human attention.

Reason: Failing check: npm audit (failure)

Latest note: foreman fix Workload prfix-misospace-dispatch-783 succeeded but PR is still not mergeable after 3/3 attempts

Posted automatically by Dispatch on 2026-08-18T02:15:06.995Z

Superseded by a newer automated review for this pull request.

[its-saffron]

AI Automated Review

Full PR review.

Analysis engine: dsv4f@https://litellm.jory.dev/v1 (openai) — primary route

Recommendation

Approve. This PR resolves issue PR 762 by adding the missing @vitest/coverage-v8 devDependency, wiring a coverage configuration with thresholds into vitest.config.ts, and adding a dedicated Coverage job to CI. All CI checks (including the new Coverage job) passed on the head commit, and the change is consistent with the repository's existing CI conventions.

Change-by-Change Findings

.github/workflows/ci.yaml

• Adds a coverage job that runs npm run test:coverage on ubuntu-latest, using the same pinned actions/checkout commit and the repository's shared ./.github/actions/setup-node action as the other jobs. This matches the existing CI structure and satisfies the issue's acceptance criterion that CI runs coverage on every push/PR.
• The job inherits the workflow-level permissions: contents: read and the DATABASE_URL env var, consistent with the test job.

package.json

• Adds @vitest/coverage-v8: ^4.1.8 to devDependencies. The installed lockfile version is 4.1.10, which exactly matches the vitest version already present (4.1.10), satisfying the package's peer dependency requirement (vitest: 4.1.10).
• The only other change is a cosmetic reflow of the overrides rationale comment (em-dash formatting); no override values changed.

package-lock.json

• Adds @vitest/coverage-v8@4.1.10 and its transitive dependencies (@bcoe/v8-coverage, ast-v8-to-istanbul, istanbul-lib-*, magicast, make-dir, supports-color, html-escaper, has-flag, std-env, js-tokens).
• The dev → devOptional flips on several @babel/* packages are a normal npm lockfile side effect of magicast (which is devOptional) depending on them; they do not change runtime behavior.
• No existing dependency versions were upgraded, so there is no breaking-change surface from this PR.

vitest.config.ts

• Adds a coverage block with provider: "v8", reporters text, html, json-summary, an include/exclude set scoped to src/**/*.{ts,tsx}, and thresholds (statements 75, branches 65, functions 70, lines 75).
• The thresholds are documented as being set below the measured baseline, which is a reasonable way to introduce a coverage gate without blocking on the current snapshot. The comment explicitly records the baseline numbers, which is good practice.
• The exclude list correctly omits test files, story files, __tests__ directories, and src/types/**.

Standards Compliance

The change follows the repository's AGENTS.md conventions:

• CI jobs use the shared ./.github/actions/setup-node action and pinned actions/checkout commit, consistent with the existing lint, typecheck, test, and build jobs.
• The new dependency is a devDependency only; no production dependencies or runtime behavior are affected.
• No secrets, environment files, or build output are committed.
• The test:coverage script already existed in package.json; this PR makes it functional rather than introducing a new script.

Linked Issue Fit

Issue PR 762 asked for:

1. npm run test:coverage completes and emits a coverage report — satisfied; the dependency is installed and the config is valid. The CI Coverage job passed, which exercises the script end-to-end.
2. @vitest/coverage-v8 listed in devDependencies — satisfied (^4.1.8 in package.json, 4.1.10 resolved in the lockfile).
3. CI runs coverage on every push/PR, or the script is removed — satisfied; a dedicated coverage job was added to .github/workflows/ci.yaml.

All acceptance criteria are met. The issue's expected files (package.json, vitest.config.ts, .github/workflows/ci.yaml) are exactly the files changed.

Tool Harness Findings

No tool harness findings were produced for this PR.

Unknowns or Needs Verification

• The coverage thresholds were set below the measured baseline, so the gate will not catch gradual coverage erosion until a metric drops below the threshold. This is a deliberate, documented tradeoff and not a blocker.
• The coverage CI job does not upload or publish the coverage report artifact; it only fails/succeeds on the threshold gate. If the team wants a browsable report, that would be a follow-up enhancement, not a requirement of the linked issue.

Must-Check Items

• Check for breaking API changes in updated dependencies: No existing dependency versions were upgraded in this PR. The only new dependency is @vitest/coverage-v8@4.1.10, which is a dev-only coverage provider that exactly matches the already-installed vitest@4.1.10 peer requirement. No breaking-change risk identified.
• Run full test suite after upgrade: The CI Tests job (npm run test) passed on the head commit, and the new Coverage job (npm run test:coverage) also passed. The full suite is green.

[itsmiso-ai]

Add Vitest code coverage support with @vitest/coverage-v8 dependency and coverage configuration in vitest.config.ts

Fixes#762

Opened by foreman on review GO (workload wl-misospace-dispatch-762).

Superseded by a newer automated review for this pull request.

[itsmiso-ai]

⚠️ This PR fix item has been marked as BLOCKED and needs human attention.

Reason: Failing check: npm audit (failure)

Latest note: foreman fix Workload prfix-misospace-dispatch-783 succeeded but PR is still not mergeable after 3/3 attempts

Posted automatically by Dispatch on 2026-08-18T02:15:06.995Z

Superseded by a newer automated review for this pull request.

[its-saffron]

AI Automated Review

Full PR review.

Analysis engine: dsv4f@https://litellm.jory.dev/v1 (openai) — primary route

Recommendation

Approve. This PR resolves issue PR 762 by adding the missing @vitest/coverage-v8 devDependency, wiring a coverage configuration with thresholds into vitest.config.ts, and adding a dedicated Coverage job to CI. All CI checks (including the new Coverage job) passed on the head commit, and the change is consistent with the repository's existing CI conventions.

Change-by-Change Findings

.github/workflows/ci.yaml

• Adds a coverage job that runs npm run test:coverage on ubuntu-latest, using the same pinned actions/checkout commit and the repository's shared ./.github/actions/setup-node action as the other jobs. This matches the existing CI structure and satisfies the issue's acceptance criterion that CI runs coverage on every push/PR.
• The job inherits the workflow-level permissions: contents: read and the DATABASE_URL env var, consistent with the test job.

package.json

• Adds @vitest/coverage-v8: ^4.1.8 to devDependencies. The installed lockfile version is 4.1.10, which exactly matches the vitest version already present (4.1.10), satisfying the package's peer dependency requirement (vitest: 4.1.10).
• The only other change is a cosmetic reflow of the overrides rationale comment (em-dash formatting); no override values changed.

package-lock.json

• Adds @vitest/coverage-v8@4.1.10 and its transitive dependencies (@bcoe/v8-coverage, ast-v8-to-istanbul, istanbul-lib-*, magicast, make-dir, supports-color, html-escaper, has-flag, std-env, js-tokens).
• The dev → devOptional flips on several @babel/* packages are a normal npm lockfile side effect of magicast (which is devOptional) depending on them; they do not change runtime behavior.
• No existing dependency versions were upgraded, so there is no breaking-change surface from this PR.

vitest.config.ts

• Adds a coverage block with provider: "v8", reporters text, html, json-summary, an include/exclude set scoped to src/**/*.{ts,tsx}, and thresholds (statements 75, branches 65, functions 70, lines 75).
• The thresholds are documented as being set below the measured baseline, which is a reasonable way to introduce a coverage gate without blocking on the current snapshot. The comment explicitly records the baseline numbers, which is good practice.
• The exclude list correctly omits test files, story files, __tests__ directories, and src/types/**.

Standards Compliance

The change follows the repository's AGENTS.md conventions:

• CI jobs use the shared ./.github/actions/setup-node action and pinned actions/checkout commit, consistent with the existing lint, typecheck, test, and build jobs.
• The new dependency is a devDependency only; no production dependencies or runtime behavior are affected.
• No secrets, environment files, or build output are committed.
• The test:coverage script already existed in package.json; this PR makes it functional rather than introducing a new script.

Linked Issue Fit

Issue PR 762 asked for:

1. npm run test:coverage completes and emits a coverage report — satisfied; the dependency is installed and the config is valid. The CI Coverage job passed, which exercises the script end-to-end.
2. @vitest/coverage-v8 listed in devDependencies — satisfied (^4.1.8 in package.json, 4.1.10 resolved in the lockfile).
3. CI runs coverage on every push/PR, or the script is removed — satisfied; a dedicated coverage job was added to .github/workflows/ci.yaml.

All acceptance criteria are met. The issue's expected files (package.json, vitest.config.ts, .github/workflows/ci.yaml) are exactly the files changed.

Tool Harness Findings

No tool harness findings were produced for this PR.

Unknowns or Needs Verification

• The coverage thresholds were set below the measured baseline, so the gate will not catch gradual coverage erosion until a metric drops below the threshold. This is a deliberate, documented tradeoff and not a blocker.
• The coverage CI job does not upload or publish the coverage report artifact; it only fails/succeeds on the threshold gate. If the team wants a browsable report, that would be a follow-up enhancement, not a requirement of the linked issue.

Must-Check Items

• Check for breaking API changes in updated dependencies: No existing dependency versions were upgraded in this PR. The only new dependency is @vitest/coverage-v8@4.1.10, which is a dev-only coverage provider that exactly matches the already-installed vitest@4.1.10 peer requirement. No breaking-change risk identified.
• Run full test suite after upgrade: The CI Tests job (npm run test) passed on the head commit, and the new Coverage job (npm run test:coverage) also passed. The full suite is green.

[itsmiso-ai]

Add Vitest code coverage support with @vitest/coverage-v8 dependency and coverage configuration in vitest.config.ts

Fixes#762

Opened by foreman on review GO (workload wl-misospace-dispatch-762).

Superseded by a newer automated review for this pull request.

[itsmiso-ai]

⚠️ This PR fix item has been marked as BLOCKED and needs human attention.

Reason: Failing check: npm audit (failure)

Latest note: foreman fix Workload prfix-misospace-dispatch-783 succeeded but PR is still not mergeable after 3/3 attempts

Posted automatically by Dispatch on 2026-08-18T02:15:06.995Z

Superseded by a newer automated review for this pull request.

[its-saffron]

AI Automated Review

Full PR review.

Analysis engine: dsv4f@https://litellm.jory.dev/v1 (openai) — primary route

Recommendation

Approve. This PR resolves issue PR 762 by adding the missing @vitest/coverage-v8 devDependency, wiring a coverage configuration with thresholds into vitest.config.ts, and adding a dedicated Coverage job to CI. All CI checks (including the new Coverage job) passed on the head commit, and the change is consistent with the repository's existing CI conventions.

Change-by-Change Findings

.github/workflows/ci.yaml

• Adds a coverage job that runs npm run test:coverage on ubuntu-latest, using the same pinned actions/checkout commit and the repository's shared ./.github/actions/setup-node action as the other jobs. This matches the existing CI structure and satisfies the issue's acceptance criterion that CI runs coverage on every push/PR.
• The job inherits the workflow-level permissions: contents: read and the DATABASE_URL env var, consistent with the test job.

package.json

• Adds @vitest/coverage-v8: ^4.1.8 to devDependencies. The installed lockfile version is 4.1.10, which exactly matches the vitest version already present (4.1.10), satisfying the package's peer dependency requirement (vitest: 4.1.10).
• The only other change is a cosmetic reflow of the overrides rationale comment (em-dash formatting); no override values changed.

package-lock.json

• Adds @vitest/coverage-v8@4.1.10 and its transitive dependencies (@bcoe/v8-coverage, ast-v8-to-istanbul, istanbul-lib-*, magicast, make-dir, supports-color, html-escaper, has-flag, std-env, js-tokens).
• The dev → devOptional flips on several @babel/* packages are a normal npm lockfile side effect of magicast (which is devOptional) depending on them; they do not change runtime behavior.
• No existing dependency versions were upgraded, so there is no breaking-change surface from this PR.

vitest.config.ts

• Adds a coverage block with provider: "v8", reporters text, html, json-summary, an include/exclude set scoped to src/**/*.{ts,tsx}, and thresholds (statements 75, branches 65, functions 70, lines 75).
• The thresholds are documented as being set below the measured baseline, which is a reasonable way to introduce a coverage gate without blocking on the current snapshot. The comment explicitly records the baseline numbers, which is good practice.
• The exclude list correctly omits test files, story files, __tests__ directories, and src/types/**.

Standards Compliance

The change follows the repository's AGENTS.md conventions:

• CI jobs use the shared ./.github/actions/setup-node action and pinned actions/checkout commit, consistent with the existing lint, typecheck, test, and build jobs.
• The new dependency is a devDependency only; no production dependencies or runtime behavior are affected.
• No secrets, environment files, or build output are committed.
• The test:coverage script already existed in package.json; this PR makes it functional rather than introducing a new script.

Linked Issue Fit

Issue PR 762 asked for:

1. npm run test:coverage completes and emits a coverage report — satisfied; the dependency is installed and the config is valid. The CI Coverage job passed, which exercises the script end-to-end.
2. @vitest/coverage-v8 listed in devDependencies — satisfied (^4.1.8 in package.json, 4.1.10 resolved in the lockfile).
3. CI runs coverage on every push/PR, or the script is removed — satisfied; a dedicated coverage job was added to .github/workflows/ci.yaml.

All acceptance criteria are met. The issue's expected files (package.json, vitest.config.ts, .github/workflows/ci.yaml) are exactly the files changed.

Tool Harness Findings

No tool harness findings were produced for this PR.

Unknowns or Needs Verification

• The coverage thresholds were set below the measured baseline, so the gate will not catch gradual coverage erosion until a metric drops below the threshold. This is a deliberate, documented tradeoff and not a blocker.
• The coverage CI job does not upload or publish the coverage report artifact; it only fails/succeeds on the threshold gate. If the team wants a browsable report, that would be a follow-up enhancement, not a requirement of the linked issue.

Must-Check Items

• Check for breaking API changes in updated dependencies: No existing dependency versions were upgraded in this PR. The only new dependency is @vitest/coverage-v8@4.1.10, which is a dev-only coverage provider that exactly matches the already-installed vitest@4.1.10 peer requirement. No breaking-change risk identified.
• Run full test suite after upgrade: The CI Tests job (npm run test) passed on the head commit, and the new Coverage job (npm run test:coverage) also passed. The full suite is green.

[itsmiso-ai]

Add Vitest code coverage support with @vitest/coverage-v8 dependency and coverage configuration in vitest.config.ts

Fixes#762

Opened by foreman on review GO (workload wl-misospace-dispatch-762).

Superseded by a newer automated review for this pull request.

[itsmiso-ai]

⚠️ This PR fix item has been marked as BLOCKED and needs human attention.

Reason: Failing check: npm audit (failure)

Latest note: foreman fix Workload prfix-misospace-dispatch-783 succeeded but PR is still not mergeable after 3/3 attempts

Posted automatically by Dispatch on 2026-08-18T02:15:06.995Z

Superseded by a newer automated review for this pull request.

[its-saffron]

AI Automated Review

Full PR review.

Analysis engine: dsv4f@https://litellm.jory.dev/v1 (openai) — primary route

Recommendation

Approve. This PR resolves issue PR 762 by adding the missing @vitest/coverage-v8 devDependency, wiring a coverage configuration with thresholds into vitest.config.ts, and adding a dedicated Coverage job to CI. All CI checks (including the new Coverage job) passed on the head commit, and the change is consistent with the repository's existing CI conventions.

Change-by-Change Findings

.github/workflows/ci.yaml

• Adds a coverage job that runs npm run test:coverage on ubuntu-latest, using the same pinned actions/checkout commit and the repository's shared ./.github/actions/setup-node action as the other jobs. This matches the existing CI structure and satisfies the issue's acceptance criterion that CI runs coverage on every push/PR.
• The job inherits the workflow-level permissions: contents: read and the DATABASE_URL env var, consistent with the test job.

package.json

• Adds @vitest/coverage-v8: ^4.1.8 to devDependencies. The installed lockfile version is 4.1.10, which exactly matches the vitest version already present (4.1.10), satisfying the package's peer dependency requirement (vitest: 4.1.10).
• The only other change is a cosmetic reflow of the overrides rationale comment (em-dash formatting); no override values changed.

package-lock.json

• Adds @vitest/coverage-v8@4.1.10 and its transitive dependencies (@bcoe/v8-coverage, ast-v8-to-istanbul, istanbul-lib-*, magicast, make-dir, supports-color, html-escaper, has-flag, std-env, js-tokens).
• The dev → devOptional flips on several @babel/* packages are a normal npm lockfile side effect of magicast (which is devOptional) depending on them; they do not change runtime behavior.
• No existing dependency versions were upgraded, so there is no breaking-change surface from this PR.

vitest.config.ts

• Adds a coverage block with provider: "v8", reporters text, html, json-summary, an include/exclude set scoped to src/**/*.{ts,tsx}, and thresholds (statements 75, branches 65, functions 70, lines 75).
• The thresholds are documented as being set below the measured baseline, which is a reasonable way to introduce a coverage gate without blocking on the current snapshot. The comment explicitly records the baseline numbers, which is good practice.
• The exclude list correctly omits test files, story files, __tests__ directories, and src/types/**.

Standards Compliance

The change follows the repository's AGENTS.md conventions:

• CI jobs use the shared ./.github/actions/setup-node action and pinned actions/checkout commit, consistent with the existing lint, typecheck, test, and build jobs.
• The new dependency is a devDependency only; no production dependencies or runtime behavior are affected.
• No secrets, environment files, or build output are committed.
• The test:coverage script already existed in package.json; this PR makes it functional rather than introducing a new script.

Linked Issue Fit

Issue PR 762 asked for:

1. npm run test:coverage completes and emits a coverage report — satisfied; the dependency is installed and the config is valid. The CI Coverage job passed, which exercises the script end-to-end.
2. @vitest/coverage-v8 listed in devDependencies — satisfied (^4.1.8 in package.json, 4.1.10 resolved in the lockfile).
3. CI runs coverage on every push/PR, or the script is removed — satisfied; a dedicated coverage job was added to .github/workflows/ci.yaml.

All acceptance criteria are met. The issue's expected files (package.json, vitest.config.ts, .github/workflows/ci.yaml) are exactly the files changed.

Tool Harness Findings

No tool harness findings were produced for this PR.

Unknowns or Needs Verification

• The coverage thresholds were set below the measured baseline, so the gate will not catch gradual coverage erosion until a metric drops below the threshold. This is a deliberate, documented tradeoff and not a blocker.
• The coverage CI job does not upload or publish the coverage report artifact; it only fails/succeeds on the threshold gate. If the team wants a browsable report, that would be a follow-up enhancement, not a requirement of the linked issue.

Must-Check Items

• Check for breaking API changes in updated dependencies: No existing dependency versions were upgraded in this PR. The only new dependency is @vitest/coverage-v8@4.1.10, which is a dev-only coverage provider that exactly matches the already-installed vitest@4.1.10 peer requirement. No breaking-change risk identified.
• Run full test suite after upgrade: The CI Tests job (npm run test) passed on the head commit, and the new Coverage job (npm run test:coverage) also passed. The full suite is green.