fix(self): stop SessionStart hook from resetting the user's business repo

[m0Nst3r873]

Summary

Fixes a data-loss bug: after teamai is set up, a background pull on every
session start could run git reset --hard + git checkout <defaultBranch>
against the user's own business repo — wiping uncommitted work and switching
them off their branch.

The field reports came from HTTP mode (clawpro / openclaw local-agent) in
project scope, but the same root cause also affects self mode and project-scope
git mode. This PR closes the whole family with two independent defense layers and
locks each path with a regression test.

#292 (single-repo / self mode) has merged, so this PR's diff is clean — the six
files below are the entire change.

Root cause

The SessionStart pull hook runs in the background (its handler is not
git-only, so it also fires under the HTTP provider) and auto-reports usage:

SessionStart hook → pull({ silent: true })
  → reportUsageToTeam(repoPath, …)                       # repoPath = <root>/.teamai/team-repo
    → resetToCleanMaster: git reset --hard HEAD
                          git checkout <defaultBranch>    # walks up to the business repo's .git!

repoPath is expected to be a disposable cache clone, but in several
configurations it lives inside the user's repo and has no .git of its own,
so git commands bubble up to the enclosing business repo:

Mode / scope	repo.localPath	Own .git?	Result before fix
HTTP, project (clawpro)	<projectRoot>/.teamai/team-repo	no (ensureDir)	reset --hard on business repo
self mode	<businessRoot>/.teamai	no (subdir)	reset --hard on business repo
git, project (team-repo clone missing/incomplete)	<projectRoot>/.teamai/team-repo	no	reset --hard on business repo

The trigger that reached real users: in pull(), the user-scope report
target filtered out kind === 'http', but the project-scope target did
not (asymmetric). So an HTTP project-scope config fell through into
reportUsageToTeam's git-mode branch and reset the working tree. This has been
present since v0.19.0 (the reset path dates to 547f9e2).

Fix — two independent layers

• src/pull.ts — the project-scope report target now also filters
  kind !== 'http', symmetric with the user-scope target. Primary defense:
  in HTTP mode both targets are skipped, so reportUsageToTeam is never called
  and no git command runs against the business repo.
• src/utils/git.ts — new shared isDedicatedRepoRoot(repoPath): confirms
  repoPath is its own git top level (git rev-parse --show-toplevel,
  compared via fs.realpath on both sides so a symlinked prefix like macOS
  /tmp → /private/tmp doesn't misjudge). Returns false (fail-closed) whenever
  that can't be positively confirmed, so callers bail.
• src/team-push.ts — the git-mode report branch uses the shared guard as a
  backstop: if repoPath isn't a dedicated root, it bails out entirely — no
  reset, pull, stats write, or commit/push.
• src/push.ts — teamai push applies the same guard before
  resetToCleanMaster. On a non-dedicated root it aborts the whole push with a
  clear message (Cannot push: team repo path is not a dedicated git root…)
  rather than reset --hard-ing the business repo or failing silently.

Tests

• src/__tests__/pull-scope-isolation.test.ts — HTTP project scope: asserts
  pull never calls reportUsageToTeam (the primary defense). Also keeps the
  existing assertion that selfConfig is forwarded for the self-mode target.
• src/__tests__/self-mode-no-business-reset.test.ts — real-git E2E (no mocks):
  • self mode: business repo's uncommitted changes + current branch survive;
  • project scope, team-repo dir without its own .git: business tree/branch
    survive and no spurious stats commit lands on the user's branch;
  • a genuine dedicated cache clone is still reset (no regression).

Both new guards were verified with a negative control — each test fails when
its guard is removed (http filter / isDedicatedRepoRoot), confirming the tests
actually catch the regression.

Test plan

• npm run build
• npx tsc --noEmit
• npx vitest run — all related suites pass
• Real-git E2E: business working tree + branch preserved across self mode and project scope; dedicated cache clone still reset
• Negative control: removing the http filter fails the HTTP test; removing isDedicatedRepoRoot fails the project-scope E2E

🤖 Generated with Claude Code