From 6fdc4c3c0928652cb26564a862e4038ffb3c7aec Mon Sep 17 00:00:00 2001
From: Jeff Carr <jcarr@wit.com>
Date: Fri, 10 Jan 2025 04:42:28 -0600
Subject: [PATCH] Notes added by 'git notes append'

---
 d9e5edb3a8486bc884841137095dd910e42b3a98 | 92 ++++++++++++++++++++++++
 1 file changed, 92 insertions(+)

diff --git a/d9e5edb3a8486bc884841137095dd910e42b3a98 b/d9e5edb3a8486bc884841137095dd910e42b3a98
index ac56139..8e86047 100644
--- a/d9e5edb3a8486bc884841137095dd910e42b3a98
+++ b/d9e5edb3a8486bc884841137095dd910e42b3a98
@@ -49,3 +49,95 @@ gopkg.in/yaml.v3 v3.0.0 h1:hjy8E9ON/egN1tAYqKb61G10WtihqetD4sz2H+8nIeA=
 gopkg.in/yaml.v3 v3.0.0/go.mod h1:K4uyk7z7BCEPqu6E+C64Yfv1cQ7kz7rIZviUmN+EgEM=
 
 // `autogen:file.marshal.pb.go`
+
+// Code generated by go.wit.com/apps/autogenpb DO NOT EDIT.
+// This file was autogenerated with autogenpb v0.0.38-3-g25ae7fc 2025.01.10_0422
+//     go install go.wit.com/apps/autogenpb@latest
+//
+// define which structs (messages) you want to use in the .proto file
+// Then sort.pb.go and marshal.pb.go files are autogenerated
+//
+// autogenpb uses it and has an example .proto file with instructions
+//
+
+package main
+
+import (
+	"google.golang.org/protobuf/encoding/protojson"
+	"google.golang.org/protobuf/encoding/prototext"
+	"google.golang.org/protobuf/proto"
+)
+
+// human readable JSON
+func (v *Files) FormatJSON() string {
+	return protojson.Format(v)
+}
+
+// marshal json
+func (v *Files) MarshalJSON() ([]byte, error) {
+	return protojson.Marshal(v)
+}
+
+// unmarshal json
+func (v *Files) UnmarshalJSON(data []byte) error {
+	return protojson.Unmarshal(data, v)
+}
+
+// apparently this isn't stable, but it's awesomely better
+// https://protobuf.dev/reference/go/faq/#unstable-text
+// it's brilliant for config files!
+func (v *Files) FormatTEXT() string {
+	return prototext.Format(v)
+}
+
+// unmarshalTEXT. This reads the .text config file back in after the user edits it
+func (v *Files) UnmarshalTEXT(data []byte) error {
+	return prototext.Unmarshal(data, v)
+}
+
+// marshal to wire. This is called winning.
+func (v *Files) Marshal() ([]byte, error) {
+	return proto.Marshal(v)
+}
+
+// unmarshal from wire. You have won.
+func (v *Files) Unmarshal(data []byte) error {
+	return proto.Unmarshal(data, v)
+}
+
+// human readable JSON
+func (v *Identify) FormatJSON() string {
+	return protojson.Format(v)
+}
+
+// marshal json
+func (v *Identify) MarshalJSON() ([]byte, error) {
+	return protojson.Marshal(v)
+}
+
+// unmarshal json
+func (v *Identify) UnmarshalJSON(data []byte) error {
+	return protojson.Unmarshal(data, v)
+}
+
+// apparently this isn't stable, but it's awesomely better
+// https://protobuf.dev/reference/go/faq/#unstable-text
+// it's brilliant for config files!
+func (v *Identify) FormatTEXT() string {
+	return prototext.Format(v)
+}
+
+// unmarshalTEXT. This reads the .text config file back in after the user edits it
+func (v *Identify) UnmarshalTEXT(data []byte) error {
+	return prototext.Unmarshal(data, v)
+}
+
+// marshal to wire. This is called winning.
+func (v *Identify) Marshal() ([]byte, error) {
+	return proto.Marshal(v)
+}
+
+// unmarshal from wire. You have won.
+func (v *Identify) Unmarshal(data []byte) error {
+	return proto.Unmarshal(data, v)
+}