Add ingestion bridge for local agent telemetry warehouse

[Zephyr709]

Background

A local-first agent telemetry warehouse MVP now exists outside this repo at /Users/jagercooper/code/agent-telemetry. It provides:

• PostgreSQL/Neon-compatible schema for agent runs, events, spans, prompts, skills, rule sets, experiments, and task outcomes
• Python CLI for manual/scripted logging
• SQL views and analysis queries for subagent effectiveness, rule impact, and prompt comparison

Follow-up

Add a Jcode ingestion bridge so tool events, model metadata, swarm/subagent lifecycle events, and task outcomes can be written to the telemetry warehouse automatically or semi-automatically.

Initial design questions

• Should ingestion be direct DB writes, CLI subprocess calls, or an event-export file that a daemon imports?
• Which events should be captured by default without leaking sensitive content?
• How should sessions map to agent_runs, agent_events, agent_spans, and task_outcomes?
• How should user opt-in/config be represented?

Acceptance criteria

• Config-gated telemetry export path.
• Captures at least run start/end, tool call/result metadata, swarm spawn/report lifecycle, and outcome annotations.
• Does not include prompts, code, file paths, or personal content by default.
• Documented local Postgres setup and validation path.

[1jehuang]

It sounds like your intent is to have a feature which is to make it easier for the user themselves to see and analyze their own telemetry data. It's an interesting ask, right now you can do this in a hacky way just by asking your agent to aggregate data from the logs. I will think about this