Repository navigation
mod: cache-vs-repo version status and stale-skill toast #442
Description
From #323 follow-up research. One additive observer in hooks/mod/cost-ledger.ts (mh may ship one module).
On session.start, compare the cached plugin version ($.plugin.root plugin.json) with the repo manifest and show the result via $.ui.status. On skill.prompt, if the repo SKILL.md differs from the cached copy, $.ui.toast that a cached copy is running.
Why: docs/reference/repo-gotchas.md "Which mh copy runs" records the wrong probe twice, plus a false "fix confirmed" through Skill().
Acceptance:
- Never denies, asks, rewrites or throws (observer contract in
docs/reference/cost-ledger-module.md). - Modules off: no behaviour change.
- Unit tests plus one live
claude -pprobe note in the doc. - Bump both manifests.
Activity
Merge pull request #446 from wasikarn/claude/mod-version-status-442-444
wasikarn commentedon Oct 4, 2026
Done in #446 (merged). On session.start in an mh checkout, the module shows the cached vs repo version through $.ui.status. On skill.prompt, it toasts once per skill whose repo SKILL.md differs from the cached copy. Unit tests: 14 pass under
claude plugin test .. Not done: the manifest bump (the operator bumps separately) and the liveclaude -pprobe (a subagent cannot start nested sessions). The probe steps are in docs/reference/cost-ledger-module.md.