docs: reconcile bot-pipeline-unblock plan doc with #2847 implementation

[wheels-bot]

The plan doc committed in #2847 (docs/superpowers/plans/2026-06-03-bot-pipeline-unblock.md) had two cosmetic drifts from the merged code that could mislead a future reader: all task checkboxes remained unchecked despite the work shipping, and the allowlist note listed web/sites/*/src/content/** as a low-risk arm that the final classify-conflicts.sh dropped. This PR makes two surgical fixes so the document accurately reflects what shipped.

Fixes #2850

Changes

• docs/superpowers/plans/2026-06-03-bot-pipeline-unblock.md

  • Added a blockquote note after the Verification paragraph: "Implementation complete as of feat(bot): unblock release pipeline (title-lint, freshen, tiered conflict resolution) #2847. Task checkboxes below are left unchecked for historical fidelity — they tracked progress during the agentic implementation run and no longer reflect pending work."
  • Updated the "Low-risk allowlist" bullet in "Decisions carried from spec open-questions" to note that the shipped script dropped the web/sites/*/src/content/** arm — *.md/*.mdx matching any path already covers MDX content files, and non-markdown files under content trees now correctly escalate. Points to the script as the authoritative allowlist.

• CHANGELOG.md — one-line [Unreleased] entry.

Screenshots needed

None.

[wheels-bot]

Wheels Bot — Reviewer A

TL;DR: Pure documentation reconciliation — adds an implementation-complete banner to the pipeline-unblock plan doc and appends an inline note clarifying what the shipped classify-conflicts.sh dropped. Two files, 4 lines added, 1 line changed. No code paths, no engine-specific CFML, no tests required. My verdict is comment (one minor CHANGELOG nit; nothing blocking merge).

---

Docs

CHANGELOG.md — entry placed under ### Changed for an internal plan-doc reconciliation

The [Unreleased] changelog is read by users and contributors to understand what is new or changed in the framework. An internal agentic planning document (docs/superpowers/plans/) is not a user-facing artifact — readers checking what changed in Wheels won't benefit from this entry the way they do from the RustCFML adapter entry above it. The fix cost is negligible: either omit the CHANGELOG entry entirely (the plan doc is self-describing) or move it to a prose-only comment in the PR body. This is a nit, not a blocker.

Everything else checks out:

• Plan doc accuracy: the blockquote banner correctly marks the work shipped in #2847, and the allowlist clarification accurately describes why web/sites/*/src/content/** was dropped from classify-conflicts.sh (the *.md/*.mdx glob already covers MDX content files at any path; keeping a redundant glob would have been noise).
• Commit message (docs: reconcile bot-pipeline-unblock plan doc with #2847 implementation): valid type, ≤ 100-char header (69 chars), sentence-case, body explains the why — fully conformant with commitlint.config.js.
• DCO: Signed-off-by: claude[bot] <41898282+claude[bot]@users.noreply.github.com> matches the commit author — clean.
• No cross-engine concerns: no CFML touched.
• No test coverage gap: documentation-only change; no spec required.
• PR body: clear summary of both changes, references the originating issue (#2850) and the implementation PR (#2847).

[wheels-bot]

Wheels Bot — Reviewer B (round 1)

A's review is sound. The CHANGELOG nit is legitimate and concrete, and all verifiable claims check out against the actual diff and commit. I agree with the comment verdict and the single finding is actionable — removing that one CHANGELOG line would be a clean fix.

Sycophancy

None detected. A issued a comment (not approve) and backed it with a specific finding rather than a blanket LGTM.

False positives

None detected.

• A's commit-message character count is off by 2 (71 chars, not 69), but the conclusion — valid, under 100 — is correct.
• A's DCO check is accurate: Signed-off-by: claude[bot] <41898282+claude[bot]@users.noreply.github.com> matches the commit author identity.
• A's plan-doc accuracy assessment is accurate: the blockquote correctly flags the unchecked boxes as historical, and the allowlist note correctly explains why web/sites/*/src/content/** was dropped from classify-conflicts.sh.

Missed issues

None detected. The diff is two files — CHANGELOG.md (one line added) and the plan doc (one blockquote + one inline sentence). A covered every material surface: doc content accuracy, commit hygiene, DCO, no CFML touched, no test gap.

Verdict alignment

A's comment verdict is consistent with calling the CHANGELOG entry a "nit, not a blocker." Correct call — nothing here warrants blocking merge.

Convergence

Aligned. A correctly identified the only real issue: adding an internal planning doc entry to the user-facing [Unreleased] CHANGELOG creates noise for Wheels framework users who use that section to understand what changed. The fix is one line: remove the added CHANGELOG.md bullet (the PR body already documents the reconciliation). Joint recommendation: apply that one-line fix, then the PR is clean to merge.