feat(operations): restack external scheduler evidence audit on latest main

[seonghobae]

Purpose

Clean protected-main successor for stale-lineage PR #97. This branch starts directly from protected main 84a1b4cc0f781fc35fae66a47ada0b099aa2555d and ports the fail-closed external-scheduler evidence validator onto the current package/coverage baseline without replaying stale package, test-policy, vitest, or CHANGELOG.md bytes.

Exact source and current-baseline integration

• protected base at construction and PR creation: 84a1b4cc0f781fc35fae66a47ada0b099aa2555d;
• exact head: a35bbf01677710a5f1c52c16d6f9342f9a7b49c8;
• source predecessor: PR feat(operations): audit external scheduler continuation evidence #97 exact head a84d490c1f6596a49d4f29c41babf4996f9ad86f, unchanged immediately before construction;
• exact source blobs retained unchanged:
  • docs/external-hourly-scheduler-evidence-audit.md 9ee0d058f8ad7a9d64de14cf234684183e33fc18;
  • scripts/external-scheduler-evidence-audit.mjs 14c4f934b90e4619e6a749c9ddb02844e274529c;
  • scripts/lib/external-scheduler-evidence-audit.mjs 79cd04d4c2955bb1d05a044f2c056068c2789b39;
  • test/external-scheduler-evidence-audit.test.ts ee94552a257d986374279e250bd93d160344b39e;
  • test/external-scheduler-evidence-cli-defaults.test.ts daee1c2c1f3fc335fdea6038dd329d4461831e2d;
  • test/external-scheduler-evidence-cli.test.ts 461ed7d37b74869ae7893b122177ba3fc9f6557c;
  • test/external-scheduler-evidence-defensive-branches.test.ts d7b39eaa4c3f6c3ce9d69c1d3e67885860ff5dea.

Current protected-main package.json, vitest.config.ts, and test/production-coverage-policy.test.ts were edited narrowly rather than replaced from the stale source lineage: the operator script is registered, both new production scripts are added to the existing exact-100% coverage include set, and the coverage-policy regression is extended while retaining current lockfile/workflow-registry coverage entries. package-lock.json is unchanged because the operation adds no dependency metadata. The predecessor's historical CHANGELOG.md blob is intentionally omitted rather than overwriting current protected history.

Security / operational boundary

The validator checks retained provider-side scheduler evidence; it does not operate the provider scheduler. It keeps bounded regular-file reads, no-follow failure closure, canonical identity checks, malformed/duplicate-key/UTF-8 rejection, recursive sensitive-field rejection, generic-error recovery binding, materially-distinct action evidence, and owner-only atomic derived reports. A successful report is operational evidence only and cannot substitute for GitHub CI, Security Scan, review authority, protected integration, release/deployment evidence, production KPI, licensing/IP authority, or acquisition readiness.

Evidence boundary

No CI, reviewer, scanner, model, review, provider, scheduler, production, release, or deployment evidence transfers from #97. This exact head must obtain fresh application CI, reviewer CI, and protected-base-eligible central Security Scan evidence against unchanged head and current protected main. Pending, queued, skipped, absent, neutral, failed, cancelled, stale, predecessor, status-only, model-only, or rate-limited evidence is non-passing.

Immediately before merge, re-resolve live main/head, formal reviews and unresolved threads, live rulesets, and central .github Security Scan revision/triggers/thresholds; verify workflow checkout SHAs and require every applicable gate terminal-success with zero valid unresolved findings. Independent non-author approval is required only if live policy actually requires it.

PR #97 remains the source predecessor until this successor is protected and independently reverified. Issue #96 continues to own real provider-side scheduler acceptance; no provider-side enablement or execution receipt is invented here.

[coderabbitai]

Warning

Review limit reached

@seonghobae, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 58 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 78cd88bf-13bf-45cf-a8ca-e72d916e5526

📥 Commits

Reviewing files that changed from the base of the PR and between db577a1 and 8b14395.

📒 Files selected for processing (10)

• docs/external-hourly-scheduler-evidence-audit.md
• package.json
• scripts/external-scheduler-evidence-audit.mjs
• scripts/lib/external-scheduler-evidence-audit.mjs
• test/external-scheduler-evidence-audit.test.ts
• test/external-scheduler-evidence-cli-defaults.test.ts
• test/external-scheduler-evidence-cli.test.ts
• test/external-scheduler-evidence-defensive-branches.test.ts
• test/production-coverage-policy.test.ts
• vitest.config.ts

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}