chore: go mod tidy — pflag is a direct dependency

cmd/report/report_test.go imports pflag directly to pin the two -W failure
shapes, so the indirect marking was stale and any -mod=mod build rewrote it.
Tech debt [036] closed rather than carried: the fix is one line and was
verified with a build and the report tests.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Author: Alexey Lesovsky

docs/tech-debt.md

@@ -41,17 +41,6 @@ Pre-existing, confirmed by A/B against a `master`-built binary — the feature's
 because WAL segment names differ only in their tail, so truncating from the right removes exactly the
 part that identifies the segment — the reason the column is on the screen at all.
 
-### [036] `go.mod` marks `spf13/pflag` as `// indirect` although a test imports it directly
-
-**Added:** 2026-08-06 (surfaced during feature: 017-feat-wal-archiver)
-**Severity:** Trivial
-**Area:** `go.mod`, `cmd/report/report_test.go`
-
-The flag-definition test imports `github.com/spf13/pflag` directly, but the `require` line still
-carries `// indirect`. Nothing fails today — the default readonly module mode builds, tests and lints
-fine, and CI has no `go mod tidy -diff` gate — but any build with `-mod=mod` rewrites `go.mod` and
-dirties the working tree. Fix is one `go mod tidy` run at a moment when no parallel work holds the
-branch.
 
 ### [027] Messages printed after a dialog closes are never visible
 
@@ -353,6 +342,23 @@ third unsafe consumer alongside `diff`, so fixing `diff` alone would not close t
 
 ## Resolved Debt
 
+### [036] `go.mod` marks `spf13/pflag` as `// indirect` although a test imports it directly
+
+**Added:** 2026-08-06 (surfaced during feature: 017-feat-wal-archiver)
+**Severity:** Trivial
+**Area:** `go.mod`, `cmd/report/report_test.go`
+
+The flag-definition test imports `github.com/spf13/pflag` directly, but the `require` line still
+carries `// indirect`. Nothing fails today — the default readonly module mode builds, tests and lints
+fine, and CI has no `go mod tidy -diff` gate — but any build with `-mod=mod` rewrites `go.mod` and
+dirties the working tree. Fix is one `go mod tidy` run at a moment when no parallel work holds the
+branch.
+
+**Resolved:** 2026-08-06, during finalization of 017-feat-wal-archiver — `go mod tidy` moved
+`github.com/spf13/pflag` into the direct requires, matching the direct import in
+`cmd/report/report_test.go`. One line; build and the report tests verified after.
+
+
 ### [025] `PGresult.sort` does not bounds-check its sort key
 
 **Added:** 2026-07-25 (surfaced during feature: 013-feat-activity-xmin-horizon, security audit)

go.mod

@@ -9,6 +9,7 @@ require (
 	github.com/jehiah/go-strftime v0.0.0-20171201141054-1d33003b3869
 	github.com/jroimartin/gocui v0.5.0
 	github.com/spf13/cobra v1.10.2
+	github.com/spf13/pflag v1.0.10
 	github.com/stretchr/testify v1.11.1
 	golang.org/x/term v0.42.0
 )
@@ -24,7 +25,6 @@ require (
 	github.com/nsf/termbox-go v1.1.1 // indirect
 	github.com/pmezard/go-difflib v1.0.0 // indirect
 	github.com/rogpeppe/go-internal v1.14.1 // indirect
-	github.com/spf13/pflag v1.0.10 // indirect
 	golang.org/x/sys v0.43.0 // indirect
 	golang.org/x/text v0.39.0 // indirect
 	gopkg.in/yaml.v3 v3.0.1 // indirect