@wix/agent-skills 1.36.0 → 1.36.1

package/skills/wix-replatform/resources/rp-execute-setup/scripts/execute-setup.js

@@ -1,442 +0,0 @@
-#!/usr/bin/env node
-'use strict';
-
-const capabilities = require('../../../lib/execution-capability');
-const fs = require('node:fs/promises');
-const path = require('node:path');
-const crypto = require('node:crypto');
-const REAL_WRITERS = require('../../rp-target-wix/lib/wix-writers.js');
-const { SCHEMA_KIND: CONTACT_V4_SCHEMA_KIND } = require('../../rp-target-wix/lib/contact-extended-fields.js');
-const { hashArtifact } = require('../../../lib/artifact-freshness.js');
-const { validatePlanShape, validateSetupVerification } = require('../../../lib/setup-verification.js');
-
-// NOTE: 'wix-stores' intentionally still maps to 1380b703-... (Wix eCommerce, not Wix
-// Stores) here — a separate, independently-tracked defect, not part of this change. See
-// wix-writers.js's WIX_STORES_APP_ID (215238eb-...) for the correct id.
-const APPS = { 'wix-stores': '1380b703-ce81-ff05-f115-39571d94dfcd', 'wix-blog': '14bcded7-0066-7c35-14d7-466cb3f09103' };
-
-// Additional app-install step ids, added for projects whose setup plan needs apps this
-// executor previously had no executor for at all (a plan naming any of these used to fail
-// closed with NO_EXECUTOR_FOR_REQUIREMENT). Ids verified live against dev.wix.com's "Apps
-// Created by Wix" reference table, 2026-08-29 -- not from a docs example, and not reusing
-// the known-wrong 'wix-stores' id above. Idempotent: an app already installed is a pass,
-// not a redundant install call (see the isWixAppInstalled check in runStep below).
-const INSTALL_STEPS = {
-  'install-wix-stores': '215238eb-22a5-4c36-9e7b-e7c08025e04e',
-  'install-wix-gift-cards': 'd80111c5-a0f4-47a8-b63a-65b54d774a27',
-  'install-wix-blog': '14bcded7-0066-7c35-14d7-466cb3f09103',
-  'install-wix-events': '140603ad-af8d-84a5-2c80-a0f60cb47351',
-  'install-wix-data': 'e593b0bd-b783-45b8-97c2-873d42aacaf4',
-};
-
-async function readJson(file) {
-  return JSON.parse(await fs.readFile(file, 'utf8'));
-}
-
-async function readJsonIfExists(file) {
-  try {
-    return await readJson(file);
-  } catch (error) {
-    if (error.code === 'ENOENT') return null;
-    throw error;
-  }
-}
-
-async function readEnv(dir) {
-  const raw = await fs.readFile(path.join(dir, 'config', 'wix.env'), 'utf8');
-  return Object.fromEntries(
-    raw
-      .split(/\r?\n/)
-      .map((line) => line.match(/^([A-Z0-9_]+)=(.*)$/))
-      .filter(Boolean)
-      .map(([, key, value]) => [key, value.trim()]),
-  );
-}
-
-async function fallbackAuthor(dir, wix, writers) {
-  const id = path.basename(dir);
-  const email = `replatform-${id}@example.com`;
-  const listed = await writers.listMembers(wix, { limit: 100 });
-  let member = (listed.members || []).find((item) => String(item.loginEmail || '').toLowerCase() === email);
-  if (!member) member = await (writers.ensureBlogFallbackAuthor || writers.createMember)(wix, { email, name: 'Imported content', slug: `imported-content-${id}` });
-  if (!member?.id) throw new Error('fallback Blog author was not created');
-  const file = path.join(dir, 'config', 'wix.env');
-  const raw = await fs.readFile(file, 'utf8');
-  await fs.writeFile(
-    file,
-    `${raw.replace(/\n?WIX_BLOG_FALLBACK_MEMBER_ID=.*(?:\n|$)/g, '\n').replace(/\s*$/, '\n')}WIX_BLOG_FALLBACK_MEMBER_ID=${member.id}\n`,
-  );
-}
-
-// Creates one Wix Data collection via the real, verified request shape (top-level key is
-// `collection`, NOT `dataCollection` — confirmed live 2026-08-29 against a 400 "collection
-// must not be empty" response from the wrong key, and against CreateDataCollectionRequest's
-// real schema). Idempotent: a collection id that already exists (409 or an existing-id list
-// hit) is a pass, never a delete-and-recreate — matches this skill's own "never delete or
-// recreate an entity to fix a mismatch" rule.
-async function createCmsCollectionsStep({ dir, wix, writers }) {
-  const requirements = await readJsonIfExists(path.join(dir, 'setup', 'setup-requirements.json'));
-  const list = Array.isArray(requirements) ? requirements : requirements?.requirements;
-  const requirement = (list || []).find((item) => item && item.id === 'create-cms-collections');
-  if (!requirement) throw new Error('setup-requirements.json has no create-cms-collections requirement');
-
-  const existing = await wix.send(writers.buildListCmsCollectionsRequest());
-  const existingIds = new Set((existing.collections || []).map((c) => c.id));
-
-  const fields = (requirement.fieldSchemaPerCollection || []).map((f) => ({
-    key: f.key,
-    type: f.type,
-    displayName: f.displayName,
-    ...(f.required ? { required: true } : {}),
-  }));
-
-  for (const collection of requirement.collections || []) {
-    if (existingIds.has(collection.id)) continue; // already provisioned, not a redo
-    await writers.ensureCmsCollection(wix, { id: collection.id, displayName: collection.displayName, fields, permissions: requirement.permissions });
-  }
-}
-
-// Runs one setup-plan step. Throws (with `blockerCode`/`recommendedAction` attached where
-// the failure is a recognized, expected condition rather than a genuinely unexpected one)
-// on anything short of full success — the caller records the failure and stops the run
-// rather than letting a step's exception propagate past a recorded outcome.
-// Provisions every `extendedFieldSchema` requirement in the plan before any
-// writer can put a value in one. Blocked reasons become setup blockers rather than being retried
-// or worked around: a breaking schema change and an archived-key collision are both decisions for
-// a human, not for this executor.
-// A step is a provisioning step if it SAYS so, not only if it happens to be spelled
-// `provision-extended-fields`. Recognising one literal id meant discovery emitting a valid
-// requirement under any other natural id -- `setup-order-extended-fields`, say -- failed closed
-// with NO_EXECUTOR_FOR_REQUIREMENT and produced no receipt at all.
-const EXTENDED_FIELD_STEP_ID = 'provision-extended-fields';
-
-// A step provisions extended fields if it SAYS so -- by the conventional id, by declaring the
-// kind, or by a requirement naming it. Matching one literal id meant a requirement scheduled
-// under any other natural id (`setup-order-extended-fields`, say) was both reported as
-// unscheduled AND unexecutable. The scheduling guard and the dispatcher share this predicate so
-// they can never disagree about which steps count.
-function stepProvisionsExtendedFields(step, declaredList) {
-  if (!step) return false;
-  if (step.id === EXTENDED_FIELD_STEP_ID) return true;
-  if (step.kind === 'extendedFieldSchema') return true;
-  return (declaredList || []).some((item) => item
-    && item.kind === 'extendedFieldSchema'
-    && (item.setupStepId === step.id || item.id === step.id));
-}
-
-async function isExtendedFieldStep(step, dir) {
-  const requirements = await readJsonIfExists(path.join(dir, 'setup', 'setup-requirements.json'));
-  const list = Array.isArray(requirements) ? requirements : requirements?.requirements;
-  return stepProvisionsExtendedFields(step, list);
-}
-
-// Blocker codes that name their own remedy. Everything else stays EXTENDED_FIELD_SCHEMA_BLOCKED.
-const EXTENDED_FIELD_BLOCKERS = {
-  CONTACTS_V5_DES_UNVERIFIED: 'The Contacts V5 Data Extension Schema path is not verified on this site. Wait until it is verified, or explicitly route the mapping to contactWriteSurface "contacts-v4" (legacy), then re-run setup. Setup does not fall back automatically.',
-  EXTENDED_FIELD_SCHEMA_CONFLICT_EXHAUSTED: 'Another change kept updating this schema while setup ran. Re-run setup once the concurrent edits stop; nothing was overwritten.',
-  'schema-budget-exceeded': 'The namespace byte budget cannot hold these fields. Route the excess fields to a CMS collection instead of extended fields, then re-run setup.',
-  'contact-extended-field-mismatch': 'A legacy contact extended field on the site does not match what the migration needs (another type or namespace, or a key different from the one an earlier run verified). Wix keys cannot change, and approving a migration action cannot repair this. Decide with the site owner how to handle the existing field; do not create a second field for the same data. Then re-run setup.',
-};
-
-// Lower-case writer codes that get their own blocker code rather than the generic one.
-const EXTENDED_FIELD_BLOCKER_CODES = {
-  'contact-extended-field-mismatch': 'CONTACT_EXTENDED_FIELD_MISMATCH',
-};
-
-function extendedFieldBlockerCode(code) {
-  if (EXTENDED_FIELD_BLOCKER_CODES[code]) return EXTENDED_FIELD_BLOCKER_CODES[code];
-  return EXTENDED_FIELD_BLOCKERS[code] && /^[A-Z0-9_]+$/.test(code) ? code : 'EXTENDED_FIELD_SCHEMA_BLOCKED';
-}
-
-async function provisionExtendedFieldsStep({ dir, wix, writers, dryRun, priorVerification = null }) {
-  const requirements = await readJsonIfExists(path.join(dir, 'setup', 'setup-requirements.json'));
-  const list = Array.isArray(requirements) ? requirements : requirements?.requirements;
-  const schemaRequirements = (list || []).filter((item) => item && item.kind === 'extendedFieldSchema');
-  if (schemaRequirements.length === 0) {
-    throw new Error('setup-requirements.json has no extendedFieldSchema requirement');
-  }
-
-  const verifications = [];
-  for (const requirement of schemaRequirements) {
-    // Routed by the requirement's own schemaKind (DES for orders/products/contacts-v5, CRM
-    // Extended Fields for contacts-v4). Older writer fixtures expose only the DES entry point.
-    const provision = writers.provisionExtendedFieldRequirement || writers.provisionExtendedFieldSchema;
-    // eslint-disable-next-line no-await-in-loop
-    const result = await provision(wix, { requirement, dryRun, priorVerification });
-    if (result.blocking.length > 0) {
-      const first = result.blocking[0];
-      const named = EXTENDED_FIELD_BLOCKERS[first.code];
-      const where = requirement.fqdn ? `${requirement.fqdn} ${requirement.namespace}` : `${requirement.schemaKind} ${requirement.contactWriteSurface || ''}`.trim();
-      throw Object.assign(new Error(`${where}: ${first.detail}`), {
-        blockerCode: extendedFieldBlockerCode(first.code),
-        recommendedAction: named || 'Resolve the schema conflict on the destination site, or approve the migration action explicitly, then re-run setup.',
-      });
-    }
-    if (result.verification) verifications.push(result.verification);
-  }
-
-  if (!dryRun) {
-    // The writer guard reads this: a value write is refused unless setup verified that field.
-    await publishAtomically(
-      path.join(dir, 'setup', 'extended-field-verification.json'),
-      `${JSON.stringify({ schemaVersion: 1, verifications }, null, 2)}\n`,
-    );
-  }
-  return verifications;
-}
-
-async function runStep(step, { dir, env, wix, writers, priorExtendedFieldVerification = null }) {
-  if (step.id === 'mute-site-notifications') {
-    const state = await writers.muteSiteNotifications(wix, { reason: `RePlatform migration — ${path.basename(dir)}` });
-    if (!state?.muted) throw new Error('notification mute verification failed');
-    return;
-  }
-  if (APPS[step.id]) {
-    await writers.installWixApp(wix, { appDefId: APPS[step.id], siteId: env.WIX_SITE_ID });
-    return;
-  }
-  if (INSTALL_STEPS[step.id]) {
-    const appDefId = INSTALL_STEPS[step.id];
-    // isWixAppInstalled is optional (older writers fixtures/tests for the APPS path above
-    // don't provide it) -- fall back to an unconditional install when it's unavailable.
-    const alreadyInstalled = writers.isWixAppInstalled ? await writers.isWixAppInstalled(wix, appDefId) : false;
-    if (!alreadyInstalled) await writers.installWixApp(wix, { appDefId, siteId: env.WIX_SITE_ID });
-    return;
-  }
-  if (await isExtendedFieldStep(step, dir)) {
-    await provisionExtendedFieldsStep({ dir, wix, writers, dryRun: false, priorVerification: priorExtendedFieldVerification });
-    return;
-  }
-  if (step.id === 'create-cms-collections') {
-    await createCmsCollectionsStep({ dir, wix, writers });
-    return;
-  }
-  if (step.id === 'stores-catalog-v3') {
-    const result = await wix.send(writers.buildGetStoresCatalogVersionRequest());
-    if (result.catalogVersion !== 'V3_CATALOG') {
-      throw Object.assign(new Error(`Catalog V3 required (got ${result.catalogVersion || 'unknown'})`), {
-        blockerCode: 'CATALOG_V1',
-        recommendedAction: 'Use a destination site provisioned with Catalog V3, or omit Stores from this migration.',
-      });
-    }
-    return;
-  }
-  if (step.id === 'blog-fallback-author') {
-    await fallbackAuthor(dir, wix, writers);
-    return;
-  }
-  if (step.intent?.writerId) {
-    const executor = writers.createWixSetupExecutor({ wixClient: wix });
-    await executor.executeSetupStep(step);
-    // A declared reference is verified through its registered read builder, once per setup target.
-    if (step.referenceKeys?.length) {
-      const read = writers[step.intent.readWriterId];
-      if (typeof read !== 'function' || !/^build(Get|Query)/.test(step.intent.readWriterId || '')) throw new Error('setup_reference_readback_missing');
-      await wix.send(read(...(step.intent.readArgs || [])));
-    }
-    return;
-  }
-  throw Object.assign(new Error(`No executor implements setup step "${step.id}"`), {
-    blockerCode: 'NO_EXECUTOR_FOR_REQUIREMENT',
-    recommendedAction: 'Add an executor for this step id in execute-setup.js, or remove it from the setup plan.',
-  });
-}
-
-async function writeBlockers(setupDir, generatedAt, blockers) {
-  await fs.writeFile(
-    path.join(setupDir, 'setup-blockers.json'),
-    `${JSON.stringify({ schemaVersion: 1, generatedAt, blockers }, null, 2)}\n`,
-  );
-}
-
-// Writes the final file via a temp-then-rename so a crash mid-write can never leave a
-// corrupt or partial receipt where a trusted one is expected — the rename is atomic on the
-// same filesystem/directory.
-async function publishAtomically(filePath, contents) {
-  const tmpPath = path.join(path.dirname(filePath), `.${path.basename(filePath)}.${crypto.randomUUID()}.tmp`);
-  await fs.writeFile(tmpPath, contents);
-  await fs.rename(tmpPath, filePath);
-}
-
-// Core logic, independent of the CLI entry point below so tests can inject a fake
-// `writers` module instead of making real Wix API calls. Performs every file write itself
-// (the receipt, the blockers file) and returns a summary rather than throwing on a
-// recognized blocker — `main()` decides how to surface that to the process exit code.
-async function executeSetup({ dir, dryRun = false, writers = REAL_WRITERS }) {
-  const env = await readEnv(dir);
-  if (!env.WIX_SITE_ID || !env.WIX_AUTH_TOKEN) throw new Error('WIX_SITE_ID and WIX_AUTH_TOKEN are required');
-
-  const setupDir = path.join(dir, 'setup');
-  const verificationPath = path.join(setupDir, 'setup-verification.json');
-  const plan = await readJsonIfExists(path.join(setupDir, 'setup-plan.json'));
-  const generatedAt = new Date().toISOString();
-
-  // Read BEFORE the receipt is invalidated below: the legacy contacts-v4 path must prove a field's
-  // key did not change since an earlier verified run (Wix keys cannot change). Only used for that
-  // comparison, never as evidence that anything is provisioned now.
-  // Only a missing file means "no earlier run". A receipt that exists but cannot be read or
-  // parsed may hold keys a legacy contacts-v4 write already used; treating it as absent would let
-  // Find Or Create accept a different key and split old and new values across two fields.
-  let priorExtendedFieldVerification = null;
-  let priorReceiptError = null;
-  try {
-    priorExtendedFieldVerification = await readJsonIfExists(path.join(setupDir, 'extended-field-verification.json'));
-  } catch (error) {
-    priorReceiptError = error;
-  }
-  if (priorReceiptError) {
-    const declaredForPrior = await readJsonIfExists(path.join(setupDir, 'setup-requirements.json'));
-    const declaredPriorList = Array.isArray(declaredForPrior) ? declaredForPrior : declaredForPrior?.requirements;
-    const needsPriorKeys = (declaredPriorList || []).some((item) => item && item.kind === 'extendedFieldSchema' && item.schemaKind === CONTACT_V4_SCHEMA_KIND);
-    if (needsPriorKeys) {
-      const blocker = {
-        code: 'PRIOR_EXTENDED_FIELD_RECEIPT_UNREADABLE',
-        severity: 'blocker',
-        requirementId: null,
-        description: `setup/extended-field-verification.json exists but could not be read: ${String(priorReceiptError.message).slice(0, 200)}`,
-        whyBlocked: 'the legacy contact extended-field keys an earlier run verified cannot be checked, so a changed key could split contact values across two fields',
-        recommendedAction: 'Restore setup/extended-field-verification.json from the earlier run (it was left in place). Remove it only if no earlier import wrote legacy contact extended-field values. Then re-run setup.',
-      };
-      // Leave the unreadable receipt where it is for recovery; only the setup receipt is invalidated.
-      if (!dryRun) {
-        await fs.rm(verificationPath, { force: true });
-        await writeBlockers(setupDir, generatedAt, [blocker]);
-      }
-      return { ok: false, dryRun, requirements: [], blocker };
-    }
-    // DES-only runs never read prior keys, so an unreadable earlier receipt is simply replaced.
-  }
-
-  if (!dryRun) {
-    // Invalidate any prior receipt the instant a new live attempt begins — before we even
-    // know whether this attempt will succeed. A crash partway through this run (or a
-    // failure to reach the blocker-write below) must never leave an earlier, possibly
-    // no-longer-true success receipt sitting there looking trusted.
-    await fs.rm(verificationPath, { force: true });
-    // Same reasoning for the extended-field receipt: the writers consult it before putting a
-    // value in one of those fields, so a receipt from an earlier run must not outlive it.
-    await fs.rm(path.join(setupDir, 'extended-field-verification.json'), { force: true });
-  }
-
-  const planShape = validatePlanShape(plan);
-  if (!planShape.ok) {
-    const blocker = {
-      code: 'INVALID_SETUP_PLAN',
-      severity: 'blocker',
-      requirementId: null,
-      description: `setup-plan.json is invalid: ${planShape.reasons.join(', ')}`,
-      whyBlocked: planShape.reasons.join(', '),
-      recommendedAction: 'Regenerate setup/setup-plan.json with a valid schemaVersion, a steps array, and unique, non-empty step ids.',
-    };
-    if (dryRun) throw new Error(blocker.description);
-    await writeBlockers(setupDir, generatedAt, [blocker]);
-    return { ok: false, dryRun: false, requirements: [], blocker };
-  }
-
-  const planDigest = hashArtifact(dir, path.join('setup', 'setup-plan.json'));
-  const setupRun = capabilities.startSetupRun({ projectDir: dir, siteId: env.WIX_SITE_ID, dryRun });
-
-  // A requirement nobody scheduled provisions nothing. The writers that need those fields then
-  // refuse their writes, which is safe but fails late and for a reason that points at the wrong
-  // place -- so the mismatch is caught here, where the plan and the requirements are both in hand.
-  const declared = await readJsonIfExists(path.join(dir, 'setup', 'setup-requirements.json'));
-  const declaredList = Array.isArray(declared) ? declared : declared?.requirements;
-  const needsExtendedFields = (declaredList || []).some((item) => item && item.kind === 'extendedFieldSchema');
-  const schedulesExtendedFields = ((plan && plan.steps) || []).some((step) => stepProvisionsExtendedFields(step, declaredList));
-  if (needsExtendedFields && !schedulesExtendedFields) {
-    const blocker = {
-      code: 'EXTENDED_FIELD_REQUIREMENT_UNSCHEDULED',
-      severity: 'blocker',
-      requirementId: null,
-      description: 'setup-requirements.json declares an extendedFieldSchema requirement but setup-plan.json has no provision-extended-fields step',
-      whyBlocked: 'the fields would never be provisioned, and every writer that needs them would refuse its write later in the run',
-      recommendedAction: 'Add a "provision-extended-fields" step to the setup plan, or remove the extendedFieldSchema requirement.',
-    };
-    // A dry run reports; it does not leave artifacts behind. Writing the blockers file here made
-    // `dryRun: true` mutate the project and report itself as a live run.
-    if (!dryRun) await writeBlockers(path.join(dir, 'setup'), new Date().toISOString(), [blocker]);
-    return { ok: false, dryRun, requirements: [], blocker };
-  }
-
-  const requirements = [];
-  let blocker = null;
-
-  for (const step of plan.steps) {
-    if (dryRun) {
-      requirements.push({ id: step.id, status: 'planned_dry_run' });
-      continue;
-    }
-    try {
-      const stepCapability = capabilities.bindSetupStep(setupRun, step.id);
-      const wix = writers.createWixClient({ capability: stepCapability, authToken: env.WIX_AUTH_TOKEN });
-      await runStep(step, { dir, env, wix, writers, priorExtendedFieldVerification });
-      const referenceBindings = step.referenceKeys?.length ? writers.captureSetupReferenceBindings(wix, step) : undefined;
-      requirements.push({ id: step.id, status: 'passed', ...(referenceBindings ? { referenceBindings } : {}) });
-    } catch (error) {
-      requirements.push({ id: step.id, status: 'blocked', detail: error.message });
-      blocker = {
-        code: error.blockerCode || 'UNEXPECTED_SETUP_ERROR',
-        severity: 'blocker',
-        requirementId: step.id,
-        description: error.message,
-        whyBlocked: error.message,
-        recommendedAction: error.recommendedAction || 'Investigate the underlying error and re-run setup once resolved.',
-      };
-      break; // Stop at the first failure — later steps were never attempted, not skipped.
-    }
-  }
-
-  if (dryRun) {
-    await fs.writeFile(
-      path.join(setupDir, 'setup-dry-run.json'),
-      `${JSON.stringify({ schemaVersion: 1, generatedAt, dryRun: true, requirements }, null, 2)}\n`,
-    );
-    return { ok: true, dryRun: true, requirements, blocker: null };
-  }
-
-  if (blocker) {
-    // The old receipt (if any) was already removed above, before this attempt began.
-    await writeBlockers(setupDir, generatedAt, [blocker]);
-    return { ok: false, dryRun: false, requirements, blocker };
-  }
-
-  // Full success: every planned requirement passed. Self-check the candidate against the
-  // exact same validator the router uses before publishing it — there must be exactly one
-  // definition of "valid", shared, never re-implemented separately here.
-  const candidate = { schemaVersion: 1, generatedAt, siteId: env.WIX_SITE_ID, dryRun: false, planDigest, requirements };
-  const selfCheck = validateSetupVerification({ verification: candidate, plan, planDigest, siteId: env.WIX_SITE_ID });
-  if (!selfCheck.ok) {
-    const internalBlocker = {
-      code: 'INTERNAL_VALIDATION_FAILURE',
-      severity: 'blocker',
-      requirementId: null,
-      description: `execute-setup.js produced a receipt that failed its own validator: ${selfCheck.reasons.join(', ')}`,
-      whyBlocked: selfCheck.reasons.join(', '),
-      recommendedAction: 'This indicates a bug in execute-setup.js itself — investigate rather than retrying.',
-    };
-    await writeBlockers(setupDir, generatedAt, [internalBlocker]);
-    return { ok: false, dryRun: false, requirements, blocker: internalBlocker };
-  }
-
-  await writeBlockers(setupDir, generatedAt, []);
-  await publishAtomically(verificationPath, `${JSON.stringify(candidate, null, 2)}\n`);
-  return { ok: true, dryRun: false, requirements, blocker: null };
-}
-
-async function main() {
-  const dir = process.argv[2] && path.resolve(process.argv[2]);
-  if (!dir) throw new Error('Usage: execute-setup.js <projectDir> [--dry-run]');
-  const dryRun = process.argv.includes('--dry-run');
-  const result = await executeSetup({ dir, dryRun });
-  if (result.blocker) throw new Error(result.blocker.description);
-  console.log(JSON.stringify({ ok: true, dryRun }));
-}
-
-if (require.main === module) {
-  main().catch((error) => {
-    console.error(error.message);
-    process.exit(1);
-  });
-}
-
-module.exports = { executeSetup, runStep };

package/skills/wix-replatform/resources/rp-execute-setup/scripts/mint-token.sh

@@ -1,64 +0,0 @@
-#!/usr/bin/env bash
-# Mints a fresh Wix CLI token for a migration project's site and writes it
-# directly into config/wix.env as WIX_AUTH_TOKEN — never printing the value.
-#
-# Usage (from the migration project root):
-#   bash scripts/mint-token.sh
-#
-# Reads WIX_SITE_ID from config/wix.env.
-# Requires: npx @wix/cli@latest (logged in — check: npx @wix/cli@latest whoami)
-#
-# This is the canonical copy. rp-import-codegen copies it into
-# migrations/<project>/scripts/mint-token.sh during project scaffolding.
-
-set -euo pipefail
-
-SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-PROJECT_ROOT="$(dirname "$SCRIPT_DIR")"
-CONFIG_FILE="$PROJECT_ROOT/config/wix.env"
-
-if [[ ! -f "$CONFIG_FILE" ]]; then
-  echo "Error: config file not found: $CONFIG_FILE" >&2
-  exit 1
-fi
-
-WIX_SITE_ID=$(grep '^WIX_SITE_ID=' "$CONFIG_FILE" | cut -d'=' -f2- | tr -d '[:space:]')
-
-if [[ -z "$WIX_SITE_ID" ]]; then
-  echo "Error: WIX_SITE_ID is blank in $CONFIG_FILE" >&2
-  exit 1
-fi
-
-echo "Minting token for site $WIX_SITE_ID ..." >&2
-
-# Capture token only on stdout; suppress CLI spinner/progress on stderr
-TOKEN=$(npx @wix/cli@latest token --site "$WIX_SITE_ID" 2>/dev/null | tr -d '[:space:]')
-
-if [[ -z "$TOKEN" ]]; then
-  echo "Error: token command returned empty output" >&2
-  exit 1
-fi
-
-# Write into config (replace existing line, or append).
-# Not `sed -i`: BSD/macOS sed requires a backup-suffix argument for -i, so the
-# portable-looking GNU form silently consumes the expression as the suffix.
-# The token is passed through the environment, never as an awk -v value or on a
-# command line, so no escape processing can corrupt it and it stays out of `ps`.
-if grep -q '^WIX_AUTH_TOKEN=' "$CONFIG_FILE"; then
-  TMP_FILE="$(mktemp "${TMPDIR:-/tmp}/wix.env.XXXXXX")"
-  trap 'rm -f "$TMP_FILE"' EXIT
-  RP_NEW_TOKEN="$TOKEN" awk '
-    /^WIX_AUTH_TOKEN=/ { print "WIX_AUTH_TOKEN=" ENVIRON["RP_NEW_TOKEN"]; next }
-    { print }
-  ' "$CONFIG_FILE" > "$TMP_FILE"
-  # Copy contents rather than mv, so the config file keeps its own permissions.
-  cat "$TMP_FILE" > "$CONFIG_FILE"
-  rm -f "$TMP_FILE"
-else
-  printf '\nWIX_AUTH_TOKEN=%s\n' "$TOKEN" >> "$CONFIG_FILE"
-fi
-
-TOKEN_LEN=${#TOKEN}
-unset TOKEN
-
-echo "✓ WIX_AUTH_TOKEN written to config/wix.env ($TOKEN_LEN chars)" >&2

package/skills/wix-replatform/resources/rp-execution-policy/SKILL.md

@@ -1,112 +0,0 @@
----
-name: rp-execution-policy
-description: >-
-  Applies cross-stage execution safety policy and writes the aggregate migration completion
-  artifact after all delivery-specific terminal evidence validates.
----
-
-# rp-execution-policy
-
-Use this resource for the execution approval gate and aggregate finalization.
-
-For `awaiting_execution_approval`, present the generated execution plan, wait for the
-required user acceptance in normal mode, and persist it in `orchestration/approvals.json`.
-In explicit user-requested 1-click mode (`automationMode=one_click`, `source=user`), use the
-deterministic agent approval helper only after the plan and any required code-safety review
-validate. Then route again. A non-user-authored `one_click` value is normal interactive mode
-and must wait for user acceptance.
-
-## Disclosing what was read from a credential-bearing source surface
-
-If the run read payment-gateway configuration from the source, the plan presented at the
-approval gate must say so: that gateway configuration was read, which gateways were found, how
-many are enabled, how many credential fields are configured, and that **no credential value was
-retained**. The source adapter produces that line — for WordPress, `describeGatewaySummary()` in
-`rp-source-wordpress/lib/gateway-summary.mjs`.
-
-A run that reports "N gateways, M enabled, K credential fields present, 0 values retained" is
-auditable. One that read the same thing silently is not, and the user approving the plan has no
-way to tell the two apart. Never put a credential value, prefix, length or hash into the plan
-report itself.
-
-## Reporting the payments section of the plan
-
-If the run imports payment records, refunds or invoice documents, build that section of the plan
-with `lib/payments-report.js` rather than by hand. It enforces three things a hand-written summary
-has got wrong before, and it BLOCKS the approval gate rather than printing a caveat:
-
-- **The payment outcomes must sum to the discovered source-order population.** A report whose
-  numbers do not add up is hiding orders. The builder returns `approvable: false` with the
-  shortfall named.
-- **Zero is a result.** Every outcome and every count is emitted even at zero, so "0 refunds
-  found" is reviewable at a glance. An implausible number is cheapest to catch here.
-- **Candidate coverage is not writable coverage.** Orders carrying a reference-shaped value and
-  orders whose reference can be defensibly attributed are separate lines. Collapsing them
-  overstates fidelity.
-
-The denominator must come from the run's own reconciled reads (`from: 'run-reconciled-read'`), not
-from a prior survey. Where a survey counted differently, both numbers are shown and the
-discrepancy must be reconciled before the pilot.
-
-The provider inventory carries identifier, display name and enabled state only — a
-credential-shaped field on a provider blocks the gate. The phrase "you will lose your history" is
-prohibited: it is false for payment records, which are provider-independent.
-
-Run:
-
-```bash
-node skills/wix-replatform/scripts/migration-completion.js <projectDir>
-```
-
-This command validates backend completion accounting and, for website delivery, the
-frontend completion receipt. It writes `completion/migration-completion.json` atomically.
-
-It also refuses, on **both** delivery modes, unless the run produced its post-execution
-handoff and its execution log. A `management` run produces no website and used to require no
-handoff at all, which is how a backend-only migration could finalize with no account of itself
-anywhere in the project. The typed refusal reasons are:
-
-| Reason | Meaning |
-| --- | --- |
-| `missing_execution_log` | no `execution-log.md`; route back to the import step that owes the chronology |
-| `missing_post_execution_handoff` | no `execution/review/migration-handoff.json`; generate it from the final outcome record |
-| `completion_report_missing_last_write` | the completion report records no `lastWriteAt`, so nothing can prove the handoff postdates the import |
-| `post_execution_handoff_predates_last_write` | the handoff was generated before the run's last write — it describes the plan, not the run |
-
-The last two compare against the completion report's own recorded last-write timestamp, never
-a file mtime: an mtime is refreshed by a copy and proves nothing.
-If validation fails, do not manufacture completion; route again to the module that owns the
-missing or stale artifact.
-
-### Entity-QA attestation gate
-
-The same finalizer also refuses without a fresh, complete `execution/qa/entity-qa-attestation.json`
-that matches the current `execution/completion-report.json` digest and covers every mapped
-entity/subtype with matching counts (`rp-execute-import/SKILL.md`'s "Entity-by-entity QA"
-section). The refusal carries `entityQa: { qaStatus, entities, recheck }`:
-
-| `qaStatus` | Meaning | Action |
-| --- | --- | --- |
-| `missing` | no attestation file, it doesn't parse as JSON, its schema is invalid, there is no usable completion report to compare against, or the independent mapped-entity coverage source (`mapping/mapping-plan.json` or, for quick mode, `quick-mode/plan.json`) is unavailable | run the full entity-by-entity QA pass from `rp-execute-import`, then `scripts/entity-qa-attestation.js` |
-| `stale` | the attestation's `completionReportDigest` does not match the report that is shipping — a later pass rewrote it | run the full entity-by-entity QA pass again, then the writer; the shipped prose treats any report change as reopening the whole review |
-| `failed` | the attestation disagrees with the independent mapped-entity list or the report's own counts for one or more entities, named in `entityQa.entities` | dispatch a fresh Developer for the listed entities, then run the full QA pass and the writer |
-
-A valid attestation proves import-row freshness and coverage only (`scope:
-'import-entity-coverage'` in `migration-completion.json`) — never business setup or launch
-readiness, and never proof the QA pass itself happened rather than a copy of the report's own
-counts.
-
-## Reporting coupons, currency and plan definitions
-
-`lib/coupon-currency-plan-report.js` `buildCouponCurrencyPlanReport` renders the section and
-decides approvability the same way `payments-report.js` does: every line with its count including
-zero; per area `written + excluded + skipped = discovered`; exactly one currency outcome, and a
-mismatch or multi-currency history BLOCKS as a halt; the coupon-usage surface must be named. Two
-phrases are refused wherever they appear — "imported N coupons" (the honest headline is the
-redeemability breakdown) and "not supported" (zero plan rows is "none found", a measured fact).
-
-## Discovered-set status and safe refinalization
-
-For every standard-mode finalization, build `execution/discovered-set-status.json` with `node scripts/discovered-set-status.js build <projectDir>` after the completion report, then regenerate the post-execution handoff, retain the current entity-QA attestation, and run `node scripts/migration-completion.js <projectDir>`. Missing or stale census approval, reconciliation or status is a hold; rebuild the owning artifact and obtain a fresh mapping review where required. The final receipt is version 2. Open discovered-set rows keep a complete backend at `complete_with_warnings`, and the handoff and receipt must agree.
-
-On `reviewOnly: true`, refinalization uses the existing import outcomes. Make no Wix client, setup, codegen, import or website dispatch. Rebuild only the discovered-set status and post-execution handoff, then the aggregate completion; the writer archives the original version-1 receipt once. Any other route is held for the Import Operator. Manual work can be recorded only for a `manual-open` row, by the merchant or Cutover Operator through `node scripts/discovered-set-status.js resolve <projectDir> --census-id <id> --by merchant|cutover-operator --evidence <short non-record evidence>`. All other open outcomes require their existing mapping/import recovery path. Quick mode requires no discovered-set status.