Agent Task Brief

Use this prompt for one bounded coding task. Fill in the acceptance checks before handing off the work; include repository instructions and sanitized fixtures. This structure follows the guidance to give coding agents clear scope, context, and verification criteria in Codex best practices.

## Goal
[Describe the observable behavior to add or fix and why it matters.]

## Repository context and scope
- Read and follow the applicable AGENTS.md and repository conventions.
- Relevant files: [paths to implementation, documentation, and existing tests]
- Files you may change: [bounded paths or modules]
- Out of scope: [unrelated behavior, dependencies, or architectural changes]
- Preserve other contributors' changes and the existing public interface unless
  the goal explicitly changes it.

## Inputs and method
- Input/output contract: [schema, units, formats, and expected behavior]
- Scientific or business rules: [definitions, thresholds, reference/version]
- Missing values and boundary cases: [explicit policy]
- Fixture: [repository path to synthetic or public example data]
- Do not invent a scientific method or resolve a material ambiguity silently.
- Use existing manifests and lockfiles; do not guess package versions.

## Execution
1. Inspect the relevant code and describe the smallest useful change.
2. Ask only about unresolved choices that affect correctness, scope, or access.
   Record reasonable implementation assumptions and continue within scope.
3. Implement the change and update directly affected documentation.
4. Run the checks below and inspect the diff for unintended changes.

## Acceptance checks
- Command: [exact command from the repository root]
- Expected result: [exit status, output schema, or observable behavior]
- Boundary fixture and expected result: [case that could reveal a wrong method]
- Regression check: [existing behavior that must remain valid]

## Stop conditions
- Pause the affected work if the method or expected result is contradictory,
  required access is unavailable, or a necessary action exceeds authorization.
- Never request protected records, credentials, or private storage paths.
  Work with the supplied schema and sanitized fixtures.
- Do not publish, deploy, or change external services unless authorized.

## Completion report
Report changed files, behavior implemented, checks actually run and their
results, remaining limitations, and any unresolved decisions. Distinguish
verified results from suggested follow-up commands.