CHAP 0.3.3: a patch test that tells true from 1

The protocol packages move together to 0.3.3. The Python coordinator now
tells a JSON boolean from a number when a patch tests a value, as the
TypeScript coordinator does, and the TypeScript coordinator reports one more
kind of failed write. chap-analytics 0.2.4, on its own track, tells a
boolean from a number when it rebuilds a corrected artefact.

npm install @brightbeamai/chap-coordinator@0.3.3
pip install "chap-coordinator==0.3.3"

Fixed

• A patch test that compares a boolean with a number, in Python. Python
  counts True as equal to 1, so a decide.override whose patch tested
  true against 1 completed in the Python coordinator and was refused with
  -32012 in TypeScript. Both now refuse it, and shared JSON Patch vectors
  hold them to the rule. (#187)
• A workspace that cannot be serialised, with a store that has only
  save. The TypeScript coordinator skipped that save without a word. It
  now reports it to onStoreError, or prints it to stderr, as it does any
  other failed write.

Changed

• The conformance Action runs on Node 24 by default. Its node-version
  input defaulted to 20, which reached its end of life in April 2026.

Documentation

• What a lapsed whisper shows. profiles/whisper.md section 4 says which
  entry records what, and that neither shows whether the people asked were
  notified. (#186)
• A review's deadline. profiles/review.md says it is recorded and has
  no effect in this version of the profile. -32013 stays reserved. (#184)

chap-analytics 0.2.4

• A patch test that compares a boolean with a number, when it rebuilds
  a corrected artefact, as in the coordinators.
• What a lapse rate says. The whispers chart and brief no longer read a
  high lapse rate as a reviewer away from the desk.

Thanks to @DevChiniwala for #187 and to @srikrishnavansi for #186 and #184.

The full entry is in the
changelog.