From ed108bf72b93ac54ca8ef36bf07b52c7ea4357ab Mon Sep 17 00:00:00 2001 From: joeVenner Date: Thu, 6 Aug 2026 21:42:22 +0100 Subject: [PATCH 1/2] docs(fly): drop smoke commands that were never implemented fly/README.md documents `npm run smoke:fly` and `npm run smoke:x`, and env vars X_SMOKE_REQUIRE_AUTH / X_SMOKE_REQUIRE_FIREHOSE that go with them. Neither script is defined in any package.json, and `git log -S` shows neither has ever been defined in this repo's history. The two env vars appear nowhere outside this file. There is no corresponding scripts/fly-smoke.ts either, so the paragraph describing what "the smoke test" backs up and restores documents a run nobody can perform. Removed rather than corrected because there is no correct name to point at. The `npm run smoke:git-cli` block below is real and is left alone. --- fly/README.md | 21 --------------------- 1 file changed, 21 deletions(-) diff --git a/fly/README.md b/fly/README.md index 10a4b645..bf311cae 100644 --- a/fly/README.md +++ b/fly/README.md @@ -177,27 +177,6 @@ For resident X tooling use the same prefix for native tool env, for example ## Smoke test -```bash -FLY_API_TOKEN="$(fly tokens create deploy -a "$FLY_SANDBOX_APP_NAME")" npm run smoke:fly -``` - -For image-resident X helper readiness: - -```bash -FLY_API_TOKEN=... npm run smoke:x -``` - -This verifies `x-api` is on PATH and reports `missing_auth=auth_missing` when no -resident X token is installed. Add `X_SMOKE_REQUIRE_AUTH=1` after configuring -`X_BEARER_TOKEN` / `X_ACCESS_TOKEN`, or `X_SMOKE_REQUIRE_FIREHOSE=1` when a vendored -`x-firehose` binary should be present. - -The smoke test uses a timestamped personal smoke-test scope, writes -workspace and resident-home state, backs it up, deletes the Fly machine, recreates it, -restores the backup, verifies `.aws/*` stayed excluded, then deletes the smoke -machine. Add `SNAPSHOT_STORE=s3 S3_BUCKET=...` to exercise the real S3 object store; -without those vars it uses the same backup-store code over an in-memory blob store. - For GitHub/GitLab resident CLI readiness: ```bash From 5abf8b6a663e6e278968fd9758f11858b5a31b5a Mon Sep 17 00:00:00 2001 From: joeVenner Date: Thu, 6 Aug 2026 21:42:34 +0100 Subject: [PATCH 2/2] ci: verify documented npm commands exist MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The stale `npm run smoke:fly` / `npm run smoke:x` blocks removed in the previous commit sat in fly/README.md indefinitely because nothing checks that a command shown in the docs is a command you can run. Every other class of rot here has a gate — knip for dead code, oxlint and eslint for source, prettier for formatting — so add the equivalent for documented commands and run it in the lint job alongside them. The check reads every tracked *.md, extracts each `npm run