🐛 Compiled Python protobuf files not regenerated after adding org field to FeatureView.proto (sdk/python/feast/protos/feast/core/FeatureView_pb2.py:22)

The .proto file adds string org = 19 to FeatureViewSpec, but the compiled Python protobuf files (FeatureView_pb2.py and FeatureView_pb2.pyi) were not regenerated. The FeatureView_pb2.pyi shows no ORG_FIELD_NUMBER, no org attribute, and no org parameter in __init__. The serialized descriptor in FeatureView_pb2.py still only covers fields up to version (field 18).

This causes runtime failures in two places:

1. to_proto_spec() at sdk/python/feast/feature_view.py:495 passes org=self.org to FeatureViewSpecProto(...), which will raise ValueError because the proto descriptor doesn't know about org.
2. _from_proto_internal() at sdk/python/feast/feature_view.py:622 and sdk/python/feast/feature_view.py:645 reads feature_view_proto.spec.org, which will raise AttributeError.

This also violates the AGENTS.md rule: "Recompile protos after making changes to .proto files."

🐛 Registry _update_metadata_fields does not update org, silently dropping org-only changes (sdk/python/feast/infra/registry/registry.py:549)

When a user changes only the org field of a feature view (without changing schema or UDF), _schema_or_udf_changed returns False (since none of the _schema_or_udf_changed overrides check org), so the code enters the _update_metadata_fields path at sdk/python/feast/infra/registry/registry.py:788. However, _update_metadata_fields updates description, tags, and owner (line 546-549) but never updates org. This means the org change is silently dropped during feast apply. The field is treated identically to owner everywhere else (constructor, __eq__, to_proto, from_proto, __copy__), so it should also be updated here alongside owner.