Update to DataFlowr

{
  "description": "Run a month-end close on an Exact Online administration by delegating to DataFlowr's hosted closing agent, then poll it, report its findings and record accept/dismiss decisions. Use when the user asks to close a period, run close checks, review a period for irregularities, or asks what is still open before closing the books.",
  "included_files": [],
  "name": "month-end-close",
  "skill_md_contents": "---\nname: month-end-close\ndescription: Run a month-end close on an Exact Online administration by delegating to DataFlowr's hosted closing agent, then poll it, report its findings and record accept/dismiss decisions. Use when the user asks to close a period, run close checks, review a period for irregularities, or asks what is still open before closing the books.\n---\n\n# Month-end close\n\n## Overview\n\nDo **not** assemble a close out of individual ledger queries. DataFlowr hosts a\nclosing agent that runs a deterministic check battery and a ledger-wide scan for\nirregularities against one shared context. Delegate to it and report what it\nfinds.\n\nFour tools: `closing_agent` starts or continues a close, `closing_agent_status`\npolls it, `closing_agent_report` returns the full picture, and\n`closing_agent_decide` records a human decision on a finding.\n\n## Steps\n\n**1 — Resolve the division and the period.**\nCall `exact_online_divisions` first (see the `dataflowr-erp` skill). The period\nis a financial year and period (`FinYear`, `FinPeriod`), not a calendar month.\nIf the user did not name one, the agent defaults to the last closed period —\nsay which one you used.\n\n**2 — Start the close.**\nCall `closing_agent` with the division and the period. It returns a short\ncorrelation key (`close-XXXXXX`). Keep it: every follow-up call needs it.\n\nAn ordinary close evaluates that one period. Only when the user asks for a\nquarter or a whole financial year to be swept, add `period_from` (the first\nperiod of the range, same financial year): the line-level checks and the\nledger scan then evaluate every listed period from `period_from` through\n`period`, one transaction read per period, while balance checks still read\nthe closing balance through `period`. Say which periods were evaluated when\nyou report. Never widen the range on your own.\n\nThe check battery and the ledger scan both start on their own. Do not try to\ntrigger them.\n\n**3 — Poll while it works.**\nA close that outruns the synchronous budget comes back as `running`. Poll\n`closing_agent_status` with the correlation key rather than starting a second\nclose — a duplicate start answers `CLOSING_RUN_IN_PROGRESS`.\n\nStatus carries intermediate results: the checks report so far and the findings\nstream. Pass the `next_cursor` back as `since` to get only what is new. Narrate\nprogress from it instead of going silent.\n\n**4 — Report.**\nWhen the run is terminal, call `closing_agent_report` for the full picture and\nsummarise it: the verdict first, then findings by severity, then what was\ndecided already. Findings come from three sources — deterministic checks, the\nledger scan, and the agent's own judgment — and the report labels them; keep\nthat labelling, it tells the user how much to trust each one.\n\nWatch the scan's completeness state. Only a **complete** scan lets silence mean\n\"nothing found\"; anything else means \"not looked at yet\", and you must say so.\n\n**5 — Record decisions.**\nWhen the user accepts or dismisses a finding, call `closing_agent_decide` with\nits `finding_key` and a short note. Decisions persist per close period and\nsurvive re-runs, so re-running is a way to *prove* something was resolved rather\nthan to clear the slate.\n\n## Hard stops\n\n- No division, or a period the administration does not have → ask, do not guess.\n- The run failed or stalled → report that plainly with the error the tool\n  returned. Do not paper over it with a partial summary.\n- The close proposes a correction booking → it needs explicit approval. Present\n  the entry in full and wait; never approve on the user's behalf.\n"
}