testeiya 0.2.1 → 0.3.1-5.1

package/skills/playwright-best-practices-skill/LICENSE.md

@@ -1,7 +0,0 @@
-Copyright © 2026 Currents Software Inc.
-
-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/skills/playwright-best-practices-skill/README.md

@@ -1,147 +0,0 @@
-```
-
-░█▀█░█░░░█▀█░█░█░█░█░█▀▄░▀█▀░█▀▀░█░█░▀█▀░░░█▀▄░█▀▀░█▀▀░▀█▀░░░█▀█░█▀▄░█▀█░█▀▀░▀█▀░▀█▀░█▀▀░█▀▀░█▀▀░
-░█▀▀░█░░░█▀█░░█░░█▄█░█▀▄░░█░░█░█░█▀█░░█░░░░█▀▄░█▀▀░▀▀█░░█░░░░█▀▀░█▀▄░█▀█░█░░░░█░░░█░░█░░░█▀▀░▀▀█░
-░▀░░░▀▀▀░▀░▀░░▀░░▀░▀░▀░▀░▀▀▀░▀▀▀░▀░▀░░▀░░░░▀▀░░▀▀▀░▀▀▀░░▀░░░░▀░░░▀░▀░▀░▀░▀▀▀░░▀░░▀▀▀░▀▀▀░▀▀▀░▀▀▀░
-```
-<img src="https://currents.dev/favicon-96x96.png" width="24" height="24" align="left" />by [currents.dev](https://currents.dev?utm_source=ai-skill) - The all-in-one Dashboard for Playwright Testing.
-
-# Playwright Best Practices Skill
-
-A skill that gives the AI specialized guidance for writing, debugging, and maintaining **Playwright** tests in **TypeScript**. Use it in any repo where you work with Playwright so the assistant follows best practices for E2E, component, API, visual regression, accessibility, security, i18n, Electron, and browser extension testing.
-
-## Installation
-
-```bash
-npx skills add https://github.com/currents-dev/playwright-best-practices-skill
-```
-
-The skill is activity-based: the AI is directed to the right reference depending on what you're doing, so you get focused advice without loading everything at once.
-
-## When the Skill Is Used
-
-The skill triggers when the AI infers you need help with things like:
-
-- Writing new E2E, component, API, visual regression, or accessibility tests
-- Testing mobile/responsive layouts, touch gestures, or device emulation
-- Implementing file uploads/downloads, date/time mocking, or WebSocket testing
-- Handling OAuth popups, geolocation, permissions, or multi-tab flows
-- Testing iframes, canvas/WebGL, service workers, or PWA features
-- Testing Electron desktop apps or browser extensions
-- Internationalization (i18n), locales, RTL layouts, or date/number formats
-- Testing error states, offline mode, or network failure scenarios
-- Security testing (XSS, CSRF, authentication, authorization)
-- Performance testing with Web Vitals or Lighthouse
-- Reviewing or refactoring Playwright test code
-- Fixing flaky tests or debugging failures
-- Setting up CI/CD, test coverage, or global setup/teardown
-- Configuring projects, dependencies, parallel runs, or sharding
-
-You don't have to mention "skill" or "Playwright best practices"; describe your task (e.g. "fix this flaky login test" or "add accessibility tests") and the AI will use the skill when it's relevant.
-
-## What's Inside
-
-**57 reference documents** organized into 8 categories:
-
-### Core (`core/`)
-
-| Topic                | Reference                   | Use for                                          |
-| -------------------- | --------------------------- | ------------------------------------------------ |
-| Test structure       | `test-suite-structure.md`   | Structure, config, E2E/component/API/visual tests |
-| Locators             | `locators.md`               | Selectors, robustness, avoiding brittle locators |
-| Assertions & waiting | `assertions-waiting.md`     | Expect APIs, auto-waiting, polling               |
-| Page Object Model    | `page-object-model.md`      | POM structure and patterns                       |
-| Fixtures & hooks     | `fixtures-hooks.md`         | Setup, teardown, auth, custom fixtures           |
-| Test data            | `test-data.md`              | Factories, Faker, data-driven testing            |
-| Annotations          | `annotations.md`            | skip, fixme, slow, test steps                    |
-| Configuration        | `configuration.md`          | playwright.config.ts options                     |
-| Global setup         | `global-setup.md`           | globalSetup/Teardown, DB migrations              |
-| Projects             | `projects-dependencies.md`  | Project config, dependencies, filtering          |
-
-### Debugging (`debugging/`)
-
-| Topic          | Reference            | Use for                                    |
-| -------------- | -------------------- | ------------------------------------------ |
-| Debugging      | `debugging.md`       | Trace viewer, inspector, common issues     |
-| Flaky tests    | `flaky-tests.md`     | Detection, diagnosis, fixing, quarantine   |
-| Error testing  | `error-testing.md`   | Error boundaries, offline, network failures |
-| Console errors | `console-errors.md`  | Capturing and failing on JS errors         |
-
-### Testing Patterns (`testing-patterns/`)
-
-| Topic               | Reference                 | Use for                                        |
-| ------------------- | ------------------------- | ---------------------------------------------- |
-| Accessibility       | `accessibility.md`        | Axe-core, keyboard nav, ARIA, focus management |
-| API testing         | `api-testing.md`          | REST API testing, request context              |
-| Component testing   | `component-testing.md`    | CT setup, mounting, props, mocking             |
-| Visual regression   | `visual-regression.md`    | Screenshot comparison, thresholds              |
-| File operations     | `file-operations.md`      | Upload, download basics                        |
-| File upload/download| `file-upload-download.md` | Progress, cancellation, retry patterns         |
-| Forms validation    | `forms-validation.md`     | Form testing, validation states                |
-| Drag and drop       | `drag-drop.md`            | Drag-and-drop interactions                     |
-| GraphQL testing     | `graphql-testing.md`      | GraphQL queries, mutations, mocking            |
-| Canvas/WebGL        | `canvas-webgl.md`         | Canvas testing, charts, WebGL, games           |
-| i18n                | `i18n.md`                 | Locales, RTL, date/number formats              |
-| Electron            | `electron.md`             | Desktop apps, IPC, main/renderer process       |
-| Browser extensions  | `browser-extensions.md`   | Popup, background, content scripts, APIs       |
-| Security testing    | `security-testing.md`     | XSS, CSRF, auth security, authorization        |
-| Performance testing | `performance-testing.md`  | Web Vitals, budgets, Lighthouse                |
-
-### Advanced (`advanced/`)
-
-| Topic            | Reference               | Use for                                     |
-| ---------------- | ----------------------- | ------------------------------------------- |
-| Authentication   | `authentication.md`     | Login flows, session storage, cookies       |
-| Auth flows       | `authentication-flows.md` | MFA, password reset, complex auth         |
-| Mobile testing   | `mobile-testing.md`     | Device emulation, touch gestures, viewports |
-| Clock mocking    | `clock-mocking.md`      | Date/time mocking, timezones, timers        |
-| Multi-context    | `multi-context.md`      | Popups, new tabs, OAuth flows               |
-| Multi-user       | `multi-user.md`         | Collaboration, RBAC, concurrent actions     |
-| Network advanced | `network-advanced.md`   | GraphQL, HAR, request modification          |
-| Third-party      | `third-party.md`        | OAuth, payments, email/SMS mocking          |
-
-### Browser APIs (`browser-apis/`)
-
-| Topic           | Reference            | Use for                                     |
-| --------------- | -------------------- | ------------------------------------------- |
-| Browser APIs    | `browser-apis.md`    | Geolocation, permissions, clipboard, camera |
-| WebSockets      | `websockets.md`      | Real-time testing, SSE, reconnection        |
-| iFrames         | `iframes.md`         | Cross-origin, nested, dynamic iframes       |
-| Service workers | `service-workers.md` | PWA, caching, offline, push notifications   |
-
-### Architecture (`architecture/`)
-
-| Topic             | Reference              | Use for                              |
-| ----------------- | ---------------------- | ------------------------------------ |
-| POM vs fixtures   | `pom-vs-fixtures.md`   | Choosing between patterns            |
-| Test architecture | `test-architecture.md` | Test type selection, structure       |
-| When to mock      | `when-to-mock.md`      | Mock vs real services decisions      |
-
-### Frameworks (`frameworks/`)
-
-| Topic   | Reference     | Use for                        |
-| ------- | ------------- | ------------------------------ |
-| React   | `react.md`    | React-specific testing patterns |
-| Angular | `angular.md`  | Angular-specific testing        |
-| Vue     | `vue.md`      | Vue/Nuxt testing patterns       |
-| Next.js | `nextjs.md`   | Next.js SSR/SSG testing         |
-
-### Infrastructure & CI/CD (`infrastructure-ci-cd/`)
-
-| Topic            | Reference              | Use for                              |
-| ---------------- | ---------------------- | ------------------------------------ |
-| CI/CD            | `ci-cd.md`             | Pipelines, general CI setup          |
-| GitHub Actions   | `github-actions.md`    | GitHub-specific workflows            |
-| GitLab CI        | `gitlab.md`            | GitLab-specific pipelines            |
-| Other providers  | `other-providers.md`   | CircleCI, Azure DevOps, Jenkins      |
-| Docker           | `docker.md`            | Container setup, Playwright images   |
-| Parallel/sharding| `parallel-sharding.md` | Sharding, parallel execution         |
-| Performance      | `performance.md`       | Parallel runs, optimization          |
-| Reporting        | `reporting.md`         | Test reporters, artifacts            |
-| Test coverage    | `test-coverage.md`     | V8 coverage, reports, thresholds, CI |
-
-The skill's `SKILL.md` maps your current activity to these references so the right content is used in context.
-
-## License
-
-MIT

package/skills/testeiya/README.md

@@ -1,29 +0,0 @@
-# Testeiya internal skills
-
-First-party skills authored in this repo and shipped with every Testeiya build.
-This folder is **not** managed by `cli/skills.yaml` — `bunosh skills:update`
-never touches it (it only replaces manifest-owned vendor folders).
-
-A skill is a folder with a `SKILL.md` — YAML frontmatter (`name` +
-`description`) followed by the instructions:
-
-    cli/skills/testeiya/my-skill/SKILL.md
-
-Scaffold one with `bunosh skills:create <name>`.
-
-Rules:
-
-- The frontmatter `name` must be a slug (`[a-z0-9-]`) — it is the `/mention`
-  token in the chat input. A non-slug name falls back to the folder name.
-- Skills placed directly in this folder get the **Testeiya** category in the
-  skills menu. To use a different category, nest a category subfolder:
-  `testeiya/<category>/<skill>/SKILL.md`.
-- A skill here **overrides** a vendored skill with the same name only by
-  load-order dedupe — avoid reusing external names; `bunosh skills:update`
-  warns on collisions.
-- Check the result with `bunosh skills:list` (this folder shows as internal).
-
-One exception to "hand-authored": `testomatio-docs/` carries generated data.
-Its `SKILL.md` is source and safe to edit, but `docs/`, `INDEX.md` and
-`docs.lock.json` are written by `bunosh docs:update` (re-run on release) from
-github.com/testomatio/docs — edit those upstream, not here.

package/skills/testeiya/answer-formatting/SKILL.md

@@ -1,30 +0,0 @@
----
-name: answer-formatting
-description: How to compose Testeiya's answer to any data question — counts, lists, statuses, trends, coverage, plan reviews, comparisons, reports. Use BEFORE composing such a reply. Defines the answer blocks (headline, chart, list, insights, offer) and the proof rules.
-license: MIT
-metadata:
-  author: Testomat.io
-  version: 2.0.0
----
-
-# Answer formatting
-
-A data question gets a visual answer. Build the reply from these blocks, in this order. Include a block when its data exists in the answer; skip it when it doesn't.
-
-1. **Headline** — one sentence: the verdict and its key number.
-2. **Chart** — `render_chart` or diagram if data can be explained with visuals.
-3. **List** — `render_result({call_id})` if data can be presented as a table. One entity → `render_item`. A hierarchy → `render_tree`.
-4. **Insights** — up to 3 bullets: what stands out, each citing its source.
-5. **Offer** — the obvious next action as an `ask_question`; a pick-a-subset proposal is its multi-select checklist. Skip when the answer closes the topic.
-
-Example: "how many of X passed?" → headline with the ratio, chart of the status split, one list of all X with status marks.
-
-## Rules
-
-- Every visual has a `title`: what it shows and how it was filtered.
-- No prose that repeats what a visual shows. Short sentences. No filler. Bold key numbers only. Never italic.
-- Workspace files as inline code (renders as a clickable link). Entities by their id.
-- Only numbers you computed from fetched data — derive counts/ratios with `query_result` on the fetched result, never by eyeballing a digest's sample; partial coverage is declared.
-- A flow or sequence → a `mermaid` block in the text.
-- Tool params live in the app-interface section of your system prompt — follow it, never invent fields.
-- No render tools in this host (terminal)? Same blocks as markdown: table with ✅ ❌ ⚠️ ⏭ marks instead of list/chart.

package/skills/testeiya/check-cucumber/SKILL.md

@@ -1,200 +0,0 @@
----
-name: check-cucumber
-description: Sync Gherkin `.feature` files with Testomat.io using the check-cucumber CLI. Import Features as suites and Scenarios as tests, write `@S`/`@T` IDs back, check or clean IDs, and pull manual BDD tests as feature files. The BDD counterpart to check-tests; Testeiya's built-in sync never touches `.feature` files. Use in a Cucumber, CodeceptJS-BDD, or Gherkin repo to import, push, sync, pull, or ID-tag features and scenarios.
-license: MIT
-metadata:
-  author: Testomat.io
-  version: 1.0.0
----
-
-# check-cucumber
-
-The `check-cucumber` CLI syncs Gherkin `.feature` files with Testomat.io. npm package `check-cucumber` (v0.6.x), run with `npx`. It:
-
-- imports every Feature as a suite and every Scenario as a test case;
-- writes `@S`/`@T` IDs back into the files for round-tripping;
-- pulls manual BDD tests from Testomat.io as `.feature` files.
-
-## Use cases
-
-- Import a Cucumber repo's features and scenarios into Testomat.io.
-- Write `@S`/`@T` IDs into the feature files so they round-trip with the TMS.
-- Import one directory without detaching the rest of the project.
-- Import into a branch, with labels, excluding drafts.
-- Gate CI on missing IDs (`--check-ids`).
-- Pull the project's manual BDD tests down as `.feature` files.
-- Diagnose an import that printed success but changed nothing.
-
-## Which tool for which tests
-
-A Cucumber project's `.feature` files ARE its tests. They are not `*.test.md`, and Testeiya's built-in sync does not cover them.
-
-- `*.test.md` markdown or code-based specs → `check-tests`.
-- Gherkin `.feature` files → this skill.
-- Test run RESULTS → `@testomatio/reporter` (`testomatio-reporter`, `qa-e2e-tests-reporting`).
-- Unsure of the project kind → `scan-automation-project` first.
-
-Never run `check-tests` over a `features/` directory, or `check-cucumber` over a markdown manual-tests directory.
-
-## Critical rules
-
-- **The import command REQUIRES the positional glob.** `npx check-cucumber -d features` alone prints the banner and exits 0 — a silent no-op. Always pass the pattern: `npx check-cucumber "**/*.feature" -d features`.
-- **Import failures exit 0.** A rejected import logs `✖️` and exits 0; a missing key logs `Cant send report, api key not set` and exits 0. Judge success by the output text (`Data sent to Testomat.io`), never the exit code.
-- **A partial import detaches everything else.** Importing a subset marks every test not in the payload as detached. Pass `--no-detached` for partial imports.
-- **Destructive flags need explicit confirmation first.** `--purge`/`--unsafe-clean-ids` regex-strip every `@S`/`@T`-shaped tag (may eat unrelated tags like `@Test1234`); `--clean-ids` removes this project's IDs; `pull` overwrites same-named files. Preflight: clean/committed git tree; `pull --dry-run` first; grep for near-miss tags before a purge.
-- **`Rule:` blocks crash the parser** (`TypeError: Cannot read properties of null (reading 'tags')`, exit 1). Scenarios must sit directly under `Feature:`.
-- **Do not pass options to the `push` subcommand.** A parsing quirk makes the root command swallow shared options (`-d`, `--sync`, `--update-ids`, `--check-ids`, …). Use the root form `check-cucumber "<glob>" [options]` for every import.
-- One source of truth per test — never double-import. A scenario synced here is automated in Testomat.io; don't also push it as markdown via check-tests.
-- Quote the glob so the shell doesn't expand it.
-
-## Testeiya workspace context
-
-- A workspace is the session cwd representing one project; metadata in `.testeiya/testeiya.json` (`{projectId, baseUrl, title}`). When `baseUrl` isn't `https://app.testomat.io`, export it as `TESTOMATIO_URL`.
-- `cli/src/workspace-model.ts` classifies a Cucumber repo as an automation workspace (`.feature` files + a cucumber config or `@cucumber/cucumber` dependency mark `hasAutomationConfig`).
-- So Testeiya's built-in pull omits `--export-automated` here: `.testeiya/manual-tests/` holds only manual markdown, and the `.feature` files stay the single source for automated ones. Keep it that way.
-- The built-in sync never picks up `features/` — feature-file sync is always an explicit check-cucumber run by the agent.
-
-### Token resolution
-
-check-cucumber reads only `TESTOMATIO` (a `tstmt_…` key; `.env` in the cwd is auto-loaded). Resolve in Testeiya's order:
-
-1. the managed session's project token;
-2. else the linked project's `apiKey` from the connected account;
-3. else the folder's own `.env` `TESTOMATIO`;
-4. else ask the user (Settings → Project → Project Reporting API key).
-
-### Manual vs automated
-
-- Each pulled markdown test carries `type: manual` or `type: automated`; a missing `type:` means manual.
-- Gherkin scenarios imported here land on the automated side — they are backed by step definitions.
-- Two exceptions import as manual: a `*.manual.feature` file (every scenario in it), and files created by `check-cucumber pull` (the pull exports the project's manual tests as Gherkin).
-- If a case already exists as a manual markdown test and the user automates it, bind them by putting the existing `@T…` ID on the scenario — don't import a duplicate. See `automate-manual-test-cases`.
-
-## Commands
-
-```bash
-npx check-cucumber "<glob>" [options]     # analyze + import (the push direction)
-npx check-cucumber pull [--dry-run]       # pull manual tests as .feature files (into cwd)
-```
-
-The glob resolves relative to `-d` (default cwd). `node_modules` is excluded automatically, but scope with `-d` on large repos anyway.
-
-### Import options (root command)
-
-| Flag | Meaning |
-|---|---|
-| `<glob>` (positional) | Required. `"**/*.feature"` for the whole tree |
-| `-d, --dir <dir>` | Scan root (default cwd). Scope to `features/` etc. |
-| `-e, --exclude <glob>` | Skip files: `-e "**/wip/*.feature"` |
-| `--sync` | Wait until the server finishes. Use in CI and whenever a next step depends on the import |
-| `-U, --update-ids` | Import, wait, then write `@S`/`@T` IDs back. Needs the key |
-| `--check-ids` | Exit 1 when any feature/scenario lacks an ID (CI guard); proceeds with the import when all present |
-| `--create` | Create tests/suites for IDs not found in the project |
-| `--no-detached` | Don't detach absent tests. Required for partial imports |
-| `--no-empty` | Delete suites left empty after import. Conflicts with `--keep-structure` |
-| `--keep-structure` | Force the source structure onto the project |
-| `-c, --codeceptjs` | CodeceptJS-BDD projects; accepted for compatibility, no payload change in 0.6.0 |
-| `--clean-ids` | **Destructive.** Remove this project's IDs (needs the key). Confirm first |
-| `--purge` / `--unsafe-clean-ids` | **Destructive.** Strip all `@S`/`@T`-shaped tags, no server check (no key needed). Confirm first |
-
-### Pull options
-
-- `--dry-run` — preview the file list without writing. Always run first.
-- `pull -d` is BROKEN in 0.6.0 (swallowed by the root command) — pull always writes to the cwd, so `cd` into the target dir before pulling.
-- Pull calls `GET {TESTOMATIO_URL}/api/test_data?api_key=…&with_files=true`, creates nested dirs, and overwrites same-named files.
-
-## Environment variables
-
-A `.env` in the cwd is auto-loaded (dotenv).
-
-| Variable | Purpose |
-|---|---|
-| `TESTOMATIO` | Project API key (`tstmt_…`). Required for import, IDs, pull |
-| `INPUT_TESTOMATIO-KEY` | Alternative key slot (GitHub Actions); takes precedence over `TESTOMATIO` |
-| `TESTOMATIO_URL` | Instance URL (default `https://app.testomat.io`). Set from `.testeiya/testeiya.json` `baseUrl` on self-hosted |
-| `TESTOMATIO_BRANCH` | Import into this branch; created if missing |
-| `TESTOMATIO_SUITE` | Import everything into an existing suite by ID (`@Sa1b2c3d4`) |
-| `TESTOMATIO_PREPEND_DIR` | Wrap imported files under a new top folder |
-| `TESTOMATIO_WORKDIR` | Rebase reported file paths to this directory |
-| `TESTOMATIO_LABELS` | Comma-separated labels on every imported test; `label:value` sets values. Alias `TESTOMATIO_SYNC_LABELS` |
-| `TESTOMATIO_NO_DETACHED` | `1` = same as `--no-detached` |
-| `TESTOMATIO_TITLE_IDS` | `1` = write test IDs into Scenario titles instead of tags |
-
-## Gherkin → Testomat.io mapping
-
-| Gherkin | Testomat.io | Notes |
-|---|---|---|
-| folder / `x.feature` file | suite hierarchy | folders and file names become parent suites |
-| `Feature:` | suite | feature tags travel with the suite; empty title = file skipped with an error |
-| `Scenario:` | test (automated) | full source block becomes the test body; empty title = scenario skipped |
-| `Scenario Outline:` + `Examples:` | ONE test | not expanded per row; the Examples table stays in the body |
-| tags (`@smoke`, `@severity:critical`) | tags on the test | sent without `@`; `@S`/`@T` ID tags are treated as sync IDs, not tags |
-| `Background:` | NOT imported | parses fine, but its steps appear in no test — keep critical context in scenarios |
-| `Rule:` | NOT supported | crashes the analyzer |
-| `And` / `But` | normalized | inherit the preceding Given/When/Then keyword |
-| `*.manual.feature` | manual tests | the marker for manual BDD cases kept in the repo |
-
-`--update-ids` write-back: IDs are inserted as tags — appended to an existing tag line, else a new tag line above `Feature:`/`Scenario:`, indentation preserved. Files carrying IDs from another project warn `Some tests have IDs from another project` and are left alone — clean with `--clean-ids` (old key) or a confirmed `--purge`.
-
-## Recipes
-
-From the workspace root, token in `.env` or env:
-
-```bash
-# First import, waiting for the server
-npx check-cucumber "**/*.feature" --sync
-
-# Import and write IDs back (the standard round-trip sync)
-npx check-cucumber "**/*.feature" --update-ids
-
-# CI guard — fail when IDs are missing
-npx check-cucumber "**/*.feature" --check-ids
-
-# Partial import of one directory, rest untouched
-npx check-cucumber "**/*.feature" -d features/checkout --no-detached
-
-# Import into a branch, with labels, excluding drafts
-TESTOMATIO_BRANCH="release-2.4" TESTOMATIO_LABELS="smoke,severity:high" \
-  npx check-cucumber "**/*.feature" -e "**/wip/*.feature" --sync
-
-# Self-hosted instance
-TESTOMATIO_URL="https://testomatio.example.com" npx check-cucumber "**/*.feature" --sync
-
-# Pull manual BDD tests into a dedicated directory (pull writes to cwd)
-mkdir -p features/manual && cd features/manual
-npx check-cucumber pull --dry-run
-npx check-cucumber pull
-
-# Re-import as a new project (confirm + commit first)
-npx check-cucumber "**/*.feature" --purge
-TESTOMATIO=<new-project-key> npx check-cucumber "**/*.feature" --update-ids
-```
-
-## Exit codes and troubleshooting
-
-Exit 1: `--check-ids` found missing IDs; `pull` without a key or with a failed request; the `Rule:` analyzer crash. Everything else — rejected imports, parse errors, a missing key on import — exits 0, so always read the output.
-
-| Symptom | Cause | Fix |
-|---|---|---|
-| Banner prints, nothing else, exit 0 | Positional glob missing | Add `"**/*.feature"` |
-| `Cant send report, api key not set` | `TESTOMATIO` unset | Resolve the token; the run parsed files but imported nothing |
-| `✖️ <server message>` after `Sending data…` | Server rejected the import (bad/foreign token) — exit still 0 | Verify the key matches this project |
-| `✖️ Error: Server cannot be reached` | Network / wrong `TESTOMATIO_URL` | Check the URL against `.testeiya/testeiya.json` `baseUrl` |
-| `TypeError: … (reading 'tags')` | A `Rule:` block | Flatten scenarios directly under `Feature:` |
-| `Errors :` listing `expected: #EOF, …` | Gherkin syntax error — that file is skipped, exit stays 0 | Fix the reported line; re-run |
-| `Total Scenarios skipped N` | Scenarios with empty titles | Give every scenario a title |
-| `N suites and M tests are missing test IDs!` (exit 1) | `--check-ids` failed | Run with `--update-ids` |
-| `Some tests have IDs from another project` | Foreign `@S`/`@T` tags | `--clean-ids` with the old key, or a confirmed `--purge` |
-| Tests unexpectedly detached | A partial import without `--no-detached` | Re-import the full tree; use `--no-detached` for partial runs |
-| Pull wrote files to the wrong place | `pull -d` not honored in 0.6.0 | `cd` into the target dir first |
-| Pull says `No files found on server` | The project has no manual tests to export | Nothing to pull; check the project kind |
-
-## Related skills
-
-- `check-tests` — the markdown/code counterpart; Testeiya's built-in sync path.
-- `sync-test-cases-with-tms` — markdown pull/push workflow details.
-- `testomatio-reporter` / `qa-e2e-tests-reporting` — report cucumber RUN RESULTS; check-cucumber only syncs definitions.
-- `scan-automation-project` — detect the framework before choosing a sync tool.
-- `automate-manual-test-cases` — bind existing manual cases to new scenarios by ID.
-- `qa-test-code-coverage` — map source files to imported test IDs.
-- `testomatio-mcp` — query the project's suites and tests directly.