fix: exclude .tmp-*.gtfs.zip from the GTFS archive scan

`scanGtfsArchives` matched any path ending in `.gtfs.zip`, including the `.tmp-<id>.gtfs.zip` files gtfsclean writes mid-cleanup before atomic-renaming to the published name. On a failed pipeline run the tmp file's recent mtime made the resume path classify it as "freshly downloaded" and upsert a `.tmp-<id>` entry into the dataset registry. After the eventual successful rename, the stale tmp entry lingered alongside the real one. Tighten the pattern to require a non-dot first character so dotfile-prefixed working files never enter the registry or the prune sweeps. Also closes a subtle data-loss window where pruneFeedsOutsideCountryFilter would wipe a `.tmp-de_DELFI.gtfs.zip` mid-rename if the country prefix didn't match.

Author: Medformatik

services/data-manager/src/jobs/transitous-pipeline.ts

@@ -18,7 +18,12 @@ export const DEFAULT_TRANSITOUS_REPO_URL = "https://github.com/public-transport/
 export const DEFAULT_TRANSITOUS_API_KEYS_PATH = "/config/transitous/api-keys.json";
 const TRANSITOUS_CATALOG_DIR = ".transitous-catalog";
 const TRANSITOUS_DOWNLOADS_DIR = ".transitous-downloads";
-const GTFS_ARCHIVE_RE = /\.(gtfs|netex)\.zip$/i;
+// Match published GTFS / NeTEx archives only. `.tmp-*.gtfs.zip` and any
+// other dotfile-prefixed name is excluded — gtfsclean writes its working
+// output as `.tmp-<id>.gtfs.zip` and renames atomically at the end, so a
+// half-written tmp file should never end up in the dataset registry or
+// the prune scans (where its mid-rename mtime would briefly look "fresh").
+const GTFS_ARCHIVE_RE = /^[^.][^/]*\.(gtfs|netex)\.zip$/i;
 
 type CommandRunner = (
   command: string,