Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@cmd/simili/commands/batch.go`:
- Around line 148-155: The assignment line "cfg = &config.Config{}" in the error
branch after calling config.LoadWithInheritance(cfgPath, fetcher) is
mis-indented and should be moved into the if-block body to match the surrounding
statements; update the indentation so that "cfg = &config.Config{}" and the
following "cfg.ApplyDefaults()" are at the same indentation level inside the if
err != nil { ... } block (the code paths around cfg, config.LoadWithInheritance
and cfg.ApplyDefaults should align with the else branch and be
gofmt-consistent).

In `@internal/steps/auto_closer.go`:
- Around line 386-417: The comment's displayed grace period (gracePeriodDisplay)
is always rendered as hours but Run may use GracePeriodMinutesOverride, so
update the logic around gracePeriodDisplay and the comment formatting to reflect
the actual runtime override: read ac.cfg.AutoClose.GracePeriodHours and
ac.cfg.AutoClose.GracePeriodMinutesOverride (or the runtime value passed to
Run), compute a single effective duration value and choose the unit (hours vs
minutes) when building the comment string (reference the variables
gracePeriodDisplay, ac.cfg.AutoClose.GracePeriodHours,
GracePeriodMinutesOverride and the comment var) so the posted message shows the
correct number and unit matching what was used to decide the close.
- Around line 253-284: The triage-comment scan currently only skips comments
older than triageWindow but fails to exclude comments newer than since, allowing
post-label bot comments to short-circuit the search; update the timestamp check
around comment.CreatedAt in the auto-closer loop so it only considers comments
whose CreatedAt is within the window [since, triageWindow] (i.e., skip if
CreatedAt is nil or CreatedAt.Time.Before(since) or
CreatedAt.Time.After(triageWindow)), leaving the isBotUser/isBotComment checks
and subsequent reaction processing (ListIssueCommentReactions) intact so we
still detect the true triage comment correctly.

In `@internal/transfer/vdb_router_test.go`:
- Around line 49-53: The derivation of issueNum from id currently assumes every
rune in id is a digit and does rune arithmetic directly; change the loop that
computes issueNum to skip any non-digit characters (e.g., check
unicode.IsDigit(c) or '0'<=c && c<='9') so only numeric runes contribute to
issueNum, leaving issueNum unchanged for skipped characters; update the loop
that references id and the variable issueNum to perform this guard so UUID-like
or alphanumeric IDs don't produce incorrect numbers.

In `@internal/transfer/vdb_router.go`:
- Around line 93-104: The dedupe logic only handles float64 so issue numbers
deserialized as int64 become 0 and all issues collapse; update the extraction
around res.Payload["issue_number"] / res.Payload["number"] (the block that sets
issueNum and builds dedupeKey/seenIssues) to use a type-switch like in
similarity.go that handles int64, int, float64 (and json.Number/string if
present), converting the found numeric value into a numeric representation used
for the key (e.g., convert ints to float64 or format the integer) before
creating dedupeKey and marking seenIssues[dedupeKey]=true.

---

Nitpick comments:
In `@cmd/simili/commands/pipeline_runner.go`:
- Around line 35-41: Replace direct equality checks against the sentinel
pipeline.ErrSkipPipeline with wrap-safe errors.Is calls: where the code
currently does if err == pipeline.ErrSkipPipeline (and similar checks around the
s.Name()/ctx.Result.SkipReason handling and the other two occurrences), change
them to if errors.Is(err, pipeline.ErrSkipPipeline) and import the standard
"errors" package; keep the existing logging (fmt.Printf lines that use s.Name(),
ctx.Result.SkipReason, and err.Error()) intact so graceful skips still produce
the same messages while safely handling wrapped errors.