feat(run-global-import): scope a global import to a single site, with an optional --force

[jindaliiita]

What

Extends the existing run global import Slack command with:

1. An optional [site-url-or-id] argument to scope a global import to a single site instead of scanning all data.
2. An optional --force flag (requires a site) telling the target handler to skip its normal gating check — used by optimize-at-edge-enabled-marking to enable a site on the edge request-id check alone, skipping prerender content validation.

Usage:

run global import optimize-at-edge-enabled-marking <site-url-or-id>            # single-site check
run global import optimize-at-edge-enabled-marking <site-url-or-id> --force    # force-enable, skip validation
run global import stale-suggestions-cleanup                                     # unchanged bulk behavior

Why

The hourly optimize-at-edge-enabled-marking job only ran across all sites. Operators need to:

• Re-check a single site on demand (testing/triage) without waiting for the hourly cron.
• Force-enable a specific site immediately when prerender content validation isn't ready or relevant yet, based on the edge request-id check alone.

Note on history: this PR originally added a standalone force-optimize-at-edge-enable Slack command for the force-enable case. That's been folded into run global import ... --force instead — avoids two near-identical commands and reuses the same site-resolution code path (the standalone command's add-then-remove is visible in this branch's commit history but nets to zero in the diff).

Change

• src/support/slack/commands/run-global-import.js: parses an optional site (URL or ID) and a --force flag out of the args (in any order); resolves the site via Site.findByBaseURL/Site.findById; rejects --force without a site (it would otherwise silently no-op on a bulk run); passes { siteId, force, forcedBy: <slack user> } through.
• src/support/utils.js: sendGlobalImportRunMessage / triggerGlobalImportRun now take a trailing options object ({ siteId, force, forcedBy }) instead of a lone siteId param.

Cross-repo

Pairs with spacecat-import-worker PR #813, which added siteId/force/forcedBy support directly to the optimize-at-edge-enabled-marking handler (single-site runs skip the daily-dedup and MAX_SITES_PER_RUN cap; force skips prerender validation only — the already-enabled idempotency guard still applies unconditionally) and removed the now-redundant standalone force-optimize-at-edge-enabled-marking handler.

Tests

• New/updated unit tests for sendGlobalImportRunMessage / triggerGlobalImportRun covering siteId/force/forcedBy inclusion and omission.
• run-global-import.js itself stays c8 ignore'd, consistent with its pre-existing convention (no dedicated test file before or after this PR).
• Full Slack-commands test suite (test/support/slack/commands/**): 852 passing. utils.test.js: 129 passing. Lint clean.

🤖 Generated with Claude Code

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[MysticatBot]

Hey @jindaliiita,

⚠ Degraded review - no spec document was found for this change (searched the PR links, the touched repos' docs, the architecture/guidelines docs, and linked Jira). This review covers code-level quality but could not validate the change against an agreed design, so confidence is reduced. Add a spec link (PR template section 4) and re-request review for a full-confidence pass.

Verdict: Request changes - error logging pattern diverges from the codebase convention, losing the stack trace on failures.
Complexity: MEDIUM - medium diff, single-service.
Changes: Adds a new Slack command (force-optimize-at-edge-enable) that force-enables Optimize at Edge for a site by enqueuing a message to the imports queue, skipping prerendered-content validation (3 files).

Must fix before merge

1. [Important] Error logging loses the stack trace - src/support/slack/commands/force-optimize-at-edge-enable.js:79 (details inline)

Non-blocking (3): minor issues and suggestions

• suggestion: Add a null guard on Configuration.findLatest() result before calling .getQueues() - the catch block handles the resulting TypeError but the Slack user sees an opaque "Cannot read properties of null" message instead of something actionable - src/support/slack/commands/force-optimize-at-edge-enable.js:60
• suggestion: Add a test for Site.findById returning null (the not-found path is only exercised via the findByBaseURL branch) - test/support/slack/commands/force-optimize-at-edge-enable.test.js
• suggestion: Tighten the success-path assertion from .calledWithMatch('force') to .calledWithMatch('Triggered') - the word "force" is too generic and would match error messages containing the command name - test/support/slack/commands/force-optimize-at-edge-enable.test.js:93

---

_{Skill: pr-review | Model: us.anthropic.claude-opus-4-6-v1[1m] | Duration: 2m 35s | Cost: $4.61 | Commit: 99b95336da0b8ab95af3771b4b1ae88ddb724362
If this code review was useful, please react with 👍. Otherwise, react with 👎.}

[github-actions]

This PR will trigger a minor release when merged.

[MysticatBot]

Hey @jindaliiita,

⚠ Degraded review - no spec document was found for this change (searched the PR links, the touched repos' docs, the architecture/guidelines docs, and linked Jira). This review covers code-level quality but could not validate the change against an agreed design, so confidence is reduced. Add a spec link (PR template section 4) and re-request review for a full-confidence pass.

Verdict: Approve - all prior findings addressed; clean implementation following established patterns.
Complexity: MEDIUM - medium diff, single-service.
Changes: Adds a new Slack command (force-optimize-at-edge-enable) that force-enables Optimize at Edge for a site by enqueuing a message to the imports queue, skipping prerendered-content validation (3 files).

Non-blocking (1): minor issues and suggestions

• suggestion: The forcedBy field carries the Slack user ID (e.g. U123ABC) - if the downstream consumer ever needs a human-readable display name for notifications or audit UI, that will require an extra Slack API call at consumption time. Worth noting as a future consideration if incident-response clarity matters here - src/support/slack/commands/force-optimize-at-edge-enable.js:51

Previously flagged, now resolved

• Error logging now passes the full error object (stack trace preserved)
• Null guard on Configuration.findLatest() with user-facing warning added
• Site.findById returning null is now tested
• Success-path assertion tightened from 'force' to 'Triggered'

---

_{Skill: pr-review | Model: us.anthropic.claude-opus-4-6-v1[1m] | Duration: 1m 14s | Cost: $2.98 | Commit: 46fc54472ff10a9e20e2e0f5d4520139abfe4855
If this code review was useful, please react with 👍. Otherwise, react with 👎.}

[shrotia]

LGTM

[MysticatBot]

Hey @jindaliiita,

⚠ Degraded review - no spec document was found for this change (searched the PR links, the touched repos' docs, the architecture/guidelines docs, and linked Jira). This review covers code-level quality but could not validate the change against an agreed design, so confidence is reduced. Add a spec link (PR template section 4) and re-request review for a full-confidence pass.

Verdict: Approve - clean implementation extending the existing command; follows established patterns with solid utility-layer test coverage.
Complexity: MEDIUM - medium diff, single-service.
Changes: Extends the run-global-import Slack command with optional single-site scoping and a --force flag that skips prerender content validation, replacing the previously planned standalone command (3 files).

Non-blocking (3): minor issues and suggestions

• suggestion: triggerGlobalImportRun has no default for the options parameter, relying on sendGlobalImportRunMessage's downstream = {} destructuring default to handle undefined. Adding options = {} to the signature makes the contract explicit at the call site - src/support/utils.js:475
• suggestion: --force is the first CLI-style flag in this repo's Slack commands (all others use purely positional args). If additional flags arise later, consider extracting flag-parsing into a shared utility rather than per-command helpers - src/support/slack/commands/run-global-import.js:34
• nit: The usage text documents that --force "requires a site" but does not mention that --force is only meaningful for optimize-at-edge-enabled-marking. The command accepts --force with any import type and silently passes it downstream where it is ignored - an explicit "Note: only supported by optimize-at-edge-enabled-marking" or a validation guard would prevent operator confusion - src/support/slack/commands/run-global-import.js:60

Previously flagged, now resolved

• Error logging stack trace concern (previous standalone implementation) - moot after the pivot to extending run-global-import
• Null guard on Configuration.findLatest() - moot (standalone command removed)
• Site.findById null test - moot (standalone command removed)
• Success-path assertion tightened - moot (standalone command removed)

---

_{Skill: pr-review | Model: us.anthropic.claude-opus-4-6-v1[1m] | Duration: 13m 25s | Cost: $6.66 | Commit: ec0f713131f4eade89a48c6a8264d093b1c86148
If this code review was useful, please react with 👍. Otherwise, react with 👎.}

[solaris007]

🎉 This PR is included in version 1.683.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀