Re-verified and fixed the existing published post **ID 157** to address the review issues.
## What I changed
1) **Corrected the inline image verification**
- Rechecked `post_content` for the inline image block.
- Found the block contains `wp:image {"id":9,...}`, and the content includes a visible ``.
- Verified inline image presence by direct `post_content` checks and extracted the referenced inline attachment id(s).
2) **Added additional required third-party external links (with `utm_source=ridgecrestchurch.com`)**
- The post previously only had 1 third-party external link with the required `utm_source`.
- Added 2 more credible third-party sources *in-body*:
- https://www.access-board.gov/ict/?utm_source=ridgecrestchurch.com
- https://www.ada.gov/?utm_source=ridgecrestchurch.com
## Verification performed after changes
- `wp post get 157` and `wp post url 157` confirmed the post is reachable at:
- https://ridgecrestchurch.com/church-map-parking-tips-ridgecrest/
- Confirmed the article body contains a visible inline image (``).
- Extracted inline image attachment id referenced by the image block: **9**.
- Confirmed there are now **at least 2** third-party `utm_source=ridgecrestchurch.com` external links in `post_content` (Access Board, ADA.gov).
- Confirmed post author user id remains **9** (“Felix Rowan”).
## Remaining risks / uncertainty
- The “direct” inline image attachment id detection relies on the `wp:image {"id":...}` block pattern in stored Gutenberg content. This is consistent here, but if the editor later changes the block structure (e.g., removes the `id`), the extracted inline attachment list could again show as incomplete even if an `` is still present.
```text
WP_POST_ID: 157
WP_POST_STATUS: publish
WP_POST_URL: https://ridgecrestchurch.com/church-map-parking-tips-ridgecrest/
WP_AUTHOR_USER: felix-rowan / Felix Rowan
FEATURED_IMAGE_ID: 9
INLINE_IMAGE_IDS: 9
BLOG_INDEX_STATUS: ready; page_for_posts=23 (https://ridgecrestchurch.com/blog/)
LINK_TARGETS_USED: none
```