feat(scope): isolate user scope when project scope is installed (#73)

[jeff-r2026]

Summary

Closes #73. When a project-scope install is detected in the current directory, teamai now operates on the project scope only — the user scope is no longer pulled or searched. This stops a self-contained project knowledge base from being polluted by user-scope team resources.

• pull: detect project scope first; in project mode skip the user scope entirely and print 检测到 project scope，已跳过 user scope. Hooks reconcile is limited to the active scope. Cross-team source skills are still pulled (decision per issue), now against the active scope so deploys land in the right base dir.
• recall: query the project index only when a project scope is detected, the user index otherwise. The two scopes are no longer merged/deduped.
• uninstall: the summary now states which scope (user/project) and .teamai path it is acting on, to avoid wiping the wrong scope.

auto-recall already resolved a single scope index via autoDetectInit(), so it stays consistent with the new behavior.

Behavior change

command	no project scope (unchanged)	project scope present (new)
teamai pull	pull user scope	project only, user skipped (+ notice)
teamai recall	search user index	project index only
teamai uninstall	acts on user scope	acts on project scope (now labeled)

Backward compatible for pure user-scope users (no project config → identical behavior).

Test plan

• npx tsc --noEmit
• npm run build
• Unit: pull-scope-isolation.test.ts (project mode skips user, source routed to active config; user mode unchanged)
• Unit: recall-scope-isolation.test.ts (project-only vs user-only results, real indexes)
• E2E (offline, no token): scope-isolation-e2e.test.ts — dual-scope sandbox driving the real CLI for pull (notice + project skill deployed, user skill NOT deployed), recall (project knowledge only), uninstall --dry-run (states project scope)
• Full unit suite: 1670 passed

Made with Cursor