feat(ops): daily heartbeat + rehearsal review procedure#25
Merged
Conversation
Every scrape run (cron or manual, empty or not) posts ONE heartbeat comment to the pinned ops-log issue (vars.OPS_ISSUE): date, run URL, trigger, docs (fetched/processed/skipped-settled/ledger settled), extract counts (extracted/in-scope/published/quarantined/out-of-scope), cost, and status (ok/truncated/aborted/RUN FAILED) with any provider error_samples. No PII — counts + a run URL only. A cron day with no comment is itself the alert that the run did not fire. run_summary.env gains FETCHED/PROCESSED/SKIPPED/EXTRACTED for the heartbeat. CONTRIBUTING §Operations documents the daily review procedure; the standing orders and launch-eligibility definition live in the pinned issue (#24). make check green.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Your directive #1 (daily heartbeat visibility). Every run posts one fixed-format comment to the pinned ops-log issue #24 (
OPS_ISSUEvar) — date · run link · docs (fetched/processed/skipped/ledger) · extract (extracted/in-scope/published/quarantined/out-of-scope) · cost · status + error_samples. Empty runs included; a missing comment on a cron day is the alert. No PII.run_summary.envgains the heartbeat fields; CONTRIBUTING §Operations documents the daily procedure; standing orders + launch-eligibility live in issue #24.make checkgreen.