Protobuf specification rework

.gitignore

@@ -62,3 +62,7 @@ modules/website/static/api
 *.hnir
 
 .bsp
+
+# smithy LSP
+build/smithy
+.smithy.lsp.log

build.sc

@@ -141,6 +141,10 @@ object core extends BaseJavaModule {
   }
 }
 
+object protobuf extends BaseJavaModule {
+
+}
+
 val scalaVersionsMap =
   Map("2.13" -> "2.13.7", "2.12" -> "2.12.17", "3" -> "3.3.0")
 object openapi extends Cross[OpenapiModule](scalaVersionsMap.keys.toList)

docs/protocols/gRPC.md

@@ -6,6 +6,8 @@ The following traits should be taken into consideration by implementors of the p
 
 - alloy.proto#protoIndex
 - alloy.proto#protoNumType
+- alloy.proto#protoWrapped
+- alloy.proto#protoCompactUUID
 
 Additionally, the following traits can be taken into consideration by other tooling to translate smithy specifications to proto specifications.
 

docs/serialisation/json.md

@@ -1,8 +1,8 @@
-### JSON serialisation
+## JSON serialisation
 
 `alloy` defines a number of traits that can be taken into consideration by protocols to express additional constraints and encodings typically found in the industry.
 
-#### Unions
+### Unions
 
 Unions in this protocol can be encoded in three different ways: tagged, discriminated, and untagged.
 
@@ -11,7 +11,7 @@ By default, the specification of the Smithy language hints that the `tagged-unio
 However, `alloy#simpleRestJson` supports two additional encodings: `discriminated` and `untagged`, which users can opt-in via the `alloy#discriminated` and `alloy#untagged` trait, respectively. These are mostly offered as a way to retrofit existing APIs in Smithy.
 
 
-##### Tagged union
+#### Tagged union
 
 This is the default behavior, and happens to visually match how Smithy unions are declared. In this encoding, the union is encoded as a JSON object with a single key-value pair, the key signalling which alternative has been encoded.