Merge remote-tracking branch 'origin/claude/discovery-index-cloudflare-container' into claude/discovery-index-cloudflare-container

Author: JSONbored

.claude/skills/contributing-to-loopover/SKILL.md

@@ -202,7 +202,7 @@ Run the matching command(s) and **commit the regenerated file(s)** — CI fails
 | A Cloudflare binding/var in `wrangler.jsonc` | `npm run cf-typegen` | `worker-configuration.d.ts` |
 | Drizzle schema (`src/db/schema.ts`) | `npm run drizzle:generate` | the new `migrations/NNNN_*.sql` |
 | Added a raw-SQL migration | (none — just author it) | next **contiguous** `migrations/NNNN_snake.sql` |
-| `src/selfhost/**` (or a few other scanned files — see `scripts/gen-selfhost-env-reference.mjs`'s `DEFAULT_SOURCE_ROOTS`) adding/removing an `env.SOMETHING` read | `npm run selfhost:env-reference` | `apps/loopover-ui/src/lib/selfhost-env-reference.ts` — the doc cites the file only (not `file:line`, deliberately, so an unrelated line shift elsewhere in the file never makes this go stale) |
+| `src/selfhost/**` (or a few other scanned files — see `scripts/gen-selfhost-env-reference.ts`'s `DEFAULT_SOURCE_ROOTS`) adding/removing an `env.SOMETHING` read | `npm run selfhost:env-reference` | `apps/loopover-ui/src/lib/selfhost-env-reference.ts` — the doc cites the file only (not `file:line`, deliberately, so an unrelated line shift elsewhere in the file never makes this go stale) |
 | CLI command surface | `npm run command-reference` | the generated command-reference doc |
 | UI files (`apps/loopover-ui/**`) | `npm --workspace @loopover/ui run format` | formatted files |
 
@@ -221,9 +221,9 @@ npm audit --audit-level=moderate          # the dependency-review job's local eq
 
 `npm run test:ci` runs, and must pass, **all of**: `actionlint`, `db:migrations:check`,
 `db:schema-drift:check`, `selfhost:env-reference:check`, `selfhost:validate-observability`,
-`cf-typegen:check`, `build:mcp:check`, `build:miner:check`, `typecheck`, `test:coverage`, `test:engine-parity`, `test:live-gate-parity`, `test:driver-parity`, the
-`@loopover/engine` workspace's own test run, `test:workers`, `test:mcp-pack`,
-`test:miner-pack`, `rees:test`, `ui:openapi:check`, `ui:openapi:settings-parity`,
+`cf-typegen:check`, `typecheck`, `test:coverage`, `test:engine-parity`, `test:live-gate-parity`, `test:driver-parity`, the
+`@loopover/engine` workspace's own test run, `test:workers`, `build:mcp`, `test:mcp-pack`,
+`build:miner`, `test:miner-pack`, `rees:test`, `ui:openapi:check`, `ui:openapi:settings-parity`,
 `ui:version-audit`, `docs:drift-check`, `manifest:drift-check`, `engine-parity:drift-check`,
 `command-reference:check`, `ui:lint`, `ui:typecheck`, `ui:test`, `ui:build`. If any step fails, fix it
 and re-run — do not push a red tree. (Full per-check table in `reference.md`; check `package.json`'s

.claude/skills/contributing-to-loopover/reference.md

@@ -40,6 +40,13 @@ jobs run only if their path filter matched; on push to `main`, everything runs.
 | mcp → pack | tarball hygiene | `npm run test:mcp-pack` | unexpected/forbidden file or stale README in the npm tarball |
 | miner → build | miner engine/pkg build | `npm run build:miner` | `@loopover/{engine,miner}` build error |
 | miner → pack | tarball hygiene | `npm run test:miner-pack` | unexpected/forbidden file in the miner npm tarball |
+
+`packages/loopover-{miner,mcp}` are `.ts`-only in git: editing their `bin`/`lib` source means editing `.ts`
+and nothing else — the compiled `.js`/`.d.ts` these two `build` commands produce is gitignored, never
+committed, and never something a PR needs to touch. Tests (in-process imports and the CLI-harness
+subprocess spawns alike) run straight off the `.ts`; `build:mcp`/`build:miner` above exist only to
+validate the real publishable artifact still compiles and packs cleanly.
+
 | rees → test | review-enrichment-service's own suite | `npm run rees:test` | any failing test under `review-enrichment/` |
 | ui → openapi drift | spec check | `npm run ui:openapi:check` | committed `openapi.json` is stale (run `npm run ui:openapi`) |
 | ui → openapi settings-parity | schema/type structural diff | `npm run ui:openapi:settings-parity` | `RepositorySettingsSchema` (src/openapi/schemas.ts) is missing a field the `RepositorySettings` type has |
@@ -60,7 +67,7 @@ jobs run only if their path filter matched; on push to `main`, everything runs.
 Every `vitest.config.ts` in the repo (root, `vitest.workers.config.ts`, and every workspace with its own
 config) wires this as `globalSetup`, so it runs once before any test file regardless of how vitest was
 invoked — including a direct `npx vitest run test/unit/<file>.test.ts`, which this doc's own §6 ("Iterate,
-then verify") recommends for fast iteration. `scripts/check-node-version.mjs`'s `pretest*` hooks
+then verify") recommends for fast iteration. `scripts/check-node-version.ts`'s `pretest*` hooks
 (`package.json`) only cover 5 high-traffic npm script names (`test`, `test:ci`, `test:coverage`,
 `test:workers`, `ui:test`) as a genuinely-faster fail there (before npm even spawns vitest) — they are a
 nicety on top of the globalSetup guarantee, not a substitute for it. An earlier version of this guard was

.dockerignore

@@ -12,7 +12,7 @@ dist-ssr
 coverage
 .git
 .claude
-# The self-host bundle's only entry point is src/server.ts (scripts/build-selfhost.mjs) and `npm ci`
+# The self-host bundle's only entry point is src/server.ts (scripts/build-selfhost.ts) and `npm ci`
 # only ever sees the root package*.json (copied before the rest of the tree) — the loopover-ui
 # workspace app and the test suite are never read during the image build, so keep both out of the
 # build context entirely (measured: ~11MB of this repo's ~22MB tracked-file footprint).
@@ -26,7 +26,7 @@ auth.json
 **/auth.json
 # The review-enrichment service (REES) is a separate Railway service with its own Dockerfile — keep it out of
 # the engine image. EXCEPT analyzer-metadata.json: the main engine's own code (src/review/enrichment-analyzers-
-# taxonomy.ts) imports it directly, so excluding it wholesale breaks `scripts/build-selfhost.mjs`'s esbuild
+# taxonomy.ts) imports it directly, so excluding it wholesale breaks `scripts/build-selfhost.ts`'s esbuild
 # bundle (module resolution failure at build time, not a runtime gap -- caught by the "build + boot smoke test"
 # workflow, which is path-gated and doesn't run on every PR).
 review-enrichment

.github/workflows/ci-duration-report.yml

@@ -33,7 +33,7 @@ jobs:
       - name: Pull ci.yml run stats
         env:
           GITHUB_TOKEN: ${{ github.token }}
-        run: node scripts/ci-duration-report.mjs --days=7 --output=ci-duration-report.json
+        run: node --experimental-strip-types scripts/ci-duration-report.ts --days=7 --output=ci-duration-report.json
       - name: Write summary
         run: |
           node <<'NODE'