Conflict resolution:
- Development QEMU: keep next's instance mode and prepared template images;
re-add v5 Podman worker Node profiles, Node seeding, Podman templates, and
the node-dev compose overlay through ./scripts/dev.
- Terminal: use next's token-based TerminalSessionService; add Node targets
with the v5 readiness and team checks at issue and redeem time.
- Sentinel: keep v5 Flux imports and next's SentinelSynchronized event; use
next's viewSentinel policy.
- Clusters page: follow next's no-placeholder rule for empty descriptions.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Add resumable VM provisioning and bootstrap development workers with Sentinel, Podman validation, mesh assignment, and network reconciliation.
Move the node inventory from Servers to Clusters and update cluster navigation.
