3 Commits

Include renames

Author	SHA1	Message	Date
Bendik Aagaard LynghaugandClaude Opus 5	214d4eb85c	Sessions outlive the deploy that interrupted them ... A MemoryStore meant every restart signed out every desk on the site being deployed. Bearable while a desk is three people, and not the kind of thing that gets better on its own. They live in NATS KV now: the JetStream already under the events, the projections, the content reload and the access questions. No new service, no new store, and the same bucket a second instance of a site would read if there ever is one. `create` draws a fresh id rather than writing over a session already at that key, the bucket's `max_age` collects what nobody comes back for, and a record's own expiry is what answers a load, whatever the bucket still holds. Proved the only way it can be: a store opened twice against one JetStream, which is what two runs of the binary are. Also fixed, while there: the integration test asserted a record's projected state was one that `aggregates::transition` never writes - it appends events, the desk handler updates the projection - so it failed whenever it was actually run. It now asserts what it says it does, that a mailed reply leaves the state alone. test.yml has been red since 0.3.47 while publish.yml stayed green, which is how v0.4.0 went out over it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-09-28 16:38:05 +02:00
Bendik Aagaard LynghaugandClaude Opus 5	26c1762dfa	A reply to a case mail becomes a note on its record ... Whatever reads the mailbox publishes on portal.mail.received; portal appends the note after checking the record exists in a bucket this site has and the sender is the address the record itself holds. A note never moves a case: a mailbox is the one door anyone may knock on, so it cannot drive a state machine even if someone forges their way past the checks. The desks show the conversation beside the case. Tested: the address parser, every refusal (a stranger, no address to compare, an empty reply, the same reply twice, an unknown contract), and the whole path through a real JetStream - the note lands, the state does not move, and no event is written. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-09-24 21:26:57 +02:00
Bendik Aagaard LynghaugandClaude Fable 5.1	e06346e43a	tests/jetstream.rs: the store, event log and projection against a real JetStream ... Until now nothing outside a live site exercised the NATS side: the aggregate engine was tested by in-memory replay only. This test submits an answer, moves it from a desk through the engine, checks that an undeclared move and an unknown record are refused, and reads the record back from its own event log. It runs when PORTAL_TEST_NATS_URL is set; CI starts a throwaway nats:2.14.6-alpine with JetStream for it and tears it down. Without the variable the test passes as skipped, so `cargo test` stays green offline. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01L4jrCgLiKKHAEFuZUJjckH	2026-09-22 16:51:15 +02:00