CSV Mapping Recipe Runner

This tool runs a repeatable declarative mapping on later files and exports the recipe. The table editor handles manual cell edits, sorting and undo. Mapping source positions are explicit and are not guessed by header names.

Choose Prepare recipe from CSV columns and run. The recipe editor receives version1 with an ordered columns array. Each entry has a1-based source position, name and steps. Reorder/remove entries or use value for a constant output column. Duplicate input headers need unique output names before transformation.

Sequential trim, upper, lower, NFC Unicode normalization, default for exact empty strings, prefix, suffix and case-sensitive literal replace. Steps use op and, where needed, value; replace also needs nonempty find. No eval, expressions, regexes, date guessing or numeric conversion.

Yes, cells remain strings throughout transformation. Case/trim/other explicit steps may intentionally change them. Spreadsheet applications can still interpret numeric-looking cells when opening CSV; import identifier columns as text.

Protection prefixes risky exported headers/cells with an apostrophe, including negative-looking text and formula/control prefixes. Working values and the before/after audit retain raw transformed strings. The on-screen audit and its CSV export contain the first200 changed/constant cells. Main CSV contains all output rows; save-recipe exports the JSON mapping.

100,000 input characters,2,000 data rows,100 columns and50,000 input/output cells. Recipes up to50,000 characters,100 output columns and20 steps per column. Literal arguments up to1,000 characters; transformed cells up to20,000. Malformed/uneven CSV, unknown recipe keys, duplicate JSON keys, invalid source positions and duplicate/blank output names are rejected. No file uploads to a server.