Bridge for G's builds: an empty meshconditionsclient/findings package #12

Merged
jschoubben merged 1 commits from fix/47-G-bridge-findings into main 2026-11-13 14:48:03 +00:00
Member

Design 47 milestone G, issue 1966 (retrospective: note 216).

G's delivery parts cannot build: assigner, builder, checker, indexer, teller, view, watchman and pipeline runner.

Their last build before G imported meshconditionsclient/findings. G removed that package, so it is unpublished and their fingerprints fall to the version line (indexer journal: "no published package holds .../meshconditionsclient/findings, so its fingerprint takes the version line"). Their build asks then name no mesh-sdk commit, fetch pre-G mesh-sdk v0.1.14, and fail on approval, operatorask and stateobjects. Because they fail, they never record their new imports.

This adds back an empty findings package so the indexer publishes it again. It goes once those modules have built under G.

go vet of the package passes. The review round is bent, said to the operator: a one-line empty package.

Reviewed-by: lead-47@shanks at 8e722a68

https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h

Design 47 milestone G, issue 1966 (retrospective: note 216). G's delivery parts cannot build: assigner, builder, checker, indexer, teller, view, watchman and pipeline runner. Their last build before G imported `meshconditionsclient/findings`. G removed that package, so it is unpublished and their fingerprints fall to the version line (indexer journal: "no published package holds .../meshconditionsclient/findings, so its fingerprint takes the version line"). Their build asks then name no mesh-sdk commit, fetch pre-G mesh-sdk v0.1.14, and fail on `approval`, `operatorask` and `stateobjects`. Because they fail, they never record their new imports. This adds back an empty `findings` package so the indexer publishes it again. It goes once those modules have built under G. `go vet` of the package passes. The review round is bent, said to the operator: a one-line empty package. Reviewed-by: lead-47@shanks at 8e722a68 https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
mesh-tools added 1 commit 2026-11-13 14:38:45 +00:00
Bridge for G's builds: an empty meshconditionsclient/findings package
mesh/delivery merged: source.main moved to novox/mesh-contracts@20b06dbcd32e
8e722a68c9
The modules whose last build before G imported meshconditionsclient/findings (the assigner, builder, checker, indexer,
teller, view, watchman) get a fingerprint on the version line while that package is unpublished, so their build asks
name no mesh-sdk commit and fetch pre-G mesh-sdk; they fail and never record new imports (2026-11-13, indexer journal
'no published package holds .../meshconditionsclient/findings'). An empty package is published again; it goes once
those modules have built under G.

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
jschoubben merged commit 20b06dbcd3 into main 2026-11-13 14:48:03 +00:00
jschoubben deleted branch fix/47-G-bridge-findings 2026-11-13 14:48:03 +00:00
Author
Member

Delivery novox/mesh-contracts@8e722a68c9f3 — merged since 2026-11-13T15:30:04Z

Source — source.main moved to novox/mesh-contracts@20b06dbcd3. Whether it reached the machines is mesh-delivery-view's, derived from source.main, the wants and the haves.

Transitions

  • 2026-11-13 15:30 (new) → proposed (announced): novox/mesh-contracts#12's head announced
  • 2026-11-13 15:30 proposed → ready (accepted): a verdict names this commit and the trunk's head as its trunk commit, the gate passed or warned, and the repository's own check did not fail; or the check gates no merge (check-gates-merge false)
  • 2026-11-13 15:30 ready → merged (merged): on the trunk its modules follow: merged there

The commit's note under refs/notes/mesh-plan keeps every transition of this change up to its merge: git log --notes=mesh-plan.

<!-- mesh-delivery:view --> **Delivery** `novox/mesh-contracts@8e722a68c9f3` — **merged** since 2026-11-13T15:30:04Z **Source** — source.main moved to novox/mesh-contracts@20b06dbcd32e. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves. **Transitions** - 2026-11-13 15:30 (new) → proposed (announced): novox/mesh-contracts#12's head announced - 2026-11-13 15:30 proposed → ready (accepted): a verdict names this commit and the trunk's head as its trunk commit, the gate passed or warned, and the repository's own check did not fail; or the check gates no merge (check-gates-merge false) - 2026-11-13 15:30 ready → merged (merged): on the trunk its modules follow: merged there The commit's note under `refs/notes/mesh-plan` keeps every transition of this change up to its merge: `git log --notes=mesh-plan`. <!-- mesh-act:switched.owed.21843.novox/mesh-contracts.12.8e722a68c9f357a72bb6eae80b0d77812f43e120.view -->
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-contracts#12