docs(java): refresh stale comments to include source + identity in auto-naming list

Three inline comments still listed 'validator and view' as the auto-naming set
after Task 5 + the auto-naming bug fix expanded the set to also include
'source' and 'identity'. One was added in this unit; two were carryover from
Unit 1. Minor finding from the final reviewer.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: dmealing

server/java/metadata/src/main/java/com/metaobjects/io/json/CanonicalJsonSerializer.java

@@ -424,7 +424,8 @@ private static boolean getNativeIsArray(MetaData node) {
      */
     private static boolean isAutoGeneratedName(MetaData node) {
         String typeName = node.getType();
-        // Only validator and view types use auto-naming — delegate to the single source of truth.
+        // Only the types in isAutoNamingType (validator, view, source, identity) use
+        // auto-naming — delegate to the single source of truth.
         if (!BaseMetaDataParser.isAutoNamingType(typeName)) {
             return false;
         }

server/java/metadata/src/main/java/com/metaobjects/loader/parser/BaseMetaDataParser.java

@@ -269,7 +269,8 @@ protected MetaData createOrOverlayMetaData( boolean isRoot,
                     + "] requires a name to be specified in file [" + getFilename() + "]");
             }
 
-            // Auto-naming only allowed for validator and view types (and not abstract at root)
+            // Auto-naming only allowed for the types in isAutoNamingType (validator, view,
+            // source, identity) and not abstract at root.
             if (isAutoNamingType(typeName) &&
                 !(isRoot && Boolean.TRUE.equals(isAbstract))) {
                 // Generate sequential name based on subtype if available, otherwise use type

server/java/metadata/src/main/java/com/metaobjects/loader/parser/json/CanonicalJsonParser.java

@@ -367,7 +367,7 @@ private void processNode(MetaData parent, String type, String subType,
         // type that follows the subType-as-name convention. Registry-driven: no
         // per-type hardcoding.
         //
-        // EXCEPTION: types that participate in auto-naming (validator, view, source)
+        // EXCEPTION: types that participate in auto-naming (validator, view, source, identity)
         // skip this fallback. They receive a sequential auto-name from
         // createOrOverlayMetaData (rdb1, rdb2, …) and the serializer's
         // isAutoGeneratedName check suppresses emission of that auto-name on the way