4 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	5fa64be894	Revert the revert of G's mesh-sdk merge (#191): G's sdk stands again over reader release 3 ... Main reverted G's half merge (#189, reverted by 8afc3eb in #191) and then took the reader release's S1-S5, which copied G's code. G's form holds where they differ (process_bus.go, seats.go, state.go and their tests); the release's kept names stay so main's callers keep building: SeatViewPrefix beside SeatReadPrefix, and QueueInvoke's empty strings on not-ok (with its test TestQueueInvoke). The tree differs from G's head f30dee54 only by those and the release's two tests (objects cap option, seat states and stream kinds). Builds: design 47 G (the milestone's sdk part, as at f30dee54) Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h	2026-11-13 12:49:56 +01:00
jschoubben	8afc3ebdf3	Revert G's mesh-sdk merge (#189): G merged half, and today's validator refuses G's delivery parts ... The group feat/47-G-join11 merged 3 of 17 members on 2026-11-13; G's mesh-sdk alone on main breaks 25 trunk modules. The operator chose to put the order right: a reader release first, then G whole. This restores main to 8fbba810 exactly. Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h	2026-11-13 11:12:48 +01:00
jschoubben	0d546d37f3	T-1, T-2: W1.11: the TypeScript side holds a seat as the Go side does ... A TypeScript holder, the forge module first, must judge a verb's caller by the runtime's proof, say its seat's events and answer its first views' read and ask-again tools (design 47, The forge module's tools come from mesh-sdk's TypeScript side; G-F1 option A). The stdio session now hands each tool the caller and call id the runtime wrote in _meta (callers.callerOf, the Go rules for Callers and VerbCallers), binds the runtime for seatPublish over mesh/seat.publish and config, and views gains the Follower and its two status tools over the state first-views. @novox/mesh-sdk 0.1.19. Builds: design 47 G §196, §200, §336 Claude-Session: https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ	2026-11-11 10:51:07 +01:00
jochen	78817c949e	A tools bundle speaks MCP over stdio: the loop in TypeScript, and skeleton SDKs for Python, Go, Rust and C (hq ADR 0187) ... The node's runtime launches a tools bundle as a process and speaks MCP over stdio to it, so a tool may be written in any language and the transport stays in the runtime (ADR 0039's refusal, kept). Each SDK is the loop and the tool type and nothing else: `@novox/mesh-sdk/stdio` (serveStdio, and serveRegisteredOverStdio for a bundle that already registers the in-process way), python/, go/, rust/ and c/ beside it, each with an example answering `greet` and the seat verb `node-lamp.on`. Skeletons, by the operator's direction: the bare minimum one bundle per language needs to be built and answer, proven here by each example answering tools/list and tools/call on stdio.	2026-10-02 20:34:19 +02:00