@qingflow-tech/qingflow-cli 1.1.43-beta.2 → 1.1.43-beta.4

package/skills/qingflow-mcp-setup/references/environments.md

@@ -1,62 +0,0 @@
-# Environment Switching
-
-Use this reference before any setup, authentication, or live validation flow.
-
-## Step 1: Resolve the active environment
-
-Decide explicitly whether the user is targeting:
-
-- `test`: for smoke tests, trial setup, DSL validation, mock data, and integration debugging
-- `prod`: for real business usage in the formal environment
-
-If the user did not specify an environment, default to `prod`.
-
-## Test Environment
-
-Default characteristics:
-
-- preferred for first-time setup and local MCP validation
-- mock or smoke data is acceptable when the user asks for it
-- use read/write verification freely inside the intended test workspace
-
-Known values in the current workspace:
-
-- use an explicitly provided non-production backend
-- common test workspace example: `ws_id=2`
-- `qf_version`: usually unset unless the user explicitly needs a routed version
-
-Setup behavior:
-
-- prefer this environment for Claude Desktop or local MCP client onboarding
-- for Wingent Momo runtime, use the injected session and skip auth/workspace preflight
-- for standalone MCP client setup, use `auth_use_credential` or `auth_login`, then `workspace_list`, then `workspace_select`
-- if the user asks to verify installation, a real read-only smoke path is acceptable
-
-## Production Environment
-
-Production is the default environment when the user does not specify one. If the user explicitly says `test`, switch to the dedicated non-production backend they provide.
-
-Expected behavior:
-
-- default `base_url`: `https://qingflow.com/api`
-- confirm the production `qf_version` explicitly when browser traffic depends on routed versions such as `canary`
-- confirm the exact workspace before any live validation
-- prefer read-only checks first
-- avoid mock data, smoke writes, or destructive tests unless the user explicitly asks for them
-
-Production guardrails:
-
-- do not store credentials in skill files or examples
-- do not assume the same workspace ids as test
-- treat startup verification and auth verification as separate steps
-- when sharing snippets, label them as `prod` and `test` clearly
-- when MCP and browser results diverge, compare `request_route` with the browser route before blaming the query logic
-
-## Reporting Rule
-
-When you give setup instructions, always state:
-
-- active environment
-- selected `base_url`
-- selected `qf_version` when relevant
-- whether the next step is read-only or write-impacting

package/skills/qingflow-mcp-setup/references/generic-stdio.md

@@ -1,32 +0,0 @@
-# Generic Stdio MCP Clients
-
-Use this for any local AI client that supports MCP over stdio.
-
-## Required mapping
-
-- `command`: `<ABSOLUTE_PATH_TO_REPO>/qingflow-support/mcp-server/qingflow-mcp`
-- `args`: `[]`
-- `env.QINGFLOW_MCP_DEFAULT_BASE_URL`: backend base URL for the active environment
-
-Environment examples:
-
-- `prod` (default): `https://qingflow.com/api`
-- `test`: use the explicitly provided non-production backend
-
-Keep separate client entries or separate config snippets for `test` and `prod`.
-
-## Validation sequence
-
-1. Start the client
-2. Confirm the `qingflow` MCP server is visible
-3. In Wingent Momo runtime, skip auth/workspace preflight and run a read-only tool such as `app_list`
-4. In a standalone client without injected credentials, run `auth_use_credential` or `auth_login`
-5. Then run `workspace_list`
-6. Then run `workspace_select`
-7. Run a read-only tool such as `app_list`
-
-## Common failures
-
-- Launch failure: bad `command` path or missing `.venv`
-- Auth failure: invalid or expired credential/token
-- Business tool failure before setup: workspace not selected

package/skills/qingflow-mcp-setup/scripts/check_local_server.sh

@@ -1,38 +0,0 @@
-#!/usr/bin/env bash
-set -euo pipefail
-
-SCRIPT_DIR="$(cd "$(dirname "$0")" && pwd)"
-ROOT="${QINGFLOW_MCP_ROOT:-}"
-
-if [[ -z "$ROOT" ]]; then
-  if git_root="$(git rev-parse --show-toplevel 2>/dev/null)" && [[ -d "$git_root/qingflow-support/mcp-server" ]]; then
-    ROOT="$git_root/qingflow-support/mcp-server"
-  elif [[ -d "$PWD/qingflow-support/mcp-server" ]]; then
-    ROOT="$PWD/qingflow-support/mcp-server"
-  else
-    repo_root="$(cd "$SCRIPT_DIR/../../../.." && pwd)"
-    if [[ -d "$repo_root/qingflow-support/mcp-server" ]]; then
-      ROOT="$repo_root/qingflow-support/mcp-server"
-    fi
-  fi
-fi
-
-if [[ -z "$ROOT" ]]; then
-  echo "Unable to locate qingflow-support/mcp-server. Set QINGFLOW_MCP_ROOT to the repo copy of the MCP server." >&2
-  exit 1
-fi
-
-ENTRY="$ROOT/qingflow-mcp"
-PY="$ROOT/.venv/bin/python"
-
-echo "ROOT=$ROOT"
-test -d "$ROOT"
-echo "OK root exists"
-
-test -x "$ENTRY"
-echo "OK entrypoint exists and is executable"
-
-test -x "$PY"
-echo "OK virtualenv python exists"
-
-PYTHONPATH="$ROOT/src" "$PY" -c "import qingflow_mcp.server; print('OK import qingflow_mcp.server')"