# Repository instructions for the example

This is a synthetic JavaScript ticket filter, not a customer repository.

- `priority` is an integer from 0 to 3, or `undefined` for no filter. Input parsing and validation are outside this function.
- Reproduce the reported bug with a regression test before changing the implementation.
- Keep the fix local to `selectTickets`. Do not add dependencies or change its public signature.
- Preserve the input array, ticket objects and the existing order.
- Run `node --test workflow.test.mjs`. Include the command and its actual result in the review notes.
- Stop if requirements are unclear. Passing tests support the specified cases; they do not establish production readiness.
- A human reviews the diff and decides whether to merge. The agent must not merge or deploy.

Suggested agent task:

> Filtering with priority 0 returns tickets of every priority. Read the repository instructions. Add a regression test that reproduces this behavior, explain the cause, and draft the smallest correction. Run the tests and present the diff and remaining assumptions for human review.