Looking for one ugly workbook case to turn into a fixture

[gregkonush]

I am trying to make the next few Bilig examples come from real workbook-shaped problems instead of more synthetic demos.

Use this thread before a fixture issue when you are still reducing one workbook/formula/import-export/service/API/agent/MCP case. If the case is already reduced and public, file the structured fixture form instead:

https://github.com/proompteng/bilig/issues/new?template=workbook_fixture.yml

Useful cases are small and boring:

• package version or commit tested
• sheet names, exact cells or ranges, and formulas
• input values before and after the edit
• expected output from Excel, another system, or a manual check
• actual Bilig output, import error, stale cached value, missing API, or current workaround
• one command or script a maintainer can run

For stale cached XLSX formula values after Node edits, start locally with:

npm exec --package @bilig/xlsx-formula-recalc@latest -- xlsx-cache-doctor ./reduced.xlsx --json

Paste only the reduced public stale object fields: target, formula, cachedValue, literalRecalculatedValue, cacheStatus, and suggestedReads. The current proof transcript is here:

https://proompteng.github.io/bilig/xlsx-cache-doctor-proof-transcript.html

For MCP or agent reports, include the write, recalculation, and readback tool transcript. A write-call status alone is not proof.

Please do not send private customer spreadsheets, confidential financial models, or files without redistribution rights. Replace names and numbers, keep the formula shape, and make sure the reduced file can become a public test, docs page, example, or corpus fixture.

What I want from this loop: fewer claims, more public proof. Accepted cases may become regression tests, XLSX corpus cases, WorkPaper JSON fixtures, service examples, docs, or compatibility notes. Out-of-scope cases should still get a concrete answer.

[gregkonush]

Narrowing this request a bit: I am especially looking for one reduced ExcelJS-style workbook that has shared formulas or stale cached formula values after a Node service edits inputs.

The useful shape is small:

• one sheet with input rows and repeated formula rows;
• the exact cells ExcelJS reports as sharedFormula or old cached results;
• the expected values after Excel or LibreOffice recalculates;
• the value Bilig gets, or the import/runtime gap that blocks it.

I wrote up the boundary here so the fixture ask is concrete, not a generic "try my library" pitch:
https://proompteng.github.io/bilig/exceljs-shared-formula-recalculation-node.html

If someone has this failure mode in a private workbook, please reduce the data before sharing. Fake names and numbers are fine; the formula shape is what matters.