• (03bdc76) Draw a symmetric relation once, and refuse the mirror, and bump to 0.32.1

    Ghost released this 2026-08-25 10:41:49 +00:00 | 40 commits to master since this release

    relate refused a relation the ticket already held but never looked at what
    the target held, so both ends of a relates to could store a line. show then
    drew the same neighbour twice under the same label, since RelatesTo maps to
    itself in inverse_label: one row from the stored line and one derived from the
    far ticket's mirror of it, indistinguishable. Live on this board, where 8556048
    and 8c8a520 each stored the other.

    Both ends of the fix, because they do different jobs. relation_rows drops a
    derived row that reads exactly like a stored one, which repairs the boards that
    already hold both directions without an edit. cmd_relate refuses to store the
    mirror in the first place, reporting no change since the edge is already
    recorded at the far end, which stops it recurring. Neither alone closes it.

    The dedupe keys on the label and the target, not the kind and the target.
    Two tickets each blocking the other is two facts and the block has to say both,
    blocked by from this end and blocks from the other; keying on the kind would
    fold them into one row and lose half of what the ticket says. Only a symmetric
    kind can collide with its own stored line, and RelationKind::is_symmetric
    derives that from label() == inverse_label() rather than naming RelatesTo,
    so a kind added later answers by construction. The same gate is what keeps the
    refusal off a cycle: a target holding blocked by <this> is not a duplicate.

    The stored row is the survivor, not the derived one, because it is the line
    relate --clear can address. The consequence is worth knowing and is written
    down: with both ends holding a line, clearing one leaves the other's, which then
    draws as the derived row. Correct, since the far end still asserts the relation.

    4179958 decided that relates to is symmetric and "written once, not onto both
    files". Nothing enforced it until now.

    The board's own data is left alone. 8556048 and 8c8a520 still both store the
    line and the block now draws it once, which is what the criterion asked for.

    Co-Authored-By: Claude Opus 5 (1M context) noreply@anthropic.com

    Downloads