feat: add generated connect-rpc code

.git-branches.toml

@@ -0,0 +1,112 @@
+# Git Town configuration file
+#
+# Run "git town config setup" to add additional entries
+# to this file after updating Git Town.
+#
+# The "push-hook" setting determines whether Git Town
+# permits or prevents Git hooks while pushing branches.
+# Hooks are enabled by default. If your Git hooks are slow,
+# you can disable them to speed up branch syncing.
+#
+# When disabled, Git Town pushes using the "--no-verify" switch.
+# More info at https://www.git-town.com/preferences/push-hook.
+push-hook = true
+
+# Should Git Town push the new branches it creates
+# immediately to origin even if they are empty?
+#
+# When enabled, you can run "git push" right away
+# but creating new branches is slower and
+# it triggers an unnecessary CI run on the empty branch.
+#
+# When disabled, many Git Town commands execute faster
+# and Git Town will create the missing tracking branch
+# on the first run of "git town sync".
+push-new-branches = false
+
+# The "create-prototype-branches" setting determines whether Git Town
+# always creates prototype branches.
+# Prototype branches sync only locally and don't create a tracking branch
+# until they are proposed.
+#
+# More info at https://www.git-town.com/preferences/create-prototype-branches.
+create-prototype-branches = false
+
+# Which method should Git Town use to ship feature branches?
+#
+# Options:
+#
+# - api: merge the proposal on your code hosting platform via the code hosting API
+# - fast-forward: in your local repo, fast-forward the parent branch to point to the commits on the feature branch
+# - squash-merge: in your local repo, squash-merge the feature branch into its parent branch
+#
+# All options update proposals of child branches and remove the shipped branch locally and remotely.
+ship-strategy = "api"
+
+# Should "git town ship" delete the tracking branch?
+# You want to disable this if your code hosting platform
+# (GitHub, GitLab, etc) deletes head branches when
+# merging pull requests through its UI.
+ship-delete-tracking-branch = false
+
+# Should "git town sync" sync tags with origin?
+sync-tags = true
+
+# Should "git town sync" also fetch updates from the upstream remote?
+#
+# If an "upstream" remote exists, and this setting is enabled,
+# "git town sync" will also update the local main branch
+# with commits from the main branch at the upstream remote.
+#
+# This is useful if the repository you work on is a fork,
+# and you want to keep it in sync with the repo it was forked from.
+sync-upstream = true
+
+[branches]
+
+# The main branch is the branch from which you cut new feature branches,
+# and into which you ship feature branches when they are done.
+# This branch is often called "main", "master", or "development".
+main = "main"
+
+# Perennial branches are long-lived branches.
+# They are never shipped and have no ancestors.
+# Typically, perennial branches have names like
+# "development", "staging", "qa", "production", etc.
+#
+# See also the "perennial-regex" setting.
+perennials = []
+
+# All branches whose name matches this regular expression
+# are also considered perennial branches.
+#
+# If you are not sure, leave this empty.
+perennial-regex = ""
+
+[hosting]
+
+# Knowing the type of code hosting platform allows Git Town
+# to open browser URLs and talk to the code hosting API.
+# Most people can leave this on "auto-detect".
+# Only change this if your code hosting server uses as custom URL.
+platform = "github"
+
+# When using SSH identities, define the hostname
+# of your source code repository. Only change this
+# if the auto-detection does not work for you.
+# origin-hostname = ""
+
+[sync-strategy]
+
+# How should Git Town synchronize feature branches?
+# Feature branches are short-lived branches cut from
+# the main branch and shipped back into the main branch.
+# Typically you develop features and bug fixes on them,
+# hence their name.
+feature-branches = "merge"
+
+# How should Git Town synchronize perennial branches?
+# Perennial branches have no parent branch.
+# The only updates they receive are additional commits
+# made to their tracking branch somewhere else.
+perennial-branches = "rebase"

.vscode/launch.json

@@ -0,0 +1,28 @@
+{
+  // Attach to Air for debugging
+  "version": "0.2.0",
+  "configurations": [
+    {
+      "name": "Launch Package",
+      "type": "go",
+      "request": "launch",
+      "mode": "auto",
+      "program": "${fileDirname}",
+      "env": {
+        "TESTCONTAINERS_RYUK_CONTAINER_PRIVILEGED": "true",
+        "TESTCONTAINERS_DOCKER_SOCKET_OVERRIDE": "/var/run/docker.sock"
+      },
+      "showLog": true,
+      "console": "integratedTerminal"
+    },
+    {
+      "name": "Attach to Air",
+      "type": "go",
+      "debugAdapter": "dlv-dap",
+      "mode": "remote",
+      "request": "attach",
+      "host": "127.0.0.1",
+      "port": 12345
+    }
+  ]
+}

buf.gen.yaml

@@ -21,3 +21,7 @@ plugins:
   - remote: buf.build/grpc/go:v1.3.0
     out: protocol/go
     opt: paths=source_relative
+  - remote: buf.build/connectrpc/go:v1.17.0
+    out: protocol/go
+    opt:
+      - paths=source_relative