dsh-office-kit 0.4.2 → 0.4.3

package/assets/skills/excel-live-control/references/read_only_qna.md

@@ -1,59 +1,54 @@
 # Answering questions about a workbook the user has open
 
-Read-only work: no writes, no saves, no restyling. The deliverable is an answer with cell
-references the user can check, not a changed document.
+Read-only: no writes, no saves, no restyling. Deliver an answer with cell references the
+user can check, not a changed document.
 
 ## Reading
 
-- `info` first: which workbook, which sheets, which used ranges, tables, charts, pivots.
-  That tells you where to look and whether the thing the user is asking about even exists.
-- `read_range --formulas` for the cells that matter. You almost always need both: the
-  value tells you *what*, the formula tells you *why*. A number with no formula behind it
-  is an input the user typed; a formula with no precedent is a number you cannot trust.
-- `read_range --display` when the question is about how something *reads* (`###`, a
-  truncated label, a date that shows as a serial). Displayed text follows the number
-  format; the value does not.
-- Read the workbook's own labels — row and column headers, period names, "Actual" vs
-  "Forecast" markers, units — before interpreting a cell. `D14` is only meaningful when
-  you know it is "Q3 advertising spend, USD".
-- The window may be ahead of the disk file. If `info` shows `saved: false`, the numbers
-  you read are the user's unsaved state; say so if the answer would differ from the file.
+- `info` first: which workbook, sheets, used ranges, tables, charts, pivots — and whether
+  the thing asked about exists.
+- `read_range --formulas` for the cells that matter. The value says *what*; the formula
+  says *why*. A number with no formula is a typed input; a formula with no precedent is
+  untrustworthy.
+- `read_range --display` when the question is how something *reads* (`###`, a truncated
+  label, a date shown as a serial): displayed text follows the number format, values do
+  not.
+- Read the workbook's labels — headers, periods, "Actual" vs "Forecast", units — before
+  interpreting a cell. `D14` means nothing without "Q3 advertising spend, USD".
+- The window may be ahead of the file. `info` showing `saved: false` means you are reading
+  the user's unsaved state; say so when the answer would differ.
 
 ## Answering
 
-1. **Locate the output by its labels**, not by guesswork: find the row/column that names
-   the metric and the period the user asked about, then read the intersection.
-2. **Trace the precedent chain** back from the output to labelled assumptions or raw
-   inputs. `read_range --formulas` on each step; stop at cells whose value is typed rather
-   than computed. Reporting an intermediate total as the cause is the classic error.
-3. **Reconcile before asserting.** If a total does not equal the sum of its parts, that is
-   the finding — report the gap and the cells, do not average it away.
-4. **Compute from the underlying values.** A cell showing `1.2` may hold `1.2345`; the
-   answer to "what is the margin" uses the stored value, and if the requested precision
-   needs the rounded number, say that you are using the displayed value.
-5. **Rank drivers** by absolute contribution when the question is "why did it move".
-   Report the top two or three with their cells and amounts, not a list of everything.
-6. **Cite cells** in the reply: `` `Summary!D14` shows 1,234 units because `Build!F7:F12`
-   sums to that ``. A claim without an address is not verifiable.
-7. If two sheets disagree, say which one you believe and why (more recent period, source
-   data rather than a copy, a formula chain rather than a paste), and do not "fix" either
-   without being asked.
+1. **Locate the output by its labels**, not by guessing: find the metric's row/column and
+   the period, then read the intersection.
+2. **Trace the precedent chain** back to labelled assumptions or raw inputs. Use
+   `read_range --formulas` at each step; stop at typed cells. Reporting an intermediate
+   total as the cause is the classic error.
+3. **Reconcile before asserting.** If a total is not the sum of its parts, that is the
+   finding: report the gap and the cells; do not average it away.
+4. **Compute from underlying values.** A cell showing `1.2` may hold `1.2345`; use the
+   stored value, and say so if the requested precision forces the displayed one.
+5. **Rank drivers** by absolute contribution for "why did it move": the top two or three,
+   with cells and amounts, not everything.
+6. **Cite cells**: `` `Summary!D14` shows 1,234 units because `Build!F7:F12` sums to that ``.
+   A claim without an address is unverifiable.
+7. Sheets disagree: say which you believe and why (more recent period, source over copy,
+   formula chain over paste) and do not "fix" either unasked.
 
 ## Sensitive reviews
 
-Clinical records, payroll and individual compensation, customer-level data: answer at the
-level the user asked for and no lower. Inspect structure, formats, dependency chains and
-formulas as evidence, and do not echo restricted values into the chat unless the user
-needs that exact figure to act. If the question cannot be answered without exposing
-personal data, say what you can answer instead.
+Clinical records, payroll/compensation, customer-level data: answer at the level asked and
+no lower. Inspect structure, formats, dependency chains and formulas as evidence; do not
+echo restricted values unless the user needs that figure to act. If the question cannot be
+answered without exposing personal data, say what you can answer instead.
 
 ## Limits
 
-- Do not equate the live window with the saved file, and do not present a read-only
-  question as if you had verified the disk copy.
-- If a formula depends on external links, volatile functions (`NOW()`, `RAND()`) or a
-  pivot cache that has not been refreshed, say the number is provisional.
-- If the workbook is protect-structured or the sheet is protected, reads still work;
-  report the protection rather than working around it.
-- `#REF!`, `#DIV/0!` and friends in the cells are part of the answer, not noise: name the
-  cell, the formula and what it broke.
+- Do not equate the live window with the saved file, or present a read-only answer as
+  verified against disk.
+- External links, volatile functions (`NOW()`, `RAND()`) or an unrefreshed pivot cache make
+  the number provisional; say so.
+- Protected sheets: reads work; report the protection, do not work around it.
+- `#REF!`, `#DIV/0!` and friends are part of the answer: name the cell, the formula and what
+  it broke.

package/assets/skills/excel-live-control/style_guidelines.md

@@ -1,87 +1,79 @@
 # Style guidelines for a live sheet
 
-Style is subordinate to content and to the user's own file. Precedence, strongest first:
+Style is subordinate to content and the user's file. Precedence, strongest first:
 
-1. What the user asked for, in this conversation.
+1. What the user asked for in this conversation.
 2. The workbook's existing conventions — fonts, colours, borders, tab colours, number
    formats. Match them; do not impose a house style on someone else's document.
-3. The domain guidance for the kind of model (`domain_guidance/`).
+3. The domain guidance for the model (`domain_guidance/`).
 4. The defaults below.
 
-Look before you paint: `info` for tab colours and structure, `read_range` for the formats
-a neighbouring block already uses. Restyling a user's sheet because your defaults are
-tidier is a defect, not a service.
+Look before you paint: `info` for tab colours and structure, `read_range` for neighbouring
+formats. Restyling because your defaults are tidier is a defect, not a service.
 
 ## Defaults that are safe anywhere
 
-- **Font family**: one per workbook. If it has none, Helvetica Neue → Helvetica → Arial →
-  Aptos. **Two sizes**: 10 pt body, 14 pt title, 16 pt ceiling. Never introduce a third
-  family or a decorative size.
+- **Font**: one family per workbook. If it has none, Helvetica Neue → Helvetica → Arial →
+  Aptos. Two sizes: 10 pt body, 14 pt title, 16 pt ceiling. Never a third family or a
+  decorative size.
 - **Alignment**: text left, numbers right, headers centred horizontally and middle
-  vertically. Do not centre numbers to look neat; they lose their decimal alignment.
+  vertically. Never centre numbers — they lose decimal alignment.
 - **Headers**: bold, one rule under the last header row (`border: "outline"` on the header
-  block, or a bottom border on the row). No merged cells in working headers — merge only a
-  single spanning title, and prefer Center Across Selection for that.
-- **Inputs vs calculations**: an input cell the user is expected to type into gets a light
-  fill (`#FFF2CC` amber) and a thin border; calculated cells keep a plain fill. If the
-  whole block is inputs, one header note beats painting every cell.
-- **Gridlines**: a clean output or dashboard sheet hides them (`ActiveWindow.DisplayGridlines
-  = $false`, a view setting, not a cell format) and uses thin structural borders instead.
-  A working sheet keeps them.
+  block, or a bottom border on the row). No merged cells in working headers; merge only a
+  single spanning title, preferring Center Across Selection.
+- **Inputs vs calculations**: cells the user types into get a light fill (`#FFF2CC` amber)
+  and thin border; calculated cells stay plain. If the whole block is inputs, one header
+  note beats painting every cell.
+- **Gridlines**: a clean output or dashboard hides them
+  (`ActiveWindow.DisplayGridlines = $false`, a view setting, not a cell format) and uses
+  thin structural borders; a working sheet keeps them.
 - **Borders**: outline a block, hairline between header and body. No box around every cell,
-  no double lines, no thick decorative frames.
-- **Column widths**: set them once per block (`column_width` in `style_range`), not per
-  cell. Widen for the formatted value, then check with `read_range --display` for `###`.
-- **Conditional formatting**: bounded to the data range, one or two rules. Never a whole
-  column, never a rule that paints a user input cell.
-- **Freeze panes** are not a styling nicety; the tool cannot set them on a hidden window.
-  If scrolling is the complaint, say so and let the user freeze the row.
+  no double or thick decorative frames.
+- **Column widths**: once per block (`column_width` in `style_range`), not per cell; widen
+  for the formatted value, then check `###` with `read_range --display`.
+- **Conditional formatting**: bounded to the data range, one or two rules; never a whole
+  column, never paint a user input cell.
+- **Freeze panes** are a view setting, not styling. The tool cannot set them on a hidden
+  window; if scrolling is the complaint, say so and let the user freeze the row.
 
 ## Model layouts
 
-- Summary above detail, outputs before workings, assumptions grouped in one block rather
-  than scattered. A reader should be able to look at the top-left and understand the sheet.
-- One blank row at the top of a new output sheet, the title in an unfilled cell on the
-  left, a thin rule under it. No logo, no merged banner, no slogan.
-- Rows of commentary go to the right of the numbers, separated by one blank column; they
-  never sit between a label and its value.
-- Helper rows: italic, grouped under the block they serve, collapsed if the workbook
-  already uses grouping. Helper columns live outside the printed range or on a separate
-  helper sheet.
-- A case or scenario selector is a visible label plus a validated cell: `Case Selected:`
-  and the value on display. Do not hide the control in a defined name.
-- Section bands (a filled row spanning the table) get one outline around the whole
-  section, not per row.
-- Dark header fill with white text, or plain text with a rule. Pick one per workbook.
+- Summary above detail, outputs before workings, assumptions grouped in one block. The
+  top-left should explain the sheet.
+- New output sheet: one blank row at the top, title in an unfilled left cell, thin rule
+  under it. No logo, merged banner or slogan.
+- Commentary goes right of the numbers, separated by one blank column; never between a
+  label and its value.
+- Helper rows: italic, grouped under their block, collapsed if the workbook already groups.
+  Helper columns outside the print range or on a separate helper sheet.
+- Scenario selector: a visible label plus a validated cell (`Case Selected:` and the value);
+  never hidden in a defined name.
+- Section bands: one outline around the whole section, not per row.
+- Dark header fill with white text, or plain with a rule — one per workbook.
 
 ## Finance conventions
 
-These are long-standing reader expectations in financial models; a reviewer notices when
-they are violated.
-
-- **Colour encodes provenance.** Blue font for editable hard-coded inputs, black for
-  formulas on the same sheet, green for links to another sheet, red for links to an
-  external workbook. Results on an output view stay black or the brand dark colour.
-- **Number formats**: `#,##0` for amounts, `#,##0.00` for per-share and price data,
-  `0.0%` for rates, `( )` for negatives and `-` for zero in accounting views
-  (`#,##0;(#,##0);"-"`). Currency symbol on the first monetary row and on totals, not on
-  every row.
-- **Indent formats** (`  @` for text labels, `_(`-style spacing) map a hierarchy without
-  empty columns.
-- **Totals** sit flush left in the label column, bold, with the rule above them. A total
-  that is a hard number rather than a formula is a finding, not a style choice.
-- **Period labels** follow `mmm-yy`, `d-mmm`, `yyyy`, `Q#:YY`, `FY:YY` as the workbook
-  already does. A date column has one format down its whole length.
-- **Actuals vs forecast**: the change of basis is visible — a divide, a different fill, or
-  a label — and never inferred from a colour alone.
-- A model that needs a gutter between the row labels and the numbers gets columns A:B
-  reserved for it. Do not retrofit a gutter onto a sheet that does not have one.
+- **Colour = provenance**: blue font for hard-coded inputs, black for same-sheet formulas,
+  green for links to another sheet, red for links to an external workbook. Output views
+  stay black or brand dark.
+- **Number formats**: `#,##0` amounts, `#,##0.00` per-share/price, `0.0%` rates,
+  `#,##0;(#,##0);"-"` for accounting (parentheses for negatives, dash for zero). Currency
+  symbol on the first monetary row and on totals, not every row.
+- **Indent formats** (`  @` for text labels, `_(`-style spacing) map hierarchy without empty
+  columns.
+- **Totals** flush left in the label column, bold, rule above. A hard-number total instead
+  of a formula is a finding.
+- **Period labels** follow `mmm-yy`, `d-mmm`, `yyyy`, `Q#:YY`, `FY:YY` as the workbook does;
+  one date format down a column.
+- **Actuals vs forecast**: a visible change of basis (divide, fill, label), never colour
+  alone.
+- A needed gutter between row labels and numbers gets columns A:B reserved; do not retrofit
+  one onto a sheet that lacks it.
 
 ## Warning colour, used sparingly
 
 - Input that must be refreshed: amber fill (`#FFF2CC`), normal font.
-- Critical error or failed check: light red fill (`#FFC7CE`) plus bold red text
-  (`#9C0006`).
-- Passing checks: neutral. A green wash over every PASS makes the one red row invisible.
-- Never encode a value only in colour — a reader with a monochrome printout, or a colour
-  vision deficiency, must still see the meaning. Put the flag in a cell.
+- Critical error or failed check: light red fill (`#FFC7CE`) plus bold red text (`#9C0006`).
+- Passing checks: neutral. A green wash over every PASS hides the one red row.
+- Never encode meaning in colour alone; put the flag in a cell so a monochrome printout or
+  colour-vision deficiency still reads it.

package/assets/skills/excel-live-control/workflows/create_workflows.md

@@ -1,44 +1,39 @@
 # Creating content in a live workbook
 
-The user is watching, so the order you do things in is visible. Plan on paper first, then
-make a small number of writes.
+The user sees every step. Plan on paper first, then write in a few batches.
 
-## 1. Decide what is actually being created
+## 1. Decide what is being created
 
-Before you write a cell, you should be able to answer:
+Answer these before writing a cell:
 
-- **Who reads it, and what decision does it support?** A one-page summary for a committee
-  and a working model for an analyst are different sheets.
-- **What are the outputs?** Name them. Each output is a number with a label, a period and
-  a unit.
-- **What are the inputs?** Name them, with their sources. Inputs nobody will update are
+- **Who reads it, and what decision does it support?** A committee summary and an analyst's
+  working model are different sheets.
+- **What are the outputs?** Name each one: a number with a label, a period and a unit.
+- **What are the inputs?** Name them with their sources. Inputs nobody updates are
   decoration.
-- **What is calculated in between?** The steps between input and output are what a reviewer
-  audits; if you cannot name them, the model is not designed yet.
-- **What would make it wrong?** A check or a reconciliation, even one line: totals tie,
-  parts sum to the whole, cash ends at the right balance.
+- **What is calculated in between?** A reviewer audits these steps; if you cannot name them,
+  the model is not designed yet.
+- **What would make it wrong?** At least one check: totals tie, parts sum to the whole, cash
+  ends at the right balance.
 
-If the request leaves two of these open, ask one short question rather than guessing —
-a live edit is expensive to unpick.
+If two are still open, ask one short question — a live edit is expensive to unpick.
 
 ## 2. Where it goes
 
-- Roles, not a fixed tab count: inputs, assumptions, calculations, outputs. A small sheet
-  can carry several roles; a large model separates them.
-- Outputs at the left of the tab strip, workings in the middle, inputs at the right; a
-  check/audit tab last if the model warrants one. Do not add a Checks tab to a simple
-  sheet — a labelled verification row is enough.
-- Keep inputs next to the calculations they feed when the model is small; move them to a
-  dedicated input sheet only when more than one sheet consumes them.
+- Organise by role, not tab count: inputs, assumptions, calculations, outputs. Small sheets
+  merge roles; large models separate them.
+- Outputs left of the tab strip, workings middle, inputs right; a check/audit tab last if
+  warranted.
+- No separate Checks tab on a simple sheet — a labelled verification row is enough.
+- Keep inputs beside their calculations; use a dedicated input sheet once several sheets
+  consume them.
 - Calculate once, link everywhere else. Two cells computing the same number is a future
   disagreement.
-- Insights (a short comment or a highlighted conclusion) go next to the result they
-  explain, not in a separate "insights" area.
+- Put insights next to the result they explain, never in a separate area.
 
-**Adding a tab is not an operation of this skill.** The tool writes into sheets that
-already exist. If the job needs a new sheet, ask the user to insert one (Right-click a tab
-→ Insert), or use the file route in `../../office-spreadsheets/SKILL.md` and tell them to
-reopen. Do not repurpose an existing sheet as scratch space.
+**This skill cannot add a tab** — it writes into existing sheets. Ask the user to insert one
+(right-click a tab → Insert), or use the file route in `../../office-spreadsheets/SKILL.md`
+and tell them to reopen. Never repurpose a sheet as scratch space.
 
 ## 3. Write it
 
@@ -51,28 +46,26 @@ recalc
 read_range --sheet "Inputs" --range B3:D9 --formulas
 ```
 
-- One `write_range` per block with its real shape. The array is rows × columns; do not pad
-  with empty strings to make it rectangular — use `null` for a genuinely empty cell.
-- Write the labels and the units with the numbers. A block of bare numbers is not done.
-- Default formats in the write step, not afterwards: `number_format` in `style_range`
-  applied to the whole block is one call and keeps every cell consistent.
-- Formulas as text starting with `=`, absolute where they must stay put (`$C$4`), relative
-  where the fill should walk (`D5`). Test one cell before filling a column.
-- If the sheet already has content, check the used range first and write beside it, not
-  over it.
+- One `write_range` per block, in its real shape (rows × columns). No empty-string padding;
+  use `null` for an empty cell.
+- Write labels and units with the numbers. Bare numbers are not done.
+- Apply `number_format` in one `style_range` over the block, not cell by cell.
+- Formulas start with `=`: absolute where fixed (`$C$4`), relative where the fill walks
+  (`D5`). Test one cell before filling.
+- If the sheet has content, check the used range and write beside it, not over it.
 
 ## 4. Check it, then say what you did
 
-- `read_range --formulas` over everything you wrote; `errors` must be empty.
-- `recalc`, then read the outputs again — a formula that never calculated proves nothing.
-- `info` if you added tables or charts, to confirm they landed on the sheet you meant.
-- Report the ranges and the state of the document (unsaved, or saved where). See the
-  Delivery section of `../SKILL.md`.
+- `read_range --formulas` over everything written; `errors` must be empty.
+- `recalc`, then re-read the outputs — an uncalculated formula proves nothing.
+- `info` after adding tables or charts, to confirm the target sheet.
+- Report the ranges and document state (unsaved, or saved where). See Delivery in
+  `../SKILL.md`.
 
 ## 5. Sizing and layout
 
-- Set column widths after the content exists, from the widest formatted value, then
-  re-read with `--display` to catch `###`.
-- Wrap long text labels instead of widening a column to half the screen.
-- Helper calculations go in their own block or sheet, labelled, not buried between two
-  output rows.
+- Set widths after content, sized to the widest formatted value; check `###` with
+  `--display`.
+- Wrap long labels instead of widening a column to half the screen.
+- Give helper calculations their own labelled block or sheet, never a row buried between
+  outputs.

package/assets/skills/excel-live-control/workflows/edit_workflows.md

@@ -1,47 +1,41 @@
 # Editing a workbook the user already built
 
-The existing workbook is the reference. Its structure, formula style, formats, labels and
-navigation are what the user expects to keep seeing; your job is to make one change that
-looks like it was always there.
+The existing workbook is the reference. Keep its structure, formula style, formats, labels
+and navigation; make one change that looks native.
 
 ## Read the ground first
 
-Nothing below works without this step, and it is cheap:
+Cheap, and nothing below works without it:
 
-1. `info` — workbook name and path, `saved` flag (unsaved work in progress!), sheets,
-   used ranges, tables, charts, pivots, protection.
-2. `read_range --formulas` over the block you are about to touch **and its neighbours**.
-   You need to know the pattern a formula follows before you extend it.
-3. `read_range --display` when the change is formatting — it tells you the current number
-   format's effect, not just the stored value.
-4. Read the labels around the block: period, unit, actual/forecast. A number is only
-   meaningful with its label, and your new row must match the surrounding convention.
+1. `info` — workbook name/path, `saved` flag (unsaved work!), sheets, used ranges, tables,
+   charts, pivots, protection.
+2. `read_range --formulas` over the target block **and its neighbours**. Know the formula
+   pattern before extending it.
+3. `read_range --display` when changing formatting: it shows the format's effect, not the
+   stored value.
+4. Read the surrounding labels: period, unit, actual/forecast. Match the convention.
 
-If the target block holds values you cannot explain from the request, stop and ask. On a
-live document, "I thought it was empty" is how an analyst's afternoon disappears.
+If the block holds values you cannot explain from the request, stop and ask.
 
 ## Rules of the edit
 
-- **Change the cells the request names, and the formulas those cells feed.** A changed
-  input propagates on its own; do not hand-edit downstream totals.
-- **Do not add, remove, rename, reorder or split sheets/tabs** unless the request says so
-  or the change genuinely cannot be expressed otherwise (a new output with no home).
+- **Change the cells the request names and the formulas those cells feed.** A changed input
+  propagates; do not hand-edit downstream totals.
+- **Do not add, remove, rename, reorder or split sheets** unless requested, or the change
+  cannot otherwise be expressed (a new output with no home).
 - **Preserve everything you did not create**: other sheets, formulas, named ranges,
-  comments, protection, hidden or grouped rows, freeze panes (user-set), native tables and
-  their structured references, pivot sources, shared formulas, filters, external links,
+  comments, protection, hidden/grouped rows, user freeze panes, native tables and their
+  structured references, pivot sources, shared formulas, filters, external links,
   `INDIRECT` routing, calculation settings.
-- **Never flatten formulas to values.** Not to "simplify", not to "fix" a display problem.
-- **Extend, do not replace.** When a row or column is added to a block that has a table,
-  conditional format or chart on it, extend the object to cover the new cells instead of
-  building a parallel object beside it. `ListObject.Resize` and the chart's
-  `SetSourceData` are the tools.
-- **Small visual fixes stay local.** Widen the one column that clips. Do not autofit the
-  sheet, do not restyle a header because it is not your default style.
-- **Match the existing formula conventions** — anchoring style, `SUMIFS` vs `SUMPRODUCT`,
-  rounding, the workbook's error handling. A locally "better" formula that reads
-  differently is a maintenance cost the user did not ask for.
-- **Pre-existing errors are not yours to fix.** Report them with the cell and the formula
-  and ask. Silently repairing a `#REF!` can change a number the user relies on.
+- **Never flatten formulas to values** — not to "simplify", not to "fix" a display problem.
+- **Extend, do not replace.** A row or column added under a table, conditional format or
+  chart extends that object (`ListObject.Resize`, `SetSourceData`), never a parallel one.
+- **Keep visual fixes local.** Widen the one clipped column. No sheet-wide autofit, no
+  restyle because it is not your default.
+- **Match formula conventions**: anchoring style, `SUMIFS` vs `SUMPRODUCT`, rounding, error
+  handling. A "better" formula that reads differently costs maintenance.
+- **Pre-existing errors are not yours to fix.** Report the cell, its formula and ask;
+  silently repairing `#REF!` can change a number the user relies on.
 
 ## Doing it
 
@@ -54,19 +48,17 @@ recalc
 read_range --sheet "Build" --range D5:G13 --formulas     # prove it
 ```
 
-- Keep writes to the named rectangle; `--clear` only on a range whose previous contents
-  you have read and can restore.
-- Style by copying the neighbouring block's codes: read a cell you want to match, mirror
-  its `number_format`, and apply it to the new cells. Do not invent a new format for one
-  row.
-- If a formula in the new cell must differ from the pattern (a different anchor, a
-  one-off), say why in the reply — a reviewer will find it.
+- Keep writes to the named rectangle. `--clear` only a range whose contents you have read
+  and can restore.
+- Copy style codes from the neighbouring block: read a matching cell, mirror its
+  `number_format`, apply to the new cells. Do not invent a format for one row.
+- A formula that must differ from the pattern (different anchor, one-off): say why in the
+  reply.
 
 ## When you are done
 
-- `read_range --formulas` over every cell you changed and its immediate neighbours.
-- `recalc` after formulas, then re-read the outputs that depend on them.
-- `info` if tables, charts or pivots were extended, to confirm the objects still exist and
-  cover the new cells.
-- Report: sheet, exact ranges, cell counts, and what the document's saved state is. If the
-  edit touched a formula graph, say which outputs were affected.
+- `read_range --formulas` over every changed cell and its neighbours.
+- `recalc` after formulas, then re-read dependents.
+- `info` if tables, charts or pivots were extended, to confirm coverage of the new cells.
+- Report sheet, exact ranges, cell counts and saved state. If the formula graph changed,
+  name the affected outputs.