chore(repo): fix all oxlint errors and warnings

[zrosenbauer]

Summary

• Resolve all 55 warnings and 1 error reported by oxlint
• Replace toBe(true/false) with toBeTruthy()/toBeFalsy() across test files
• Use object/array destructuring instead of direct member access
• Rename describe titles that collide with imported function names
• Capitalize continuation comments to satisfy capitalized-comments rule
• Replace ternary with ts-pattern match in config middleware (the 1 error)
• Name anonymous async generator in log test

Test plan

• pnpm check passes (typecheck + lint + format)
• pnpm test passes (all 17 tasks successful)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
oss-kidd	Ignored	Preview	Apr 8, 2026 8:06pm

[changeset-bot]

🦋 Changeset detected

Latest commit: 6aae715

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 0 packages

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 2635c5f2-50fc-4e5a-b556-8a5cd436a480

📥 Commits

Reviewing files that changed from the base of the PR and between ece55ac and 6aae715.

📒 Files selected for processing (2)

• packages/core/src/context/resolve-defaults.test.ts
• packages/core/src/stories/check.test.ts

---

📝 Walkthrough

Walkthrough

This PR updates test assertions across multiple packages to use truthiness matchers (toBeTruthy(), toBeFalsy()) instead of strict boolean equality comparisons, changes several test describe blocks to reference imported functions directly instead of string labels, applies minor destructuring refactors to test snapshot access, and adjusts comment capitalization and wording in source files and configuration.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Possibly related PRs

• fix(cli): bundle @kidd-cli/* deps so published CLI is self-contained #150: Modifies the same packages/cli/tsdown.config.ts file's deps.alwaysBundle configuration that this PR's comment update references.
• chore(deps): upgrade all packages to latest versions #140: Disables the prefer-strict-boolean-matchers Vitest linting rule, which directly relates to the matcher migration changes across test files in this PR.
• test(repo): improve test coverage from 77% to 93% #142: Adds/expands test modules in the same files that this PR updates with matcher and describe-label changes.

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 75.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	Title accurately summarizes the main objective: fixing linting errors and warnings reported by oxlint.
Description check	✅ Passed	Description is directly related to the changeset, providing specific detail about the linting fixes, test assertion updates, and refactoring applied.

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

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/fix-lint-warnings

---

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

[codspeed-hq]

Merging this PR will not alter performance

✅ 2 untouched benchmarks
⏩ 2 skipped benchmarks¹

---

_{Comparing chore/fix-lint-warnings (6aae715) with main (f050fd1)}

Footnotes

1. 2 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩