enumeray connector cleanup

Inspect or reclaim eligible completed data on connector and compute hosts.

Use when: Delivered runs leave staging, workspaces, transfer copies, outputs or logs to reclaim, or an interrupted cleanup needs resuming.

Role and prerequisites: Connector host operator with access to the original private journal. Dry-run can inspect an active service without taking its journal lock. Stop the service before applying manual cleanup. Matching compute-runner binaries, retained connection credentials and access to the original compute host are needed for remote cleanup; no API/database credential is required.

Example

enumeray connector cleanup --journal ./connector-state/journal --dry-run --limit 8
# Stop the connector service before applying the manual pass.
enumeray connector cleanup --journal ./connector-state/journal --limit 8

Relative journal paths are supported. Default completed retention is zero seconds. Deletion needs the service run-directory reservation capability and saved installation-protection inventory; an older service or missing protection evidence retains payloads while execution continues. Unknown or unseeded host protection blocks payload deletion across the connector. Successfully protected bindings can still be pruned independently during configuration reconciliation. Active or uncertain execution, pending delivery and live transfer ownership also block deletion. Legacy overlapping releases remain protected. Published object versions, installed releases, shared roots and site-owned files are outside connector cleanup.

Inputs and options

Input	Meaning and use
--journal <JOURNAL>	Private durable journal directory. Reuse the same path after restart and never copy it to create another active connector. It contains ownership and backend execution evidence.
--dry-run	Read cleanup candidates and blocked reasons without deleting files, writing cleanup progress or taking the journal process lock. Safe while the service is running.
--limit <LIMIT>	Maximum archived assignments reported or unfinished cleanup items attempted by one pass; default 8. Repeat bounded passes to resume interrupted cleanup or reclaim further eligible data.
--completed-retention-seconds <COMPLETED_RETENTION_SECONDS>	Retention before reclaiming eligible completed run data; default 0 seconds. Eligibility still requires confirmed execution release and final delivery, independently of unpublished-output deadlines.

Host commands use explicit connector credentials or the private journal and emit JSON results; compute-runner uses only its stdin protocol and directory. User profile and API override options do not apply.

Result and next step

Reports eligibility, retention, reclaimed data and blocked reasons; an applied pass records durable progress and preserves archived evidence and launch replay guards.

Applying cleanup resumes a durable queue of unfinished runs. An upgrade discovers legacy archives once in bounded passes; blocked and partially cleaned runs stay queued for retry. Completed runs leave the queue while their archive, compact checkpoint and replay guards remain. Fresh installation protection is checked on every deletion attempt; permanent per-run checkpoints retain the delivery authority and progress without copying the full installation inventory.

Repeat bounded passes as needed, or restart the service for automatic cleanup. Keep uncertain or unavailable work for evidence-based recovery.

Exact syntax, defaults and accepted values

Reclaim confirmed, delivered run payloads; preserve evidence and launch fences

Usage: enumeray connector cleanup [OPTIONS] --journal <JOURNAL>

Options:
      --api <API>
          User API origin override; credentials never cross origins. Host/runner commands use explicit configuration
      --journal <JOURNAL>
          Existing private durable journal; dry-run inspection may run while its service owns it
      --dry-run
          Inspect eligibility and payload usage without changing durable state
      --profile <PROFILE>
          Named local user API/login profile; host/runner commands use explicit configuration [default: default]
      --config <CONFIG>
          Private user profiles file; defaults to $XDG_CONFIG_HOME/enumeray/profiles.json or ~/.config/enumeray/profiles.json
      --limit <LIMIT>
          Maximum archived assignments reported or unfinished cleanup items attempted (1-64) [default: 8]
      --completed-retention-seconds <COMPLETED_RETENTION_SECONDS>
          Keep safely completed payloads for this optional debugging grace period [default: 0]
      --json
          Emit user API results as JSON (NDJSON for following logs) and runtime errors on stderr; host/runner output follows its own protocol
      --timeout <TIMEOUT>
          User API HTTP timeout in seconds; live logs use it for read inactivity. Does not limit execution time [default: 60]
  -h, --help
          Print help