Git Operations and Project identity locality

[BramVR]

Parent

#70

What to build

Build a thin vertical slice where current scan, status, hydrate, and agent handoff paths use one Git Operations module for remote inspection, Git command execution, normalized Project identity support, clone URL cleanup, and redaction. The user-visible behavior should stay the same, but Git behavior should stop being duplicated across Project Registry, Readiness, Agent Prep, Policy, and State Store migration paths.

Acceptance criteria

• Existing scan/add/status/hydrate/agent prepare behavior remains user-visible compatible.
• Git Operations has process and fake/test adapters.
• Normalized remote handling, clone URL cleanup, and credential redaction are exercised through one shared module.
• Existing unit and e2e tests pass, with added coverage for redaction and Git error normalization.

Blocked by

None - can start immediately