feat(platform)!: required document fields via contract updates (requiredSince)

packages/rs-dpp/schema/meta_schemas/document/v3/document-meta.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json-schema.org/draft/2020-12/schema",
   "$id": "https://github.com/dashpay/platform/blob/master/packages/rs-dpp/schema/meta_schemas/document/v1/document-meta.json",
-  "$comment": "EDITABLE UNTIL THE RELEASE CARRYING PROTOCOL V14 SHIPS — FROZEN AFTER. This v3 document meta-schema activates with protocol v14 (CONTRACT_VERSIONS_V6). It is v2 plus the ranked index keywords (rankedCountable, rankedSummable, rankedAverageable) and the refersTo reference keyword on identifier properties, and admits every v14+ contract written to disk. v2 stays in place for protocol v13, where those keys still fail an index entry's `additionalProperties: false`. Once the release carrying protocol v14 ships, mutating it would change historical validation results and break consensus replay. After release, any new top-level property or rule MUST go in a newer meta-schema version (v4+). The $id above deliberately still names the v1 path: v1, v2 and v3 all share that identity, and it is the exact string `enrich_with_base_schema` injects as every PV12+ document schema's `$schema`, so bumping it here would be a wire-visible change rather than a documentation fix.",
+  "$comment": "EDITABLE UNTIL THE RELEASE CARRYING PROTOCOL V14 SHIPS — FROZEN AFTER. This v3 document meta-schema activates with protocol v14 (CONTRACT_VERSIONS_V6). It is v2 plus the ranked index keywords (rankedCountable, rankedSummable, rankedAverageable), the refersTo reference keyword on identifier properties, and the requiredSince property keyword (the contract version a property is required from), and admits every v14+ contract written to disk. v2 stays in place for protocol v13, where those keys still fail an index entry's `additionalProperties: false`. Once the release carrying protocol v14 ships, mutating it would change historical validation results and break consensus replay. After release, any new top-level property or rule MUST go in a newer meta-schema version (v4+). The $id above deliberately still names the v1 path: v1, v2 and v3 all share that identity, and it is the exact string `enrich_with_base_schema` injects as every PV12+ document schema's `$schema`, so bumping it here would be a wire-visible change rather than a documentation fix.",
   "type": "object",
   "$defs": {
     "documentProperties": {
@@ -224,6 +224,11 @@
         "position": {
           "type": "integer",
           "minimum": 0
+        },
+        "requiredSince": {
+          "type": "integer",
+          "minimum": 1,
+          "maximum": 4294967295
         }
       },
       "dependentSchemas": {

packages/rs-dpp/src/data_contract/document_type/class_methods/mod.rs

@@ -1,3 +1,4 @@
+use crate::consensus::basic::data_contract::DataContractInvalidRequiredFieldsUpdateError;
 #[cfg(feature = "validation")]
 use crate::consensus::basic::BasicError;
 #[cfg(feature = "validation")]
@@ -26,6 +27,27 @@ pub(crate) fn consensus_or_protocol_data_contract_error(
     }
 }
 
+#[inline]
+pub(crate) fn consensus_or_protocol_required_fields_error(
+    error: DataContractInvalidRequiredFieldsUpdateError,
+) -> ProtocolError {
+    #[cfg(feature = "validation")]
+    {
+        ProtocolError::ConsensusError(
+            ConsensusError::BasicError(BasicError::DataContractInvalidRequiredFieldsUpdateError(
+                error,
+            ))
+            .into(),
+        )
+    }
+    #[cfg(not(feature = "validation"))]
+    {
+        ProtocolError::DataContractError(DataContractError::InvalidContractStructure(
+            error.to_string(),
+        ))
+    }
+}
+
 #[inline]
 pub(crate) fn consensus_or_protocol_value_error(
     platform_value_error: platform_value::Error,

packages/rs-dpp/src/data_contract/document_type/class_methods/try_from_schema/common/mod.rs

@@ -745,6 +745,7 @@ fn parse_document_properties(
             &mut document_properties,
             &required_fields,
             &transient_fields,
+            true,
             property_key,
             property_value,
             root_schema,