Agent.md

# Agent.md

## 1. Deployment Configuration

### Target Space
- **Profile:** `AUXteam`  
- **Space:** `Maxun`  
- **Full Identifier:** `AUXteam/Maxun`  
- **Frontend Port:** `7860` (mandatory for all Hugging Face Spaces)

### Deployment Method
- **Docker SDK** — for all other applications (recommended default for flexibility)

### HF Token
- The environment variable **`HF_TOKEN` will always be provided at execution time**.
- Never hardcode the token. Always read it from the environment.
- All monitoring and log‑streaming commands rely on `HF_TOKEN`.

### Required Files
- `Dockerfile`
- `README.md` with Hugging Face YAML frontmatter:
  ```yaml
  ---
  title: Maxun
  sdk: docker
  app_port: 7860
  ---
  ```
- `.hfignore` to exclude unnecessary files
- This `Agent.md` file (must be committed before deployment)

---

## 2. API Exposure and Documentation

### Mandatory Endpoints
Every deployment **must** expose:

- **`/health`**  
  - Returns HTTP 200 when the app is ready.  
  - Required for Hugging Face to transition the Space from *starting* → *running*.

- **`/api-docs`**  
  - Documents **all** available API endpoints.  
  - Must be reachable at:  
    `https://AUXteam-Maxun.hf.space/api-docs`

### Functional Endpoints
- **Method:** GET
- **Path:** `/api/runs/{run_id}/vision`
- **Purpose:** Get VNC connection details for a run
- **Request Example:** `GET /api/runs/1/vision`
- **Response Example:** 
  ```json
  {
    "status": true,
    "vnc_url": "http://localhost:6080/vnc.html?autoconnect=true&resize=scale",
    "has_vnc": true
  }
  ```

---

## 3. Deployment Workflow

### Standard Deployment Command
After any code change, run:

```bash
hf upload AUXteam/Maxun --repo-type=space
```

This command must be executed **after updating and committing Agent.md**.

### Deployment Steps
1. Ensure all code changes are committed.  
2. Ensure `Agent.md` is updated and committed.  
3. Run the upload command.  
4. Wait for the Space to build.  
5. Monitor logs (see next section).  
6. When the Space is running, execute all test cases.

### Continuous Deployment Rule
After **every** relevant edit (logic, dependencies, API changes):

- Update `Agent.md`
- Redeploy using the upload command
- Re-run all test cases
- Confirm `/health` and `/api-docs` are functional

This applies even for long-running projects.

---

## 4. Monitoring and Logs

### Build Logs (SSE)
```bash
curl -N \
  -H "Authorization: Bearer $HF_TOKEN" \
  "https://huggingface.co/api/spaces/AUXteam/Maxun/logs/build"
```

### Run Logs (SSE)
```bash
curl -N \
  -H "Authorization: Bearer $HF_TOKEN" \
  "https://huggingface.co/api/spaces/AUXteam/Maxun/logs/run"
```

### Notes
- If the Space stays in *starting* for too long, `/health` is usually failing.  
- If the Space times out after ~30 minutes, check logs immediately.  
- Fix issues, commit changes, redeploy.

---

## 5. Test Run Cases (Mandatory After Every Deployment)

These tests ensure the agentic system can verify the deployment automatically.

### 1. Health Check
```
GET https://AUXteam-Maxun.hf.space/health
Expected: HTTP 200, body: {"status": "ok"} or similar
```

### 2. API Docs Check
```
GET https://AUXteam-Maxun.hf.space/api-docs
Expected: HTTP 200, valid documentation UI or JSON spec
```

### 3. Functional Endpoint Tests
- Example request:
```
GET https://AUXteam-Maxun.hf.space/api/runs/1/vision
```
- Expected response structure:
```json
{
  "status": true,
  "vnc_url": "...",
  "has_vnc": true
}
```
- Validation criteria: HTTP 200, JSON response with keys `status`, `vnc_url`, `has_vnc`.

### 4. End-to-End Behaviour
- Confirm the UI loads (if applicable)
- Confirm API endpoints respond within reasonable time
- Confirm no errors appear in run logs

---

## 6. Maintenance Rules

- `Agent.md` must always reflect the **current** deployment configuration, API surface, and test cases.
- Any change to:
  - API routes  
  - Dockerfile  
  - Dependencies  
  - App logic  
  - Deployment method  
  requires updating this file.
- This file must be committed **before** every deployment.
- This file is the operational contract for autonomous agents interacting with the project.