@assertrx/dino 1.0.5 → 1.0.7

package/README.md

@@ -15,7 +15,7 @@ An Automated Verification agent based on Pi Harness
 | Skill | `playwright-core` | Battle-tested Playwright patterns for writing and debugging reliable E2E, API, component, visual, accessibility, and security tests |
 | Skill | `playwright-pom` | Page Object Model patterns for Playwright — when to use POM, how to structure page objects, and when fixtures or helpers are a better fit |
 | Skill | `mabl-mcp` | Guidance for using the mabl MCP bridge — workspace context, running tests, retrieving results, and handling OAuth auth |
-| Prompt | `create-pr` | Create a GitHub pull request for changes in the current workspace, installing `gh` and setting up git if needed |
+| Prompt | `create-pr` | Create a GitHub pull request for changes in the current workspace against a repository URL, installing `gh`, authenticating from an optional env file, and setting up git if needed |
 | Prompt | `generate-bdd-from-url` | Generate exhaustive Gherkin BDD scenarios for a single page by inspecting it with `playwright-cli` or Playwright MCP |
 | Prompt | `generate-pom-from-url` | Generate Playwright Page Object Models from a live URL using the Playwright MCP bridge (`browser_*` tools) |
 | Prompt | `generate-pom-from-url-cli` | Generate Playwright Page Object Models from a live URL using `playwright-cli` commands |
@@ -49,7 +49,7 @@ For browser-based tasks, **prefer the `playwright-cli` prompts**. They are more
 
 | Prompt | What it does | Example usage |
 |--------|--------------|---------------|
-| `/create-pr` | Create a GitHub pull request for changes in the current workspace, installing `gh` if needed. | `/create-pr` |
+| `/create-pr` | Create a GitHub pull request for changes in the current workspace against a given repository URL, installing `gh` and authenticating from an optional auth env file. | `/create-pr https://github.com/octocat/repo github-auth.env` |
 | `/generate-bdd-from-url` | Inspect a page and generate exhaustive Gherkin BDD scenarios for that page only. | `/generate-bdd-from-url https://example.com tests/features` |
 | `/generate-pom-from-url-cli` | Generate Playwright Page Object Models from a live URL using `playwright-cli` (**preferred**). | `/generate-pom-from-url-cli https://example.com tests/pom` |
 | `/generate-pom-from-url` | Generate Page Object Models from a live URL using the Playwright MCP bridge (**fallback only**). | `/generate-pom-from-url https://example.com tests/pom` |
@@ -310,7 +310,7 @@ This single script:
 1. Checks that Node.js is installed
 2. Installs `pi` globally if missing
 3. Installs `@assertrx/dino` via `pi install` if missing
-4. Starts the API server on port 3000
+4. Starts the API server on port 4003
 
 ### Manual setup
 
@@ -367,7 +367,7 @@ All POST bodies accept auth/model options, `cwd` (workspace directory, defaults
 | Prompt name | Required params |
 |-------------|---------------|
 | `setup-playwright` | _none_ |
-| `create-pr` | _none_ |
+| `create-pr` | _none_ (optional: `repoUrl`, `authEnvFile`) |
 | `generate-pom-from-url` | `url` |
 | `generate-pom-from-url-cli` | `url` |
 | `generate-bdd-from-url` | `url` |
@@ -378,28 +378,28 @@ All POST bodies accept auth/model options, `cwd` (workspace directory, defaults
 
 ```bash
 # List all prompts
-curl http://localhost:3000/api/prompts
+curl http://localhost:4003/api/prompts
 
 # Discover providers and their auth status
-curl http://localhost:3000/api/providers
+curl http://localhost:4003/api/providers
 
 # List models available to the server (optionally per provider)
-curl http://localhost:3000/api/models
-curl "http://localhost:3000/api/models?provider=anthropic"
+curl http://localhost:4003/api/models
+curl "http://localhost:4003/api/models?provider=anthropic"
 
 # Execute a prompt (SSE streaming, auth from env vars)
-curl -X POST http://localhost:3000/api/prompts/setup-playwright \
+curl -X POST http://localhost:4003/api/prompts/setup-playwright \
   -H "Content-Type: application/json" \
   -d '{"cwd": "/path/to/workspace"}'
 
 # Execute with a single provider key + model selection
 # (env: export OPENAI_API_KEY=sk-... then:)
-curl -X POST http://localhost:3000/api/prompts/setup-playwright \
+curl -X POST http://localhost:4003/api/prompts/setup-playwright \
   -H "Content-Type: application/json" \
   -d '{"cwd": "/path/to/workspace", "model": "openai/gpt-5.2"}'
 
 # Execute with multiple per-request API keys and an explicit model
-curl -X POST http://localhost:3000/api/prompts/setup-playwright \
+curl -X POST http://localhost:4003/api/prompts/setup-playwright \
   -H "Content-Type: application/json" \
   -d '{
     "cwd": "/path/to/workspace",
@@ -408,7 +408,7 @@ curl -X POST http://localhost:3000/api/prompts/setup-playwright \
   }'
 
 # Execute with URL parameter (non-streaming JSON response)
-curl -X POST http://localhost:3000/api/prompts/generate-pom-from-url-cli \
+curl -X POST http://localhost:4003/api/prompts/generate-pom-from-url-cli \
   -H "Content-Type: application/json" \
   -d '{"url": "https://example.com", "outputDir": "tests/pom", "stream": false}'
 ```
@@ -439,7 +439,7 @@ event: error      → {"message": "..."}      # error
 
 | Variable | Default | Description |
 |----------|---------|-------------|
-| `PORT` | `3000` | Server port |
+| `PORT` | `4003` | Server port |
 | `HOST` | `0.0.0.0` | Server host |
 | Provider env vars | — | Any provider's standard env var (e.g. `ANTHROPIC_API_KEY`, `OPENAI_API_KEY`, `GEMINI_API_KEY`); per-request `apiKeys`/`apiKey` override these |
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@assertrx/dino",
-  "version": "1.0.5",
+  "version": "1.0.7",
   "description": "A friendly purple dinosaur pi package with a custom TUI header, theme, and Playwright skills.",
   "keywords": [
     "pi-package"

package/prompts/create-pr.md

@@ -1,8 +1,14 @@
 ---
-description: Create a GitHub PR for current changes, installing gh and git setup if needed
+description: Create a GitHub PR for current changes using a repository URL and optional auth env file
+argument-hint: "[repo-url] [auth-env-file]"
 ---
 
-Create a GitHub pull request for the changes in the current workspace. Install the GitHub CLI (`gh`) if it is missing, and handle both existing git repos and brand-new projects.
+Create a GitHub pull request for the changes in the current workspace, targeting the GitHub repository at ${1:-the origin remote (or a repository you will be asked for)}. Install the GitHub CLI (`gh`) if it is missing, and handle both existing git repos and brand-new projects.
+
+## Arguments
+
+- `$1` — GitHub repository URL (e.g. `https://github.com/octocat/repo`, `git@github.com:octocat/repo.git`, or `owner/repo`). If empty, fall back to the existing `origin` remote; if there is none, ask the user.
+- `$2` — optional env file with GitHub login details (see **Authentication**).
 
 ## Steps
 
@@ -17,11 +23,48 @@ Create a GitHub pull request for the changes in the current workspace. Install t
      - **Fedora / RHEL**: `sudo dnf install -y gh`
    - After installing, verify with `gh --version`.
 
-2. **Check `gh` authentication**.
-   - Run `gh auth status`.
-   - If not authenticated, ask the user to run `gh auth login` manually (do not paste tokens into chat). Do not proceed until authenticated.
+2. **Authenticate `gh`**.
+
+### Preferred: auth env file (`$2`)
+
+If `$2` was provided:
+
+- Verify the file exists before use; if it is missing, report that and fall back to existing `gh` authentication.
+- The env file should contain variables such as:
+  ```bash
+  GITHUB_TOKEN=ghp_xxxxxxxxxxxxxxxxxxxx
+  GITHUB_USERNAME=octocat
+  GIT_USER_NAME=Octo Cat
+  GIT_USER_EMAIL=octocat@example.com
+  ```
+  `GITHUB_TOKEN` (a personal access token with repo scope) is required; the remaining variables are used for git identity.
+- Load the file and authenticate in a single bash command, and **do not echo, log, or persist the values anywhere**:
+  ```bash
+  set -a; . <auth-env-file>; set +a
+  printf '%s' "$GITHUB_TOKEN" | gh auth login --with-token
+  gh auth setup-git
+  gh auth status
+  ```
+- `gh auth setup-git` configures git's credential helper so `git push` over HTTPS works without embedding the token in remote URLs.
+- Never print the token, never write it into git config or remote URLs, and never commit the env file. Make sure it is listed in `.gitignore` if it lives inside the workspace.
+
+### Fallback: existing `gh` authentication
+
+If no env file was provided:
+
+- Run `gh auth status`.
+- If not authenticated, ask the user to run `gh auth login` manually (do not paste tokens into chat). Do not proceed until authenticated.
+
+3. **Resolve the target repository**.
+   - Normalize `$1` to `owner/repo` (accept `https://github.com/owner/repo.git`, `git@github.com:owner/repo.git`, or `owner/repo`).
+   - If `$1` is empty, use the existing `origin` remote (`git remote get-url origin`).
+   - If neither exists, ask the user for the repository URL before proceeding.
+   - Determine the default (base) branch of the target repository:
+     ```bash
+     gh repo view <owner>/<repo> --json defaultBranchRef --jq .defaultBranchRef.name
+     ```
 
-3. **Detect git project state**.
+4. **Detect git project state**.
    - Check whether `.git` exists in the current workspace.
 
 ### A. Existing git project
@@ -32,23 +75,35 @@ If `.git` exists:
    - Run `git status --short` to see modified/untracked files.
    - Show the user a concise summary of the changes.
 
-2. **Prepare a branch**.
+2. **Point the remote at the target repository**.
+   - If `$1` was provided:
+     - If no `origin` remote exists, run `git remote add origin <repo-url>`.
+     - If `origin` points elsewhere, run `git remote set-url origin <repo-url>` (tell the user before changing it).
+   - If `$1` is empty, keep the existing `origin` as-is.
+
+3. **Prepare a branch**.
    - Get the current branch with `git branch --show-current`.
-   - If currently on `main` or `master`, create and switch to a feature branch:
+   - If currently on the default branch (`main`/`master`), create and switch to a feature branch:
      ```bash
      git checkout -b update/<short-description>
      ```
    - Use a descriptive branch name based on the changes.
 
-3. **Configure git identity if needed**.
+4. **Configure git identity if needed**.
    - Run `git config user.name` and `git config user.email`.
-   - If either is missing, ask the user for a name and email, then set them locally:
+   - If either is missing and an auth env file was provided, source it in a single bash command and set the identity locally from `GIT_USER_NAME`/`GIT_USER_EMAIL` (fall back to `GITHUB_USERNAME` for the name):
+     ```bash
+     set -a; . <auth-env-file>; set +a
+     git config user.name "${GIT_USER_NAME:-$GITHUB_USERNAME}"
+     git config user.email "$GIT_USER_EMAIL"
+     ```
+   - Otherwise, ask the user for a name and email, then set them locally:
      ```bash
      git config user.name "Name"
      git config user.email "email@example.com"
      ```
 
-4. **Commit and push**.
+5. **Commit and push**.
    - Stage the relevant changes with `git add`.
    - Commit with a clear message. Ask the user for a message if one is not obvious, or use a sensible default summarizing the changes.
    - Push the branch:
@@ -56,32 +111,45 @@ If `.git` exists:
      git push -u origin <branch-name>
      ```
 
-5. **Create the pull request**.
-   - Use `gh pr create` with non-interactive flags:
+6. **Create the pull request**.
+   - Use `gh pr create` with non-interactive flags against the target repository:
      ```bash
-     gh pr create --title "<title>" --body "<body>" --base <base-branch>
+     gh pr create --repo <owner>/<repo> --title "<title>" --body "<body>" --base <base-branch>
      ```
    - Derive the PR title and body from the commit message and changed files.
-   - If a PR already exists for this branch, run `gh pr view <branch>` and report the URL instead.
+   - If a PR already exists for this branch, run `gh pr view <branch> --repo <owner>/<repo>` and report the URL instead.
 
 ### B. New project without git
 
 If `.git` does not exist:
 
-1. **Ask the user** for:
-   - The desired GitHub repository name.
-   - Whether it should be public or private.
-   - The GitHub owner/organization (default to the authenticated user).
-
-2. **Create the remote repository**.
+1. **Resolve the repository**.
+   - If `$1` was provided, use its `owner/repo` (do not ask the user).
+     - Check whether the repository already exists with `gh repo view <owner>/<repo>`.
+     - If it does not exist, ask whether it should be public or private, then create it:
+       ```bash
+       gh repo create <owner>/<repo> --<public|private>
+       ```
+     - Ask the user before creating a public repo.
+   - If `$1` is empty, **ask the user** for:
+     - The desired GitHub repository name (or full URL).
+     - Whether it should be public or private.
+     - The GitHub owner/organization (default to the authenticated user).
+     - Then create the remote repository:
+       ```bash
+       gh repo create <owner>/<repo> --<public|private>
+       ```
+
+2. **Initialize git and the remote**.
    - Run:
      ```bash
-     gh repo create <owner>/<repo> --<public|private> --source=. --remote=origin --push
+     git init -b main
+     git remote add origin <repo-url>
      ```
-   - If the user only provided a repo name without an owner, use `gh repo create <repo> --<public|private> --source=. --remote=origin --push`.
+   - If `main` is not the desired default branch name, use `master` or ask the user.
 
 3. **Configure git identity**.
-   - Ask for name and email if not already set globally.
+   - Ask for name and email if not already set globally, or use `GIT_USER_NAME`/`GIT_USER_EMAIL` (falling back to `GITHUB_USERNAME`) from the auth env file when provided (see step 4.4 in section A).
 
 4. **Commit the current code**.
    - Run:
@@ -90,21 +158,23 @@ If `.git` does not exist:
      git commit -m "Initial commit"
      git push -u origin main
      ```
-   - If `main` is not the default branch name, use `master` or ask the user.
 
 5. **Report the repository URL**.
 
 ## Rules
 
-- Never paste credentials or tokens into the chat.
+- Never paste credentials or tokens into the chat; never echo, log, or print the auth env file contents.
+- Never write the token into remote URLs or git config.
+- Do not run interactive `gh auth login` automatically; use the auth env file when provided, otherwise prompt the user to authenticate manually.
+- Ensure the auth env file is listed in `.gitignore` and never committed; suggest deleting it when the session is complete.
 - Ask the user before creating a public repo if privacy matters.
-- Do not run `gh auth login` automatically; prompt the user to authenticate manually.
 - Do not overwrite or ignore local git configuration without asking.
 - If there are no changes to commit, report that and stop.
 - Keep the PR title/body concise and relevant to the actual changes.
 
 After completing, summarize:
 - Whether `gh` was installed or already present.
+- How authentication was handled (auth env file or existing `gh` login).
 - The repository and branch used.
 - The commit message and PR URL (if created).
 - Any errors or manual steps the user still needs to take.

package/scripts/.playwright-mcp/console-2026-08-27T21-43-04-193Z.log

@@ -0,0 +1,9 @@
+[     261ms] [VERBOSE] [DOM] Input elements should have autocomplete attributes (suggested: "current-password"): (More info: https://goo.gl/9p2vKq) %o @ https://www.saucedemo.com/:0
+[     273ms] [ERROR] Failed to load resource: the server responded with a status of 401 (Unauthorized) @ https://events.backtrace.io/api/summed-events/submit?universe=UNIVERSE&token=TOKEN:0
+[    1303ms] [ERROR] Failed to load resource: the server responded with a status of 401 (Unauthorized) @ https://events.backtrace.io/api/unique-events/submit?universe=UNIVERSE&token=TOKEN:0
+[   10394ms] [ERROR] Failed to load resource: the server responded with a status of 401 (Unauthorized) @ https://events.backtrace.io/api/summed-events/submit?universe=UNIVERSE&token=TOKEN:0
+[   11462ms] [ERROR] Failed to load resource: the server responded with a status of 401 (Unauthorized) @ https://events.backtrace.io/api/unique-events/submit?universe=UNIVERSE&token=TOKEN:0
+[   30324ms] [ERROR] Access to fetch at 'https://submit.backtrace.io/UNIVERSE/TOKEN/json' from origin 'https://www.saucedemo.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. @ https://www.saucedemo.com/:0
+[   30324ms] [ERROR] Failed to load resource: net::ERR_FAILED @ https://submit.backtrace.io/UNIVERSE/TOKEN/json:0
+[   30538ms] [ERROR] Failed to load resource: the server responded with a status of 401 (Unauthorized) @ https://events.backtrace.io/api/summed-events/submit?universe=UNIVERSE&token=TOKEN:0
+[   31620ms] [ERROR] Failed to load resource: the server responded with a status of 401 (Unauthorized) @ https://events.backtrace.io/api/unique-events/submit?universe=UNIVERSE&token=TOKEN:0

package/scripts/.playwright-mcp/console-2026-08-27T21-54-18-098Z.log

@@ -0,0 +1 @@
+[     289ms] [VERBOSE] [DOM] Input elements should have autocomplete attributes (suggested: "current-password"): (More info: https://goo.gl/9p2vKq) %o @ https://www.saucedemo.com/:0

package/scripts/.playwright-mcp/page-2026-08-27T21-43-04-389Z.yml

@@ -0,0 +1,14 @@
+- generic [ref=e3]:
+  - generic [ref=e4]: Swag Labs
+  - generic [ref=e5]:
+    - generic [ref=e9]:
+      - textbox "Username" [ref=e11]
+      - textbox "Password" [ref=e13]
+      - button "Login" [ref=e15] [cursor=pointer]
+    - generic [ref=e17]:
+      - generic [ref=e18]:
+        - heading "Accepted usernames are:" [level=4] [ref=e19]
+        - text: standard_userlocked_out_userproblem_userperformance_glitch_usererror_uservisual_user
+      - generic [ref=e20]:
+        - heading "Password for all users:" [level=4] [ref=e21]
+        - text: secret_sauce

package/scripts/.playwright-mcp/page-2026-08-27T21-43-35-033Z.yml

@@ -0,0 +1,17 @@
+- generic [ref=e3]:
+  - generic [ref=e4]: Swag Labs
+  - generic [ref=e5]:
+    - generic [ref=e9]:
+      - textbox "Username" [ref=e11]: invalid_user
+      - textbox "Password" [ref=e13]: wrong_password
+      - heading [level=3] [ref=e26]:
+        - button [ref=e27] [cursor=pointer]
+        - text: "Epic sadface: Username and password do not match any user in this service"
+      - button "Login" [active] [ref=e15] [cursor=pointer]
+    - generic [ref=e17]:
+      - generic [ref=e18]:
+        - heading "Accepted usernames are:" [level=4] [ref=e19]
+        - text: standard_userlocked_out_userproblem_userperformance_glitch_usererror_uservisual_user
+      - generic [ref=e20]:
+        - heading "Password for all users:" [level=4] [ref=e21]
+        - text: secret_sauce

package/scripts/.playwright-mcp/page-2026-08-27T21-54-18-321Z.yml

@@ -0,0 +1,14 @@
+- generic [ref=e3]:
+  - generic [ref=e4]: Swag Labs
+  - generic [ref=e5]:
+    - generic [ref=e9]:
+      - textbox "Username" [ref=e11]
+      - textbox "Password" [ref=e13]
+      - button "Login" [ref=e15] [cursor=pointer]
+    - generic [ref=e17]:
+      - generic [ref=e18]:
+        - heading "Accepted usernames are:" [level=4] [ref=e19]
+        - text: standard_userlocked_out_userproblem_userperformance_glitch_usererror_uservisual_user
+      - generic [ref=e20]:
+        - heading "Password for all users:" [level=4] [ref=e21]
+        - text: secret_sauce

package/scripts/.playwright-mcp/page-2026-08-27T21-54-38-840Z.yml

@@ -0,0 +1,17 @@
+- generic [ref=e3]:
+  - generic [ref=e4]: Swag Labs
+  - generic [ref=e5]:
+    - generic [ref=e9]:
+      - textbox "Username" [ref=e11]
+      - textbox "Password" [ref=e13]
+      - heading [level=3] [ref=e26]:
+        - button [ref=e27] [cursor=pointer]
+        - text: "Epic sadface: Username is required"
+      - button "Login" [active] [ref=e15] [cursor=pointer]
+    - generic [ref=e17]:
+      - generic [ref=e18]:
+        - heading "Accepted usernames are:" [level=4] [ref=e19]
+        - text: standard_userlocked_out_userproblem_userperformance_glitch_usererror_uservisual_user
+      - generic [ref=e20]:
+        - heading "Password for all users:" [level=4] [ref=e21]
+        - text: secret_sauce

package/scripts/.playwright-mcp/page-2026-08-27T21-54-53-294Z.yml

@@ -0,0 +1,102 @@
+- generic [ref=e30]:
+  - generic [ref=e31]:
+    - generic [ref=e32]:
+      - generic [ref=e33]:
+        - generic [ref=e34]:
+          - button "Open Menu" [ref=e35] [cursor=pointer]
+          - img "Open Menu" [ref=e36]
+        - generic [ref=e37]: Swag Labs
+      - generic [ref=e41]:
+        - generic [ref=e42]: Products
+        - generic [ref=e44] [cursor=pointer]:
+          - generic [ref=e45]: Name (A to Z)
+          - combobox [ref=e46]:
+            - option "Name (A to Z)" [selected]
+            - option "Name (Z to A)"
+            - option "Price (low to high)"
+            - option "Price (high to low)"
+    - generic [ref=e50]:
+      - generic [ref=e51]:
+        - link [ref=e53] [cursor=pointer]:
+          - /url: "#"
+          - img "Sauce Labs Backpack" [ref=e54]
+        - generic [ref=e55]:
+          - generic [ref=e56]:
+            - link "Sauce Labs Backpack" [ref=e57] [cursor=pointer]:
+              - /url: "#"
+            - generic [ref=e59]: carry.allTheThings() with the sleek, streamlined Sly Pack that melds uncompromising style with unequaled laptop and tablet protection.
+          - generic [ref=e60]:
+            - generic [ref=e61]: $29.99
+            - button "Add to cart" [ref=e62] [cursor=pointer]
+      - generic [ref=e63]:
+        - link [ref=e65] [cursor=pointer]:
+          - /url: "#"
+          - img "Sauce Labs Bike Light" [ref=e66]
+        - generic [ref=e67]:
+          - generic [ref=e68]:
+            - link "Sauce Labs Bike Light" [ref=e69] [cursor=pointer]:
+              - /url: "#"
+            - generic [ref=e71]: A red light isn't the desired state in testing but it sure helps when riding your bike at night. Water-resistant with 3 lighting modes, 1 AAA battery included.
+          - generic [ref=e72]:
+            - generic [ref=e73]: $9.99
+            - button "Add to cart" [ref=e74] [cursor=pointer]
+      - generic [ref=e75]:
+        - link [ref=e77] [cursor=pointer]:
+          - /url: "#"
+          - img "Sauce Labs Bolt T-Shirt" [ref=e78]
+        - generic [ref=e79]:
+          - generic [ref=e80]:
+            - link "Sauce Labs Bolt T-Shirt" [ref=e81] [cursor=pointer]:
+              - /url: "#"
+            - generic [ref=e83]: Get your testing superhero on with the Sauce Labs bolt T-shirt. From American Apparel, 100% ringspun combed cotton, heather gray with red bolt.
+          - generic [ref=e84]:
+            - generic [ref=e85]: $15.99
+            - button "Add to cart" [ref=e86] [cursor=pointer]
+      - generic [ref=e87]:
+        - link [ref=e89] [cursor=pointer]:
+          - /url: "#"
+          - img "Sauce Labs Fleece Jacket" [ref=e90]
+        - generic [ref=e91]:
+          - generic [ref=e92]:
+            - link "Sauce Labs Fleece Jacket" [ref=e93] [cursor=pointer]:
+              - /url: "#"
+            - generic [ref=e95]: It's not every day that you come across a midweight quarter-zip fleece jacket capable of handling everything from a relaxing day outdoors to a busy day at the office.
+          - generic [ref=e96]:
+            - generic [ref=e97]: $49.99
+            - button "Add to cart" [ref=e98] [cursor=pointer]
+      - generic [ref=e99]:
+        - link [ref=e101] [cursor=pointer]:
+          - /url: "#"
+          - img "Sauce Labs Onesie" [ref=e102]
+        - generic [ref=e103]:
+          - generic [ref=e104]:
+            - link "Sauce Labs Onesie" [ref=e105] [cursor=pointer]:
+              - /url: "#"
+            - generic [ref=e107]: Rib snap infant onesie for the junior automation engineer in development. Reinforced 3-snap bottom closure, two-needle hemmed sleeved and bottom won't unravel.
+          - generic [ref=e108]:
+            - generic [ref=e109]: $7.99
+            - button "Add to cart" [ref=e110] [cursor=pointer]
+      - generic [ref=e111]:
+        - link [ref=e113] [cursor=pointer]:
+          - /url: "#"
+          - img "Test.allTheThings() T-Shirt (Red)" [ref=e114]
+        - generic [ref=e115]:
+          - generic [ref=e116]:
+            - link "Test.allTheThings() T-Shirt (Red)" [ref=e117] [cursor=pointer]:
+              - /url: "#"
+            - generic [ref=e119]: This classic Sauce Labs t-shirt is perfect to wear when cozying up to your keyboard to automate a few tests. Super-soft and comfy ringspun combed cotton.
+          - generic [ref=e120]:
+            - generic [ref=e121]: $15.99
+            - button "Add to cart" [ref=e122] [cursor=pointer]
+  - contentinfo [ref=e123]:
+    - list [ref=e124]:
+      - listitem [ref=e125]:
+        - link "Twitter" [ref=e126] [cursor=pointer]:
+          - /url: https://twitter.com/saucelabs
+      - listitem [ref=e127]:
+        - link "Facebook" [ref=e128] [cursor=pointer]:
+          - /url: https://www.facebook.com/saucelabs
+      - listitem [ref=e129]:
+        - link "LinkedIn" [ref=e130] [cursor=pointer]:
+          - /url: https://www.linkedin.com/company/sauce-labs/
+    - generic [ref=e131]: © 2026 Sauce Labs. All Rights Reserved. Terms of Service | Privacy Policy

package/scripts/api-server.mjs

@@ -28,7 +28,10 @@ const PROMPT_REGISTRY = {
   },
   "create-pr": {
     file: "create-pr.md",
-    params: [],
+    params: [
+      { name: "repoUrl", required: false, description: "GitHub repository URL (https://github.com/owner/repo, owner/repo, or git@ URL; default: existing origin remote)" },
+      { name: "authEnvFile", required: false, description: "Env file with GitHub login (GITHUB_TOKEN, GITHUB_USERNAME, GIT_USER_NAME, GIT_USER_EMAIL)" },
+    ],
     description: "Create a GitHub pull request for changes in the current workspace",
   },
   "generate-pom-from-url": {
@@ -542,7 +545,7 @@ app.post("/api/prompts/:name", async (request, reply) => {
 });
 
 // ── Start server ───────────────────────────────────────────────────────────
-const PORT = parseInt(process.env.PORT || "3000", 10);
+const PORT = parseInt(process.env.PORT || "4003", 10);
 const HOST = process.env.HOST || "0.0.0.0";
 
 try {

package/scripts/setup-dino-api.bat

@@ -61,7 +61,7 @@ echo [4/4] Starting Dino API server...
 echo.
 
 :: Defaults — override via env vars
-if "%PORT%"=="" set PORT=3000
+if "%PORT%"=="" set PORT=4003
 if "%HOST%"=="" set HOST=0.0.0.0
 
 echo           Port: %PORT%

package/scripts/setup-dino-api.sh

@@ -40,7 +40,7 @@ fi
 echo "[4/4] Starting Dino API server..."
 echo ""
 
-PORT="${PORT:-3000}"
+PORT="${PORT:-4003}"
 HOST="${HOST:-0.0.0.0}"
 
 echo "       Port: ${PORT}"

package/scripts/start-dino-server.bat

@@ -10,7 +10,7 @@ if not exist "%DINO_DIR%" (
     exit /b 1
 )
 
-echo Starting Dino API server on port %PORT% (default: 3000)...
+echo Starting Dino API server on port %PORT% (default: 4003)...
 
 :: The published npm package may not include api-server.mjs, so fall back
 :: to the local source copy when this script is run from the Dino repo.

package/scripts/start-dino-server.sh

@@ -12,5 +12,5 @@ if [ ! -d "${DINO_DIR}" ]; then
     exit 1
 fi
 
-echo "Starting Dino API server on port ${PORT:-3000}..."
+echo "Starting Dino API server on port ${PORT:-4003}..."
 exec node "${DINO_DIR}/scripts/api-server.mjs"