vybekiit 0.7.3 → 0.7.7

package/dist/global-skills/use-railway/references/iac.md

@@ -1,37 +1,149 @@
-# Infrastructure as Code
+# Configuration in source control
 
-Define, import, preview, and apply a Railway project from `.railway/railway.ts`.
+Choose one configuration model before editing files. Never manage the same service with both models.
 
-Use Railway IaC when the user wants project-level configuration in source control: services, databases, buckets, volumes, variables, replicas, domains, and canvas groups. Do not use it for a single-service deploy setting that is already owned by `railway.json` or `railway.toml`; migrate that service first so there is only one source of truth.
+## Choose the model
 
-## Files
+Prefer TypeScript Infrastructure as Code when the repository has TypeScript set up. Use `railway.json` only as the fallback for repositories without TypeScript.
 
-Railway IaC uses TypeScript:
+Use TypeScript IaC when any of these signals exist in the current project or workspace:
+
+- `.railway/railway.ts` already exists.
+- A `tsconfig.json` or another `tsconfig*.json` exists.
+- `package.json` declares `typescript`, or the project contains `.ts` or `.tsx` source files.
+
+If none of those signals exist, create or edit `railway.json`. Do not choose `railway.toml` for new agent-authored configuration.
+
+If a TypeScript repository already has `railway.json`, migrate the intended settings to `.railway/railway.ts` and remove the old file before planning. If the user explicitly asks to preserve the existing model rather than migrate, edit the existing file and explain that it remains service-level Config as Code.
+
+The models have different scopes:
+
+| Model | Scope | Applies when |
+|---|---|---|
+| `.railway/railway.ts` | Whole Railway project: services, databases, buckets, volumes, variables, replicas, domains, and canvas groups | `railway config apply` applies the reviewed project plan |
+| `railway.json` | One service's build and deploy settings | The next deployment reads the file; it does not update dashboard settings |
+
+## TypeScript Infrastructure as Code
+
+The desired Railway project state lives in:
 
 ```text
 .railway/railway.ts
-.railway/README.md
-.agents/skills/railway-config/SKILL.md
 ```
 
-`railway config init` and `railway config pull` create the support files when missing. The project-local `railway-config` skill helps future agents edit `.railway/railway.ts` safely.
+`railway config init` and `railway config pull` also create `.railway/README.md`. Railway agent setup installs the shared `use-railway` skill; config commands do not need or create a project-local skill.
 
-## Initialize or import
+### Core rules
+
+1. Express Railway product intent, not internal API details.
+2. Do not write Railway UUIDs into `.railway/railway.ts`.
+3. Do not write `EnvironmentConfigPatch`, `ServiceInstance`, Backboard internals, or generated Railway domains into source.
+4. Prefer helpers such as `service()`, `postgres()`, `redis()`, `mysql()`, `mongo()`, `bucket()`, `volume()`, `group()`, `github()`, and `image()`.
+5. Use `service.env.VARIABLE` and `database.env.VARIABLE` for references.
+6. Keep secrets out of source. Imported unknown secret values should use `preserve()` or be omitted when the user wants a smaller import.
+7. Prefer product DSL names such as `domains`, `replicas`, and `group`; avoid internal names such as `customDomains` and `multiRegionConfig`.
+8. Do not add platform defaults unless the user explicitly wants them.
+9. After editing `.railway/railway.ts`, run `railway config plan`.
+10. Do not run `railway config apply` unless the user explicitly asks.
+11. Never use `railway config apply --yes` or `--confirm-destructive` from an agent session without explicit user approval for the exact plan.
+
+### Initialize or import
 
 ```bash
-railway config init                         # create a starter .railway/railway.ts
+railway config init                         # create .railway/railway.ts
 railway config init --force                 # overwrite existing generated files
 railway config pull                         # import the linked project
 railway config pull --force                 # overwrite existing .railway/railway.ts
+railway config pull --omit-preserved-variables # omit unknown variable values
 railway config pull --json                  # print current graph instead of writing files
 railway config pull --agent                 # ask an agent to clean the import afterward
 ```
 
-If the directory is not linked, the CLI prompts for project/environment in an interactive terminal. In agent workflows, prefer linking first or passing explicit project/environment context when the CLI supports it.
+If the directory is not linked, the CLI prompts for project and environment in an interactive terminal. In agent workflows, link first or pass explicit project and environment context when supported.
+
+### Authoring
+
+Import the helpers needed by the project:
+
+```ts
+import {
+  bucket,
+  defineRailway,
+  github,
+  group,
+  image,
+  mongo,
+  mysql,
+  postgres,
+  preserve,
+  project,
+  redis,
+  service,
+  volume,
+} from "railway/iac";
+```
+
+Common resource patterns:
+
+```ts
+const db = postgres("postgres");
+
+const api = service("api", {
+  source: github("owner/repo", { branch: "main" }),
+  build: "pnpm build",
+  start: "pnpm start",
+  env: {
+    DATABASE_URL: db.env.DATABASE_URL,
+    INTERNAL_TOKEN: preserve(),
+  },
+  domains: ["api.example.com"],
+  replicas: 3,
+  volumeMounts: {
+    "/data": volume("uploads", { sizeMB: 4096 }),
+  },
+});
+
+const worker = service("worker", {
+  source: image("ghcr.io/acme/worker:latest"),
+  env: {
+    API_HOST: api.env.RAILWAY_PRIVATE_DOMAIN,
+    API_TOKEN: api.env.INTERNAL_TOKEN,
+  },
+});
+
+const media = bucket("media", { region: "iad" });
+const backend = group("Backend", [api, worker, db]);
+```
+
+Advanced placement can map regions to replica counts:
+
+```ts
+const web = service("web", {
+  replicas: {
+    "us-west2": 2,
+    "europe-west4": 1,
+  },
+});
+```
+
+Return every managed resource from the project:
+
+```ts
+export default defineRailway(() => {
+  const db = postgres("postgres");
+  const web = service("web", {
+    env: { DATABASE_URL: db.env.DATABASE_URL },
+  });
+
+  return project("my-app", {
+    resources: [db, web],
+  });
+});
+```
 
-## Plan
+### Plan
 
-Always plan before applying:
+Always plan after editing and before applying:
 
 ```bash
 railway config plan
@@ -47,9 +159,9 @@ Plan output summarizes changes in Terraform style:
 Plan: 1 to add, 0 to change, 0 to destroy
 ```
 
-Variable values are redacted by default. Use `--show-values` only when the user is intentionally reviewing non-secret config or accepts the secret exposure risk. Use `--detailed-exit-code` for CI drift checks: exit `0` means no changes, exit `2` means changes are pending, and other non-zero exits are errors.
+Variable values are redacted by default. Use `--show-values` only when the user accepts the secret exposure risk. For CI drift checks, `--detailed-exit-code` returns `0` for no changes, `2` for pending changes, and another non-zero code for errors.
 
-## Apply
+### Apply
 
 ```bash
 railway config apply
@@ -58,51 +170,88 @@ railway config apply --yes --confirm-destructive
 railway config apply --json --yes --confirm-destructive
 ```
 
-`apply` always runs a fresh plan first. If the environment changed after the last plan, Railway rejects the apply and asks for a new plan. In non-interactive or agent sessions, destructive changes require `--confirm-destructive` in addition to `--yes` or `--json`; do not add it unless the user explicitly approved the destructive impact.
-
-## Authoring pattern
-
-Keep `.railway/railway.ts` readable and explicit:
-
-```ts
-import { defineRailway, project, service } from "railway/iac";
-
-export default defineRailway(() => {
-  const web = service("web", {
-    build: "pnpm build",
-    start: "pnpm start",
-  });
-
-  return project("my-project", {
-    resources: [web],
-  });
-});
+`apply` runs a fresh plan. If remote state changed, Railway rejects the stale apply and requires another plan. In non-interactive or agent sessions, destructive changes require `--confirm-destructive` in addition to `--yes` or `--json`; add it only after the user explicitly approves the exact destructive impact.
+
+### Review checklist
+
+Before applying, confirm:
+
+- The latest plan shows only expected changes.
+- The user reviewed the plan and explicitly requested apply.
+- Secrets are not replaced with literal placeholders.
+- Existing Railway-managed variables are omitted or use `preserve()` when they should remain untouched.
+- Custom domains use `domains`, not networking internals.
+- Scaling uses `replicas`, not `multiRegionConfig`.
+- No generated Railway service domains or Railway UUIDs are committed.
+
+### Troubleshoot TypeScript IaC
+
+- **Service is already managed by `railway.json`**: migrate its intended settings and remove the old file before planning; Railway blocks dual ownership.
+- **Plan shows secrets as hidden**: expected. Use `--show-values` only with user approval.
+- **Apply says the plan is stale**: run a new plan, inspect it, then apply again only if requested.
+- **Destructive apply is blocked**: get explicit approval for the exact plan before adding `--confirm-destructive`.
+- **Imported variables use `preserve()`**: Railway could not safely print encrypted values; `preserve()` retains the remote value.
+- **Generated code is too literal**: simplify `.railway/railway.ts`, then run another plan.
+
+## `railway.json` fallback
+
+Use this path only when the repository has no TypeScript setup. `railway.json` controls one service's build and deploy settings, not project resources such as databases, buckets, variables, or canvas groups.
+
+Start with the schema so editors validate fields:
+
+```json
+{
+  "$schema": "https://railway.com/railway.schema.json",
+  "build": {
+    "builder": "RAILPACK",
+    "buildCommand": "npm run build"
+  },
+  "deploy": {
+    "preDeployCommand": ["npm run db:migrate"],
+    "startCommand": "npm start",
+    "healthcheckPath": "/health",
+    "healthcheckTimeout": 300,
+    "restartPolicyType": "ON_FAILURE",
+    "restartPolicyMaxRetries": 5
+  }
+}
 ```
 
-Use imported helpers when needed: `service`, `postgres`, `redis`, `mysql`, `mongo`, `bucket`, `volume`, `group`, `github`, `image`, and `preserve`.
-
-## Migration from config as code
-
-When a service has `railway.json` or `railway.toml`:
-
-1. Run `railway config pull --force`.
-2. Translate only the intended service settings into `.railway/railway.ts`.
-3. Remove the old service-level config file or clear its custom config file path.
-4. Run `railway config plan`.
-5. Apply only when the plan matches the intended migration.
-
-If the plan shows unexpected service deletes, variable deletes, bucket deletes, or unrelated changes, stop and inspect the generated file before applying.
-
-## Troubleshoot IaC
+Rules for this fallback:
+
+1. Include only settings the user intends to override. File values override dashboard values for that deployment.
+2. Use the canonical schema field names; do not copy internal environment patch names blindly.
+3. Keep service variables and secrets out of `railway.json`; manage them with Railway variables.
+4. Use `environments.<name>` for environment-specific overrides and `environments.pr` for PR environments.
+5. In a monorepo, place the file at the service root or set the service's custom Railway config file path to its absolute repository path.
+6. Validate the JSON after editing. A deployment is required for the config to take effect; editing the file does not mutate dashboard settings.
+
+Example environment override:
+
+```json
+{
+  "$schema": "https://railway.com/railway.schema.json",
+  "deploy": {
+    "startCommand": "npm start"
+  },
+  "environments": {
+    "staging": {
+      "deploy": {
+        "startCommand": "npm run staging"
+      }
+    },
+    "pr": {
+      "deploy": {
+        "startCommand": "npm run preview"
+      }
+    }
+  }
+}
+```
 
-- **Service is already managed by `railway.json` or `railway.toml`**: migrate that service first; Railway blocks dual ownership.
-- **Plan shows secrets as hidden**: this is expected. Use `--show-values` only with user approval.
-- **Apply says the plan is stale**: run `railway config plan` again, inspect the new diff, then re-apply.
-- **Destructive apply blocked**: get explicit user approval and rerun with `--confirm-destructive`.
-- **Imported variables use `preserve()`**: Railway could not safely print encrypted secret values; preserve keeps the remote value.
-- **Generated code is too literal**: edit `.railway/railway.ts` into a cleaner shape, then verify with `railway config plan`.
+For the complete field list, use the live JSON schema or Railway's Config as Code reference rather than guessing unsupported keys.
 
 ## Validated against
 
-- Docs: [infrastructure-as-code.md](https://docs.railway.com/infrastructure-as-code), [infrastructure-as-code/reference.md](https://docs.railway.com/infrastructure-as-code/reference)
-- CLI source: [config/mod.rs](https://github.com/railwayapp/cli/blob/v5.23.3/src/commands/config/mod.rs), [config/runner.rs](https://github.com/railwayapp/cli/blob/v5.23.3/src/commands/config/runner.rs)
+- Docs: [Infrastructure as Code](https://docs.railway.com/infrastructure-as-code), [IaC reference](https://docs.railway.com/infrastructure-as-code/reference), [Config as Code](https://docs.railway.com/guides/config-as-code), [Config as Code reference](https://docs.railway.com/reference/config-as-code)
+- CLI source: [config/mod.rs](https://github.com/railwayapp/cli/blob/v5.27.1/src/commands/config/mod.rs), [config/runner.rs](https://github.com/railwayapp/cli/blob/v5.27.1/src/commands/config/runner.rs)

package/dist/global-skills/use-railway/scripts/railway-api.sh

@@ -42,11 +42,16 @@ else
 fi
 
 HEADERS=(
-  -H "Authorization: Bearer $TOKEN"
   -H "Content-Type: application/json"
   -H "X-Railway-Skill-Id: $SKILL_ID"
   -H "X-Railway-Skill-Version: $SKILL_VERSION"
   -H "X-Railway-Agent-Session: $RAILWAY_AGENT_SESSION"
 )
 
-curl -s https://backboard.railway.com/graphql/v2 "${HEADERS[@]}" -d "$PAYLOAD"
+# Keep the token and the request body out of argv: /proc/<pid>/cmdline is
+# readable by any other local user, so anything passed as an argument leaks on a
+# shared host. The bearer goes in through --config on a pipe, the payload on stdin.
+printf '%s' "$PAYLOAD" | curl -s https://backboard.railway.com/graphql/v2 \
+  "${HEADERS[@]}" \
+  --config <(printf 'header = "Authorization: Bearer %s"\n' "$TOKEN") \
+  -d @-

package/dist/global-skills/xcode-project-setup/SKILL.md

@@ -2,6 +2,8 @@
 name: xcode-project-setup
 description: Safely modifies Xcode projects (.pbxproj) to add Swift Packages and link files. Use this skill whenever an iOS project needs dependencies installed (e.g. Firebase, Alamofire).
 compatibility: Requires Swift to be installed locally and macOS environment.
+metadata:
+  category: ApplicationDevelopment
 ---
 
 # Xcode Project Setup

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "vybekiit",
-  "version": "0.7.3",
-  "description": "Set up tools and create a VybeKiit app: `npx vybekiit setup` then `npx vybekiit create app --web`.",
+  "version": "0.7.7",
+  "description": "Choose your services, sign in, create a VybeKiit app, and open its verified local welcome page.",
   "license": "MIT",
   "publishConfig": {
     "access": "public"
@@ -14,6 +14,7 @@
     "dist"
   ],
   "dependencies": {
+    "@modelcontextprotocol/sdk": "^1.12.1",
     "@aws-sdk/client-dynamodb": "^3.1075.0",
     "@aws-sdk/client-s3": "^3.1075.0",
     "@aws-sdk/lib-dynamodb": "^3.1075.0",
@@ -23,19 +24,21 @@
     "effect": "3.21.4",
     "firebase-admin": "^13.0.2",
     "mongodb": "^7.4.0",
-    "open": "11.0.0"
+    "open": "11.0.0",
+    "playwright": "^1.61.1"
   },
   "devDependencies": {
     "@types/node": "22.20.0",
     "tsup": "8.5.1",
     "typescript": "5.7.2",
     "vitest": "3.2.6",
-    "@vybekiit/agent-kit": "0.7.3",
-    "@vybekiit/core": "0.7.3",
-    "@vybekiit/db": "0.7.3",
-    "@vybekiit/deploy": "0.7.3",
-    "@vybekiit/payments": "0.7.3",
-    "@vybekiit/report-mode": "0.7.3"
+    "@vybekiit/agent-kit": "0.7.7",
+    "@vybekiit/agent-mcp": "0.7.7",
+    "@vybekiit/core": "0.7.7",
+    "@vybekiit/db": "0.7.7",
+    "@vybekiit/deploy": "0.7.7",
+    "@vybekiit/payments": "0.7.7",
+    "@vybekiit/report-mode": "0.7.7"
   },
   "scripts": {
     "build": "tsup && node scripts/bundleGlobalSkills.mjs",

package/LICENSE.md

@@ -1,47 +0,0 @@
-# VybeKiit licensing
-
-This repository is **dual-licensed by component**, matching the Owned vs Maintained split (see
-`CONTEXT.md`). Which license applies depends only on the path:
-
-| Path | License | Why |
-|---|---|---|
-| `packages/*` (published `@vybekiit/*`) | **MIT** | Public, headless logic — free updates double as marketing; nothing secret here. |
-| `cli/` (the published `vybekiit` scaffolder) | **MIT** | The public npm CLI anyone may `npx`; the paid gate is repo access, not the CLI itself. |
-| `templates/*` + the buyer agent layer (`.vybekiit/`, and each template's `AGENTS.md` / `CLAUDE.md` / `.cursor/rules` / `language.md` / `BUILDER-VOICE.md`) | **Proprietary — VybeKiit EULA** | The paid, owned product. Full terms in [`EULA.md`](./EULA.md). |
-| `apps/landing/`, root tooling/config, and other repo internals | Proprietary (not distributed) | Our store and build infrastructure — never shipped to a buyer. |
-
-The MIT-licensed paths are the only parts published to public npm. The proprietary paths reach
-buyers through private GitHub mirror repos after purchase (the gate) and are governed by the
-[VybeKiit EULA](./EULA.md), which includes a plain-language summary of what a buyer can and can't do.
-
----
-
-## MIT License — applies to `packages/*` and `cli/`
-
-Copyright (c) 2026 VybeKiit authors
-
-Permission is hereby granted, free of charge, to any person obtaining a copy of this software and
-associated documentation files (the "Software"), to deal in the Software without restriction,
-including without limitation the rights to use, copy, modify, merge, publish, distribute,
-sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all copies or substantial
-portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT
-LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
-IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
-WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
-
----
-
-## Proprietary — applies to `templates/*` and the buyer agent layer
-
-These paths are **not** open source. They are the paid product, licensed (not sold) to buyers under
-the **[VybeKiit EULA](./EULA.md)**. In short: a buyer may build unlimited products of their own,
-including commercial ones, but may **not** redistribute, resell, or republish the kit itself, build a
-competing kit with it, or share their access. Provided as-is, no warranty, liability capped at the
-amount paid, best-effort updates with no compatibility guarantee. See `EULA.md` for the full terms
-and the plain-language buyer summary.

package/dist/global-skills/eas-workflows/scripts/validate.js

@@ -1,84 +0,0 @@
-#!/usr/bin/env node
-
-import { readFile } from 'node:fs/promises';
-import { resolve } from 'node:path';
-import process from 'node:process';
-
-import Ajv2020 from 'ajv/dist/2020.js';
-import addFormats from 'ajv-formats';
-import yaml from 'js-yaml';
-
-import { fetchCached } from './fetch.js';
-
-const SCHEMA_URL = 'https://api.expo.dev/v2/workflows/schema';
-
-async function fetchSchema() {
-  const data = await fetchCached(SCHEMA_URL);
-  const body = JSON.parse(data);
-  return body.data;
-}
-
-function createValidator(schema) {
-  const ajv = new Ajv2020({ allErrors: true, strict: true });
-  addFormats(ajv);
-  return ajv.compile(schema);
-}
-
-async function validateFile(validator, filePath) {
-  const content = await readFile(filePath, 'utf-8');
-
-  let doc;
-  try {
-    doc = yaml.load(content);
-  } catch (e) {
-    return { valid: false, error: `YAML parse error: ${e.message}` };
-  }
-
-  const valid = validator(doc);
-  if (!valid) {
-    return { valid: false, error: formatErrors(validator.errors) };
-  }
-
-  return { valid: true };
-}
-
-function formatErrors(errors) {
-  return errors
-    .map((error) => {
-      const path = error.instancePath || '(root)';
-      const allowed = error.params?.allowedValues?.join(', ');
-      return `  ${path}: ${error.message}${allowed ? ` (allowed: ${allowed})` : ''}`;
-    })
-    .join('\n');
-}
-
-if (import.meta.main) {
-  const args = process.argv.slice(2);
-  const files = args.filter((a) => !a.startsWith('-'));
-
-  if (files.length === 0 || args.includes('--help') || args.includes('-h')) {
-    console.log(`Usage: validate <workflow.yml> [workflow2.yml ...]
-
-Validates EAS workflow YAML files against the official schema.`);
-    process.exit(files.length === 0 ? 1 : 0);
-  }
-
-  const schema = await fetchSchema();
-  const validator = createValidator(schema);
-
-  let hasErrors = false;
-
-  for (const file of files) {
-    const filePath = resolve(process.cwd(), file);
-    const result = await validateFile(validator, filePath);
-
-    if (result.valid) {
-      console.log(`✓ ${file}`);
-    } else {
-      console.error(`✗ ${file}\n${result.error}`);
-      hasErrors = true;
-    }
-  }
-
-  process.exit(hasErrors ? 1 : 0);
-}

package/dist/global-skills/expo-skill-feedback/scripts/skill-feedback.cjs

@@ -1,118 +0,0 @@
-#!/usr/bin/env node
-// Submit feedback about an Expo skill to PostHog.
-//
-// Usage:
-//   node skill-feedback.cjs --skill <name> --rating <rating> --text "..." \
-//     [--about skill|expo] [--agent-harness <harness>] [--dry-run]
-
-const {
-  POSTHOG_PROJECT_API_KEY,
-  SOURCE,
-  telemetryActive,
-  telemetryConfigured,
-  detectHarness,
-  platformProps,
-  telemetryIdentity,
-  sendToPosthog,
-} = require("./telemetry_common.cjs");
-
-const EVENT_NAME = "skill_feedback";
-const RATINGS = ["useful", "confusing", "bug", "idea", "other"];
-// What the feedback is about: the skill's own guidance (default), or Expo the
-// framework — when a skill fell short because of Expo itself, not the skill.
-const ABOUT_VALUES = ["skill", "expo"];
-const MAX_FEEDBACK_CHARS = 4000;
-
-function parseArgs(argv) {
-  const args = { skill: "", rating: "", text: "", about: "skill", agentHarness: "", dryRun: false };
-  for (let i = 0; i < argv.length; i++) {
-    const flag = argv[i];
-    const next = () => argv[++i] || "";
-    switch (flag) {
-      case "--skill": args.skill = next(); break;
-      case "--rating": args.rating = next(); break;
-      case "--text": args.text = next(); break;
-      case "--about": args.about = next(); break;
-      case "--agent-harness": args.agentHarness = next(); break;
-      case "--dry-run": args.dryRun = true; break;
-      default: break;
-    }
-  }
-  return args;
-}
-
-function eventPayload(args) {
-  const feedback = args.text.trim().slice(0, MAX_FEEDBACK_CHARS);
-  const skill = args.skill.trim();
-  const agentHarness = args.agentHarness.trim() || detectHarness();
-
-  if (!feedback) throw new Error("--text cannot be empty");
-  if (!skill) throw new Error("--skill cannot be empty");
-  if (!RATINGS.includes(args.rating)) throw new Error(`--rating must be one of: ${RATINGS.join(", ")}`);
-  const about = (args.about || "skill").trim() || "skill";
-  if (!ABOUT_VALUES.includes(about)) throw new Error(`--about must be one of: ${ABOUT_VALUES.join(", ")}`);
-
-  const timestamp = new Date().toISOString();
-  const [distinctId, identityProperties] = telemetryIdentity(agentHarness, { createInstallation: !args.dryRun });
-
-  return {
-    api_key: POSTHOG_PROJECT_API_KEY,
-    event: EVENT_NAME,
-    distinct_id: distinctId,
-    timestamp,
-    properties: {
-      $process_person_profile: false,
-      source: SOURCE,
-      ...identityProperties,
-      agent_harness: agentHarness,
-      ...platformProps(),
-      skill,
-      about,
-      rating: args.rating,
-      feedback_text: feedback,
-    },
-  };
-}
-
-async function main(argv) {
-  const args = parseArgs(argv);
-
-  if (!args.dryRun && !telemetryActive()) {
-    console.debug("skill-feedback: telemetry is off (opt-in, off by default); nothing sent. Enable with `telemetry.cjs --on` or EXPO_SKILLS_TELEMETRY=1.");
-    return 0;
-  }
-  if (!telemetryConfigured() && !args.dryRun) {
-    console.error("skill-feedback: no PostHog key in this build (key stripped to placeholder); nothing sent. Set EXPO_SKILLS_POSTHOG_KEY or restore the key in telemetry_common.cjs.");
-    return 0;
-  }
-
-  let payload;
-  try {
-    payload = eventPayload(args);
-  } catch (err) {
-    console.error(`skill-feedback: ${err.message}`);
-    return 2;
-  }
-
-  if (args.dryRun) {
-    console.log(JSON.stringify({ ...payload, api_key: "phc_..." }, null, 2));
-    return 0;
-  }
-
-  try {
-    await sendToPosthog(payload, { userAgent: "expo-skills/skill-feedback", timeoutMs: 10000 });
-  } catch (err) {
-    console.error(`skill-feedback: ${err.message}`);
-    return 1;
-  }
-
-  console.log(`sent skill feedback: ${payload.properties.skill}`);
-  return 0;
-}
-
-main(process.argv.slice(2))
-  .then((code) => process.exit(code))
-  .catch((err) => {
-    console.error(`skill-feedback: ${err && err.message ? err.message : err}`);
-    process.exit(1);
-  });