)]}'
{
  "commit": "2da25a0dcc89801e114e0af281a153e89667b5a4",
  "tree": "40bad4567c19df4c486ee41a26280ef2e502c8af",
  "parents": [
    "a21033b0870e30d833f344e37f51106ca9649302"
  ],
  "author": {
    "name": "Eric Stone",
    "email": "ecstone@fuchsia.infra.roller.google.com",
    "time": "Thu Dec 11 22:10:56 2025 -0800"
  },
  "committer": {
    "name": "Copybara-Service",
    "email": "copybara-worker@google.com",
    "time": "Thu Dec 11 22:13:28 2025 -0800"
  },
  "message": "[roll] Roll fuchsia [security] Add platform component_tree_config\n\nThis file will allow platform-defined components which use dynamic\nrouting features to tell Scrutiny how to incorporate their capabilities\ninto Scrutiny\u0027s model. In this current state, it enforces that code\nwhich dynamically handles capabilities be able to represent the set of\ncapabilities in this static config file.\n\nFor example, this is needed for config capabilities presented from a\ndynamic dictionary to successfully route for the structured config\nmodel.\n\nTo soft-migrate OOT usages, this change will add a new field to\nrepresent a list of component tree configs without removing the existing\nsingle-file field.\n\nOriginal-Bug: b/468009955\nOriginal-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1446188\nOriginal-Revision: c84911a1933f64c249fdf23dd9e8f5d95072df05\nGitOrigin-RevId: f85b720824f8db77c53320b7e0755f800a82ec4d\nChange-Id: Id42849f05db25d545183e4973d08fb4f8d6cb1af\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "be646c2b179c3a5c70877c50ccc2898107a46899",
      "old_mode": 33188,
      "old_path": "stem",
      "new_id": "0d212f243ee68f7e9c4176e99aaf4ecdb35966e9",
      "new_mode": 33188,
      "new_path": "stem"
    }
  ]
}