Remove incidental tool coupling from artifacts that claim to outlive the stack that wrote them.

Goal

A durable artifact should stay true and actionable when the agent, harness, operating system, vendor, model, or toolchain changes. detool finds stack-specific nouns in portable content and rewrites them to the underlying mechanism without deleting the action they enabled.

The point is portability, not vagueness. A reader should still know what to inspect, run, measure, compare, or verify after the rewrite.

Workflow

Read the target artifact end to end.
Role before edit: classify the whole artifact, or each section if mixed, as durable/portable content, provenance/operational record, or a claim about a named tool.
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 stated as timeless truth.
Mechanism not euphemism: replace each durable-content hit with the neutral mechanism that preserves the action. If neutral wording would lose the action, keep the concrete detail as an example of the mechanism instead of pretending it generalizes.
Keep provenance and operational content concrete. Build records, capsules, benchmark logs, install guides, runbooks, tool-targeted how-tos, command transcripts, and exact reproduction steps are supposed to name the stack that produced them.
Keep comparative and tool-subject claims concrete. If the sentence is about a named tool, vendor, model, bug, prior-art source, or measured limit, the name is the subject, not incidental coupling.
Re-read as a reader on a different stack: the artifact should still be true, portable, and executable where it promised action.
Report what was neutralized, what was deliberately kept, and the role judgment behind each keep.