- Add startFeatureOperationEvent(name, operationKey, context) returning start event with vitalId
- Add succeedFeatureOperationEvent(name, operationKey, context) returning stop event without failureReason
- Add failFeatureOperationEvent(name, operationKey, failureReason, context) returning stop event with failureReason
- All factories use inline object literals with eventType first, matching existing convention
- UUID generated via CreateObject("roDeviceInfo").GetRandomUUID()

Co-Authored-By: Claude Opus 4.6 <[email protected]>

…spatch for operation methods

- Add 3 field declarations (startOperation, succeedOperation, failOperation) to RumAgent.xml
- Add 3 function declarations to RumAgent.xml interface
- Register 3 field observers in RumAgent.bs init()
- Add 3 dispatch branches in rumAgentLoop() event loop

Co-Authored-By: Claude Opus 4.6 <[email protected]>

…ation helpers

- Add startOperation, succeedOperation, failOperation public methods with input validation
- Add __onStartOperation, __onSucceedOperation, __onFailOperation private handlers
- Add __isValidOperationName, __isValidOperationKey, __isValidFailureReason helpers
- Validate blank names, blank operationKeys, and invalid failureReasons via ddLogError
- Accept invalid (nil) operationKey as valid for unkeyed operations

Co-Authored-By: Claude Opus 4.6 <[email protected]>

- 6 dispatch tests verifying startOperation, succeedOperation, failOperation delegate correctly to RumScope
- 6 validation tests covering blank names, whitespace names, nil keys, blank keys, whitespace keys, and invalid failure reasons

Co-Authored-By: Claude Opus 4.6 <[email protected]>

Add observeFieldScoped registrations and event loop dispatch branches
for startOperation, succeedOperation, and failOperation fields in
RumAgent, along with the corresponding XML field declarations.

Co-Authored-By: Claude Sonnet 4.6 <[email protected]>

Implement handleVitalEvent at the session scope level to construct and
write JSON payloads for start/succeed/fail feature operations. Includes:
- Active operation tracking with duplicate-start and missing-operation warnings
- Developer warning when a vital event is emitted without an active view
- Session renewal clears active operation state
- Guard against invalid rumScope before calling handleEvent

Co-Authored-By: Claude Sonnet 4.6 <[email protected]>

Add comprehensive tests for handleVitalEvent covering:
- Correct JSON payload construction for start/succeed/fail operations
- Keyed and unkeyed operation tracking
- Duplicate start warnings and missing-operation warnings
- No-active-view fallback behaviour
- Session renewal mid-operation clears state
- Context merging priority, Unicode names, long names, special characters

Co-Authored-By: Claude Sonnet 4.6 <[email protected]>

- Add OperationsScreen.xml with LabelList and messageLabel (matches DebugScreen pattern)
- Add OperationsScreen.bs with 7 menu items covering full operation API surface
- Timer-based delays: 2s content load auto-succeed, 1.5s login timeout
- Keyed operation demo with random key generation
- All calls use BrighterScript @. syntax with correct failOperation parameter order

…ation instrumentation

- Add operationsLabel and OperationsScreen component to MainScene.xml
- Update MainScene.bs with full navigation support (init, switchScreen, getScreenByName, getLabelByName, getNextScreen, getPreviousScreen)
- Navigation cycle: Home -> Video -> Network -> Debug -> Operations -> Home
- Add inline startOperation("playbackStart") to VideoScreen on play press
- Add onVideoStateChange: succeedOperation on "playing", failOperation on "error"
- unobserveField after completion to prevent duplicate calls