Update inscription field docs (#4506)

Author: casey

docs/src/inscriptions.md

@@ -76,15 +76,23 @@ Fields
 Inscriptions may include fields before an optional body. Each field consists of
 two data pushes, a tag and a value.
 
-Currently, there are six defined fields:
-
-- `content_type`, with a tag of `1`, whose value is the MIME type of the body.
-- `pointer`, with a tag of `2`, see [pointer docs](inscriptions/pointer.md).
-- `parent`, with a tag of `3`, see [provenance](inscriptions/provenance.md).
-- `metadata`, with a tag of `5`, see [metadata](inscriptions/metadata.md).
-- `metaprotocol`, with a tag of `7`, whose value is the metaprotocol identifier.
-- `content_encoding`, with a tag of `9`, whose value is the encoding of the body.
-- `delegate`, with a tag of `11`, see [delegate](inscriptions/delegate.md).
+Currently, there are thirteen defined fields:
+
+| tag | name | comment |
+|-----|------|---------|
+| `1` | `content_type` | MIME type of the body |
+| `2` | `pointer` | see [pointer](inscriptions/pointer.md) |
+| `3` | `parent` | see [provenance](inscriptions/provenance.md) |
+| `5` | `metadata` | see [metadata](inscriptions/metadata.md) |
+| `7` | `metaprotocol` | metaprotocol identifier |
+| `9` | `content_encoding` | encoding of the body |
+| `11` | `delegate` | see [delegate](inscriptions/delegate.md) |
+| `13` | `rune` | serialized rune |
+| `15` | | no-op |
+| `17` | `properties` | see [properties](inscriptions/properties.md) |
+| `19` | `property_encoding` | encoding of the properties field |
+| `66` | | unbinds inscription |
+| `255` | | no-op |
 
 The beginning of the body and end of fields is indicated with an empty data
 push.