@gfdelarue/testkit 0.3.5 → 0.3.6

package/README.md

@@ -7,7 +7,9 @@
 `@gfdelarue/testkit` is the orchestrator and managed distribution for product test
 suites. It discovers `*.testkit.ts` files, infers suite ownership from the
 filesystem, starts local services, provisions Docker-managed local Postgres
-databases, schedules suites, and collects results and artifacts.
+databases, schedules suites, and collects results and artifacts. Coding agents
+use it to write tests and hunt bugs, and CI uses it to run those tests. It needs
+no account or server.
 
 Testkit exists to replace false confidence with inspectable execution evidence.
 It cannot prove that an entire application works. It can make narrower claims
@@ -47,33 +49,6 @@ Testkit writes the immutable, verifiable run bundle under
 `.testkit/results/runs/<run-id>/`. Upload `.testkit/results` with `if: always()`
 when CI evidence should survive a failed job.
 
-Publishing that evidence to Testkit Cloud is an additional explicit step. Set
-`TESTKIT_CLOUD_PROJECT_ID` and the secret `TESTKIT_CLOUD_TOKEN`, then run:
-
-```bash
-npx testkit cloud publish
-```
-
-The command verifies the immutable bundle before upload. Ordinary runs never
-contact Cloud, and the presence of `CI` does not authorize publication.
-
-## Connect to Cloud
-
-For interactive use, approve your CLI through the browser once:
-
-```sh
-npx testkit cloud login
-npx testkit cloud project create
-npx testkit cloud publish --project PROJECT_ID --run RUN_ID
-```
-
-Login works outside Git. Project creation infers the repository from Git origin
-or accepts `--repository owner/repo`. It resumes after any required provider
-consent. `cloud list`, `cloud show`, and `cloud apply --file` provide discovery,
-settings and product control. See the [Cloud control boundary](docs/testkit-cloud-boundary.md#complete-cloud-control)
-and [complete operation reference](https://github.com/gfdelarue/testkit-cloud/blob/master/docs/cloud-control.md).
-Explicit `TESTKIT_CLOUD_TOKEN` still takes precedence over the saved account.
-
 ## Execution engines
 
 Testkit has three explicit built-in engines rather than one implicit runtime:
@@ -219,40 +194,9 @@ Batch `run` output stays intentionally short: one line per completed file,
 concise failure blocks, and a final summary. Service logs, captured runtime
 output, and emitted artifacts are persisted under `.testkit/results/`.
 
-Testkit produces an immutable local run bundle and, when requested, a Cloud
-publication receipt. `testkit run` prints `Run ID: <id>` after sealing in text
-output and returns `runId` in `--json` output, for passed and failed runs.
-Publish that exact evidence with `testkit cloud publish --run <id>`. Omitting
-`--run` selects the newest bundle for interactive use. Historical summaries
-and trends belong to Testkit Cloud.
-
-For CI, preserve the run exit status and publish the ID from that invocation:
-
-```sh
-run_exit=0
-testkit run --json > testkit-run.json || run_exit=$?
-run_id=$(node -e 'const r = JSON.parse(require("node:fs").readFileSync("testkit-run.json", "utf8")); if (typeof r.runId !== "string" || !r.runId) process.exit(1); process.stdout.write(r.runId)') || {
-  if [ "$run_exit" -ne 0 ]; then exit "$run_exit"; fi
-  exit 1
-}
-publish_exit=0
-testkit cloud publish --run "$run_id" || publish_exit=$?
-if [ "$publish_exit" -ne 0 ]; then
-  echo "Cloud publication failed with exit $publish_exit" >&2
-fi
-exit "$run_exit"
-```
-
-Set `TESTKIT_CLOUD_PROJECT_ID` and `TESTKIT_CLOUD_TOKEN` in the CI environment.
-`TESTKIT_CLOUD_URL`, or the `--url` flag on `cloud publish`, `cloud apply`, and
-`cloud snapshot`, changes the Testkit Cloud origin. The bearer token and the
-run bundle are sent only to that origin, so protect the variable like the
-token itself. Leave it unset to use `https://testkit.cloud`.
-A failed run can still publish a valid sealed bundle. Publication reports its
-own exit status and does not change the test outcome. This recipe reports a
-publication failure and retains the run status as the job status. See the
-[Cloud boundary](docs/testkit-cloud-boundary.md) and
-[breaking-change migration](https://github.com/gfdelarue/testkit/blob/master/docs/release-notes.md).
+Testkit seals an immutable local run bundle. `testkit run` prints
+`Run ID: <id>` after sealing in text output and returns `runId` in `--json`
+output, for passed and failed runs.
 
 Test execution also maintains a scheduler cache at `.testkit/timings.json`.
 Completed file-level task durations are used to rank future runs with a
@@ -653,16 +597,6 @@ Programmatic consumers can import `listRunBundles`, `loadRunBundleArtifact`,
 `loadRunBundleManifest`, and `verifyRunBundle` from
 `@gfdelarue/testkit/workspace`.
 
-The run bundle is also the boundary for Testkit Cloud. The local runner never
-reads regression state or mutates GitHub. See
-[`docs/testkit-cloud-boundary.md`](docs/testkit-cloud-boundary.md) for ownership,
-ingestion, and migration rules.
-
-Use `testkit cloud snapshot` to read versioned Cloud regression state. Apply
-reviewed mutations from a file with `testkit cloud apply --file commands.json`;
-the file must contain a schema version, idempotency key, expected snapshot
-version, and commands.
-
 ## Authoring
 
 ### Node setup beside a test
@@ -1039,7 +973,7 @@ identifier plus canonical metadata such as:
 - `dependsOn`
 - `displayName`
 
-For cross-run counts, last outcomes, durations, or trends, use Testkit Cloud.
+Discovery output has no cross-run counts, last outcomes, durations, or trends.
 See the [status and history migration](https://github.com/gfdelarue/testkit/blob/master/docs/release-notes.md#local-status-and-history-removal)
 for the removed discovery fields and consumer migration.
 

package/dist/process/execa-bundle.json

@@ -3,7 +3,7 @@
   "entrypoint": "dist/process/process.js",
   "sourceSha256": "a54f01864b603cee568b2945390dff35d578e07f6d26b5add06014169c3d17b0",
   "bundleSha256": "62f76cf9fd019f6c552bfde2787f058917caf279670a62e7a6bfa12be34cb4b1",
-  "packageLockSha256": "93deb1e48aab38546ad53118a260f78c22f023ebd9a215d52953481c716d5d1b",
+  "packageLockSha256": "c0f28403d05b2838f4d0d104862548469ad7cc74e1aeb9fb9a33c7df856d7f5b",
   "esbuildVersion": "0.28.1",
   "options": {
     "format": "esm",

package/docs/cloud-control.md

@@ -1,5 +1,8 @@
 # Cloud command reference
 
+The `testkit cloud` commands are deprecated. See the
+[Cloud boundary](testkit-cloud-boundary.md) for the direction.
+
 `testkit cloud apply --help` prints the account-command envelope, every supported
 operation, its scope IDs, and its input fields. This reference ships with Testkit.
 

package/docs/testkit-cloud-boundary.md

@@ -1,8 +1,10 @@
 # Testkit Cloud boundary
 
-The local Testkit runner owns execution through publication of an immutable run
-bundle. Testkit Cloud owns organisation-wide history, regression state, release
-policy, and GitHub automation.
+The `testkit cloud` commands are deprecated. Testkit works without Cloud, and
+bugs and evidence stay in your repository and in GitHub or Gitea. Testkit Cloud
+is becoming an optional analytics dashboard that reads facts from GitHub or
+Gitea instead of receiving run bundles. This document describes the commands
+and the publication contract that still ship.
 
 ```text
 discover -> prepare -> execute -> seal and verify run bundle -> clean up
@@ -13,13 +15,11 @@ discover -> prepare -> execute -> seal and verify run bundle -> clean up
                            Testkit Cloud ingest
 ```
 
-## Complete Cloud control
+## Cloud commands
 
-The CLI is a full control client for Cloud. New or changed product operations
-ship their API, installed command or file input, and acceptance coverage together.
 The local [Cloud command reference](cloud-control.md) lists supported operations
 and file fields. `testkit cloud apply --help` includes the account-command format.
-Cloud continues to own identity, permissions, product state and domain validation.
+Cloud checks identity, permissions, and domain rules on every command.
 
 ```sh
 testkit cloud login
@@ -176,13 +176,13 @@ The token is an environment secret. It is not stored in `testkit.config.ts` or
 accepted as a command flag. `CI` is execution context only; it does not enable
 publication or supply authority.
 
-## Cloud ownership
+## Cloud ingestion
 
-Testkit Cloud may ingest a verified bundle and derive regression identities,
+Testkit Cloud ingests a verified bundle and derives regression identities,
 baselines, comparisons, recommendations, GitHub checks, and issue lifecycle
 actions. Cloud state is separate from the product repository and may be shared
-across repositories. Cloud must retain the source bundle identity for every
-derived decision so a user can trace a check or issue back to its evidence.
+across repositories. Cloud keeps the source bundle identity for every derived
+decision.
 
 Cloud ingestion uses an explicit versioned contract. It rejects an invalid
 bundle, preserves the underlying run outcome, and reports GitHub projection
@@ -197,21 +197,9 @@ The old `./regression-workflow` package export, runner integration,
 Git retains their implementation history, but that does not migrate a
 consumer's live state.
 
-Before a Testkit package containing this removal is published:
-
-1. Inventory known uses of the removed export and state file.
-2. Assign each consumer an owner and decide whether to discard or import its
-   stored state.
-3. Rehearse required consumers against the exact packed candidate.
-4. Block publication when a required consumer cannot move atomically.
-
-The removed implementation is useful source material for Testkit Cloud, but it
-must not be copied back into the runner. Cloud should consume verified bundles
-through its own adapter and own its persistence and GitHub credentials.
-
 ## Report an externally executed campaign
 
-Cloud owns campaign state, finding verification, and counts. A user or agent
+Cloud keeps campaign state, finding verification, and counts. A user or agent
 starts and runs the investigation independently. These commands never start
 execution or infer a finding from a failed assertion.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@gfdelarue/testkit",
-  "version": "0.3.5",
+  "version": "0.3.6",
   "description": "Test orchestration platform for product acceptance and QA workflows",
   "license": "SEE LICENSE IN LICENSE",
   "type": "module",

package/testkit-config-schema.md

@@ -758,6 +758,8 @@ cloud?: {
 };
 ```
 
+This setting is deprecated with the `testkit cloud` commands.
+
 `cloud.verification.minimumConfirmingRuns` is an integer from 1 through 64,
 defaulting to 2. It controls whether Testkit submits a new `finding.verify`
 campaign report. It counts distinct full run IDs from available cited accepted