detool

1Remove incidental tool coupling from artifacts meant to outlive the stack that wrote them.
2 
3## Goal
4 
5Keep durable artifacts true and actionable across changes of agent, harness, operating system, vendor, model, or toolchain. `detool` replaces incidental stack nouns in portable content with the underlying mechanism, preserving the action they enabled.
6 
7The reader must still know what to inspect, run, measure, compare, or verify.
8 
9## Workflow
10 
111. Read the target artifact end to end.
122. **Role before edit**: classify the artifact, or each section if mixed, as durable/portable content, provenance/operational record, or a claim about a named tool.
133. Sweep durable content for incidental coupling: harness paths, vendor CLIs and flags, model or product brands used as mechanisms, tool-specific environment variables, quotas, UI steps, cache homes, session files, and version-pinned behavior presented as timeless.
144. **Mechanism not euphemism**: replace each hit with a neutral mechanism that preserves the action. If neutral wording would lose the action, keep the concrete detail as an example rather than claim it generalizes.
155. Keep provenance and operations concrete: build records, capsules, benchmark logs, install guides, runbooks, tool-targeted how-tos, command transcripts, and exact reproduction steps must name their stack.
16…