Define CloudShell FOG integration profile for TurtleTerm receipts and agent terminal workflows

[mdheller]

Summary

CloudShell FOG has matured into the browser/fog/cloud shell execution plane with session API, WSS PTY attach, placement metadata, audit events, OpenAPI contracts, and Kubernetes execution.

TurtleTerm has matured into the SourceOS policy-aware, agent-addressable terminal workbench with command lifecycle events and durable receipts.

We should define the integration boundary so TurtleTerm can serve as a local/operator/agent terminal surface for CloudShell FOG without duplicating receipt semantics.

Proposed scope

• Define how TurtleTerm command receipts relate to CloudShell FOG audit events.
• Define whether a CloudShell session can set or propagate SOURCEOS_TERMINAL_SESSION_ID and related SourceOS terminal environment variables.
• Define shared fields for actor, workspace, policy bundle, execution domain, command digest, placement, and runtime identity.
• Decide whether TurtleTerm owns the terminal receipt schema and CloudShell FOG references it, or whether a shared SourceOS terminal contract repo should own it.
• Add a docs/integration/cloudshell-fog.md profile or equivalent.

Acceptance criteria

• TurtleTerm documents how it integrates with CloudShell FOG.
• Schema ownership is explicit.
• A local TurtleTerm command receipt can be correlated to a CloudShell FOG session/audit trail where applicable.

[mdheller]

Addressed by merged work. PR #19 (Replay CloudShell FOG integration note on current main) landed docs/integration/cloudshell-fog.md and the receipt-context smoke test (test_cloudshell_fog_receipt_context.py), satisfying the integration profile and schema ownership requirements. PRs #31–33 (agent/cloudshell-fog-integration-*) captured the full CloudShell FOG integration branch content into main. The correlation path between local TurtleTerm command receipts and CloudShell FOG session/audit trails is now documented.