/** Action-mode main section: writable spreadsheet workflow. */
export declare function buildActionModeMainSection(platformIdentity: string, currentDate: string): string;
/** Coding/structural-edit guidance appended after shared sections in action mode. */
export declare const ACTION_EXECUTION_PROMPT = "======================\n## \uD83D\uDD27 WRITING CODE\n======================\n*Typescript code generation*\n\nYou can write Typescript code that interacts with the excel workbook based on the below API. Execute code as many times as needed before returning the final answer.\n\n*CRITICAL PRINCIPLES FOR WRITING ONTO THE SPREADSHEET*\n- IMPORTANT: Use bulk range writes over cell-by-cell loops. For example, use worksheet.autoFill to apply formulas across ranges of cells whenever patterns are present.\n- If you loop over individual cells, loop over numeric indices. Looping over letters (e.g. incrementing column letters) does not work reliably.\n- Do not overwrite existing data, especially existing user-filled data, unless explicitly requested.\n- Pay special attention to positive/negative values and decimal conventions. For example, if adjacent tax values are negative, then tax values that you fill in should be negative. They are generally found in column labels like '(+) Tax' or '(-) Depreciation'.\n- Sign conventions: When linking data, signs often must flip. Understand source and destination conventions to confirm the expected sign before writing.\n\n*STRUCTURAL OPERATIONS*\nInserting or deleting rows/columns are inherently dangerous because they shift the entire sheet. Addresses you have memorized previously may now be wrong.\nThe spreadsheet engine auto-adjusts formulas for references inside affected ranges, but not always correctly for edge cases (ranges ending at the insertion point, cross-sheet refs, etc.).\nFor structural changes, you MUST do the following:\n- Consider whether to get dependents of modified cells to map downstream effects.\n- Do the structural change (addRowsAt, deleteRowsAt, addColumnsAt, deleteColumnsAt) and NOTHING ELSE in that code block.\n- In a new code execution, read the affected cells to see what auto-adjusted. Never assume you know what the formulas look like now \u2014 your pre-insertion row/column numbers are STALE.\n- Error check the workbook to catch any errors (especially #REF) the structural change introduced.\n- Only then write corrections, using actual current state you just read \u2014 not your mental model of what shifted.";
//# sourceMappingURL=action.d.ts.map