Story: Show a curve evolving in ores.web

A person opens ores.web, names a curve or a surface, and watches it evolve as an aligned matrix of instants by nodes, with each node's change, staleness and provenance.

• The BFF exposes the identity, snapshot, slice and evolution reads, each behind the permission the server checks.
• A person reaches the evolution screen from the market data area and reads the aligned matrix for a named object.
• The screen shows each node's status, the age of each value and, on request, where each value came from.
• A hole is shown as a hole and a refused request is shown as a reason.

• One module, four POST routes. The BFF reads a composite object through /api/curves/ series, snapshot, slice and evolution. Each is a POST because the identity is a structure. The routes check structure only. The server keeps the permission and the shape rules, and a refused read reaches the person as the server's reason.
• The screen is the evolution matrix plus the object now. Nodes are rows and instants are columns. Each node states its change over the range. A missing value is a hole and never a zero. The Now table gives the age of each value and, when asked, its source.
• Curve data is visible to the party that owns it. The first look in a browser showed an empty page, because the demo data belonged to the System Party and the person had signed in as another party. The screen now says so instead of saying the object has no node. The story does not change the rule.
• Real data found what canned data hid. The contract typed the snapshot's warning as a string and the server sends a boolean. Tests built on invented replies passed. A run against the running stack with ORE's own FX volatility data found it. Contract tests for a wire shape should use a reply the server sent.

Left for later, none of it in this story.

• A series list route and a picker, so the object is chosen and not typed. It should list only the series the party can see. Capture curve_screen_series_picker.
• A shape declared when a synthetic feed starts. Feed ticks never declare axes, so a synthetic curve has points and cannot be shown. It crosses into the synthetic story, which another environment owns. Capture synthetic_feed_declares_its_shape.
• A wire operation to key and clear a manual point, and the adjust-by-hand screen. Capture key_a_manual_point_from_the_web.
• The approval chain and the publication record. Capture curve_publication_and_approval.

• Writing a point. Keying and clearing a manual point needs a wire operation first.
• The approval chain: ask, decide, publish and withdraw.
• Charts beyond the aligned matrix. The first screen is a table.