5 Commits

Include renames

Author	SHA1	Message	Date
jochen	9c548753b8	go: say an Increment error other than a lost write may have spent its number, refuse null, and prove the writers collided ... The review of 2026-10-10: a timeout can come after the write landed, so a caller tolerates gaps; a null value is no counter; and a contention test where no write was lost would prove nothing.	2026-10-10 12:33:41 +02:00
jochen	c58ce2c7fe	go: a counter by compare-and-set, so a number is handed out once (hq research 042) ... The coming issues module hands out issue numbers from its own state; two instances must never hand out one number twice. Create and Update already write by compare-and-set (ADR 0259), so State(...).Increment reads, writes one more at the revision read, and on a lost write reads and tries again, bounded by the caller's attempts. A lost write past the bound is ErrChanged, any other refusal and a value that is no counter are returned at once: nothing is reported counted that was not written. Part of the issue tracker decision, hq research 042.	2026-10-10 12:31:05 +02:00
jochen	a75add0d59	Module state is hq ADR 0201 after all: the derived-value record moved to 0202 on hq main	2026-10-04 11:02:45 +02:00
jochen	d937c7bc2f	Module state is hq ADR 0202: 0201 landed first for a provider's derivations	2026-10-04 03:44:56 +02:00
jochen	096c5562a4	A module's state through the runtime, in TypeScript and Go (novox/hq ADR 0201) ... state(name) / stdio.State(name): get, put, delete, keys and watch over the runtime's mesh/state verbs. A watch's handler is registered under the id it is asked with, so its current values — which arrive before the watch is answered — and its changes reach it and no other watch.	2026-10-04 02:47:31 +02:00