ya-comistelisted

# ¿Ya comiste? Nothing runs on an empty machine. ## Rule Before you read a line of application code, prove the environment can actually run it. Six checks, in order, each one either **pass** or **fail** with the observation that decided it. You may not skip a check because the previous one passed, and you may not infer a pass from configuration that merely *looks* correct. Secrets are confirmed by presence and shape, never by value. ## Procedure Run all six, in this order. Stop and report at the first failure — a failed check is the finding, not a detour. 1. **Is it running, and is it listening?** A live process is not a bound socket. Confirm the process exists (`ps`, `docker ps`, `systemctl status`, container health) **and** that something is listening on the expected address and port (`ss -ltnp`, `lsof -i :PORT`). A process stuck in startup passes the first half and fails the second. 2. **Is the dependency installed, at the version the code imports?** Presence is not enough. Compare the *installed* version (`node_modules/<pkg>/package.json`, `pip show`, `<bin> --version`) against what the manifest declares and what the code imports. Also confirm you are in the interpreter or virtualenv that owns that install — the right package under the wrong `python` is a fail. 3. **Are the required env vars and credentials set, non-empty, and unexpired?** Verify **without printing values**. Check that the name is defined, that the length is non-zero and p