chore: publish Go module as github.com/priompt/proto

README.md

@@ -17,7 +17,7 @@ So the shared things live here, and there is exactly one of each:
 
 ```mermaid
 flowchart TD
-    subgraph This["📖 This repo (module priomptproto)"]
+    subgraph This["📖 This repo (module github.com/priompt/proto)"]
         P["proto/priompt/v1/prompt.proto<br/>the PromptService contract"]
         G["gen/<br/>generated Go stubs"]
         C["claims/<br/>JWT claims contract"]
@@ -77,10 +77,10 @@ The honest fine print:
   fork.
 - **python-sdk commits its generated stubs** so the wheel ships them; they are
   artifacts of this repo's `.proto`, regenerated by `buf generate` there.
-- **The Go module is `priomptproto`** — a placeholder path until first
-  release. Sibling repos point at it with a `replace` directive
-  (`replace priomptproto => ../proto`); at publish time the path becomes the
-  real one and the replaces drop.
+- **The Go module is `github.com/priompt/proto`**, versioned by `v*` tags.
+  Dependents require a tagged version. To change it alongside a dependent
+  repo, use a `go.work` in the parent directory
+  (`go work init ./proto ./priompt`) instead of a `replace`.
 
 ## Relation to the other repos
 

go.mod

@@ -1,4 +1,4 @@
-module priomptproto
+module github.com/priompt/proto
 
 go 1.25.0
 

proto/priompt/v1/prompt.proto

@@ -2,7 +2,7 @@ syntax = "proto3";
 
 package priompt.v1;
 
-option go_package = "priomptproto/gen/priompt/v1;priomptv1";
+option go_package = "github.com/priompt/proto/gen/priompt/v1;priomptv1";
 
 // PromptService serves validated prompts. Phase 1 is read-only over the wire;
 // writes happen via the `priompt put` CLI until promptctl lands (Phase 3).