testeiya 0.4.4 → 0.4.5

package/skills/testomatio/test-management/scan-automation-project/SKILL.md

@@ -1,15 +1,15 @@
 ---
 name: scan-automation-project
-description: Scan project source code to inventory languages, frameworks, and existing tests (manual `*.test.md` and automated test files). Use this skill whenever analyzing a codebase for test planning, detecting test frameworks, or preparing for test automation. Specifically, when the user mentions "scan project", "what tests exist", "analyze codebase", "detect frameworks", "test matrix", or needs a codebase inventory before a QA workflow.
+description: Scan a project and inventory what is available for QA work - project type, languages, frameworks, manual `*.test.md` cases, automated tests and automated references, and how Testomat.io is reachable (token, MCP, project settings). Use this skill whenever analyzing a codebase for test planning, detecting test frameworks, counting tests, or preparing for test automation. Specifically, when the user mentions "scan project", "what tests exist", "how many tests", "analyze codebase", "detect frameworks", "test matrix", or needs an inventory before a QA workflow.
 license: MIT
 metadata:
   author: Testomat.io
-  version: 1.0.0
+  version: 1.1.0
 ---
 
 # Scan Automation Project
 
-Scan project source code and return a QA-focused inventory: languages, frameworks, and existing tests.
+Scan the project and return a QA-focused inventory: project type, languages, frameworks, existing tests, and what Testomat.io access is available.
 
 **Shallow scan only.** No full import resolution, no line-by-line parsing, no reading full test implementations. High-level structure only.
 
@@ -27,26 +27,42 @@ Where is the source code?
 ```
 
 - Wait for the user's reply.
-- If the user gives a Git repo or another folder, clone or symlink it into `.testeiya/code/`. No-op if it is already there.
+- If the user gives a Git repo or another folder, clone or symlink it into `.testeiya/<name>/` (the source's basename; `extra-` prefix if taken). No-op if it is already there.
+
+### The `.testeiya/` folder
+
+All persistent QA metadata lives in `.testeiya/` in the project root.
+
+- `<name>/`: a linked or cloned external project, named after its source. Read-only reference.
+- `requirements/`: user stories and acceptance criteria (pdfs, docs, images).
+- `docs/`: feature explanations, test planning and strategy files. Prose for humans, never data dumps.
+- `manual-tests/`: markdown test cases pulled from Testomat.io.
+- `auto-tests/`: references to the relevant automated (e2e) tests.
+- `exploratory/`: explorbot setup.
+- `project-info.json`: the project's settings as Testomat.io reports them, when cached.
+
+Rules:
+
+- It is a dot-folder. File-search tools skip it by default: search it with hidden:true or an explicit `.testeiya/` path prefix. A linked folder is a symlink; wildcard searches do not descend into it, so search it with its own `.testeiya/<name>/` prefix.
+- It excludes itself from git: when you create `.testeiya/`, also create `.testeiya/.gitignore` containing a single `*`. **Never add `.testeiya/` to the repo's own `.gitignore`**: a repo-level entry hides the folder from search tools, so the next scan reports "no manual tests" while the cases sit right there.
 
 ### Rule for pulled data
 
 **When you need to pull external data** (manual test cases, app code, e2e tests from another repo) into this project:
 
-| This project has | Store pulled data in | Gitignored? |
-| ------------------ | ---------------------- | ----------- |
-| **Source code** (`src/` folder) or **big project** | `.testeiya/…` | **Yes** |
-| **Only test infrastructure** (e2e dirs like `tests/`, `playwright/`, `cypress/` but no `src/`) | `manual-tests/` or `e2e-tests/` | No |
-| **Empty / manual-only** | `manual-tests/` | No |
+| This project has | Store pulled data in |
+| ------------------ | ---------------------- |
+| **Source code** (`src/` folder) or **big project** | `.testeiya/…` |
+| **Only test infrastructure** (e2e dirs like `tests/`, `playwright/`, `cypress/` but no `src/`) | `manual-tests/` or `e2e-tests/` |
+| **Empty / manual-only** | `manual-tests/` |
 
 Detection logic:
 1. Has `src/` folder or is a monorepo? → Use `.testeiya/`
 2. Has e2e test dirs (`tests/`, `playwright/`, `cypress/`, `e2e/`)? → Use tracked folder (`manual-tests/`, `e2e-tests/`)
 3. Otherwise → Default to `manual-tests/`
 
-- Any skill that creates `.testeiya/...` must also add `.testeiya/` to the project's `.gitignore` — but only if it is not there yet. Never add it twice.
 - The rule covers *pulled* data only. Output a skill *produces* and the user wants — a `coverage.*.yml`, new `*.test.md` files — goes in the repo as normal.
-- On a source repo with no manual tests, this skill changes no tracked file: it only creates the gitignored `.testeiya/` directory and, if needed, adds one line to `.gitignore`.
+- On a source repo with no manual tests, this skill changes no tracked file: it only creates the self-ignored `.testeiya/` directory.
 - **Only touch `.testeiya/` and tracked folders — never pollute the repo with cache in a wrong location.**
 
 ## Step 2: Project Analysis
@@ -59,11 +75,15 @@ Include:
 
 Exclude:
 - Dependencies, build output, coverage, reports, caches, config, lock, and environment files.
-- Paths ignored by `.gitignore` — but **not** `.testeiya/code/`. In a manual-tests repo the app code lives there; scan it as source.
+- Paths ignored by `.gitignore` — but **not** `.testeiya/<name>/`. In a manual-tests repo the app code lives there; scan it as source.
 - Testeiya internal files (e.g. `session-factory.ts`, `system-prompt.ts`).
 - **If in doubt**, exclude.
 
 From the file list:
+- Classify the **project type**, one of:
+  - `source`: application source code. Never change it; use it for discovery.
+  - `e2e`: a test automation project (e2e dirs, a test framework config, little or no app source). You can write tests for it.
+  - `manual`: empty, or mostly `*.test.md` files. Test cases go into the project itself.
 - Detect languages and frameworks. Collect one `frameworks` list with ALL application and testing frameworks.
 - Extract the project name from a project config file (`package.json`, `Cargo.toml`, `pom.xml`, ...); fall back to the root directory name.
 - Rate complexity by source file count:
@@ -75,34 +95,81 @@ From the file list:
 | 151-500    | `large`      |
 | 500+       | `very-large` |
 
-## Step 3: Test Inventory (optional)
+## Step 3: Test Inventory
 
 Detect existing tests, automated and manual. Stay shallow.
 
-Automated tests:
-- Detect frameworks via config files (`jest.config.*`, `playwright.config.*`, `vitest.config.*`, `pytest.ini`, `pom.xml`, ...), project dependencies, and test file patterns (`*.test.*`, `*.spec.*`, `*_test.*`).
-- For each framework: identify its test file pattern and count matching files.
+### Manual tests
 
-Manual tests:
-- Find all `.test.md` files and parse test titles. `find .` also looks inside `.testeiya/manual-tests/`, so a re-run after a pull finds the cached cases instead of reporting "no manual tests":
+A `*.test.md` file is a suite. Each test inside it is a `<!-- test ... -->` block followed by an `#`/`##` heading (the title). The block's `type:` field says which kind of test it is:
+
+- `type: manual`: a manual test case, authored and maintained here as markdown.
+- `type: automated`: a **reference** to an automated test (see below).
+- No `type:` line at all: treat as manual. This is common, so never count manual tests by grepping for `type: manual`; it silently undercounts.
+
+Know the counts before you answer anything about project scope, coverage or progress. Read them straight from the files; this mirrors how Testomat.io parses them. `find .` also looks inside `.testeiya/manual-tests/`, so a re-run after a pull finds the cached cases instead of reporting "no manual tests":
 
 ```bash
+# one line per suite or test: SUITE <title>, or <type> <title>
 find . -name "*.test.md" -exec awk '
-  /^<!-- test/   { in_block=1; kind="TEST";  next }
   /^<!-- suite/  { in_block=1; kind="SUITE"; next }
+  /^<!-- test/   { in_block=1; kind="manual"; next }
+  in_block && /^type:[[:space:]]*automated/ { kind="automated"; next }
   in_block && /^-->/ { in_block=0; expect=1; next }
   expect && /^#+[[:space:]]+/ {
     title=$0; sub(/^#+[[:space:]]+/, "", title)
     if (kind == "SUITE") printf "SUITE: %s\n", title
-    else             printf "|- %s\n",     title
+    else                 printf "|- [%s] %s\n", kind, title
     expect=0
   }
 ' {} +
 ```
 
+Pipe the output into `grep -c '\[manual\]'` or `grep -c '\[automated\]'` to count one kind.
+
 - If the only `.test.md` files are under `.testeiya/manual-tests/`, say so in the inventory: they came from Testomat.io, not from this repo.
+- A source checkout with no `*.test.md` files has nothing to count. Say so; do not estimate.
+
+### Automated tests
+
+- Detect frameworks via config files (`jest.config.*`, `playwright.config.*`, `vitest.config.*`, `pytest.ini`, `pom.xml`, ...), project dependencies, and test file patterns (`*.test.*`, `*.spec.*`, `*_test.*`).
+- For each framework: identify its test file pattern and count matching files.
+- Unit and integration tests are inventory, not QA scope: note them, but flag e2e and acceptance suites as the ones QA work targets.
+
+### Automated references
+
+`type: automated` entries in `*.test.md` are references, not runnable code. They arrive via `check-tests pull --export-automated`, which exports the automated tests Testomat.io knows about as markdown. The real implementation lives in a **different repository**, the automation project, which is usually not this one.
+
+- Never claim you ran an automated test because you found its reference here. Nothing here executes.
+- Do not edit a reference's markdown to change the test's behaviour. The code is elsewhere, the edit gets overwritten on the next pull, and pushing it can clobber TMS data. Locate the real test in the automation repo instead.
+- To actually run them, use a CI profile (Step 4): if the project has one configured, a run can be triggered through Testomat.io.
+- They are still valuable context: they tell you what is already automated versus what is still manual, which is what coverage gaps and automation candidates need.
+
+## Step 4: Testomat.io Access
+
+Record how Testomat.io is reachable from this session. Check, do not assume:
+
+- **Token:** `TESTOMATIO` in the environment (or in `.env`). With it, `npx check-tests` can pull and push test cases and the REST API answers under `$TESTOMATIO_URL/api/v2`.
+- **MCP:** Testomat.io MCP tools are present (tools prefixed `testomatio-`, direct tools such as `tests_list` and `runs_list`, or one `mcp` tool that searches and calls operations). MCP needs `TESTOMATIO_PROJECT_ID` as well as the token; a token alone identifies no project. Setup lives in the `testomatio-mcp` skill.
+- **Project settings:** `.testeiya/project-info.json`, when present: framework, language, environments, labels, tags, and **CI profiles** (runs can be triggered through them).
 
-## Step 4: Output
+Never ask the user for the Testomat.io token when one is configured. Secrets the app under test needs are a different thing; a missing one blocks a run.
+
+### Which source answers what
+
+| Question is about | First action |
+|---|---|
+| Test content: steps, gherkin, description, file path, tags | `read`, `find`, `grep` in the project |
+| Suite hierarchy, structure, which files exist | `ls`, `find` |
+| Individual test metadata: priority, status flag, labels | the files; if missing, get the test from Testomat.io |
+| Runs, testruns, plans, labels, issues, analytics | Testomat.io (MCP or REST); these are not files |
+| Creating or updating tests or suites | edit the markdown file, then `npx check-tests push` (see `sync-test-cases-with-tms`) |
+| Launching an automated or mixed run on CI | `npx -y @testomatio/reporter@latest run --remote <profile>`; raise an error if no CI profile is configured |
+| Running automated tests locally | the local test runner with the Testomat.io reporter attached |
+
+Statuses and counts in Testomat.io are live. Runs change them at any time, so fresh query results supersede numbers from earlier in the conversation.
+
+## Step 5: Output
 
 Return one structured markdown result directly. **Do NOT save to a file.**
 
@@ -111,14 +178,16 @@ Return one structured markdown result directly. **Do NOT save to a file.**
 
 - **Project Name:** acme-web-app
 - **Description:** A React-based customer dashboard with an Express API.
+- **Project Type:** source
 - **Languages:** TypeScript, SQL
 - **Frameworks:** React, Express, Jest, Playwright
 - **Complexity:** small (12 files)
 
 ## Test Inventory
 
-- **Automated Tests:** 10 files
-- **Manual Tests:** 37 cases
+- **Automated Tests:** 10 files (Playwright)
+- **Manual Tests:** 37 cases (`.testeiya/manual-tests/`, pulled from Testomat.io)
+- **Automated References:** 12 (implementation lives in another repository)
 
 ### Manual Tests (20 of 37 shown)
 
@@ -133,17 +202,25 @@ Return one structured markdown result directly. **Do NOT save to a file.**
 
 - home.page.spec.ts
 ...
+
+## Testomat.io
+
+- **Token:** set (`TESTOMATIO`)
+- **MCP:** available (`testomatio-*` tools)
+- **Project settings:** `.testeiya/project-info.json`, framework playwright, CI profiles: "e2e" (github)
 ```
 
 Field rules:
 - **Description:** 1-2 sentences based only on detected source code and folder structure (include the domain area if that makes sense).
+- **Project Type:** one of `source` | `e2e` | `manual`.
 - **Complexity:** one of `small` | `moderate` | `large` | `very-large`, plus the file count.
-- **Manual Tests:** preserve hierarchy as plain strings — SUITE items as parent bullets, test titles (`|-`) as nested children.
+- **Manual Tests:** preserve hierarchy as plain strings — SUITE items as parent bullets, test titles (`|-`) as nested children. Say where they live.
 - **Automated Tests:** list of detected test files.
-- All values must come from observable files. Do NOT guess missing data or add fields not shown above.
+- **Testomat.io:** one line per access path, `available`/`not available`; omit the section only when none is present, and then say the project is not connected.
+- All values must come from observable files and tools. Do NOT guess missing data or add fields not shown above.
 
 Sections:
-- If Step 3 was skipped or found no tests, omit `## Test Inventory` and note that the project contains no tests; the `# Project Overview` section is still useful for next steps.
+- If Step 3 found no tests, omit `## Test Inventory` and note that the project contains no tests; the `# Project Overview` section is still useful for next steps.
 - If one test type is absent, note it with a blockquote, e.g. ``> No manual tests (`.test.md`) found in the project.``
 
 Test listing truncation:

package/dist/prompt/context.js

@@ -1,87 +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, folders = []) {
-    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, folders = []) {
-    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, folders) {
-    const lines = [];
-    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) {
-    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) {
-    const idx = rel.lastIndexOf("/");
-    if (idx < 0)
-        return "";
-    return rel.slice(0, idx);
-}
-function describeEntry(e) {
-    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})`;
-}
-//# sourceMappingURL=context.js.map

package/dist/prompt/context.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"context.js","sourceRoot":"","sources":["../../prompt/context.ts"],"names":[],"mappings":"AAAA,OAAO,MAAM,MAAM,QAAQ,CAAC;AAC5B,OAAO,EAAE,iBAAiB,EAAE,MAAM,YAAY,CAAC;AAE/C,4EAA4E;AAC5E,MAAM,UAAU,oBAAoB,CAClC,OAAuB,EACvB,UAA2B,EAAE;IAE7B,IAAI,OAAO,CAAC,MAAM,KAAK,CAAC,IAAI,OAAO,CAAC,MAAM,KAAK,CAAC;QAAE,OAAO,EAAE,CAAC;IAC5D,OAAO,MAAM,CAAA;;;;IAIX,YAAY,CAAC,OAAO,EAAE,OAAO,CAAC;;0CAEQ,iBAAiB,kJAAkJ,iBAAiB,sTAAsT,iBAAiB,kCAAkC,iBAAiB,yBAAyB,iBAAiB;;GAE/nB,CAAC;AACJ,CAAC;AAED,2FAA2F;AAC3F,MAAM,UAAU,mBAAmB,CACjC,OAAuB,EACvB,UAA2B,EAAE;IAE7B,IAAI,OAAO,CAAC,MAAM,KAAK,CAAC,IAAI,OAAO,CAAC,MAAM,KAAK,CAAC,EAAE,CAAC;QACjD,OAAO,MAAM,CAAA;;;;KAIZ,CAAC;IACJ,CAAC;IACD,OAAO,MAAM,CAAA;;;;IAIX,YAAY,CAAC,OAAO,EAAE,OAAO,CAAC;;kGAEgE,iBAAiB;;GAEhH,CAAC;AACJ,CAAC;AAED,SAAS,YAAY,CAAC,OAAuB,EAAE,OAAwB;IACrE,MAAM,KAAK,GAAa,EAAE,CAAC;IAC3B,MAAM,OAAO,GAAG,IAAI,GAAG,CAAC,OAAO,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,SAAS,CAAC,CAAC,CAAC,IAAI,CAAC,CAAC,CAAC,CAAC;IAC/D,KAAK,MAAM,CAAC,IAAI,OAAO,EAAE,CAAC;QACxB,IAAI,OAAO,CAAC,GAAG,CAAC,CAAC,CAAC,IAAI,CAAC;YAAE,SAAS;QAClC,KAAK,CAAC,IAAI,CAAC,OAAO,CAAC,CAAC,IAAI,SAAS,aAAa,CAAC,CAAC,CAAC,IAAI,CAAC,EAAE,CAAC,CAAC;IAC5D,CAAC;IACD,KAAK,MAAM,CAAC,IAAI,OAAO;QAAE,KAAK,CAAC,IAAI,CAAC,KAAK,aAAa,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC;IAC7D,OAAO,KAAK,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;AAC1B,CAAC;AAED,SAAS,aAAa,CAAC,IAAY;IACjC,IAAI,IAAI,KAAK,cAAc,EAAE,CAAC;QAC5B,OAAO,yGAAyG,CAAC;IACnH,CAAC;IACD,IAAI,IAAI,KAAK,MAAM;QAAE,OAAO,iCAAiC,CAAC;IAC9D,IAAI,IAAI,KAAK,cAAc;QAAE,OAAO,wBAAwB,CAAC;IAC7D,IAAI,IAAI,KAAK,MAAM;QAAE,OAAO,sCAAsC,CAAC;IACnE,IAAI,IAAI,KAAK,YAAY;QAAE,OAAO,2BAA2B,CAAC;IAC9D,OAAO,2BAA2B,CAAC;AACrC,CAAC;AAED,SAAS,SAAS,CAAC,GAAW;IAC5B,MAAM,GAAG,GAAG,GAAG,CAAC,WAAW,CAAC,GAAG,CAAC,CAAC;IACjC,IAAI,GAAG,GAAG,CAAC;QAAE,OAAO,EAAE,CAAC;IACvB,OAAO,GAAG,CAAC,KAAK,CAAC,CAAC,EAAE,GAAG,CAAC,CAAC;AAC3B,CAAC;AAED,SAAS,aAAa,CAAC,CAAe;IACpC,MAAM,IAAI,GAAG,CAAC,CAAC,OAAO,EAAE,KAAK,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,IAAI,EAAE,CAAC;IAC5C,0EAA0E;IAC1E,+EAA+E;IAC/E,IAAI,CAAC,CAAC,CAAC,IAAI,CAAC,UAAU,CAAC,GAAG,iBAAiB,GAAG,CAAC,EAAE,CAAC;QAChD,IAAI,IAAI,GAAG,QAAQ,CAAC;QACpB,IAAI,CAAC,CAAC,IAAI,KAAK,MAAM;YAAE,IAAI,GAAG,MAAM,CAAC;QACrC,OAAO,KAAK,CAAC,CAAC,IAAI,kBAAkB,IAAI,2BAA2B,IAAI,GAAG,CAAC;IAC7E,CAAC;IACD,IAAI,IAAI,GAAG,EAAE,CAAC;IACd,IAAI,CAAC,CAAC,MAAM,IAAI,CAAC,CAAC,MAAM,KAAK,CAAC,CAAC,IAAI;QAAE,IAAI,GAAG,SAAS,CAAC,CAAC,MAAM,EAAE,CAAC;IAChE,IAAI,CAAC,CAAC,IAAI,KAAK,MAAM;QAAE,OAAO,KAAK,CAAC,CAAC,IAAI,sBAAsB,IAAI,KAAK,IAAI,GAAG,CAAC;IAChF,IAAI,CAAC,CAAC,IAAI,KAAK,QAAQ;QAAE,OAAO,KAAK,CAAC,CAAC,IAAI,oBAAoB,IAAI,KAAK,IAAI,GAAG,CAAC;IAChF,OAAO,KAAK,CAAC,CAAC,IAAI,gBAAgB,IAAI,KAAK,IAAI,GAAG,CAAC;AACrD,CAAC"}

package/dist/prompt/index.js

@@ -1,60 +0,0 @@
-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,
-            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");
-}
-//# sourceMappingURL=index.js.map

package/dist/prompt/index.js.map

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

@@ -1,30 +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) {
-    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

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

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

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

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