You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Schema repinned to schema-dist v0.33.0-dist.56 (from dist.55; same canonical 00.33.00, no schema file moved). The one serial settles five readings of profiles/spine.md that the first reader found ambiguous, and the fixture grows to 40 cases.
SpineRead.dropped entries are {"key", "value"} dicts (were "<key>: <JSON>" strings), the value exactly as the element held it, a copy. The page now compares dropped as JSON values, never as text, because Python and JavaScript write JSON differently. A caller that read the strings changes; a SpineRead that dropped something is no longer hashable.
A non-string x_spine_truth or x_spine_probe is named in dropped (it was left out silently). The order is the page's: address, truth, access, status, layer, audience, depends_on, probe, verified.
Already so in 0.44.0, and now on the page: probe verbs are syntax (case-sensitive, single spaces), verified.at must be a real calendar day, and an empty depends_on is stated.
Tests: the fixture is compared as canonical JSON, because Python's == holds True == 1; a dropped boolean stays a boolean; the page's key order; the probe form's syntax. Two mutants watched failing (a boolean written as 1, a non-string probe not named).