Fix Whitaker test-helper assertions

[leynos]

Pull Request

Summary

• Adds a shared ExpectValid assertion boundary for test-only helpers.
• Routes helper assertions through that boundary so Whitaker accepts intentional test failures.
• Upgrades the CI Whitaker installer to 0.2.7 for current suite behaviour.

Change Type

• CI/Infrastructure
• Refactor

Linked Issue

None; this is a targeted CI lint-regression repair.

Validation

• make all
• make typecheck
• make markdownlint
• make nixie
• git diff --check

Security Impact

None. This changes test assertion boundaries and CI lint tooling only.

Database Impact

None. No schema, migration, query, or data changes.

Blast Radius

Limited to test helpers compiled by the Whitaker CI lint job.

Rollback Plan

Revert the shared assertion boundary and installer update if they prove incompatible.

---

Review track: C (CI)

References

• Lody session

Summary by Sourcery

Make test-helper assertions compatible with current Whitaker linting while preserving their failure diagnostics.

Bug Fixes:

• Update Whitaker CI tooling to accept intentional assertion failures in test-only helpers.

Enhancements:

• Introduce a shared ExpectValid assertion boundary and apply it across test helpers and fixtures without changing test behavior.

CI:

• Upgrade the Whitaker installer used by the code-style workflow from 0.2.6 to 0.2.7.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates the Whitaker CI linter installer version to use the corrected test-context detection, ensuring test-only helpers are no longer linted as production code.

File-Level Changes

Change	Details	Files
Bump Whitaker installer version used in the code-style CI workflow to pick up corrected test-context handling.	Update WHITAKER_INSTALLER_VERSION from 0.2.6 to 0.2.7 in the code_style workflow job environment Ensure CI lint job runs against the new Whitaker release with fixed test-context classification	.github/workflows/code_style.yml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[coderabbitai]

Warning

Your free Security trial is over. An organization admin can activate billing to continue.

[coderabbitai]

Warning

Your free Security trial is over. An organization admin can activate billing to continue.

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 1d974411-0343-414f-a0f9-b7913afb3ed7

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

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