# QQQ Tools development

Use Java 21 and `./mvnw verify` (`mvnw.cmd` on Windows). Keep the standard Qbit build parent, Checkstyle, and architecture guardrails enabled. Java follows the existing three-space Allman style.

Tools publishes read-only catalog metadata through the ordinary widget API. Never place credentials or pairing tokens in metadata or scripts. Client permissions and enrollment remain in their owning Qbits.

Run the sibling Next Tools and widget-dispatcher tests, build/typecheck, lint, and Tools browser tests when changing the catalog contract. Regenerate its checked-in fixture from `target/tools-catalog.json` after backend changes.

Release using docs/RELEASING.md and the shared QRun pipeline. Never mark a version published based only on a local build or tag.