09-core-use-office-cli-for-office-fileslisted

# Use OfficeCLI for Office Files (CORE) **What it is:** [iOfficeAI/OfficeCLI](https://github.com/iOfficeAI/OfficeCLI) — a single self-contained binary (`officecli`) that reads, edits, and renders `.docx` / `.xlsx` / `.pptx` with **no Microsoft Office install required**. It exposes an MCP stdio server so the agent drives Office files as precise tool calls. Registered in the provisioning-repos `GMCP` (server name `officecli`, launched via `officecli mcp`), so it syncs to every CLI agent via `agent-provisioning-toolkit/sync`. ## TIER-C RULE — pick the lane honestly (read vs. edit) OfficeCLI is **not** mandatory for every byte you ever pull out of an Office file. Two lanes: 1. **Cheap one-off TEXT extraction** (you just need the words, formatting is irrelevant — e.g. dump a .docx to plain text to grep it): a lighter/faster parser is fine. Bundle size and speed win here. OfficeCLI's own `view <file> text` mode also does this if it's already in play — but you are not forced onto it for trivial reads. 2. **Anything structural or any WRITE** — reading with formatting/tables/layout intact, inspecting structure, finding issues, rendering, OR creating/modifying/formatting a file you will hand back to a human → **use OfficeCLI.** This is the "work on it locally, human-like" case: OfficeCLI preserves structure, does round-trip-safe edits, and can render to HTML/PNG for a look→fix loop. A raw-XML hand-edit or a basic text dumper here loses formatting and corrupts f