Reconcile CrossRepoActions with the ktsu repo branch

[matt-edmondson]

c:/dev/ktsu-dev/CrossRepoActions is a standalone CLI that batches operations across many git repos and .NET solutions: DiscoverRepositories, BuildAndTest, GitPull, UpdatePackages. KtsuTools already has a repo branch with discover, build, pull, update-packages — there is heavy overlap.

What to figure out

1. Was KtsuTools.Repo ported from CrossRepoActions or written fresh?
2. Which CrossRepoActions features didn't make it across? Documented features include:
   • Interactive menu mode (no flags → menu).
   • Parallel build/test execution.
   • PowerShell-Core-driven steps.
3. Should CrossRepoActions be archived once parity is reached?

Acceptance

• A short audit comment on this issue listing each CrossRepoActions feature and whether it exists in KtsuTools.Repo.
• Each missing feature is either filed as a follow-up issue or implemented.
• A decision recorded on whether to archive CrossRepoActions.

[matt-edmondson]

Audit: CrossRepoActions features vs KtsuTools.Repo

I can't reach the ktsu-dev/CrossRepoActions source from this scope (restricted to ktsu-dev/ktsutools), so the comparison below uses the feature list documented in the issue body against the current KtsuTools.Repo implementation.

Documented features

CrossRepoActions feature	KtsuTools.Repo today	Notes
DiscoverRepositories	✅ repo discover	RepoService.DiscoverRepositoriesAsync recursively walks for .git dirs and stops at the first one (no nested-repo recursion).
BuildAndTest	⚠️ partial	repo build runs dotnet build then dotnet test per solution, sequentially.
GitPull	✅ repo pull	Runs git pull --all --autostash and surfaces error/conflict lines.
UpdatePackages	✅ repo update-packages	Walks csprojs, calls dotnet list package --outdated --format json, restores.
Interactive menu (no flags → menu)	❌	Program.cs registers the tool as Spectre.Console.Cli only; running ktsu repo with no args prints help.
Parallel build/test execution	❌ dead flag	RepoBuildCommand.cs:25-27 exposes --parallel, but RepoService.BuildAndTestAsync discards it (_ = parallel; at RepoService.cs:91). The loop at RepoService.cs:113 is sequential. Same shape as the --batch issue called out in #2.
PowerShell-Core-driven steps	❌	Everything goes through IProcessService.RunAsync (direct dotnet/git invocations). No pwsh dependency.

Recommendation

1. Wire up --parallel — small follow-up: replace the foreach with Parallel.ForEachAsync (or Task.WhenAll with a SemaphoreSlim) and route progress writes through a lock so the Spectre output doesn't tear. File as a sub-issue.
2. Skip the interactive menu and pwsh steps — these are UX/runtime choices that conflict with the rest of the KtsuTools surface (everything else is flag-driven, no pwsh). Document them as intentional drops here rather than porting.
3. Archive CrossRepoActions once ISettingsService is injected but never used in 5 services #1 lands — at that point KtsuTools.Repo has functional parity for the useful features. The two dropped features above are the only gaps and they're deliberate.

Maintainer can confirm or override; I won't archive anything without explicit approval.

---

Generated by Claude Code

[matt-edmondson]

Filed #35 for the --parallel wiring (the only real functional gap). Once #35 lands, this issue can be closed and the maintainer can archive ktsu-dev/CrossRepoActions (out of my scope).

The dropped items (interactive menu, pwsh-driven steps) stand as intentional drops per the audit above.

---

Generated by Claude Code

[matt-edmondson]

CrossRepoActions vs ktsu repo audit

CrossRepoActions feature	ktsu repo status	Notes
Repository discovery	✅ repo discover	RepoService.DiscoverRepositoriesAsync recurses, treats any .git dir as a repo root, doesn't descend further.
Build & test	✅ repo build	BuildAndTestAsync runs dotnet build + dotnet test --no-build per discovered solution.
Git pull	✅ repo pull	PullAllAsync uses git pull --all --autostash, classifies result by exit code + error/fatal/CONFLICT in stderr.
Update packages	✅ repo update-packages	UpdatePackagesAsync runs dotnet list package --outdated per project and counts upgradable refs.
Parallel build/test execution	✅ closed via #35	--parallel now uses Parallel.ForEachAsync with DOP = ProcessorCount/2; failures aggregated with names.
Interactive menu mode	❌ not ported	KtsuTools.Repo is non-interactive only; you have to invoke each verb explicitly.
PowerShell-Core-driven steps	❌ not ported	Everything goes through IProcessService.RunAsync directly.

Decision

The functional gap was the parallel build, which is now closed. The remaining deltas — menu mode and PowerShell-driven steps — are stylistic and (in my view) not worth porting:

• A menu would be inconsistent with the rest of ktsu's flag-driven surface; users coming from CrossRepoActions can build a wrapper script.
• The PowerShell layer was historical baggage from CrossRepoActions' predecessor; direct process invocation is simpler.

Recommendation: archive CrossRepoActions. Both functional commands and the parallelism that justified the standalone tool now live in ktsu repo.

(Posting as an audit, not closing — the archive call belongs to a human.)

---

Generated by Claude Code

[matt-edmondson]

Parity is reached (see audit comment); the only thing keeping this open is the "archive CrossRepoActions" call, which is a human/admin action — leaving the issue open as a tracker for that. Close once you've archived the repo on GitHub.

---

Generated by Claude Code