Development record
intent.SetPromotedFrom returns a populated Intent beside a non-nil ErrBackEdgeTaken, deliberately and documented, and the promote route depends on that value to report the kept back-edge, but the primitive's own test discards the return, so the stated contract is asserted only indirectly through the capture result's BackEdgeKept field. The fidelity verdict for itd-2609020625400169 records this as its one missing item; a primitive-level assertion closes it.
issueresolvedminoriss-2609021815563506
intent.SetPromotedFrom returns a populated Intent beside a non-nil ErrBackEdgeTaken, deliberately and documented, and the promote route depends on that value to report the kept back-edge, but the primitive's own test discards the return, so the stated contract is asserted only indirectly through the capture result's BackEdgeKept field. The fidelity verdict for itd-2609020625400169 records this as its one missing item; a primitive-level assertion closes it.
Grounds
- pursued: we expect primitive-level assertions on AddRelatedIssue's return to catch a regression the promote route's BackEdgeKept would otherwise hide; it is shown wrong if a mutation returning a populated intent beside an error, or an empty list on the no-op, passes the intent tests
Frontmatter
| id | iss-2609021815563506 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | minor |
.abcd/work/issues/resolved/iss-2609021815563506-intent-setpromotedfrom-returns-a.md
open on GitHub ↗ · commit history ↗
mentions1
- itd-2609020625400169An intent that a reading occasioned says so in its origin, with the run and the item that occasioned it