testeiya 0.4.4 → 0.4.5

package/dist/prompt/testomatio.js

@@ -1,264 +0,0 @@
-import dedent from "dedent";
-const MAX_PROMPT_LABELS = 20;
-const MAX_PROMPT_TAGS = 30;
-const MAX_PROMPT_ENVS = 15;
-const tmsViaDirectTools = dedent `
-  # Testomat.io-first operating rules (highest priority)
-
-  This agent works on Testomat.io projects. You have TWO sources of truth and they answer different kinds of questions:
-
-  1. **The pulled markdown workspace (\`cwd\`)** — for **tests** and **suites**. Each project's tests and suite structure are already pulled as markdown files into the working directory (one directory per project slug). This is the canonical source for test content, suite hierarchy, test bodies, tags, gherkin scenarios, file layout. Use \`read\`, \`find\`, \`grep\`, \`ls\` — they're instant and don't hit the network.
-  2. **MCP tools under \`testomatio-<slug>\`** — for **dynamic Testomat.io data**: runs, testruns, plans, labels, linked issues, ims config, ci config, analytics. These things don't live as files and MUST come from MCP.
-
-  **Prefer the filesystem for test/suite queries.** Only fall back to \`testomatio-*_tests_list\` / \`testomatio-*_suites_list\` if the user's question genuinely needs cross-tree metadata (e.g. priority, labels, status) that isn't in the markdown, or if the workspace looks stale. Reading test files is faster, cheaper, and gives you the actual code/gherkin.
-
-  **Never** ask the user for the **Testomat.io** API token — it's configured. (This does NOT cover secrets the *app under test* needs to run — its own env vars/tokens. If a test run is blocked by one of those, ask for it.)
-
-  **Statuses and counts are live** — runs change them at any time. Fresh query results supersede numbers from earlier in the conversation; when they differ, the data changed — report the new snapshot.
-
-  ## Banned moves
-
-  - Do NOT call an MCP \`*_tests_list\` or \`*_suites_list\` as your first action for a test/suite question — **read the filesystem first** (\`find\`, \`ls\`, \`grep\`, \`read\`). Fall back to MCP only if the metadata you need isn't in the markdown.
-  - Do NOT ask the user for the **Testomat.io** API token — it's already configured. (Secrets the app under test needs to run are a different thing — ask for those if a run is blocked.)
-  - Do NOT call \`bash\` / \`find\` / \`grep\` to answer questions about **runs, testruns, plans, labels, linked issues, analytics** — those don't exist as files. Use MCP.
-
-  ## Filesystem vs. MCP cheat sheet
-
-  | Question is about… | First action |
-  |---|---|
-  | Test content (code, steps, gherkin, description, file path, tags) | \`read\` / \`find\` / \`grep\` in \`cwd\` |
-  | Suite hierarchy / structure / which files exist | \`ls\` / \`find\` |
-  | Individual test metadata (priority, status flag, labels) | try filesystem; if missing, \`testomatio-*_tests_get\` |
-  | Runs, testruns, plans, labels, issues, analytics | MCP \`testomatio-*\` tools |
-  | Creating/updating tests or suites | edit the markdown file, then \`npx check-tests push\` |
-  | Creating/updating runs, linking issues | MCP create/update tools |
-  | Launching automated or mixed Run remotely on CI | Use npx -y @testomatio/reporter@latest run --remote <profile>, raise error if no CI profiles configured
-  | Running automated Run | Use local test runner with testomatio reporter attached to report to current project
-
-  ---
-`;
-const tmsViaProxy = dedent `
-  # Testomat.io-first operating rules (highest priority)
-
-  This agent works on a Testomat.io project. You have TWO sources of truth and they answer different kinds of questions:
-
-  1. **The pulled markdown workspace (\`cwd\`)** — for **tests** and **suites**. Test content, suite hierarchy, bodies, tags and gherkin scenarios are files. Use \`read\`, \`find\`, \`grep\`, \`ls\` — they are instant and hit no network.
-  2. **The \`mcp\` tool** — for **dynamic Testomat.io data**: runs, testruns, plans, labels, linked issues, ims config, ci config, analytics. These do not live as files and MUST come from there.
-
-  Testomat.io is reached through **one \`mcp\` tool**, not a tool per operation. Call \`mcp({ search: "<what you need>" })\` to find the right operation, then \`mcp({ tool: "<name>", ... })\` to run it. The handful of reads used most often are also registered as their own tools — use those directly when they fit.
-
-  **Prefer the filesystem for test/suite queries.** Reach for a listing only when the question needs cross-tree metadata (priority, labels, status) the markdown does not carry, or when the workspace looks stale.
-
-  **Never** ask the user for the **Testomat.io** API token — it's configured. (This does NOT cover secrets the *app under test* needs to run — its own env vars/tokens. If a test run is blocked by one of those, report it.)
-
-  **Statuses and counts are live** — runs change them at any time. Fresh query results supersede numbers from earlier in the conversation; when they differ, the data changed — report the new snapshot.
-
-  ## Banned moves
-
-  - Do NOT search for an operation as your first action for a test/suite question — **read the filesystem first** (\`find\`, \`ls\`, \`grep\`, \`read\`). Fall back to a listing only if the metadata you need isn't in the markdown.
-  - Do NOT ask the user for the **Testomat.io** API token — it's already configured. (Secrets the app under test needs to run are a different thing — report those if a run is blocked.)
-  - Do NOT call \`bash\` / \`find\` / \`grep\` to answer questions about **runs, testruns, plans, labels, linked issues, analytics** — those don't exist as files.
-
-  ## Filesystem vs. Testomat.io cheat sheet
-
-  | Question is about… | First action |
-  |---|---|
-  | Test content (code, steps, gherkin, description, file path, tags) | \`read\` / \`find\` / \`grep\` in \`cwd\` |
-  | Suite hierarchy / structure / which files exist | \`ls\` / \`find\` |
-  | Individual test metadata (priority, status flag, labels) | try filesystem; if missing, \`mcp({ search: "get test" })\` |
-  | Runs, testruns, plans, labels, issues, analytics | \`mcp({ search: … })\`, then \`mcp({ tool: … })\` |
-  | Creating/updating tests or suites | edit the markdown file, then \`npx check-tests push\` |
-  | Creating/updating runs, linking issues | the matching \`mcp\` create/update operation |
-  | Launching automated or mixed Run remotely on CI | Use npx -y @testomatio/reporter@latest run --remote <profile>, raise error if no CI profiles configured |
-  | Running automated Run | Use local test runner with testomatio reporter attached to report to current project |
-
-  ---
-`;
-const tmsViaCli = dedent `
-  # Testomat.io-first operating rules (highest priority)
-
-  This agent works on a Testomat.io project through the **shell only** — there are no Testomat.io tools in this session.
-
-  1. **The pulled markdown workspace (\`cwd\`)** — the canonical source for **tests** and **suites**: content, hierarchy, bodies, tags, gherkin scenarios. Use \`read\`, \`find\`, \`grep\`, \`ls\`.
-  2. **\`npx check-tests\`** — moves test cases between the markdown and Testomat.io (\`pull\`, \`push\`). It reads its credentials from the environment.
-  3. **The REST API through \`bash\`** — for dynamic data (runs, testruns, plans, labels, linked issues, analytics): \`curl -H "Authorization: $TESTOMATIO" "$TESTOMATIO_URL/api/v2/..."\`.
-
-  **Never** ask the user for the **Testomat.io** API token — it's configured as \`TESTOMATIO\`. (This does NOT cover secrets the *app under test* needs to run — its own env vars/tokens. If a test run is blocked by one of those, report it.)
-
-  **Statuses and counts are live** — runs change them at any time. Fresh query results supersede numbers from earlier in the conversation.
-
-  ## Banned moves
-
-  - Do NOT shell out for test content that is already a file in \`cwd\` — read the file.
-  - Do NOT invent REST paths or parameters. Read the workspace first; when a call is genuinely needed, keep to documented \`/api/v2\` endpoints.
-  - Do NOT ask the user for the **Testomat.io** API token.
-
-  ## Filesystem vs. shell cheat sheet
-
-  | Question is about… | First action |
-  |---|---|
-  | Test content (code, steps, gherkin, description, file path, tags) | \`read\` / \`find\` / \`grep\` in \`cwd\` |
-  | Suite hierarchy / structure / which files exist | \`ls\` / \`find\` |
-  | Runs, testruns, plans, labels, issues, analytics | \`curl\` against \`/api/v2\` |
-  | Creating/updating tests or suites | edit the markdown file, then \`npx check-tests push\` |
-  | Launching automated or mixed Run remotely on CI | Use npx -y @testomatio/reporter@latest run --remote <profile>, raise error if no CI profiles configured |
-  | Running automated Run | Use local test runner with testomatio reporter attached to report to current project |
-
-  ---
-`;
-/**
- * How the agent reaches Testomat.io in this session. The rules are the same;
- * the way to act on them is not, so the harness picks the matching wording.
- */
-export function testomatioTms(access) {
-    if (access === "mcp-proxy")
-        return tmsViaProxy;
-    if (access === "cli-only")
-        return tmsViaCli;
-    return tmsViaDirectTools;
-}
-export function testomatioConnection(tokenSlugs, backendUrl, connection, access = "mcp-direct") {
-    let urlSuffix = "";
-    if (backendUrl)
-        urlSuffix = ` (\`${backendUrl}\`)`;
-    if (tokenSlugs.length === 0) {
-        let project = "";
-        if (connection?.projectId)
-            project = ` \`${connection.projectId}\``;
-        if (connection?.title)
-            project += ` ("${connection.title}")`;
-        return dedent `
-      ## Testomat.io Connection (pre-configured)
-
-      This workspace is linked to the Testomat.io project${project}.
-
-      The project API key is **already set** as \`TESTOMATIO\` in the environment of every \`bash\` command you run, along with \`TESTOMATIO_URL\`${urlSuffix}. **Never ask the user for a Testomat.io token or API key** — it is already in scope.
-
-      Push or pull manual test cases with \`npx check-tests\` (or other \`npx @testomatio/*\` commands) — they pick the credentials up from the environment. ${envTokenActions(access)}
-
-    `;
-    }
-    if (tokenSlugs.length > 1) {
-        const projects = tokenSlugs.map((s) => `- ${s}`).join("\n");
-        return dedent `
-      ## Testomat.io Connection (pre-configured)
-
-      This session spans several Testomat.io projects, so no single \`TESTOMATIO\` env var is exported — only \`TESTOMATIO_URL\`${urlSuffix}. Each project's **MCP server** carries its own credentials (tool prefix: \`testomatio-<slug>\`) — use those for structured actions. **Never ask the user for a Testomat.io token or API key.** Do not guess tokens for \`check-tests\`; use the app's Sync (Pull/Push in the Workspace panel) to move test cases.
-
-      Projects pulled into this working directory (one dir per project):
-      ${projects}
-
-    `;
-    }
-    const projects = tokenSlugs.map((s) => `- ${s}`).join("\n");
-    return dedent `
-    ## Testomat.io Connection (pre-configured)
-
-    The Testomat.io API key is **already set** in the environment as \`TESTOMATIO\`, and the backend URL is set as \`TESTOMATIO_URL\`${urlSuffix}.
-
-    **Do not ask the user for a Testomat.io token** — it is available to every \`bash\` command you run as the \`TESTOMATIO\` env var.
-
-    Projects pulled into this working directory (one dir per project):
-    ${projects}
-
-    ${perProjectActions(access)}
-
-    When you need to push changes back, run \`npx check-tests push\` (or similar \`npx @testomatio/*\` commands) directly — credentials are already in scope.
-
-  `;
-}
-export function testomatioNotConnected() {
-    return dedent `
-    ## Testomat.io Connection (not connected)
-
-    This workspace is not linked to a Testomat.io project and no API key is available in the environment.
-
-    **Never ask the user to paste a Testomat.io API key or token into the chat.** If a task needs Testomat.io access (pulling or pushing test cases, runs, analytics), tell the user to connect the project first — open **Settings → Testomat.io connection** and link this workspace — then continue once connected. Parts of the task that only touch local files can proceed right away.
-  `;
-}
-/**
- * Compact project-settings block for the system prompt, built from the cached
- * `GET /api/v2/{id}/info` payload (`.testeiya/project-info.json`). Only present
- * fields are rendered; labels/tags are capped with a pointer to the full file.
- */
-export function projectSettings(info) {
-    let heading = `**${info.title}** (\`${info.project_id}\`)`;
-    if (info.subscription)
-        heading += ` — ${info.subscription} plan`;
-    const lines = [];
-    const stack = [];
-    if (info.framework)
-        stack.push(`framework: ${info.framework}`);
-    if (info.language)
-        stack.push(`language: ${info.language}`);
-    if (stack.length > 0)
-        lines.push(`- Test stack — ${stack.join(", ")}`);
-    if (info.repository_url)
-        lines.push(`- Repository: ${info.repository_url}`);
-    if (info.artifacts_storage_enabled) {
-        lines.push("- Artifacts storage is enabled (test runs can attach screenshots/videos/logs)");
-    }
-    if (info.environments?.length > 0) {
-        const shown = info.environments.slice(0, MAX_PROMPT_ENVS);
-        lines.push(`- Environments: ${capped(shown, info.environments.length)}`);
-    }
-    if (info.features?.length > 0) {
-        lines.push(`- Enabled features: ${info.features.join(", ")}`);
-    }
-    if (info.labels?.length > 0) {
-        const shown = info.labels
-            .slice(0, MAX_PROMPT_LABELS)
-            .map((l) => `${l.title} (\`${l.slug}\`)`);
-        lines.push(`- Labels defined in this project: ${capped(shown, info.labels.length)}`);
-    }
-    if (info.tags?.length > 0) {
-        const shown = info.tags.slice(0, MAX_PROMPT_TAGS).map((t) => `@${t}`);
-        lines.push(`- Tags in use: ${capped(shown, info.tags.length)}`);
-    }
-    if (info.ci_profiles?.length > 0) {
-        const profiles = info.ci_profiles.map((p) => {
-            if (p.service)
-                return `"${p.profile_name}" (${p.service})`;
-            return `"${p.profile_name}"`;
-        });
-        lines.push(`- CI profiles configured (runs can be triggered through them): ${profiles.join(", ")}`);
-    }
-    let body = heading;
-    if (lines.length > 0)
-        body += `\n\n${lines.join("\n")}`;
-    return dedent `
-    ## Project Settings (Testomat.io)
-
-    ${body}
-
-    Use these when creating or editing tests: assign only labels that exist here, reuse the existing tags/environments before inventing new ones, and match the project's framework/language when generating automated tests. The full configuration JSON (every label, tag, and CI profile config) is cached at \`.testeiya/project-info.json\` — read that file when you need the complete lists.
-  `;
-}
-// How to act on a connection whose token comes from the environment.
-function envTokenActions(access) {
-    if (access === "mcp-proxy") {
-        return "For structured actions (list/create/update tests, runs, labels, suites, etc.) prefer the `mcp` tool: `mcp({ search })` to find an operation, `mcp({ tool })` to run it.";
-    }
-    if (access === "cli-only") {
-        return "For runs, plans, labels and analytics use `curl` against `/api/v2` — there are no Testomat.io tools in this session.";
-    }
-    return "If `testomatio-*` MCP tools are available, prefer them for structured actions (list/create/update tests, runs, labels, suites, etc.).";
-}
-// The same, where the harness runs one MCP server per pulled project.
-function perProjectActions(access) {
-    if (access === "mcp-proxy") {
-        return "The **Testomat.io MCP server** is also connected, reached through the `mcp` tool (`mcp({ search })` to find an operation, `mcp({ tool })` to run it). Prefer it for structured actions (list/create/update tests, runs, labels, suites, etc.) — those are typed, safer, and faster than shell calls. Fall back to `bash` + `check-tests` only for things it does not cover (e.g. pulling full markdown files).";
-    }
-    if (access === "cli-only") {
-        return "There are no Testomat.io tools in this session: use `npx check-tests` for test cases and `curl` against `/api/v2` for runs, plans and labels.";
-    }
-    return "The **Testomat.io MCP server** is also auto-connected, one instance per project (tool prefix: `testomatio-<slug>`). Prefer MCP tools for structured actions (list/create/update tests, runs, labels, suites, etc.) — they are typed, safer, and faster than shell calls. Fall back to `bash` + `check-tests` only for things the MCP does not cover (e.g. pulling full markdown files).";
-}
-function capped(shown, total) {
-    let suffix = "";
-    if (total > shown.length) {
-        suffix = ` … and ${total - shown.length} more (see \`.testeiya/project-info.json\`)`;
-    }
-    return shown.join(", ") + suffix;
-}
-//# sourceMappingURL=testomatio.js.map

package/dist/prompt/testomatio.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"testomatio.js","sourceRoot":"","sources":["../../prompt/testomatio.ts"],"names":[],"mappings":"AAAA,OAAO,MAAM,MAAM,QAAQ,CAAC;AAG5B,MAAM,iBAAiB,GAAG,EAAE,CAAC;AAC7B,MAAM,eAAe,GAAG,EAAE,CAAC;AAC3B,MAAM,eAAe,GAAG,EAAE,CAAC;AAE3B,MAAM,iBAAiB,GAAG,MAAM,CAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAkC/B,CAAC;AAEF,MAAM,WAAW,GAAG,MAAM,CAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAoCzB,CAAC;AAEF,MAAM,SAAS,GAAG,MAAM,CAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA+BvB,CAAC;AAEF;;;GAGG;AACH,MAAM,UAAU,aAAa,CAAC,MAAiB;IAC7C,IAAI,MAAM,KAAK,WAAW;QAAE,OAAO,WAAW,CAAC;IAC/C,IAAI,MAAM,KAAK,UAAU;QAAE,OAAO,SAAS,CAAC;IAC5C,OAAO,iBAAiB,CAAC;AAC3B,CAAC;AAED,MAAM,UAAU,oBAAoB,CAClC,UAAoB,EACpB,UAAmB,EACnB,UAAmD,EACnD,SAAoB,YAAY;IAEhC,IAAI,SAAS,GAAG,EAAE,CAAC;IACnB,IAAI,UAAU;QAAE,SAAS,GAAG,OAAO,UAAU,KAAK,CAAC;IAEnD,IAAI,UAAU,CAAC,MAAM,KAAK,CAAC,EAAE,CAAC;QAC5B,IAAI,OAAO,GAAG,EAAE,CAAC;QACjB,IAAI,UAAU,EAAE,SAAS;YAAE,OAAO,GAAG,MAAM,UAAU,CAAC,SAAS,IAAI,CAAC;QACpE,IAAI,UAAU,EAAE,KAAK;YAAE,OAAO,IAAI,MAAM,UAAU,CAAC,KAAK,IAAI,CAAC;QAC7D,OAAO,MAAM,CAAA;;;2DAG0C,OAAO;;oJAEkF,SAAS;;+JAEE,eAAe,CAAC,MAAM,CAAC;;KAEjL,CAAC;IACJ,CAAC;IAED,IAAI,UAAU,CAAC,MAAM,GAAG,CAAC,EAAE,CAAC;QAC1B,MAAM,QAAQ,GAAG,UAAU,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,KAAK,CAAC,EAAE,CAAC,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;QAC5D,OAAO,MAAM,CAAA;;;kIAGiH,SAAS;;;QAGnI,QAAQ;;KAEX,CAAC;IACJ,CAAC;IAED,MAAM,QAAQ,GAAG,UAAU,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,KAAK,CAAC,EAAE,CAAC,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;IAC5D,OAAO,MAAM,CAAA;;;uIAGwH,SAAS;;;;;MAK1I,QAAQ;;MAER,iBAAiB,CAAC,MAAM,CAAC;;;;GAI5B,CAAC;AACJ,CAAC;AAED,MAAM,UAAU,sBAAsB;IACpC,OAAO,MAAM,CAAA;;;;;;GAMZ,CAAC;AACJ,CAAC;AAED;;;;GAIG;AACH,MAAM,UAAU,eAAe,CAAC,IAA2B;IACzD,IAAI,OAAO,GAAG,KAAK,IAAI,CAAC,KAAK,SAAS,IAAI,CAAC,UAAU,KAAK,CAAC;IAC3D,IAAI,IAAI,CAAC,YAAY;QAAE,OAAO,IAAI,MAAM,IAAI,CAAC,YAAY,OAAO,CAAC;IAEjE,MAAM,KAAK,GAAa,EAAE,CAAC;IAC3B,MAAM,KAAK,GAAa,EAAE,CAAC;IAC3B,IAAI,IAAI,CAAC,SAAS;QAAE,KAAK,CAAC,IAAI,CAAC,cAAc,IAAI,CAAC,SAAS,EAAE,CAAC,CAAC;IAC/D,IAAI,IAAI,CAAC,QAAQ;QAAE,KAAK,CAAC,IAAI,CAAC,aAAa,IAAI,CAAC,QAAQ,EAAE,CAAC,CAAC;IAC5D,IAAI,KAAK,CAAC,MAAM,GAAG,CAAC;QAAE,KAAK,CAAC,IAAI,CAAC,kBAAkB,KAAK,CAAC,IAAI,CAAC,IAAI,CAAC,EAAE,CAAC,CAAC;IACvE,IAAI,IAAI,CAAC,cAAc;QAAE,KAAK,CAAC,IAAI,CAAC,iBAAiB,IAAI,CAAC,cAAc,EAAE,CAAC,CAAC;IAC5E,IAAI,IAAI,CAAC,yBAAyB,EAAE,CAAC;QACnC,KAAK,CAAC,IAAI,CAAC,+EAA+E,CAAC,CAAC;IAC9F,CAAC;IACD,IAAI,IAAI,CAAC,YAAY,EAAE,MAAM,GAAG,CAAC,EAAE,CAAC;QAClC,MAAM,KAAK,GAAG,IAAI,CAAC,YAAY,CAAC,KAAK,CAAC,CAAC,EAAE,eAAe,CAAC,CAAC;QAC1D,KAAK,CAAC,IAAI,CAAC,mBAAmB,MAAM,CAAC,KAAK,EAAE,IAAI,CAAC,YAAY,CAAC,MAAM,CAAC,EAAE,CAAC,CAAC;IAC3E,CAAC;IACD,IAAI,IAAI,CAAC,QAAQ,EAAE,MAAM,GAAG,CAAC,EAAE,CAAC;QAC9B,KAAK,CAAC,IAAI,CAAC,uBAAuB,IAAI,CAAC,QAAQ,CAAC,IAAI,CAAC,IAAI,CAAC,EAAE,CAAC,CAAC;IAChE,CAAC;IACD,IAAI,IAAI,CAAC,MAAM,EAAE,MAAM,GAAG,CAAC,EAAE,CAAC;QAC5B,MAAM,KAAK,GAAG,IAAI,CAAC,MAAM;aACtB,KAAK,CAAC,CAAC,EAAE,iBAAiB,CAAC;aAC3B,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,GAAG,CAAC,CAAC,KAAK,OAAO,CAAC,CAAC,IAAI,KAAK,CAAC,CAAC;QAC5C,KAAK,CAAC,IAAI,CAAC,qCAAqC,MAAM,CAAC,KAAK,EAAE,IAAI,CAAC,MAAM,CAAC,MAAM,CAAC,EAAE,CAAC,CAAC;IACvF,CAAC;IACD,IAAI,IAAI,CAAC,IAAI,EAAE,MAAM,GAAG,CAAC,EAAE,CAAC;QAC1B,MAAM,KAAK,GAAG,IAAI,CAAC,IAAI,CAAC,KAAK,CAAC,CAAC,EAAE,eAAe,CAAC,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,IAAI,CAAC,EAAE,CAAC,CAAC;QACtE,KAAK,CAAC,IAAI,CAAC,kBAAkB,MAAM,CAAC,KAAK,EAAE,IAAI,CAAC,IAAI,CAAC,MAAM,CAAC,EAAE,CAAC,CAAC;IAClE,CAAC;IACD,IAAI,IAAI,CAAC,WAAW,EAAE,MAAM,GAAG,CAAC,EAAE,CAAC;QACjC,MAAM,QAAQ,GAAG,IAAI,CAAC,WAAW,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE;YAC1C,IAAI,CAAC,CAAC,OAAO;gBAAE,OAAO,IAAI,CAAC,CAAC,YAAY,MAAM,CAAC,CAAC,OAAO,GAAG,CAAC;YAC3D,OAAO,IAAI,CAAC,CAAC,YAAY,GAAG,CAAC;QAC/B,CAAC,CAAC,CAAC;QACH,KAAK,CAAC,IAAI,CAAC,kEAAkE,QAAQ,CAAC,IAAI,CAAC,IAAI,CAAC,EAAE,CAAC,CAAC;IACtG,CAAC;IAED,IAAI,IAAI,GAAG,OAAO,CAAC;IACnB,IAAI,KAAK,CAAC,MAAM,GAAG,CAAC;QAAE,IAAI,IAAI,OAAO,KAAK,CAAC,IAAI,CAAC,IAAI,CAAC,EAAE,CAAC;IAExD,OAAO,MAAM,CAAA;;;MAGT,IAAI;;;GAGP,CAAC;AACJ,CAAC;AAED,qEAAqE;AACrE,SAAS,eAAe,CAAC,MAAiB;IACxC,IAAI,MAAM,KAAK,WAAW,EAAE,CAAC;QAC3B,OAAO,yKAAyK,CAAC;IACnL,CAAC;IACD,IAAI,MAAM,KAAK,UAAU,EAAE,CAAC;QAC1B,OAAO,sHAAsH,CAAC;IAChI,CAAC;IACD,OAAO,uIAAuI,CAAC;AACjJ,CAAC;AAED,sEAAsE;AACtE,SAAS,iBAAiB,CAAC,MAAiB;IAC1C,IAAI,MAAM,KAAK,WAAW,EAAE,CAAC;QAC3B,OAAO,gZAAgZ,CAAC;IAC1Z,CAAC;IACD,IAAI,MAAM,KAAK,UAAU,EAAE,CAAC;QAC1B,OAAO,+IAA+I,CAAC;IACzJ,CAAC;IACD,OAAO,yXAAyX,CAAC;AACnY,CAAC;AAED,SAAS,MAAM,CAAC,KAAe,EAAE,KAAa;IAC5C,IAAI,MAAM,GAAG,EAAE,CAAC;IAChB,IAAI,KAAK,GAAG,KAAK,CAAC,MAAM,EAAE,CAAC;QACzB,MAAM,GAAG,UAAU,KAAK,GAAG,KAAK,CAAC,MAAM,6CAA6C,CAAC;IACvF,CAAC;IACD,OAAO,KAAK,CAAC,IAAI,CAAC,IAAI,CAAC,GAAG,MAAM,CAAC;AACnC,CAAC"}

package/dist/prompt/tools.js

@@ -1,70 +0,0 @@
-import { existsSync } from 'node:fs';
-import { delimiter, join } from 'node:path';
-import dedent from 'dedent';
-/**
- * The tools every harness gives the agent. Anything a particular harness adds —
- * a question tool, a browser it can drive for a watching user — arrives as an
- * extra bullet from that harness, since the agent must not be told about a tool
- * it does not have.
- */
-export function tools(options) {
-    const extra = (options?.extra ?? []).join('');
-    let routing = '    - GitHub: issues and projects through MCP.';
-    if (onPath('gh')) {
-        routing +=
-            '\n    - Pull requests and repositories: `gh` in `bash`. When a PR question needs issue detail, query the issue through MCP — never infer it from a PR title.';
-    }
-    if (onPath('acli')) {
-        routing +=
-            '\n    - Jira in bulk (many issues at once), boards, sprints and filters: `acli` in `bash`, per the `atlassian` skill. Confluence and attachments have no `acli` command and stay on MCP.';
-    }
-    if (onPath('glab')) {
-        routing +=
-            '\n    - GitLab releases, labels, milestones, snippets, CI artifacts, and any endpoint with no MCP tool: `glab` in `bash`. Issues, merge requests, pipelines and code search stay on MCP, which covers them well.';
-    }
-    return dedent `
-<available-tools>
-  You have these tools available:
-  * **Read operations (use freely):** \`read\`, \`grep\`, \`ls\`.
-    - Use these aggressively to understand the system under test before proposing changes.
-  * **Write operations (restricted):** \`write\`, \`edit\`, \`bash\`.
-    - Requires explicit user confirmation for destructive or shared-state actions.
-${extra}  * **Internal Skills:** For QA-related tasks, check available skills first and prefer using them when applicable.
-  * **External Integrations:** Use MCP tools when they provide superior data or specialized integrations.
-    - Primary MCP (Testomat.io): Use Testomat.io MCP tools to extend functionality.
-    - Secondary MCP (Jira, GitHub, etc.): Invoke only when user explicitly asks or when remote context exploration is required.
-${routing}
-
-  <tool-governance>
-    * **Prioritize Specificity:** Use \`read\` instead of \`cat\`, and \`edit\` instead of \`sed\`. Dedicated tools provide better error tracking and safety.
-    * **Parallel Execution:** Call independent tools in parallel to minimize latency. Sequential calls are reserved for operations with data dependencies.
-    * **Atomic Updates:** Mark tasks as complete in your internal state immediately upon execution. Do not batch status updates.
-    * **Analysis-First:** Use your own reasoning to guide tool selection. Do not wait for step-by-step instructions if discovery tools can provide the answer.
-  </tool-governance>
-</available-tools>
-`;
-}
-/** Is this CLI on PATH? Never tell the agent to use a binary this machine lacks. */
-function onPath(bin) {
-    for (const dir of (process.env.PATH ?? '').split(delimiter)) {
-        if (!dir)
-            continue;
-        if (existsSync(join(dir, bin)) || existsSync(join(dir, `${bin}.exe`)))
-            return true;
-    }
-    return false;
-}
-/**
- * CLIs Testeiya knows how to connect, probed on PATH — the same trio routed in
- * `<available-tools>` above. Shared with the prompt's connections section so
- * the two can never disagree about whether `gh` etc. exist.
- */
-export const KNOWN_CLIS = [
-    { bin: 'gh', label: 'gh (GitHub CLI)' },
-    { bin: 'acli', label: 'acli (Atlassian CLI)' },
-    { bin: 'glab', label: 'glab (GitLab CLI)' },
-];
-export function pathClis() {
-    return KNOWN_CLIS.filter((c) => onPath(c.bin)).map((c) => c.label);
-}
-//# sourceMappingURL=tools.js.map

package/dist/prompt/tools.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"tools.js","sourceRoot":"","sources":["../../prompt/tools.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,UAAU,EAAE,MAAM,SAAS,CAAC;AACrC,OAAO,EAAE,SAAS,EAAE,IAAI,EAAE,MAAM,WAAW,CAAC;AAE5C,OAAO,MAAM,MAAM,QAAQ,CAAC;AAE5B;;;;;GAKG;AACH,MAAM,UAAU,KAAK,CAAC,OAA8B;IAClD,MAAM,KAAK,GAAG,CAAC,OAAO,EAAE,KAAK,IAAI,EAAE,CAAC,CAAC,IAAI,CAAC,EAAE,CAAC,CAAC;IAC9C,IAAI,OAAO,GAAG,gDAAgD,CAAC;IAC/D,IAAI,MAAM,CAAC,IAAI,CAAC,EAAE,CAAC;QACjB,OAAO;YACL,8JAA8J,CAAC;IACnK,CAAC;IACD,IAAI,MAAM,CAAC,MAAM,CAAC,EAAE,CAAC;QACnB,OAAO;YACL,0LAA0L,CAAC;IAC/L,CAAC;IACD,IAAI,MAAM,CAAC,MAAM,CAAC,EAAE,CAAC;QACnB,OAAO;YACL,kNAAkN,CAAC;IACvN,CAAC;IACD,OAAO,MAAM,CAAA;;;;;;;EAOb,KAAK;;;;EAIL,OAAO;;;;;;;;;CASR,CAAC;AACF,CAAC;AAED,oFAAoF;AACpF,SAAS,MAAM,CAAC,GAAW;IACzB,KAAK,MAAM,GAAG,IAAI,CAAC,OAAO,CAAC,GAAG,CAAC,IAAI,IAAI,EAAE,CAAC,CAAC,KAAK,CAAC,SAAS,CAAC,EAAE,CAAC;QAC5D,IAAI,CAAC,GAAG;YAAE,SAAS;QACnB,IAAI,UAAU,CAAC,IAAI,CAAC,GAAG,EAAE,GAAG,CAAC,CAAC,IAAI,UAAU,CAAC,IAAI,CAAC,GAAG,EAAE,GAAG,GAAG,MAAM,CAAC,CAAC;YAAE,OAAO,IAAI,CAAC;IACrF,CAAC;IACD,OAAO,KAAK,CAAC;AACf,CAAC;AAED;;;;GAIG;AACH,MAAM,CAAC,MAAM,UAAU,GAAqC;IAC1D,EAAE,GAAG,EAAE,IAAI,EAAE,KAAK,EAAE,iBAAiB,EAAE;IACvC,EAAE,GAAG,EAAE,MAAM,EAAE,KAAK,EAAE,sBAAsB,EAAE;IAC9C,EAAE,GAAG,EAAE,MAAM,EAAE,KAAK,EAAE,mBAAmB,EAAE;CAC5C,CAAC;AAEF,MAAM,UAAU,QAAQ;IACtB,OAAO,UAAU,CAAC,MAAM,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,MAAM,CAAC,CAAC,CAAC,GAAG,CAAC,CAAC,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,KAAK,CAAC,CAAC;AACrE,CAAC"}

package/dist/prompt/vocab.js

@@ -1,8 +0,0 @@
-/**
- * The per-project config directory name, as the agent knows it. Part of the
- * vocabulary the system prompt teaches — every path the prompt names below it
- * (`.testeiya/manual-tests`, `.testeiya/project-info.json`, …) is built from
- * this constant, so the prompt and the harness can never disagree about it.
- */
-export const TESTEIYA_DIR_NAME = ".testeiya";
-//# sourceMappingURL=vocab.js.map

package/dist/prompt/vocab.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"vocab.js","sourceRoot":"","sources":["../../prompt/vocab.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AACH,MAAM,CAAC,MAAM,iBAAiB,GAAG,WAAW,CAAC"}

package/prompt/context.ts

@@ -1,108 +0,0 @@
-import dedent from "dedent";
-import { TESTEIYA_DIR_NAME } from "./vocab.js";
-
-/** System-prompt section describing the workspace context; "" when none. */
-export function contextPromptSection(
-  entries: ContextEntry[],
-  folders: ContextFolder[] = []
-): string {
-  if (entries.length === 0 && folders.length === 0) return "";
-  return dedent`
-  <workspace-context>
-    This workspace has context attached — the user (or you, earlier) put it there for a purpose. Consult it before answering, and prefer it over assumptions about the project.
-
-  ${contextLines(entries, folders)}
-
-    Everything whose path starts with \`${TESTEIYA_DIR_NAME}/\` is in a hidden dir: file-search tools skip hidden dirs by default, so search those explicitly (pass hidden:true, or prefix the path with \`${TESTEIYA_DIR_NAME}/\`). Any other path above is an ordinary workspace path the user attached — read it where it is. Linked folders and cloned repositories are reference material: read them, never modify them. A linked folder is a symlink — wildcard searches do not descend into it; search it with its own path prefix (e.g. \`${TESTEIYA_DIR_NAME}/<name>/\`). Documents under \`${TESTEIYA_DIR_NAME}/requirements\` and \`${TESTEIYA_DIR_NAME}/docs\` are specs and plans — use them when writing or reviewing tests.
-  </workspace-context>
-  `;
-}
-
-/** Per-prompt notice when the context changed mid-session; appended to the next prompt. */
-export function contextUpdateNotice(
-  entries: ContextEntry[],
-  folders: ContextFolder[] = []
-): string {
-  if (entries.length === 0 && folders.length === 0) {
-    return dedent`
-    <workspace-context-update>
-      All extra workspace context was removed. Do not rely on it anymore.
-    </workspace-context-update>
-    `;
-  }
-  return dedent`
-  <workspace-context-update>
-    The workspace context just changed. It now contains:
-
-  ${contextLines(entries, folders)}
-
-    This was done for a purpose — take it into account for this and future requests. Remember \`${TESTEIYA_DIR_NAME}/\` is hidden: search it with hidden:true or an explicit path prefix.
-  </workspace-context-update>
-  `;
-}
-
-function contextLines(entries: ContextEntry[], folders: ContextFolder[]): string {
-  const lines: string[] = [];
-  const covered = new Set(entries.map((e) => parentDir(e.path)));
-  for (const f of folders) {
-    if (covered.has(f.path)) continue;
-    lines.push(`- \`${f.path}/\` — ${folderPurpose(f.name)}`);
-  }
-  for (const e of entries) lines.push(`- ${describeEntry(e)}`);
-  return lines.join("\n");
-}
-
-function folderPurpose(name: string): string {
-  if (name === "manual-tests") {
-    return "the project's manual test suites pulled from Testomat.io (*.test.md — THE manual tests of this project)";
-  }
-  if (name === "code") return "reference code added as context";
-  if (name === "requirements") return "requirements and specs";
-  if (name === "docs") return "test planning and strategy documents";
-  if (name === "auto-tests") return "automated test references";
-  return "exploratory testing setup";
-}
-
-function parentDir(rel: string): string {
-  const idx = rel.lastIndexOf("/");
-  if (idx < 0) return "";
-  return rel.slice(0, idx);
-}
-
-function describeEntry(e: ContextEntry): string {
-  const date = e.addedAt?.split("T")[0] ?? "";
-  // A path outside the hidden dir is one the user attached where it already
-  // lives — it is part of the project, not reference material dropped beside it.
-  if (!e.path.startsWith(`${TESTEIYA_DIR_NAME}/`)) {
-    let what = "folder";
-    if (e.kind === "file") what = "file";
-    return `\`${e.path}\` — workspace ${what}, attached by the user (${date})`;
-  }
-  let from = "";
-  if (e.origin && e.origin !== e.name) from = ` from ${e.origin}`;
-  if (e.kind === "repo") return `\`${e.path}\` — git repository${from} (${date})`;
-  if (e.kind === "folder") return `\`${e.path}\` — local folder${from} (${date})`;
-  return `\`${e.path}\` — document${from} (${date})`;
-}
-
-export type ContextKind = "folder" | "repo" | "file";
-
-/** A top-level `.testeiya` folder shown as a status-bar section. */
-export interface ContextFolder {
-  name: string;
-  /** Relative to cwd (`.testeiya/<name>`). */
-  path: string;
-  /** Direct children (files + dirs, dot entries excluded). */
-  count: number;
-}
-
-export interface ContextEntry {
-  id: string;
-  kind: ContextKind;
-  name: string;
-  /** Location inside the workspace, relative to cwd (always under `.testeiya/`). */
-  path: string;
-  /** Where it came from: an absolute local path, a git URL, or the uploaded filename. */
-  origin: string;
-  addedAt: string;
-}

package/prompt/index.ts

@@ -1,102 +0,0 @@
-import { getSystemPrompt } from "./system-prompt.js";
-import {
-  testomatioTms,
-  testomatioConnection,
-  testomatioNotConnected,
-  projectSettings,
-  type TmsAccess,
-} from "./testomatio.js";
-import { briefAnswer, nonInteractive, reportOutput } from "./print.js";
-import {
-  contextPromptSection,
-  type ContextEntry,
-  type ContextFolder,
-} from "./context.js";
-import type { TestomatioProjectInfo } from "./project-info.js";
-
-export function buildSystemPrompt(options?: SystemPromptOptions): string {
-  const mode = options?.mode ?? "tui";
-  const interactive = mode !== "print";
-
-  // The base prompt (role, workspace, tools, goals) comes first — it defines who
-  // the agent is. Specialized rules layer on after it, dynamic context goes last.
-  // Anything only one harness can do — its own question tool, a browser it can
-  // open for a watching user — reaches the prompt through `sections`,
-  // `toolBullets` and `rules`, never from here.
-  const parts: string[] = [
-    getSystemPrompt(options?.cwd, {
-      interactive,
-      toolBullets: options?.toolBullets,
-      rules: options?.rules,
-      connectedClis: options?.connectedClis,
-      connectedMcps: options?.connectedMcps,
-    }),
-  ];
-
-  const tokenSlugs = options?.tokens ? Object.keys(options.tokens) : [];
-  // The TUI passes no `connection`, so it keeps the managed-tokens gating.
-  const tokenAvailable = options?.connection?.tokenAvailable ?? tokenSlugs.length > 0;
-  const tms = options?.tms ?? "mcp-direct";
-  // Gated on the same condition as the connection section below: both describe
-  // the same connection, and the rules are just as needed when the token comes
-  // from the environment rather than from a per-project session token.
-  if (tokenAvailable || tokenSlugs.length > 0) parts.push(testomatioTms(tms));
-  if (mode === "print") parts.push(nonInteractive);
-  // Whatever this harness alone can offer — its chat-app UI tools, a browser it
-  // can open for a watching user. A one-shot CLI contributes none of it, and
-  // `nonInteractive` tells the agent to report such a gap rather than try.
-  for (const section of options?.sections ?? []) parts.push(section);
-
-  if (options?.promptContext) {
-    parts.push(`## Project Test Context\n\n${options.promptContext}`);
-  }
-  if (options?.contextEntries?.length || options?.contextFolders?.length) {
-    parts.push(
-      contextPromptSection(options.contextEntries ?? [], options.contextFolders ?? [])
-    );
-  }
-  if (options?.projectInfo) {
-    parts.push(projectSettings(options.projectInfo));
-  }
-  if (tokenAvailable || tokenSlugs.length > 0) {
-    parts.push(testomatioConnection(tokenSlugs, options?.backendUrl, options?.connection, tms));
-  } else if (mode === "web" || mode === "print") {
-    parts.push(testomatioNotConnected());
-  }
-
-  // The answer contract goes last so it is the final instruction the model reads.
-  if (options?.brief) parts.push(briefAnswer);
-  if (options?.outputFile) parts.push(reportOutput(options.outputFile));
-
-  return parts.join("\n\n");
-}
-
-export interface SystemPromptOptions {
-  cwd?: string;
-  promptContext?: string;
-  backendUrl?: string;
-  tokens?: Record<string, string>;
-  connection?: { tokenAvailable?: boolean; projectId?: string; title?: string };
-  mode?: "tui" | "web" | "print";
-  /** Whole sections this harness contributes (chat-app UI tools, live browser). */
-  sections?: string[];
-  /** Extra `<available-tools>` bullets for tools only this harness provides. */
-  toolBullets?: string[];
-  /** Extra `<rules>` bullets, for rules that only hold in this harness. */
-  rules?: string[];
-  /** How the agent reaches Testomat.io; defaults to `mcp-direct`. */
-  tms?: TmsAccess;
-  /** Absolute path the agent must write its final report to (`--output`). */
-  outputFile?: string;
-  /** Answer a question instead of doing a task and reporting (`testeiya ask`). */
-  brief?: boolean;
-  projectInfo?: TestomatioProjectInfo | null;
-  /** User-added context (linked folders, cloned repos, uploaded docs). */
-  contextEntries?: ContextEntry[];
-  /** Non-empty predefined `.testeiya` context folders (manual-tests, code, …). */
-  contextFolders?: ContextFolder[];
-  /** CLI tools the user has connected and signed in (e.g. `gh`, `acli`). */
-  connectedClis?: string[];
-  /** MCP servers connected for this session (the enabled `mcp.json` set). */
-  connectedMcps?: string[];
-}

package/prompt/print.ts

@@ -1,32 +0,0 @@
-import dedent from "dedent";
-
-export const nonInteractive = dedent`
-<non-interactive>
-  * Nobody is watching this session. There is no way to ask a question and no answer will ever come.
-  * Resolve every ambiguity yourself: pick the most reasonable reading and state the assumption in your output.
-  * Never wait for input, confirmation, or approval. Finish the whole task in this run.
-  * Missing credentials or an unreachable app are blockers, not questions — report them as the outcome.
-  * Do not launch or drive a browser. If the task needs one, report what it would take and stop.
-  * Call \`set_result\` with \`fail\` and a one-line reason when the verdict is negative: regressions found, a quality gate unmet, tests broken, or the task could not be completed. Otherwise do not call it — silence means success.
-</non-interactive>
-`;
-
-export function reportOutput(path: string): string {
-  return dedent`
-<final-report>
-  * Write your complete final report to \`${path}\` with the \`write\` tool. Writing it is required before you finish.
-  * That file is your answer — it is the run's deliverable. Nothing else you say is kept.
-  * Markdown. Open with an \`#\` title, then the findings. Overwrite the file; never append.
-  * Keep your chat replies short: the report carries the detail.
-</final-report>
-`;
-}
-
-export const briefAnswer = dedent`
-<answer>
-  * You were asked a question, not given a task. Answer it.
-  * Lead with the answer in one line, then the evidence you checked.
-  * A few sentences. No report file, no headings, no plan.
-  * Say plainly when what you found does not settle the question.
-</answer>
-`;

package/prompt/project-info.ts

@@ -1,30 +0,0 @@
-/**
- * A project's configuration as Testomat.io reports it (`GET /api/v2/{id}/info`).
- * Rendered into the system prompt by `projectSettings` so the agent assigns only
- * labels that exist, reuses the project's tags and environments, and matches its
- * framework when writing automated tests.
- */
-export interface TestomatioProjectInfo {
-  title: string;
-  project_id: string;
-  framework: string | null;
-  language: string | null;
-  status: string | null;
-  repository_url: string | null;
-  artifacts_storage_enabled: boolean;
-  environments: string[];
-  labels: { title: string; slug: string }[];
-  tags: string[];
-  subscription: string | null;
-  features: string[];
-  ci_profiles: TestomatioCiProfile[];
-}
-
-export interface TestomatioCiProfile {
-  profile_name: string;
-  service: string | null;
-  config: Record<string, unknown> | null;
-  pass_testomatio_key: boolean;
-  pass_testomatio_url: boolean;
-  pass_run_id: boolean;
-}