Skip to content

feat(scenario): add DAG critical-path execution#172

Merged
Rjected merged 1 commit into
mainfrom
dan/scenario-critical-path
Jul 24, 2026
Merged

feat(scenario): add DAG critical-path execution#172
Rjected merged 1 commit into
mainfrom
dan/scenario-critical-path

Conversation

@Rjected

@Rjected Rjected commented Jul 24, 2026

Copy link
Copy Markdown
Member

Adds opt-in dependency-graph execution for multi-chain scenarios while preserving sequential specs. Ready branches execute concurrently with dependency/output ancestry validation, fragment-boundary dependencies, ordered-nonce safety, and deterministic Tempo expiring transaction identities that preserve the configured priority fee.

Scenario waits use WebSocket-assisted canonical observation with a 50 ms polling fallback, confirmation-aware receipt/log milestones, and receipt-scoped event groups. JSON report schema v2 separates command duration from protocol timing and computes per-instance critical paths and causal edges.

ClickHouse publication remains compatible with migrations through 008 by writing the existing aggregate, step, receipt-gas, and run-marker projection; v2 causal metrics and sampled traces are JSON-only in this PR.

@Rjected
Rjected force-pushed the dan/scenario-critical-path branch from faea42a to 1177200 Compare July 24, 2026 19:52
@Rjected
Rjected marked this pull request as ready for review July 24, 2026 20:25
@Rjected
Rjected merged commit cef418d into main Jul 24, 2026
8 checks passed
@Rjected
Rjected deleted the dan/scenario-critical-path branch July 24, 2026 20:25
Rjected added a commit that referenced this pull request Jul 24, 2026
Publishes scenario report v2 causal metrics and sampled lifecycle traces
to ClickHouse on top of #172.

It adds DAG identity and command-duration columns to the existing
scenario tables, creates dedicated causal-edge and sampled-trace tables,
and updates the migration runner to apply migration 009’s statements
individually. The additive migration retains the legacy latency columns
used by existing queries.

Deploy migration 009 before switching scenario runners to this branch.
It can roll out first because the migration-free writer from #172
remains compatible with the expanded tables.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant