## §OIP SYSTEM ARTICLE — OUTSTANDING (1 operations)
A generated article for one OIP shelf. It lists every operation in this API/CLI/MCP/device/model/core subsystem, links each leaf article, and gives the ledger path for proof.

### Read Order
- scan operations
- open a leaf doc
- run via run_now or POST /api/dispatch
- open receipt
- repair/replay if needed

### Operations
- **OUTSTANDING_SYNC_EMAIL** — Build one unified outstanding-sync report and email it: every open GitHub issue, open/running task inventory, 
  when: The owner asks to sync GitHub issues, tasks, Kimi, model work, outstanding work, or wants everything sent by email.
  args: mode. blank/force = send email + short iMessage notice. dry = collect only, no send.
  doc: https://miscsubjects.com/api/dispatch?key=OUTSTANDING_SYNC_EMAIL&format=markdown
  run: https://miscsubjects.com/api/dispatch?invoke=OUTSTANDING_SYNC_EMAIL&body=force&share=<TOKEN>
  history: https://miscsubjects.com/api/invocations?object_id=OUTSTANDING_SYNC_EMAIL

### Troubleshooting
- If a row's example has placeholders, replace only the placeholder values and preserve separators.
- If a call fails, open its receipt and repair it with POST /api/dispatch {key, body, repairs:'inv_ID'}.
- If token scope denies this system, ask the owner for a row:/rows:/pfx: token scoped to the exact operation set.

Back to the tree: https://miscsubjects.com/api/dispatch?map=1&format=markdown