docs(ops): retarget durable-tracker table at the live tracker issues - #2871
Conversation
The tracker table pointed at #1868, closed 2026-05-14 and replaced by #2210, so anyone following the doc landed on a dead issue. Two further gaps surfaced while auditing open trackers: maint-69 stamps a "Durable tracker - see DURABLE_TRACKING_ISSUES.md" header onto #2470 but the doc never listed it, and #1836's title had drifted from the live issue. Also records the superseded tracker numbers so older comments stay traceable, and notes that maint-69 clears its stuck-window marker without ever closing the tracker - the issue body's "close this once the next run succeeds" step predates that marker and misleads triage.
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 5 minutes Your organization has reached its usage spending cap. Adjust your spending cap in the billing tab. How can I continue?After more reviews become available, a review can be triggered using the 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 configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe changes update durable tracker references and lifecycle guidance, document current and retired trackers, and add the ChangesDurable tracker alignment
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 3 | ❌ 2❌ Failed checks (2 warnings)
✅ Passed checks (3 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
Workflow source neededPR #2871 needs either a linked GitHub issue or one valid non-issue Workflow Source before PR metadata automation can manage it safely. Please do one of:
Once a valid source is present, this warning will not be reposted. |
Automated Status SummaryHead SHA: 9c2f3e1
Coverage Overview
Coverage Trend
Top Coverage Hotspots (lowest coverage)
Low Coverage Files (<50.0%)
Updated automatically; will refresh on subsequent CI/Docker completions. Keepalive checklistScopeNo scope information available Tasks
Acceptance criteria
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 4
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs/ops/DURABLE_TRACKING_ISSUES.md`:
- Around line 24-26: Update the blanket closure guidance in
DURABLE_TRACKING_ISSUES.md to apply only to dashboard and report trackers, or
explicitly exclude `#1836`, so it does not imply that closing the active campaign
tracker is harmless.
- Line 44: Update the `#2470` description in DURABLE_TRACKING_ISSUES.md to state
that the stuck-window marker is cleared only by the next successful run with a
sync token; leave the surrounding recovery behavior and resolution guidance
unchanged.
- Line 37: Update the cadence cell for maint-69-sync-integration-repo.yml to
document all trigger paths: qualifying pushes to templates/integration-repo
files, the two consumer workflow files, .github/workflows/autofix-versions.env,
and manual workflow_dispatch; use concise wording such as “On qualifying
template/config pushes or manual dispatch.”
- Around line 110-116: Update the Current durable trackers section to add issue
`#2415` for the LangSmith Trace Coverage Dashboard with the behavior text “Body
rewritten in place.” Document that maint-80-langsmith-metrics-dashboard.yml
applies the tracker:durable label in addition to the existing metrics and
automated labels, ensuring newly created dashboard issues match the
durable-tracker filter.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro
Run ID: c1f159a0-4ed8-409a-804d-2553781f56fd
📒 Files selected for processing (2)
docs/ops/CONSUMER_REPO_MAINTENANCE.mddocs/ops/DURABLE_TRACKING_ISSUES.md
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: ad91d938b8
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
There was a problem hiding this comment.
Pull request overview
Updates the operational documentation that defines which GitHub issues are treated as durable trackers (i.e., dashboards/queues that should generally remain open) so the docs point at the currently-live tracker issues and reflect current tracker behavior.
Changes:
- Retargets the consumer drift durable tracker from #1868 → #2210 (including cross-reference in
CONSUMER_REPO_MAINTENANCE.md). - Corrects the campaign queue tracker title (Sync/Dependabot) and adds the missing #2470 integration-sync durable tracker row.
- Adds a “Superseded tracker numbers” mapping table and expands transient-alert examples (retired LangSmith weekly-report format).
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| docs/ops/DURABLE_TRACKING_ISSUES.md | Updates the durable tracker table (including new #2470), adds superseded-tracker mapping, and refines guidance/examples for durable vs transient automation issues. |
| docs/ops/CONSUMER_REPO_MAINTENANCE.md | Updates the consumer-drift durable tracker cross-reference from #1868 to #2210. |
Suppressed comments (2)
docs/ops/DURABLE_TRACKING_ISSUES.md:37
- The cadence cell for the #2470 tracker implies it only triggers on changes under
templates/integration-repo/**, butmaint-69-sync-integration-repo.ymlruns on pushes tomainthat touch several other paths too (agent hub workflows +.github/workflows/autofix-versions.env) and can also be invoked viaworkflow_dispatch. This table should reflect the full trigger surface so operators don’t miss why the tracker updated.
| [#2470](https://github.com/stranske/Workflows/issues/2470) | 🚨 Integration-Tests Sync Failed - Action Required | [`maint-69-sync-integration-repo.yml`](../../.github/workflows/maint-69-sync-integration-repo.yml) | On push to `templates/integration-repo/**` | Stuck-window marker in body + recovery comment |
docs/ops/DURABLE_TRACKING_ISSUES.md:43
- This bullet claims the consumer-drift tracker “auto-resolves …; the closure happens in the workflow, not by hand.” The
health-68-consumer-sync-drift.ymljob only creates/updates the tracker body and appends comments; it does not close the issue when drift clears. To avoid telling operators the issue will self-close, please reword this to describe “auto-resolves” as the drift counts going back to 0 (while the tracker stays open).
- **#2210** — fan-out drift report across registered consumer repos. Auto-resolves on the next clean `Maint 68` run; the closure happens in the workflow, not by hand.
GitHub Actions
Inactive
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs/ops/DURABLE_TRACKING_ISSUES.md`:
- Around line 24-27: Update the introductory body-rewrite issue list in
DURABLE_TRACKING_ISSUES.md to include `#2415` alongside `#1836`, `#2210`, and `#2470`,
keeping the surrounding guidance unchanged.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro
Run ID: 34667d16-14bc-4776-b275-b46335d2959e
📒 Files selected for processing (4)
.github/workflows/maint-80-langsmith-metrics-dashboard.ymldocs/ops/CONSUMER_REPO_MAINTENANCE.mddocs/ops/DURABLE_TRACKING_ISSUES.mdtests/workflows/test_langsmith_metrics_dashboard.py
Co-authored-by: Cursor <cursoragent@cursor.com>
GitHub Actions
Inactive
GitHub Actions
Inactive
Provider Comparison ReportProvider Summary
📋 Full Provider Details (click to expand)openai
anthropic
Agreement
Disagreement
Unique Insights
🔍 LangSmith Traces |
Closer verifier disposition — unanimous PASS; every "could not verify" concern confirmed present on
|
| Anthropic's unverified item | State on main |
|---|---|
#1836 title corrected |
Present — "Sync/Dependabot campaign queue" (table row, maint-82 + sync_dependency_campaign.js) |
#2470 row added |
Present — full row, Update style = "Stuck-window marker in body + recovery comment" |
| Superseded tracker numbers table added | Present — ### Superseded tracker numbers, both rows (#1796→#2211, #1868→#2210) |
| Proven-duplicate close exception documented | Present — "How humans should treat these": close only when retiring the controller "or when the tracker is a proven duplicate of a newer one for the same controller" |
Retired LangSmith Trace Coverage Report - Week of <date> format |
Present — "Distinguishing trackers from transient alerts", naming the upsert to #2415 and the 2026-08-01 closures (#2213, #2247, #2194 earlier) |
Its remaining note — no markdownlint/link-check enforces the cross-references going forward — is accurate and was an explicit accepted trade-off in the PR, not an unmet criterion.
Disposition: terminal, no follow-up debt. The three source issues this follow-up chain served (#1796, #2213, #2247) were closed 2026-08-01 with evidence comments; #2470 was audited and deliberately left open as a live tracker. Nothing remains open on this chain.
Summary
docs/ops/DURABLE_TRACKING_ISSUES.mdis the page that tells automations and humans which auto-bot issues must not be closed in routine triage. Two of its four facts were wrong, so following it led to a closed issue.Found while auditing every open
tracker:durableissue in this repo during a closer sweep.Changes
CONSUMER_REPO_MAINTENANCE.md.maint-69-sync-integration-repo.ymlstamps> **Durable tracker** — see docs/ops/DURABLE_TRACKING_ISSUES.mdinto that issue's body, but the doc never listed it, so the header pointed at a page that disclaimed it.LangSmith Trace Coverage Report - Week of <date>format to the transient-alert examples.Why #2470 needed a nuanced note
Its
Resolution Stepsstill say "Close this issue once the next run succeeds." That predates the stuck-window marker.clearStuckWindowin.github/scripts/sync_tracker_state/index.jsonly strips the marker from the body and appends a✅ Integration sync recoveredcomment — it never closes the issue, andfindTrackeris called withcreateIfMissing: false, so the issue is reused indefinitely. A marker-free body carrying a recovery comment is therefore the healthy resting state, not an oversight. The doc now says so.Evidence for the #1796 → #2211 supersession
agents-weekly-metrics.ymlpicks its tracker withissues.find((issue) => issue.title === title)overlistForRepo, which defaults tosort=created&direction=desc. The newest matching open issue always wins, so #2211 (created 2026-06-01) permanently shadowed #1796 (last comment 2026-05-25, 45 comments, noclosed/reopened/renamedevent in its timeline). No third tracker has appeared in the nine weeks since, so the current dedup path is sound and this was a one-off historical duplicate. #1796 was closed on evidence; #2211 remains open and green (Parse errors: 0).Test plan
Docs-only; no runtime surface is touched.
rg '#1868|#1796'across the repo — remaining hits are the new supersession table and dated snapshots indocs/HISTORY.md, which are historical records and intentionally unchanged.agents-weekly-metrics.yml,maint-82-sync-dependency-campaign.yml,health-68-consumer-sync-drift.yml,maint-69-sync-integration-repo.yml)..github/workflows/, and no test asserts this doc's contents (.github/scripts/__tests__/sync-tracker-state.test.jscovers the marker helpers, not the table).Summary by CodeRabbit
Documentation
Maintenance