@network-harness/core-kernel

The mechanics every core component shares, and nothing a component owns.

• Caller derivation (callingEntry): which installed extension a component operation is being called from, read off the accessing context. This is the mechanism behind attribution, policy checks, and per-protocol scoping, so the components never take a caller-supplied id.
• Settle audit (auditEntries, formatAudit): the legible report the daemon prints once the extension tree settles -- a failed entry with its error, a pending entry with the services it is waiting for.