@gurupanguji

wp:quote Safe Shape Paragraph Breaks Implementation Plan

For agentic workers: REQUIRED SUB-SKILL: Use superpowers:subagent-driven-development (recommended) or superpowers:executing-plans to implement this plan task-by-task. Steps use checkbox (- [ ]) syntax for tracking.

Goal: Extend scripts/normalize_wp_quotes.py so wp:quote paragraphs with harmless <p> attributes, <br /><br /> paragraph breaks, empty spacing paragraphs, and link-only paragraphs count as safe, while keeping file-level skip reporting for any still-unsupported quote blocks.

Architecture: Make a narrow parser change in the quote normalizer rather than broadening the entire HTML model. Add tests first for the new paragraph shapes, then implement the minimal matcher and rendering update, then rerun the dry-run normalizer to inspect which files still skip and why.

Tech Stack: Python 3, unittest, regex parsing, markdown generation for Jekyll posts

---

Task 1: Add Failing Tests For The New Safe Shape

Files:

• Modify: tests/test_normalize_wp_quotes.py

• Step 1: Add a failing unit test for <br /><br /> paragraph splitting

Cover a wp:quote block whose paragraph content includes <br /><br /> and assert the markdown output becomes:

> Paragraph one.
>
> Paragraph two.

• Step 2: Add a failing test for a paragraph with an id attribute

Use the user-provided third-block example shape and assert the paragraph itself is now considered safe.

• Step 3: Add failing tests for empty and link-only quote paragraphs

Cover:

• <p></p> becoming >

• <p><a href="...">Title</a></p> becoming > [Title](...)

• Step 4: Add a regression test for file-level skipping when another block remains unsupported

Construct a post with:

• one now-safe quote paragraph sequence
• one still-unsupported quote block

Assert the whole file remains skipped and that a reason is still reported.

• Step 5: Run the focused quote-normalizer test file

Run:

python3 -m unittest tests/test_normalize_wp_quotes.py

Expected: FAIL on the new cases before implementation.

Task 2: Expand The Safe Quote Matcher

Files:

• Modify: scripts/normalize_wp_quotes.py

• Modify: tests/test_normalize_wp_quotes.py

• Step 1: Update paragraph matching to allow harmless <p> attributes

Adjust the paragraph parser so <p> tags with attributes like id still match as safe quote paragraphs.

• Step 2: Preserve <br /><br /> as a markdown paragraph break

Implement the smallest possible rendering change so double breaks become:

>

between quote paragraphs instead of collapsing into one run-on block.

• Step 3: Treat empty and link-only paragraphs as safe mechanical shapes

Implement the smallest possible support for:

• empty <p></p> as >

• single-anchor paragraphs as > [text](url)

• Step 4: Keep all existing hard skips intact

Do not relax support for:

• nested wp:quote
• image or figure content
• malformed markers
• arbitrary rich inner markup

• link-only quote paragraphs are supported in this scope

• Step 5: Run the quote-normalizer tests again

Run:

python3 -m unittest tests/test_normalize_wp_quotes.py

Expected: PASS

Task 3: Re-run The Dry-Run Audit

Files:

• Verify: scripts/normalize_wp_quotes.py

• Verify: _posts/

• Step 1: Run the normalizer in dry-run mode

Run:

python3 scripts/normalize_wp_quotes.py

• Step 2: Inspect the output for the target post

Check whether _posts/2025-07-21-negativity-blackholes-unburdening-and-resilience.md now:

• converts cleanly, or

• still skips but with a more precise remaining blocker

• Step 3: Summarize the remaining skipped files

Capture the current skip list so the user can provide the next safe-shape suggestion from a concrete backlog instead of guessing.

Task 4: Verify And Prepare Review

Files:

• Verify: tests/test_normalize_wp_quotes.py

• Verify: scripts/normalize_wp_quotes.py

• Step 1: Re-run the focused automated tests

Run:

python3 -m unittest tests/test_normalize_wp_quotes.py

Expected: PASS

• Step 2: Keep the diff narrow

Verify the implementation changes are limited to:

• the quote normalizer
• its test file

• no unrelated content rewrites

• Step 3: Leave the next backlog visible

Make sure the final report still includes which files remain skipped, because the user explicitly wants that list to drive the next cleanup rule.