Trace chart: surface a run-context header (manifest/instrument/window) in the served page #102

New Issue

2026-06-19T00:58:50+02:00

Brummel commented

2026-06-19 00:58:50 +02:00

Surface a run-context header in the served trace chart

The first-cut trace chart (aura chart <name>, spec 0056, shipped via #101) renders
the recorded series (equity / exposure, overlaid or in timestamp-aligned panels)
but does not surface any run-context: which instrument, broker, window, or commit
the chart belongs to. The page chrome is also still the graph-viewer's (<title> /
header read "aura graph", inherited from the shared SHELL_HEAD).

The data is already there — the run RunManifest (commit, params, window, seed,
broker) is persisted on disk in runs/traces/<name>/index.json and read back into
aura_registry::RunTraces.manifest — but render_chart_html deliberately drops it
from the injected window.AURA_TRACES (the naive viewer renders only series). This
was a ratified scope call at the trace-charts cycle close: a run-context header
matters most when distinguishing multiple runs, which is the deferred
families/comparison work (C21), not the single-run first cut.

When the families/comparison views land (or sooner if wanted):

re-include manifest (and the taps list) in ChartData / the injected
window.AURA_TRACES;
render a small run-context header in chart-viewer.js (e.g. taps · broker · window), and adjust the page chrome (title/header) to read as a chart rather than
the graph viewer;
a node .mjs guard for the header-build is cheap (pure, like buildCharts).

depends on: families/comparison meta-views (C21) — natural home; standalone-doable sooner.
context: ratified deviation from spec 0056 §1/§4, surfaced by the architect at the
trace-charts cycle-close audit. The series render is unaffected.

## Surface a run-context header in the served trace chart The first-cut trace chart (`aura chart <name>`, spec 0056, shipped via #101) renders the recorded **series** (equity / exposure, overlaid or in timestamp-aligned panels) but does **not** surface any run-context: which instrument, broker, window, or commit the chart belongs to. The page chrome is also still the graph-viewer's (`<title>` / header read "aura graph", inherited from the shared `SHELL_HEAD`). The data is already there — the run `RunManifest` (commit, params, window, seed, broker) is persisted on disk in `runs/traces/<name>/index.json` and read back into `aura_registry::RunTraces.manifest` — but `render_chart_html` deliberately drops it from the injected `window.AURA_TRACES` (the naive viewer renders only series). This was a **ratified scope call** at the trace-charts cycle close: a run-context header matters most when *distinguishing multiple runs*, which is the deferred families/comparison work (C21), not the single-run first cut. When the families/comparison views land (or sooner if wanted): - re-include `manifest` (and the `taps` list) in `ChartData` / the injected `window.AURA_TRACES`; - render a small run-context header in `chart-viewer.js` (e.g. `taps · broker · window`), and adjust the page chrome (title/header) to read as a chart rather than the graph viewer; - a node `.mjs` guard for the header-build is cheap (pure, like `buildCharts`). depends on: families/comparison meta-views (C21) — natural home; standalone-doable sooner. context: ratified deviation from spec 0056 §1/§4, surfaced by the architect at the trace-charts cycle-close audit. The series render is unaffected.

Brummel added the idea label 2026-06-19 00:58:50 +02:00

Brummel referenced this issue

2026-06-19 01:05:12 +02:00

feat: trace charts — tap graph streams to disk, serve as web charts (visual face, first cut) #101

Brummel referenced this issue from a commit

2026-06-19 12:42:57 +02:00

audit(trace-charts): cycle close — C22 realization note, retire ephemera

Brummel referenced this issue

2026-06-19 18:09:02 +02:00

feat: trace-chart viewer comfort (Tier 1) — collapse-gaps x-axis (optional continuous), zoom/pan/cursor-sync #103

Brummel referenced this issue

2026-06-19 18:11:11 +02:00