api: POST /api/scenario returns result plus graph topology (M3 slice 1)

One panel's whole world in one call: effective config in, echoed
config + cascade result + undirected edge list out. Edges are
[from, to] pairs with from < to in deterministic node order;
Graph.Edges() walks the adjacency once, GraphEdges(config) rebuilds
the seeded world (~25us) so Result stays lean and /api/comparison
stays untouched. This closes the topology gap the design brief
flagged; the frontend's seeded d3-force layout consumes these pairs.
Go bits: [][2]int is a slice of fixed-size arrays; [2]int is a value
type, comparable, and JSON-marshals to [a, b], exactly the wire
shape the spec asks for.
tygo regen includes a fix: engine.Strategy now maps to the generated
Strategy type instead of decaying to 'any' in ScenarioRequest.
Verified live through the dev stack: 7/120 reached, 351 edges.
This commit is contained in:
Justin Visser 2026-06-10 15:48:48 +02:00
parent 8c8d5bca11
commit 9a392b1860
12 changed files with 1790 additions and 2 deletions

View file

@ -1,5 +1,5 @@
// Code generated by tygo. DO NOT EDIT.
import type { Config, Result } from "./engine";
import type { Config, Result, Strategy } from "./engine";
//////////
// source: api.go
@ -18,3 +18,22 @@ export interface ComparisonResponse {
config: Config;
results: Result[];
}
/**
* ScenarioRequest is the body of POST /api/scenario: one panel's effective
* config plus its strategy.
*/
export interface ScenarioRequest {
config: Config;
strategy: Strategy;
}
/**
* ScenarioResponse carries everything one dashboard panel needs: the
* echoed config, the cascade result, and the network topology as
* [from, to] node-index pairs (deterministic from the config's graph
* fields) for the frontend's force layout.
*/
export interface ScenarioResponse {
config: Config;
result: Result;
edges: number /* int */[][];
}