Add fenced native operation runtime - #146
Merged
hotzenplotz5 merged 21 commits intoAug 7, 2026
Merged
Conversation
hotzenplotz5
marked this pull request as ready for review
August 7, 2026 12:30
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
vdr.native.proberuntime boundary defined by PR Define fenced native operation contract #145startingbefore local dispatch and reconcile ambiguous same-epoch dispatches without repeating native executionpluginInstanceEpochmutations=disabled,sideEffectClass=none, and the existingBackendNode.onlineauthority unchangedScope guards
This PR does not add timer, recording, search timer, remote, OSD, channel, EPG, configuration, or metadata mutation. It does not add provider ownership, provider selection, adapter fallback, a generic SVDRP tunnel, shell/process execution, a public listener, Phase 64 behavior, or
mutations=enabled.Final base and head
8150abc2c64c25f1a74a49378368b846f6484df08150abc2c64c25f1a74a49378368b846f6484df0f69b695144096f056c424f48818de310e4d98ddbagent/phase63-fenced-native-operation-runtimeFinal verification
VDR-Suite CI
Run
#7346on final headf69b695144096f056c424f48818de310e4d98ddb: all five jobs passed.fast-regression-test: successmake-test-audit: successpackaging-regression-test: successfrontend-regression-test: successdocs-check: successReal yaVDR acceptance
Acceptance passed on the exact final head with the previously built candidate artifacts reused only after strict ancestor, changed-file-scope, and SHA-256 verification.
Evidence directory:
/root/vdr-suite-phase63-fenced-native-operation-acceptance-f69b6951-retry-2Verified markers:
CANDIDATE_BUILD_REUSED=yesPHASE_63_FENCED_NATIVE_OPERATION_ACCEPTANCE=PASSBASELINE_NATIVE_PROBE_COMPLETED=yesCONTROL_PLANE_REPLAY_NO_NATIVE_REEXECUTION=yesLOST_LOCAL_RESPONSE_RECOVERED=yesPLUGIN_EPOCH_REPLAY_FENCED=yesNATIVE_RECEIPT_EVIDENCE_SEPARATE=yesNATIVE_RESULT_EVIDENCE_SEPARATE=yesAUTHORITATIVE_READBACK_VERIFIED=yesDAEMON_RESTART_PERSISTED=yesAGENT_RESTART_RECOVERED=yesVDR_NATIVE_STATE_UNCHANGED=yesEXISTING_AGENT_IDENTITY_PRESERVED=yesCREDENTIAL_GENERATION_PRESERVED=yesORIGINAL_CONFIGURATION_RESTORED=yesVDR_ACTIVE=yesDAEMON_ACTIVE=yesAGENT_ACTIVE=yesACCEPTANCE_RC=0,HOST_CONFIGURATION_UNCHANGED=yes,PHASE63_FINAL_ACCEPTANCE_WRAPPER=PASSCloseout state
The PR was marked Ready for review after successful final-head CI and real yaVDR acceptance. It has not been merged.