Task: Carry the bulk observation reads in the models

The component drift gate passes for marketdata on main, with the bulk observation reads and the export handler carried by their models.

• check_component_drift.py –component marketdata passes.
• The generated files equal what the models regenerate, and the bulk reads and the export handler keep their behaviour.

Commit b06ddccb2f edited three generated files by hand: the observation repository (header and source) and the series handler header. The drift gate regenerates them and removes the edits. So the code moves into the paste blocks of the two models, ores.marketdata.market_observation.org and ores.marketdata.market_series.org, and the files are regenerated. The code does not change.

Every number this task claims about a tree, with the command that produced it and the commit it was measured at. A number without both is not a measurement, because a clean-up record describes a tree and trunk moves under a branch: a consumer count, a gate's component count and a suite's size all change with no code changing, and the reader of a bare number cannot tell which tree it came from. Where the raw output matters, put it in an evidence/ file beside the task and name that file in the Command column.

Found by another session, which ran the gate on main and saw it fail for marketdata. The cause was mine. I ran no drift gate on the pull request of that commit, because I chose to run gates sparingly, and I edited generated files instead of the model blocks. A model-carried read needs its section, its slot blocks and its includes in the model. read_latest_all and read_as_of_all are new sections. The manual point helper joins the block of read_as_of_records. The handler block and its chrono include are updated.

The regenerated source files equal what was committed. The header differs in order only: the generator orders the declarations by the order of the model sections.

The gate compares the tree with the committed state, so a task page or story row that is not yet committed reads as drift.

Manual QA scenarios (scaffolded via compass add test_scenario) that verify this task. Link new ones here as they're created; the scenario doc itself links back via its "Verifies task" field.

The bulk reads and the export handler live in their models, and the generated files are what the models regenerate. The drift gate for marketdata passes.