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

Two agents could start on one issue without seeing each other, and an issue
could be resolved without anyone having said they started its fix. A move to
diagnosing or fixing now names by, the worker as who@node; get and list show
the worker with since and stale; another worker is refused while it is
current unless take-over says why (noted); a worker untouched for
worker-stale-after (24h) may be taken over from without a reason. Resolved is
reached only from fixing. The moved event carries by, since and caller.
Fixing counts as not closed for the triage and the duplicate check.
hq ADR 0283.

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

..

testdata/hq/04-ISSUES

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

bus_test.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

check.go

mesh-issues: triage every new issue — severity, needs, suggested owner, dependencies — and say an issue ready when what it depends on is delivered (hq ADR 0279)

2026-10-10 17:56:08 +02:00

delivery_test.go

mesh-issues: an issue knows whether its fix is delivered, says it ready to verify, and a fix stuck after its merge is said (hq ADR 0281)

2026-10-10 18:12:52 +02:00

delivery.go

mesh-issues: an issue knows whether its fix is delivered, says it ready to verify, and a fix stuck after its merge is said (hq ADR 0281)

2026-10-10 18:12:52 +02:00

groom.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

import_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

import.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

issue.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

main.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

manifest_test.go

mesh-issues: an issue knows whether its fix is delivered, says it ready to verify, and a fix stuck after its merge is said (hq ADR 0281)

2026-10-10 18:12:52 +02:00

memory_test.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

ready.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

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

tracker_test.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

tracker.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

triage_test.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

worker_test.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

worker.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