From the 0.11.0 field report.
findGitRootForSession (internal/cmd/trace.go) emits session_git_root_missing whenever the session's recorded cwd doesn't resolve to a git repo on the current filesystem — even when the process-cwd fallback then finds the right repo. In containerized/remote setups where the session was recorded under a host path, this is the common case, not an error: every trace prints two warnings and carries them in the JSON.
Fix: when the fallback resolves a repo, record provenance in the git correlation block (e.g. resolved_from: "process cwd") instead of warning; keep the warning only when nothing resolves. A path-remap hint was floated in the report but is YAGNI until someone actually needs cross-path resolution.
Priority: P2 (ergonomics).
From the 0.11.0 field report.
findGitRootForSession(internal/cmd/trace.go) emitssession_git_root_missingwhenever the session's recorded cwd doesn't resolve to a git repo on the current filesystem — even when the process-cwd fallback then finds the right repo. In containerized/remote setups where the session was recorded under a host path, this is the common case, not an error: every trace prints two warnings and carries them in the JSON.Fix: when the fallback resolves a repo, record provenance in the git correlation block (e.g.
resolved_from: "process cwd") instead of warning; keep the warning only when nothing resolves. A path-remap hint was floated in the report but is YAGNI until someone actually needs cross-path resolution.Priority: P2 (ergonomics).