testeiya 0.2.1 → 0.3.10

package/dist/prompt/index.js

@@ -0,0 +1,60 @@
+import { getSystemPrompt } from "./system-prompt.js";
+import { testomatioTms, testomatioConnection, testomatioNotConnected, projectSettings, } from "./testomatio.js";
+import { briefAnswer, nonInteractive, reportOutput } from "./print.js";
+import { contextPromptSection, } from "./context.js";
+export function buildSystemPrompt(options) {
+    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 = [
+        getSystemPrompt(options?.cwd, {
+            interactive,
+            toolBullets: options?.toolBullets,
+            rules: options?.rules,
+            connectedClis: options?.connectedClis,
+            supportedMcps: options?.supportedMcps,
+        }),
+    ];
+    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");
+}
+//# sourceMappingURL=index.js.map

package/dist/prompt/index.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../../prompt/index.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,eAAe,EAAE,MAAM,oBAAoB,CAAC;AACrD,OAAO,EACL,aAAa,EACb,oBAAoB,EACpB,sBAAsB,EACtB,eAAe,GAEhB,MAAM,iBAAiB,CAAC;AACzB,OAAO,EAAE,WAAW,EAAE,cAAc,EAAE,YAAY,EAAE,MAAM,YAAY,CAAC;AACvE,OAAO,EACL,oBAAoB,GAGrB,MAAM,cAAc,CAAC;AAGtB,MAAM,UAAU,iBAAiB,CAAC,OAA6B;IAC7D,MAAM,IAAI,GAAG,OAAO,EAAE,IAAI,IAAI,KAAK,CAAC;IACpC,MAAM,WAAW,GAAG,IAAI,KAAK,OAAO,CAAC;IAErC,+EAA+E;IAC/E,gFAAgF;IAChF,6EAA6E;IAC7E,oEAAoE;IACpE,8CAA8C;IAC9C,MAAM,KAAK,GAAa;QACtB,eAAe,CAAC,OAAO,EAAE,GAAG,EAAE;YAC5B,WAAW;YACX,WAAW,EAAE,OAAO,EAAE,WAAW;YACjC,KAAK,EAAE,OAAO,EAAE,KAAK;YACrB,aAAa,EAAE,OAAO,EAAE,aAAa;YACrC,aAAa,EAAE,OAAO,EAAE,aAAa;SACtC,CAAC;KACH,CAAC;IAEF,MAAM,UAAU,GAAG,OAAO,EAAE,MAAM,CAAC,CAAC,CAAC,MAAM,CAAC,IAAI,CAAC,OAAO,CAAC,MAAM,CAAC,CAAC,CAAC,CAAC,EAAE,CAAC;IACtE,yEAAyE;IACzE,MAAM,cAAc,GAAG,OAAO,EAAE,UAAU,EAAE,cAAc,IAAI,UAAU,CAAC,MAAM,GAAG,CAAC,CAAC;IACpF,MAAM,GAAG,GAAG,OAAO,EAAE,GAAG,IAAI,YAAY,CAAC;IACzC,6EAA6E;IAC7E,6EAA6E;IAC7E,qEAAqE;IACrE,IAAI,cAAc,IAAI,UAAU,CAAC,MAAM,GAAG,CAAC;QAAE,KAAK,CAAC,IAAI,CAAC,aAAa,CAAC,GAAG,CAAC,CAAC,CAAC;IAC5E,IAAI,IAAI,KAAK,OAAO;QAAE,KAAK,CAAC,IAAI,CAAC,cAAc,CAAC,CAAC;IACjD,8EAA8E;IAC9E,2EAA2E;IAC3E,yEAAyE;IACzE,KAAK,MAAM,OAAO,IAAI,OAAO,EAAE,QAAQ,IAAI,EAAE;QAAE,KAAK,CAAC,IAAI,CAAC,OAAO,CAAC,CAAC;IAEnE,IAAI,OAAO,EAAE,aAAa,EAAE,CAAC;QAC3B,KAAK,CAAC,IAAI,CAAC,8BAA8B,OAAO,CAAC,aAAa,EAAE,CAAC,CAAC;IACpE,CAAC;IACD,IAAI,OAAO,EAAE,cAAc,EAAE,MAAM,IAAI,OAAO,EAAE,cAAc,EAAE,MAAM,EAAE,CAAC;QACvE,KAAK,CAAC,IAAI,CACR,oBAAoB,CAAC,OAAO,CAAC,cAAc,IAAI,EAAE,EAAE,OAAO,CAAC,cAAc,IAAI,EAAE,CAAC,CACjF,CAAC;IACJ,CAAC;IACD,IAAI,OAAO,EAAE,WAAW,EAAE,CAAC;QACzB,KAAK,CAAC,IAAI,CAAC,eAAe,CAAC,OAAO,CAAC,WAAW,CAAC,CAAC,CAAC;IACnD,CAAC;IACD,IAAI,cAAc,IAAI,UAAU,CAAC,MAAM,GAAG,CAAC,EAAE,CAAC;QAC5C,KAAK,CAAC,IAAI,CAAC,oBAAoB,CAAC,UAAU,EAAE,OAAO,EAAE,UAAU,EAAE,OAAO,EAAE,UAAU,EAAE,GAAG,CAAC,CAAC,CAAC;IAC9F,CAAC;SAAM,IAAI,IAAI,KAAK,KAAK,IAAI,IAAI,KAAK,OAAO,EAAE,CAAC;QAC9C,KAAK,CAAC,IAAI,CAAC,sBAAsB,EAAE,CAAC,CAAC;IACvC,CAAC;IAED,gFAAgF;IAChF,IAAI,OAAO,EAAE,KAAK;QAAE,KAAK,CAAC,IAAI,CAAC,WAAW,CAAC,CAAC;IAC5C,IAAI,OAAO,EAAE,UAAU;QAAE,KAAK,CAAC,IAAI,CAAC,YAAY,CAAC,OAAO,CAAC,UAAU,CAAC,CAAC,CAAC;IAEtE,OAAO,KAAK,CAAC,IAAI,CAAC,MAAM,CAAC,CAAC;AAC5B,CAAC"}

package/dist/prompt/print.js

@@ -0,0 +1,30 @@
+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) {
+    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>
+`;
+//# sourceMappingURL=print.js.map

package/dist/prompt/print.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"print.js","sourceRoot":"","sources":["../../prompt/print.ts"],"names":[],"mappings":"AAAA,OAAO,MAAM,MAAM,QAAQ,CAAC;AAE5B,MAAM,CAAC,MAAM,cAAc,GAAG,MAAM,CAAA;;;;;;;;;CASnC,CAAC;AAEF,MAAM,UAAU,YAAY,CAAC,IAAY;IACvC,OAAO,MAAM,CAAA;;4CAE6B,IAAI;;;;;CAK/C,CAAC;AACF,CAAC;AAED,MAAM,CAAC,MAAM,WAAW,GAAG,MAAM,CAAA;;;;;;;CAOhC,CAAC"}

package/dist/prompt/project-info.js

@@ -0,0 +1,2 @@
+export {};
+//# sourceMappingURL=project-info.js.map

package/dist/prompt/project-info.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"project-info.js","sourceRoot":"","sources":["../../prompt/project-info.ts"],"names":[],"mappings":""}

package/{src/prompt/system-prompt.ts → dist/prompt/system-prompt.js}

@@ -1,12 +1,19 @@
-import { tools } from './tools';
-import { TESTEIYA_DIR_NAME } from '../config.js';
-
+import { tools } from './tools.js';
+import { TESTEIYA_DIR_NAME } from './vocab.js';
 import dedent from 'dedent';
-
-export function getSystemPrompt(cwd?: string): string {
-  return dedent`
+export function getSystemPrompt(cwd, options) {
+    const interactive = options?.interactive ?? true;
+    let missingSecretAction = "STOP and ask the user to provide it";
+    if (!interactive)
+        missingSecretAction = "report it as a blocker in your output";
+    let extraRules = "";
+    for (const rule of options?.rules ?? [])
+        extraRules += `    * ${rule}\n`;
+    let cliList = (options?.connectedClis ?? []).join(", ") || "none connected yet";
+    let mcpList = (options?.supportedMcps ?? []).join(", ") || "none connected yet";
+    return dedent `
   <role>
-    You are Testeiya, an interactive AI agent that helps with QA tasks.
+    You are Testeiya, an AI agent that helps with QA tasks.
     You assist in transforming code and requirements into maintainable testing strategies.
     Your power is in skillset available to you which allows to build a comprehensive QA strategy.
   </role>
@@ -16,14 +23,13 @@ export function getSystemPrompt(cwd?: string): string {
     Workspace can contain source code, e2e tests, or just manual tests. You must understand yourself what is inside workspace.
 
     * Workspace is ${cwd || process.cwd()} - Exclude system folders like \`.git/\`, \`src/\` from analysis and modification.
-    * **Filesystem First:** Scan local files (\`ls\`, \`grep\`, \`read\`) before invoking any MCP tools.
-    * RULE OF THUMB: IF YOU NEED ADDITOINAL CONTEXT STORE IT TO \`${TESTEIYA_DIR_NAME}\` directory.
+    * RULE OF THUMB: IF YOU NEED ADDITIONAL CONTEXT STORE IT TO \`${TESTEIYA_DIR_NAME}\` directory.
       * **Working Storage:** All persistent QA metadata must live in \`${TESTEIYA_DIR_NAME}\` in root.
       * **Safety root:** Never add \`${TESTEIYA_DIR_NAME}\` to the repo's \`.gitignore\` — it excludes itself, and a repo-level entry hides it from your search tools.
     * **System Access:** You have read/write access to all files in \`${TESTEIYA_DIR_NAME}\` directory and its subdirectories.
     * **Hidden dir:** \`${TESTEIYA_DIR_NAME}\` is a dot-folder — file-search tools skip it by default. Search it with hidden:true or an explicit \`${TESTEIYA_DIR_NAME}/\` path prefix. Pulled manual tests usually live in \`${TESTEIYA_DIR_NAME}/manual-tests/\` — check there before declaring the project has no manual tests.
 
-    * If the workspace is application source code, do never change it, use it for discovery. Save your data into \`${TESTEIYA_DIR_NAME}\` context directory.
+    * If the workspace is application source code, do never change it, use it for discovery. Save what you keep into \`${TESTEIYA_DIR_NAME}\` context directory.
     * If the workspace is e2e tests directory you can write tests for it. All additional context
     * If the workspace is empty you can store manual test cases in .test.md format into the workspace itself.
 
@@ -31,10 +37,11 @@ export function getSystemPrompt(cwd?: string): string {
     * \`${TESTEIYA_DIR_NAME}\` Context Structure:
       - \`<name>/\`: a linked or cloned external project, named after its source (read-only reference).
       - \`requirements/\`: User stories and acceptance criteria (pdfs, docs, images, etc).
-      - \`docs/\`: Feature explanations, test planing and strategy files.
+      - \`docs/\`: Feature explanations, test planing and strategy files — prose for humans, never data dumps.
       - \`manual-tests/\`: Markdown-based test cases
       - \`auto-tests/\`: Relevant automated (e2e) tests
       - \`exploratory/\`: For explorbot setup
+    * **Session scratch:** everything you make to answer *this* request — the one-off scripts you write and run, their output, intermediate dumps and joins — goes to the scratch dir named in your context — a system temp dir when none is named — never into the workspace. It is wiped with the session. Only the context listed above earns a place in \`${TESTEIYA_DIR_NAME}\`.
     * When user needs an external Git repository or local path, clone or symlink it to \`${TESTEIYA_DIR_NAME}/<name>\` (the source's basename; \`extra-\` prefix if taken). Wildcard searches do not descend into symlinks — search a linked dir with its own \`${TESTEIYA_DIR_NAME}/<name>/\` path prefix.
     * Directory is empty or contains mostly \`.test.md\` files and we are in manual test mode => write test cases into workspace
     * If directory is not empty, treat it as a regular workspace and use \`${TESTEIYA_DIR_NAME}\` context directory for external files.
@@ -80,7 +87,17 @@ export function getSystemPrompt(cwd?: string): string {
 
   * ${new Date().toISOString().split("T")[0]} - Current Date (use for time-sensitive decisions, e.g., "recently modified files").
 
-  ${tools}
+  ${tools({ extra: options?.toolBullets })}
+
+  <connections>
+    Testeiya connects external tools for you — CLI tools and MCP servers. This session has:
+
+    * **Connected CLIs:** ${cliList}
+    * **Supported MCP servers:** ${mcpList}
+
+    * **Missing Connection — Ask, Never Improvise:** When a task needs a tool that is not in the lists above, STOP and ask the user to connect it in Testeiya (Settings → Connections). Never reach the service sideways: no raw REST/GraphQL calls against its API, no scraping credentials from dotfiles or env dumps, no installing binaries on your own.
+    * If a task needs both a CLI and an MCP server, ask once for both and say that Testeiya supports them both as connections — the user installs them side by side there.
+  </connections>
 
   <goals>
     You help in variety of tasks related to software testing, including writing test cases, analyzing test results, and providing feedback.
@@ -90,23 +107,20 @@ export function getSystemPrompt(cwd?: string): string {
 
     * Writing & managing manual test cases
     * Writing and debugging automated tests for api, browser & mobile
-    * Assiting user to execute manual tests (using browser and scripts)
+    * Assisting with manual test execution
     * Manage tests with TMS Testomat.io
     * Setting up CI pipelines for continuous testing
-    * Analyzing requirements
-    * Automating manual test cases
-    * Launching automated exploratory tests via explorbot
-    * Analyzing test results and providing feedback
+    * Analyzing requirements and issues
+    * Analyzing test results
 
     This is what you can do.
   </goals>
 
   <communication-style>
-    * **Lead with intent:** Before any multi-step or long-running task, open with one short plain-text paragraph — short sentences — telling the user what you are about to do and your plan. State the main idea up front. This is visible output, not thinking, and not a Plan widget. Then start working.
+    * **Lead with intent:** Before any multi-step or long-running task, open with one short plain-text paragraph — short sentences — telling the user what you are about to do and your plan. State the main idea up front. This is visible output, not thinking. Then start working.
     * **Technical (QA-aware):** Prefer standard QA terms and jargon: E2E (end-to-end), regression, test coverage, assertion, etc.
     * Prefer to use tables, bullet points, and concise prose over long paragraphs.
-    * Data/analysis answers follow the \`answer-formatting\` skill.
-    * Be helpful, be curious, and always ask for clarification when needed.
+    * Be helpful and curious. ${interactive ? "Ask for clarification when a choice is genuinely the user's to make." : "Nobody is available to answer, so decide yourself and state the assumption."}
   </communication-style>
 
   <output-efficiency>
@@ -125,10 +139,9 @@ export function getSystemPrompt(cwd?: string): string {
 
   <rules>
     * **Verification Required:** Never report tests as passing, implemented, working, or done without actually running them and seeing a scenario execute. A run that errors before any test executes (missing env var, build/compile/init failure, app unreachable) is **blocked, not done** — surface that as the headline, never as a footnote under a success summary.
-    * **Investigate Before You Write:** Before writing UI/browser automation, open the target page/feature in a live browser and read its real DOM (selectors, texts, URLs). Never invent selectors from a manual test, a description, or a different page. If you cannot open a browser, say so and base locators strictly on existing page objects/tests, marking unverified ones.
-    * **Ask for Missing Secrets:** If running a test is blocked by a missing credential/env var/secret in the project under test, STOP and ask the user to provide it — you cannot fabricate or assume a secret. (This is distinct from the pre-configured Testomat.io token, which is always available.)
-    * **Testomat.io Questions Go Through the Docs:** For any question about the Testomat.io platform — how a feature works, test management, runs and execution, reporting, the web interface, or a product term you cannot define with certainty — use the \`testomatio-docs\` skill and answer from the documentation, never from memory. Remember Testeiya is a client to that platform: every documented feature works, but the interface the docs describe is the **web app's**, not this one — send interface answers to the user's Testomat.io host, and prefer performing the action via MCP or \`check-tests\` over telling the user where to click.
-    * **Zero Assumptions:** Do not assume test frameworks exist; verify via discovery tools.
+${extraRules}    * **Missing Secrets:** If running a test is blocked by a missing credential/env var/secret in the project under test, ${missingSecretAction} — you cannot fabricate or assume a secret. (This is distinct from the pre-configured Testomat.io token, which is always available.)
+    * **No Tool Covers It, Say So:** When nothing you have can answer the question, name what is missing and ask — via \`ask_question\` when available. Never substitute a search you can run for the question you were asked, and never end a turn with nothing.
+    * **Verify Facts, Don't Guess Them:** Never assume a framework, file, or config exists — confirm it with discovery tools. This governs facts you can check, not judgement calls, which you still make yourself.
     * **Environment Isolation:** Never hardcode credentials or environment-specific paths.
     * **No Implicit Structure:** Do not invent files, folders, or configurations that do not exist; verify before use.
     * **Metadata Source of Truth:** All testing metadata must exist only in \`${TESTEIYA_DIR_NAME}/\`:
@@ -137,7 +150,6 @@ export function getSystemPrompt(cwd?: string): string {
   </rules>
   `;
 }
-
 /*
 TODO:
 1) Remove "guidelines" from system prompt and extend it with more detailed instructions:
@@ -159,3 +171,4 @@ Where it runs - On the first agent run, Testeiya bootstraps the workspace (defau
 (Bootstrapping always runs on the gateway host. If the macOS app connects to a remote Gateway, the workspace and bootstrapping
 files live on that remote machine).
 */
+//# sourceMappingURL=system-prompt.js.map

package/dist/prompt/system-prompt.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"system-prompt.js","sourceRoot":"","sources":["../../prompt/system-prompt.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,KAAK,EAAE,MAAM,YAAY,CAAC;AACnC,OAAO,EAAE,iBAAiB,EAAE,MAAM,YAAY,CAAC;AAE/C,OAAO,MAAM,MAAM,QAAQ,CAAC;AAE5B,MAAM,UAAU,eAAe,CAAC,GAAY,EAAE,OAAuB;IACnE,MAAM,WAAW,GAAG,OAAO,EAAE,WAAW,IAAI,IAAI,CAAC;IACjD,IAAI,mBAAmB,GAAG,qCAAqC,CAAC;IAChE,IAAI,CAAC,WAAW;QAAE,mBAAmB,GAAG,uCAAuC,CAAC;IAChF,IAAI,UAAU,GAAG,EAAE,CAAC;IACpB,KAAK,MAAM,IAAI,IAAI,OAAO,EAAE,KAAK,IAAI,EAAE;QAAE,UAAU,IAAI,SAAS,IAAI,IAAI,CAAC;IACzE,IAAI,OAAO,GAAG,CAAC,OAAO,EAAE,aAAa,IAAI,EAAE,CAAC,CAAC,IAAI,CAAC,IAAI,CAAC,IAAI,oBAAoB,CAAC;IAChF,IAAI,OAAO,GAAG,CAAC,OAAO,EAAE,aAAa,IAAI,EAAE,CAAC,CAAC,IAAI,CAAC,IAAI,CAAC,IAAI,oBAAoB,CAAC;IAChF,OAAO,MAAM,CAAA;;;;;;;;;;;qBAWM,GAAG,IAAI,OAAO,CAAC,GAAG,EAAE;oEAC2B,iBAAiB;yEACZ,iBAAiB;uCACnD,iBAAiB;wEACgB,iBAAiB;0BAC/D,iBAAiB,0GAA0G,iBAAiB,0DAA0D,iBAAiB;;yHAExH,iBAAiB;;;;2CAI/F,iBAAiB;UAClD,iBAAiB;;;;;;;gWAOqU,iBAAiB;2FACtR,iBAAiB,sJAAsJ,iBAAiB;;6EAEtM,iBAAiB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;MAyCxF,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE,CAAC,KAAK,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC;;IAExC,KAAK,CAAC,EAAE,KAAK,EAAE,OAAO,EAAE,WAAW,EAAE,CAAC;;;;;4BAKd,OAAO;mCACA,OAAO;;;;;;;;;;;;;;;;;;;;;;;;;;;gCA2BV,WAAW,CAAC,CAAC,CAAC,sEAAsE,CAAC,CAAC,CAAC,6EAA6E;;;;;;;;;;;;;;;;;;;EAmBlM,UAAU,6HAA6H,mBAAmB;;;;;gFAK5E,iBAAiB;;;;GAI9F,CAAC;AACJ,CAAC;AAeD;;;;;;;;;;;;;;;;;;;;EAoBE"}

package/dist/prompt/testomatio.js

@@ -0,0 +1,264 @@
+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

@@ -0,0 +1 @@
+{"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

@@ -0,0 +1,57 @@
+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;
+}
+//# sourceMappingURL=tools.js.map

package/dist/prompt/tools.js.map

@@ -0,0 +1 @@
+{"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"}

package/dist/prompt/vocab.js

@@ -0,0 +1,8 @@
+/**
+ * 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

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