# AI Agent Instructions

This document provides workspace-level instructions for AI agents working anywhere under `/home/aw/code/cds`.

## Commit Approval

Always let the user review the proposed commit scope and commit message first, and wait for the user's explicit approval before creating any local git commit in this workspace.

## Repository Safety

- Never commit or push to the nested `galaxy-complete` repo under `/home/aw/code/cds/galaxy-complete` without the user's explicit approval.
- Never assume work in `/home/aw/code/cds` should be pushed to `rnd.cdsi.us.com`.

## ATVM Prep Script Guardrail

- Do not run `/root/atvm_prep/atvm_prep.py` unless the operator explicitly asks for an `atvm_prep` task.
- For any `atvm_prep` execution request, always show the planned command first and wait for explicit operator approval before running it.

## Exact VM Name Guardrail

- For VM power or maintenance requests, act only on the exact VM names provided by the operator.
- If any requested VM name is not found, stop and report it; do not infer, substitute, or search for replacement VMs unless the operator explicitly asks for that discovery step.

## ATVM Prep Mapping Defaults

- For `atvm_prep` requests in this workspace, infer common options from operator shorthand when intent is clear.
- Datastore shorthand mapping for `-n`:
  - `Gold` -> `AutomatedTest-VMBootImg-Gold`
  - `Gold2` -> `AutomatedTest-VMBootImg-Gold-2`
  - `ComputeMigration` (or `compute migration`) -> `AutomatedTest-VMBootImgComputeMigration-Gold`
- Client/ESXi pairing defaults:
  - `CDS1-ESX165` <-> `192.168.1.165`
  - `CDS1-ESX166` <-> `192.168.1.166`
- If only one of `-c` or `-e` is provided, auto-fill the paired value from this mapping.
- If both `-c` and `-e` are provided but conflict with mapping, stop and ask for confirmation before execution.