## §OIP SYSTEM ARTICLE — REPO (2 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
- **REPO_SNAPSHOT** — Read the FULL repo snapshot from KV: {sha, ts, byte_count, content} — content is ~310KB and floods the next tu
  when: you need to repo snapshot
  args: none
  doc: https://miscsubjects.com/api/dispatch?key=REPO_SNAPSHOT&format=markdown
  run: https://miscsubjects.com/api/dispatch?invoke=REPO_SNAPSHOT&share=<TOKEN>
  history: https://miscsubjects.com/api/invocations?object_id=REPO_SNAPSHOT
- **REPO_ABSORB** — 
  doc: https://miscsubjects.com/api/dispatch?key=REPO_ABSORB&format=markdown
  run: https://miscsubjects.com/api/dispatch?invoke=REPO_ABSORB&body=%3Carg1%3E&share=<TOKEN>
  history: https://miscsubjects.com/api/invocations?object_id=REPO_ABSORB

### 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