{"version":"2.1.234","anchor":"assorted-small-behaviour-changes","canonical_anchor":"assorted-small-behaviour-changes","heading":"Assorted small behaviour changes","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/assorted-small-behaviour-changes","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Assorted small behaviour changes\n\nSmall fixes, including permission prompts falling back to a tool's registered name when the display name is empty.\n\n**What**\n\nA handful of unrelated touch-ups, none of them behind a flag. The one you might notice: a permission prompt now falls back to the tool's registered name when the tool produces an empty display name.\n\n**Details**\n\n- GitHub PR events gained `reopened` alongside `auto-merge-enabled`.\n- Adoption telemetry reports a new `adopted_frame_live` count; message-send records carry an optional `source`; artifact file metadata gained `rendered_locally`.\n- Publish-denied errors truncate the underlying error to 300 characters rather than including all of it.\n- A settings module exports a reporter for an SDK inline setting dropped because the inline settings blob failed to parse. It is exported but nothing in this build calls it.\n\n**Evidence**\n\n`adopted_frame_live`\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}