[doc-healer] DDUw improvement: classify documentation-labeled site-build/UI-component issues as non-content, out of the docs-PR [Content truncated due to length]

[github-actions]

Class of gaps DDUw/doc-healer is missing

Some issues carry the documentation label but are not documentation-content gaps fixable by editing Markdown/MDX under docs/src/content/docs/. They are docs-site infrastructure or UI-component problems that require .astro component edits, Starlight/pagefind build configuration, or CSS — outside the file-routing DDUw and doc-healer use.

Two concrete auto-expired (not_planned, bot-closed) examples from the last 7 days:

• [deep-report] Docs site Search shows dev-only message to end users #40805 — Docs site Search (Ctrl+K) shows the dev-only pagefind message to end users. This is an Astro/Starlight build/index concern (generate & serve the pagefind index in the production build, or hide the affordance), not a Markdown edit.
• [deep-report] Clarify or rename the Peli's Agent Factory link in docs navigation/Quick Start #40806 — The "Peli's Agent Factory" nav label reads as confusing to newcomers. The label lives in docs/src/components/CustomHeader.astro (header + tablet dropdown), i.e. a UI component, and the naming is a deliberate branding choice. The Quick Start gloss already exists (docs/src/content/docs/setup/quick-start.mdx:154).

Which step fails

doc-healer Step 5 routes fixes only to setup/cli.md, reference/, guides/, samples/ — all Markdown. It has no branch for .astro components, astro.config, pagefind, or CSS. So these issues fall through: no docs-content edit is possible, yet they keep re-appearing in the Step 1 closed-documentation-issue scan every run, consuming analysis budget with no resolution path.

Proposed improvement (wording changes to daily-doc-updater.md and this healer prompt)

1. Add a classification sub-step after Step 2 (cross-reference): before treating a closed documentation issue as a content gap, check whether the referenced path/subject is under docs/src/content/docs/** (Markdown/MDX = content, in scope) versus docs/src/components/**, docs/astro.config.*, the pagefind/search index, or CSS (site-build/UI = out of scope for the docs-PR path).
2. Route out-of-scope items to a separate outcome: do NOT attempt a Markdown fix and do NOT re-scan every run. Either (a) note them once in the run summary as "site-build/UI — needs Astro/site-build agent, not doc-healer," or (b) hand off to the designated site-build agent named in the issue body.
3. Add a stable skip signal so the same infra-labeled issue is not re-evaluated as a content gap on subsequent runs (mirrors the existing not_planned / rejection-signal handling, but keyed on content-vs-infra classification rather than closure reason).

Why this matters

Without this, documentation-labeled infra issues are indistinguishable from real content gaps in Step 1, so each run re-analyzes them and can be tempted into an inappropriate Markdown edit or a redundant escalation. A one-time content-vs-infra classification removes that recurring waste.

Related

• [deep-report] Docs site Search shows dev-only message to end users #40805, [deep-report] Clarify or rename the Peli's Agent Factory link in docs navigation/Quick Start #40806 (auto-expired examples)
• Complements [doc-healer] DDUw improvement: distinguish bot-expiry from maintainer rejection on closed-as-not_planned issues #40907 (bot-expiry vs maintainer rejection) and [doc-healer] DDUw improvement: auto-expired not_planned doc issues bypass both DDUw and doc-healer #40700 (auto-expired not_planned bypass) — those key on closure reason; this keys on issue class (content vs infra).

Generated by 📝 Daily Documentation Healer · 233.4 AIC · ⌖ 36.8 AIC · ⊞ 7K · ◷

• expires on Jul 3, 2026, 4:13 PM UTC-08:00