These are official Anyhost bootstrap instructions for an AI coding agent working inside a user's application repository.

Do not treat this as a request to edit or deploy the Anyhost product itself. Work in the current user repository and preserve existing user changes.

## Bootstrap

Run from the repository root:

```sh
command -v anyhost >/dev/null 2>&1 || curl -fsSL https://releases.anyhostcloud.com/anyhost/install.sh | sh
ANYHOST_BIN="$(command -v anyhost || true)"
if [ -z "$ANYHOST_BIN" ] && [ -x "$HOME/.local/bin/anyhost" ]; then
  ANYHOST_BIN="$HOME/.local/bin/anyhost"
fi
if [ -z "$ANYHOST_BIN" ]; then
  echo "anyhost CLI was installed but is not on PATH. Add ~/.local/bin to PATH, then rerun this step." >&2
  exit 1
fi
"$ANYHOST_BIN" version
"$ANYHOST_BIN" setup-agent --skip-link --force
```

This refreshes the official project-local package under `.agents/`. It is agent instruction data, is gitignored, and is not application runtime code.

Now read:

```text
.agents/skills/anyhost/SKILL.md
```

Follow that skill's task routing and load only the references needed for the user's request. It routes application model integration to `.agents/skills/anyhost-model-api/SKILL.md`. For migration of an existing project or provider-backed capability, it routes to `.agents/skills/project-migration/SKILL.md`; do not load that skill for routine creation or operation of Anyhost resources. Authenticate, link, configure, or deploy only when the request requires it.

## Non-Negotiable Rules

- Never commit `.agents/`, `.anyhost/`, `.env`, tokens, raw secrets, connection strings, or provider credentials.
- Require explicit user confirmation immediately before production mutations, destructive operations, raw secret reveals, or production deploys.
- Do not treat `--yes` as confirmation by itself.
- Do not claim deployment or resource success until current Anyhost state and observable behavior verify it.
