[Feature/Enhancement] Worktrees of same project are counted separate in "By Project" usage whereas they should be shown as same

[RotBolt]

The issue is git worktrees are shown as separately in "By Project" usage
Git worktrees belong to same project therefore either data should be summed up for all worktrees or they should be grouped under same project and codeburn can show separate worktree usage like in present just that they are grouped under same project

Option A

Project usage = sum of all worktrees

Option B

Project usage
- worktree A usage
- worktree B usage

Current behavior

[iamtoruk]

Thanks for the report — this is a valid gap. Here's the plan:

Approach

A single canonicalProjectPath(cwd) function (~20 lines) in the project-aggregation layer. It reads the .git entry at the project path:

• If .git is a directory (normal repo) → return cwd as-is (no change)
• If .git is a file → parse the gitdir: line. If the resolved path contains /.git/worktrees/, strip that suffix to get the main repo path. Group under that.
• If .git doesn't exist or doesn't parse → return cwd as-is (graceful fallback to current behavior)

The /.git/worktrees/ guard prevents submodules (/.git/modules/...) or --separate-git-dir setups from being incorrectly merged.

Resolution at ingest time

The canonical path is resolved once when a session is first processed, not on every report query. This means:

• Zero filesystem I/O at query time (it's just a GROUP BY on the stored canonical path)
• Deleted worktrees still group correctly — the path was resolved while it was alive
• No persistent worktree cache needed

Display

Flat sum (your Option A) — all worktrees fold into one project line, named after the main repo's directory. This keeps the output clean and matches the mental model of "one project."

Default behavior

On by default, no config flag. Worktree users get correct grouping automatically; non-worktree users are unaffected.