Task: Repair the generated files main left drifted

Table of Contents

This page documents a task in the Let the model state how the store keeps a column story. It captures the goal, current status, acceptance, and any notes or results.

1. Goal

The estate renders without drift, so a codegen change can land.

2. Status

Field Value
State DONE
Parent story Let the model state how the store keeps a column
Now Nothing.
Waiting on Nothing.
Next Nothing.
Last touched 2026-10-31

3. Acceptance

  • The feed scope model states the feed its row references, and the generated test seeds that parent by reading the catalogue
  • No hand edit to a generated file remains in the estate
  • The drift gate over every component reports no drift

4. Plan

A codegen change under projects/ores.codegen selects every component for the drift gate, because a template decides every component's output. The gate therefore read the two files main carries drifted, and neither belongs to this branch's own commit.

Take each one at its cause.

The feed scope test needed a feed the system catalogue holds. The hand edit named one by id and carried its include. The model states the reference instead: a soft FK to the feed catalogue with :use_system_tenant:, and :skip_check: because the invariants trigger already refuses a scope whose feed is absent and says more than a plain existence check would. The generated test then reads the catalogue and takes the first feed.

The trade summary files are stale output: the model declares structure_id and is_leg, and the TypeScript was generated before they landed. Regenerate.

5. Measurements

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.

What Value Command Commit
marketdata drift no drift check_component_drift.py --component marketdata branch head
trading drift no drift check_component_drift.py --component trading-cpp branch head
marketdata suite 340 cases, 0 failures compass test run -- -R ores.marketdata.core.tests branch head
BFF list requests 1054 requests agree with the protocol python3 projects/ores.codegen/scripts/check_bff_list_requests.py branch head

6. Notes

7. Test Scenarios

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.

Scenario State Notes
     

8. PRs

PR Title
   

9. Review

Comment summary File Decision Notes
       

10. Result

The generated eventing test seeds its feed by reading the system catalogue, so no hand edit and no hardcoded id remain. The trade summary TypeScript carries the two columns its model declares. Both components render without drift, which is what a codegen change needs before it can land.

Emacs 29.3 (Org mode 9.6.15)