Persist a Hono notification record before post-response dispatch: Perch rule pack
1 saved requirement for Hono. Inspect the selectors and adapt the example paths to your repository.
- name: persist-notification-before-dispatch
where: "confirm.ts"
ensure: >-
The confirm function persists a durable notification record by calling tx.insertOutbox inside the same db.transaction callback as tx.confirmOrder, before scheduling dispatchCommittedOutbox with waitUntil. Confirming the order and scheduling dispatch without inserting an outbox record violates this requirement.
Download the rule pack ZIP · Download YAML · Agent repair task · Implementation, integration requirements and captured checks
Install the rule without replacing your configuration
npm install -g @lakeday/perch
perch login
curl -fL 'https://reporules.fyi/hono/waituntil-after-persistence/rule-pack.zip' -o 'perch-guide-hono-waituntil-after-persistence.zip'
unzip -n 'perch-guide-hono-waituntil-after-persistence.zip'Keep your existing perch.yaml. Extraction preserves existing files and adds .perch/rules/perch-guide-hono-waituntil-after-persistence.yaml. Review each where selector before running a check on your application.
Configure your coding agent
perch setup claude-code
perch setup codex
perch setup cursor
perch setup piChoose the setup command for the agent you use.
Check the edit, fix the finding, check again
perch check confirm.ts --rules persist-notification-before-dispatch --jsonRun the check after an agent edit. Read the finding and affected code, repair the implementation, and repeat the identical command. Keep the application regression tests as separate gates.
Exit 3 means a finding. Exit 1 or 2 means the check did not complete. A pass does not prove application correctness. Fresh judgments can vary; unchanged requests reuse cached answers. Relevant source is sent to the configured model service.