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

The seed linked 188 issues at once and every one read as moved at the seed's minute, hiding when each
really moved; on a worked issue the link also counted as its worker's activity. These links only place
an issue, so last-moved and the worker's activity leave them out.

2026-10-26 19:12:12 +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

mesh-issues: record who acted as the caller the runtime proves (hq issue 365)

2026-10-11 11:22:41 +02: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

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

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

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

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

Match a fix to a delivered revision by what the gate says of its merge; keep #474's source catch-up at start (issues 1946, 1726)

2026-10-24 18:13:40 +02: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

Match a fix to a delivered revision by what the gate says of its merge; keep #474's source catch-up at start (issues 1946, 1726)

2026-10-24 18:13:40 +02: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

Read the mesh's comment verdicts as approvals, and warn on no fix timed from the log (issue 403, review 69)

2026-10-12 16:16:04 +02: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

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

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

manifest_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

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

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_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

reads-outside

Mark the packages whose tests read files outside their directory, found by the review (issue 1935)

2026-10-24 04:38:49 +02: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

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

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