Contributing

Contributing and requesting support

Find an issue or PR, choose the correct repository owner and provide a reproducible, sanitized example. Include current source/deployed image/schema version and whether the behavior was actually observed on a live environment. Proposals must not be described as deployed features.

A useful PR includes its ADR/contract change, migration compatibility, tests for wrong-user access, RLS and idempotency, worker retry/cancellation tests, explicit approval boundaries and documentation. Security vulnerabilities need private reporting. Do not add a new harness abstraction solely to rename existing frameworks.

Read Developer guide, release runbook and wiki editorial/publishing policy.