palarran-vps-manage

Topics in the source

• /palarran:vps:manage {operation} [repository-url] [--plan]

Read the target INDEX, accepted decisions, applicable AGENTS, decision memory, and global memory cycle. Recall bounded relevant evidence before work; publish only verified sanitized deduplicated findings afterward. --plan has no network calls/publication; an outage does not block local planning. Mandatory memory guides: overview, sources, architecture, contract, operations, workflow. Also read infrastructure workflow, security/network and storage/recovery guides. 1. Identify the exact operation and existing user authorization. Credentials or a previous deployment do not authorize unrelated changes. For deploy , follow the mandatory application stack workflow: inspect the application and host, prepare its required stack, then apply only the concrete authorized plan. --plan does not clone/fetch, SSH or execute application code. 2. In execution scope, inspect workloads, ports, disk, OS and runtime read-only. Prepare a deployment plan with immutable source/image subjects, affected resources, prerequisites, backups, rollback and independent tests. Record rationale before dependent changes. Preserve the existing application stack and services. 3. Complete reviewable configs before any mi

This is an excerpt. Refer to the complete source and its current requirements.