go mod tidy and more information on New()

go.mod

@@ -7,6 +7,7 @@ require (
 	github.com/Masterminds/semver/v3 v3.2.1
 	github.com/briandowns/spinner v1.23.0
 	github.com/charmbracelet/glamour v0.6.0
+	github.com/charmbracelet/log v0.3.1
 	github.com/creack/pty v1.1.21
 	github.com/davecgh/go-spew v1.1.1
 	github.com/fatih/color v1.16.0
@@ -28,7 +29,6 @@ require (
 	github.com/sirupsen/logrus v1.9.3
 	github.com/tdewolff/minify/v2 v2.20.9
 	github.com/ulikunitz/xz v0.5.11
-	github.com/undefinedlabs/go-mpatch v1.0.7
 	github.com/urfave/cli/v2 v2.26.0
 	github.com/versent/saml2aws/v2 v2.36.13
 	github.com/zalando/go-keyring v0.2.3
@@ -50,10 +50,8 @@ require (
 
 require (
 	dario.cat/mergo v1.0.0 // indirect
-	github.com/aymanbagabas/go-osc52 v1.0.3 // indirect
 	github.com/aymanbagabas/go-osc52/v2 v2.0.1 // indirect
 	github.com/charmbracelet/lipgloss v0.9.1 // indirect
-	github.com/charmbracelet/log v0.3.1 // indirect
 	github.com/cloudflare/circl v1.3.3 // indirect
 	github.com/cyphar/filepath-securejoin v0.2.4 // indirect
 	github.com/go-logfmt/logfmt v0.6.0 // indirect

pkg/olog/olog.go

@@ -22,6 +22,16 @@ import (
 // The logger will be automatically associated with the module and
 // package that it was instantiated in. This is done by looking at the
 // call stack.
+//
+// Note: As mentioned above, this logger is associated with the module
+// and package that created it. So, if you pass this logger to another
+// module or package, the association will NOT be changed. This
+// includes the caller metadata added to every log line as well as
+// log-level management. If a type has a common logging format that the
+// other module or package should use, then a slog.LogValuer should be
+// implemented on that type instead of passing a logger around. If
+// trying to set attributes the be logged by default, this is not
+// supported without retaining the original association.
 func New() *slog.Logger {
 	m, err := getMetadata()
 	if err != nil {