Repository navigation
Reconcile exact-source project runners with governed execution - #36
Draft
echoomegaprime wants to merge 1 commit into
Conversation
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.
Objective
Reconcile source-bound project runners with the newer governed execution and recovery lineage. The API and worker select the same operator-owned tenant/project/repository/exact-source binding, verify dependency hashes before customer execution, and commit that binding to the measured environment. Other repositories retain the default restricted sandbox; callers cannot select an image or replace the validated journey.
This draft is stacked on PR31,
agent/certforge-ecf-release-reconcile-20261027at4878c04fc044f16fa917f473b965cacd62d48609. It ports the existing PR33 project-binding delta while preserving the newer operator-input circuit, subscriber claims, tenant isolation, intake recovery, signing and deployment protections. The new binding rejection uses the existing bounded tenant retry delay. Real Windows acceptance also exposed transaction-only SQLite contexts that retained owned handles; explicit closure preserves commit/rollback and strict cleanup.Evidence
95bfed62905543c061414a5149b471605f51c65b; treec099925fccb08a7e9b1cbe787bcc3cc7c5f76e67.Security and release impact
This is source delivery only. No running service, live SDK registration, runtime profile, scope, trust root, signing key or current report renewal changed. Install the matching API/worker/dispatcher, generated SDK contract and paired App caller only through the existing release path. Actual image qualification, App-principal/project ownership, profile admission, staging acceptance and independent exact-SHA certification remain required before installation, merge or deployment.