fix(errcheck): handle all unchecked error returns without changing behaviormain

errcheck ./... flagged unchecked HTTP response Close(), file Close(),
os.RemoveAll(), fmt.Scanln(), and fmt.Fprintf() calls across codeberg,
github, release, showcase, and sync. None of these were bugs causing
incorrect behavior today, but leaving them unchecked hid real failure
modes (e.g. a lagging NFS mount failing a file Close() after writes,
which this codebase has hit before per commit 23ecaa2).

- internal/codeberg/codeberg.go, internal/github/github.go,
  internal/release/release.go: added a small closeResponseBody(resp)
  helper per package and used it for all deferred resp.Body.Close()
  calls. The body is always fully read (or abandoned on an earlier
  error) by the time Close() runs, so the error is intentionally
  discarded - matching the explicit `_ = ...` discard convention
  already used elsewhere in this repo (e.g. showcase.go's
  os.RemoveAll on the worktree-add failure path).
- internal/release/release.go: the two fmt.Scanln(&response) prompts
  now explicitly discard the return values; a Scanln error already
  leaves response == "", which the existing y/yes check already
  treats as a safe decline, so behavior is unchanged.
- internal/showcase/code_extractor.go, images.go, language_detector.go:
  added a shared closeFile(*os.File) helper (package showcase) for the
  read-only file Close() calls, matching the same discard rationale.
  copyFile's destination Close() is the one write-side case where a
  close failure is real data-loss information, so it now uses a named
  return to surface it via err without masking any earlier error.
- internal/showcase/showcase.go: the deferred os.RemoveAll(tempRoot)
  now explicitly discards its error, matching the sibling `_ =` call
  three lines above in the same function.
- internal/sync/branch_analyzer.go: GenerateDeleteScript's per-repository
  fmt.Fprintf(file, ...) calls are now checked and wrapped with
  fmt.Errorf(...: %w), matching the error-wrapping convention already
  used by writeBranchDeletionBlock right below it in the same file
  (the repeated repo-header writes were pulled into a new
  writeDeleteScriptRepoHeader helper to keep this readable). The
  script file's defer file.Close() now uses a named return so a close
  failure is reported instead of silently discarded.

Added focused tests for the two behavior-relevant paths: copyFile's
missing-source/success paths after the named-return change, and
PromptConfirmation's empty-input-declines/explicit-yes behavior after
touching the Scanln call. Trivial defer-Close discards elsewhere are
not additionally unit tested per the task's guidance against
overengineering.

Verified: go build ./..., go vet ./..., errcheck ./... (clean), and
go test ./... all pass.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

0 files changed, 0 insertions, 0 deletions