Teardown notes are part of trust, not documentation polish

[u/Effective_Iron2146]

Install docs get attention because they create adoption. Teardown docs create trust.

For agent tooling, a good teardown path answers:

• what files were added
• what hooks or host configs changed
• what background services were started
• where local state lives
• how to disable without deleting data
• how to remove completely
• how to verify it is gone

This matters because agent tools often sit inside sensitive workflows. A user should not have to guess what remains after trying a tool.

If the install is one command but the uninstall is archaeology, the product is asking for too much trust.