fix: pin rustledger v0.24.0 and refresh the snapshots it moves

[robcohen]

Closes rustledger/rustledger#2302. Supersedes #321.

Two changes that only work together

RUSTLEDGER_VERSION moves v0.22.0 -> v0.24.0, and the four snapshots move with it. Separately each is red: the bumped pin produces output the old snapshots reject (that is #321, stuck since 2026-09-06), and refreshed snapshots do not match what v0.22.0's component emits.

That deadlock is the whole of rustledger#2302. The snapshots went stale, so the upgrade bot's PR could not go green, so the pin stayed two releases behind, so rustledger's Downstream (rustfava) check -- which tests against rustledger main -- stayed red on the same four tests. The dead advisory signal there and the stalled upgrade here are one bug.

Downstream (rustfava) in rustledger has failed on every run since 2026-09-01 — 29 of its last 30, the exception being a cancelled run. That job exists to catch embedder breakage before a release: every FFI bug in the v0.17–v0.19 arc was found by rustfava after a release shipped, and the job moves that discovery pre-merge. A check that is red continuously cannot do that — a real break looks identical to the standing noise.

All four failures are stale expectations here, not regressions in rustledger. I checked each against the oracle rather than assuming, since the obvious reading (downstream fails, upstream broke it) is backwards in this case.

Two causes, six changed values

1. document directives carry tags and links — tests/__snapshots__/test_json_api-test_api-documents.json, and the same entry at index 18 of ...-journal.json.

- 'links': [],   'tags': []
+ 'links': ['link1'],   'tags': ['tag']

beancount 3.2.3, on 2012-12-15 document Expenses:Food "./import.csv" #tag ^link1:

Document -> tags=['tag'] links=['link1']

So populating them is correct. Compare beancount#2160, where Note gained the same two fields.

2. An unaliased function column is named with the whole expression — ...-sum.json and ...-misc.json.

- {'name': 'sum'}              + {'name': 'sum(day)'}
- {'name': 'units'}            + {'name': 'units(position)'}

beanquery 0.2.0 names them the same way (SELECT sum(day) → ['sum(day)']); these snapshots matched an older beanquery.

How this was produced

• Component built fresh from rustledger main (6972f5edd1) for wasm32-wasip2, and resolved through the same RUSTLEDGER_COMPONENT_WASM override the CI job uses — not the released artifact, and not the stale one that had been sitting in that path.
• Reproduced the four failures first (4 failed, 46 passed), then pytest --snapshot-update.
• Diffed the regenerated files structurally, not by line: six changed values across the four files, each attributable to a cause above. Nothing else moved.
• Full suite against the released v0.24.0 component, resolved the way CI resolves it rather than through the RUSTLEDGER_COMPONENT_WASM override: 679 passed, 1 skipped, 100% coverage. The same snapshots also pass against a component built from rustledger main (6972f5edd1), so they are correct for both.

🤖 Generated with Claude Code

https://claude.ai/code/session_012nNGPA44Dt32NyxWem26xr