2.0 KiB
Executable File
Архив исходника Broker
Историческая копия до очистки репозитория 2026-10-16. Источник: mallexxx/execution-broker, commit ae92c15d31c8396789765cebf82f7971d6f4cb12, файл docs/ipad-deployment-plan.md. Старые статусы и deployment pins ниже не заменяют актуальную personal/projects/balda/execution-broker.
Local-agent iPad deployment scenario (reference)
Ownership: a local agent/project workflow, outside Execution Broker's release scope. This repository contains this reference note, not an iPad implementation. No iPad-specific actions or application logic belong in Broker.
The existing macOS VM build of the iOS 9.3 armv7 app does not prove installation or launch on a physical device. The scenario owns its remaining work:
- Build the app and sign it with the project's selected signing tool; verify the signature and bundle identifier.
- Obtain the verified build artifact. If Broker ran the build, use its generic authenticated artifact API and check the artifact digest.
- Use the local agent's configured SSH/device tools to upload, install with the device's available installer, verify the installed bundle, unlock and launch. Select compatibility flags from that device's actual requirements.
- Check each outcome and reconcile the device after a disconnect before retrying a mutation. Report build and deployment outcomes separately.
Connection setup, device credentials, project scripts and approvals belong to that scenario's existing local-agent configuration. This note introduces no new global permission policy and does not require the scenario to use Broker for SSH or installation.
Broker can supply reusable disposable execution, tool provisioning and artifact transport. Any future generic remote-action API is a separately scoped feature in the Broker work plan, not a prerequisite for this scenario. Physical iPad acceptance does not block a Broker release.