td-ai-tools 1.3.4 → 1.3.6

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "td-ai-tools",
-  "version": "1.3.4",
+  "version": "1.3.6",
   "description": "Install agent skills and packs into your project",
   "type": "module",
   "scripts": {

package/skills/forge-cli/SKILL.md

@@ -1,22 +1,33 @@
 ---
 name: forge-cli
-version: 1.0.0
-description: Manage Laravel Forge servers, sites, and provisioned resources from the terminal with the Laravel Forge CLI, falling back to the Forge HTTP API (Statamic-relevant endpoints documented here) for anything the CLI does not cover. Use when the user wants to inspect Forge state, switch active servers, deploy sites, update environment variables, view logs, run remote commands, use Tinker, manage services like PHP, Nginx, daemons, and databases, or perform Statamic site setup tasks the CLI lacks a verb for (site/SSL/git/worker/scheduler/backup/recipe/composer-auth management).
+description: Manage Laravel Forge organizations, servers, sites, and provisioned resources with Forge CLI 2.x, falling back to the organization-scoped Forge HTTP API v2 for operations the CLI does not cover. Use for deploys, environment files, logs, remote commands, Tinker, PHP, Nginx, databases, background processes, sites, SSL, scheduled jobs, backups, recipes, or Composer credentials.
 ---
 
 # Laravel Forge CLI
 
 ## Core Workflow
 
-1. Start with `forge` to confirm the CLI is installed and to inspect available commands.
-2. Check the active server before making changes:
+1. Confirm the installed package and inspect the available commands:
 
 ```bash
+forge --version
+composer global show laravel/forge-cli
+forge list --raw
+```
+
+2. Check the active organization and server before making changes:
+
+```bash
+forge organization:current
+forge organization:list
+forge organization:switch organization-slug
 forge server:current
 forge server:list
 forge server:switch staging
 ```
 
+Switching organizations clears the active server. Select the server again after an organization switch.
+
 3. If the task needs SSH access, verify connectivity first:
 
 ```bash
@@ -36,7 +47,7 @@ forge site:list
 forge deploy
 forge deploy example.com
 forge deploy:logs
-forge deploy:logs 12345
+forge deploy:logs example.com
 ```
 
 ### Environment Variables
@@ -70,31 +81,34 @@ forge database:shell my-database-name --user=my-user
 forge php:status 8.5
 forge php:restart 8.5
 forge nginx:logs access
-forge daemon:restart
+forge background-process:list
+forge background-process:restart 12345
 ```
 
+`daemon:*` remains a legacy alias in CLI 2.x. Prefer `background-process:*`.
+
 ## Decision Guide
 
-- Need server context first: use `server:current`, `server:list`, or `server:switch`.
+- Need context first: use `organization:*`, then `server:*`.
 - Need site-level work: use `site:list`, `deploy`, `env:*`, `site:logs`, `command`, or `tinker`.
 - Need service health or maintenance: use `{resource}:status`, `{resource}:logs`, `{resource}:restart`, or `{resource}:shell`.
 - Need a secure shell on the box: confirm `ssh:test`, then use `forge ssh`.
-- Need something the CLI does not expose (creating sites, issuing SSL, wiring up workers, the Laravel scheduler, backups, recipes, Composer auth for Statamic Pro, etc.): drop down to the Forge HTTP API — see the API references below.
+- Need something the CLI does not expose (creating sites, issuing SSL, background-process creation, the Laravel scheduler, backups, recipes, Composer auth for Statamic Pro, etc.): use the Forge HTTP API v2 references below.
 
 ## When the CLI Is Not Enough
 
-The CLI is intentionally narrow. For Statamic site tasks it does not cover, call the Forge HTTP API directly. Authentication, IDs, and error handling are documented in [references/api-overview.md](references/api-overview.md); start there before reaching for an endpoint table.
+The CLI is intentionally narrow. For Statamic site tasks it does not cover, call the Forge HTTP API directly. Authentication, organization scope, IDs, pagination, and v1-to-v2 migration rules are documented in [references/api-v2-overview.md](references/api-v2-overview.md); start there.
 
 Picking the right reference:
 
-- Creating or reconfiguring a site, wiring a Git repo, editing the deployment script or Nginx, viewing deployment history, registering webhooks → [references/api-sites.md](references/api-sites.md).
-- Queue workers, generic daemons, scheduled jobs, the Laravel scheduler integration, maintenance mode → [references/api-workers-and-scheduler.md](references/api-workers-and-scheduler.md).
-- MySQL/Postgres databases, database users, scheduled backups, restores → [references/api-databases-and-backups.md](references/api-databases-and-backups.md).
-- Let's Encrypt or imported certificates, HTTP basic auth security rules (e.g. locking down `/cp`) → [references/api-ssl-and-security.md](references/api-ssl-and-security.md).
-- Installing/patching PHP, OPCache toggles, service start/stop/restart, server log files, saved Recipes, Composer auth for `composer.statamic.com` and other private repos → [references/api-php-services-recipes.md](references/api-php-services-recipes.md).
+- Sites, domains, deployment scripts and history, commands, logs, webhooks, deploy keys → [references/api-v2-sites.md](references/api-v2-sites.md).
+- Background processes, scheduled jobs, Laravel Scheduler, maintenance mode, and the removal of queue workers in v2 → [references/api-v2-processes-and-scheduler.md](references/api-v2-processes-and-scheduler.md).
+- Database schemas, database users, backups, and restores → [references/api-v2-databases-and-backups.md](references/api-v2-databases-and-backups.md).
+- Domain certificates and HTTP basic-auth security rules → [references/api-v2-certificates-and-security.md](references/api-v2-certificates-and-security.md).
+- PHP versions, service actions, recipes, and Composer credentials → [references/api-v2-php-services-recipes.md](references/api-v2-php-services-recipes.md).
 
-Operations not relevant to Statamic (WordPress installs, Horizon/Octane/Reverb/Pulse/Inertia SSR daemons, server provisioning, load balancers, deprecated MySQL endpoints) are deliberately omitted — fall back to the [official API docs](https://forge.laravel.com/api-documentation) if one of those comes up.
+The v2 route tables are not complete request-schema documentation. Before a mutating request, confirm the body in the [official API v2 documentation](https://laravel.com/forge/docs/api-reference/introduction) or the current `laravel/forge-sdk` 4.x source. Never substitute a remembered API v1 payload.
 
 ## Reference
 
-Read [references/command-reference.md](references/command-reference.md) when you need the fuller CLI command set, examples, or reminders about how the active server affects command behavior.
+Read [references/command-reference-v2.md](references/command-reference-v2.md) for the supported CLI 2.x command families and active-context behavior.

package/skills/forge-cli/references/api-v2-certificates-and-security.md

@@ -0,0 +1,28 @@
+# Forge API v2 — Certificates and Security Rules
+
+Paths are relative to `https://forge.laravel.com/api`; `{org}` is the organization slug.
+
+## Domain Certificates
+
+API v2 manages certificates beneath a specific site domain. Resolve the domain ID first; do not pass a hostname where `{domainId}` is expected.
+
+| Operation | Method | Path |
+| --- | --- | --- |
+| List domains | GET | `/orgs/{org}/servers/{serverId}/sites/{siteId}/domains` |
+| List / create certificates | GET / POST | `/orgs/{org}/servers/{serverId}/sites/{siteId}/domains/{domainId}/certificates` |
+| Get active certificate | GET | `/orgs/{org}/servers/{serverId}/sites/{siteId}/domains/{domainId}/certificates/active` |
+| Get / delete certificate | GET / DELETE | `/orgs/{org}/servers/{serverId}/sites/{siteId}/domains/{domainId}/certificates/{certificateId}` |
+| Perform certificate action | POST | `/orgs/{org}/servers/{serverId}/sites/{siteId}/domains/{domainId}/certificates/{certificateId}/actions` |
+
+Certificate creation and action payloads differ by certificate type and operation. Check the current v2 schema for Let's Encrypt, imported certificates, DNS validation, installation, and activation. The API v1 endpoints such as `/certificates/letsencrypt`, `/install`, and `/activate` must not be reused.
+
+Before replacing or deleting an active production certificate, verify the domain, certificate ID, renewal state, and rollback path.
+
+## Security Rules (HTTP Basic Auth)
+
+| Operation | Method | Path |
+| --- | --- | --- |
+| List / create | GET / POST | `/orgs/{org}/servers/{serverId}/sites/{siteId}/security-rules` |
+| Get / update / delete | GET / PUT / DELETE | `/orgs/{org}/servers/{serverId}/sites/{siteId}/security-rules/{ruleId}` |
+
+Security-rule payloads contain sensitive credentials. Never print passwords or commit them. A path-specific rule can protect a staging site or `/cp`, but confirm its routing effect and remove unintended double authentication before launch.

package/skills/forge-cli/references/api-v2-databases-and-backups.md

@@ -0,0 +1,35 @@
+# Forge API v2 — Databases and Backups
+
+Paths are relative to `https://forge.laravel.com/api`; `{org}` is the organization slug. Many Statamic sites are flat-file and do not require a database. Database backups also do not cover Statamic content, assets, or other files on disk.
+
+## Database Schemas
+
+| Operation | Method | Path |
+| --- | --- | --- |
+| List / create | GET / POST | `/orgs/{org}/servers/{serverId}/database/schemas` |
+| Get / delete | GET / DELETE | `/orgs/{org}/servers/{serverId}/database/schemas/{databaseId}` |
+| Synchronize | POST | `/orgs/{org}/servers/{serverId}/database/schemas/synchronizations` |
+
+API v2 calls databases schemas. There is no update-schema endpoint in the current SDK.
+
+## Database Users
+
+| Operation | Method | Path |
+| --- | --- | --- |
+| List / create | GET / POST | `/orgs/{org}/servers/{serverId}/database/users` |
+| Get / update / delete | GET / PUT / DELETE | `/orgs/{org}/servers/{serverId}/database/users/{userId}` |
+| Update database password | PUT | `/orgs/{org}/servers/{serverId}/database/password` |
+
+Confirm whether an update replaces the full database-access set before changing a user. Never expose database passwords in command output or logs.
+
+## Backup Configurations and Instances
+
+| Operation | Method | Path |
+| --- | --- | --- |
+| List / create configurations | GET / POST | `/orgs/{org}/servers/{serverId}/database/backups` |
+| Get / update / delete configuration | GET / PUT / DELETE | `/orgs/{org}/servers/{serverId}/database/backups/{configurationId}` |
+| List instances / run now | GET / POST | `/orgs/{org}/servers/{serverId}/database/backups/{configurationId}/instances` |
+| Get / delete instance | GET / DELETE | `/orgs/{org}/servers/{serverId}/database/backups/{configurationId}/instances/{backupId}` |
+| Restore instance | POST | `/orgs/{org}/servers/{serverId}/database/backups/{configurationId}/instances/{backupId}/restores` |
+
+Backup configuration payloads vary by storage provider. Verify the provider-specific schema before creation. Treat restores and deletions as destructive: resolve IDs with GET requests and confirm the target database first.

package/skills/forge-cli/references/api-v2-overview.md

@@ -0,0 +1,102 @@
+# Forge HTTP API v2 Overview
+
+Use the HTTP API when Forge CLI 2.x does not expose the required resource mutation. These references cover the API v2 routes most relevant to Statamic and Laravel operations.
+
+## Authentication and Transport
+
+- Base URL: `https://forge.laravel.com/api`
+- Authentication: `Authorization: Bearer <FORGE_API_TOKEN>`
+- Headers: `Accept: application/json` and `Content-Type: application/json`
+- Do not append `/v1`; that is the deprecated legacy API.
+- Do not print, log, or commit API tokens.
+
+Use a token supplied by the user or already available in the process environment. Do not read stored CLI credentials from disk merely to discover a token.
+
+```bash
+curl -sS "https://forge.laravel.com/api/orgs" \
+  -H "Authorization: Bearer $FORGE_API_TOKEN" \
+  -H "Accept: application/json"
+```
+
+## Organization Scope
+
+Most API v2 resources are scoped to an organization slug:
+
+```text
+/orgs/{organizationSlug}/servers/{serverId}/...
+```
+
+Resolve context before composing a request:
+
+```bash
+forge organization:current
+forge organization:list
+forge server:current
+forge server:list
+forge site:list
+```
+
+Useful discovery routes:
+
+| Operation | Method | Path |
+| --- | --- | --- |
+| List organizations | GET | `/orgs` |
+| Get organization | GET | `/orgs/{organizationSlug}` |
+| List servers | GET | `/orgs/{organizationSlug}/servers` |
+| Get server | GET | `/orgs/{organizationSlug}/servers/{serverId}` |
+| List sites on a server | GET | `/orgs/{organizationSlug}/servers/{serverId}/sites` |
+| Get a site within an organization | GET | `/orgs/{organizationSlug}/sites/{siteId}` |
+
+## API v1 to v2 Migration Rules
+
+- Base URL changed from `/api/v1` to `/api`.
+- Most paths gained `/orgs/{organizationSlug}`.
+- Collection responses use a `data` envelope and cursor pagination.
+- Daemons are now background processes; jobs are now scheduled jobs.
+- Domains are first-class site resources and certificates are domain-scoped.
+- Databases are under `/database/schemas`; database users are under `/database/users`.
+- Service mutations use `/services/{service}/actions`.
+- Queue-worker endpoints and Git repository management were removed from API v2.
+- Many mutations return `202 Accepted` with no resource body. Follow with a GET after the asynchronous operation finishes.
+
+Never translate only the host or prefix of an API v1 example. Verify the entire v2 path and payload.
+
+## Pagination and Responses
+
+List responses are cursor-paginated. Follow the response links or cursor instead of assuming one page contains every resource. Raw responses generally wrap resources in `data`; content and log endpoints typically put text under `data.attributes` rather than returning bare text.
+
+Common status codes:
+
+| Code | Meaning |
+| --- | --- |
+| 200 / 201 | Successful read or creation |
+| 202 | Accepted asynchronous mutation; poll or follow with GET |
+| 204 | Successful response with no body |
+| 401 / 403 | Missing, invalid, or insufficiently scoped token |
+| 404 | Wrong organization slug or resource ID, or unavailable endpoint |
+| 422 | Validation failure; inspect the response body before retrying |
+| 429 | Rate limited; back off and retry |
+
+## Safe Request Pattern
+
+Prefer explicit variables and inspect with GET before a mutation:
+
+```bash
+FORGE_API_BASE="https://forge.laravel.com/api"
+ORGANIZATION_SLUG="example-org"
+SERVER_ID="123"
+SITE_ID="456"
+
+curl -sS \
+  -H "Authorization: Bearer $FORGE_API_TOKEN" \
+  -H "Accept: application/json" \
+  "$FORGE_API_BASE/orgs/$ORGANIZATION_SLUG/servers/$SERVER_ID/sites/$SITE_ID"
+```
+
+For writes, add `Content-Type: application/json` and a payload verified against the current v2 docs. Confirm exact IDs with a read-only request first, and get explicit approval before destructive deletions not already requested.
+
+## Sources
+
+- [Forge API v2 introduction](https://laravel.com/forge/docs/api-reference/introduction)
+- [Forge SDK](https://laravel.com/forge/docs/sdk)
+- [Forge CLI](https://laravel.com/forge/docs/cli)

package/skills/forge-cli/references/api-v2-php-services-recipes.md

@@ -0,0 +1,64 @@
+# Forge API v2 — PHP, Services, Recipes, and Composer Credentials
+
+Paths are relative to `https://forge.laravel.com/api`; `{org}` is the organization slug.
+
+## PHP Versions and Configuration
+
+| Operation | Method | Path |
+| --- | --- | --- |
+| List / install versions | GET / POST | `/orgs/{org}/servers/{serverId}/php/versions` |
+| Get / update / delete version | GET / PUT / DELETE | `/orgs/{org}/servers/{serverId}/php/versions/{phpVersionId}` |
+| Get / set CLI version | GET / PUT | `/orgs/{org}/servers/{serverId}/php/cli-version` |
+| Get / set default site version | GET / PUT | `/orgs/{org}/servers/{serverId}/php/site-version` |
+| Get / update FPM config | GET / PUT | `/orgs/{org}/servers/{serverId}/php/versions/{phpVersionId}/configs/fpm` |
+| Get / update CLI config | GET / PUT | `/orgs/{org}/servers/{serverId}/php/versions/{phpVersionId}/configs/cli` |
+| Get / update pool config | GET / PUT | `/orgs/{org}/servers/{serverId}/php/versions/{phpVersionId}/configs/pool` |
+| Get OPCache state | GET | `/orgs/{org}/servers/{serverId}/php/opcache` |
+| Enable / configure OPCache | POST | `/orgs/{org}/servers/{serverId}/php/opcache` |
+| Disable OPCache | DELETE | `/orgs/{org}/servers/{serverId}/php/opcache` |
+
+`{phpVersionId}` is the v2 resource ID, not a remembered v1 `php84` path segment. Installation payloads still identify a requested version, but verify the supported value and the project’s PHP requirement before changing production.
+
+## Service Actions
+
+Service operations use a shared action route:
+
+```text
+POST /orgs/{org}/servers/{serverId}/services/{service}/actions
+```
+
+Supported SDK service names are `nginx`, `mysql`, `postgres`, `redis`, `php`, and `supervisor`. A restart payload is:
+
+```json
+{"action":"restart"}
+```
+
+Use the CLI for supported restarts:
+
+```bash
+forge nginx:restart
+forge database:restart
+forge php:restart 8.5
+```
+
+Do not reuse API v1 paths such as `/nginx/reboot`, `/mysql/stop`, or `/services/restart`.
+
+## Recipes
+
+| Operation | Method | Path |
+| --- | --- | --- |
+| List / create | GET / POST | `/orgs/{org}/recipes` |
+| Get / update / delete | GET / PUT / DELETE | `/orgs/{org}/recipes/{recipeId}` |
+| List runs / run recipe | GET / POST | `/orgs/{org}/recipes/{recipeId}/runs` |
+| Get run | GET | `/orgs/{org}/recipes/{recipeId}/runs/{runId}` |
+
+Recipes can run privileged scripts. Inspect the complete script, target servers, and execution user before starting a run.
+
+## Composer Credentials
+
+| Operation | Method | Path |
+| --- | --- | --- |
+| List / create | GET / POST | `/orgs/{org}/servers/{serverId}/sites/{siteId}/composer/credentials` |
+| Get / update / delete | GET / PUT / DELETE | `/orgs/{org}/servers/{serverId}/sites/{siteId}/composer/credentials/{repository}` |
+
+Use this for `composer.statamic.com` and other private repositories. Treat usernames, tokens, passwords, and license keys as secrets; do not print them in logs or include them in documentation examples.

package/skills/forge-cli/references/api-v2-processes-and-scheduler.md

@@ -0,0 +1,67 @@
+# Forge API v2 — Background Processes and Scheduling
+
+Paths are relative to `https://forge.laravel.com/api`; `{org}` is the organization slug.
+
+## Queue Workers Were Removed from API v2
+
+The old `/sites/{siteId}/workers` API is not available in v2. Do not call it or try to translate it by adding organization scope.
+
+For a long-running Laravel or Statamic queue consumer, create a server background process whose command changes into the site directory and runs the appropriate `queue:work` command. Confirm the exact command, site user, working directory, and process count with the project before creating it. If the Forge dashboard offers a higher-level queue-worker workflow, prefer that for worker-specific settings.
+
+## Background Processes
+
+API v2 renamed daemons to background processes.
+
+| Operation | Method | Path | Notes |
+| --- | --- | --- | --- |
+| List | GET | `/orgs/{org}/servers/{serverId}/background-processes` | Cursor-paginated |
+| Create | POST | `/orgs/{org}/servers/{serverId}/background-processes` | Verify current body schema |
+| Get | GET | `/orgs/{org}/servers/{serverId}/background-processes/{processId}` | — |
+| Update | PUT | `/orgs/{org}/servers/{serverId}/background-processes/{processId}` | Often returns 202 |
+| Restart/action | POST | `/orgs/{org}/servers/{serverId}/background-processes/{processId}/actions` | For restart: `{"action":"restart"}` |
+| Read log | GET | `/orgs/{org}/servers/{serverId}/background-processes/{processId}/log` | Content is in `data.attributes.content` |
+| Delete | DELETE | `/orgs/{org}/servers/{serverId}/background-processes/{processId}` | Destructive |
+
+CLI 2.x provides read and restart operations:
+
+```bash
+forge background-process:list
+forge background-process:status 12345
+forge background-process:logs 12345
+forge background-process:restart 12345
+```
+
+The `daemon:*` aliases remain for compatibility, but skill instructions and new automation should use `background-process:*`.
+
+## Scheduled Jobs
+
+Forge v2 supports server-scoped and site-scoped jobs.
+
+| Scope | Operation | Method | Path |
+| --- | --- | --- | --- |
+| Server | List / create | GET / POST | `/orgs/{org}/servers/{serverId}/scheduled-jobs` |
+| Server | Get / delete | GET / DELETE | `/orgs/{org}/servers/{serverId}/scheduled-jobs/{jobId}` |
+| Server | Output | GET | `/orgs/{org}/servers/{serverId}/scheduled-jobs/{jobId}/output` |
+| Site | List / create | GET / POST | `/orgs/{org}/servers/{serverId}/sites/{siteId}/scheduled-jobs` |
+| Site | Get / delete | GET / DELETE | `/orgs/{org}/servers/{serverId}/sites/{siteId}/scheduled-jobs/{jobId}` |
+| Site | Output | GET | `/orgs/{org}/servers/{serverId}/sites/{siteId}/scheduled-jobs/{jobId}/output` |
+
+For Statamic or Laravel applications, prefer the Scheduler integration when the application already defines its schedule. Use individual scheduled jobs only for independent cron commands.
+
+## Laravel Scheduler Integration
+
+| Operation | Method | Path |
+| --- | --- | --- |
+| Status | GET | `/orgs/{org}/servers/{serverId}/sites/{siteId}/integrations/laravel-scheduler` |
+| Enable | POST | `/orgs/{org}/servers/{serverId}/sites/{siteId}/integrations/laravel-scheduler` |
+| Disable | DELETE | `/orgs/{org}/servers/{serverId}/sites/{siteId}/integrations/laravel-scheduler` |
+
+## Laravel Maintenance Mode
+
+| Operation | Method | Path |
+| --- | --- | --- |
+| Status | GET | `/orgs/{org}/servers/{serverId}/sites/{siteId}/integrations/laravel-maintenance` |
+| Enable | POST | `/orgs/{org}/servers/{serverId}/sites/{siteId}/integrations/laravel-maintenance` |
+| Disable | DELETE | `/orgs/{org}/servers/{serverId}/sites/{siteId}/integrations/laravel-maintenance` |
+
+Confirm enable payload options against the current v2 schema; do not reuse the old v1 maintenance payload without verification.

package/skills/forge-cli/references/api-v2-sites.md

@@ -0,0 +1,84 @@
+# Forge API v2 — Sites, Domains, Deployments, Commands, and Logs
+
+Paths are relative to `https://forge.laravel.com/api`. Replace `{org}` with the organization slug. Confirm request bodies in the current API documentation before writing; API v1 payloads are not assumed compatible.
+
+## Sites and Domains
+
+| Operation | Method | Path |
+| --- | --- | --- |
+| List all organization sites | GET | `/orgs/{org}/sites` |
+| Get organization site | GET | `/orgs/{org}/sites/{siteId}` |
+| List server sites | GET | `/orgs/{org}/servers/{serverId}/sites` |
+| Create site | POST | `/orgs/{org}/servers/{serverId}/sites` |
+| Update site | PUT | `/orgs/{org}/servers/{serverId}/sites/{siteId}` |
+| Delete site | DELETE | `/orgs/{org}/servers/{serverId}/sites/{siteId}` |
+| List domains | GET | `/orgs/{org}/servers/{serverId}/sites/{siteId}/domains` |
+| Create domain | POST | `/orgs/{org}/servers/{serverId}/sites/{siteId}/domains` |
+| Get domain | GET | `/orgs/{org}/servers/{serverId}/sites/{siteId}/domains/{domainId}` |
+| Update domain | PATCH | `/orgs/{org}/servers/{serverId}/sites/{siteId}/domains/{domainId}` |
+| Delete domain | DELETE | `/orgs/{org}/servers/{serverId}/sites/{siteId}/domains/{domainId}` |
+
+API v2 removed the old aliases endpoint. Manage each hostname through the domains collection. Git repository install, update, and delete operations were also removed from API v2; connect or change source control in the Forge dashboard.
+
+## Environment and Nginx
+
+| Operation | Method | Path | Payload / response note |
+| --- | --- | --- | --- |
+| Get environment | GET | `/orgs/{org}/servers/{serverId}/sites/{siteId}/environment` | Content is in `data.attributes.content` |
+| Update environment | PUT | `/orgs/{org}/servers/{serverId}/sites/{siteId}/environment` | `environment`: full file content |
+| Get site Nginx | GET | `/orgs/{org}/servers/{serverId}/sites/{siteId}/nginx` | Content is in `data.attributes.content` |
+| Update site Nginx | PUT | `/orgs/{org}/servers/{serverId}/sites/{siteId}/nginx` | `config`: full configuration |
+| Get domain Nginx | GET | `/orgs/{org}/servers/{serverId}/sites/{siteId}/domains/{domainId}/nginx` | Domain-specific configuration |
+| Update domain Nginx | PUT | `/orgs/{org}/servers/{serverId}/sites/{siteId}/domains/{domainId}/nginx` | `config`: full configuration |
+
+Prefer `forge env:pull` and `forge env:push` for interactive environment work. Always fetch the current Nginx configuration before replacing it.
+
+## Deployments and Deploy Keys
+
+| Operation | Method | Path |
+| --- | --- | --- |
+| List deployments | GET | `/orgs/{org}/servers/{serverId}/sites/{siteId}/deployments` |
+| Start deployment | POST | `/orgs/{org}/servers/{serverId}/sites/{siteId}/deployments` |
+| Get deployment | GET | `/orgs/{org}/servers/{serverId}/sites/{siteId}/deployments/{deploymentId}` |
+| Get deployment log | GET | `/orgs/{org}/servers/{serverId}/sites/{siteId}/deployments/{deploymentId}/log` |
+| Get deployment status | GET | `/orgs/{org}/servers/{serverId}/sites/{siteId}/deployments/status` |
+| Disable quick deploy | DELETE | `/orgs/{org}/servers/{serverId}/sites/{siteId}/deployments/status` |
+| Get deployment script | GET | `/orgs/{org}/servers/{serverId}/sites/{siteId}/deployments/script` |
+| Update deployment script | PUT | `/orgs/{org}/servers/{serverId}/sites/{siteId}/deployments/script` |
+| Get deploy hook | GET | `/orgs/{org}/servers/{serverId}/sites/{siteId}/deployments/deploy-hook` |
+| Update deploy hook | PUT | `/orgs/{org}/servers/{serverId}/sites/{siteId}/deployments/deploy-hook` |
+| Enable push-to-deploy | POST | `/orgs/{org}/servers/{serverId}/sites/{siteId}/deployments/push-to-deploy` |
+| Disable push-to-deploy | DELETE | `/orgs/{org}/servers/{serverId}/sites/{siteId}/deployments/push-to-deploy` |
+| Get / create deploy key | GET / POST | `/orgs/{org}/servers/{serverId}/sites/{siteId}/deploy-key` |
+| Delete deploy key | DELETE | `/orgs/{org}/servers/{serverId}/sites/{siteId}/deploy-key` |
+
+Use `forge deploy` and `forge deploy:logs` for normal deployment operations. API v2 has no equivalent for the old reset-deployment-state endpoint.
+
+## Site Commands
+
+| Operation | Method | Path |
+| --- | --- | --- |
+| List / run | GET / POST | `/orgs/{org}/servers/{serverId}/sites/{siteId}/commands` |
+| Get / delete | GET / DELETE | `/orgs/{org}/servers/{serverId}/sites/{siteId}/commands/{commandId}` |
+| Get output | GET | `/orgs/{org}/servers/{serverId}/sites/{siteId}/commands/{commandId}/output` |
+
+Prefer `forge command example.com --command="..."` unless scripting through HTTP.
+
+## Site Logs
+
+| Log | Read | Clear |
+| --- | --- | --- |
+| Nginx access | `GET .../sites/{siteId}/logs/nginx-access` | `DELETE .../sites/{siteId}/logs/nginx-access` |
+| Nginx error | `GET .../sites/{siteId}/logs/nginx-error` | `DELETE .../sites/{siteId}/logs/nginx-error` |
+| Application | `GET .../sites/{siteId}/logs/application` | `DELETE .../sites/{siteId}/logs/application` |
+
+Each abbreviated path begins `/orgs/{org}/servers/{serverId}`. Prefer `forge site:logs --follow` for a live application-log tail.
+
+## Deployment Webhooks
+
+| Operation | Method | Path |
+| --- | --- | --- |
+| List / create | GET / POST | `/orgs/{org}/servers/{serverId}/sites/{siteId}/webhooks` |
+| Get / delete | GET / DELETE | `/orgs/{org}/servers/{serverId}/sites/{siteId}/webhooks/{webhookId}` |
+
+The API v1 deployment-failure-email endpoint is not available in v2.

package/skills/forge-cli/references/command-reference-v2.md

@@ -0,0 +1,145 @@
+# Forge CLI 2.x Command Reference
+
+This reference covers the currently supported Forge CLI 2.x command families.
+
+## Installation and Verification
+
+Requirements:
+
+- PHP 8.2 or newer
+- Composer available globally
+
+Install or upgrade within major version 2:
+
+```bash
+composer global require "laravel/forge-cli:^2.0" --with-all-dependencies
+```
+
+Verify both the executable and Composer package metadata:
+
+```bash
+forge --version
+composer global show laravel/forge-cli
+forge list --raw
+```
+
+If `forge --version` disagrees with Composer metadata, confirm `command -v forge` points to the Composer global binary. Package metadata is the reliable installed-package version; a release may contain a stale display string.
+
+Authenticate:
+
+```bash
+forge login
+forge login --token="your-api-token"
+forge logout
+```
+
+For CI, set `FORGE_API_TOKEN` in the CI secret store. Never echo the token.
+
+## Active Organization and Server
+
+CLI 2.x commands run in an active organization and usually an active server:
+
+```bash
+forge organization:current
+forge organization:list
+forge organization:switch
+forge organization:switch organization-slug
+
+forge server:current
+forge server:list
+forge server:switch
+forge server:switch production
+```
+
+Aliases `org:current`, `org:list`, and `org:switch` are available. Switching organizations resets the active server, so choose the server again afterward.
+
+## SSH
+
+```bash
+forge ssh:test
+forge ssh:configure
+forge ssh:configure --key=/path/to/public-key.pub --name=laptop-key
+forge ssh
+forge ssh server-name
+```
+
+## Sites
+
+```bash
+forge site:list
+forge open
+forge open example.com
+forge deploy
+forge deploy example.com
+forge deploy:logs
+forge deploy:logs example.com
+```
+
+The optional `deploy:logs` argument is a site name, not a deployment ID.
+
+Environment files:
+
+```bash
+forge env:pull
+forge env:pull example.com
+forge env:pull example.com .env
+forge env:push
+forge env:push example.com
+forge env:push example.com .env
+```
+
+Application logs and remote commands:
+
+```bash
+forge site:logs
+forge site:logs --follow
+forge site:logs example.com --follow
+forge command
+forge command example.com --command="php artisan about"
+forge tinker
+forge tinker example.com
+```
+
+If configuration is cached or a long-running process consumes environment values, deploy and restart that process after pushing `.env` changes.
+
+## Background Processes
+
+```bash
+forge background-process:list
+forge background-process:status
+forge background-process:status 12345
+forge background-process:logs
+forge background-process:logs 12345 --follow
+forge background-process:restart
+forge background-process:restart 12345
+```
+
+CLI 2.x retains `daemon:list`, `daemon:status`, `daemon:logs`, and `daemon:restart` as aliases. Prefer `background-process:*` in new instructions.
+
+## Database, Nginx, and PHP
+
+```bash
+forge database:status
+forge database:logs
+forge database:restart
+forge database:shell
+forge database:shell database-name --user=database-user
+
+forge nginx:status
+forge nginx:logs
+forge nginx:logs access
+forge nginx:restart
+
+forge php:status
+forge php:status 8.5
+forge php:logs
+forge php:logs 8.5
+forge php:restart
+forge php:restart 8.5
+```
+
+Use read-only status and log commands before restarts when diagnosing. Confirm organization and server context before any state-changing command.
+
+## Source
+
+[Official Laravel Forge CLI documentation](https://laravel.com/forge/docs/cli)

package/skills/shopify-lint/SKILL.md

@@ -40,7 +40,7 @@ python3 .agents/skills/shopify-lint/scripts/shopify_lint.py --path .
 
 The script identifies files changed since the current branch's merge-base, adds staged, unstaged, and untracked files, then runs three linters over that set and merges their results into one report:
 
-- **Theme Check** — `shopify theme check --output json`. The root `.theme-check.yml` directly requires the bundled `theme-check-theory` package from this skill directory. `DisallowedScriptOrStyleTag` reports inline executable `<script>` and all `<style>` tags in modified Liquid files while allowing external-source and JSON-data scripts. `HardcodedText` reports rendered hard-coded copy, except content inside Liquid `stylesheet`, `javascript`, and `schema` tags, and except text beginning with `--`, which is a CSS custom property name rather than copy. The generated `.theme-check.yml` also pins the upstream `StaticStylesheetAndJavascriptTags` to `error`, so Liquid written inside a `{% stylesheet %}` or `{% javascript %}` block always fails the lint.
+- **Theme Check** — `shopify theme check --output json`. The root `.theme-check.yml` directly requires the bundled `theme-check-theory` package from this skill directory. `DisallowedScriptOrStyleTag` reports inline executable `<script>` and all `<style>` tags in modified Liquid files while allowing external-source and JSON-data scripts. `HardcodedText` reports rendered hard-coded copy, except content inside Liquid `stylesheet`, `javascript`, and `schema` tags, except text beginning with `--`, which is a CSS custom property name rather than copy, and except string arguments passed to `{% render %}` and `{% include %}`, which are as often class names or size tokens as copy. The generated `.theme-check.yml` also pins the upstream `StaticStylesheetAndJavascriptTags` to `error`, so Liquid written inside a `{% stylesheet %}` or `{% javascript %}` block always fails the lint.
 - **JavaScript** — ESLint's recommended rules plus the bundled `eslint-plugin-theory`, over modified `.js` and `.mjs` files *and* the JavaScript inside `{% javascript %}` blocks of modified `.liquid` files.
 - **CSS** — `stylelint-config-standard` through the bundled `stylelint-config-theory`, over modified `.css` files *and* the CSS inside `{% stylesheet %}` blocks of modified `.liquid` files.