Should a document format do table arithmetic?

[xiongjy2104]

A GEML table can compute a column and a summary row at build time:

=== table {#fy25 format=csv header=1 compute="FY = Q1 + Q2 + Q3 + Q4" summary="Segment = 'Total'; FY = sum(FY)"}
Segment,  Q1, Q2, Q3, Q4
Cloud,     8, 10, 12, 14
===

This is the only place the format computes anything, and it sits right against
a boundary we wrote ourselves: "tables compute, but aren't a spreadsheet engine."

Keeping it means owning formula semantics forever — precision, error reporting,
locale, and a steady stream of "just one more function". Dropping it means the
numbers get computed somewhere else and pasted in, which is the copy-drift
the format exists to prevent.

The options

1. Keep — leave compute= / summary= as they are.
2. Freeze — keep exactly today's arithmetic, write "no new functions, ever"
   into the spec, and close the slope.
3. Drop — no arithmetic in the format; a preprocessor emits a plain table.

If you have a document with compute= in it, say what it computes — that is
worth more than any argument here.

(No poll widget on this one — reply with 1, 2 or 3 and, if you have one, the reason. A bare number is a useful answer.)