Skip to content

chore: remove compounded footer blocks, batch 34 of 45 (#3451) - #3653

Merged
eleshar merged 1 commit into
developfrom
fix/footer-cleanup-batch-34-of-45-3451
Sep 28, 2026
Merged

eleshar merged 1 commit into
developfrom
fix/footer-cleanup-batch-34-of-45-3451

Conversation

@eleshar

@eleshar eleshar commented Sep 28, 2026

Copy link
Copy Markdown
Contributor

Compounded footer blocks removed — batch 34 of 45

Refs #3451 — not Closes. The issue stays open until all 45 batches land and the whole-repo run reports zero.

Linked issues

Relates to #3451 — repo-wide footer duplicate cleanup. 11 batches remain after this one.

Why 90 files and not 1,950

CodeRabbit's server-side review only runs under 100 changed files. Every batch of the earlier plan was skipped with Review skipped: … files exceed the limit of 100, so their review was a local slice rather than a review of the pull request. Batches are capped at 90, leaving headroom for CHANGELOG.md and keeping the largest pull request at 91 files. The cost is explicit: 45 pull requests.

Context

  • Severity/Impact: High. 751 of 11,474 tracked Markdown files still carry compounded footer blocks after the previous batches.
  • Affected versions/environments: repository Markdown content. No code, no configuration, no runtime behaviour.

Reproduction

Scoped to this batch's manifest, so the check reports only what this pull request changed:

node scripts/dedupe-footers.js --check --paths-from=small-34.txt

Before the fix: 90/90 file(s) affected · blocks found 500 · exempt-path files 85, exit 1.
After the fix: 0/90 file(s) affected, exit 0.

Root Cause

Two defects, both fixed in merged tooling:

Fix Summary

Deletion only, produced by the committed tool over this batch's fixed manifest:

node scripts/dedupe-footers.js --fix --paths-from=small-34.txt
files outcome
footer-exempt path 85 footer removed entirely — the guide states these carry none
everything else 5 collapsed to exactly one trailing footer, the last block

The split is decided by isFooterExemptPath() in scripts/agents/includes/footer-policy.js and the keep decision in analyseContent(), not by a judgement call per file. Batch 34 covers skills/zendesk-backlog-trend-analysis.

Verification

  • Re-running --check over the manifest after the fix reports 0/90 file(s) affected, exit 0 — idempotent.
  • Independent differential pass: the change is a pure order-preserving deletion, every deleted line is footer structure, and none came from frontmatter or a fenced code block. The classified counts sum to exactly the numstat deletion total, a second independent count of the same number. The checker is negative-tested — an injected content line and a deletion from inside a fence both make it fail.
  • Staged paths match the manifest exactly — 90 files, 0 outside, 0 additions outside the changelog.
  • 0 files shared with any other batch in the series.

CodeRabbit

Recorded in the running report for this batch: whether the review actually ran on this pull request, or was rate-limited and therefore did not run. A green CodeRabbit tick here means "reviewed" only if that report says so — the check also passes when it declines.

Changelog

None. This is a Markdown-only diff, which the changelog-unified.yml gate exempts as docs-only. The skills/ area-level entry lands on the last pull request for that area.

Risk & Rollback

  • Risk level: Low. Deletion-only, mechanically generated, independently verified as confined to footer structure. No code, no configuration, no behaviour change.
  • Rollback plan: git revert this commit. The revert is itself a pure insertion.
  • The pre-commit hook is bypassed, as in every commit in this series: it runs npx lint-staged, dependencies are not installed in the worktree used for this work, and fix: lint:md and lint-staged corrupt shields.io badge links whose URL contains a space #3590 records that the Markdown hook corrupts shields.io badge links. CI does not run lint:md.

Refs #3451

Batch 34 of 45. Pure deletion: 90 files, 0 added.

  node scripts/dedupe-footers.js --fix --paths-from=small-34.txt

The scope split comes from the code, not per-file judgement:
isFooterExemptPath() in scripts/agents/includes/footer-policy.js with the
keep decision in analyseContent(). 85 of the 90 files are
footer-exempt and lost their footer entirely, which is the policy
docs/QUIRKY_FOOTERS_GUIDE.md states; the other 5 were collapsed to
exactly one clean trailing footer, the last block, which is what
ensureFooter() treats as canonical.

Covers `skills/zendesk-backlog-trend-analysis`. Manifests were derived once before any of this ran
and are fixed: batch N is small-NN.txt. Cross-batch overlap is 0, so
these pull requests cannot conflict with each other.

Verification:
- re-running --check over the manifest reports 0/90 affected
- independent differential pass, negative-tested: pure order-preserving
  deletion, every deleted line classified as footer structure, none from
  frontmatter or a fenced code block, and the classified counts sum to
  exactly the numstat deletion total
- staged paths match the manifest exactly, 0 outside

No changelog entry: Markdown-only diff, exempt as docs-only by the gate
in changelog-unified.yml.

The pre-commit hook is bypassed for this commit, as in every commit in this
series. It runs npx lint-staged, dependencies are not installed in this
worktree, and #3590 records that the Markdown hook corrupts shields.io
badge links. CI does not run lint:md, so this does not diverge from what
CI checks.
@eleshar
eleshar requested review from a team and ashleyshaw as code owners September 28, 2026 11:33
@qodo-code-review

Copy link
Copy Markdown

ⓘ Qodo reviews are paused because the subscription is no longer active. Ask your workspace admin to reactivate the subscription to resume reviews. Manage billing

@coderabbitai

coderabbitai Bot commented Sep 28, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

Next included review available in 57 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

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

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: Repository: lightspeedwp/.github/.coderabbit.yml

Review profile: CHILL

Plan: Advanced

Run ID: 5f58c26b-d0f7-4fe2-9c21-f2839bfc9a9a

📥 Commits

Reviewing files that changed from the base of the PR and between 08ccff2 and ce47f48.

📒 Files selected for processing (90)
  • skills/zendesk-backlog-trend-analysis/references/shared-agent-rollout-checklist.md
  • skills/zendesk-backlog-trend-analysis/references/shared-agent-smoke-test-plan.md
  • skills/zendesk-backlog-trend-analysis/references/workspace-capability-profile.md
  • skills/zendesk-backlog-trend-analysis/references/zendesk-query-recipes.md
  • skills/zendesk-backlog-trend-analysis/templates/backlog-health-summary.md
  • skills/zendesk-backlog-trend-analysis/templates/daily-digest.md
  • skills/zendesk-backlog-trend-analysis/templates/evidence-basis.md
  • skills/zendesk-backlog-trend-analysis/templates/repeated-theme-review.md
  • skills/zendesk-backlog-trend-analysis/templates/shared-agent-installation-note.md
  • skills/zendesk-backlog-trend-analysis/templates/trend-comparison.md
  • skills/zendesk-backlog-trend-analysis/templates/weekly-support-report.md
  • skills/zendesk-bug-report-package/examples/bug-package-cases.md
  • skills/zendesk-bug-report-package/examples/shared-agent-smoke-tests.md
  • skills/zendesk-bug-report-package/references/memory-policy.md
  • skills/zendesk-bug-report-package/references/router-integration.md
  • skills/zendesk-bug-report-package/references/routing-boundaries.md
  • skills/zendesk-bug-report-package/references/shared-agent-setup.md
  • skills/zendesk-bug-report-package/references/source-access-profile.md
  • skills/zendesk-bug-report-package/templates/bug-package-template.md
  • skills/zendesk-create-knowledge/references/article-templates.md
  • skills/zendesk-create-knowledge/references/evidence-confidence-rubric.md
  • skills/zendesk-create-knowledge/references/examples.md
  • skills/zendesk-create-knowledge/references/public-internal-boundary.md
  • skills/zendesk-create-knowledge/references/routing-boundaries.md
  • skills/zendesk-create-knowledge/references/shared-agent-runtime-rules.md
  • skills/zendesk-customer-escalation/SKILL.md
  • skills/zendesk-customer-escalation/references/CONNECTORS.example.md
  • skills/zendesk-customer-escalation/references/escalation-lanes.md
  • skills/zendesk-customer-escalation/references/escalation-record-schema.md
  • skills/zendesk-customer-escalation/references/routing-boundaries.md
  • skills/zendesk-customer-escalation/references/severity-matrix.md
  • skills/zendesk-customer-escalation/references/shared-agent-portability.md
  • skills/zendesk-customer-escalation/templates/escalation-template.md
  • skills/zendesk-customer-research/SKILL.md
  • skills/zendesk-customer-research/references/citation-ledger-schema.md
  • skills/zendesk-customer-research/references/examples.md
  • skills/zendesk-customer-research/references/health-rubric.md
  • skills/zendesk-customer-research/references/input-normalisation-schema.md
  • skills/zendesk-customer-research/references/output-template.md
  • skills/zendesk-customer-research/references/routing-boundaries.md
  • skills/zendesk-customer-research/references/shared-agent-access-model.md
  • skills/zendesk-customer-research/references/source-permission-matrix.md
  • skills/zendesk-draft-response/SKILL.md
  • skills/zendesk-draft-response/examples/billing-risk.expected.md
  • skills/zendesk-draft-response/examples/billing-risk.input.md
  • skills/zendesk-draft-response/examples/feature-limitation.expected.md
  • skills/zendesk-draft-response/examples/feature-limitation.input.md
  • skills/zendesk-draft-response/examples/frustrated-follow-up.expected.md
  • skills/zendesk-draft-response/examples/frustrated-follow-up.input.md
  • skills/zendesk-draft-response/examples/localisation.expected.md
  • skills/zendesk-draft-response/examples/localisation.input.md
  • skills/zendesk-draft-response/examples/new-issue.expected.md
  • skills/zendesk-draft-response/examples/new-issue.input.md
  • skills/zendesk-draft-response/examples/no-eta-delay.expected.md
  • skills/zendesk-draft-response/examples/no-eta-delay.input.md
  • skills/zendesk-draft-response/references/connector-source-map.md
  • skills/zendesk-draft-response/references/data-redaction-rules.md
  • skills/zendesk-draft-response/references/escalation-boundaries.md
  • skills/zendesk-draft-response/references/evidence-quality-rules.md
  • skills/zendesk-draft-response/references/localisation-rules.md
  • skills/zendesk-draft-response/references/routing-boundaries.md
  • skills/zendesk-draft-response/references/shared-agent-installation-checklist.md
  • skills/zendesk-draft-response/references/shared-agent-regression-tests.md
  • skills/zendesk-draft-response/references/shared-agent-setup.md
  • skills/zendesk-draft-response/references/tone-playbook.md
  • skills/zendesk-draft-response/templates/CONNECTORS.example.md
  • skills/zendesk-draft-response/templates/customer-reply-template.md
  • skills/zendesk-draft-response/templates/redacted-support-context-template.md
  • skills/zendesk-draft-response/templates/reply-only-template.md
  • skills/zendesk-draft-response/tests/shared-agent-smoke-prompts.md
  • skills/zendesk-evidence-collector/SKILL.md
  • skills/zendesk-evidence-collector/examples/README.md
  • skills/zendesk-evidence-collector/examples/evidence-pack-partially-ready.md
  • skills/zendesk-evidence-collector/examples/evidence-pack-ready.md
  • skills/zendesk-evidence-collector/examples/investigation-blocked-event-time.md
  • skills/zendesk-evidence-collector/examples/zendesk-unavailable-pasted-thread-only.md
  • skills/zendesk-evidence-collector/references/routing-boundaries.md
  • skills/zendesk-evidence-collector/references/shared-agent-compatibility.md
  • skills/zendesk-evidence-collector/references/shared-agent-defaults.md
  • skills/zendesk-evidence-collector/references/source-precedence-examples.md
  • skills/zendesk-evidence-collector/templates/evidence-pack.md
  • skills/zendesk-evidence-collector/templates/investigation-report.md
  • skills/zendesk-evidence-quality-review/examples/backlog-summary-review-example.md
  • skills/zendesk-evidence-quality-review/examples/customer-reply-review-example.md
  • skills/zendesk-evidence-quality-review/examples/escalation-review-example.md
  • skills/zendesk-evidence-quality-review/examples/knowledge-draft-review-example.md
  • skills/zendesk-evidence-quality-review/examples/privacy-redaction-review-example.md
  • skills/zendesk-evidence-quality-review/examples/review-severity-calibration-cases.md
  • skills/zendesk-evidence-quality-review/examples/routing-boundary-cases.md
  • skills/zendesk-evidence-quality-review/examples/shared-agent-acceptance-test-fixtures.md

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

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

@github-actions

Copy link
Copy Markdown
Contributor

PR Template Routing

Branch Type: fix
Scope: footer-cleanup-batch-34-of-45-3451
Template: pr_bug.md
Labels Applied: type:bug

This PR was automatically routed based on the branch naming strategy.

@github-actions

Copy link
Copy Markdown
Contributor

No description provided.

@eleshar
eleshar merged commit a63f723 into develop Sep 28, 2026
30 checks passed
@eleshar
eleshar deleted the fix/footer-cleanup-batch-34-of-45-3451 branch September 28, 2026 12:12
@linear-code

linear-code Bot commented Sep 28, 2026

Copy link
Copy Markdown

GIT-2441

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant