@joe-broadhead/messaging 0.7.0 → 0.7.1

package/CHANGELOG.md

@@ -6,6 +6,51 @@ Versions follow [Semantic Versioning](https://semver.org); see
 
 ## [Unreleased]
 
+## [0.7.1] - 2026-11-09
+
+**No store change.** A 0.7.0 home and a 0.7.0 relay database open unchanged, and a 0.7.0 messagingd or relay still
+opens what 0.7.1 writes. 0.7.0 was the last store reset: from 0.7.0 on, stores only grow (the owner's decision of
+8 November, when the first people other than the owner began to use Messaging).
+
+### Changed
+
+- **A refused store has a code and an exit status of its own** (spec §8.8). messagingd and messaging-relay exit
+  **78** (`EX_CONFIG`; `STORE_REFUSED_EXIT` in `@messaging/core`) for a store they do not read, instead of 1. messagingd
+  prints one line, `messagingd: store_refused: …`; the relay's event is still `relay.store_refused`. A new error code,
+  `store_refused`, is what `messaging daemon start` reports, with its own next step, and what agent clients
+  report (`TOOL_REMEDIES`). Clients match the status or the code, never the wording. The relay's systemd unit does
+  not restart on 78.
+- **A refusal says why** (spec §8.8): `pre-reset` (no store generation, or another: start over by moving the home
+  aside) or `newer` (a `min_reader` above the reader's schema: upgrade and keep the home). messagingd prints
+  `messagingd: store_refused: <reason>: …`; `StoreRefusedError.reason`, `reason` in `messaging --json` errors and in
+  agent tool errors carry it, each reason with its own next step. Moving the home aside is offered only for
+  `pre-reset`. The relay's event is `relay.store_refused {db, reason, message}`: **its `reason` field is now the
+  reason, and the text moved to `message`**.
+- **A home moved aside is named `<home>.pre-reset-<UTC timestamp>`** (spec §8.8), with no version in the name, and
+  messagingd's start-over text says so.
+
+### Fixed
+
+- **A roster sync that succeeds on retry clears the error it reported.** messagingd kept the old `relay.lastError`
+  after a later sync succeeded.
+- **The darwin executables are signed with a fixed 4 KiB page size,** so any Mac rebuilds a release byte for byte.
+  The default page size of `codesign` depends on the macOS version (docs/distribution.md).
+- **publish.yml stages `./<tarball>`.** npm read a bare `dir/name.tgz` as a GitHub shorthand, so 0.7.0's packages
+  were staged by hand; `npm run test:pack` now refuses a stage line without `./`.
+
+### Documentation
+
+- The relay's operator docs give its limits and flags as built: pre-auth limits 1024 and 128, `--max-connections`,
+  `--max-buffered-bytes`, `--preauth-*`, `--metrics` and `--sth-witness`. A test fails when they drift.
+- The README describes both identity modes: the Jelly directory and self-hosted roster teams.
+
+### Tests
+
+- The architecture tests enforce where SQLite, network listeners and raw sockets may be used, as AGENTS.md says.
+- A lying relay that withholds the roster entries a signed head commits to is caught (`heads.ts`).
+- The timing tests wait on events and bound cost in units measured on the same machine, not in wall-clock time, so
+  they pass on loaded and slow runners.
+
 ## [0.7.0] - 2026-11-08
 
 ### Store reset