[Bug] scan-repository fails with "core.repositoryformatversion does not support extension: worktreeconfig" in v2.33.0

[jamesdag]

Regression: works in v2.32.3, fails in v2.33.0 (introduced by the dependency bump in PR #1322).

Root cause: git sparse-checkout writes extensions.worktreeConfig = true into .git/config. The version of go-git pulled in by v2.33.0 validates git repo format extensions strictly and doesn't recognise worktreeConfig, failing immediately at repo open.

Error:

  [Info] Frogbot version: 2.33.0
  [Info] Running Frogbot "scan-repository" command
  [Info] Getting resources (git repository: ...) active watches...
  [Error] core.repositoryformatversion does not support extension: worktreeconfig

Repro: run actions/checkout with sparse-checkout: configured before the Frogbot step, then run frogbot scan-repository.

Workaround: run git sparse-checkout disable before Frogbot runs.

Fix suggestion: upgrade to a go-git version that supports worktreeConfig (standard since git 2.20).

[omribz156]

I took a focused look at this because the failure matches go-git's repository-extension validation path.

What I found:

• Frogbot is already on the latest tagged github.com/go-git/go-git/v5 (v5.19.1), so this does not look fixable by a normal v5 patch bump today.
• A tiny local repro with go-git/v5.19.1 and a repo config containing extensions.worktreeConfig = true reproduces the same error: core.repositoryformatversion does not support extension: worktreeconfig.
• The same tiny repro works with go-git/v6.0.0-alpha.3, where WorktreeConfig is modeled.
• There is already upstream go-git tracking for this exact v5 casing/extension validation problem: verifyExtensions rejects standard extensions due to case-mismatched whitelist go-git/go-git#2156 and an older open PR: [v5] repository: fix extension validation for worktreeConfig repositories go-git/go-git#1982.

I did not open a Frogbot PR because the two obvious options are both a bit risky: downgrading/pinning around a dependency update that included security hardening, or moving Frogbot to the v6 alpha import path. The cleanest path seems to be either waiting for an upstream go-git v5 fix/release, or carrying a very explicit temporary dependency override if the sparse-checkout regression needs an urgent Frogbot release.

This was checked with Codex assistance, but I manually verified the repro/source path before posting.