Add deletion-test coverage proving hacktools inventory earns its depth

[mswell]

Parent

#32

What to build

Add deletion-test coverage proving the hacktools inventory earns its depth. The tests should fail if install behavior is re-spread across the installer script or if plan/apply behavior stops crossing the hacktools inventory seam.

This slice should lock in the domain boundary: one hacktools inventory model drives plan, apply, skip decisions, path expansion, repository behavior, wordlists, and post-install actions.

Acceptance criteria

• Tests cover plan and apply behavior for ProjectDiscovery tools, generic Go tools, Python tools, repositories, wordlists, and post-install actions through the hacktools inventory interface.
• Tests prove dry-run and apply behavior share the same inventory model rather than separate historical expectations.
• Tests catch stale expectations such as obsolete installer mechanisms or bypassed inventory records.
• Tests would fail if the hacktools inventory module were deleted or reduced to a shallow rename of installer loops.
• The default test suite does not run live network downloads, repository clones, or real tool installations.

Blocked by

• Collapse install_hacktools.sh into a thin hacktools inventory caller #59