livespec-prune-history

Explicitly invoke /skill:livespec-prune-history in the pi session or directly ask to prune the livespec history. The skill resolves the livespec core root, reads core's prune-history prose, and runs the prune_history CLI named in the project's .livespec.jsonc config.

Model-driven invocation is disabled via the disable-model-invocation frontmatter, so pi hides the skill from the system prompt. Only an explicit /skill:livespec-prune-history invocation or a direct user request to prune history triggers it, never a generic mention of history.

Yes. The governed project's .livespec.jsonc names the CLI under spec_clis.prune_history as an argv array. If absent, the skill falls back to core's reference default: python3 <core-root>/scripts/bin/prune_history.py.

Pi's project-trust gate silently ignores project-local packages in non-interactive mode until a trust decision exists, so core-root resolution fails. The skill stops and surfaces the resolver's diagnostic verbatim rather than improvising a path or running installs.

The Driver's tool_call footgun-guard extension (extensions/livespec-footgun-guard.ts) must be loaded before any mutating operation. If pi reports the package's extensions are not loaded, the skill stops instead of proceeding unguarded.