Apply repository tools through hacktools inventory with predictable update behavior

[mswell]

Parent

#32

What to build

Move repository tool clone/update, dependency install, setup/build handling, and failure behavior into the hacktools inventory apply behavior. Repository tools should have explicit semantics for existing clones, fresh clones, dependency steps, build steps, and partial failures.

This slice should preserve the current repository tool set and current broad behavior, while making failures easier to diagnose and test.

Acceptance criteria

• Repository records in the hacktools inventory include local directory names and GitHub source URLs.
• Apply behavior pulls existing Git repositories and clones missing repositories through a repository adapter.
• Requirements, setup, and Makefile dependency/build steps are represented through command execution adapters.
• Clone, pull, dependency, and build failures have consistent skip/continue behavior and useful diagnostics.
• Existing special behavior for gf and Gf-Patterns templates is preserved or represented as a named post-install action if that seam is cleaner.
• Tests use fake repository and command adapters instead of real clones or installs.

Blocked by

• Deepen hacktools inventory plan records into typed install actions #51
• Add fakeable host adapters for hacktools inventory apply behavior #53