npm - @amerged/ohmyhost-mcp - Versions diffs - 0.1.25 → 0.1.26 - Mend

@amerged/ohmyhost-mcp 0.1.25 → 0.1.26

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (10) hide show

package/README.md +1 -1
package/dist/{chunk-L5A5FEGY.js → chunk-K57THTQL.js} +2 -2
package/dist/index.js +1 -1
package/dist/stdio-main.js +2 -2
package/package.json +1 -1
package/src/apps/mcp/package.json +1 -1
package/src/apps/product-cli/package.json +1 -1
package/src/apps/product-cli/src/repository-init.ts +4 -2
package/src/packages/agent-skills/src/generated-skill-resources.ts +1 -1
package/src/packages/sdk-ts/package.json +1 -1

package/README.md CHANGED Viewed

@@ -1,6 +1,6 @@
 # @amerged/ohmyhost-mcp
-Local MCP server of ohmyho.st, version 0.1.25. Sign-in and setting secrets need the CLI too:
+Local MCP server of ohmyho.st, version 0.1.26. Sign-in and setting secrets need the CLI too:
 ```sh
 npm install --global @amerged/ohmyhost-cli @amerged/ohmyhost-mcp

package/dist/{chunk-L5A5FEGY.js → chunk-K57THTQL.js} RENAMED Viewed

@@ -8,7 +8,7 @@ var __export = (target, all) => {
 // apps/mcp/package.json
 var package_default = {
   name: "@ohmyhost/mcp",
-  version: "0.1.25",
+  version: "0.1.26",
   private: true,
   ohmyhost: {
     deployment: "production",
@@ -30653,7 +30653,7 @@ var GENERATED_SKILL_RESOURCES = Object.freeze([
     title: "ohmyhost-get-started",
     description: "Connect a customer agent to ohmyho.st. Determine what is already installed and signed in, guide the customer through browser sign-in, and select an organization before the first GitHub deployment. Also use when one computer holds several accounts, a prompt names the user and organization to work as, the customer needs support, or an automation needs a non-expiring API token. Use the deployment Skill once access is ready.",
     mimeType: "text/markdown",
-    text: '---\nname: ohmyhost-get-started\ndescription: Connect a customer agent to ohmyho.st. Determine what is already installed and signed in, guide the customer through browser sign-in, and select an organization before the first GitHub deployment. Also use when one computer holds several accounts, a prompt names the user and organization to work as, the customer needs support, or an automation needs a non-expiring API token. Use the deployment Skill once access is ready.\n---\n\n# Start with ohmyho.st\n\nConnect this agent to the customer\'s account, then continue with the selected GitHub app.\n\n## What ohmyho.st is and what you can do with it\n\nohmyho.st hosts a customer\'s GitHub app: Vite/React, TanStack Start, Next.js or a plain Worker\nmodule with HTTP handlers and optional cron schedules. Their coding agent operates it through the local\nMCP server or CLI, both calling the same REST API. Deploy a pushed commit to Dev or Prod,\nverify the app, and promote a tested Dev artifact when appropriate. Dev is protected by default;\nthe deployment Skill handles public Dev, data choices and the shared-database promotion rule.\nYou can also give the app Postgres, private runtime secrets, Cloudflare R2 files, optional\ntransactional mail and a custom domain, export its database as an encrypted SQL ZIP, and read\nusage, credits and project budgets. The customer keeps their own application authentication;\nnothing here replaces it. Sign-up is open and free to start.\n\nThe initial connection normally asks the customer to sign in and authorize GitHub for the\nworkspace. A working saved login or API token can avoid another sign-in, and a connected\nworkspace can reuse its GitHub connection. Optional payments, DNS/account consent or harness\nreloads can require further customer action; use the relevant Skill for the feature they chose.\n\nThe whole path, and the proof that each step is done:\n\n| Step | Result                                                        | Proof                                                                                                                         | Section      |\n| ---- | ------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- | ------------ |\n| 1    | You know what is installed and who is signed in               | `ohmyhost --version`, `ohmyhost whoami --json` or MCP `identity_get`, and the MCP tool list                                   | Step 1       |\n| 2    | CLI and MCP are current and registered                        | Installed versions match the published release; the harness\'s MCP `tools/list` exposes the tools after any required reload    | Step 2       |\n| 3    | The intended account is authenticated                         | `ohmyhost whoami --json` or MCP `identity_get` returns the intended user                                                      | Step 3       |\n| 4    | A workspace is selected                                       | The identity returns the intended organization                                                                                | Step 4       |\n| 5    | Access survives this session                                  | The same identity check succeeds from a fresh process with its chosen login or private token source                           | Step 5       |\n| 6    | GitHub is connected and existing projects are known           | MCP `github_status` returns `connected`; `projects_list` identifies a project to reuse                                        | Step 6       |\n| 7    | The repository is linked and the app is deployed and verified | MCP `source_get` confirms the linked repository; the deployment operation succeeds and the selected app URL passes its checks | Deploy Skill |\n\nEach step is a separate result. Confirm it using the Proof column; a completed browser page,\na saved MCP configuration or a started process does not substitute for its returned state.\n\nWhich Skill to read next:\n\n| The customer wants to \u2026                                          | Skill                              |\n| ---------------------------------------------------------------- | ---------------------------------- |\n| prepare or adapt an app so it runs here                          | ohmyhost-build-portable-app        |\n| convert a real Supabase database, Auth, Storage or Functions use | ohmyhost-migrate-supabase-postgres |\n| deploy a commit, verify it, promote Dev to Prod                  | ohmyhost-deploy-github             |\n| understand a queued, stuck or failed deployment, or report a bug | ohmyhost-troubleshoot-deployment   |\n| read or change data, database size or Dev-to-Prod migrations     | ohmyhost-manage-database           |\n| connect a custom domain or mail sender                           | ohmyhost-domains-and-mail          |\n| export the database as an encrypted backup                       | ohmyhost-export-database           |\n| see usage, credits or set a spending limit                       | ohmyhost-usage-and-budgets         |\n\nUsers normally reach this Skill from a prompt such as "connect this agent to ohmyho.st and deploy\nthis project". In that case finish Steps 1 to 6 with as few messages as possible, then continue\nwith the deployment Skill without asking again for anything already decided.\n\n## How to talk to the customer here\n\n- One action per message, in short plain sentences. Give the link, then what they will see.\n- Write in the language the customer writes in. Translate the message templates below; copy no\n  other sentence from this file into the chat.\n- Keep customer-facing messages focused on the action and why it is needed. Avoid narrating\n  routine internal steps; explain an actual limitation when it prevents the requested work.\n- Wait for required browser input before taking actions that depend on it. Independent repository\n  inspection can continue while the customer signs in; do not start another sign-in for the same\n  account or repeat the instruction without new information. Respect the customer\'s existing authorization and scope.\n- Never ask for a password, an email code or a token value. Never paste a credential into chat,\n  source or a command argument.\n- After they report back, verify with a command instead of trusting the report.\n\n## Step 1 \u2014 determine the state before doing anything\n\nIf the customer\'s prompt names an account ("Use my ohmyho.st account user \u2026 in organization \u2026"),\nread "Several accounts on one computer" first. Use that login\'s `--profile-name` on authenticated\nchecks when needed. Then run these checks:\n\n```sh\nohmyhost --version\nohmyhost whoami --json\nohmyhost profile list --json\n```\n\nAlso list the MCP tools of the `ohmyho` server. A saved configuration alone is not a working connection.\n\nRead the result:\n\n| Observation                                               | State                      | Continue with    |\n| --------------------------------------------------------- | -------------------------- | ---------------- |\n| `ohmyhost` missing, or the MCP server exposes no tools    | not installed              | Step 2           |\n| `--version` is older than the published release           | outdated                   | Step 2           |\n| CLI runs, `whoami` fails with `authentication_required`   | installed, signed out      | Step 3           |\n| `whoami` fails with `credential_store_unavailable`        | no usable credential store | Step 5           |\n| `whoami` returns an identity with an organization         | ready                      | Step 5           |\n| `whoami` returns `next_action` instead of an organization | signed in, no workspace    | Step 4           |\n| `whoami` fails with `profile_selection_required`          | several saved logins       | Several accounts |\n\n`whoami` selects the workspace itself when the customer has exactly one, so an identity that\narrives with an organization needs no workspace step. Without an organization, `next_action`\nmeans the choice would be a guess or no workspace exists yet. With an organization,\n`next_action` can name `github connect`: that workspace has no GitHub connection yet, and Step 6\nhandles it.\n\nIf `OHMYHOST_TOKEN` is set in this process, that token is the credential: the CLI and MCP ignore any\nsaved login. Verify its returned identity, organization and selected platform against the task,\neven if a browser is already signed in. If `whoami` succeeds for that account, go to Step 5 without\nstarting another login. If it fails, ask the customer to update the private credential source,\nnot to paste a replacement value into chat.\nDo not send them to a sign-in link, because `ohmyhost login` refuses to run while the variable is set.\nWith a working token, `profile list` can still answer `credential_store_unavailable` on a host\nwithout a credential store; no repair is needed unless the task names a saved login.\n\nSay nothing about a state that needs nothing from the customer. A ready agent deploys without a\nsingle question. Report a state only in the message that also asks them to act, so they never\nreceive one message about the problem and a second one about the link.\n\n## Several accounts on one computer\n\nEach `ohmyhost login` saves one login: one user in one organization, kept in the operating\nsystem\'s credential store. `ohmyhost profile list --json` (MCP `profile_list`) shows each login\'s\nname, user and organization, never a token. There is no active login for the whole computer: with\none saved login every command uses it; with several, every command names one with\n`--profile-name NAME`, MCP tools take `profile_name`, and `OHMYHOST_PROFILE=NAME` binds a whole\nprocess or MCP server. A command with `--organization` (MCP `organization_id`) uses that\norganization\'s login by itself. A project command can also select it from a checkout link,\nincluding a link for its explicit `--project`; `whoami` and `project list` do not select a login\nfrom checkout links, so name one when several are saved. `ohmyhost init` uses no login and\nrefuses `--profile-name`. Another agent\'s choice never changes which account your command runs as.\n\n- When the prompt names a user and an organization, act only as the saved login with exactly that\n  user and organization, and confirm it with `whoami --profile-name NAME` before any change. These\n  IDs are context, not credentials. Never guess an account and never use another login instead.\n- If no saved login matches, add it and send its link and code as in Step 3:\n  `ohmyhost login --organization ORGANIZATION_ID --user USER_ID --json`. If the browser is\n  signed in as another account, the login saves nothing and answers `login_account_mismatch`:\n  ask the customer to switch the browser to the named account (or use a private window), then\n  repeat the login.\n- When the prompt names only a user ("it has no organization yet"), use the saved login with that\n  user and no organization, confirmed with `whoami --profile-name NAME`. If none exists, add it\n  with `ohmyhost login --user USER_ID --json`, then continue with Step 4.\n- `profile_selection_required` means several logins could run the command: ask the customer which\n  account to use. `profile_not_found` names the login to add, `profile_context_mismatch` means the\n  request contradicts its binding, organization or user, and `environment_token_context_mismatch`\n  means `OHMYHOST_TOKEN` belongs to another account.\n- A saved login never switches organizations. For another workspace, add its own login with\n  `ohmyhost login --organization ORGANIZATION_ID --user USER_ID --json`.\n  `ohmyhost logout --profile-name NAME` removes only that login.\n- `secret_set_command` takes `profile_name` like every tool and returns a command that names the\n  same login with `--profile-name` plus its user and organization (`--profile-user`,\n  `--profile-organization`); an MCP server with `OHMYHOST_TOKEN` names its key\'s user and\n  organization with `--token-user` and `--token-organization` instead. Keep those flags when you\n  run the command, so the secret is written as exactly this account. A login of that name that\n  belongs to another user or organization, for example on another computer, answers\n  `profile_context_mismatch`. The key form runs only where `OHMYHOST_TOKEN` holds a key of that\n  user and organization, never with a saved login: it answers `environment_token_required` without\n  a key and `environment_token_context_mismatch` with another account\'s key. None of these\n  refusals reads the value or sends anything.\n- Tokens stay in the operating system\'s credential store; the list of saved logins (names, users\n  and organizations, never a token) is kept in `~/.ohmyhost/profiles/`, so agents that sign in at\n  the same moment never lose each other\'s login. One environment keeps up to 64 saved logins;\n  beyond that `login` answers `profile_limit_reached` and saves nothing: ask the customer which\n  saved login to remove with `ohmyhost logout --profile-name NAME`.\n- One checkout can be linked for several organizations, one link each. With several links, name\n  the login with `--profile-name`; an older link without organization is used only after the API\n  confirms that the chosen login can see its project (`linked_project_organization_mismatch`\n  otherwise).\n- Errors that depend on the account name it in `acting_as`: `resource_not_found` with another\n  account\'s login means the wrong login, `github_connection_required` means that workspace has no\n  GitHub connection yet, and `repository_not_installed` means its GitHub App installation does not\n  cover the repository.\n\n## Step 2 \u2014 install what is missing\n\nRead <https://ohmyho.st/llms.txt> and the [CLI/MCP installation guide](https://docs.ohmyho.st/agents/mcp).\nCompare the installed versions with <https://ohmyho.st/client-release.json>: `ohmyhost --version`\nnames the CLI, and `npm ls --global --depth=0` lists both packages (`ohmyhost-mcp` has no\n`--version` flag; it starts the server). When either is missing or older, install both from the\nsource already in use: the current archive URLs from that guide, or npm\n(`npm install --global @amerged/ohmyhost-cli @amerged/ohmyhost-mcp`). Both provide the same\n`ohmyhost` and `ohmyhost-mcp` commands, so uninstall one pair before switching to the other.\nAn older client lacks commands and rejects newer server responses with `response_contract_invalid`;\nan older MCP server reports the same case as `client_request_failed` although connection and login\nwork. Upgrade both clients and reload MCP before treating either as a platform fault; if both are\ncurrent, report it with `feedback_submit`.\n\nRead [harness setup](references/harness-setup.md) and register the local `ohmyhost-mcp` command with this harness\'s documented settings. Preserve other MCP servers, model choices and permission settings. Use `OHMYHOST_ENVIRONMENT=production` for CLI and MCP unless the customer explicitly selected the development platform.\n\nEvery CLI command and MCP tool is listed in [surfaces](references/surfaces.md); use it to find the exact name of a capability a customer asks for instead of guessing or assuming it is missing.\n\nReload the MCP connection after every install or upgrade, then verify `tools/list` and `resources/list`. A running server keeps the tool list it started with, so a freshly installed version is invisible until it restarts. Repeat Step 1 afterwards.\n\n## Step 3 \u2014 the customer signs in once\n\n```sh\nohmyhost login --json\n```\n\nWhen the prompt named a user and organization, add\n`--organization ORGANIZATION_ID --user USER_ID`, so nothing is saved unless the browser signs in\nas exactly that account. Each login is saved under a name derived from its organization;\n`--profile-name NAME` chooses another (lowercase letters, digits, `-` and `_`, starting with a\nletter or digit, at most 63 characters; another name answers `invalid_command`). If that name\nalready belongs to another saved login (`profile_name_conflict`), choose a different name;\nremove the other login only when the customer asks.\n\nStart it as a background process and read its output while it runs: a sign-in link, a confirmation\ncode such as `ABCD-EFGH` and how many minutes both stay valid appear on stderr at once. The\ncommand waits up to 30 minutes for the customer and saves the login only when it ends by itself;\na harness timeout that stops it earlier saves nothing. The sign-in page shows the same code and\nasks the customer to confirm it. Send one message with the full link, code and validity, then\nwait for the customer while leaving the command running.\n\n> I found no valid ohmyho.st login for this account on this computer. Open this link to connect it:\n>\n> [full link exactly as printed]\n>\n> The page shows the code **[code]**. Continue only if it shows exactly this code.\n> Sign in there, or choose **Sign up** on that same page if you do not have an account yet.\n> Link and code are valid for [minutes] minutes; if the page rejects the code, say so and I will send a new one.\n> Tell me when you are done.\n\nRules for this step:\n\n- Always show the code. Every message that carries a sign-in link also carries its code, the first\n  time and after every repeated login. The customer checks it against the page; a code that\n  appears on the page but never in the chat gives them nothing to check.\n- Write the full link on its own line, exactly as the CLI printed it, so the customer sees the\n  address before opening it. Never hide it behind words like "this link" or "sign-in link" and\n  never shorten it; a bare address the chat makes clickable is fine. The customer types nothing.\n- State how long link and code are valid, taking the number from the CLI\'s own message rather than\n  inventing one.\n- Do not ask whether they have an account. The same page serves both, so naming both costs one\n  sentence and saves a round trip.\n- Sign-up is open. There is no invitation, no waitlist and no access code. Never send the customer\n  somewhere else to request access.\n- Wait for the customer. The command completes on its own once they finish; do not start a second\n  login while the first is still open.\n- A confirmation code lives only a few minutes. While `ohmyhost login --json` still runs, it\n  replaces a lapsed code by itself for up to 30 minutes and prints the new link and code: send\n  them the same way. Run the original login command again, keeping its account flags, only\n  after it ended with `device_authorization_expired`. This is expected, not a failure: do not\n  report an error or suggest the customer did something wrong.\n\nWhen the command returns, verify and continue:\n\n```sh\nohmyhost whoami --json\n```\n\n## Step 4 \u2014 make sure a workspace is selected\n\n`login` and `whoami` select the workspace themselves when the customer has exactly one, and their\nresponse names the selected organization. They report `next_action` with several choices, and then\nthe customer decides; with no workspace at all, create the first one. `organization use` binds a\nlogin that has no organization yet; a login that already has one keeps it (use a separate login\nfor another workspace, see "Several accounts on one computer").\n\nAlways look before creating. A verified first portal signup creates or reuses **My workspace**,\nincluding a direct signup or one with an invalid referral. The customer may also have a workspace\nfrom an earlier session:\n\n```sh\nohmyhost organization list --json\nohmyhost organization use --organization "$ORGANIZATION_ID" --json\n```\n\nCreate a workspace only when that list is empty, with a name the customer gave you:\n\n```sh\nohmyhost organization create --name "$ORGANIZATION_NAME" --source "$SIGNUP_SOURCE" --idempotency-key "$ORGANIZATION_REQUEST_KEY" --json\nohmyhost whoami --json\n```\n\n- `--source` (MCP `signup_source`) is optional attribution. If the task mentioned a campaign,\n  referral (`https://ohmyho.st/?r=ref-\u2026`) or flag (`https://ohmyho.st/?r=flag-\u2026`) link, pass its\n  single accepted `r` value unchanged (lowercase letters, digits, `-` and `_`, starting with a\n  letter or digit, at most 64 characters); otherwise omit it. The portal treats a malformed\n  value as Direct, so missing or invalid attribution never blocks signup and earns no referral\n  bonus. The server decides any once-per-user benefit: an eligible\n  referral or active flag on the first workspace gives 1,000 credits and 30 days of Paid, and a\n  registered campaign can add credits; promise nothing else. Attribution is never an access\n  code or secret and is fixed per user: later workspaces pass the same Signup source shown on\n  the portal\'s Profile page (omit the flag for Direct); another value answers `forbidden`.\n- Reuse the same name, source and idempotency key after an interrupted response instead of creating a second organization.\n- Creating a workspace selects it immediately for a login that had none; `whoami` or `identity_get` confirms the selection before you create a project. A login already in another workspace keeps it, and the response names the `login` that adds one for the new workspace.\n- Over MCP, `organization_create`, `organization_list` and `organization_use` do the same and report the same `selected` workspace.\n- Creating, listing and selecting a workspace need the interactive login. An API token can do none of them, and says so.\n- Never create another workspace on your own when the customer already has one.\n- A session that selected none lists no projects: `projects_list` and `ohmyhost project list` answer `organization_required` instead of an empty page. Select a workspace, then read the list again.\n\n## Step 5 \u2014 keep access for later\n\nThe current CLI login is enough to continue; MCP uses it.\n\n`ohmyhost login` saves each login in the operating system\'s credential store, and MCP reads it\nthere. `credential_store_unavailable` means the CLI cannot use that store. On a desktop, ask the\ncustomer to unlock it, then retry. In a container, CI runner or headless Linux, do not start a\nsign-in that cannot be saved: ask the customer to create a user token at\n<https://app.ohmyho.st/tokens> and load it as `OHMYHOST_TOKEN` from a private env file.\n\nFor automation, use `token_create` with `out_file`, or\n`ohmyhost token create --organization ULID --name NAME --idempotency-key KEY --out .env.local --json`.\nThe client appends `OHMYHOST_TOKEN` once to that private env file, sets mode `600` and returns\nonly metadata; the value is never shown in the client result and cannot be read again. The file\nname must start or end with `.env`, be ignored by Git or lie outside the repository\n(`token_file_not_ignored`), and not already hold `OHMYHOST_TOKEN` (`token_file_has_token`).\nConfigure the process to load it. Preserve existing credentials and never put the value in chat,\nsource or a command argument. If `token_file_changed` names an issued key that could not be saved,\nrevoke that key with `token_revoke` or the returned CLI command before creating a replacement\nwith a new idempotency key; `token_value_unavailable` means use the original file or revoke and\nreplace the key, since replay cannot reveal its value.\n\n`OHMYHOST_TOKEN` overrides the saved logins in any process where it is set. A token alone runs every\ncommand in these Skills except these, which need the interactive login: `login`, `logout` (including\n`logout --revoke`), `organization create|list|use`, and `token create|list|revoke`. Run those in a\nprocess without the variable. Never delete a saved token file. A token belongs to one account and\norganization: a command that names another (`--profile-name`, `--organization`, or a checkout\nlinked for another organization) is refused with `environment_token_context_mismatch` before\nanything is sent.\n\n## Step 6 \u2014 continue with the app\n\nConfirm the selected directory and GitHub repository. Read `github_status` for the selected workspace. If it is not connected, an Owner or Admin uses `github_connect` (CLI below), opens its single `authorization_url`, then repeats the same request/key after the browser completes until the returned status is `connected`.\n\n```sh\nohmyhost github status --organization "$ORGANIZATION_ID" --json\nohmyhost github connect --organization "$ORGANIZATION_ID" --idempotency-key "$GITHUB_CONNECT_KEY" --json\n```\n\nThe one link handles the required installation/user authorization. Do not construct a second installation link, replay OAuth callbacks, or ask for an installation ID or provider token. Use the intended GitHub browser profile. A connected installation covers only its selected repositories; if one is missing, open `connection.settings_url` from status, add the repository and repeat its original source-link request/key.\n\nMCP/REST returns these objects directly. CLI JSON wraps the handoff in `authorization` and status\nin `github`: read `authorization.authorization_url` and `github.connection.settings_url`.\nThe handoff lives 30 minutes (`expires_at`). While `pending`, a `last_failure` of\n`provider_unavailable` or `authorization_code_rejected` means reopen the returned\n`authorization_url` with the same key. `failed` or `expired` is final: `account_admin_required`\nneeds the GitHub account owner or organization admin, `installation_access_required` means the\nApp was not installed for that account, `session_inactive` needs a fresh login by a workspace\nOwner or Admin, and `denied` means the customer declined. Resolve the cause, then connect with a\nnew key for the same workspace; never poll a terminal failure.\n\nUse `projects_list` to reuse a project and `project_context_get` when resuming one. Preserve an existing project\'s region. For a new project, an explicit customer region wins; otherwise use a browser-location hint supplied in the customer\'s onboarding prompt and send that region explicitly. Without either, ask once for US or EU. Never infer customer location from the agent/server IP. The API default remains US; the selected region cannot change later.\n\nContinue with the **ohmyhost-deploy-github** Skill when a deployment is requested. Login, workspace creation, GitHub connection and project linking are distinct results; check each returned state rather than treating a completed browser page as deployment success.\n\nSupport runs through this agent. When the customer needs help, reports a bug or asks for a feature, submit a redacted report with `feedback_submit` (CLI `ohmyhost feedback submit`), give the customer the receipt ID and read replies later with `feedback_status`; the **ohmyhost-troubleshoot-deployment** Skill describes a good report. Point the customer to https://ohmyho.st/contact only when they cannot sign in, a billing issue names `contact_support`, or they ask about privacy or the DPA. The customer page is https://docs.ohmyho.st/support.\n'
+    text: '---\nname: ohmyhost-get-started\ndescription: Connect a customer agent to ohmyho.st. Determine what is already installed and signed in, guide the customer through browser sign-in, and select an organization before the first GitHub deployment. Also use when one computer holds several accounts, a prompt names the user and organization to work as, the customer needs support, or an automation needs a non-expiring API token. Use the deployment Skill once access is ready.\n---\n\n# Start with ohmyho.st\n\nConnect this agent to the customer\'s account, then continue with the selected GitHub app.\n\n## What ohmyho.st is and what you can do with it\n\nohmyho.st hosts a customer\'s GitHub app: Vite/React, TanStack Start, Next.js or a plain Worker\nmodule with HTTP handlers and optional cron schedules. Their coding agent operates it through the local\nMCP server or CLI, both calling the same REST API. Deploy a pushed commit to Dev or Prod,\nverify the app, and promote a tested Dev artifact when appropriate. Dev is protected by default;\nthe deployment Skill handles public Dev, data choices and the shared-database promotion rule.\nYou can also give the app Postgres, private runtime secrets, Cloudflare R2 files, optional\ntransactional mail and a custom domain, export its database as an encrypted SQL ZIP, and read\nusage, credits and project budgets. The customer keeps their own application authentication;\nnothing here replaces it. Sign-up is open and free to start.\n\nThe initial connection normally asks the customer to sign in and authorize GitHub for the\nworkspace. A working saved login or API token can avoid another sign-in, and a connected\nworkspace can reuse its GitHub connection. Optional payments, DNS/account consent or harness\nreloads can require further customer action; use the relevant Skill for the feature they chose.\n\nThe whole path, and the proof that each step is done:\n\n| Step | Result                                                        | Proof                                                                                                                         | Section      |\n| ---- | ------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- | ------------ |\n| 1    | You know what is installed and who is signed in               | `ohmyhost --version`, `ohmyhost whoami --json` or MCP `identity_get`, and the MCP tool list                                   | Step 1       |\n| 2    | CLI and MCP are current and registered                        | Installed versions match the published release; the harness\'s MCP `tools/list` exposes the tools after any required reload    | Step 2       |\n| 3    | The intended account is authenticated                         | `ohmyhost whoami --json` or MCP `identity_get` returns the intended user                                                      | Step 3       |\n| 4    | A workspace is selected                                       | The identity returns the intended organization                                                                                | Step 4       |\n| 5    | Access survives this session                                  | The same identity check succeeds from a fresh process with its chosen login or private token source                           | Step 5       |\n| 6    | GitHub is connected and existing projects are known           | MCP `github_status` returns `connected`; `projects_list` identifies a project to reuse                                        | Step 6       |\n| 7    | The repository is linked and the app is deployed and verified | MCP `source_get` confirms the linked repository; the deployment operation succeeds and the selected app URL passes its checks | Deploy Skill |\n\nEach step is a separate result. Confirm it using the Proof column; a completed browser page,\na saved MCP configuration or a started process does not substitute for its returned state.\n\nWhich Skill to read next:\n\n| The customer wants to \u2026                                          | Skill                              |\n| ---------------------------------------------------------------- | ---------------------------------- |\n| prepare or adapt an app so it runs here                          | ohmyhost-build-portable-app        |\n| convert a real Supabase database, Auth, Storage or Functions use | ohmyhost-migrate-supabase-postgres |\n| deploy a commit, verify it, promote Dev to Prod                  | ohmyhost-deploy-github             |\n| understand a queued, stuck or failed deployment, or report a bug | ohmyhost-troubleshoot-deployment   |\n| read or change data, database size or Dev-to-Prod migrations     | ohmyhost-manage-database           |\n| connect a custom domain or mail sender                           | ohmyhost-domains-and-mail          |\n| export the database as an encrypted backup                       | ohmyhost-export-database           |\n| see usage, credits or set a spending limit                       | ohmyhost-usage-and-budgets         |\n\nUsers normally reach this Skill from a prompt such as "connect this agent to ohmyho.st and deploy\nthis project". In that case finish Steps 1 to 6 with as few messages as possible, then continue\nwith the deployment Skill without asking again for anything already decided.\n\n## How to talk to the customer here\n\n- One action per message, in short plain sentences. Give the link, then what they will see.\n- Write in the language the customer writes in. Translate the message templates below; copy no\n  other sentence from this file into the chat.\n- Keep customer-facing messages focused on the action and why it is needed. Avoid narrating\n  routine internal steps; explain an actual limitation when it prevents the requested work.\n- Wait for required browser input before taking actions that depend on it. Independent repository\n  inspection can continue while the customer signs in; do not start another sign-in for the same\n  account or repeat the instruction without new information. Respect the customer\'s existing authorization and scope.\n- Never ask for a password, an email code or a token value. Never paste a credential into chat,\n  source or a command argument.\n- After they report back, verify with a command instead of trusting the report.\n\n## Step 1 \u2014 determine the state before doing anything\n\nIf the customer\'s prompt names an account ("Use my ohmyho.st account user \u2026 in organization \u2026"),\nread "Several accounts on one computer" first. Use that login\'s `--profile-name` on authenticated\nchecks when needed. Then run these checks:\n\n```sh\nohmyhost --version\nohmyhost whoami --json\nohmyhost profile list --json\n```\n\nAlso list the MCP tools of the `ohmyho` server. A saved configuration alone is not a working connection.\n\nRead the result:\n\n| Observation                                               | State                      | Continue with    |\n| --------------------------------------------------------- | -------------------------- | ---------------- |\n| `ohmyhost` missing, or the MCP server exposes no tools    | not installed              | Step 2           |\n| `--version` is older than the published release           | outdated                   | Step 2           |\n| CLI runs, `whoami` fails with `authentication_required`   | installed, signed out      | Step 3           |\n| `whoami` fails with `credential_store_unavailable`        | no usable credential store | Step 5           |\n| `whoami` returns an identity with an organization         | ready                      | Step 5           |\n| `whoami` returns `next_action` instead of an organization | signed in, no workspace    | Step 4           |\n| `whoami` fails with `profile_selection_required`          | several saved logins       | Several accounts |\n\n`whoami` selects the workspace itself when the customer has exactly one, so an identity that\narrives with an organization needs no workspace step. Without an organization, `next_action`\nmeans the choice would be a guess or no workspace exists yet. With an organization,\n`next_action` can name `github connect`: that workspace has no GitHub connection yet, and Step 6\nhandles it.\n\nIf `OHMYHOST_TOKEN` is set in this process, that token is the credential: the CLI and MCP ignore any\nsaved login. Verify its returned identity, organization and selected platform against the task,\neven if a browser is already signed in. If `whoami` succeeds for that account, go to Step 5 without\nstarting another login. If it fails, ask the customer to update the private credential source,\nnot to paste a replacement value into chat.\nDo not send them to a sign-in link, because `ohmyhost login` refuses to run while the variable is set.\nWith a working token, `profile list` can still answer `credential_store_unavailable` on a host\nwithout a credential store; no repair is needed unless the task names a saved login.\n\nSay nothing about a state that needs nothing from the customer. A ready agent deploys without a\nsingle question. Report a state only in the message that also asks them to act, so they never\nreceive one message about the problem and a second one about the link.\n\n## Several accounts on one computer\n\nEach `ohmyhost login` saves one login: one user in one organization, kept in the operating\nsystem\'s credential store. `ohmyhost profile list --json` (MCP `profile_list`) shows each login\'s\nname, user and organization, never a token. There is no active login for the whole computer: with\none saved login every command uses it; with several, every command names one with\n`--profile-name NAME`, MCP tools take `profile_name`, and `OHMYHOST_PROFILE=NAME` binds a whole\nprocess or MCP server. A command with `--organization` (MCP `organization_id`) uses that\norganization\'s login by itself. A project command can also select it from a checkout link,\nincluding a link for its explicit `--project`; `whoami` and `project list` do not select a login\nfrom checkout links, so name one when several are saved. `ohmyhost init` uses no login and\nrefuses `--profile-name`. Another agent\'s choice never changes which account your command runs as.\n\n- When the prompt names a user and an organization, act only as the saved login with exactly that\n  user and organization, and confirm it with `whoami --profile-name NAME` before any change. These\n  IDs are context, not credentials. Never guess an account and never use another login instead.\n- If no saved login matches, add it and send its link and code as in Step 3:\n  `ohmyhost login --organization ORGANIZATION_ID --user USER_ID --json`. If the browser is\n  signed in as another account, the login saves nothing and answers `login_account_mismatch`:\n  ask the customer to switch the browser to the named account (or use a private window), then\n  repeat the login.\n- When the prompt names only a user ("it has no organization yet"), use the saved login with that\n  user and no organization, confirmed with `whoami --profile-name NAME`. If none exists, add it\n  with `ohmyhost login --user USER_ID --json`, then continue with Step 4.\n- `profile_selection_required` means several logins could run the command: ask the customer which\n  account to use. `profile_not_found` names the login to add, `profile_context_mismatch` means the\n  request contradicts its binding, organization or user, and `environment_token_context_mismatch`\n  means `OHMYHOST_TOKEN` belongs to another account.\n- A saved login never switches organizations. For another workspace, add its own login with\n  `ohmyhost login --organization ORGANIZATION_ID --user USER_ID --json`.\n  `ohmyhost logout --profile-name NAME` removes only that login.\n- `secret_set_command` takes `profile_name` like every tool and returns a command that names the\n  same login with `--profile-name` plus its user and organization (`--profile-user`,\n  `--profile-organization`); an MCP server with `OHMYHOST_TOKEN` names its key\'s user and\n  organization with `--token-user` and `--token-organization` instead. Keep those flags when you\n  run the command, so the secret is written as exactly this account. A login of that name that\n  belongs to another user or organization, for example on another computer, answers\n  `profile_context_mismatch`. The key form runs only where `OHMYHOST_TOKEN` holds a key of that\n  user and organization, never with a saved login: it answers `environment_token_required` without\n  a key and `environment_token_context_mismatch` with another account\'s key. None of these\n  refusals reads the value or sends anything.\n- Tokens stay in the operating system\'s credential store; the list of saved logins (names, users\n  and organizations, never a token) is kept in `~/.ohmyhost/profiles/`, so agents that sign in at\n  the same moment never lose each other\'s login. One environment keeps up to 64 saved logins;\n  beyond that `login` answers `profile_limit_reached` and saves nothing: ask the customer which\n  saved login to remove with `ohmyhost logout --profile-name NAME`.\n- One checkout can be linked for several organizations, one link each. With several links, name\n  the login with `--profile-name`; an older link without organization is used only after the API\n  confirms that the chosen login can see its project (`linked_project_organization_mismatch`\n  otherwise).\n- Errors that depend on the account name it in `acting_as`: `resource_not_found` with another\n  account\'s login means the wrong login, `github_connection_required` means that workspace has no\n  GitHub connection yet, and `repository_not_installed` means its GitHub App installation does not\n  cover the repository.\n\n## Step 2 \u2014 install what is missing\n\nRead <https://ohmyho.st/llms.txt> and the [CLI/MCP installation guide](https://docs.ohmyho.st/agents/mcp).\nCompare the installed versions with <https://ohmyho.st/client-release.json>: `ohmyhost --version`\nnames the CLI, and `npm ls --global --depth=0` lists both packages (`ohmyhost-mcp` has no\n`--version` flag; it starts the server). When either is missing or older, install both from the\nsource already in use: the current archive URLs from that guide, or npm\n(`npm install --global @amerged/ohmyhost-cli @amerged/ohmyhost-mcp`). Both provide the same\n`ohmyhost` and `ohmyhost-mcp` commands, so uninstall one pair before switching to the other.\nAn older client lacks commands and rejects newer server responses with `response_contract_invalid`;\nan older MCP server reports the same case as `client_request_failed` although connection and login\nwork. Upgrade both clients and reload MCP before treating either as a platform fault; if both are\ncurrent, report it with `feedback_submit`.\n\nRead [harness setup](references/harness-setup.md) and register the local `ohmyhost-mcp` command with this harness\'s documented settings. Preserve other MCP servers, model choices and permission settings. Use `OHMYHOST_ENVIRONMENT=production` for CLI and MCP unless the customer explicitly selected the development platform.\n\nEvery CLI command and MCP tool is listed in [surfaces](references/surfaces.md); use it to find the exact name of a capability a customer asks for instead of guessing or assuming it is missing.\n\nReload the MCP connection after every install or upgrade, then verify `tools/list` and `resources/list`. A running server keeps the tool list it started with, so a freshly installed version is invisible until it restarts. Repeat Step 1 afterwards.\n\n## Step 3 \u2014 the customer signs in once\n\n```sh\nohmyhost login --json\n```\n\nWhen the prompt named a user and organization, add\n`--organization ORGANIZATION_ID --user USER_ID`, so nothing is saved unless the browser signs in\nas exactly that account. Each login is saved under a name derived from its organization;\n`--profile-name NAME` chooses another (lowercase letters, digits, `-` and `_`, starting with a\nletter or digit, at most 63 characters; another name answers `invalid_command`). If that name\nalready belongs to another saved login (`profile_name_conflict`), choose a different name;\nremove the other login only when the customer asks.\n\nStart it as a background process and read its output while it runs: a sign-in link, a confirmation\ncode such as `ABCD-EFGH` and how many minutes both stay valid appear on stderr at once. The\ncommand waits up to 30 minutes for the customer and saves the login only when it ends by itself;\na harness timeout that stops it earlier saves nothing. The sign-in page shows the same code and\nasks the customer to confirm it. Send one message with the full link, code and validity, then\nwait for the customer while leaving the command running.\n\n> I found no valid ohmyho.st login for this account on this computer. Open this link to connect it:\n>\n> [full link exactly as printed]\n>\n> The page shows the code **[code]**. Continue only if it shows exactly this code.\n> Sign in there, or choose **Sign up** on that same page if you do not have an account yet.\n> Link and code are valid for [minutes] minutes; if the page rejects the code, say so and I will send a new one.\n> Tell me when you are done.\n\nRules for this step:\n\n- Always show the code. Every message that carries a sign-in link also carries its code, the first\n  time and after every repeated login. The customer checks it against the page; a code that\n  appears on the page but never in the chat gives them nothing to check.\n- Write the full link on its own line, exactly as the CLI printed it, so the customer sees the\n  address before opening it. Never hide it behind words like "this link" or "sign-in link" and\n  never shorten it; a bare address the chat makes clickable is fine. The customer types nothing.\n- State how long link and code are valid, taking the number from the CLI\'s own message rather than\n  inventing one.\n- Do not ask whether they have an account. The same page serves both, so naming both costs one\n  sentence and saves a round trip.\n- Sign-up is open. There is no invitation, no waitlist and no access code. Never send the customer\n  somewhere else to request access.\n- Wait for the customer. The command completes on its own once they finish; do not start a second\n  login while the first is still open.\n- A confirmation code lives only a few minutes. While `ohmyhost login --json` still runs, it\n  replaces a lapsed code by itself for up to 30 minutes and prints the new link and code: send\n  them the same way. Run the original login command again, keeping its account flags, only\n  after it ended with `device_authorization_expired`. This is expected, not a failure: do not\n  report an error or suggest the customer did something wrong.\n\nWhen the command returns, verify and continue:\n\n```sh\nohmyhost whoami --json\n```\n\n## Step 4 \u2014 make sure a workspace is selected\n\n`login` and `whoami` select the workspace themselves when the customer has exactly one, and their\nresponse names the selected organization. They report `next_action` with several choices, and then\nthe customer decides; with no workspace at all, create the first one. `organization use` binds a\nlogin that has no organization yet; a login that already has one keeps it (use a separate login\nfor another workspace, see "Several accounts on one computer").\n\nAlways look before creating. A verified first portal signup creates or reuses **My workspace**,\nincluding a direct signup or one with an invalid referral. The customer may also have a workspace\nfrom an earlier session:\n\n```sh\nohmyhost organization list --json\nohmyhost organization use --organization "$ORGANIZATION_ID" --json\n```\n\nCreate a workspace only when that list is empty, with a name the customer gave you:\n\n```sh\nohmyhost organization create --name "$ORGANIZATION_NAME" --source "$SIGNUP_SOURCE" --idempotency-key "$ORGANIZATION_REQUEST_KEY" --json\nohmyhost whoami --json\n```\n\n- `--source` (MCP `signup_source`) is optional attribution. If the task mentioned a campaign,\n  referral (`https://ohmyho.st/?r=ref-\u2026`) or flag (`https://ohmyho.st/?r=flag-\u2026`) link, pass its\n  single accepted `r` value unchanged (lowercase letters, digits, `-` and `_`, starting with a\n  letter or digit, at most 64 characters); otherwise omit it. The portal treats a malformed\n  value as Direct, so missing or invalid attribution never blocks signup and earns no referral\n  bonus. The server decides any once-per-user benefit: an eligible\n  referral or active flag on the first workspace gives 1,000 credits and 30 days of Paid, and a\n  registered campaign can add credits; promise nothing else. Attribution is never an access\n  code or secret and is fixed per user: later workspaces pass the same Signup source shown on\n  the portal\'s Profile page (omit the flag for Direct); another value answers `forbidden`.\n- Reuse the same name, source and idempotency key after an interrupted response instead of creating a second organization.\n- Creating a workspace selects it immediately for a login that had none; `whoami` or `identity_get` confirms the selection before you create a project. A login already in another workspace keeps it, and the response names the `login` that adds one for the new workspace.\n- Over MCP, `organization_create`, `organization_list` and `organization_use` do the same and report the same `selected` workspace.\n- Creating, listing and selecting a workspace need the interactive login. An API token can do none of them, and says so.\n- Never create another workspace on your own when the customer already has one.\n- A session that selected none lists no projects: `projects_list` and `ohmyhost project list` answer `organization_required` instead of an empty page. Select a workspace, then read the list again.\n\n## Step 5 \u2014 keep access for later\n\nThe current CLI login is enough to continue; MCP uses it.\n\n`ohmyhost login` saves each login in the operating system\'s credential store, and MCP reads it\nthere. `credential_store_unavailable` means the CLI cannot use that store. On a desktop, ask the\ncustomer to unlock it, then retry. In a container, CI runner or headless Linux, do not start a\nsign-in that cannot be saved: ask the customer to create a user token at\n<https://app.ohmyho.st/tokens> and load it as `OHMYHOST_TOKEN` from a private env file.\n\nFor automation, use `token_create` with `out_file`, or\n`ohmyhost token create --organization ULID --name NAME --idempotency-key KEY --out .env.local --json`.\nThe client appends `OHMYHOST_TOKEN` once to that private env file, sets mode `600` and returns\nonly metadata; the value is never shown in the client result and cannot be read again. The file\nname must start or end with `.env`, be ignored by Git or lie outside the repository\n(`token_file_not_ignored`), and not already hold `OHMYHOST_TOKEN` (`token_file_has_token`).\nConfigure the process to load it. Preserve existing credentials and never put the value in chat,\nsource or a command argument. If `token_file_changed` names an issued key that could not be saved,\nrevoke that key with `token_revoke` or the returned CLI command before creating a replacement\nwith a new idempotency key; `token_value_unavailable` means use the original file or revoke and\nreplace the key, since replay cannot reveal its value.\n\n`OHMYHOST_TOKEN` overrides the saved logins in any process where it is set. A token alone runs every\ncommand in these Skills except these, which need the interactive login: `login`, `logout` (including\n`logout --revoke`), `organization create|list|use`, and `token create|list|revoke`. Run those in a\nprocess without the variable. Never delete a saved token file. A token belongs to one account and\norganization: a command that names another (`--profile-name`, `--organization`, or a checkout\nlinked for another organization) is refused with `environment_token_context_mismatch` before\nanything is sent.\n\n## Step 6 \u2014 continue with the app\n\nConfirm the selected directory and GitHub repository. Read `github_status` for the selected workspace. If it is not connected, an Owner or Admin uses `github_connect` (CLI below), opens its single `authorization_url`, then repeats the same request/key after the browser completes until the returned status is `connected`.\n\n```sh\nohmyhost github status --organization "$ORGANIZATION_ID" --json\nohmyhost github connect --organization "$ORGANIZATION_ID" --idempotency-key "$GITHUB_CONNECT_KEY" --json\n```\n\nThe one link handles the required installation/user authorization. Do not construct a second installation link, replay OAuth callbacks, or ask for an installation ID or provider token. Use the intended GitHub browser profile. A connected installation covers only its selected repositories; if one is missing, open `connection.settings_url` from status, add the repository and repeat its original source-link request/key.\n\nMCP/REST returns these objects directly. CLI JSON wraps the handoff in `authorization` and status\nin `github`: read `authorization.authorization_url` and `github.connection.settings_url`.\nThe handoff lives 30 minutes (`expires_at`). While `pending`, a `last_failure` of\n`provider_unavailable` or `authorization_code_rejected` means reopen the returned\n`authorization_url` with the same key. `failed` or `expired` is final: `account_admin_required`\nneeds the GitHub account owner or organization admin, `installation_access_required` means the\nApp was not installed for that account, `session_inactive` needs a fresh login by a workspace\nOwner or Admin, and `denied` means the customer declined. Resolve the cause, then connect with a\nnew key for the same workspace; never poll a terminal failure.\n\nUse `projects_list` to reuse a project and `project_context_get` when resuming one. Preserve an existing project\'s region. For a new project, an explicit customer region wins; otherwise use a browser-location hint supplied in the customer\'s onboarding prompt and send that region explicitly. Without either, ask once for US or EU. Never infer customer location from the agent/server IP. The API default remains US; the selected region cannot change later.\n\nContinue with the **ohmyhost-deploy-github** Skill when a deployment is requested. Login, workspace creation, GitHub connection and project linking are distinct results; check each returned state rather than treating a completed browser page as deployment success.\n\nFor a repository containing several apps, run local `init` from its Git root and check that the\nrepository-root `ohmyhost.yaml` selects the intended `applicationRoot` before planning the pushed\ncommit. For example, `applicationRoot: apps/web` selects that app\'s sources and migrations;\nan `ohmyhost.yaml` inside `apps/web` does not override the repository\'s selection. Compare the\nlocal result with the plan\'s `application_root` and keep any admission diagnostic visible.\n\nSupport runs through this agent. When the customer needs help, reports a bug or asks for a feature, submit a redacted report with `feedback_submit` (CLI `ohmyhost feedback submit`), give the customer the receipt ID and read replies later with `feedback_status`; the **ohmyhost-troubleshoot-deployment** Skill describes a good report. Point the customer to https://ohmyho.st/contact only when they cannot sign in, a billing issue names `contact_support`, or they ask about privacy or the DPA. The customer page is https://docs.ohmyho.st/support.\n'
   },
   {
     skillName: "ohmyhost-get-started",

package/dist/index.js CHANGED Viewed

@@ -2,7 +2,7 @@ import { createRequire as __ohmyhostCreateRequire } from "node:module"; const re
 import {
   createOhmyhostMcpServer,
   ohmyhostMcpHandler
-} from "./chunk-L5A5FEGY.js";
+} from "./chunk-K57THTQL.js";
 export {
   createOhmyhostMcpServer,
   ohmyhostMcpHandler

package/dist/stdio-main.js CHANGED Viewed

@@ -27,7 +27,7 @@ import {
   serverIdentityOf,
   setNegotiatedProtocolVersion,
   validateEnvelopeMeta
-} from "./chunk-L5A5FEGY.js";
+} from "./chunk-K57THTQL.js";
 // node_modules/.pnpm/@modelcontextprotocol+server@2.0.0/node_modules/@modelcontextprotocol/server/dist/stdio.mjs
 var StdioServerTransport = class {
@@ -812,7 +812,7 @@ function exact2(v, keys) {
 // apps/product-cli/package.json
 var package_default2 = {
   name: "@ohmyhost/product-cli",
-  version: "0.1.25",
+  version: "0.1.26",
   private: true,
   ohmyhost: {
     deployment: "production",

package/package.json CHANGED Viewed

@@ -1,6 +1,6 @@
 {
   "name": "@amerged/ohmyhost-mcp",
-  "version": "0.1.25",
+  "version": "0.1.26",
   "type": "module",
   "engines": {
     "node": ">=22"

package/src/apps/mcp/package.json CHANGED Viewed

@@ -1,6 +1,6 @@
 {
   "name": "@ohmyhost/mcp",
-  "version": "0.1.25",
+  "version": "0.1.26",
   "private": true,
   "ohmyhost": {
     "deployment": "production",

package/src/apps/product-cli/package.json CHANGED Viewed

@@ -1,6 +1,6 @@
 {
   "name": "@ohmyhost/product-cli",
-  "version": "0.1.25",
+  "version": "0.1.26",
   "private": true,
   "ohmyhost": {
     "deployment": "production",

package/src/apps/product-cli/src/repository-init.ts CHANGED Viewed

@@ -292,8 +292,10 @@ export async function initializeRepository(
   const supabaseMigrationCount = applicationFiles.filter((path) =>
     /^supabase\/migrations\/[^/]+\.sql$/u.test(path),
   ).length;
-  const postgresMigrationCount = applicationFiles.filter((path) =>
-    /^postgres\/migrations\/[^/]+\.sql$/u.test(path),
+  const postgresMigrationRoot =
+    existingConfiguration?.database?.migrations ?? "postgres/migrations";
+  const postgresMigrationCount = applicationFiles.filter(
+    (path) => path.startsWith(`${postgresMigrationRoot}/`) && path.endsWith(".sql"),
   ).length;
   const edgeFunctionNames = new Set(
     applicationFiles.flatMap((path) => {

package/src/packages/agent-skills/src/generated-skill-resources.ts CHANGED Viewed

@@ -84,7 +84,7 @@ export const GENERATED_SKILL_RESOURCES = Object.freeze([
     description:
       "Connect a customer agent to ohmyho.st. Determine what is already installed and signed in, guide the customer through browser sign-in, and select an organization before the first GitHub deployment. Also use when one computer holds several accounts, a prompt names the user and organization to work as, the customer needs support, or an automation needs a non-expiring API token. Use the deployment Skill once access is ready.",
     mimeType: "text/markdown",
-    text: '---\nname: ohmyhost-get-started\ndescription: Connect a customer agent to ohmyho.st. Determine what is already installed and signed in, guide the customer through browser sign-in, and select an organization before the first GitHub deployment. Also use when one computer holds several accounts, a prompt names the user and organization to work as, the customer needs support, or an automation needs a non-expiring API token. Use the deployment Skill once access is ready.\n---\n\n# Start with ohmyho.st\n\nConnect this agent to the customer\'s account, then continue with the selected GitHub app.\n\n## What ohmyho.st is and what you can do with it\n\nohmyho.st hosts a customer\'s GitHub app: Vite/React, TanStack Start, Next.js or a plain Worker\nmodule with HTTP handlers and optional cron schedules. Their coding agent operates it through the local\nMCP server or CLI, both calling the same REST API. Deploy a pushed commit to Dev or Prod,\nverify the app, and promote a tested Dev artifact when appropriate. Dev is protected by default;\nthe deployment Skill handles public Dev, data choices and the shared-database promotion rule.\nYou can also give the app Postgres, private runtime secrets, Cloudflare R2 files, optional\ntransactional mail and a custom domain, export its database as an encrypted SQL ZIP, and read\nusage, credits and project budgets. The customer keeps their own application authentication;\nnothing here replaces it. Sign-up is open and free to start.\n\nThe initial connection normally asks the customer to sign in and authorize GitHub for the\nworkspace. A working saved login or API token can avoid another sign-in, and a connected\nworkspace can reuse its GitHub connection. Optional payments, DNS/account consent or harness\nreloads can require further customer action; use the relevant Skill for the feature they chose.\n\nThe whole path, and the proof that each step is done:\n\n| Step | Result                                                        | Proof                                                                                                                         | Section      |\n| ---- | ------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- | ------------ |\n| 1    | You know what is installed and who is signed in               | `ohmyhost --version`, `ohmyhost whoami --json` or MCP `identity_get`, and the MCP tool list                                   | Step 1       |\n| 2    | CLI and MCP are current and registered                        | Installed versions match the published release; the harness\'s MCP `tools/list` exposes the tools after any required reload    | Step 2       |\n| 3    | The intended account is authenticated                         | `ohmyhost whoami --json` or MCP `identity_get` returns the intended user                                                      | Step 3       |\n| 4    | A workspace is selected                                       | The identity returns the intended organization                                                                                | Step 4       |\n| 5    | Access survives this session                                  | The same identity check succeeds from a fresh process with its chosen login or private token source                           | Step 5       |\n| 6    | GitHub is connected and existing projects are known           | MCP `github_status` returns `connected`; `projects_list` identifies a project to reuse                                        | Step 6       |\n| 7    | The repository is linked and the app is deployed and verified | MCP `source_get` confirms the linked repository; the deployment operation succeeds and the selected app URL passes its checks | Deploy Skill |\n\nEach step is a separate result. Confirm it using the Proof column; a completed browser page,\na saved MCP configuration or a started process does not substitute for its returned state.\n\nWhich Skill to read next:\n\n| The customer wants to …                                          | Skill                              |\n| ---------------------------------------------------------------- | ---------------------------------- |\n| prepare or adapt an app so it runs here                          | ohmyhost-build-portable-app        |\n| convert a real Supabase database, Auth, Storage or Functions use | ohmyhost-migrate-supabase-postgres |\n| deploy a commit, verify it, promote Dev to Prod                  | ohmyhost-deploy-github             |\n| understand a queued, stuck or failed deployment, or report a bug | ohmyhost-troubleshoot-deployment   |\n| read or change data, database size or Dev-to-Prod migrations     | ohmyhost-manage-database           |\n| connect a custom domain or mail sender                           | ohmyhost-domains-and-mail          |\n| export the database as an encrypted backup                       | ohmyhost-export-database           |\n| see usage, credits or set a spending limit                       | ohmyhost-usage-and-budgets         |\n\nUsers normally reach this Skill from a prompt such as "connect this agent to ohmyho.st and deploy\nthis project". In that case finish Steps 1 to 6 with as few messages as possible, then continue\nwith the deployment Skill without asking again for anything already decided.\n\n## How to talk to the customer here\n\n- One action per message, in short plain sentences. Give the link, then what they will see.\n- Write in the language the customer writes in. Translate the message templates below; copy no\n  other sentence from this file into the chat.\n- Keep customer-facing messages focused on the action and why it is needed. Avoid narrating\n  routine internal steps; explain an actual limitation when it prevents the requested work.\n- Wait for required browser input before taking actions that depend on it. Independent repository\n  inspection can continue while the customer signs in; do not start another sign-in for the same\n  account or repeat the instruction without new information. Respect the customer\'s existing authorization and scope.\n- Never ask for a password, an email code or a token value. Never paste a credential into chat,\n  source or a command argument.\n- After they report back, verify with a command instead of trusting the report.\n\n## Step 1 — determine the state before doing anything\n\nIf the customer\'s prompt names an account ("Use my ohmyho.st account user … in organization …"),\nread "Several accounts on one computer" first. Use that login\'s `--profile-name` on authenticated\nchecks when needed. Then run these checks:\n\n```sh\nohmyhost --version\nohmyhost whoami --json\nohmyhost profile list --json\n```\n\nAlso list the MCP tools of the `ohmyho` server. A saved configuration alone is not a working connection.\n\nRead the result:\n\n| Observation                                               | State                      | Continue with    |\n| --------------------------------------------------------- | -------------------------- | ---------------- |\n| `ohmyhost` missing, or the MCP server exposes no tools    | not installed              | Step 2           |\n| `--version` is older than the published release           | outdated                   | Step 2           |\n| CLI runs, `whoami` fails with `authentication_required`   | installed, signed out      | Step 3           |\n| `whoami` fails with `credential_store_unavailable`        | no usable credential store | Step 5           |\n| `whoami` returns an identity with an organization         | ready                      | Step 5           |\n| `whoami` returns `next_action` instead of an organization | signed in, no workspace    | Step 4           |\n| `whoami` fails with `profile_selection_required`          | several saved logins       | Several accounts |\n\n`whoami` selects the workspace itself when the customer has exactly one, so an identity that\narrives with an organization needs no workspace step. Without an organization, `next_action`\nmeans the choice would be a guess or no workspace exists yet. With an organization,\n`next_action` can name `github connect`: that workspace has no GitHub connection yet, and Step 6\nhandles it.\n\nIf `OHMYHOST_TOKEN` is set in this process, that token is the credential: the CLI and MCP ignore any\nsaved login. Verify its returned identity, organization and selected platform against the task,\neven if a browser is already signed in. If `whoami` succeeds for that account, go to Step 5 without\nstarting another login. If it fails, ask the customer to update the private credential source,\nnot to paste a replacement value into chat.\nDo not send them to a sign-in link, because `ohmyhost login` refuses to run while the variable is set.\nWith a working token, `profile list` can still answer `credential_store_unavailable` on a host\nwithout a credential store; no repair is needed unless the task names a saved login.\n\nSay nothing about a state that needs nothing from the customer. A ready agent deploys without a\nsingle question. Report a state only in the message that also asks them to act, so they never\nreceive one message about the problem and a second one about the link.\n\n## Several accounts on one computer\n\nEach `ohmyhost login` saves one login: one user in one organization, kept in the operating\nsystem\'s credential store. `ohmyhost profile list --json` (MCP `profile_list`) shows each login\'s\nname, user and organization, never a token. There is no active login for the whole computer: with\none saved login every command uses it; with several, every command names one with\n`--profile-name NAME`, MCP tools take `profile_name`, and `OHMYHOST_PROFILE=NAME` binds a whole\nprocess or MCP server. A command with `--organization` (MCP `organization_id`) uses that\norganization\'s login by itself. A project command can also select it from a checkout link,\nincluding a link for its explicit `--project`; `whoami` and `project list` do not select a login\nfrom checkout links, so name one when several are saved. `ohmyhost init` uses no login and\nrefuses `--profile-name`. Another agent\'s choice never changes which account your command runs as.\n\n- When the prompt names a user and an organization, act only as the saved login with exactly that\n  user and organization, and confirm it with `whoami --profile-name NAME` before any change. These\n  IDs are context, not credentials. Never guess an account and never use another login instead.\n- If no saved login matches, add it and send its link and code as in Step 3:\n  `ohmyhost login --organization ORGANIZATION_ID --user USER_ID --json`. If the browser is\n  signed in as another account, the login saves nothing and answers `login_account_mismatch`:\n  ask the customer to switch the browser to the named account (or use a private window), then\n  repeat the login.\n- When the prompt names only a user ("it has no organization yet"), use the saved login with that\n  user and no organization, confirmed with `whoami --profile-name NAME`. If none exists, add it\n  with `ohmyhost login --user USER_ID --json`, then continue with Step 4.\n- `profile_selection_required` means several logins could run the command: ask the customer which\n  account to use. `profile_not_found` names the login to add, `profile_context_mismatch` means the\n  request contradicts its binding, organization or user, and `environment_token_context_mismatch`\n  means `OHMYHOST_TOKEN` belongs to another account.\n- A saved login never switches organizations. For another workspace, add its own login with\n  `ohmyhost login --organization ORGANIZATION_ID --user USER_ID --json`.\n  `ohmyhost logout --profile-name NAME` removes only that login.\n- `secret_set_command` takes `profile_name` like every tool and returns a command that names the\n  same login with `--profile-name` plus its user and organization (`--profile-user`,\n  `--profile-organization`); an MCP server with `OHMYHOST_TOKEN` names its key\'s user and\n  organization with `--token-user` and `--token-organization` instead. Keep those flags when you\n  run the command, so the secret is written as exactly this account. A login of that name that\n  belongs to another user or organization, for example on another computer, answers\n  `profile_context_mismatch`. The key form runs only where `OHMYHOST_TOKEN` holds a key of that\n  user and organization, never with a saved login: it answers `environment_token_required` without\n  a key and `environment_token_context_mismatch` with another account\'s key. None of these\n  refusals reads the value or sends anything.\n- Tokens stay in the operating system\'s credential store; the list of saved logins (names, users\n  and organizations, never a token) is kept in `~/.ohmyhost/profiles/`, so agents that sign in at\n  the same moment never lose each other\'s login. One environment keeps up to 64 saved logins;\n  beyond that `login` answers `profile_limit_reached` and saves nothing: ask the customer which\n  saved login to remove with `ohmyhost logout --profile-name NAME`.\n- One checkout can be linked for several organizations, one link each. With several links, name\n  the login with `--profile-name`; an older link without organization is used only after the API\n  confirms that the chosen login can see its project (`linked_project_organization_mismatch`\n  otherwise).\n- Errors that depend on the account name it in `acting_as`: `resource_not_found` with another\n  account\'s login means the wrong login, `github_connection_required` means that workspace has no\n  GitHub connection yet, and `repository_not_installed` means its GitHub App installation does not\n  cover the repository.\n\n## Step 2 — install what is missing\n\nRead <https://ohmyho.st/llms.txt> and the [CLI/MCP installation guide](https://docs.ohmyho.st/agents/mcp).\nCompare the installed versions with <https://ohmyho.st/client-release.json>: `ohmyhost --version`\nnames the CLI, and `npm ls --global --depth=0` lists both packages (`ohmyhost-mcp` has no\n`--version` flag; it starts the server). When either is missing or older, install both from the\nsource already in use: the current archive URLs from that guide, or npm\n(`npm install --global @amerged/ohmyhost-cli @amerged/ohmyhost-mcp`). Both provide the same\n`ohmyhost` and `ohmyhost-mcp` commands, so uninstall one pair before switching to the other.\nAn older client lacks commands and rejects newer server responses with `response_contract_invalid`;\nan older MCP server reports the same case as `client_request_failed` although connection and login\nwork. Upgrade both clients and reload MCP before treating either as a platform fault; if both are\ncurrent, report it with `feedback_submit`.\n\nRead [harness setup](references/harness-setup.md) and register the local `ohmyhost-mcp` command with this harness\'s documented settings. Preserve other MCP servers, model choices and permission settings. Use `OHMYHOST_ENVIRONMENT=production` for CLI and MCP unless the customer explicitly selected the development platform.\n\nEvery CLI command and MCP tool is listed in [surfaces](references/surfaces.md); use it to find the exact name of a capability a customer asks for instead of guessing or assuming it is missing.\n\nReload the MCP connection after every install or upgrade, then verify `tools/list` and `resources/list`. A running server keeps the tool list it started with, so a freshly installed version is invisible until it restarts. Repeat Step 1 afterwards.\n\n## Step 3 — the customer signs in once\n\n```sh\nohmyhost login --json\n```\n\nWhen the prompt named a user and organization, add\n`--organization ORGANIZATION_ID --user USER_ID`, so nothing is saved unless the browser signs in\nas exactly that account. Each login is saved under a name derived from its organization;\n`--profile-name NAME` chooses another (lowercase letters, digits, `-` and `_`, starting with a\nletter or digit, at most 63 characters; another name answers `invalid_command`). If that name\nalready belongs to another saved login (`profile_name_conflict`), choose a different name;\nremove the other login only when the customer asks.\n\nStart it as a background process and read its output while it runs: a sign-in link, a confirmation\ncode such as `ABCD-EFGH` and how many minutes both stay valid appear on stderr at once. The\ncommand waits up to 30 minutes for the customer and saves the login only when it ends by itself;\na harness timeout that stops it earlier saves nothing. The sign-in page shows the same code and\nasks the customer to confirm it. Send one message with the full link, code and validity, then\nwait for the customer while leaving the command running.\n\n> I found no valid ohmyho.st login for this account on this computer. Open this link to connect it:\n>\n> [full link exactly as printed]\n>\n> The page shows the code **[code]**. Continue only if it shows exactly this code.\n> Sign in there, or choose **Sign up** on that same page if you do not have an account yet.\n> Link and code are valid for [minutes] minutes; if the page rejects the code, say so and I will send a new one.\n> Tell me when you are done.\n\nRules for this step:\n\n- Always show the code. Every message that carries a sign-in link also carries its code, the first\n  time and after every repeated login. The customer checks it against the page; a code that\n  appears on the page but never in the chat gives them nothing to check.\n- Write the full link on its own line, exactly as the CLI printed it, so the customer sees the\n  address before opening it. Never hide it behind words like "this link" or "sign-in link" and\n  never shorten it; a bare address the chat makes clickable is fine. The customer types nothing.\n- State how long link and code are valid, taking the number from the CLI\'s own message rather than\n  inventing one.\n- Do not ask whether they have an account. The same page serves both, so naming both costs one\n  sentence and saves a round trip.\n- Sign-up is open. There is no invitation, no waitlist and no access code. Never send the customer\n  somewhere else to request access.\n- Wait for the customer. The command completes on its own once they finish; do not start a second\n  login while the first is still open.\n- A confirmation code lives only a few minutes. While `ohmyhost login --json` still runs, it\n  replaces a lapsed code by itself for up to 30 minutes and prints the new link and code: send\n  them the same way. Run the original login command again, keeping its account flags, only\n  after it ended with `device_authorization_expired`. This is expected, not a failure: do not\n  report an error or suggest the customer did something wrong.\n\nWhen the command returns, verify and continue:\n\n```sh\nohmyhost whoami --json\n```\n\n## Step 4 — make sure a workspace is selected\n\n`login` and `whoami` select the workspace themselves when the customer has exactly one, and their\nresponse names the selected organization. They report `next_action` with several choices, and then\nthe customer decides; with no workspace at all, create the first one. `organization use` binds a\nlogin that has no organization yet; a login that already has one keeps it (use a separate login\nfor another workspace, see "Several accounts on one computer").\n\nAlways look before creating. A verified first portal signup creates or reuses **My workspace**,\nincluding a direct signup or one with an invalid referral. The customer may also have a workspace\nfrom an earlier session:\n\n```sh\nohmyhost organization list --json\nohmyhost organization use --organization "$ORGANIZATION_ID" --json\n```\n\nCreate a workspace only when that list is empty, with a name the customer gave you:\n\n```sh\nohmyhost organization create --name "$ORGANIZATION_NAME" --source "$SIGNUP_SOURCE" --idempotency-key "$ORGANIZATION_REQUEST_KEY" --json\nohmyhost whoami --json\n```\n\n- `--source` (MCP `signup_source`) is optional attribution. If the task mentioned a campaign,\n  referral (`https://ohmyho.st/?r=ref-…`) or flag (`https://ohmyho.st/?r=flag-…`) link, pass its\n  single accepted `r` value unchanged (lowercase letters, digits, `-` and `_`, starting with a\n  letter or digit, at most 64 characters); otherwise omit it. The portal treats a malformed\n  value as Direct, so missing or invalid attribution never blocks signup and earns no referral\n  bonus. The server decides any once-per-user benefit: an eligible\n  referral or active flag on the first workspace gives 1,000 credits and 30 days of Paid, and a\n  registered campaign can add credits; promise nothing else. Attribution is never an access\n  code or secret and is fixed per user: later workspaces pass the same Signup source shown on\n  the portal\'s Profile page (omit the flag for Direct); another value answers `forbidden`.\n- Reuse the same name, source and idempotency key after an interrupted response instead of creating a second organization.\n- Creating a workspace selects it immediately for a login that had none; `whoami` or `identity_get` confirms the selection before you create a project. A login already in another workspace keeps it, and the response names the `login` that adds one for the new workspace.\n- Over MCP, `organization_create`, `organization_list` and `organization_use` do the same and report the same `selected` workspace.\n- Creating, listing and selecting a workspace need the interactive login. An API token can do none of them, and says so.\n- Never create another workspace on your own when the customer already has one.\n- A session that selected none lists no projects: `projects_list` and `ohmyhost project list` answer `organization_required` instead of an empty page. Select a workspace, then read the list again.\n\n## Step 5 — keep access for later\n\nThe current CLI login is enough to continue; MCP uses it.\n\n`ohmyhost login` saves each login in the operating system\'s credential store, and MCP reads it\nthere. `credential_store_unavailable` means the CLI cannot use that store. On a desktop, ask the\ncustomer to unlock it, then retry. In a container, CI runner or headless Linux, do not start a\nsign-in that cannot be saved: ask the customer to create a user token at\n<https://app.ohmyho.st/tokens> and load it as `OHMYHOST_TOKEN` from a private env file.\n\nFor automation, use `token_create` with `out_file`, or\n`ohmyhost token create --organization ULID --name NAME --idempotency-key KEY --out .env.local --json`.\nThe client appends `OHMYHOST_TOKEN` once to that private env file, sets mode `600` and returns\nonly metadata; the value is never shown in the client result and cannot be read again. The file\nname must start or end with `.env`, be ignored by Git or lie outside the repository\n(`token_file_not_ignored`), and not already hold `OHMYHOST_TOKEN` (`token_file_has_token`).\nConfigure the process to load it. Preserve existing credentials and never put the value in chat,\nsource or a command argument. If `token_file_changed` names an issued key that could not be saved,\nrevoke that key with `token_revoke` or the returned CLI command before creating a replacement\nwith a new idempotency key; `token_value_unavailable` means use the original file or revoke and\nreplace the key, since replay cannot reveal its value.\n\n`OHMYHOST_TOKEN` overrides the saved logins in any process where it is set. A token alone runs every\ncommand in these Skills except these, which need the interactive login: `login`, `logout` (including\n`logout --revoke`), `organization create|list|use`, and `token create|list|revoke`. Run those in a\nprocess without the variable. Never delete a saved token file. A token belongs to one account and\norganization: a command that names another (`--profile-name`, `--organization`, or a checkout\nlinked for another organization) is refused with `environment_token_context_mismatch` before\nanything is sent.\n\n## Step 6 — continue with the app\n\nConfirm the selected directory and GitHub repository. Read `github_status` for the selected workspace. If it is not connected, an Owner or Admin uses `github_connect` (CLI below), opens its single `authorization_url`, then repeats the same request/key after the browser completes until the returned status is `connected`.\n\n```sh\nohmyhost github status --organization "$ORGANIZATION_ID" --json\nohmyhost github connect --organization "$ORGANIZATION_ID" --idempotency-key "$GITHUB_CONNECT_KEY" --json\n```\n\nThe one link handles the required installation/user authorization. Do not construct a second installation link, replay OAuth callbacks, or ask for an installation ID or provider token. Use the intended GitHub browser profile. A connected installation covers only its selected repositories; if one is missing, open `connection.settings_url` from status, add the repository and repeat its original source-link request/key.\n\nMCP/REST returns these objects directly. CLI JSON wraps the handoff in `authorization` and status\nin `github`: read `authorization.authorization_url` and `github.connection.settings_url`.\nThe handoff lives 30 minutes (`expires_at`). While `pending`, a `last_failure` of\n`provider_unavailable` or `authorization_code_rejected` means reopen the returned\n`authorization_url` with the same key. `failed` or `expired` is final: `account_admin_required`\nneeds the GitHub account owner or organization admin, `installation_access_required` means the\nApp was not installed for that account, `session_inactive` needs a fresh login by a workspace\nOwner or Admin, and `denied` means the customer declined. Resolve the cause, then connect with a\nnew key for the same workspace; never poll a terminal failure.\n\nUse `projects_list` to reuse a project and `project_context_get` when resuming one. Preserve an existing project\'s region. For a new project, an explicit customer region wins; otherwise use a browser-location hint supplied in the customer\'s onboarding prompt and send that region explicitly. Without either, ask once for US or EU. Never infer customer location from the agent/server IP. The API default remains US; the selected region cannot change later.\n\nContinue with the **ohmyhost-deploy-github** Skill when a deployment is requested. Login, workspace creation, GitHub connection and project linking are distinct results; check each returned state rather than treating a completed browser page as deployment success.\n\nSupport runs through this agent. When the customer needs help, reports a bug or asks for a feature, submit a redacted report with `feedback_submit` (CLI `ohmyhost feedback submit`), give the customer the receipt ID and read replies later with `feedback_status`; the **ohmyhost-troubleshoot-deployment** Skill describes a good report. Point the customer to https://ohmyho.st/contact only when they cannot sign in, a billing issue names `contact_support`, or they ask about privacy or the DPA. The customer page is https://docs.ohmyho.st/support.\n',
+    text: '---\nname: ohmyhost-get-started\ndescription: Connect a customer agent to ohmyho.st. Determine what is already installed and signed in, guide the customer through browser sign-in, and select an organization before the first GitHub deployment. Also use when one computer holds several accounts, a prompt names the user and organization to work as, the customer needs support, or an automation needs a non-expiring API token. Use the deployment Skill once access is ready.\n---\n\n# Start with ohmyho.st\n\nConnect this agent to the customer\'s account, then continue with the selected GitHub app.\n\n## What ohmyho.st is and what you can do with it\n\nohmyho.st hosts a customer\'s GitHub app: Vite/React, TanStack Start, Next.js or a plain Worker\nmodule with HTTP handlers and optional cron schedules. Their coding agent operates it through the local\nMCP server or CLI, both calling the same REST API. Deploy a pushed commit to Dev or Prod,\nverify the app, and promote a tested Dev artifact when appropriate. Dev is protected by default;\nthe deployment Skill handles public Dev, data choices and the shared-database promotion rule.\nYou can also give the app Postgres, private runtime secrets, Cloudflare R2 files, optional\ntransactional mail and a custom domain, export its database as an encrypted SQL ZIP, and read\nusage, credits and project budgets. The customer keeps their own application authentication;\nnothing here replaces it. Sign-up is open and free to start.\n\nThe initial connection normally asks the customer to sign in and authorize GitHub for the\nworkspace. A working saved login or API token can avoid another sign-in, and a connected\nworkspace can reuse its GitHub connection. Optional payments, DNS/account consent or harness\nreloads can require further customer action; use the relevant Skill for the feature they chose.\n\nThe whole path, and the proof that each step is done:\n\n| Step | Result                                                        | Proof                                                                                                                         | Section      |\n| ---- | ------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- | ------------ |\n| 1    | You know what is installed and who is signed in               | `ohmyhost --version`, `ohmyhost whoami --json` or MCP `identity_get`, and the MCP tool list                                   | Step 1       |\n| 2    | CLI and MCP are current and registered                        | Installed versions match the published release; the harness\'s MCP `tools/list` exposes the tools after any required reload    | Step 2       |\n| 3    | The intended account is authenticated                         | `ohmyhost whoami --json` or MCP `identity_get` returns the intended user                                                      | Step 3       |\n| 4    | A workspace is selected                                       | The identity returns the intended organization                                                                                | Step 4       |\n| 5    | Access survives this session                                  | The same identity check succeeds from a fresh process with its chosen login or private token source                           | Step 5       |\n| 6    | GitHub is connected and existing projects are known           | MCP `github_status` returns `connected`; `projects_list` identifies a project to reuse                                        | Step 6       |\n| 7    | The repository is linked and the app is deployed and verified | MCP `source_get` confirms the linked repository; the deployment operation succeeds and the selected app URL passes its checks | Deploy Skill |\n\nEach step is a separate result. Confirm it using the Proof column; a completed browser page,\na saved MCP configuration or a started process does not substitute for its returned state.\n\nWhich Skill to read next:\n\n| The customer wants to …                                          | Skill                              |\n| ---------------------------------------------------------------- | ---------------------------------- |\n| prepare or adapt an app so it runs here                          | ohmyhost-build-portable-app        |\n| convert a real Supabase database, Auth, Storage or Functions use | ohmyhost-migrate-supabase-postgres |\n| deploy a commit, verify it, promote Dev to Prod                  | ohmyhost-deploy-github             |\n| understand a queued, stuck or failed deployment, or report a bug | ohmyhost-troubleshoot-deployment   |\n| read or change data, database size or Dev-to-Prod migrations     | ohmyhost-manage-database           |\n| connect a custom domain or mail sender                           | ohmyhost-domains-and-mail          |\n| export the database as an encrypted backup                       | ohmyhost-export-database           |\n| see usage, credits or set a spending limit                       | ohmyhost-usage-and-budgets         |\n\nUsers normally reach this Skill from a prompt such as "connect this agent to ohmyho.st and deploy\nthis project". In that case finish Steps 1 to 6 with as few messages as possible, then continue\nwith the deployment Skill without asking again for anything already decided.\n\n## How to talk to the customer here\n\n- One action per message, in short plain sentences. Give the link, then what they will see.\n- Write in the language the customer writes in. Translate the message templates below; copy no\n  other sentence from this file into the chat.\n- Keep customer-facing messages focused on the action and why it is needed. Avoid narrating\n  routine internal steps; explain an actual limitation when it prevents the requested work.\n- Wait for required browser input before taking actions that depend on it. Independent repository\n  inspection can continue while the customer signs in; do not start another sign-in for the same\n  account or repeat the instruction without new information. Respect the customer\'s existing authorization and scope.\n- Never ask for a password, an email code or a token value. Never paste a credential into chat,\n  source or a command argument.\n- After they report back, verify with a command instead of trusting the report.\n\n## Step 1 — determine the state before doing anything\n\nIf the customer\'s prompt names an account ("Use my ohmyho.st account user … in organization …"),\nread "Several accounts on one computer" first. Use that login\'s `--profile-name` on authenticated\nchecks when needed. Then run these checks:\n\n```sh\nohmyhost --version\nohmyhost whoami --json\nohmyhost profile list --json\n```\n\nAlso list the MCP tools of the `ohmyho` server. A saved configuration alone is not a working connection.\n\nRead the result:\n\n| Observation                                               | State                      | Continue with    |\n| --------------------------------------------------------- | -------------------------- | ---------------- |\n| `ohmyhost` missing, or the MCP server exposes no tools    | not installed              | Step 2           |\n| `--version` is older than the published release           | outdated                   | Step 2           |\n| CLI runs, `whoami` fails with `authentication_required`   | installed, signed out      | Step 3           |\n| `whoami` fails with `credential_store_unavailable`        | no usable credential store | Step 5           |\n| `whoami` returns an identity with an organization         | ready                      | Step 5           |\n| `whoami` returns `next_action` instead of an organization | signed in, no workspace    | Step 4           |\n| `whoami` fails with `profile_selection_required`          | several saved logins       | Several accounts |\n\n`whoami` selects the workspace itself when the customer has exactly one, so an identity that\narrives with an organization needs no workspace step. Without an organization, `next_action`\nmeans the choice would be a guess or no workspace exists yet. With an organization,\n`next_action` can name `github connect`: that workspace has no GitHub connection yet, and Step 6\nhandles it.\n\nIf `OHMYHOST_TOKEN` is set in this process, that token is the credential: the CLI and MCP ignore any\nsaved login. Verify its returned identity, organization and selected platform against the task,\neven if a browser is already signed in. If `whoami` succeeds for that account, go to Step 5 without\nstarting another login. If it fails, ask the customer to update the private credential source,\nnot to paste a replacement value into chat.\nDo not send them to a sign-in link, because `ohmyhost login` refuses to run while the variable is set.\nWith a working token, `profile list` can still answer `credential_store_unavailable` on a host\nwithout a credential store; no repair is needed unless the task names a saved login.\n\nSay nothing about a state that needs nothing from the customer. A ready agent deploys without a\nsingle question. Report a state only in the message that also asks them to act, so they never\nreceive one message about the problem and a second one about the link.\n\n## Several accounts on one computer\n\nEach `ohmyhost login` saves one login: one user in one organization, kept in the operating\nsystem\'s credential store. `ohmyhost profile list --json` (MCP `profile_list`) shows each login\'s\nname, user and organization, never a token. There is no active login for the whole computer: with\none saved login every command uses it; with several, every command names one with\n`--profile-name NAME`, MCP tools take `profile_name`, and `OHMYHOST_PROFILE=NAME` binds a whole\nprocess or MCP server. A command with `--organization` (MCP `organization_id`) uses that\norganization\'s login by itself. A project command can also select it from a checkout link,\nincluding a link for its explicit `--project`; `whoami` and `project list` do not select a login\nfrom checkout links, so name one when several are saved. `ohmyhost init` uses no login and\nrefuses `--profile-name`. Another agent\'s choice never changes which account your command runs as.\n\n- When the prompt names a user and an organization, act only as the saved login with exactly that\n  user and organization, and confirm it with `whoami --profile-name NAME` before any change. These\n  IDs are context, not credentials. Never guess an account and never use another login instead.\n- If no saved login matches, add it and send its link and code as in Step 3:\n  `ohmyhost login --organization ORGANIZATION_ID --user USER_ID --json`. If the browser is\n  signed in as another account, the login saves nothing and answers `login_account_mismatch`:\n  ask the customer to switch the browser to the named account (or use a private window), then\n  repeat the login.\n- When the prompt names only a user ("it has no organization yet"), use the saved login with that\n  user and no organization, confirmed with `whoami --profile-name NAME`. If none exists, add it\n  with `ohmyhost login --user USER_ID --json`, then continue with Step 4.\n- `profile_selection_required` means several logins could run the command: ask the customer which\n  account to use. `profile_not_found` names the login to add, `profile_context_mismatch` means the\n  request contradicts its binding, organization or user, and `environment_token_context_mismatch`\n  means `OHMYHOST_TOKEN` belongs to another account.\n- A saved login never switches organizations. For another workspace, add its own login with\n  `ohmyhost login --organization ORGANIZATION_ID --user USER_ID --json`.\n  `ohmyhost logout --profile-name NAME` removes only that login.\n- `secret_set_command` takes `profile_name` like every tool and returns a command that names the\n  same login with `--profile-name` plus its user and organization (`--profile-user`,\n  `--profile-organization`); an MCP server with `OHMYHOST_TOKEN` names its key\'s user and\n  organization with `--token-user` and `--token-organization` instead. Keep those flags when you\n  run the command, so the secret is written as exactly this account. A login of that name that\n  belongs to another user or organization, for example on another computer, answers\n  `profile_context_mismatch`. The key form runs only where `OHMYHOST_TOKEN` holds a key of that\n  user and organization, never with a saved login: it answers `environment_token_required` without\n  a key and `environment_token_context_mismatch` with another account\'s key. None of these\n  refusals reads the value or sends anything.\n- Tokens stay in the operating system\'s credential store; the list of saved logins (names, users\n  and organizations, never a token) is kept in `~/.ohmyhost/profiles/`, so agents that sign in at\n  the same moment never lose each other\'s login. One environment keeps up to 64 saved logins;\n  beyond that `login` answers `profile_limit_reached` and saves nothing: ask the customer which\n  saved login to remove with `ohmyhost logout --profile-name NAME`.\n- One checkout can be linked for several organizations, one link each. With several links, name\n  the login with `--profile-name`; an older link without organization is used only after the API\n  confirms that the chosen login can see its project (`linked_project_organization_mismatch`\n  otherwise).\n- Errors that depend on the account name it in `acting_as`: `resource_not_found` with another\n  account\'s login means the wrong login, `github_connection_required` means that workspace has no\n  GitHub connection yet, and `repository_not_installed` means its GitHub App installation does not\n  cover the repository.\n\n## Step 2 — install what is missing\n\nRead <https://ohmyho.st/llms.txt> and the [CLI/MCP installation guide](https://docs.ohmyho.st/agents/mcp).\nCompare the installed versions with <https://ohmyho.st/client-release.json>: `ohmyhost --version`\nnames the CLI, and `npm ls --global --depth=0` lists both packages (`ohmyhost-mcp` has no\n`--version` flag; it starts the server). When either is missing or older, install both from the\nsource already in use: the current archive URLs from that guide, or npm\n(`npm install --global @amerged/ohmyhost-cli @amerged/ohmyhost-mcp`). Both provide the same\n`ohmyhost` and `ohmyhost-mcp` commands, so uninstall one pair before switching to the other.\nAn older client lacks commands and rejects newer server responses with `response_contract_invalid`;\nan older MCP server reports the same case as `client_request_failed` although connection and login\nwork. Upgrade both clients and reload MCP before treating either as a platform fault; if both are\ncurrent, report it with `feedback_submit`.\n\nRead [harness setup](references/harness-setup.md) and register the local `ohmyhost-mcp` command with this harness\'s documented settings. Preserve other MCP servers, model choices and permission settings. Use `OHMYHOST_ENVIRONMENT=production` for CLI and MCP unless the customer explicitly selected the development platform.\n\nEvery CLI command and MCP tool is listed in [surfaces](references/surfaces.md); use it to find the exact name of a capability a customer asks for instead of guessing or assuming it is missing.\n\nReload the MCP connection after every install or upgrade, then verify `tools/list` and `resources/list`. A running server keeps the tool list it started with, so a freshly installed version is invisible until it restarts. Repeat Step 1 afterwards.\n\n## Step 3 — the customer signs in once\n\n```sh\nohmyhost login --json\n```\n\nWhen the prompt named a user and organization, add\n`--organization ORGANIZATION_ID --user USER_ID`, so nothing is saved unless the browser signs in\nas exactly that account. Each login is saved under a name derived from its organization;\n`--profile-name NAME` chooses another (lowercase letters, digits, `-` and `_`, starting with a\nletter or digit, at most 63 characters; another name answers `invalid_command`). If that name\nalready belongs to another saved login (`profile_name_conflict`), choose a different name;\nremove the other login only when the customer asks.\n\nStart it as a background process and read its output while it runs: a sign-in link, a confirmation\ncode such as `ABCD-EFGH` and how many minutes both stay valid appear on stderr at once. The\ncommand waits up to 30 minutes for the customer and saves the login only when it ends by itself;\na harness timeout that stops it earlier saves nothing. The sign-in page shows the same code and\nasks the customer to confirm it. Send one message with the full link, code and validity, then\nwait for the customer while leaving the command running.\n\n> I found no valid ohmyho.st login for this account on this computer. Open this link to connect it:\n>\n> [full link exactly as printed]\n>\n> The page shows the code **[code]**. Continue only if it shows exactly this code.\n> Sign in there, or choose **Sign up** on that same page if you do not have an account yet.\n> Link and code are valid for [minutes] minutes; if the page rejects the code, say so and I will send a new one.\n> Tell me when you are done.\n\nRules for this step:\n\n- Always show the code. Every message that carries a sign-in link also carries its code, the first\n  time and after every repeated login. The customer checks it against the page; a code that\n  appears on the page but never in the chat gives them nothing to check.\n- Write the full link on its own line, exactly as the CLI printed it, so the customer sees the\n  address before opening it. Never hide it behind words like "this link" or "sign-in link" and\n  never shorten it; a bare address the chat makes clickable is fine. The customer types nothing.\n- State how long link and code are valid, taking the number from the CLI\'s own message rather than\n  inventing one.\n- Do not ask whether they have an account. The same page serves both, so naming both costs one\n  sentence and saves a round trip.\n- Sign-up is open. There is no invitation, no waitlist and no access code. Never send the customer\n  somewhere else to request access.\n- Wait for the customer. The command completes on its own once they finish; do not start a second\n  login while the first is still open.\n- A confirmation code lives only a few minutes. While `ohmyhost login --json` still runs, it\n  replaces a lapsed code by itself for up to 30 minutes and prints the new link and code: send\n  them the same way. Run the original login command again, keeping its account flags, only\n  after it ended with `device_authorization_expired`. This is expected, not a failure: do not\n  report an error or suggest the customer did something wrong.\n\nWhen the command returns, verify and continue:\n\n```sh\nohmyhost whoami --json\n```\n\n## Step 4 — make sure a workspace is selected\n\n`login` and `whoami` select the workspace themselves when the customer has exactly one, and their\nresponse names the selected organization. They report `next_action` with several choices, and then\nthe customer decides; with no workspace at all, create the first one. `organization use` binds a\nlogin that has no organization yet; a login that already has one keeps it (use a separate login\nfor another workspace, see "Several accounts on one computer").\n\nAlways look before creating. A verified first portal signup creates or reuses **My workspace**,\nincluding a direct signup or one with an invalid referral. The customer may also have a workspace\nfrom an earlier session:\n\n```sh\nohmyhost organization list --json\nohmyhost organization use --organization "$ORGANIZATION_ID" --json\n```\n\nCreate a workspace only when that list is empty, with a name the customer gave you:\n\n```sh\nohmyhost organization create --name "$ORGANIZATION_NAME" --source "$SIGNUP_SOURCE" --idempotency-key "$ORGANIZATION_REQUEST_KEY" --json\nohmyhost whoami --json\n```\n\n- `--source` (MCP `signup_source`) is optional attribution. If the task mentioned a campaign,\n  referral (`https://ohmyho.st/?r=ref-…`) or flag (`https://ohmyho.st/?r=flag-…`) link, pass its\n  single accepted `r` value unchanged (lowercase letters, digits, `-` and `_`, starting with a\n  letter or digit, at most 64 characters); otherwise omit it. The portal treats a malformed\n  value as Direct, so missing or invalid attribution never blocks signup and earns no referral\n  bonus. The server decides any once-per-user benefit: an eligible\n  referral or active flag on the first workspace gives 1,000 credits and 30 days of Paid, and a\n  registered campaign can add credits; promise nothing else. Attribution is never an access\n  code or secret and is fixed per user: later workspaces pass the same Signup source shown on\n  the portal\'s Profile page (omit the flag for Direct); another value answers `forbidden`.\n- Reuse the same name, source and idempotency key after an interrupted response instead of creating a second organization.\n- Creating a workspace selects it immediately for a login that had none; `whoami` or `identity_get` confirms the selection before you create a project. A login already in another workspace keeps it, and the response names the `login` that adds one for the new workspace.\n- Over MCP, `organization_create`, `organization_list` and `organization_use` do the same and report the same `selected` workspace.\n- Creating, listing and selecting a workspace need the interactive login. An API token can do none of them, and says so.\n- Never create another workspace on your own when the customer already has one.\n- A session that selected none lists no projects: `projects_list` and `ohmyhost project list` answer `organization_required` instead of an empty page. Select a workspace, then read the list again.\n\n## Step 5 — keep access for later\n\nThe current CLI login is enough to continue; MCP uses it.\n\n`ohmyhost login` saves each login in the operating system\'s credential store, and MCP reads it\nthere. `credential_store_unavailable` means the CLI cannot use that store. On a desktop, ask the\ncustomer to unlock it, then retry. In a container, CI runner or headless Linux, do not start a\nsign-in that cannot be saved: ask the customer to create a user token at\n<https://app.ohmyho.st/tokens> and load it as `OHMYHOST_TOKEN` from a private env file.\n\nFor automation, use `token_create` with `out_file`, or\n`ohmyhost token create --organization ULID --name NAME --idempotency-key KEY --out .env.local --json`.\nThe client appends `OHMYHOST_TOKEN` once to that private env file, sets mode `600` and returns\nonly metadata; the value is never shown in the client result and cannot be read again. The file\nname must start or end with `.env`, be ignored by Git or lie outside the repository\n(`token_file_not_ignored`), and not already hold `OHMYHOST_TOKEN` (`token_file_has_token`).\nConfigure the process to load it. Preserve existing credentials and never put the value in chat,\nsource or a command argument. If `token_file_changed` names an issued key that could not be saved,\nrevoke that key with `token_revoke` or the returned CLI command before creating a replacement\nwith a new idempotency key; `token_value_unavailable` means use the original file or revoke and\nreplace the key, since replay cannot reveal its value.\n\n`OHMYHOST_TOKEN` overrides the saved logins in any process where it is set. A token alone runs every\ncommand in these Skills except these, which need the interactive login: `login`, `logout` (including\n`logout --revoke`), `organization create|list|use`, and `token create|list|revoke`. Run those in a\nprocess without the variable. Never delete a saved token file. A token belongs to one account and\norganization: a command that names another (`--profile-name`, `--organization`, or a checkout\nlinked for another organization) is refused with `environment_token_context_mismatch` before\nanything is sent.\n\n## Step 6 — continue with the app\n\nConfirm the selected directory and GitHub repository. Read `github_status` for the selected workspace. If it is not connected, an Owner or Admin uses `github_connect` (CLI below), opens its single `authorization_url`, then repeats the same request/key after the browser completes until the returned status is `connected`.\n\n```sh\nohmyhost github status --organization "$ORGANIZATION_ID" --json\nohmyhost github connect --organization "$ORGANIZATION_ID" --idempotency-key "$GITHUB_CONNECT_KEY" --json\n```\n\nThe one link handles the required installation/user authorization. Do not construct a second installation link, replay OAuth callbacks, or ask for an installation ID or provider token. Use the intended GitHub browser profile. A connected installation covers only its selected repositories; if one is missing, open `connection.settings_url` from status, add the repository and repeat its original source-link request/key.\n\nMCP/REST returns these objects directly. CLI JSON wraps the handoff in `authorization` and status\nin `github`: read `authorization.authorization_url` and `github.connection.settings_url`.\nThe handoff lives 30 minutes (`expires_at`). While `pending`, a `last_failure` of\n`provider_unavailable` or `authorization_code_rejected` means reopen the returned\n`authorization_url` with the same key. `failed` or `expired` is final: `account_admin_required`\nneeds the GitHub account owner or organization admin, `installation_access_required` means the\nApp was not installed for that account, `session_inactive` needs a fresh login by a workspace\nOwner or Admin, and `denied` means the customer declined. Resolve the cause, then connect with a\nnew key for the same workspace; never poll a terminal failure.\n\nUse `projects_list` to reuse a project and `project_context_get` when resuming one. Preserve an existing project\'s region. For a new project, an explicit customer region wins; otherwise use a browser-location hint supplied in the customer\'s onboarding prompt and send that region explicitly. Without either, ask once for US or EU. Never infer customer location from the agent/server IP. The API default remains US; the selected region cannot change later.\n\nContinue with the **ohmyhost-deploy-github** Skill when a deployment is requested. Login, workspace creation, GitHub connection and project linking are distinct results; check each returned state rather than treating a completed browser page as deployment success.\n\nFor a repository containing several apps, run local `init` from its Git root and check that the\nrepository-root `ohmyhost.yaml` selects the intended `applicationRoot` before planning the pushed\ncommit. For example, `applicationRoot: apps/web` selects that app\'s sources and migrations;\nan `ohmyhost.yaml` inside `apps/web` does not override the repository\'s selection. Compare the\nlocal result with the plan\'s `application_root` and keep any admission diagnostic visible.\n\nSupport runs through this agent. When the customer needs help, reports a bug or asks for a feature, submit a redacted report with `feedback_submit` (CLI `ohmyhost feedback submit`), give the customer the receipt ID and read replies later with `feedback_status`; the **ohmyhost-troubleshoot-deployment** Skill describes a good report. Point the customer to https://ohmyho.st/contact only when they cannot sign in, a billing issue names `contact_support`, or they ask about privacy or the DPA. The customer page is https://docs.ohmyho.st/support.\n',
   },
   {
     skillName: "ohmyhost-get-started",

package/src/packages/sdk-ts/package.json CHANGED Viewed

@@ -1,6 +1,6 @@
 {
   "name": "@ohmyhost/sdk-ts",
-  "version": "0.1.25",
+  "version": "0.1.26",
   "private": true,
   "type": "module",
   "exports": {