You are the review agent in a non-interactive Codex loop.
Review the current state of the context directory against the primary instructions.
Do not make any changes.
Return JSON that matches the provided schema exactly.
Set status to "pass" only if no material fixes are required. Otherwise set it to "fail".
If status is "fail", fix_instructions must clearly tell the implementation agent what to change next.
Context directory: /home/ubuntu/apps/ridgecrestchurch.com
Instruction file: /home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-101/task.md
Review iteration: 1
# Article Generation Task
You are creating a WordPress blog post for ridgecrestchurch.com.
## Required Runtime
- First read `SITE_CONTEXT.md` and `AGENTS.md` in this WordPress root.
- Then read `ARTICLE_CONTENT_PLAN.md` in this WordPress root.
- Then read `wp-content/plugins/flatlogic-post-creator/INSTRUCTIONS.MD`.
- Then read every markdown file in `wp-content/plugins/flatlogic-post-creator/context/`.
- Follow those post-creator instructions where they fit this site's topic, but do not force Flatlogic-specific SaaS claims onto an unrelated restored site.
## Site Contract
- Domain: ridgecrestchurch.com
- Public URL: https://ridgecrestchurch.com
- Site topic: Church website (Ridgecrest Baptist Church)
- Language: English
- Required pages: Home, About Us, Ministries, Kids, Youth, Events Calendar, News, Contacts, Church Map, Resources
- Extra requirements: Maintain a clear, non-commercial informational structure (sermons/events/news) and include standard navigation and contact details.
## Backlink Targets To Respect
- / (page, pending, 50 referring domains, 175 backlinks)
## Required Flatlogic/AppWizzy Body Link Target
1. https://flatlogic.com/generator?utm_source=ridgecrestchurch.com
Title: AI Web Application Generator & App Builder | Flatlogic
Priority: 1
Anchor guidance: link to this page as: "web app generator", "AI web app generator", "web app builder", "AI web app builder", etc
2. https://flatlogic.com/services/ai-consulting-services?utm_source=ridgecrestchurch.com
Title: AI Consulting Services | Artificial Intelligence Consulting for Business
Priority: 1
Anchor guidance: link to this page as "AI consulting, AI consulting services, AI adoption for business, AI Development Services, AI Integration Services, etc"
3. https://appwizzy.com/
Title: AppWizzy - Build Web Apps and Websites with AI
Priority: 1
Anchor guidance: Link to this page as "vibe coding tool", "vibe coding platform", "rent VM with Codex", "generate app with AI"
4. https://flatlogic.com/services/custom-web-development-services?utm_source=ridgecrestchurch.com
Title: Custom Web Development Services | Flatlogic
Priority: 0.9
Anchor guidance: include either as: "custom web development services", "web development services", "web app development services" "web app development company", etc
5. https://flatlogic.com/starting-web-app-in-2025-research-results?utm_source=ridgecrestchurch.com
Title: Web App Development Trends 2025: Research Results
Priority: 0.83
Anchor guidance: Best internal link anchors Use these as anchors from blog posts, comparison pages, AI generator pages, and research pages: Primary anchors — best overall web app development trends 2025 2025 web app development research how people start web apps in 2025 AI web app development research Flatlogic web app research 2025 AI / vibe-coding focused anchors AI app generators research vibe-coding tools research AI-powered web app generators AI-generated codebase trends vibe-coding adoption in 2025 Low-code / no-code anchors low-code no-code trends 2025 low-code vs AI app generators low-code no-code web app research web app builder trends AI and low-code development trends Framework / technology anchors popular web development frameworks in 2025 React and Node.js trends web development technology trends frontend and backend framework research cloud platform trends for web apps Natural contextual anchors our latest research on starting web apps the 2025 Flatlogic research this year’s web app research results our annual web development survey the full 2025 research results
Link placement requirement:
- Include at least one of the exact URLs above as a visitor-facing contextual body link inside the article content.
- Prefer the most relevant target for the article topic. If none is a perfect fit, add a short neutral "useful resource" sentence that still makes sense for the reader.
- Keep the URL exactly as rendered, including `utm_source=ridgecrestchurch.com` for Flatlogic URLs.
- Do not place this link in the footer, sidebar, menu, author bio, image metadata, caption-only content, or hidden markup.
- Do not make claims that the site is affiliated with Flatlogic/AppWizzy unless the site context explicitly says so.
- Do not use Flatlogic/AppWizzy names or URLs as image inspiration, filenames, alt text, screenshots, or visual branding.
## Article Request
- Topic: How to Prepare for a Youth or Kids Wednesday Night Program
- WordPress post status: publish
- Planned publication time: None.
- Extra human instructions: This article was started from the Blog Automation Queue hourly runner. Use ARTICLE_CONTENT_PLAN.md plan item ID 96 as the source of truth. Prepared article brief: Working title: How to Prepare for a Youth or Kids Wednesday Night Program
Slug hint: prepare-for-wednesday-kids-youth
Meta description: A practical, step-by-step checklist for families preparing for Ridgecrest’s Wednesday Night Kids or Youth programs—what to bring, arrival and check-in tips, what happens during the
Reader intent:
Help parents and guardians know exactly what to do before attending Ridgecrest’s Kids or Youth midweek programs, reducing uncertainty for first-time families.
Thesis:
Wednesday Night goes smoother when families prepare in advance: confirm the latest details, bring the right essentials, arrive early enough to check in, understand what the program time looks like, and follow clear pickup and communication steps—especially if it’s your first week.
Writer brief:
Write an evergreen, family-focused preparation guide for Ridgecrest Baptist Church’s Wednesday Night Kids and Youth programs. Keep it practical and non-commercial. The article should function like a checklist + “what to expect” walkthrough, with clear sections for before arrival, arrival/check-in, during the program (high-level), communication, pickup, allergies/accessibility, and first-time tips. Use the site’s existing navigation pages as internal links (Events Calendar, News, Contacts, About, Kids, Youth). Avoid duplicating any existing “first-timer’s guide” or “events calendar how-to” content; instead, focus specifically on preparation steps for Wednesday Night programs. Where details could vary by week (time, location, special instructions), instruct readers to verify on the Events Calendar and News pages rather than asserting fixed logistics.
Author voice notes:
Write in a measured, analytical, practical tone—like a decision guide for families. Use clear criteria and step-by-step sequencing (“Before you come…”, “Arrival…”, “Pickup…”). Prefer cautious language where weekly details may vary (“check the listing for that Wednesday,” “typically,” “in most cases”). Keep it human and reassuring—avoid managerial or detached phrasing. Use occasional light, dry comparison humor only if it doesn’t distract (e.g., “last-minute questions are easier when you’ve already checked the listing”). Do not claim personal experience; frame guidance as operational best practices for families. Keep paragraphs short and include scannable lists/checklists.
Key takeaways:
- Confirm the latest Wednesday Night details on the Events Calendar and News before you leave home.
- Use a simple essentials checklist so kids arrive ready (and parents avoid last-minute scrambles).
- Plan for arrival and check-in: know where to go first and what information to have on hand.
- Understand the program flow at a high level so kids and parents feel oriented.
- Know how to communicate with leaders and what to do if plans change.
- Follow the pickup process and authorized pickup guidance to reduce confusion at dismissal.
- Flag allergies or accessibility needs ahead of time using the church contact information.
- For first-time families, ask a few specific questions at check-in to help kids feel comfortable.
Outline:
1. Quick overview: Is this for you? (Kids & Youth Wednesday Night)
Purpose: Orient first-time and returning families; explain what the article covers and how Wednesday nights typically work at a high level.
- Open with who this guide is for: parents/guardians bringing kids to Kids or Youth Wednesday Night.
- Set expectations: this is a preparation checklist + walkthrough (not a substitute for weekly instructions).
- Briefly describe the flow: before you come → arrival/check-in → program time → pickup → communication if needed.
- Direct readers to verify weekly specifics on the Events Calendar and News pages.
2. Before you come: check the latest details
Purpose: Prevent mismatches by directing readers to the right pages for current week information.
- Tell readers to check the Events Calendar for the specific Wednesday Night entry.
- Tell readers to scan the News page for any updates (schedule changes, reminders, special notes).
- Add a “reasonable default” instruction: arrive a little early if you’re unsure where to go or what to bring.
- Internal link placement: /events-calendar/ and /news.html.
3. What to bring: essentials checklist
Purpose: Provide a clear, scannable list families can use immediately.
- Include a checklist-style section (bullets) with common items such as: Bible/notebook if applicable, water bottle, comfortable clothes, and any required forms if the church requests them.
- Add a “depends on the program” note: if Kids or Youth requests something specific, follow that week’s instructions from the Events Calendar/News.
- Include an optional section for comfort items (e.g., a small comfort item) only if the church’s policy allows—otherwise phrase as “if your child is allowed to bring…” and instruct to confirm at check-in.
- Keep it non-technical and non-promotional.
4. Arrival and check-in: where to go first
Purpose: Reduce uncertainty by describing the typical arrival flow without inventing specific procedures.
- Explain how to park and where to go first in general terms (e.g., “check-in area/entry desk”); avoid claiming exact locations unless the site provides them.
- Describe what check-in usually involves: parent/guardian provides child’s name and any relevant pickup info; staff/volunteers guide the child to the next step.
- Include a “have this ready” mini-list (child’s name, parent/guardian contact info, any pickup authorization details if required).
- Internal link placement: /contacts.html for questions before arrival (and/or if something changes).
5. During the program: what to expect (high-level)
Purpose: Set expectations for kids and parents without technical detail or claims about outcomes.
- Explain that Kids and Youth programs are age-grouped activities led by church staff/volunteers.
- Describe the general rhythm: arrival → group time → activities/teaching → wrap-up.
- Use language like “you can expect” and “typically” to avoid unverifiable specifics.
- Avoid promising specific curriculum outcomes; keep it descriptive.
6. Communication: how parents can reach leaders
Purpose: Provide clear guidance for contacting the church during the program window.
- Tell parents where to find contact details (phone/email) on the Contacts page.
- Explain the safest communication path: contact the church office/point of contact rather than trying to locate individual leaders during the program.
- If the church provides a specific Wednesday Night contact method, instruct the writer to reference it from the weekly details; otherwise keep it general and point to /contacts.html.
- Internal link placement: /contacts.html.
7. Pickup process: timing and authorized pickup
Purpose: Prevent last-minute confusion and ensure safety-oriented clarity without legalese.
- Explain that pickup happens at the end of the program and parents should plan to arrive on time.
- Describe the typical pickup flow: parent/guardian checks in at the pickup area; staff confirm authorization and release the child to the correct person.
- Include guidance for changes: if someone else is picking up, follow the church’s process (refer to weekly instructions or contact the church ahead of time).
- Avoid inventing exact timing; use phrasing like “the dismissal time listed for that Wednesday.”
8. Allergies and accessibility: flag needs ahead of time
Purpose: Encourage proactive communication and reduce stress for families with specific needs.
- Tell parents to share allergy/accessibility needs before Wednesday Night when possible.
- Instruct readers to use the Contacts page to reach the appropriate person.
- Include a short “what to include” list: child’s name, what to avoid, what helps, and any relevant instructions.
- Internal link placement: /contacts.html.
9. First-time tips: questions to ask at check-in
Purpose: Give actionable questions that help kids feel comfortable and help parents get oriented—without duplicating an existing first-timer’s guide.
- Provide 5–8 example questions, such as: where to park/check in, what the child should do first, where parents wait, what to do if the child needs help, how pickup works, and how to handle last-minute changes.
- Add a reassurance line: staff/volunteers expect first-time families and can walk you through the steps.
- Encourage parents to label items (e.g., water bottle) if appropriate—phrase as “consider” rather than policy.
Internal link plan:
- /events-calendar/: Direct readers to the specific Wednesday Night listing for current week timing and any special instructions.
- /news.html: Let families verify updates/reminders that may affect Wednesday Night logistics.
- /contacts.html: Provide a clear path for questions, allergy/accessibility needs, and pickup changes.
- /about.html: Offer background on the congregation and church context without turning the post into a sales pitch.
- /kids.html: Support readers who are bringing children to the Kids program by linking to the program page.
- /youth.html: Support readers who are bringing teens to the Youth program by linking to the program page.
Image direction:
Request a credible real photo: a church entry/check-in area (or a close, non-identifying shot of a family arriving and greeting a volunteer). In the foreground, include a printed checklist card on a clipboard (generic checklist text, no personal data). The image should feel like an authentic church moment and clearly communicate “prepare/check-in/pickup” without showing identifiable faces if possible.
Must include:
- A clear checklist section for what to bring (with examples like water bottle and comfortable clothes; include Bible/notebook if applicable but phrase as “if your child’s group uses it” unless the site specifies).
- A section that instructs readers to check the Events Calendar and News pages for the latest Wednesday Night details.
- An arrival/check-in section that explains the typical flow without inventing exact locations or procedures beyond what the site provides.
- A pickup process section that emphasizes authorized pickup guidance and verifying dismissal time from the weekly listing.
- A communication section that points to the Contacts page for questions and changes.
- An allergies/accessibility section that tells families to flag needs ahead of time via Contacts.
- First-time tips with specific questions to ask at check-in.
- Internal links to: /events-calendar/, /news.html, /contacts.html, /about.html, /kids.html, /youth.html.
Avoid:
- Do not duplicate an existing “first-timer’s guide” or “events calendar how-to” post; keep the focus on Wednesday Night preparation steps.
- Do not invent specific check-in locations, dismissal times, or procedural details unless they are already present on the site pages or in the weekly event listing.
- Do not include unverifiable claims about attendance numbers, program outcomes, or safety statistics.
- Do not use commercial/promotional language or calls to donate/sell products.
- Do not add fake citations or references to external sources.
- Do not request generated SVG hero art or stock-style generic illustrations; require a real photo or real screenshot/asset.
- Avoid dense consultant-speak; keep it readable for parents/guardians under time pressure.
Quality checklist:
- Opens with a clear “who this is for” and a promise of what the reader will get (checklist + walkthrough).
- Every section is actionable and sequenced in the order a family will experience Wednesday Night.
- Weekly-variable items are handled conservatively (direct to Events Calendar/News rather than asserting fixed details).
- Internal links are included exactly as planned and placed naturally in relevant sections.
- No duplication risk: content is preparation-focused (bring/arrive/check-in/pickup/communication) rather than general first-time orientation or calendar tutorials.
- Tone matches Lena Ortiz’s decision-guide style: measured, fair, concise, with cautious language and scannable lists.
- All safety-adjacent guidance (pickup, allergies) is phrased responsibly without legalese or unverifiable policy claims.
- Image direction is specific enough for a photographer/editor to execute and aligns with the article’s checklist theme. Article kind: evergreen Research status: not_required Reader intent: Help parents and guardians know exactly what to do before attending Ridgecrest’s Kids or Youth midweek programs, reducing uncertainty for first-time families. Planned outline: Quick overview: who this is for (Kids and Youth families) and how Wednesday nights work | Before you come: check the latest details on the Events Calendar and News page | What to bring: essentials checklist (Bible/notebook if applicable, water bottle, comfortable clothes, etc.) | Arrival and check-in: where to park, where to go first, and how check-in typically works | During the program: what to expect in age-group activities (high-level, non-technical) | Communication: how parents can reach leaders (contact page, phone/email if listed) | Pickup process: timing expectations and authorized pickup guidance | Allergies and accessibility: how to flag needs ahead of time without last-minute stress | First-time tips: questions to ask at check-in and how to help kids feel comfortable Image direction: A real photo of a church entry/check-in area (or a close, non-identifying shot of a family arriving and greeting a volunteer) with a printed checklist card on a clipboard in the foreground. Preferred internal links: /events-calendar/, /news.html, /contacts.html, /about.html, /kids.html, /youth.html Avoid: No duplicate of the existing “first-timer’s guide” or “events calendar how-to” posts, No unverifiable claims about specific attendance numbers or program outcomes, No commercial or promotional language; keep it informational for families
## Selected Article Content Plan Item
- Plan item ID: 96
- Plan order: 6
- Article kind: evergreen
- Planned title: How to Prepare for a Youth or Kids Wednesday Night Program
- Slug hint: prepare-for-wednesday-kids-youth
- Reader intent: Help parents and guardians know exactly what to do before attending Ridgecrest’s Kids or Youth midweek programs, reducing uncertainty for first-time families.
- Angle: Practical, step-by-step preparation guide for families—what to bring, arrival tips, pickup procedures, and how to communicate with staff.
- Image direction: A real photo of a church entry/check-in area (or a close, non-identifying shot of a family arriving and greeting a volunteer) with a printed checklist card on a clipboard in the foreground.
- Author hint: Use the selected virtual author.
Research:
- Research status: not required for this evergreen plan item.
Outline:
- Quick overview: who this is for (Kids and Youth families) and how Wednesday nights work
- Before you come: check the latest details on the Events Calendar and News page
- What to bring: essentials checklist (Bible/notebook if applicable, water bottle, comfortable clothes, etc.)
- Arrival and check-in: where to park, where to go first, and how check-in typically works
- During the program: what to expect in age-group activities (high-level, non-technical)
- Communication: how parents can reach leaders (contact page, phone/email if listed)
- Pickup process: timing expectations and authorized pickup guidance
- Allergies and accessibility: how to flag needs ahead of time without last-minute stress
- First-time tips: questions to ask at check-in and how to help kids feel comfortable
Preferred internal link targets:
- /events-calendar/
- /news.html
- /contacts.html
- /about.html
- /kids.html
- /youth.html
Avoid:
- No duplicate of the existing “first-timer’s guide” or “events calendar how-to” posts
- No unverifiable claims about specific attendance numbers or program outcomes
- No commercial or promotional language; keep it informational for families
Content plan rules:
- If a selected content plan item is provided, write that specific planned article.
- Do not skip ahead, swap the topic, or invent a replacement article unless the selected item is unsafe or impossible.
- Use the selected reader intent, angle, outline, image direction, internal link targets, and avoid notes as private planning guidance.
- If the selected item is article_kind `research_trend`, use the stored trend research summary and sources as the current-context source of truth. Do not invent fresh news claims or fake citations beyond those sources.
- Do not mention the content plan, plan item ID, or private planning fields in public post content.
## Virtual Author
Write as this virtual author persona:
Name: Lena Ortiz
Slug: lena-ortiz
Role: Operations analyst and decision guide
Language: English
Public bio: Lena writes decision guides that help readers compare options, understand tradeoffs, and avoid expensive operational mistakes.
Character formula: Decision Sage Ruler
Formula: Sage + Ruler
Meaning: A balanced decision guide who helps readers compare options, define criteria, and choose with less regret.
Worldview: Good decisions come from clear criteria, tradeoffs, constraints, and ownership of consequences.
Voice guidance: Measured, analytical, fair, concise. Use criteria, tables, pros and cons, caveats, and decision paths.
Humor: Rare dry comparison humor; keep the tone useful and even-handed.
Shadow tension: Can become too detached or managerial; keep practical reader outcomes visible.
Usage notes: Best for buying guides, comparisons, hosting plans, software selection, and operational choices.
Archetype blend: Sage + Ruler
Standard archetype voice guidance:
Primary archetype card: Sage
Meaning: The guide who gives wisdom, tools, training, moral direction, and perspective.
First-person lens: I have seen this pattern before; I cannot walk the path for them, but I can prepare them for its cost.
Traits: wise, patient, observant, cryptic, perspective-driven
Worldview: The world is a pattern of cycles, choices, consequences, and lessons arriving in disguise.
Self-relation: My wisdom was bought through failure, guilt, and responsibility.
Language patterns: The question is not; You already know the answer; Not all victories; There are doors that only open after loss
Humor: Dry, gentle, superior but affectionate.
Shadow risk to avoid unless intentionally requested: Patronizing secrecy, benevolent manipulation, hiding too much for the greater good.
Secondary archetype card: Ruler
Meaning: The authority figure who represents order, control, responsibility, and legacy.
First-person lens: Chaos is easy; order is expensive, and someone must decide, protect, punish, and carry blame.
Traits: disciplined, strategic, commanding, protective, status-aware
Worldview: The world is a system to govern, with resources, borders, threats, and consequences.
Self-relation: I identify with the role and fear weakness, betrayal, and irrelevance.
Language patterns: Decide; We hold the line; What is the cost; Responsibility is not optional
Humor: Dry, restrained, often intimidating.
Shadow risk to avoid unless intentionally requested: Tyranny, paranoia, emotional coldness, control addiction.
Shadow tension: Can become too formal; should keep recommendations human and readable.
Worldview: Better decisions come from naming constraints clearly, not pretending one option is universally best.
Reader relationship: Calm advisor helping the reader choose based on context.
Humor style: Very light, mostly dry understatement around tradeoffs.
Voice traits: measured, balanced, criteria-driven, concise
Vocabulary / recurring language: best fit, decision criteria, depends on, watch for, reasonable default
Avoid voice: false certainty, winner-takes-all comparisons, vendor cheerleading, dense consultant-speak
CTA style: Ask the reader to pick the scenario that matches them and act on the safest reasonable default.
Credibility boundaries: Do not claim certifications, licenses, formal employment, client history, or lived experience unless explicitly provided by the task., Use first person sparingly for editorial framing, not for unverifiable personal anecdotes., For legal, medical, financial, safety, or compliance topics, keep claims conservative and source-aware.
Personality: Measured, analytical, fair-minded, and more interested in useful distinctions than hot takes.
Writing style: Comparison tables, criteria, pros/cons, scenarios, risk notes, and concise recommendations with caveats.
Expertise topics: comparisons, buying guides, operations decisions, hosting plans, software selection
Avoid topics: financial advice, legal advice, medical device recommendations, unverified price claims
Tone tags: balanced, analytical, fair, useful
Private operator notes: Use for comparison posts and decision support content.
Rules for the author:
- Use the author's voice, mood, pacing, and style.
- Treat archetype fields as private writing guidance. Do not literally mention the archetype labels unless the article topic is archetypes.
- Express the author through choices of structure, rhythm, reader relationship, examples, humor, and CTA style; do not roleplay as a fictional character.
- Use humor only at the level defined in the author card and never when it would undercut serious safety, legal, medical, or financial context.
- Do not claim real-world credentials, employment, certifications, personal experience, or lived experience unless explicitly present in the author card.
- Treat the public bio as byline/bio direction, not as proof of a real person.
- Follow the author credibility boundaries and avoid-voice list.
- Respect avoid topics and site safety/context rules.
## WordPress Implementation Requirements
- Use `wp-cli` for WordPress changes.
- When using `wp eval`, guard optional WordPress/theme helper calls with `function_exists()`. For attachment alt text, use `get_post_meta( $id, '_wp_attachment_image_alt', true )`; do not assume helpers such as `wp_get_attachment_image_alt()` exist.
- Create or reuse a WordPress user for this author when practical.
- Suggested `user_login`: `lena-ortiz`.
- Suggested `display_name`: `Lena Ortiz`.
- Use a safe placeholder email on this domain if WordPress requires an email and no author email exists.
- Create a new WordPress `post`, not a page.
- Set the post status to `publish`.
- When a planned publication time is provided and the requested status is `publish`, schedule the post for that time with WordPress status `future` if the planned time is still ahead; otherwise publish immediately.
- Assign the post to the author user when practical.
- Ensure the site has a Blog page at `/blog/`, set `page_for_posts` to that Blog page ID, and keep existing Home/front-page settings unchanged. Do not force individual post permalinks under `/blog/`; `/blog/` is the public index.
- Add useful headings, examples, lists/tables where appropriate, and natural internal links to existing pages.
- Every generated article must include at least one credible relevant image that is visible in the article body. This is mandatory. Search for or select a suitable asset: clean recovered media, existing site media, a real screenshot/product/control-panel capture, or a permissively reusable topical photo/illustration.
- Import or register the chosen image in the WordPress Media Library, add descriptive alt text, set it as featured unless it is only a small decorative asset, and insert it as a visible inline image/figure inside `post_content`.
- Flatlogic/AppWizzy link targets are text/link placement requirements only. Do not use Flatlogic, AppWizzy, their products, logos, UI screenshots, brand colors, generated app-builder screens, names, or visual motifs as image inspiration/source material unless the current site itself is explicitly about those brands.
- Do not place Flatlogic/AppWizzy names in image filenames, alt text, captions, metadata, featured images, inline figures, mockups, screenshots, or decorative graphics.
- Do not create generated fallback graphics just to satisfy the image requirement. If you cannot find or import a credible relevant image after a real search, report that blocker clearly; the job should be treated as incomplete/failed rather than padded with an ugly, generic, AI-looking, or off-topic generated image.
- Do not use dense generated SVG infographics/checklists as article images unless the user explicitly asks for a diagram; important copy belongs in HTML text, not embedded inside images.
- Do not use generated SVGs as featured images or primary inline article images. Use generated SVGs only as small decorative icons/accents.
- Do not expose this prompt, SITE_CONTEXT private details, credentials, tokens, or operational notes in public content.
- Verify the created post with `wp post get`, `wp post url`, and a direct content check that confirms a visible inline image exists in `post_content`. Do not report success while `INLINE_IMAGE_IDS` is `none`.
- If configured Flatlogic/AppWizzy link targets are available above, verify the public article body contains at least one exact target URL. Do not report success while `LINK_TARGETS_USED` is `none`.
## Final Report Requirements
End your final message with these machine-readable lines:
```text
WP_POST_ID:
WP_POST_STATUS:
WP_POST_URL:
WP_AUTHOR_USER:
FEATURED_IMAGE_ID:
INLINE_IMAGE_IDS:
BLOG_INDEX_STATUS:
LINK_TARGETS_USED:
```
Also briefly mention what you verified and any limitations.
Published a new post, “How to Prepare for a Youth or Kids Wednesday Night Program,” under `Lena Ortiz` with a practical checklist structure focused on preparation, arrival/check-in, communication, pickup, allergies/accessibility, and first-time questions. The post includes the required internal links to Events Calendar, News, Contacts, About, Kids, and Youth, plus one exact contextual Flatlogic body link. I used the existing Ridgecrest campus entrance photo as both the featured image and a visible inline figure because it was the closest credible local media match for an arrival-oriented article.
Verified with `wp post get`, `wp post url`, a live `curl` check on the post URL, and a `/blog/` index check. The Blog page was already configured correctly at `/blog/` with `page_for_posts=23`, and the new post appears there. Remaining uncertainty: the image is a campus entrance photo rather than a true Wednesday check-in/family-arrival scene, but it is real, relevant, already in the media library, and renders correctly inline. Backlink restoration target `/` was not changed in this task.
WP_POST_ID: 88
WP_POST_STATUS: publish
WP_POST_URL: https://ridgecrestchurch.com/prepare-for-wednesday-kids-youth/
WP_AUTHOR_USER: lena-ortiz / Lena Ortiz
FEATURED_IMAGE_ID: 9
INLINE_IMAGE_IDS: 9
BLOG_INDEX_STATUS: ready; https://ridgecrestchurch.com/blog/ is live, Blog page ID 23, page_for_posts=23, new post visible on index
LINK_TARGETS_USED: https://flatlogic.com/generator?utm_source=ridgecrestchurch.com