rename compatible to evolving

Author: chaokunyang

compiler/README.md

@@ -236,7 +236,7 @@ option (fory).polymorphism = true;
 ```fdl
 message MyMessage {
     option (fory).id = 100;
-    option (fory).compatible = true;
+    option (fory).evolving = false;
     option (fory).use_record_for_java = true;
     string name = 1;
 }

compiler/extension/fory_options.proto

@@ -30,7 +30,7 @@
 // Message options:
 //   message MyMessage {
 //     option (fory).id = 100;
-//     option (fory).compatible = true;
+//     option (fory).evolving = false;
 //     option (fory).use_record_for_java = true;
 //   }
 //
@@ -83,10 +83,10 @@ message ForyMessageOptions {
   // If not specified, namespace-based registration is used.
   optional int32 id = 1;
 
-  // Enable schema compatibility mode for this message.
-  // When true, fields can be added/removed without breaking compatibility.
-  // Default: false (strict schema matching)
-  optional bool compatible = 2;
+  // Enable schema evolution for this message.
+  // When true (default), fields can be added/removed with forward/backward compatibility.
+  // When false, schema is fixed like a struct - no changes allowed, better performance.
+  optional bool evolving = 2;
 
   // Generate a Java record instead of a class for this specific message.
   // Overrides file-level use_record_for_java_message setting.

compiler/fory_compiler/parser/parser.py

@@ -68,7 +68,7 @@
 # Known Fory message-level options (option statements inside message body)
 KNOWN_FORY_MESSAGE_OPTIONS: Set[str] = {
     "id",
-    "compatible",
+    "evolving",
     "use_record_for_java",
     "deprecated",
     "namespace",

compiler/tests/test_package_options.py

@@ -1105,7 +1105,7 @@ def test_message_level_fory_option(self):
         package myapp;
         message User {
             option (fory).id = 100;
-            option (fory).compatible = true;
+            option (fory).evolving = false;
             string name = 1;
         }
         '''
@@ -1116,7 +1116,7 @@ def test_message_level_fory_option(self):
         user = schema.messages[0]
         assert user.type_id == 100  # fory.id should set type_id
         assert user.options.get("fory.id") == 100
-        assert user.options.get("fory.compatible") is True
+        assert user.options.get("fory.evolving") is False
 
     def test_message_fory_id_sets_type_id(self):
         """Test that option (fory).id sets message type_id."""
@@ -1315,11 +1315,11 @@ def test_unknown_extension_warns(self):
             assert "ignoring unknown extension 'custom'" in str(w[0].message)
 
     def test_inline_and_body_options_merge(self):
-        """Test that inline [id=100] and body option (fory).compatible merge."""
+        """Test that inline [id=100] and body option (fory).evolving merge."""
         source = '''
         package myapp;
         message User [id=100] {
-            option (fory).compatible = true;
+            option (fory).evolving = false;
             string name = 1;
         }
         '''
@@ -1330,7 +1330,7 @@ def test_inline_and_body_options_merge(self):
         user = schema.messages[0]
         assert user.type_id == 100  # From inline option
         assert user.options.get("id") == 100  # Stored in options
-        assert user.options.get("fory.compatible") is True  # From body option
+        assert user.options.get("fory.evolving") is False  # From body option
 
     def test_body_option_overrides_inline_id(self):
         """Test that body option (fory).id overrides inline [id=...]."""

docs/schema/fdl-syntax.md

@@ -1010,7 +1010,7 @@ Options can be specified inside the message body:
 ```fdl
 message MyMessage {
     option (fory).id = 100;
-    option (fory).compatible = true;
+    option (fory).evolving = false;
     option (fory).use_record_for_java = true;
     string name = 1;
 }
@@ -1019,7 +1019,7 @@ message MyMessage {
 | Option                | Type   | Description                                |
 | --------------------- | ------ | ------------------------------------------ |
 | `id`                  | int    | Type ID for serialization (sets type_id)   |
-| `compatible`          | bool   | Enable schema compatibility mode           |
+| `evolving`            | bool   | Schema evolution support (default: true). When false, schema is fixed like a struct |
 | `use_record_for_java` | bool   | Generate Java record for this message      |
 | `deprecated`          | bool   | Mark this message as deprecated            |
 | `namespace`           | string | Custom namespace for type registration     |
@@ -1069,7 +1069,7 @@ You can combine standard options with Fory extension options:
 ```fdl
 message User {
     option deprecated = true;        // Standard option
-    option (fory).compatible = true; // Fory extension option
+    option (fory).evolving = false; // Fory extension option
 
     string name = 1;
     MyType data = 2 [deprecated = true, (fory).ref = true];
@@ -1098,7 +1098,7 @@ extend google.protobuf.MessageOptions {
 
 message ForyMessageOptions {
     optional int32 id = 1;
-    optional bool compatible = 2;
+    optional bool evolving = 2;
     optional bool use_record_for_java = 3;
     optional bool deprecated = 4;
     optional string namespace = 5;