Catalog versions: each module's version floor from its Go tags and its package holders, per module, as a kept call (A-490c..A-490i, §412) #260

Merged
mesh-tools merged 4 commits from fix/catalog-versions-first-fill into main 2026-11-19 21:40:13 +00:00
Member

Design 47 G §412 and lead answers A-490c..A-490i (hq G-22-lead-answers-2.md); ADR 0668 §3; ADR 0437 §8 kept (no timer). Live 2026-11-19: mesh-catalog.versions answered [] for every module the builder held nothing of (the forge-tag floor of §412 was never built; the fill closed itself), so the builder reserved mesh-sdk 0.1.0 while the forge holds go/v0.1.16 and the npm holder 0.1.18. Now: for every module with no version, at start and every revision, the floor is the highest of its Go tags (prefix = package dir + /v) and each package holder's versions; each read a kept call per module; call-unanswered after five minutes, cleared on every exit; a floor entry is replaced by the release heard at its version. Quick vs thorough: thorough, every module, not the sdk alone. Whole-indexer integration test added (13 of 50).

Manifest validator: three new invokes (seat:git.tags, seat:go-package-registry.versions, seat:npm-package-registry.versions); not run against the live seat list; a local judge.Manifest re-run gave 0 problems for trunk and head; all three verbs exist live.

Reviewed-by: mesh-code-reviewer@shanks at b413949ea8 (three rounds)

https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy

Design 47 G §412 and lead answers A-490c..A-490i (hq G-22-lead-answers-2.md); ADR 0668 §3; ADR 0437 §8 kept (no timer). Live 2026-11-19: mesh-catalog.versions answered [] for every module the builder held nothing of (the forge-tag floor of §412 was never built; the fill closed itself), so the builder reserved mesh-sdk 0.1.0 while the forge holds go/v0.1.16 and the npm holder 0.1.18. Now: for every module with no version, at start and every revision, the floor is the highest of its Go tags (prefix = package dir + /v) and each package holder's versions; each read a kept call per module; call-unanswered after five minutes, cleared on every exit; a floor entry is replaced by the release heard at its version. Quick vs thorough: thorough, every module, not the sdk alone. Whole-indexer integration test added (13 of 50). Manifest validator: three new invokes (seat:git.tags, seat:go-package-registry.versions, seat:npm-package-registry.versions); not run against the live seat list; a local judge.Manifest re-run gave 0 problems for trunk and head; all three verbs exist live. Reviewed-by: mesh-code-reviewer@shanks at b413949ea8420067a3211b45bed55ae29a244a08 (three rounds) https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
mesh-tools added 4 commits 2026-11-19 16:46:55 +00:00
mesh-catalog.versions answered [] for mesh-sdk although the forge holds go/v0.1.12..v0.1.16: the first fill read only
builder_versions, so a module the builder held nothing of was filled with nothing, and the once-only key closed it. The
indexer now reads, for every module of the newest trunk revision the versions hold none of, every tag of its Go package
from the seat git's verb tags (repository of its catalog entry, prefix the package's directory + "/v", "v" at the root),
fills the highest as its version, at each start and each catalog revision kept, and raises call-unanswered after five
minutes when the forge does not answer.

Builds: design 47 G §412, A-490b, A-490c, A-490d, A-490e
Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
The floor of a module with no version is the highest among its Go tags and the versions each package holder answers through
its seat's verb versions (npm-package-registry, go-package-registry; the sdk's npm 0.1.18 above its Go tags 0.1.16). An
unanswered read is asked again on a growing pause (5 s, 15 s, 30 s, 1, 2, 5 min) until it answers, with call-unanswered five
minutes after the first. A floor entry holds no artifacts, so a package-published heard later at its version is recorded as
its release and says version-released. One whole-indexer integration test on a real bus with a stand-in seat git and holder.

Builds: design 47 G §412, A-490c, A-490d, A-490e, A-490f, A-490g, A-490h
Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
A-490i corrects A-490h: the growing-pause timer is gone (floorpause.go and the guard's exemption removed; ADR 0437 §8 stands).
Each module's floor is read on its own (FloorModules, FillFloor); a read is a kept call through mesh-sdk's form, asked again
at once when the form gives up, so it has no bound; the first unanswered try starts the module's clock and the finding
call-unanswered is written five minutes later and cleared on answer. The integration test leaves the forge unserved until
a delay, and the fill follows with no restart and no revision.

Builds: design 47 G §412, A-490c, A-490d, A-490e, A-490f, A-490g, A-490h, A-490i
Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
FillFloor clears the module's call-unanswered finding and its call-since key on every exit but the end of its context (a release
gave the module a version, it left the trunk, the callee answered with a failure), as ADR 0668 §3 has: FloorModules never
picks the module again. The module's clock starts at its first unanswered try, not when the form gives up. The integration test
sets the form's bound to one second, waits for the module's call-since key in the state heard, and only then serves git.tags;
it fails with `return err` at the unanswered try. Unit cases for the three exits.

Builds: design 47 G §412, A-490g, A-490h, A-490i
Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
mesh-tools merged commit 5da42d1775 into main 2026-11-19 21:40:13 +00:00
mesh-tools deleted branch fix/catalog-versions-first-fill 2026-11-19 21:40:13 +00:00
Author
Member

{
"records": [
{
"instance": "record/main_1041_cdc95be5/6d594ced7b852ffe",
"sequence": 10276,
"bytes": 504,
"of-bytes": 262144,
"waits": "its difference is not known yet",
"record": {
"milestone": "main.1041",
"heads": {
"novox/mesh-delivery@260": "5da42d1775db385de3d8102ddd9810c26b337c7e"
},
"opened": "2026-11-19T21:42:05.795919145Z",
"form": 1,
"group": {
"group": "",
"pulls": [
{
"repository": "novox/mesh-delivery",
"number": 260,
"head": "5da42d1775db385de3d8102ddd9810c26b337c7e",
"state": "merged",
"commit": "5da42d1775db385de3d8102ddd9810c26b337c7e",
"base": "main"
}
]
},
"outcomes": {
"|||take-in": {
"key": "|||take-in",
"module": "",
"step": "take-in",
"outcome": "taken-in",
"at": "2026-11-19T21:42:05.794943434Z"
}
}
}
}
]
}

<!-- mesh-delivery:view --> { "records": [ { "instance": "record/main_1041_cdc95be5/6d594ced7b852ffe", "sequence": 10276, "bytes": 504, "of-bytes": 262144, "waits": "its difference is not known yet", "record": { "milestone": "main.1041", "heads": { "novox/mesh-delivery@260": "5da42d1775db385de3d8102ddd9810c26b337c7e" }, "opened": "2026-11-19T21:42:05.795919145Z", "form": 1, "group": { "group": "", "pulls": [ { "repository": "novox/mesh-delivery", "number": 260, "head": "5da42d1775db385de3d8102ddd9810c26b337c7e", "state": "merged", "commit": "5da42d1775db385de3d8102ddd9810c26b337c7e", "base": "main" } ] }, "outcomes": { "|||take-in": { "key": "|||take-in", "module": "", "step": "take-in", "outcome": "taken-in", "at": "2026-11-19T21:42:05.794943434Z" } } } } ] } <!-- mesh-act:view.record/main_1041_cdc95be5/6d594ced7b852ffe.novox/mesh-delivery#260@1795124533538526023.dfe3c60b -->
Sign in to join this conversation.
No Reviewers
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/mesh-delivery#260