Expose local Workspace Operations in SourceOS shell UX

[mdheller]

Purpose

Make sourceos-shell the local shell surface for showing and controlling SourceOS-local Workspace Operations: sync, terminal, browser, local agent-machine, model carry, and workstation state.

Context

The repository dossier identifies sourceos-shell as the SourceOS shell and user-interface plane. It must render Operation Plane state without becoming runtime or policy authority.

Required surfaces

• Local Operation Tray projection.
• Local Operation Inspector projection.
• File availability states: local, remote, syncing, conflicted, quarantined.
• Device identity/trust profile display.
• Sync status from sourceos-syncd.
• TurtleTerm operation integration entry points.
• BearBrowser operation integration entry points.
• Agent-machine operation integration entry points.
• Redacted diagnostics export entry point.

Required integrations

• SourceOS-Linux/sourceos-spec#87
• SociOS-Linux/workstation-contracts#28
• SourceOS-Linux/sourceos-syncd#3
• SourceOS-Linux/sourceos-devtools#19
• SourceOS-Linux/BearBrowser#20
• SourceOS-Linux/agent-machine#18
• SocioProphet/prophet-core-contracts#1
• SocioProphet/sociosphere#259

Acceptance criteria

• Shell can display operation/task state from contracts, not ad hoc local UI state.
• Shell can distinguish stored, quarantined, admitted, activated, syncing, conflicted, and failed states.
• Shell actions route through OperationCommand equivalents.
• Shell diagnostics export applies redaction policy.
• Shell does not own Policy Fabric or Operation Plane runtime logic.

Hard rule

SourceOS shell is a control surface and projection layer. It must not create hidden mutations or policy decisions outside the Operation Plane.

[mdheller]

@copilot please implement this as a bounded shell projection slice.

Scope:

• Add fixture-backed local Operation Tray and Operation Inspector projections, following this repo’s existing conventions.
• Display file availability states: local, remote, syncing, conflicted, quarantined.
• Add device identity/trust profile fixture projection.
• Add entry points or route stubs for sourceos-syncd, TurtleTerm, BearBrowser, agent-machine, and redacted diagnostics export.
• Shell actions should be represented as OperationCommand-shaped payloads, not hidden side effects.

Use current seams:

• SocioProphet/prophet-core-contracts#1 fixtures.
• SocioProphet/prophet-platform#376 command/snapshot shape.
• SociOS-Linux/workstation-contracts#28.
• SourceOS-Linux/sourceos-spec#87.
• SourceOS-Linux/sourceos-syncd#3.

Validation:

• Add tests/fixtures for tray summary, inspector detail, file availability states, conflict state, and diagnostic export entry point.
• Do not implement policy rules, runtime event log, sync daemon internals, browser runtime, terminal runtime, or agent-machine execution here.

PR evidence required:

• Summary of files changed.
• Validation commands run and output.
• Screenshot or textual fixture output if preview is unavailable.
• Explanation of how shell state is projected from operation contracts rather than invented locally.