From e40bd8274462c187a1c50035e321c3b1e785b745 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Sat, 30 May 2026 00:12:30 +0000 Subject: [PATCH 1/3] Initial plan From 9f9b0866174af3b7a46fe5c2f3157e29baf3a282 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Sat, 30 May 2026 00:18:41 +0000 Subject: [PATCH 2/3] initial plan Co-authored-by: gh-aw-bot <259018956+gh-aw-bot@users.noreply.github.com> --- go.mod | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/go.mod b/go.mod index ea1d4b08374..f546a97c9f1 100644 --- a/go.mod +++ b/go.mod @@ -7,6 +7,7 @@ require ( charm.land/bubbletea/v2 v2.0.6 charm.land/huh/v2 v2.0.3 charm.land/lipgloss/v2 v2.0.3 + github.com/charmbracelet/colorprofile v0.4.3 github.com/charmbracelet/x/exp/golden v0.0.0-20260527151214-009e6338d40d github.com/cli/go-gh/v2 v2.13.0 github.com/creack/pty v1.1.24 @@ -43,7 +44,6 @@ require ( github.com/catppuccin/go v0.3.0 // indirect github.com/ccojocar/zxcvbn-go v1.0.4 // indirect github.com/cespare/xxhash/v2 v2.3.0 // indirect - github.com/charmbracelet/colorprofile v0.4.3 // indirect github.com/charmbracelet/harmonica v0.2.0 // indirect github.com/charmbracelet/ultraviolet v0.0.0-20260416161146-9c68a866306c // indirect github.com/charmbracelet/x/ansi v0.11.7 // indirect From 1d0c6a16c833952672dbcbfe7bdeef0b9b4142e0 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Sat, 30 May 2026 00:20:32 +0000 Subject: [PATCH 3/3] DDUw: catch not_planned docs-coverage/convention gaps with engine-example parity Co-authored-by: gh-aw-bot <259018956+gh-aw-bot@users.noreply.github.com> --- .github/workflows/daily-doc-updater.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/.github/workflows/daily-doc-updater.md b/.github/workflows/daily-doc-updater.md index eacaca409e0..167419a59ba 100644 --- a/.github/workflows/daily-doc-updater.md +++ b/.github/workflows/daily-doc-updater.md @@ -130,6 +130,11 @@ For each closed issue: 4. If all listed items are already documented, treat the issue as already addressed and skip it (do not continue to Step 2 for this issue). - Otherwise, treat it as an unaddressed gap and follow the normal Step 2 flow. - **closed as not_planned**: Do not create documentation based solely on this issue. Instead, cross-reference the issue's subject matter against commits from the same 7-day window (Step 2). If a related code change is found, treat it as a new documentation gap (independent of the original issue decision) and follow the normal Step 2 flow for that code change. + - **Cross-cutting docs-coverage / convention gaps (no triggering code change)**: If the issue describes a cross-cutting documentation **coverage or convention** gap (e.g., example parity across multiple reference pages, consistent terminology, missing cross-links) and carries the `cookie`, `improvement`, or `quick-win` label, *and no triggering code change was found above*, do not require a code change to act. Instead: + 1. Sample the files listed in the issue to confirm the gap still exists. + 2. If the gap persists **and** the fix direction is unambiguous (e.g., a phrase is clearly missing from a specific location), apply the fix and reference the issue with `Closes #NNN`. + 3. If the fix direction is a docs-convention choice (e.g., add parallel examples vs. omit redundant defaults vs. tabbed multi-engine blocks), **do not guess** — open a `[doc-healer]` maintainer-decision issue instead of editing. + 4. If a triggering code change *was* already found, the code-change path (Step 2) takes full precedence; do not apply this coverage-gap path as well. ### 1d. Scan Cookie-Labeled Automation Issues @@ -311,6 +316,8 @@ When calling `noop`, use this format: - **Test Understanding**: If unsure about a feature, review the code changes in detail - **Issue-Driven**: Proactively check open `documentation` issues — do not wait for them to be reported manually. - **Validate Examples**: YAML frontmatter examples in docs must be structurally valid. When in doubt, test with `gh aw compile`. +- **Default-value awareness for engine examples**: `engine: copilot` is the default and is redundant when `copilot` is the intended engine (omitting it produces identical behaviour). When normalizing engine examples, prefer *removing* the redundant `engine: copilot` line over duplicating workflow blocks with alternative engine values. This keeps examples engine-agnostic by default, reduces unnecessary doc size, and aligns with the `unbloat-docs` effort. +- **`unbloat-docs` guardrail**: Example-coverage fixes **must not** duplicate large workflow blocks. Prefer `` for multi-engine illustration only where the engine choice is genuinely instructive to the reader; otherwise omit the redundant `engine:` line rather than adding parallel copies. ## Important Notes