qrlib

Use when the task involves modifying files in this repository and preparing the work as a GitHub Flow change. The change should follow qrlib's spec-driven workflow: decide a change slug, sync local main with origin/main, recommend a branch name, plan commit boundaries, and prepare a PR-ready summary that references spec/design docs. Do not use for read-only explanation tasks.

Use when adding or modifying Python library code under src/qrlib. Start from an existing or new developer spec/design, keep public API boundaries explicit, separate internal modules from stable exports, and update tests plus public docs together. Do not use for pure Git workflow tasks or read-only explanation tasks.

Use when planning or executing any non-trivial change in qrlib. Decide whether the change needs a full spec/design, create or update docs/developer/specs and docs/developer/design first, then map the change to implementation, tests, public docs, and verification. Do not use for typo-only or read-only tasks.