A child's proposal says what the child proved

When a child forge proposes a change to its parent, it also sends what its own check found on that commit (#13645). The parent shows this beside its own check. It never decides anything on it.

  1. On the child, land a change on main and press Propose. The proposal (src/actions/upstream.ts) sends attestation: { verdict, tree }. The verdict is the child's own check of the tip (green, red, pending or none) and the tree is the tip's tree id.
  2. On the parent, open the pull, on either tab. After proposed by child it reads proven on <child>: green at 1a2b3c4d. In the terminal, the pull screen's head line has the same line after proposed by child.
  3. If the pull's head tree is not the tree the child proved, the line ends · tree differs. That happens when someone pushed on top of the proposal or main was combined into it. In that case the child's verdict is about a different tree.

The boundary (src/http/api.ts, parseAttestation in src/core/attestation.ts) accepts only a verdict from that set and a 40- or 64-character lowercase hex tree id. Anything else is refused with 422 invalid_attestation. Only a proposal may carry one. The API's pull answer echoes it under proposal.attestation.

Every view reads it with pullProposalAt (src/core/proposal_token.ts): the page head (changeHead), the conflicts page and the terminal's local source. It reads the head's tree only when the child attested one. Nothing gates or ranks on the child's verdict. The parent's own check is still the one that lands a pull.

Test: test/attestation.test.ts (the verdict mapping and the line), test/proposal-token.test.ts (accepted, refused, shown on both tabs and in the terminal, tree differs) and test/upstream-forge.test.ts (the child sends none with no check, and green when its check of the tip passed).

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs