What a real AI-assisted PR looks like

Ahnii! A lot of AI coding content ends too early. The model writes a patch. The patch looks plausible. A few tests pass. Someone posts a screenshot and calls it proof. That is not the part I care about. What I want to know is whether an AI-assisted change can survive the whole engineering process: audit, review, CI, static analysis, contract repair, docs drift, and merge. PR #1022 was the first pull request in Waaseyaa where that full chain played out end to end. The Invariant The bug looked small: pipeline navigation in the admin SPA was non-deterministic. Whether the pipeline link showed up depended on whether a mount-time request happened to succeed. If a board-config request failed for incidental reasons, the UI could act like the entity type had no pipeline at all. That is not just a UI bug. That is a contract problem. The invariant was simple: Pipeline navigation visibility must be a pure function of runtime.catalog actions. If the catalog entry declares board-config, show pipeli