docs: update durable tracker pointer from #1796 to #2211 in ops docs

[stranske]

Summary

Follow-up to PR #2726 (2026-Q3 README refresh sweep). Two operational docs still referenced the old "Agent metrics weekly summary" tracker issue (issue 1796, now superseded by issue 2211).

Files changed

• docs/QUICK_REFERENCE.md — live operational pointer updated to #2211; sentence reflowed to keep issue number inline and avoid MD018 markdownlint warning
• docs/ops/DURABLE_TRACKING_ISSUES.md — four occurrences updated: registry table row, signal-flow description, red-signal guidance, and inline prose example

Not changed

docs/HISTORY.md references to old issue numbers are intentional historical records (phase-endpoint snapshots of which issues were open at a given development milestone) and should remain as-is.

[coderabbitai]

📝 Walkthrough

Walkthrough

Documentation references to the weekly agent metrics tracker issue number were updated from #1796 to #2211 in two markdown files: docs/QUICK_REFERENCE.md and docs/ops/DURABLE_TRACKING_ISSUES.md, with no code or structural changes.

Changes

Tracker Issue Reference Update

Layer / File(s)	Summary
Update issue number references docs/QUICK_REFERENCE.md, docs/ops/DURABLE_TRACKING_ISSUES.md	Replaces references to tracker issue #1796 with #2211 in the verification-result section, the "Why this exists" example, the durable trackers table/signal-flow description, and the "red signal" parse-error bullet.

Estimated code review effort: 1 (Trivial) | ~2 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly describes the docs-only update from issue #1796 to #2211 in ops documentation.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/followup-tracker-link-2026-q3

---

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

[agents-workflows-bot]

Gate fast-pass: docs-only change detected; heavy checks skipped.

[agents-workflows-bot]

Automated Status Summary

Head SHA: 9c315da
Latest Runs: ⏳ pending — Gate
Required contexts: Gate / gate, Health 45 Agents Guard / guard
Required: core tests (3.12): ⏳ pending, core tests (3.13): ⏳ pending, docker smoke: ⏳ pending, gate: ⏳ pending

Workflow / Job	Result	Logs
(no jobs reported)	⏳ pending	—

Updated automatically; will refresh on subsequent CI/Docker completions.

---

Keepalive checklist

Scope

No scope information available

Tasks

• No tasks defined

Acceptance criteria

• No acceptance criteria defined

[Copilot]

Pull request overview

Updates operational documentation to point the “Agent metrics weekly summary” durable tracker from issue #1796 to the currently active tracker #2211, keeping ops references aligned with the current weekly metrics surface.

Changes:

• Update the quick-reference “Fleet/aggregate metrics” pointer from #1796 to #2211.
• Update the durable tracker registry table and related signal-flow guidance to reference #2211 (including the link target).

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
docs/QUICK_REFERENCE.md	Updates the weekly metrics tracker issue number referenced in the ops quick reference.
docs/ops/DURABLE_TRACKING_ISSUES.md	Updates the durable tracker table and guidance text to point to the active weekly metrics tracker issue.

[coderabbitai]

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/QUICK_REFERENCE.md`:
- Line 99: The markdown in QUICK_REFERENCE has the issue reference split across
lines, which triggers MD018; reflow the affected sentence so the `#2211` reference
stays on the same line as the surrounding text. Update the nearby paragraph in
QUICK_REFERENCE.md without changing the meaning, keeping the issue number
attached to the same line as the rest of the sentence.

🪄 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: db4823f6-305f-4457-a6d1-d02391e2545d

📥 Commits

Reviewing files that changed from the base of the PR and between 5bd2da9 and 00a331f.

📒 Files selected for processing (2)

• docs/QUICK_REFERENCE.md
• docs/ops/DURABLE_TRACKING_ISSUES.md

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 00a331ff60

ℹ️ 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".

[chatgpt-codex-connector]

Restore durable label coverage for #2211

Listing #2211 as the current durable tracker makes the label-based guidance below inaccurate: the live tracker at #2211 currently has no labels, and .github/workflows/agents-weekly-metrics.yml:401-407 creates this tracker title without applying tracker:durable. In any triage/stale scanner that follows this doc’s recommended label:tracker:durable filter, the active weekly metrics tracker will not be excluded and can be treated as ordinary work; please either label the tracker/creation path or avoid documenting label coverage for this tracker.

Useful? React with 👍 / 👎.

[stranske]

Valid observation — issue #2211 is indeed missing the tracker:durable label. This is a pre-existing gap in agents-weekly-metrics.yml (around lines 401–407): the workflow creates the issue but never applies tracker:durable on creation. That label-application fix belongs in the workflow itself, not in these docs. This PR is docs-only (updating the stale #1796 → #2211 reference), so fixing the workflow is out of scope here. I'll track it as a follow-up against agents-weekly-metrics.yml.

---

Generated by Claude Code

[agents-workflows-bot]

Workflow source needed

PR #2737 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:

• Add <!-- meta:issue:123 --> or a normal Closes #123 / Related to #123 line.
• Check one Workflow Source option in the PR body.
• Add a hidden marker such as <!-- workflow-source:local_request -->, <!-- workflow-source:manual_remote -->, <!-- workflow-source:review_followup -->, <!-- workflow-source:sync_campaign -->, or <!-- workflow-source:dependabot -->.
• Add a workflow source label such as workflow:source-direct-pr, workflow:source-local-request, workflow:source-review-followup, workflow:source-sync, or workflow:no-automation.

Once a valid source is present, this warning will not be reposted.