jschoubben a74f9db508 Test route-proxy without composing: its manifest's own facts and a plan entry's port, since the composition left mesh-sdk ...

The composer's proof that the manifest composes, and that a port is the placement's, is the node-engine's now (ADR 0593 §7).

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

2026-11-02 19:06:37 +01:00

..

main.go

Keep route-proxy's contract a package of its own module, not a second module behind a replace

2026-11-02 13:55:07 +01:00

manifest_test.go

Test route-proxy without composing: its manifest's own facts and a plan entry's port, since the composition left mesh-sdk

2026-11-02 19:06:37 +01:00

provider_test.go

Pin route-proxy at the group's mesh-sdk head acbf80a and its contract at the published tag v0.1.0, so it builds and reads the contributed payload; refresh its manifest digest for the events its contract names (issue 774)

2026-10-31 10:27:05 +01:00

provider.go

Keep route-proxy's contract a package of its own module, not a second module behind a replace

2026-11-02 13:55:07 +01:00

tools_test.go

Keep route-proxy's contract a package of its own module, not a second module behind a replace

2026-11-02 13:55:07 +01:00

tools.go

Keep route-proxy's contract a package of its own module, not a second module behind a replace

2026-11-02 13:55:07 +01:00