@network-harness/core-trace

Claims ctx.trace. Every message sent, run executed, revision authored, and consent answered leaves a record here, attributed to the identity or extension that caused it, so what this node's representative did can be reconstructed afterwards.

Two properties the rest of the harness depends on:

• append never fails into the caller's path. A component that cannot record what it did still has to finish doing it.
• Attribution is derived, never supplied. The actor comes from the accessing context (callerOf): an extension's row in the extensions tree makes it an extension, anything else is a component. trigger stays a caller input, because only the caller knows whether it acted for a human, a peer, a schedule, or itself.

The store is one JSONL file, appended synchronously. Records are small and low-volume, and a queued write that a crash loses is worse than the time a small synchronous append costs. Queries read a bounded tail of the file, so retention is prune, not a growing scan.