bug: report --project flag with relative path (e.g. '.') never matches any entries

[claude]

Problem

uncompact report --project . always returns zero results, even when the current project has activity log entries.

In cmd/report.go:82-85, the flag value is only cleaned, not resolved to an absolute path:

var filterProject string
if reportProject != "" {
    filterProject = filepath.Clean(reportProject)
}

filepath.Clean(".") returns "." — a relative path. But activity log entries store absolute paths (e.g. /home/user/myproject) set via proj.RootDir from project.Detect. The comparison in filterEntries at cmd/report.go:131 is:

filepath.Clean(e.Project) != filterProject

filepath.Clean("/home/user/myproject") != "." is always true, so every entry is filtered out.

Steps to reproduce

1. Run uncompact run a few times to populate the activity log.
2. cd into that project directory.
3. Run uncompact report --project .
4. Observe zero results even though events exist.

Fix

Resolve the flag value to an absolute path before storing it:

if reportProject != "" {
    if abs, err := filepath.Abs(reportProject); err == nil {
        filterProject = abs
    } else {
        filterProject = filepath.Clean(reportProject)
    }
}

Location

• cmd/report.go:82-85 (relative path not resolved)
• cmd/report.go:131 (comparison using the unresolved path)

Note: logsHandler and statsHandler correctly call project.Detect (which calls os.Getwd() internally) to resolve the project path, so they are not affected. Only reportHandler has this bug.

@claude please implement this

[claude]

Claude finished @claude[bot]'s task in 1m 39s —— View job • claude/issue-430-20260301-2015 • [Create PR ➔](https://github.com/supermodeltools/Uncompact/compare/main...claude/issue-430-20260301-2015?quick_pull=1&title=Issue%20%23430%3A%20Changes%20from%20Claude&body=This%20PR%20addresses%20issue%20%23430%0A%0AGenerated%20with%20%5BClaude%20Code%5D(https%3A%2F%2Fclaude.ai%2Fcode)

---

Tasks

• Analyze issue and gather context
• Read cmd/report.go to understand current code
• Apply fix: resolve relative paths to absolute paths in reportHandler
• Build and vet to verify compilation
• Commit and push changes
• Create PR

Summary

Fixed the bug in cmd/report.go where --project . (or any relative path) always returned zero results.

Root cause: filepath.Clean(".") returns ".", which never matches absolute paths like /home/user/myproject stored in the activity log.

Fix: Replaced filepath.Clean with filepath.Abs in the project filter normalization block (lines 82–88), so relative paths are resolved to absolute before comparison. Falls back to filepath.Clean if filepath.Abs fails.

PR: #433