linux-development-vm-workflowlisted

# Linux Development VM Workflow ## Purpose Prepare one persistent Linux development environment whose lifecycle, host integrations, provenance, validation, and reset path are explicit. ## When To Use - Use for distro-specific builds, services, systemd or another init system, repeated shells, full-system tests, custom kernels, EFI boot, or GUI Linux. - Use to decide between `container machine`, Lima/Colima, and a full VM by required fidelity rather than product preference. - Do not use for a single portable application image; use the container owner skills. ## Single-Path Workflow 1. Consume the [virtualization shape record](../choose-macos-virtualization-shape/references/virtualization-shape-record.md). 2. Discover current official documentation and installed versions/help for every candidate tool. 3. Select the smallest adequate path: - `container machine`: OCI-backed persistent Linux, init/services, repeated interactive development - Lima/Colima adapter: tool-managed Linux environment when its documented lifecycle and integration match the task - full Virtualization framework VM: custom boot/kernel/disk/devices, full-system or GUI behavior, or tighter integration control 4. Record distro/image/kernel provenance, architecture, CPU, memory, disks, network, mounts, sockets, credentials, and expected lifetime. 5. Keep host home, writeable shares, SSH agent, credentials, clipboard, and unrestricted network opt-in. A development convenience is not a security bounda