All issues

The shipped example renumbers published `pcs/priority` when a circuit is inserted mid-list, and has never exercised the shed path

#58

· dcj opened

on Aug 27, 2026

Prose left stale by the 0.7.0 locked-relay change

#56

· dcj opened

on Aug 25, 2026

`relay-behavior` now has two behaviours, not three: a locked-open circuit cannot be modelled

#55

· dcj opened

on Aug 25, 2026

`RelayResolver.register(always_on=)` changed meaning in 0.7.0 without a rename, and `relay_locked` is not importable

#54

· dcj opened

on Aug 25, 2026

`_settable_for` derives the locked bit from unvalidated metadata, so a mistyped `relay-behavior` silently locks the circuit

#53

· dcj opened

on Aug 25, 2026

`default-priority` accepts three REST-generation values that can only be published as `UNKNOWN`, and that silently never shed

#51

· cayossarian opened

on Aug 25, 2026

`asserted-islanding-state` accepts and republishes writes the spec says to ignore, removing the consumer's only rejection signal

#31

· cayossarian opened

on Aug 12, 2026

Circuit `placement` models a sub-enclosure as this enclosure's own circuits, and the `connection` properties the spec designates for it cannot be populated

#30

· cayossarian opened

on Aug 9, 2026