# TermRemoteCtl

TermRemoteCtl is a personal remote coding controller for one Windows workstation.

## Workspace Layout
- apps/mobile_app: Flutter app for iPhone and Android
- apps/windows_agent: Windows resident agent
- docs: specifications, plans, and protocol notes

## Prerequisites
- Flutter 3.x
- .NET 8 SDK
- Windows 11 for the agent runtime

## Initial Setup
1. Run flutter create apps/mobile_app --platforms=android,ios --project-name term_remote_ctl
2. Run dotnet new sln -n TermRemoteCtl.Agent -o apps/windows_agent
3. Verify the generated workspace with `flutter --version` and `dotnet --version`
4. Begin implementation in `apps/mobile_app` and `apps/windows_agent` using the checked-in workspace files and protocol notes

## Verification

- `dotnet test apps/windows_agent/tests/TermRemoteCtl.Agent.Tests/TermRemoteCtl.Agent.Tests.csproj`
- `flutter test apps/mobile_app/test`
- `flutter test apps/mobile_app/integration_test`
- The Flutter `integration_test` suite may still require a supported local runtime target or device on the machine running it.

## Terminal Truth Source

The stable product path uses one rendering truth source:

- backend `restore` plus `output` provide the durable terminal data
- frontend `xterm` is the only visible renderer on the mainline
- local mobile snapshots are provisional cache only

Backend `screen_snapshot`, `screen_patch`, and `screen_sync` are experiment-only paths. They must stay behind an explicit opt-in switch and must not drive the default product terminal.