mesh-catalog

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

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: take a delivery's id as mesh-delivery forms it, owner/repo@commit (hq issue 475)

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

claims_test.go

mesh-issues: call an issue its worker left abandoned, not a stale claim (hq ADR 0294)

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

delivery_test.go

mesh-issues: end a fix-stuck warning when its issue is resolved, and never say a closed issue's fix stuck (issue 547)

2026-10-12 13:31:51 +02:00

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

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

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

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

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

manifest_test.go

Feature 57 (config and provisioning): modules declare config and provisions, their files rendered from templates; synced with main (issues of feature 57, 874)

2026-10-16 07:37:43 +00:00

memory_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

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

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): modules declare config and provisions, their files rendered from templates; synced with main (issues of feature 57, 874)

2026-10-16 07:37:43 +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

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

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

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

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

mesh-issues: call an issue its worker left abandoned, not a stale claim (hq ADR 0294)

2026-10-11 12:26:57 +02:00