feature/Runner-log-context · L-260916-b7759f — drop shim, json sink, no rich

[lchoquel]

The runner now binds the runtime's log context per request and emits its fields through the runtime's log calls, so its own request-id contextvars and logfmt flattener are gone. It boots on the json sink with the silent pretty-print mode and builds its image without the Rich extra; it pins pipelex 0.66.0, the release that carries the log seam.

Closes L-260916-b7759f

🤖 Generated with Claude Code

https://claude.ai/code/session_019vmb35cM2bCxTwn49kCAXQ

---

Summary by cubic

Replaces the runner's request-id contextvars and logfmt flattener with Pipelex's runtime log context and a JSON line sink on stderr. Error lines now carry each value as its own JSON field, and request_id is bound per request so every record the request emits — including ones Pipelex emits from inside a run — carries it. Drops the cli extra, so the Rich terminal renderer is never reached.

Closes L-260916-b7759f.

Notes

• Anything parsing the old console/logfmt output must switch to the JSON line format.
• A custom pipelex.toml must keep sink = "json", console_log_target = "stderr", and pretty_print_mode = "silent".
• The sprint git-source pin for pipelex has collapsed onto the released 0.66.0; the runtime-contract guard and its test are deleted with it.
• pipelex 0.66.0's redaction processor escapes control characters in field values and redacts credentials echoed into detail; tests and docs/logging.md cover both.
• Local Docker builds no longer bake untracked .pipelex override files into the image.
• Deferred review findings are tracked in wip/structured-logs/review-deferrals.md.

^{Written for commit ef292eb. Summary will update on new commits.}

[lchoquel]

/rev round 4, profile 4, bar freeze on e4b607f (the branch after absorbing dev through v0.27.5 and moving the pipelex pin to 80896463).

Four reviewers ran: cubic, Codex review, Codex adversarial and code-review at level medium. code-review found nothing. Two findings were verified: Codex review's claim that .dockerignore drops a flavor's baked .pipelex/api_<env>.toml was refuted, because no tracked file is lost and the one real flavor builds from its own tree with its own ignore file. Codex adversarial's claim that a distributed /execute loses request_id at the worker was confirmed; it predates this branch and is not critical.

Nothing was fixed, because the bar admits only criticals and there were none. Every other finding is deferred with its trace in wip/structured-logs/review-deferrals.md under round 4 (fe2ac4b): the request-id gap on a Temporal /execute, the 413, 404 and 405 responses that write no api_error record, uvicorn's plain-text traceback on the JSON stderr stream, the missing version specifier on pipelex, a runtime-contract test that cannot fail, and a round-2 deferral whose premise dev has since closed.

converged — the round-4 pass at profile 4 was clean with full coverage, at or above the required depth of 4; nothing further is warranted