[doc-healer] DDUw improvement: add secondary scan for cookie-labeled automation issues (4th recurrence)

[github-actions]

Problem

DDUw's Step 1c (Scan Recently Closed Documentation Issues) systematically cannot read issues from automated monitoring workflows because they carry the cookie label, which DDUw's min-integrity: approved filter blocks.

The affected workflows are:

• CLI Consistency Checker — files [cli-consistency] issues with labels documentation automation cli cookie
• Multi-Device Docs Tester — files 🔍 Multi-Device Docs Testing Report issues with labels documentation testing cookie

Both produce real, actionable documentation gaps (incomplete options lists in cli.md, rendering bugs in .md files, broken links) — but DDUw cannot read their bodies because they fall below the integrity threshold.

Evidence: 4 Consecutive Healer Runs Affected

This pattern has been identified in every healer run since it was first detected:

Healer Run	PR	Issue(s) Caught	Gap Type
2026-03-26	#23124	#22702 (CLI Consistency)	gh aw list --path missing from cli.md
2026-03-27	#23240	Code-based (unrelated to cookie)	—
2026-03-28	#23355	#23111 (Multi-Device Docs)	Duplicate H1, abnf code fence
2026-03-30	(this issue)	#22435, #22702 (CLI Consistency)	All doc gaps already fixed; no new fix needed

Each healer PR (#23124, #23240, #23355) included a <details> improvement suggestion, but the DDUw workflow has not been updated in response.

Root Cause

DDUw Step 1c searches:

repo:$\{\{ github.repository }} is:issue is:closed label:documentation closed:>=YYYY-MM-DD

But reads results with min-integrity: approved. The cookie label marks issues from automated workflows (not human-authored), so they receive a lower integrity score and their bodies are inaccessible. DDUw cannot read the issue body → cannot identify the documentation gap → cannot act.

Proposed Fix

Add a dedicated secondary scan step in daily-doc-updater.md after Step 1c that explicitly targets cookie-labeled automation issues with a lower integrity threshold:

#### 1d. Scan Automation Monitoring Issues (Cookie Label)

Issues from the CLI Consistency Checker and Multi-Device Docs Tester carry the `cookie` label and require a lower integrity threshold to read. Search for these separately:

    repo:$\{\{ github.repository }} is:issue is:closed label:documentation label:cookie closed:>=YYYY-MM-DD

Read these with `min-integrity: unapproved` so their bodies are accessible. For each issue:
- Read the full body to identify any **documentation file** gaps (cli.md, reference pages, guides).
- Skip findings that require changes to Go source code (CLI help text, flag names) — those require code PRs.
- For confirmed documentation file gaps, apply the same fix process as Step 2.

Alternatively, lower min-integrity globally for Step 1c only, since the step already filters by label:documentation which limits scope.

Why This Matters

Without this fix, an entire class of actionable documentation gaps will continue to be invisible to DDUw indefinitely. The CLI Consistency Checker and Multi-Device Docs Tester run daily and surface real gaps — they should feed into DDUw's scan loop, not require manual healer intervention on every run.

Related

• PR [docs] Self-healing documentation fixes from issue analysis - 2026-03-26 #23124 — first healer run to identify this pattern (2026-03-26)
• PR [docs] Self-healing documentation fixes from issue analysis - 2026-03-28 #23355 — third consecutive healer run (2026-03-28), explicitly noted as "3rd occurrence"
• Issues caught and fixed: [cli-consistency] CLI Consistency Issues - 2026-03-24 #22702 (cli.md --path flag), 🔍 Multi-Device Docs Testing Report - 2026-03-26 #23111 (fuzzy-schedule-specification duplicate H1 + abnf)

Generated by Daily Documentation Healer · ◷

• expires on Apr 2, 2026, 1:30 PM UTC