Testing and releases
Shipping should leave a trail.
Coodra changes should be testable, reviewable, and easy to connect back to the release that introduced them.
Checks before shipping
Check
Why it matters
Lint
Catches code-quality issues and unused implementation leftovers.
Type check
Catches route, prop, and data-shape issues before production.
Build
Confirms sitemap generation, bundling, and SSR output work together.
Browser smoke
Catches layout and routing issues the compiler cannot see.
Release trail
A release should be traceable back to the commit that changed behavior. If an error appears after deploy, the team should know which release introduced it, which route is affected, and whether rollback is available.
Docs upkeep
When product boundaries, routes, pricing, security posture, or connector status change, the knowledge base and public docs should change with them. Stale docs are how future agents make confident mistakes.