pair-change

Read ~/.agents/sdlc/MAIN.md and PAIRING.md, then the project profile and
applicable standards. The operator's bounded objective and explicit iteration
instructions are the working specification. A question remains a question.

For code or script changes, reuse the applicable work item or create its skeleton
before coding. Append authorized requirements and decisions as the session
progresses. Documentation-only changes do not require a ticket.

Iterate implementation with the operator. Use automated TDD wherever justified,
and record each explicit visual, ergonomic, editorial, or operational validation
without replacing it with artificial automation. Audit each coherent code
increment promptly through the combined implementation gate, not each keystroke.
When the outcome stabilizes, consolidate spec.org, validation.org, and
affected documentation, then run the retrospective definition review.

Follow ~/.agents/sdlc/AUDITS.md for the Workflow: paired audit-context marker,
separate retained gate sessions, and remediation limits. Refer proposed behaviour
or design changes to the operator for normal delivery; do not redesign during
wrap-up. Ask the operator to confirm the recorded user tests and close the work.