docs: add CloudShell FOG integration profile (current-main draft)#13
Draft
docs: add CloudShell FOG integration profile (current-main draft)#13
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.
Summary
Adds the TurtleTerm-side CloudShell FOG integration profile and receipt-context smoke test on a fresh branch from current
main.Why this replaces PR #3
The earlier PR #3 branch diverged heavily from
mainwhile upstream added TurtleTerm CloudFog, Superconscious, and Agent Machine bridge surfaces. This replacement branch starts from currentmainand replays only the integration artifacts plus the minimal current-main-safe fixes proven by CI triage.Included
docs/integration/cloudshell-fog.mdassets/sourceos/tests/test_cloudshell_fog_receipt_context.pyturtle-agentctl%installinvokes the staging helper throughbashIntegration scope
This PR documents and validates:
SOURCEOS_*environment propagation from CloudShell contextFollow-up tracking
Remaining repo-wide checks should stay tracked separately if they still fail: