@table ... params= is accepted into Table.params (src/document.jl:682, :707).
Neither emitter reads it:
src/themes/agent.jl:148-176 emit_table -- no params in the JSON
src/themes/gallery.jl:1242-1268 emit_table -- no params either
Repo-wide, params on a Table is read in exactly one place: src/testset.jl:1648-1649, which @warns that it is dropped across a shard dump. In an ordinary direct render it is dropped with no warning at all.
A caller who writes @table data params=key, mirroring @figure ... params=key and expecting the same DataVault-lineage treatment CLAUDE.md attributes to params, gets a complete no-op.
Fix
Surface Table.params in agent.json the way _agent_params_json does for Figure, or drop the kwarg and warn at macro-expansion time.
@table ... params=is accepted intoTable.params(src/document.jl:682,:707).Neither emitter reads it:
Repo-wide,
paramson aTableis read in exactly one place:src/testset.jl:1648-1649, which@warns that it is dropped across a shard dump. In an ordinary direct render it is dropped with no warning at all.A caller who writes
@table data params=key, mirroring@figure ... params=keyand expecting the same DataVault-lineage treatment CLAUDE.md attributes toparams, gets a complete no-op.Fix
Surface
Table.paramsinagent.jsonthe way_agent_params_jsondoes forFigure, or drop the kwarg and warn at macro-expansion time.