Development record

Building an issue the person has just filed takes a pull request round trip first, with nothing in the capture or build output saying so up front. On 2026-10-24 a person asked a session to capture an issue and then build it. abcd build refused three times in a row, each on a different ground found only by running it. First, the default category the capture gave the issue (observation) is outside the drain rule's fixable set. Second, the issue lane fetches origin's default branch, so a record that exists only in the working tree cannot be built at all, and the record had to go through its own branch, preflight, pull request and merge queue (a queue run that failed once on an unrelated flaky test), about three hours. Third, once it landed, the severity the capture gave it (major) is above the drain's nitpick and minor, so the issue was a person's all along. None of the three was visible when the issue was filed, and the person's intent, to file and then build, needed four round trips to learn that it could not be built.