Skip to main content

​
Repo Fit

This monorepo is larger than gb-travio-webhooks, but it should keep the same operational posture.

​
Carry-over rules

  • write direct READMEs
  • keep runtime status and replay surfaces explicit
  • prefer typed config over implicit environment behavior
  • treat auditability and rejected deliveries as product requirements
  • keep CI legible enough to audit quickly
  • release through GitHub, not from a laptop

​
PR standard

Every feature PR should include:
  • typed code
  • tests for the primary path and at least one failure path
  • docs for new or changed runtime surfaces
  • explicit notes where mock behavior still stands in for durable persistence

​
Runtime standard

Every operational surface should document:
  • endpoint path
  • auth model
  • request and response shape
  • failure modes
  • retry or replay posture