wiki-history-ingest

1# Unified History Ingest Router
2 
3This is a thin router for **history sources only**. It does not replace `wiki-ingest` for documents.
4 
5## Subcommands
6 
7If the user invokes `/wiki-history-ingest <target>` (or equivalent text command), dispatch directly:
8 
9| Subcommand | Route To |
10|---|---|
11| `claude` | `claude-history-ingest` |
12| `copilot` | `copilot-history-ingest` |
13| `codex` | `codex-history-ingest` |
14| `hermes` | `hermes-history-ingest` |
15| `openclaw` | `openclaw-history-ingest` |
16| `pi` | `pi-history-ingest` |
17| `auto` | infer from context using rules below |
18 
19## Routing Rules
20 
211. If the user explicitly says `claude`, `copilot`, `codex`, `hermes`, `openclaw`, or `pi`, route directly.
222. If the user provides a path/source:
23   - `~/.claude` or Claude memory/session JSONL artifacts -> `claude-history-ingest`
24   - `~/.copilot`, `session-store.db`, VS Code copilot-chat transcripts -> `copilot-history-ingest`
25   - `~/.codex` or rollout/session index artifacts -> `codex-history-ingest`
26   - `~/.hermes` or Hermes memories/session artifacts -> `hermes-history-ingest`
27   - `~/.openclaw` or OpenClaw MEMORY.md/session JSONL artifacts -> `openclaw-history-ingest`
28   - `~/.pi/agent/sessions` or Pi session JSONL artifacts -> `pi-history-ingest`
293. If ambiguous, ask one short clarification:
30   - "Should I ingest `claude`, `copilot`, `codex`, `hermes`, `openclaw`, or `pi` history?"
31 
32## Execution Contract
33 
34- After routing, execute the destination skill's workflow exactly.
35…