jschoubben e009088150 Point messenger, mesh-watcher, restic and mesh-issues away from the controller ...

The controller is not placed (ADR 0590): messenger no longer treats it as
a condition owner or a walk's subject, mesh-watcher reads only where the bus
runs, restic tells the operator to compose the machine or set config through
the seats that do it now, and mesh-issues' examples name a placed repository.
mesh-issues keeps mesh-controller among its owners: issues located there,
issue 1126 among them, and route-proxy until it moves, still name it
(issue 1126 B11).

Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL

2026-11-02 12:29:56 +01:00

..

testdata

mesh-issues and mesh-knowledge: milestones are records of the issue tracker, and progress reads them (ADR 0493 §1 to §4, issue 1781)

2026-10-26 18:42:51 +01:00

brief_test.go

Let issue-tracker.get answer briefly, with only its last note (issue 1071)

2026-10-17 22:45:42 +02:00

bus_test.go

Keep two values of each issue in the tracker's bucket, since the log holds them all (issue 1221)

2026-10-19 12:38:55 +02:00

caller_test.go

Make tests that wait for concurrent work wait on the event or a condition with a long deadline (issue 1814)

2026-11-01 17:24:19 +01:00

changes.go

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)

2026-10-12 10:35:57 +02:00

check.go

Point messenger, mesh-watcher, restic and mesh-issues away from the controller

2026-11-02 12:29:56 +01:00

claims_test.go

The tracker derives a fix's delivered from the delivery view's event, not the gate's gone states (issue 1946)

2026-10-24 16:50:50 +02:00

claims.go

mesh-issues: a learned merge is kept as of now, closed untimed issues get no fix time, the forge read is declared, the sweep rotates its asks (issue 1950)

2026-10-27 01:30:37 +01:00

conditionkey_test.go

mesh-issues: take a delivery's id as mesh-delivery forms it, owner/repo@commit (hq issue 475)

2026-10-11 19:24:23 +02:00

core_test.go

Make the build modules and the delivery parts core issue owners and drop build-agent (issue 1041, E3)

2026-10-23 15:12:21 +02:00

delivered_test.go

Cover a merged fix from the delivery view's reached head in the sweep, not only from its once-said event, so a fix named after the saying is delivered (issue 1950)

2026-10-27 21:17:53 +01:00

delivery_test.go

The tracker derives a fix's delivered from the delivery view's event, not the gate's gone states (issue 1946)

2026-10-24 16:50:50 +02:00

delivery.go

Cover a merged fix from the delivery view's reached head in the sweep, not only from its once-said event, so a fix named after the saying is delivered (issue 1950)

2026-10-27 21:17:53 +01:00

fixtime_test.go

The tracker derives a fix's delivered from the delivery view's event, not the gate's gone states (issue 1946)

2026-10-24 16:50:50 +02:00

fixtime.go

mesh-issues: a learned merge is kept as of now, closed untimed issues get no fix time, the forge read is declared, the sweep rotates its asks (issue 1950)

2026-10-27 01:30:37 +01:00

groom.go

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)

2026-10-12 02:41:54 +02:00

import_test.go

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)

2026-10-12 02:41:54 +02:00

import.go

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)

2026-10-12 02:41:54 +02:00

issue.go

Measure each fix from the move to fixing to delivered, and say one over its budget (issue 403)

2026-10-12 15:50:12 +02:00

learn_test.go

mesh-issues: a learned merge is kept as of now, closed untimed issues get no fix time, the forge read is declared, the sweep rotates its asks (issue 1950)

2026-10-27 01:30:37 +01:00

learn.go

Cover a merged fix from the delivery view's reached head in the sweep, not only from its once-said event, so a fix named after the saying is delivered (issue 1950)

2026-10-27 21:17:53 +01:00

list_numbers_review1_test.go

Review round 1: list numbers combines search and before as AND, its limit defaults to the count asked and said names a cut; README names brief, numbers and worker (issues 1070, 1071)

2026-10-17 23:07:29 +02:00

list_numbers_worker_test.go

Let issue-tracker.list take numbers and worker (issue 1070)

2026-10-17 22:50:09 +02:00

list_progress_test.go

mesh-issues: a milestone or commit link moves no issue and keeps no worker current (issue 1781)

2026-10-26 19:12:12 +01:00

log_test.go

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)

2026-10-12 10:35:57 +02:00

main.go

Point messenger, mesh-watcher, restic and mesh-issues away from the controller

2026-11-02 12:29:56 +01:00

manifest_test.go

mesh-issues: a learned merge is kept as of now, closed untimed issues get no fix time, the forge read is declared, the sweep rotates its asks (issue 1950)

2026-10-27 01:30:37 +01:00

memory_test.go

mesh-issues and mesh-knowledge: milestones are records of the issue tracker, and progress reads them (ADR 0493 §1 to §4, issue 1781)

2026-10-26 18:42:51 +01:00

milestone_bus_test.go

issue-tracker.changes reads each issue's moves over a window from the tracker's own log, so progress since says from what each issue moved, not only where it is

2026-10-28 12:33:01 +01:00

milestone_test.go

mesh-issues and mesh-knowledge: milestones are records of the issue tracker, and progress reads them (ADR 0493 §1 to §4, issue 1781)

2026-10-26 18:42:51 +01:00

milestone.go

mesh-issues and mesh-knowledge: milestones are records of the issue tracker, and progress reads them (ADR 0493 §1 to §4, issue 1781)

2026-10-26 18:42:51 +01:00

milestoneimport.go

mesh-issues and mesh-knowledge: milestones are records of the issue tracker, and progress reads them (ADR 0493 §1 to §4, issue 1781)

2026-10-26 18:42:51 +01:00

moves_test.go

issue-tracker.changes reads each issue's moves over a window from the tracker's own log, so progress since says from what each issue moved, not only where it is

2026-10-28 12:33:01 +01:00

moves.go

issue-tracker.changes reads each issue's moves over a window from the tracker's own log, so progress since says from what each issue moved, not only where it is

2026-10-28 12:33:01 +01:00

reads-outside

mesh-build-go: a reads-outside marker lists what its tests read, so its package is kept until one of those files changes (issue 1936)

2026-10-26 22:02:58 +01:00

ready.go

Let issue-tracker.get answer briefly, with only its last note (issue 1071)

2026-10-17 22:45:42 +02:00

report_test.go

mesh-issues: import hq's issue folders at their own numbers, and an issue with a folder is whole in the tracker (hq ADR 0275, to-be 53 slice 3)

2026-10-10 16:00:19 +02:00

report.go

mesh-issues: an issue says who works on it, and resolves only from fixing (hq issue 399)

2026-10-10 21:04:32 +02:00

reserve_test.go

mesh-issues: a counter not started never starts without the knowledge base's answer, floor or no floor (review of #214)

2026-10-11 12:44:45 +02:00

reserve.go

mesh-issues: a counter not started never starts without the knowledge base's answer, floor or no floor (review of #214)

2026-10-11 12:44:45 +02:00

templates_test.go

Feature 57 (config and provisioning): release the catalogue, the reviewed release branch merged with main, on top of main

2026-10-16 09:42:45 +00:00

tracker_test.go

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)

2026-10-12 10:35:57 +02:00

tracker.go

Retire the spelling catalogue: the words check lists it and skips module paths in imports

2026-10-28 12:17:21 +01:00

tracking_test.go

Check that tracking says no event and writes nothing, as ADR 0285 states

2026-10-10 21:51:30 +02:00

tracking.go

mesh-issues: read merged from the pull request, not the state, so a closed one is withdrawn (hq issue 483)

2026-10-11 12:24:45 +02:00

triage_test.go

The tracker derives a fix's delivered from the delivery view's event, not the gate's gone states (issue 1946)

2026-10-24 16:50:50 +02:00

view.go

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)

2026-10-12 10:35:57 +02:00

worker_test.go

mesh-issues: read merged from the pull request, not the state, so a closed one is withdrawn (hq issue 483)

2026-10-11 12:24:45 +02:00

worker.go

Let issue-tracker.list take numbers and worker (issue 1070)

2026-10-17 22:50:09 +02:00