testeiya 0.2.0 → 0.3.1-0.1

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Testomat.io
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -1,212 +1,384 @@
+<p align="center">
+  <img src="https://raw.githubusercontent.com/testomatio/testeiya-app/main/assets/testeiya-cli-logo.png" alt="Testeiya" width="220">
+</p>
+
 # Testeiya
 
-AI-powered testing agent for QA teams, built on top of the [oh-my-pi](https://github.com/can1357/oh-my-pi) coding-agent SDK (a fork of [Pi](https://github.com/badlogic/pi-mono) by Mario Zechner).
+[![npm](https://img.shields.io/npm/v/testeiya)](https://www.npmjs.com/package/testeiya)
+[![licence](https://img.shields.io/npm/l/testeiya)](LICENSE)
+
+An agent, app, and the goddess of testing.
+
+Testeiya is an autonomous QA agent. It reacts to triggers — a pull request, a new
+issue, a failed test run, a deploy — runs exactly one analysis, and delivers its
+verdict where your team works: a PR comment, a markdown report, or a Testomat.io
+project. There is no interactive mode and no human in the loop. That is the point:
+you wire it into CI once, and every event that should get QA thinking gets it.
+
+It ships as a desktop app, a web app, and the command-line agent in this repository.
+
+| Folder | What it is |
+|---|---|
+| `prompt/` | System-prompt fragments: the agent's role, rules, tool guidance, Testomat.io operating rules, and the report contract |
+| `skills/` | The manifest of skills the agent can invoke. Every folder is fetched from its own upstream repository |
+| `src/` | The `testeiya` command-line agent (Node) |
+
+The desktop and web harness is not open source. That covers the servers, session management, sync, and UI.
 
-## About
+## Install
 
-Testeiya is an interactive terminal agent that helps developers analyze test suites, find coverage gaps, and plan testing strategies. It reads your codebase aggressively while keeping write operations locked down, so you can safely point it at any project.
+Requires Node 22.19 or newer, an LLM provider key, and a model.
 
-It ships with [Testomat.io](https://testomat.io) skills for test case management and connects to any OpenAI-compatible API (default: [OpenRouter](https://openrouter.ai)).
+```bash
+npx testeiya doctor
+```
 
-## Features
+`doctor` reports which key won, which skills loaded, and whether Testomat.io is reachable — without spending a token.
 
-- QA-focused system prompt tuned for test analysis
-- Read-permissive / write-restricted permission model
-- Safe bash commands (git log, cat, grep...) auto-allowed; destructive commands blocked
-- Testomat.io skills: test generation, duplicate detection, test improvement, reporter setup
-- Markdown-rendered output in terminal
-- Multi-line paste support
-- Configurable LLM provider and model (OpenRouter by default; any OpenAI-compatible endpoint)
+The key comes from the environment (`OPENROUTER_API_KEY`, `ANTHROPIC_API_KEY`,
+`OPENAI_API_KEY`, `GEMINI_API_KEY`), from `~/.testeiya/.env`, or from
+`~/.testeiya/auth.json`. That last file is the one the desktop app's Settings
+dialog writes, so configuring it once covers both.
 
-## Installation
+There is no default model. Name one with `--model <provider>/<id>` or
+`TESTEIYA_MODEL`. CI usually has neither set, so a run that resolves no model
+exits `2` rather than picking one for you.
 
 ```bash
-npm install -g testeiya    # requires Bun (https://bun.sh) on your PATH
-testeiya
+export TESTEIYA_MODEL=openrouter/anthropic/claude-sonnet-5
+testeiya models anthropic   # list what your key can reach
 ```
 
-Or run from source. This package lives in the [`cli/`](https://github.com/testomatio/testeiya-app/tree/main/cli) directory of the Testeiya monorepo:
+## How it runs
 
 ```bash
-git clone git@github.com:testomatio/testeiya-app.git
-cd testeiya-app/cli
-bun install
-bun src/cli.ts
+testeiya task "<task>"     # run one task, deliver a report, exit
+testeiya ask "<question>"  # answer a question, no report
+testeiya skills            # list the skills bundled with this package
+testeiya sessions          # list saved sessions for this folder
 ```
 
-### Requirements
+The agent runs one task and exits. Progress goes to stderr, so a run drops into CI as-is:
 
-- [Bun](https://bun.sh) — the CLI runs under Bun (its `testeiya` bin uses a `#!/usr/bin/env bun` shebang and runs the TypeScript directly)
-- An API key for whatever you set as `provider.name` in config (default is OpenRouter; see [API keys](#api-keys) below)
+| Exit code | Meaning |
+|---|---|
+| `0` | pass, or a positive verdict from the agent |
+| `1` | failed run, or a negative verdict — findings that need a human |
+| `2` | bad usage |
+| `130` | interrupted |
 
-## Running in Container (Optional)
+Pass `--exit-zero` when a negative verdict must not fail the job. A broken run
+still exits `1`, bad usage still exits `2`, and the verdict is still in the
+report and in the run envelope for anything that wants to gate on it.
 
-Instead of installing locally, you can run Testeiya in Docker. Requires [Docker](https://docker.com) to be installed.
+A task can come from stdin too:
 
 ```bash
-# Build the container
-make build
+cat issue-42.md | testeiya task --output report.md
+```
 
-# Configure environment (copy example and edit)
-cp .env.example .env
-# Edit .env with your API keys
+Every command takes `--json` for machine-readable output of the run envelope
+(verdict, reason, tokens, session id). `testeiya --help` lists all options;
+`testeiya help` is the full guide.
 
-# Run the container
-make run
+## Scenarios
 
-# Stop the container
-make stop
+Each scenario below is a single unattended run. Nobody answers questions; the
+agent reads what the trigger gives it and acts on its own judgement. If its
+verdict is negative, the job fails — that failure *is* the signal.
 
-# Clean up containers
-make clean
+### Grill a pull request
+
+Every PR gets a QA review before merge. The agent loads the branch's diff,
+analyzes it through the `qa-thinking` skill — edge cases, negative flows,
+abuses, data-consistency risks — and posts the findings as a PR comment:
+
+```bash
+git fetch origin "$PR_BRANCH"
+git checkout "$PR_BRANCH"
+testeiya task "Review this pull request as a QA engineer. What could go wrong?" \
+  --output gh:pr-comment --output review.json
 ```
 
-The container mounts `./src` to `/app/src`, so you can edit code locally and run it inside the container.
+Exit code `1` means the agent found real risk, so you can gate the merge on it.
 
-### MCP (Testomat.io Integration)
+### Write test cases from a pull request
 
-Testeiya includes MCP server for Testomat.io. To enable:
+Same trigger, different deliverable: the `qa-write-test-cases` skill turns the
+change into test cases in Testomat.io markdown format, written as a build
+artifact ready to commit or import:
 
-1. Copy `.env.example` to `.env`
-2. Add your Testomat.io credentials:
+```bash
+testeiya task "Create test cases covering the changes in this pull request" \
+  --output testcases/
+```
+
+With `TESTOMATIO` and the project id set, add
+`sync them to Testomat.io` to the task and they land straight in the TMS via
+`sync-test-cases-with-tms`.
+
+### Create test cases from a new issue
+
+A requirements text arrives from the issue tracker — piped in, no human
+summarizing it first. The agent writes a checklist and test cases from it:
 
 ```bash
-# In .env file
-OPENROUTER_API_KEY=sk-or-your-key
-TESTOMATIO_PROJECT_TOKEN=tstmt_xxx
-TESTOMATIO_PROJECT_ID=your-project-id
-TESTOMATIO_BASE_URL=https://app.testomat.io # or any anoher one
+gh issue view 57 --json title,body -q '.title + "\n\n" + .body' \
+| testeiya task --output testcases/issue-57.md
 ```
 
-3. Run `make run` - MCP will auto-connect
+### Explore a deployed app with Explorbot
 
-## Usage
+After a deploy, point [Explorbot](https://github.com/testomatio/explorbot) — the
+autonomous browser-testing CLI the agent drives through the `explorbot-*`
+skills — at the staging URL. It researches, plans, and tests the live app in
+its own browser, then reports what broke:
 
 ```bash
-export OPENROUTER_API_KEY=sk-or-your-key-here
-bun src/cli.ts
+testeiya task "Run explorbot against https://staging.example.com, max 10 tests, report failures" \
+  --output explorbot-report.md
 ```
 
-Or build and run with Node:
+### Repair failing tests after a red build
+
+On a failed CodeceptJS run, the `ci-fix-tests` skill attempts safe fixes only —
+locator drift, missing waits — reruns just the failing scenarios, rolls back any
+edit that did not help, and always writes `output/ci-fix.md` for the next job:
 
 ```bash
-npm run build
-node dist/cli.js
+testeiya task "Fix the failed CodeceptJS tests using ci-fix-tests. No refactors." \
+  --no-session
 ```
 
-You'll see:
+### Audit the test suite on a schedule
 
+Nightly, the agent walks the Testomat.io project and reports gaps — suites with
+no tests, cases gone stale against the current code, coverage holes:
+
+```bash
+TESTOMATIO=tstmt_xxx testeiya task \
+  "Audit this project: which suites have no automated tests, and which manual cases look automatable?" \
+  --output audits/$(date +%F).md
 ```
-  Model: openrouter/anthropic/claude-sonnet-4
-  Skills: analyze-tests, find-duplicate-cases, generate-test-cases, ...
 
-  Testeiya - AI Testing Agent
+## CI setup
+
+Testeiya needs three things in any CI system: a provider key, a model name, and
+the checkout of whatever the task reads. Everything else is standard.
+
+### GitHub Actions
+
+GitHub runners ship the [GitHub CLI](https://cli.github.com), so posting back to
+the PR is one flag. `GITHUB_TOKEN` authenticates it; keep the LLM key in
+repository secrets.
+
+```yaml
+name: qa-review
+on:
+  pull_request:
+    types: [opened, synchronize]
+
+permissions:
+  pull-requests: write
+  contents: read
+
+jobs:
+  grill:
+    runs-on: ubuntu-latest
+    env:
+      GH_TOKEN: ${{ github.token }}
+      OPENROUTER_API_KEY: ${{ secrets.OPENROUTER_API_KEY }}
+      TESTEIYA_MODEL: openrouter/anthropic/claude-sonnet-5
+      # optional, for scenarios that touch Testomat.io
+      TESTOMATIO: ${{ secrets.TESTOMATIO }}
+      TESTOMATIO_PROJECT_ID: my-project
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+      - uses: actions/setup-node@v4
+        with:
+          node-version: 22
+      - run: npx testeiya@latest doctor
+      - run: |
+          npx testeiya@latest task \
+            "Review this pull request as a QA engineer. What could go wrong?" \
+            --output gh:pr-comment --output review.json
+      - uses: actions/upload-artifact@v4
+        if: always()
+        with:
+          name: review
+          path: review.json
+```
 
-  What can I do for you?
+The same shape works for the other scenarios: trigger on `issues` and pipe the
+body in for test-case generation, or run on a `schedule` for the nightly audit.
+
+### GitLab CI
+
+GitLab runners do not ship `gh`, so the report goes to job artifacts — visible
+in the merge request pipeline page. Exit code `1` fails the job and blocks the
+merge when you mark it required.
+
+```yaml
+qa-review:
+  image: node:22
+  rules:
+    - if: $CI_PIPELINE_SOURCE == "merge_request_event"
+  variables:
+    TESTEIYA_MODEL: openrouter/anthropic/claude-sonnet-5
+    TESTOMATIO_PROJECT_ID: my-project
+  script:
+    - git fetch origin $CI_MERGE_REQUEST_TARGET_BRANCH_NAME
+    - npx testeiya@latest doctor
+    - npx testeiya@latest task
+        "Review this merge request as a QA engineer. What could go wrong?"
+        --output review/report.md --output review/envelope.json
+  artifacts:
+    when: always
+    paths:
+      - review/
+  parallel:
+    # secrets go to Settings > CI/CD > Variables:
+    #   OPENROUTER_API_KEY (masked), TESTOMATIO (masked, protected)
 ```
 
-Type a request like:
+For posting back to the merge request, hand the envelope's report to GitLab's
+API in a follow-up step, or install `gh` plus a token mirror if the project is
+also on GitHub.
 
-- "Analyze the test suite in this project"
-- "Find untested code paths in src/controllers"
-- "Generate test cases for the auth module"
+### Anywhere else
 
-Paste multi-line text (API docs, specs, requirements) directly into the prompt.
+Any scheduler that can run a container works — the contract is just stdin,
+stdout, and an exit code:
+
+```bash
+echo "Audit the checkout suite for gaps" | testeiya task --output audit.md
+case $? in
+  0) echo "clean" ;;
+  1) echo "findings need review" ;;
+esac
+```
 
-## Configuration
+## Where the report goes
 
-Edit `testeiya.config.json` in the project root:
+`--output` names a destination and can repeat. Without one the report goes to stdout.
 
-```json
-{
-  "provider": {
-    "name": "openrouter",
-    "baseUrl": "https://openrouter.ai/api/v1",
-    "model": "anthropic/claude-sonnet-4",
-    "contextWindow": 200000,
-    "maxTokens": 16384
-  },
-  "permissions": {
-    "autoAllowRead": true,
-    "blockWrites": true,
-    "blockBash": true
-  }
-}
+```bash
+testeiya task "<task>" --output report.md --output run.json --output gh:pr-comment
 ```
 
-- **provider.model** - Any model available on OpenRouter (e.g. `anthropic/claude-sonnet-4`, `openai/gpt-4o`, `google/gemini-2.5-pro`)
-- **permissions.blockWrites** - When `true`, edit/write tools are blocked
-- **permissions.blockBash** - When `true`, only read-only bash commands are allowed
+| Destination | What happens |
+|---|---|
+| `report.md` | the agent writes the report there |
+| `run.json` | the run envelope: verdict, reason, report, tokens, session id |
+| `gh:pr-comment` | posted on this branch's pull request |
+| `gh:pr#123` | posted on that pull request |
+
+Posting uses the GitHub CLI and resolves the PR number from `GITHUB_EVENT_PATH`,
+`GITHUB_REF`, or `gh pr view` — so inside Actions it just works. Every
+destination is checked before the run starts, so a missing `gh` costs no tokens.
 
-Config is also loaded from `~/.testeiya/config.json` as a fallback.
+`--footer "<text>"` adds a line under a posted comment, and nowhere else. It is
+what turns a report into a conversation: tell the reader how to answer, and let
+the workflow feed their reply back into the same session.
 
-### API keys
+```bash
+testeiya task "Review this pull request" \
+  --output gh:pr-comment \
+  --footer "> You can reply to this comment by typing /testeiya"
+```
 
-Read the API key from `process.env.<PROVIDER_NAME>_API_KEY`, where `<PROVIDER_NAME>` is your `provider.name` (uppercase) from config (e.g. `openrouter` in `testeiya.config.json`).
+## Sessions
 
-Example: if `provider.name` is `openrouter`, read the API key from `process.env.OPENROUTER_API_KEY`.
+Runs are saved under `~/.testeiya`, so a follow-up picks up where the last one
+stopped. A resumed run reuses its session's model.
 
-| `provider.name` | Environment variable   |
-| --------------- | ---------------------- |
-| `openrouter`    | `OPENROUTER_API_KEY`   |
-| `openai`        | `OPENAI_API_KEY`       |
-| `anthropic`     | `ANTHROPIC_API_KEY`    |
-| `groq`          | `GROQ_API_KEY`         |
+```bash
+testeiya task "Review the checkout suite" --name checkout-review --output report.md
+testeiya task "Now write the missing cases" -c
+testeiya sessions
+testeiya task "<task>" --resume <id>
+```
 
-Or set any environment variable name depending of provider name.
+Pass `--name` to label a session and `--no-session` to save nothing.
 
-## Skills
+In CI, `--session <label>` is the one to reach for: it continues the session
+with that label, and starts it the first time, so a job that runs again and
+again needs no "does it exist yet" branch. Give each thread its own label, and
+carry `~/.testeiya` between rounds with the runner's cache. `--no-session` keeps
+runners stateless when continuity is not wanted.
 
-Testeiya loads skills from [@testomatio/skills](https://github.com/testomatio/skills) plus a built-in `analyze-tests` skill:
+```bash
+testeiya task "Review the new commits" --session "pr-42" --output gh:pr-comment
+```
 
-| Skill                | Purpose                                  |
-| -------------------- | ---------------------------------------- |
-| analyze-tests        | Analyze test coverage, quality, and gaps |
-| generate-test-cases  | Create test cases from specs or code     |
-| find-duplicate-cases | Locate duplicate tests                   |
-| improve-test-cases   | Enhance existing test quality            |
-| reporter-setup       | Configure test reporters                 |
-| sync-cases           | Synchronize test cases with Testomat.io  |
+## Testomat.io
 
-Update skills to latest:
+Set `TESTOMATIO` to a project API key. The agent can then read and write that
+project's tests, suites, runs and plans through `check-tests` and the REST API.
 
 ```bash
-npm update @testomatio/skills
+TESTOMATIO=tstmt_xxx testeiya task --project my-project "Which suites have no tests?"
 ```
 
-## Architecture
+Add the project id and the agent also gets the Testomat.io MCP tools. The id
+comes from `--project` or from `TESTOMATIO_PROJECT_ID`; the MCP server needs it,
+because a token alone does not say which project to talk to. `TESTOMATIO_URL`
+points at a self-hosted instance.
 
-Built on top of the [oh-my-pi coding-agent SDK](https://github.com/can1357/oh-my-pi) (a fork of [Pi](https://github.com/badlogic/pi-mono)):
+## Skills
 
-- **`@oh-my-pi/pi-coding-agent`** - Agent session, tools (read/write/bash/grep/find), extensions
-- **`@oh-my-pi/pi-ai`** - Multi-provider LLM abstraction
-- **`@oh-my-pi/pi-tui`** - Markdown rendering
+A skill is a folder with a `SKILL.md`. The agent loads them all and invokes the
+ones a task calls for — you never pick a skill explicitly, the task phrasing
+does.
 
-```
-src/
-  cli.ts              # Entry point
-  main.ts             # Bootstrap: config, auth, model, skills, session
-  config.ts           # Load testeiya.config.json
-  system-prompt.ts    # QA/testing system prompt
-  permissions.ts      # Read-allow / write-block permission gate
-  repl.ts             # Interactive REPL with markdown + paste support
-  skills/
-    analyze-tests.ts  # Built-in test analysis skill
+The set is vendored from upstream repositories and moves with every release, so
+ask your own install rather than a list in a README:
+
+```bash
+testeiya skills             # every bundled skill: name and what it is for
+testeiya skills playwright  # filter by name, category or description
+testeiya skills --json      # [{name, group, description}]
 ```
 
-## Development
+Categories today: QA process, test management, test automation, Explorbot,
+Playwright, CodeceptJS.
 
-```bash
-# Run directly (no build needed)
-bun src/cli.ts
+Sources are declared in `skills/skills.yaml` and pinned in
+`skills/skills.lock.json`. The vendored folders are deliberately not committed —
+they belong to their authors, under their own licences. A clone has the manifest
+and nothing else; `node scripts/vendor-skills.js` fills the tree. Every release
+runs it, so the published `testeiya` package ships each skill as current on
+release day.
 
-# Type-check
-npx tsc --noEmit
+`skillsOverride` in `src/session.ts` keeps only what is found under that tree,
+so an arbitrary clone cannot hand the model its own skills. To add yours, point
+`additionalSkillPaths` at your folder. [EXTENDING.md](EXTENDING.md) covers both hooks.
 
-# Build for Node
-npm run build
-```
+To propose a new source, add its line to `skills/skills.yaml`. See [CONTRIBUTING.md](CONTRIBUTING.md).
+
+## Building your own agent
+
+The CLI is a thin composition over [pi](https://pi.dev): about 1,500 lines wiring
+the SDK to the prompt and skills here. A fork can add pi extensions and custom
+tools, or swap the one-shot run loop for pi's full interactive TUI.
+[EXTENDING.md](EXTENDING.md) walks through both.
+
+## Contributing
+
+Prompt wording is exactly what an outside contributor can improve, and a change
+to it changes how the agent behaves for everyone. Read
+[CONTRIBUTING.md](CONTRIBUTING.md) first. It covers what belongs here and what
+belongs upstream, in the repository that owns a given skill.
+
+## Issues
+
+This repository is also the public issue tracker for both surfaces:
+
+- Testeiya Desktop app, the packaged desktop application
+- Testeiya CLI, the command-line agent in `src/`
 
-## License
+## Licence
 
-ISC
+[MIT](LICENSE).

package/dist/prompt/context.js

@@ -0,0 +1,79 @@
+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)}
+
+    ALL of it lives under the hidden \`${TESTEIYA_DIR_NAME}/\` dir: file-search tools skip hidden dirs by default, so search it explicitly (pass hidden:true, or prefix the path with \`${TESTEIYA_DIR_NAME}/\`). 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] ?? "";
+    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

@@ -0,0 +1 @@
+{"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;;yCAEO,iBAAiB,gIAAgI,iBAAiB,0NAA0N,iBAAiB,kCAAkC,iBAAiB,yBAAyB,iBAAiB;;GAEhhB,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,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"}