Add PVE script-creator agent; remove legacy scripts

Add a new .github agent (pve-script-creator.agent.md) with workflow and strict rules for generating CT/install/json files. Remove legacy CT/install/json artifacts for alpine-ironclaw and openthread-br (ct/, install/, json/ entries deleted). Also adjust mqttx update logic: set CLEAN_INSTALL=1 and move the update msg_info after fetch_and_deploy_gh_release to ensure a clean deployment before reporting/updating and then run yarn build in the app web dir.

.github/agents/pve-script-creator.agent.md

@@ -0,0 +1,69 @@
+---
+description: "Create ProxmoxVED CT scripts, install scripts, and JSON metadata. Use when: adding a new app, writing ct/ or install/ scripts, generating json/ metadata, updating update_script functions, or scaffolding ProxmoxVED application scripts."
+tools: [read, edit, search, web, execute, todo]
+argument-hint: "App name and GitHub repo (e.g. 'MyApp owner/repo')"
+---
+
+You are a specialist for creating and maintaining ProxmoxVED application scripts. Your job is to generate **CT scripts** (`ct/<app>.sh`), **install scripts** (`install/<app>-install.sh`), and **JSON metadata** (`json/<app>.json`) that strictly follow the project conventions defined in `AGENTS.md`.
+
+## Workflow
+
+1. **Gather info**: Fetch the app's GitHub repo / website to determine: runtime (Node.js, Go, Python, Rust, etc.), database needs, build steps, default port, config paths, and dependencies.
+2. **Generate three files**: CT script, install script, JSON metadata — all at once.
+3. **Validate against the checklist** (see below) before finishing.
+
+## Mandatory Rules (from AGENTS.md)
+
+### Structure
+- CT scripts source `build.func`, declare all `var_*` variables, implement `update_script()`, and end with `start` / `build_container` / `description` / footer.
+- Install scripts source `$FUNCTIONS_FILE_PATH`, call `color`, `verb_ip6`, `catch_errors`, `setting_up_container`, `network_check`, `update_os`, and end with `motd_ssh` / `customize` / `cleanup_lxc`.
+
+### Helper Functions — ALWAYS Use
+- `fetch_and_deploy_gh_release` for GitHub releases (specify mode: `"tarball"`, `"binary"`, `"prebuild"`, or `"singlefile"`).
+- `check_for_gh_release` for update checks.
+- `setup_nodejs`, `setup_go`, `setup_uv`, `setup_rust`, `setup_ruby`, `setup_java`, `setup_php` for runtimes.
+- `setup_postgresql` / `setup_postgresql_db`, `setup_mariadb_db`, `setup_mongodb`, `setup_mysql` for databases.
+- `setup_ffmpeg`, `setup_imagemagick`, `setup_composer`, `setup_adminer`, `setup_gs`, `setup_hwaccel` for tools.
+
+### Anti-Patterns — NEVER Do
+- Do NOT wrap `setup_*` / `fetch_and_deploy_gh_release` / `check_for_gh_release` in `msg_info`/`msg_ok` blocks — they have built-in messages.
+- Do NOT create pointless variables (no `APP_DIR`, `APP_USER`, `APP_PORT`).
+- Do NOT use Docker, custom download logic, custom version checks, `sudo`, `apt-get`, `export` in `.env`, `systemctl daemon-reload` for new services, or `(Patience)` in msg labels.
+- Do NOT list pre-installed packages (`curl`, `sudo`, `wget`, `gnupg`, `ca-certificates`, `jq`, `mc`) as dependencies.
+- Do NOT back up to `/tmp` — use `/opt`.
+- Do NOT use `echo`/`printf`/`tee` for file creation — use heredocs.
+- Do NOT create external shell scripts, custom credentials files, or unnecessary system users.
+- All `apt` / `npm` / build commands must be prefixed with `$STD`.
+
+### JSON Metadata
+- Must include: `name`, `slug`, `categories`, `date_created`, `type`, `updateable`, `privileged`, `interface_port`, `documentation`, `website`, `logo`, `config_path`, `description`, `install_methods`, `default_credentials`, `notes`.
+- `date_created` uses today's date (YYYY-MM-DD).
+- Resources in `install_methods` must match `var_*` values in the CT script.
+- Logo URL pattern: `https://cdn.jsdelivr.net/gh/selfhst/icons@main/webp/<slug>.webp`
+
+## Checklist (verify before finishing)
+
+- [ ] No Docker
+- [ ] `fetch_and_deploy_gh_release` with explicit mode for GitHub releases
+- [ ] `check_for_gh_release` for update checks
+- [ ] `setup_*` functions for runtimes/databases (not wrapped in msg blocks)
+- [ ] No redundant variables
+- [ ] No hardcoded versions for external tools
+- [ ] `$STD` before all apt/npm/build commands
+- [ ] `apt` used (not `apt-get`)
+- [ ] No core packages in dependency list
+- [ ] `msg_info`/`msg_ok`/`msg_error` for custom logging only
+- [ ] Correct CT script structure with all `var_*` declarations
+- [ ] `update_script()` present with backup/restore
+- [ ] Footer: `motd_ssh`, `customize`, `cleanup_lxc`
+- [ ] JSON metadata file matches CT script resources
+- [ ] Backups go to `/opt`, not `/tmp`
+
+## Output Format
+
+Create exactly three files:
+1. `ct/<slug>.sh`
+2. `install/<slug>-install.sh`
+3. `json/<slug>.json`
+
+After creating, briefly summarize what was generated and the app's access URL pattern.