jschoubben bf5339cec2 runtime: take node and module identity from the sealed credential ...

The mesh scoped the account to a node and module; the credential now carries
both, so the runtime names its queue and stamps its events as the mesh
authorised without a manifest interpolating a node the vocabulary has no token
for. Verified: with only MESH_BROKER_FILE, the audit logger consumed as
anchor/audit-logger.

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

2026-09-04 01:53:23 +02:00

..

broker-amqp.ts

runtime: take node and module identity from the sealed credential

2026-09-04 01:53:23 +02:00

main.ts

runtime: take node and module identity from the sealed credential

2026-09-04 01:53:23 +02:00

runtime.ts

runtime: connect with a sealed credential, scoped, over pinned amqps (ADR 0048)

2026-09-04 01:51:17 +02:00