stage-tabs-builder

Invoke the skill with a table ID, file slug, or purpose phrase, and it reads the fingerprinted evidence files under mates/, maps each row and column to an anchored number, and emits a booktabs table under manus/tabs/ with per-row source comments.

Each data row gets a % src: mates/<file>#<anchor> comment placed directly above it, so an auditor can walk from any cell to the exact evidence file and anchor. Numbers are re-read at their anchors before the table ships.

The cell becomes a \todo{...} naming the missing measurement, and an unsourced claim row is opened in notes/claims.md. Hand-typed numbers from chat or memory are never written into cells; the user is routed to register the evidence first.

Yes, but only after registering them through mates/manual/ with a MANIFEST entry via the evidence curation step. Even well-known literature numbers must carry a fingerprint before they can appear in a table cell.

An empty mates/ directory means there is no fingerprinted evidence to compile from, so the skill halts and routes to evidence import instead of starting a table on promises. This enforces the rule that evidence precedes typesetting.

Yes, it runs import.sh --diff to compare source stamps of cited entries against upstream before typesetting. Stale evidence is reported and re-imported with user approval before its numbers ship.