mesh-delivery

Files

T

jschoubben 0c4660eea8 The assigner's seat verbs ask the indexer's first views instead of reading its state (issue 1966, recovery)

mesh-module-assigner.propose and mesh-wants' upgrade and bus read the indexer's
modules and manifests straight from its bus state, which the runtime refuses
since those reads moved to the indexer's first-view tools (ADR 0615 §1, ADR 0621):
"mesh-delivery-assigner keeps and reads no state called mesh-delivery-indexer.modules".
Another module's data is asked through its tools, never read from its state
(ADR 0596). The verbs now ask mesh-delivery-indexer.modules and .manifests through
the tool runner, every page, at each call; the manifest already invokes both and
the indexer answers them to the assigner.

Claude-Session: https://claude.ai/code/session_01NcbgfFfQ4Z9UE5jK32PmE5

2026-11-08 11:54:37 +01:00

mesh-delivery-assigner

The assigner's seat verbs ask the indexer's first views instead of reading its state (issue 1966, recovery)

2026-11-08 11:54:37 +01:00

mesh-delivery-builder

Take the Go package artifacts out of the delivery parts for now, so the running builder builds them (issue 1966)

2026-11-07 19:48:57 +01:00

mesh-delivery-checker

Round 1: known by the module path alone, never a package inside it

2026-11-08 01:24:54 +01:00

mesh-delivery-forge-bridge

Take the Go package artifacts out of the delivery parts for now, so the running builder builds them (issue 1966)