Work through TypeScript examples of real application boundaries: Enforce Hono JWT permissions after verification and before mutation; Persist a Hono notification record before post-response dispatch. Each recipe includes implementation code, integration prerequisites, failure-path tests to add, a Perch rule, and the captured broken/fixed source checks.
Download the Hono rule pack ZIP · Inspect the YAML rules
TypeScript
Verifying a token signature does not decide whether the principal may write orders. The application must check the required permission and then pass trusted identity scope to its data adapter. An authenticated read-only token is the important negative control.
Broken edit flagged · corrected edit passes
TypeScript
waitUntil extends execution after a response; it does not wait for an unrelated database transaction to commit. Persist order and outbox together, await the transaction, and only then schedule a delivery attempt. A durable worker must still discover undelivered rows if the request process dies.
Broken edit flagged · corrected edit passes
Choose the failure you need to prevent, add the scoped rule to your repository, and check both the broken and corrected implementation. Ask your agent to inspect the finding, repair the code and recheck the same rule. Keep framework tests beside the model check.
Perch keeps the requirement beside the code. Reuse the named check during the agent’s next edit and in CI, with cached answers free on unchanged requests.
Official Hono documentation · All language and framework recipes
