@amerged/ohmyhost-mcp 0.1.22 → 0.1.24

package/src/packages/contracts/src/operation-data-change-result.ts

@@ -0,0 +1,86 @@
+import {
+  parseOperationDeploymentResult,
+  type OperationDeploymentResult,
+} from "./operation-deployment-result.js";
+
+export const OPERATION_DATA_CHANGE_RESULT_SCHEMA_VERSION =
+  "ohmyhost.operation-data-change-result/v1" as const;
+export interface OperationDataChangeResult {
+  readonly schemaVersion: typeof OPERATION_DATA_CHANGE_RESULT_SCHEMA_VERSION;
+  readonly operationId: string;
+  readonly change:
+    | "isolate_prod_keeps_data"
+    | "isolate_dev_keeps_data"
+    | "share_prod_keeps_data"
+    | "reset_dev";
+  readonly data_mode: "shared" | "isolated";
+  readonly redeploy_environments: readonly ("dev" | "prod")[];
+  readonly deleted_database: boolean;
+  readonly deleted_files: number;
+}
+export type OperationResult = OperationDeploymentResult | OperationDataChangeResult;
+
+export function createOperationDataChangeResult(
+  input: Omit<OperationDataChangeResult, "schemaVersion">,
+): OperationDataChangeResult {
+  return parseOperationDataChangeResult({
+    schemaVersion: OPERATION_DATA_CHANGE_RESULT_SCHEMA_VERSION,
+    ...input,
+  });
+}
+export function parseOperationDataChangeResult(value: unknown): OperationDataChangeResult {
+  if (value === null || typeof value !== "object" || Array.isArray(value)) invalid();
+  const input = value as Record<string, unknown>;
+  if (
+    Object.keys(input).sort().join(",") !==
+      "change,data_mode,deleted_database,deleted_files,operationId,redeploy_environments,schemaVersion" ||
+    input["schemaVersion"] !== OPERATION_DATA_CHANGE_RESULT_SCHEMA_VERSION ||
+    typeof input["operationId"] !== "string" ||
+    !/^[0-7][0-9A-HJKMNP-TV-Z]{25}$/u.test(input["operationId"])
+  )
+    invalid();
+  const change = input["change"];
+  if (
+    change !== "isolate_prod_keeps_data" &&
+    change !== "isolate_dev_keeps_data" &&
+    change !== "share_prod_keeps_data" &&
+    change !== "reset_dev"
+  )
+    invalid();
+  const retiring = change === "reset_dev" || change === "share_prod_keeps_data";
+  const redeploy = input["redeploy_environments"];
+  if (
+    input["data_mode"] !== (change === "share_prod_keeps_data" ? "shared" : "isolated") ||
+    !Array.isArray(redeploy) ||
+    redeploy.length !== 1 ||
+    redeploy[0] !== (change === "isolate_dev_keeps_data" ? "prod" : "dev") ||
+    typeof input["deleted_database"] !== "boolean" ||
+    !Number.isSafeInteger(input["deleted_files"]) ||
+    Number(input["deleted_files"]) < 0 ||
+    (!retiring && (input["deleted_database"] || input["deleted_files"] !== 0))
+  )
+    invalid();
+  return Object.freeze({
+    schemaVersion: OPERATION_DATA_CHANGE_RESULT_SCHEMA_VERSION,
+    operationId: input["operationId"],
+    change,
+    data_mode: input["data_mode"] as "shared" | "isolated",
+    redeploy_environments: Object.freeze([redeploy[0] as "dev" | "prod"]),
+    deleted_database: input["deleted_database"],
+    deleted_files: Number(input["deleted_files"]),
+  });
+}
+
+/** Keep the deployment-specific parser and its return type unchanged. */
+export function parseOperationResult(value: unknown): OperationResult {
+  return value !== null &&
+    typeof value === "object" &&
+    !Array.isArray(value) &&
+    (value as Record<string, unknown>)["schemaVersion"] ===
+      OPERATION_DATA_CHANGE_RESULT_SCHEMA_VERSION
+    ? parseOperationDataChangeResult(value)
+    : parseOperationDeploymentResult(value);
+}
+function invalid(): never {
+  throw new TypeError("Operation data change result is invalid");
+}

package/src/packages/contracts/{operation-deployment-result.ts → src/operation-deployment-result.ts}

@@ -91,9 +91,9 @@ const deploymentProgressActions = {
   publishing:
     "The build has completed. Runtime preparation or publication is still running; poll this same operation.",
   waiting_for_mail:
-    "Read 'ohmyhost mail domain status --project PROJECT --json' now and follow its verification issue and DNS records. Keep this operation; do not rebuild or repeat correct DNS changes.",
+    "Read 'ohmyhost mail status --project PROJECT --environment PROD_ENVIRONMENT_ULID --json' (MCP mail_status) now, with the Prod environment ID from 'ohmyhost project status', and follow its verification issue and DNS records. Keep this operation; do not rebuild or repeat correct DNS changes.",
   mail_status_unavailable:
-    "Mail readiness could not be observed. Read 'ohmyhost mail domain status --project PROJECT --json' and report a persistent error; keep this operation.",
+    "Mail readiness could not be observed. Read 'ohmyhost mail status --project PROJECT --environment PROD_ENVIRONMENT_ULID --json' (MCP mail_status) with the Prod environment ID from 'ohmyhost project status', and report a persistent error; keep this operation.",
 } as const;
 export type DeploymentProgressPhase = keyof typeof deploymentProgressActions;
 export interface OperationDeploymentProgress {

package/src/packages/contracts/{operation-failure.ts → src/operation-failure.ts}

@@ -1,11 +1,11 @@
 const failures = {
   operation_abandoned: [
-    "The operation stopped renewing its execution lease and was ended.",
-    "Inspect project status and, when this operation names a deployment_id, its diagnostics with 'ohmyhost deployment logs --project PROJECT_ULID --deployment DEPLOYMENT_ULID --follow --json' or MCP deployment_logs before creating a fresh plan. Keep this operation ID; the expired execution cannot resume.",
+    "ohmyho.st stopped this operation before it finished and ended it.",
+    "Repeating this operation cannot resume it. Read project status for what is live; if this operation names a deployment_id, read 'ohmyhost deployment logs --project PROJECT_ULID --deployment DEPLOYMENT_ULID --follow --json' or MCP deployment_logs. Then submit the request once more with a new idempotency key: a deployment, promotion, rollback or deletion from a fresh plan, a rename with the ETag from project status. If it ends the same way, report both operation IDs through feedback.",
   ],
   database_write_rejected: [
     "The database rejected this write; it was not committed.",
-    "Inspect the schema and parameter types with database query, then correct the statement and use a new key. Do not reset the database.",
+    "The statement failed on PostgreSQL, ran or waited for a lock longer than 5 seconds, affected more than 1,000 rows, or was not one INSERT, UPDATE or DELETE. Check table, column and parameter types with database query, split a large change into batches of at most 1,000 rows, then submit with a new key. Nothing was committed; do not reset the database.",
   ],
   database_write_unavailable: [
     "The database write could not start.",
@@ -58,7 +58,7 @@ const failures = {
   ],
   operation_failed: [
     "The operation failed.",
-    "Inspect the operation events and deployment diagnostics. Include the operation ID when reporting the issue.",
+    "Read project status and, if this operation names a deployment_id, its diagnostics with 'ohmyhost deployment logs --project PROJECT_ULID --deployment DEPLOYMENT_ULID --follow --json'. Without one (a source link or project creation), check project status or project list, then repeat that command once with a new idempotency key. If it fails again, report the operation ID through feedback.",
   ],
   build_not_started: [
     "The deployment ended without starting a build.",
@@ -66,7 +66,7 @@ const failures = {
   ],
   build_failed: [
     "The build did not produce a verified deployable artifact.",
-    "Read the BUILD_FAILED diagnostic of this operation's deployment_id with 'ohmyhost deployment logs --project PROJECT_ULID --deployment DEPLOYMENT_ULID --follow --json' or MCP deployment_logs; its excerpt is the tail of the install and build output. Correct that failure and verify the commands for the admitted commit before planning a new deployment.",
+    "Read the BUILD_FAILED item of this operation's deployment_id with 'ohmyhost deployment logs --project PROJECT_ULID --deployment DEPLOYMENT_ULID --follow --json' or MCP deployment_logs. Its excerpt is the tail of your install and build output: fix that error, push and plan the new commit. Without an excerpt the build printed nothing, passed the 8-minute limit or failed inside ohmyho.st: plan the same commit once more, and report the operation ID through feedback if it fails again.",
   ],
   insufficient_organization_credits: [
     "The organization does not have sufficient available credits for this operation.",
@@ -74,28 +74,40 @@ const failures = {
   ],
   paid_plan_required: [
     "Transactional mail requires an active Paid plan for this organization.",
-    "Activate or renew Paid for the organization, then create a new deployment plan. Replaying this terminal operation cannot enable mail. Do not change application code or reset its database.",
+    "Ask the organization Owner to activate Paid through billing checkout; top-ups and signup credits do not activate it. Then plan the same deployment or promotion again. If the app should send no mail, instead set mail.enabled to false in ohmyhost.yaml, commit and push, and plan the new commit. Replaying this operation cannot enable mail. Do not reset the database.",
   ],
   database_migration_failed: [
-    "The database migrations could not be applied.",
-    "Inspect the migration diagnostics and verify the canonical SQL migrations on PostgreSQL. Preserve production data; do not reset the database to retry a deployment.",
+    "The database migrations were not applied; none of this deployment's new migration files took effect.",
+    "Read the DATABASE_MIGRATION_FAILED item in 'ohmyhost deployment logs --project PROJECT_ULID --deployment DEPLOYMENT_ULID --follow --json' and fix what it names; run 'ohmyhost init --dry-run --json' for migration_sql_not_admitted. Keep applied files unchanged, give new files later timestamps, and add to existing tables only nullable columns without default and non-unique indexes. Push and plan the new commit; never reset the database.",
   ],
   runtime_candidate_failed: [
     "The deployed candidate failed its runtime checks.",
-    "Read the HEALTH_CHECK_FAILED diagnostic of this operation's deployment_id with 'ohmyhost deployment logs --project PROJECT_ULID --deployment DEPLOYMENT_ULID --follow --json' or MCP deployment_logs. Its route must answer 2xx to a cookieless GET without a redirect; status_code and, for owners, excerpt show what it answered. Fix that, often a missing secret or a redirect, then plan a new deployment.",
+    "Read the HEALTH_CHECK_FAILED item with 'ohmyhost deployment logs --project PROJECT_ULID --deployment DEPLOYMENT_ULID --follow --json' or MCP deployment_logs. ohmyhost.yaml runtime.healthcheck (default /) must answer 2xx to a cookieless GET without redirect; status_code and, for owners, excerpt show the answer. After a promotion or rollback, fix that environment, often a missing secret, and plan it again; else fix the app, push and plan the new commit. No such item: plan once more, then report.",
   ],
   runtime_candidate_rejected: [
-    "The runtime rejected the built Worker script.",
-    "Check that src/ohmyhost/worker.ts exports its handlers as the default export and imports no framework-only modules, then plan the new commit. Replaying this terminal operation cannot stage the same script.",
+    "The runtime refused to load the built Worker.",
+    "The built Worker could not be loaded: top-level code throws or calls fetch, timers or random values outside a handler, an import cannot be resolved, a Worker module such as src/ohmyhost/companion.ts has no default export, or the bundle is too large. Fix that, push and plan the new commit; replaying this operation cannot pass. If none of this applies, report the operation ID through feedback.",
   ],
   storage_jurisdiction_conflict: [
     "storage.jurisdiction must equal the project's hosting region.",
-    "Set storage.jurisdiction in ohmyhost.yaml to the project's hosting region shown by project status and plan again. A project cannot move its files between regions; do not delete or recreate the project to change it.",
+    "Set storage.jurisdiction in ohmyhost.yaml to the project's region (us or eu) shown by 'ohmyhost project status', commit and push, then plan the new commit (for a promotion, deploy it to Dev and promote again); the unchanged commit fails again. A project cannot move its files between regions; do not delete or recreate the project to change it.",
   ],
   provider_state_absent: [
     "Reconciliation confirmed that the required deployment resources are absent.",
     "Create a fresh deployment plan. The original operation is terminal; do not repeatedly reconcile it.",
   ],
+  auto_deploy_plan_rejected: [
+    "The GitHub push could not be planned for deployment.",
+    "Read project status and the operation's error or deployment diagnostics. Correct the source or configuration named there, push the new commit and plan it before deploying. Replaying this failed operation cannot start a build.",
+  ],
+  promotion_source_stale: [
+    "The Dev deployment changed before promotion could start.",
+    "Read the current Dev deployment with 'ohmyhost project status --project ULID --json', then run 'ohmyhost deployment promote plan' for that succeeded deployment and confirm the new plan. Replaying this terminal promotion cannot select another source.",
+  ],
+  promotion_target_stale: [
+    "The Prod deployment changed before promotion could start.",
+    "Read current Prod status, run 'ohmyhost deployment promote plan' again and confirm it with the new resource_etag and confirmation_token. Replaying this terminal operation cannot replace its stale target.",
+  ],
 } as const;
 
 export interface PublicOperationFailure {