diff options
| author | Adam Malczewski <[email protected]> | 2026-06-06 22:23:23 +0900 |
|---|---|---|
| committer | Adam Malczewski <[email protected]> | 2026-06-06 22:23:23 +0900 |
| commit | 219cf053fad4e48b22590d3178438bf5d67d04e3 (patch) | |
| tree | 5d04a3105efc793de8ad3b3cf1c584f8b176dc27 /packages/kernel/src/runtime | |
| parent | 2c5bc242a8a99e3b863c247f70b26f5883333677 (diff) | |
| download | dispatch-219cf053fad4e48b22590d3178438bf5d67d04e3.tar.gz dispatch-219cf053fad4e48b22590d3178438bf5d67d04e3.zip | |
docs(harness): author extension-logging rule (close the pending logging gap)
The .dispatch/rules/extension-logging.md rule was '(pending)' in ORCHESTRATOR
§3 for the entire life of the observability substrate, so every extension
summon was built without logging/self-redaction guidance — leaving most
extensions silent (a coverage audit found conversation-store, transport-http,
credential-store, tool-read-file, storage-sqlite, auth-apikey, surface-* all
with zero logger refs).
- Author .dispatch/rules/extension-logging.md (tribal-knowledge only, P6/P7):
self-redact your own secrets in your own code (no shared helper; §6 tiers),
use injected host.logger/ctx.log, flat scalar attrs, no token-delta logging,
one-way logs, edge verbatim capture.
- Wire it into ORCHESTRATOR §3 as 'every extension' — include on EVERY
extension summon; remove the (pending) note.
- Record the coverage audit + remaining instrumentation debt (#1 reconcile.repair
span in conversation-store, #2 transport-edge logging) in tasks.md.
Future extensions now get logging by construction.
Diffstat (limited to 'packages/kernel/src/runtime')
0 files changed, 0 insertions, 0 deletions