This is the product, not a side plugin. It is the writer socket of KRouter (same tree as extras/dsh). Self-evolution: seal yesterday’s log, distill, write provisional the same day when the five gates pass.
install.sh installs the timer (KROUTER_NO_TIMER=1 skips it); the one-line install asks the host first (lamp: running once installed). API key first: lock that provider’s flagship model, then distill and promote. No key: the user’s Claudian-class CLI subscription does the same work. lamp: unused = you turned the timer off.
The job auto-detects the CLI each run. Keys come from the vault page, ~/.dsh-krouter-keys.env (what install.sh writes), or the job environment — the vault page wins. Do not commit a live key.
| File | Role |
|---|---|
check.sh |
Proves writer files exist and reads lamp:. Default running. Does not fire the job. |
run.sh |
OS job entry. Calls resolve.py --exec, then nightly.py (the five nightly steps, outcomes on 夜间维护.md and the health page). Skips distill if the key and CLI login are both missing. --dry-run lists what would be sent and written. |
run.py |
Same as run.sh for Windows (no /bin/sh). scripts/install_windows_task.ps1 registers it as a daily task. |
resolve.py |
The one probe engine: collects keys (process env, ~/.dsh-krouter-keys.env, vault page — page wins), detects a logged-in CLI, otherwise runs the bundled API writer. Never prints secrets. |
api_writer.py |
Distill with only an *_API_KEY. No grok / Codex / claude required. |
wire_keys.py |
Installer front end over resolve.py: detect a logged-in CLI (--detect), probe keys, keep the live ones in ~/.dsh-krouter-keys.env. Never copies auth.json, never writes the vault. |
patch_health.py |
Updates health fields (present / missing / dead / unknown). Never the secret. |
PROMPT.md |
Writer contract. Passed to the detected CLI. |
launchd.example.plist |
macOS example. OBSIDIAN_VAULT, KROUTER_ROUTER, HOME, PATH (includes ~/.grok/bin). No key slot. |
cron.example |
cron example. Same. install.sh writes one marked crontab line on Linux without systemd. |
systemd/ |
systemd user service + timer that install.sh installs on Linux. |
dsh plugin add is a mount, not this writer. It does not replace the timer.
export OBSIDIAN_VAULT=/path/to/KRouter/template
./extras/host-daily-evolution/check.sh
./scripts/first_run.sh runs that check. Pass means the writer files exist, the key page ships placeholders only, and the lamp is running (default) or unused (you turned it off). CI does not fire the daily job.
OBSIDIAN_VAULT to your vault root (copy template/ there first).~/.dsh-krouter-keys.env; a key pasted on 90 系统文件/自动化/自进化钥匙.md moves there on the next run. The writer locks the flagship model. No key: already-logged-in Claudian-class CLI (grok / official Codex / claude / …). Distill and two-step promotion both run. Do not use a PATH-level agent.provisional the same day (no ask). Do not auto-promote to active.90 系统文件/canonical_sources.psv). The API writer refuses that path; the host ticks rows in 别名候选.md.scripts/uninstall.sh removes the schedule (launchd / systemd / crontab line); on Windows install_windows_task.ps1 -Uninstall.Paste a live *_API_KEY on the vault page, or log in a coding CLI. Either lane distills and promotes. API lane auto-locks the flagship. Subscription lane is the Claudian channel (spawn the logged-in harness).