Supported safe editing path for existing native Graphics from Premiere UXP / Hybrid

We are developing a Premiere UXP editing assistant. The recorded test environment is Premiere 26.5.2 on Apple Silicon, using the supplied Premiere C++ SDK 26.0 and UXP Hybrid SDK headers. We have successfully loaded a minimal Hybrid addon, called a function returning fixed metadata, and unloaded it. That probe did not access Premiere host APIs.

We need to preserve existing native Graphic text and styling while applying a narrowly scoped opacity animation to one explicitly reviewed timeline item. We want to avoid relying on undocumented APIs or bypassing host locking.

Could you clarify these supported contracts?

1. Hybrid host context: What supported entry point gives a Premiere UXP Hybrid addon access to SPBasicSuite and an appropriate live Project/Sequence/timeline context? The supplied generic addon initializer receives addon_env, exports, and addon_apis. We have not found the Premiere equivalent of Photoshop's host-specific entry point. If this access is not supported, please confirm the intended boundary.

2. Target identity and native Graphic text: Is there a supported stable identity for an individual VideoClipTrackItem that can be revalidated after reorder, duplicate, Undo, and save/reopen? What API reads the full text and styling of an existing native AE.ADBE Text Graphic, including mixed runs, font, color, stroke/shadow and text kind? Does the 27.0 beta MogrtText API cover this native Graphic type, or only particular MOGRT parameters?

3. Atomic validation and edit: Project.lockedAccess accepts a synchronous callback, but getSequence, clip bounds, and ComponentParam.getStartValue are asynchronous. What supported pattern validates the selected item's identity and expected previous values and then creates/executes Actions without an intervening edit race? A pre-read followed by a synchronous lock does not by itself establish that the pre-read is still current. Is there a conditional Action, revision token, or another supported transaction pattern?

4. Alternative C++ plugin types: The Control Surface entry point receives SPBasicSuite, while the public suite table lists Video Segment Suite for Exporters. Is there a supported C++ plugin type for the above live Graphic editing use case? If so, please identify the specific suite/header and target/thread lifetime requirements. We do not assume that command dispatch or render-node IDs provide an editing transaction or persistent clip identity.

Relevant references:
- https://developer.adobe.com/premiere-pro/uxp/plugins/hybrid-plugins/build/
- https://developer.adobe.com/premiere-pro/uxp/ppro-reference/classes/project#lockedaccess
- https://github.com/adobe/premierepro-types/commit/5df7d27dcc59cb4877e9ecc38229dc57738c0cea
- https://ppro-plugins.docsforadobe.dev/control-surfaces/control-surfaces/

A minimal official example or a confirmation that a capability is not currently supported would help us select the correct design. No customer project is required to discuss these API contracts.

[Moved to Premiere by a moderator］