gd-tools-cli 0.6.0__tar.gz → 0.8.0__tar.gz

{gd_tools_cli-0.6.0 → gd_tools_cli-0.8.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: gd-tools-cli
-Version: 0.6.0
+Version: 0.8.0
 Summary: A modern development workflow CLI for GDScript projects in Godot 4.5+
 Author-email: mansyar <m.ansyarafi@gmail.com>
 License: MIT
@@ -35,6 +35,7 @@ Requires-Dist: watchdog
 Provides-Extra: dev
 Requires-Dist: pytest; extra == "dev"
 Requires-Dist: pytest-cov; extra == "dev"
+Requires-Dist: pytest-xdist; extra == "dev"
 Requires-Dist: ruff==0.15.21; extra == "dev"
 Requires-Dist: black; extra == "dev"
 Requires-Dist: commitizen; extra == "dev"
@@ -74,10 +75,11 @@ One install, one config, one mental model.
 | Feature | Description |
 |---------|-------------|
 | **Unified workflow** | One install, one config (`gd-tools.toml`), one mental model for test, lint, format, and coverage. Consistent terminal output with colored markers and summary footers across all commands. |
-| **Native test runtime** | Tests extend `GdToolsTest` and run inside Godot itself. Scene and resource integration tests reach the real scene tree through an explicit context object rather than a proxy. |
+| **Native test runtime** | Tests extend `GdToolsTest` and run inside Godot itself. Scene and resource integration tests reach the real scene tree through an explicit context object rather than a proxy. Doubles, partial doubles, and stubbing isolate collaborators; spy assertions cover calls, argument wildcards, call order, and property values. |
+| **Snapshot testing** | `assert_snapshot(value)` pins rendered values -- including object property dumps and node trees -- against versioned, diffable `.snap` files. First run writes and passes; mismatches fail with a unified diff, and `--snapshot-update` accepts the new output. |
 | **Zero-friction bootstrap** | `gd-tools init` gets a project fully set up in under a minute -- native test and coverage addons deployed, configs generated. |
-| **Coverage gap-filling** | Production-quality line and branch coverage for GDScript -- HTML, LCOV, and Cobertura reports that integrate with CI and code review tools. `# gd-tools: no cover` annotations exclude debug-only code from the numbers. `coverage run` collects coverage during manual playtest sessions, not just automated tests. |
-| **CI/CD friendly** | Exit codes, `--check` flags, machine-readable output (JSON, JUnit XML, LCOV, Cobertura), no interactive prompts in CI mode. |
+| **Coverage gap-filling** | Production-quality line and branch coverage for GDScript -- HTML, LCOV, Cobertura, and JSON reports, plus GitHub Actions annotations that surface failures inline on pull requests. Independent line (`--min`) and branch (`--min-branch`) gates. `# gd-tools: no cover` annotations exclude debug-only code from the numbers. `coverage run` collects coverage during manual playtest sessions, not just automated tests. Patch coverage (`coverage diff --patch`) reports coverage over only the lines a pull request changes, with its own gate and inline annotations. |
+| **CI/CD friendly** | Exit codes, `--check` flags, machine-readable output (JSON, JUnit XML, LCOV, Cobertura), and GitHub Actions annotations for lint violations and coverage gates. No interactive prompts in CI mode. |
 | **Standalone compatibility** | gdlint and gdformat continue to work if invoked directly. `gd-tools` is a layer on top, not a lock-in. |
 
 ## 3. Installation
@@ -140,13 +142,13 @@ func test_health_starts_at_full() -> void:
 |---------|-------------|
 | `gd-tools init` | Bootstrap a Godot project -- deploy the native test and coverage addons, generate configs. |
 | `gd-tools doctor` | Diagnose the development environment -- Godot, native test addon, coverage addon, tooling; reports legacy GUT artifacts as migration advice. |
-| `gd-tools test` | Run tests with optional coverage, thresholds, and JUnit XML output. Suites must extend `GdToolsTest`; `GutTest` suites are rejected with exit 2 and migration guidance. Accepts optional path arguments to override configured test directories. `--parallel N` runs suites through a bounded worker pool. `--changed` runs only the suites mapped from git-changed files. `--watch` re-runs affected suites on `.gd` file changes. Every run publishes a machine-readable artifact index under `.gd-tools/artifacts/<run_id>/`. |
+| `gd-tools test` | Run tests with optional coverage, thresholds, and JUnit XML output. Suites must extend `GdToolsTest`; `GutTest` suites are rejected with exit 2 and migration guidance. Accepts optional path arguments to override configured test directories. `--parallel N` runs suites through a bounded worker pool. `--changed` runs only the suites mapped from git-changed files. `--watch` re-runs affected suites on `.gd` file changes. `--durations N` reports the N slowest tests after the run. `--exitfirst` (`-x`) stops dispatching new suites after the first failing suite; `--shard K/N` runs one round-robin shard for CI matrix splitting. Every run publishes a machine-readable artifact index under `.gd-tools/artifacts/<run_id>/`. |
 | `gd-tools migrate` | Guided GUT-to-native migration. Default: read-only report with unsupported-construct inventory and proposed base-class rewrites. `--apply` renames clean suites to `GdToolsTest` and translates `.gutconfig.json` into `gd-tools.toml` (merge, never clobber). `--config-only` translates config only. |
-| `gd-tools lint` | Lint GDScript files using gdlint with text or JSON output. Accepts one or more file or directory paths. |
+| `gd-tools lint` | Lint GDScript files using gdlint with text, JSON, or GitHub Actions annotation output. Accepts one or more file or directory paths. |
 | `gd-tools format` | Format GDScript files using gdformat with check and diff modes. Accepts one or more file or directory paths. |
-| `gd-tools coverage` | Coverage subcommands -- `report`, `merge`, `show`, `save-baseline`, `diff` (baseline comparison for CI regression gates), and `run` (collect coverage during a manual playtest session). |
+| `gd-tools coverage` | Coverage subcommands -- `report`, `merge`, `show`, `save-baseline`, `diff` (baseline comparison for CI regression gates; with `--patch`, PR-scoped coverage over changed lines), and `run` (collect coverage during a manual playtest session). |
 | `gd-tools config` | Configuration management -- `show` (display resolved config), `validate` (check config validity), `schema` (print or write the JSON Schema for `gd-tools.toml`). |
-| `gd-tools version` | Display versions of all gd-tools components (gd-tools, Godot, gdtoolkit, Python, and GUT when installed) in a table or JSON. |
+| `gd-tools version` | Display versions of all gd-tools components (gd-tools, Godot, gdtoolkit, Python) in a table or JSON. |
 | `gd-tools completion` | Generate shell completion scripts for bash, zsh, fish, or PowerShell. |
 
 ### Selecting and Filtering Tests
@@ -158,8 +160,11 @@ gd-tools test --test test_takes_damage     # one test method
 gd-tools test --tag smoke                  # suites with that class-level tag
 gd-tools test --test-timeout 30            # per-test timeout, in seconds
 gd-tools test --parallel 4                 # run suites with 4 concurrent workers
+gd-tools test --durations 10               # report the 10 slowest tests
 gd-tools test --changed                    # only suites mapped from git-changed files
 gd-tools test --changed --base main        # PR/CI mode: diff from merge-base with main
+gd-tools test --exitfirst                  # stop dispatching after the first failing suite
+gd-tools test --shard 2/4                  # CI sharding: run suite shard 2 of 4
 ```
 
 `--tag` is repeatable, and `--test-timeout` (per test) is separate from
@@ -168,6 +173,13 @@ worker pool (1-32 workers; bare `--parallel` means 4) while keeping results,
 JUnit XML, and merged coverage identical to a sequential run. Persist the
 choice with `parallel = 4` under `[test]` in `gd-tools.toml`.
 
+`--durations N` prints a "Slowest Tests" table after the run, sorted
+slowest-first, covering pass, fail, and skip outcomes. Bare `--durations`
+means 10; `--durations 0` lists every executed test (pytest parity). Persist
+the choice with `durations = 10` under `[test]` in `gd-tools.toml`; the flag
+overrides the config for one invocation. The table renders identically under
+`--watch` re-runs and `--parallel` runs.
+
 `--changed` selects suites from git instead of running everything: uncommitted
 changes (staged, unstaged, and untracked) map to suites by the same
 file→suite convention as `--watch` — `src/enemy.gd` selects
@@ -181,6 +193,29 @@ pull-request CI. `--changed` composes with `--parallel`, `--coverage`, and
 the `--suite`/`--test`/`--tag` filters (the active filters bound the
 mapping domain); an empty change set exits 0 without launching Godot.
 
+`--exitfirst` (short form `-x`) stops dispatching **new** suites after the
+first suite whose final result is a failure — a test failure or an
+infrastructure error. In-flight suites finish and are collected; suites that
+were never started are reported as skipped (`not_run`) and summarized in a
+`Stopped early: fail-fast after suite <id> (K of M suites skipped)` line.
+Passes and skips never trigger the gate, and a suite that passes after a
+retry does not either — only final suite results decide. The exit code stays
+1 for test failures. `--exitfirst` composes with `--parallel` (the pool
+drains instead of killing workers), with `--coverage` (the report covers the
+suites that ran, labeled partial when plan targets went unmeasured), and with
+`--watch` (the gate resets for every re-run).
+
+`--shard K/N` runs only the suites assigned to shard `K` of `N` — suite *i*
+of the deterministic plan order belongs to shard `(i mod N) + 1` — for
+splitting one test run across CI jobs. Selection happens after `--changed`
+filtering and before `--parallel`, so each flag keeps exactly one job.
+`--shard 1/1` is valid and equivalent to no sharding; malformed values
+(`--shard 4/3`, `--shard 3`) exit 2 before any work. Each shard produces its
+own coverage report; merge the shards with `gd-tools coverage merge`.
+`--shard` and `--watch` are rejected together (exit 2). See the
+[sharding recipe](./docs/USER_GUIDE.md#sharding-a-test-run-across-ci-jobs)
+for a GitHub Actions matrix example.
+
 Repeat runs are faster: the `godot --headless --import` step is cached under
 `.gd-tools/native/import-cache/` and skipped when `project.godot`, any
 project source/resource file (scripts, scenes, import sidecars, addons), or
@@ -319,7 +354,41 @@ eval "$(gd-tools)"
 See the [User Guide](./docs/USER_GUIDE.md) for detailed per-shell
 instructions.
 
-## 7. Configuration
+## 7. Pre-commit Hooks
+
+Wire gd-tools into the [pre-commit](https://pre-commit.com) framework so
+every commit runs your format check, lint, and (optionally) your test suite:
+
+```bash
+gd-tools install-hooks
+```
+
+The command generates `.pre-commit-hooks.yaml` and merges a `repos: local:`
+entry into `.pre-commit-config.yaml`. Existing hooks — including your own —
+are preserved; re-runs update only the gd-tools entries in place.
+
+Interactive by default: confirm each hook (`format`, `lint`, `test`). For
+scripted or CI use, pass flags instead:
+
+```bash
+gd-tools install-hooks --non-interactive      # format + lint (defaults)
+gd-tools install-hooks --all                  # format + lint + test
+gd-tools install-hooks --hooks format,lint    # explicit selection
+```
+
+| Flag | Behavior |
+|---|---|
+| `--all` | Enable every hook (format, lint, test). |
+| `--hooks HOOKS` | Comma-separated selection, e.g. `--hooks format,lint`. |
+| `--non-interactive` | Never prompt; use defaults or explicit flags. |
+
+Exit codes follow the gd-tools convention: `0` installed, `1` nothing to do,
+`2` config/environment error.
+
+See the [User Guide](./docs/USER_GUIDE.md#8-pre-commit-hooks) for the
+generated file contents and per-hook details.
+
+## 8. Configuration
 
 `gd-tools` uses a single `gd-tools.toml` file as the source of truth for
 all tool configuration. `gd-tools init` generates this file with sensible
@@ -333,10 +402,9 @@ binary = ""  # Optional -- auto-detected if unset
 test_dirs = ["test", "tests"]
 prefix = "test_"
 suffix = ".gd"
-gutconfig = ".gutconfig.json"  # legacy; not read by any runtime
 runtime = "native"        # native (default); "gut" is no longer a runnable runtime
 timeout_seconds = 5.0     # default per-test timeout for async native tests
-retries = 0               # opt-in retries per native test
+retries = 0               # opt-in retries per native test; retried passes are flagged as flaky
 # parallel = 4            # opt-in parallel suite execution (1-32; unset runs sequentially)
 tags = []                 # native suite tag filters
 
@@ -384,7 +452,7 @@ version's config model.
 See the [User Guide](./docs/USER_GUIDE.md) for a full configuration reference
 with all keys, defaults, and examples.
 
-## 8. Documentation
+## 9. Documentation
 
 | Document | Description |
 |----------|-------------|
@@ -395,7 +463,7 @@ with all keys, defaults, and examples.
 | [Roadmap](./docs/ROADMAP.md) | Release phases and milestones. |
 | [Testing Strategy](./docs/TESTING_STRATEGY.md) | Test pyramid, coverage targets, and CI integration. |
 
-## 9. Development
+## 10. Development
 
 ```bash
 # Clone and install in editable mode with dev dependencies
@@ -425,15 +493,14 @@ See [Testing Strategy](./docs/TESTING_STRATEGY.md) for the full testing
 guide and [Contributing Guide](./docs/CONTRIBUTING.md) for development
 setup details.
 
-## 10. License
+## 11. License
 
 MIT
 
-## 11. Acknowledgements
+## 12. Acknowledgements
 
-`gd-tools` stands on the shoulders of two excellent community tools. It
-wraps them; it does not replace them. Full credit to their authors for the
-hard parts.
+`gd-tools` stands on the shoulders of excellent community tools, past and
+present. Full credit to their authors for the hard parts.
 
 - **[GUT (Godot Unit Test)](https://github.com/bitwes/Gut)** by
   [bitwes](https://github.com/bitwes): the GDScript test framework whose

{gd_tools_cli-0.6.0 → gd_tools_cli-0.8.0}/README.md

@@ -33,10 +33,11 @@ One install, one config, one mental model.
 | Feature | Description |
 |---------|-------------|
 | **Unified workflow** | One install, one config (`gd-tools.toml`), one mental model for test, lint, format, and coverage. Consistent terminal output with colored markers and summary footers across all commands. |
-| **Native test runtime** | Tests extend `GdToolsTest` and run inside Godot itself. Scene and resource integration tests reach the real scene tree through an explicit context object rather than a proxy. |
+| **Native test runtime** | Tests extend `GdToolsTest` and run inside Godot itself. Scene and resource integration tests reach the real scene tree through an explicit context object rather than a proxy. Doubles, partial doubles, and stubbing isolate collaborators; spy assertions cover calls, argument wildcards, call order, and property values. |
+| **Snapshot testing** | `assert_snapshot(value)` pins rendered values -- including object property dumps and node trees -- against versioned, diffable `.snap` files. First run writes and passes; mismatches fail with a unified diff, and `--snapshot-update` accepts the new output. |
 | **Zero-friction bootstrap** | `gd-tools init` gets a project fully set up in under a minute -- native test and coverage addons deployed, configs generated. |
-| **Coverage gap-filling** | Production-quality line and branch coverage for GDScript -- HTML, LCOV, and Cobertura reports that integrate with CI and code review tools. `# gd-tools: no cover` annotations exclude debug-only code from the numbers. `coverage run` collects coverage during manual playtest sessions, not just automated tests. |
-| **CI/CD friendly** | Exit codes, `--check` flags, machine-readable output (JSON, JUnit XML, LCOV, Cobertura), no interactive prompts in CI mode. |
+| **Coverage gap-filling** | Production-quality line and branch coverage for GDScript -- HTML, LCOV, Cobertura, and JSON reports, plus GitHub Actions annotations that surface failures inline on pull requests. Independent line (`--min`) and branch (`--min-branch`) gates. `# gd-tools: no cover` annotations exclude debug-only code from the numbers. `coverage run` collects coverage during manual playtest sessions, not just automated tests. Patch coverage (`coverage diff --patch`) reports coverage over only the lines a pull request changes, with its own gate and inline annotations. |
+| **CI/CD friendly** | Exit codes, `--check` flags, machine-readable output (JSON, JUnit XML, LCOV, Cobertura), and GitHub Actions annotations for lint violations and coverage gates. No interactive prompts in CI mode. |
 | **Standalone compatibility** | gdlint and gdformat continue to work if invoked directly. `gd-tools` is a layer on top, not a lock-in. |
 
 ## 3. Installation
@@ -99,13 +100,13 @@ func test_health_starts_at_full() -> void:
 |---------|-------------|
 | `gd-tools init` | Bootstrap a Godot project -- deploy the native test and coverage addons, generate configs. |
 | `gd-tools doctor` | Diagnose the development environment -- Godot, native test addon, coverage addon, tooling; reports legacy GUT artifacts as migration advice. |
-| `gd-tools test` | Run tests with optional coverage, thresholds, and JUnit XML output. Suites must extend `GdToolsTest`; `GutTest` suites are rejected with exit 2 and migration guidance. Accepts optional path arguments to override configured test directories. `--parallel N` runs suites through a bounded worker pool. `--changed` runs only the suites mapped from git-changed files. `--watch` re-runs affected suites on `.gd` file changes. Every run publishes a machine-readable artifact index under `.gd-tools/artifacts/<run_id>/`. |
+| `gd-tools test` | Run tests with optional coverage, thresholds, and JUnit XML output. Suites must extend `GdToolsTest`; `GutTest` suites are rejected with exit 2 and migration guidance. Accepts optional path arguments to override configured test directories. `--parallel N` runs suites through a bounded worker pool. `--changed` runs only the suites mapped from git-changed files. `--watch` re-runs affected suites on `.gd` file changes. `--durations N` reports the N slowest tests after the run. `--exitfirst` (`-x`) stops dispatching new suites after the first failing suite; `--shard K/N` runs one round-robin shard for CI matrix splitting. Every run publishes a machine-readable artifact index under `.gd-tools/artifacts/<run_id>/`. |
 | `gd-tools migrate` | Guided GUT-to-native migration. Default: read-only report with unsupported-construct inventory and proposed base-class rewrites. `--apply` renames clean suites to `GdToolsTest` and translates `.gutconfig.json` into `gd-tools.toml` (merge, never clobber). `--config-only` translates config only. |
-| `gd-tools lint` | Lint GDScript files using gdlint with text or JSON output. Accepts one or more file or directory paths. |
+| `gd-tools lint` | Lint GDScript files using gdlint with text, JSON, or GitHub Actions annotation output. Accepts one or more file or directory paths. |
 | `gd-tools format` | Format GDScript files using gdformat with check and diff modes. Accepts one or more file or directory paths. |
-| `gd-tools coverage` | Coverage subcommands -- `report`, `merge`, `show`, `save-baseline`, `diff` (baseline comparison for CI regression gates), and `run` (collect coverage during a manual playtest session). |
+| `gd-tools coverage` | Coverage subcommands -- `report`, `merge`, `show`, `save-baseline`, `diff` (baseline comparison for CI regression gates; with `--patch`, PR-scoped coverage over changed lines), and `run` (collect coverage during a manual playtest session). |
 | `gd-tools config` | Configuration management -- `show` (display resolved config), `validate` (check config validity), `schema` (print or write the JSON Schema for `gd-tools.toml`). |
-| `gd-tools version` | Display versions of all gd-tools components (gd-tools, Godot, gdtoolkit, Python, and GUT when installed) in a table or JSON. |
+| `gd-tools version` | Display versions of all gd-tools components (gd-tools, Godot, gdtoolkit, Python) in a table or JSON. |
 | `gd-tools completion` | Generate shell completion scripts for bash, zsh, fish, or PowerShell. |
 
 ### Selecting and Filtering Tests
@@ -117,8 +118,11 @@ gd-tools test --test test_takes_damage     # one test method
 gd-tools test --tag smoke                  # suites with that class-level tag
 gd-tools test --test-timeout 30            # per-test timeout, in seconds
 gd-tools test --parallel 4                 # run suites with 4 concurrent workers
+gd-tools test --durations 10               # report the 10 slowest tests
 gd-tools test --changed                    # only suites mapped from git-changed files
 gd-tools test --changed --base main        # PR/CI mode: diff from merge-base with main
+gd-tools test --exitfirst                  # stop dispatching after the first failing suite
+gd-tools test --shard 2/4                  # CI sharding: run suite shard 2 of 4
 ```
 
 `--tag` is repeatable, and `--test-timeout` (per test) is separate from
@@ -127,6 +131,13 @@ worker pool (1-32 workers; bare `--parallel` means 4) while keeping results,
 JUnit XML, and merged coverage identical to a sequential run. Persist the
 choice with `parallel = 4` under `[test]` in `gd-tools.toml`.
 
+`--durations N` prints a "Slowest Tests" table after the run, sorted
+slowest-first, covering pass, fail, and skip outcomes. Bare `--durations`
+means 10; `--durations 0` lists every executed test (pytest parity). Persist
+the choice with `durations = 10` under `[test]` in `gd-tools.toml`; the flag
+overrides the config for one invocation. The table renders identically under
+`--watch` re-runs and `--parallel` runs.
+
 `--changed` selects suites from git instead of running everything: uncommitted
 changes (staged, unstaged, and untracked) map to suites by the same
 file→suite convention as `--watch` — `src/enemy.gd` selects
@@ -140,6 +151,29 @@ pull-request CI. `--changed` composes with `--parallel`, `--coverage`, and
 the `--suite`/`--test`/`--tag` filters (the active filters bound the
 mapping domain); an empty change set exits 0 without launching Godot.
 
+`--exitfirst` (short form `-x`) stops dispatching **new** suites after the
+first suite whose final result is a failure — a test failure or an
+infrastructure error. In-flight suites finish and are collected; suites that
+were never started are reported as skipped (`not_run`) and summarized in a
+`Stopped early: fail-fast after suite <id> (K of M suites skipped)` line.
+Passes and skips never trigger the gate, and a suite that passes after a
+retry does not either — only final suite results decide. The exit code stays
+1 for test failures. `--exitfirst` composes with `--parallel` (the pool
+drains instead of killing workers), with `--coverage` (the report covers the
+suites that ran, labeled partial when plan targets went unmeasured), and with
+`--watch` (the gate resets for every re-run).
+
+`--shard K/N` runs only the suites assigned to shard `K` of `N` — suite *i*
+of the deterministic plan order belongs to shard `(i mod N) + 1` — for
+splitting one test run across CI jobs. Selection happens after `--changed`
+filtering and before `--parallel`, so each flag keeps exactly one job.
+`--shard 1/1` is valid and equivalent to no sharding; malformed values
+(`--shard 4/3`, `--shard 3`) exit 2 before any work. Each shard produces its
+own coverage report; merge the shards with `gd-tools coverage merge`.
+`--shard` and `--watch` are rejected together (exit 2). See the
+[sharding recipe](./docs/USER_GUIDE.md#sharding-a-test-run-across-ci-jobs)
+for a GitHub Actions matrix example.
+
 Repeat runs are faster: the `godot --headless --import` step is cached under
 `.gd-tools/native/import-cache/` and skipped when `project.godot`, any
 project source/resource file (scripts, scenes, import sidecars, addons), or
@@ -278,7 +312,41 @@ eval "$(gd-tools)"
 See the [User Guide](./docs/USER_GUIDE.md) for detailed per-shell
 instructions.
 
-## 7. Configuration
+## 7. Pre-commit Hooks
+
+Wire gd-tools into the [pre-commit](https://pre-commit.com) framework so
+every commit runs your format check, lint, and (optionally) your test suite:
+
+```bash
+gd-tools install-hooks
+```
+
+The command generates `.pre-commit-hooks.yaml` and merges a `repos: local:`
+entry into `.pre-commit-config.yaml`. Existing hooks — including your own —
+are preserved; re-runs update only the gd-tools entries in place.
+
+Interactive by default: confirm each hook (`format`, `lint`, `test`). For
+scripted or CI use, pass flags instead:
+
+```bash
+gd-tools install-hooks --non-interactive      # format + lint (defaults)
+gd-tools install-hooks --all                  # format + lint + test
+gd-tools install-hooks --hooks format,lint    # explicit selection
+```
+
+| Flag | Behavior |
+|---|---|
+| `--all` | Enable every hook (format, lint, test). |
+| `--hooks HOOKS` | Comma-separated selection, e.g. `--hooks format,lint`. |
+| `--non-interactive` | Never prompt; use defaults or explicit flags. |
+
+Exit codes follow the gd-tools convention: `0` installed, `1` nothing to do,
+`2` config/environment error.
+
+See the [User Guide](./docs/USER_GUIDE.md#8-pre-commit-hooks) for the
+generated file contents and per-hook details.
+
+## 8. Configuration
 
 `gd-tools` uses a single `gd-tools.toml` file as the source of truth for
 all tool configuration. `gd-tools init` generates this file with sensible
@@ -292,10 +360,9 @@ binary = ""  # Optional -- auto-detected if unset
 test_dirs = ["test", "tests"]
 prefix = "test_"
 suffix = ".gd"
-gutconfig = ".gutconfig.json"  # legacy; not read by any runtime
 runtime = "native"        # native (default); "gut" is no longer a runnable runtime
 timeout_seconds = 5.0     # default per-test timeout for async native tests
-retries = 0               # opt-in retries per native test
+retries = 0               # opt-in retries per native test; retried passes are flagged as flaky
 # parallel = 4            # opt-in parallel suite execution (1-32; unset runs sequentially)
 tags = []                 # native suite tag filters
 
@@ -343,7 +410,7 @@ version's config model.
 See the [User Guide](./docs/USER_GUIDE.md) for a full configuration reference
 with all keys, defaults, and examples.
 
-## 8. Documentation
+## 9. Documentation
 
 | Document | Description |
 |----------|-------------|
@@ -354,7 +421,7 @@ with all keys, defaults, and examples.
 | [Roadmap](./docs/ROADMAP.md) | Release phases and milestones. |
 | [Testing Strategy](./docs/TESTING_STRATEGY.md) | Test pyramid, coverage targets, and CI integration. |
 
-## 9. Development
+## 10. Development
 
 ```bash
 # Clone and install in editable mode with dev dependencies
@@ -384,15 +451,14 @@ See [Testing Strategy](./docs/TESTING_STRATEGY.md) for the full testing
 guide and [Contributing Guide](./docs/CONTRIBUTING.md) for development
 setup details.
 
-## 10. License
+## 11. License
 
 MIT
 
-## 11. Acknowledgements
+## 12. Acknowledgements
 
-`gd-tools` stands on the shoulders of two excellent community tools. It
-wraps them; it does not replace them. Full credit to their authors for the
-hard parts.
+`gd-tools` stands on the shoulders of excellent community tools, past and
+present. Full credit to their authors for the hard parts.
 
 - **[GUT (Godot Unit Test)](https://github.com/bitwes/Gut)** by
   [bitwes](https://github.com/bitwes): the GDScript test framework whose

{gd_tools_cli-0.6.0 → gd_tools_cli-0.8.0}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "gd-tools-cli"
-version = "0.6.0"
+version = "0.8.0"
 description = "A modern development workflow CLI for GDScript projects in Godot 4.5+"
 readme = "README.md"
 license = {text = "MIT"}
@@ -49,6 +49,7 @@ Documentation = "https://github.com/mansyar/gd-tools#readme"
 dev = [
     "pytest",
     "pytest-cov",
+    "pytest-xdist",
     "ruff==0.15.21",
     "black",
     "commitizen",
@@ -71,6 +72,10 @@ where = ["src"]
 
 [tool.pytest.ini_options]
 testpaths = ["tests"]
+# Import gd_tools from this checkout's src/ rather than any globally
+# installed (editable) copy, so worktrees and CI checkouts always test
+# their own tree.
+pythonpath = ["src"]
 markers = [
     "unit: Unit tests for individual modules.",
     "integration: Integration tests for command flows.",
@@ -105,7 +110,7 @@ target-version = ["py310"]
 
 [tool.commitizen]
 name = "cz_conventional_commits"
-version = "0.6.0"
+version = "0.8.0"
 version_files = ["pyproject.toml:version"]
 changelog_file = "CHANGELOG.md"
 tag_format = "v$version"