7 Commits

Include renames

Author	SHA1	Message	Date
jochen	d413da203c	mesh-issues: resume an interrupted carry by revision and fault one issue instead of the whole start, so no kept value is lost and the tracker always starts (review of PR 228) ... An open's lost answer is judged by the issue's first entry; an entry that does not fold faults its issue on start; a value written beside the log is never folded over; one issue is kept in at most 252 KiB so its whole operation fits a log entry.	2026-10-12 10:35:57 +02:00
jochen	d33f3e3f71	mesh-issues: pin mesh-sdk at main 9747f3e, where the log and the history are both merged	2026-10-12 10:22:19 +02:00
jochen	dcc7510cd8	mesh-issues: carry each value the issues bucket kept, read through the runtime's history, so the log begins with all the bucket still knew (hq ADR 0300 §6, ADR 0307)	2026-10-12 10:20:51 +02:00
jochen	983d434623	mesh-issues: keep every issue in the log changes and the bucket as its fold, so the record outlives the bucket's cap and a week of events (hq ADR 0300, issues 501, 502) ... Every write appends one operation at the issue's last sequence before the bucket is written; a refused append writes nothing. The start carries what the bucket holds, refolds what is behind and indexes every issue in memory, so list answers from memory with a ranked search and a before cursor.	2026-10-12 02:41:54 +02:00
jschoubben	f134ed5910	mesh-issues and mesh-knowledge: pin mesh-sdk at its merge of CallerOf; mesh-knowledge reads the caller from the runtime (hq issue 365) ... Both pin mesh-sdk/go at 4cf45b5 (mesh-sdk#20 merged). mesh-knowledge's one reading of the caller, callerOf, now answers stdio.CallerOf, so a call on the caller-named subject is recorded as its caller's bus user and any other as unproven, never from the arguments.	2026-10-11 11:26:45 +02:00
jschoubben	66068febb0	mesh-issues: record who acted as the caller the runtime proves (hq issue 365) ... The tool runner now takes a call's caller from the subject it arrived on and hands it to the module through the SDK (stdio.CallerOf); the tracker records that bus user on what each verb writes instead of unproven. Never from the arguments, which still refuse any caller, and unproven where the runtime proves none. Needs mesh-sdk's go/caller.go (pinned at its branch head until merged).	2026-10-11 11:22:41 +02:00
jochen	2493e3e048	Add mesh-issues, the issue tracker, so an issue's number comes from one counter no two openers share (hq ADR 0275, to-be 53 slice 1) ... The seat issue-tracker, held once for the mesh: open, get, list, move, note and link. The counter is advanced by the SDK's compare-and-set Increment (go/v0.1.12) and started once at the setting first-number (365, after hq's highest), never below an issue kept. The cycle's issue rules are refused at the write; every change is an event. The runtime does not yet say who called, so every change is recorded as by "unproven" and no argument can name a caller.	2026-10-10 12:51:15 +02:00