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-80/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 Use Our Events Calendar: RSVP, Reminders, and What to Bring - 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 94 as the source of truth. Prepared article brief: Working title: How to Use Our Events Calendar: RSVP, Reminders, and What to Bring Slug hint: how-to-use-events-calendar-rsvp-reminders-what-to-bring Meta description: Learn how to find events fast on Ridgecrest Baptist Church’s calendar, confirm RSVP details, set reminders, and know what to bring for common gatherings—so you can show up prepared Reader intent: Help me quickly find upcoming events, RSVP/confirm details, set reminders, and know what to bring so I feel comfortable attending. Thesis: The Events Calendar is designed to answer the practical questions—when, where, who it’s for, and whether you need to RSVP—so you can plan ahead with reminders and arrive prepared for the most common event types. Writer brief: Write an evergreen, practical walkthrough for first-time visitors and regular attendees on how to use ridgecrestchurch.com’s Events Calendar. The article should be step-by-step and action-oriented: where to find the calendar, how to scan it quickly, how to interpret event details (date/time, location, age groups), how RSVP/confirmation works (including what to do if an event requires it and who to contact), how to set reminders (phone calendar and what to expect from confirmation messages), and what to bring for common event types (worship services, kids/youth activities, community events). Keep the tone careful and grounded—no hype, no unverifiable claims, and no assumptions about specific event policies beyond what the site pages can support. Where details vary by event, explicitly instruct readers to check the event listing and, if unsure, contact the church using the provided contact/navigation pages. Use internal links to: /events-calendar, /contacts.html (or /contact.php if that is the actual primary contact endpoint), /kids, /youth, /about. Maintain a non-commercial, informational structure focused on sermons/events/news and standard navigation/contact details. Author voice notes: Write in a careful, grounded “research explorer” style: practical steps first, then brief explanations of why each step matters. Avoid false certainty—use language like “check the event listing for…” and “if the listing indicates…” when policies may vary by event. Keep the tone welcoming and non-technical. End sections with usable next actions (e.g., “If you can’t find RSVP instructions, contact us via the site’s contact page.”). Do not include personal anecdotes or unverifiable claims. Light, dry humor is optional but should not distract from clarity. Key takeaways: - You can find the right event quickly by scanning the calendar for date/time, location, and age group labels. - Event listings tell you whether RSVP/confirmation is required—follow the instructions on that specific event. - If you need to RSVP, use the contact method listed for that event; if you don’t receive confirmation, reach out. - Set reminders immediately after you confirm details so you don’t miss check-in times or family activities. - Bring what’s typically requested for the event type (and check the listing for any special items). - If accessibility, family needs, or questions come up, contact the church before the event using the site’s contact pages. Outline: 1. Where to find the Events Calendar (and how to scan it fast) Purpose: Help readers locate the calendar and quickly identify relevant events without getting lost. - Direct readers to /events-calendar and explain what they’ll see there (calendar view + event cards/listing, if applicable). - Teach a fast scan method: look first for the date, then time, then any location label, then the audience/age group tag. - Explain how to use the calendar controls (month/week navigation, filters if present, search if present) in a way that matches the actual UI on the site. - Set expectations: event details can differ by listing, so the calendar is the starting point, not the final authority. 2. Understanding event details: date/time, location, and age groups Purpose: Translate event-listing fields into clear “what it means for me” guidance. - Break down the common fields: date, start/end time (or start time), location/room, and any age group notes. - Explain what “age group” typically implies (e.g., kids/youth participation vs. family-friendly events) without assuming specific program structure beyond the site’s Kids/Youth pages. - If the event listing includes check-in instructions, highlight that as the next step. - Encourage readers to read the event description for any special notes (parking, arrival time, materials, accessibility notes). 3. RSVP/confirmation basics (what to do if an event requires it, and who to contact) Purpose: Remove uncertainty about RSVP by giving a simple decision tree. - State plainly: some events may require RSVP; others may not—always follow the instructions on that event’s listing. - If RSVP is required, instruct readers to use the method provided (link/form/email/phone) and to include any requested info (names, number attending, age group) as shown. - If confirmation is expected, explain what to look for (e.g., confirmation message or follow-up) without promising specific timing. - If the reader can’t find RSVP instructions or has questions, direct them to /contacts.html and/or /contact.php and suggest contacting the church using the contact method listed. - Include a short “If you don’t hear back” guidance: wait a reasonable window per the site’s instructions (if none exist, advise contacting again rather than guessing). 4. Setting reminders: phone calendar tips and email/text confirmation expectations Purpose: Help readers operationalize the plan so they arrive prepared. - Recommend adding the event to a phone calendar immediately after RSVP/reading the listing. - Provide practical reminder settings: at least one reminder the day before and one on the day of the event (adjust based on arrival/check-in needs noted in the listing). - Explain how to handle confirmation messages: save the email/text details, or screenshot the confirmation page if applicable. - If the event includes a specific arrival time or check-in location, instruct readers to set reminders that account for that (e.g., earlier arrival). - Avoid claiming the church sends confirmations for every event; instead, say “if the listing indicates confirmation.” 5. What to bring for common events (worship services, kids/youth activities, community events) Purpose: Give a clear, non-overwhelming packing guide tied to typical event categories. - Worship services: general guidance (arrive early if check-in is mentioned; bring a Bible if you prefer, and any personal items you need). Avoid asserting specific service requirements not confirmed on the site. - Kids: direct readers to /kids for program expectations and instruct them to check the specific event listing for any items (e.g., pickup/check-in info, what to label). - Youth: direct readers to /youth and instruct them to check the event listing for any activity-specific items. - Community events: instruct readers to read the listing for any “bring” notes (registration items, seating needs, weather considerations) and to contact the church if unclear. - Include a “when in doubt” line: the event listing wins; contact the church via /contacts.html or /contact.php for specifics. 6. Accessibility and family needs: seating, check-in, and contact options Purpose: Address common concerns respectfully and practically. - Encourage readers to review the event listing for accessibility notes (if present) and to contact the church ahead of time for accommodations. - Explain how check-in typically works at church events in general terms (arrive early, look for signage/greeters, ask at the welcome/contact point) without inventing a specific system. - Direct readers to /contacts.html and/or /contact.php for accessibility questions. - Mention family needs: if bringing kids/youth, confirm the correct age group and check-in expectations using the listing and the Kids/Youth pages. 7. If you’re unsure: when to reach out and what questions to ask Purpose: Provide a short script so readers know exactly what to ask. - When to reach out: RSVP required but unclear, no RSVP instructions found, accessibility needs, arrival/check-in questions, or “what to bring” uncertainty. - What to ask (bullet list): event date/time, location/room, whether RSVP is required, check-in time, where to park/enter (if relevant), what to bring, and any accessibility accommodations. - Include a reminder to include the event name/date in the message so staff can respond faster. - Direct to /contacts.html and/or /contact.php. 8. Quick checklist recap (before you go) Purpose: End with a scannable, actionable summary. - Find the event on /events-calendar and confirm: date/time, location, and age group. - Read the listing for RSVP requirements and follow the instructions. - If RSVP is required, save confirmation details and add the event to your phone calendar. - Check the listing for any “what to bring” notes; when unsure, contact the church. - Plan for accessibility/family needs by asking ahead of time if needed. Internal link plan: - /events-calendar: Primary navigation target for the article’s core walkthrough; readers should land here to follow the steps. - /contacts.html: General contact destination for RSVP questions, accessibility needs, and “what to bring” clarifications. - /contact.php: Use if this is the actual contact form/endpoint on the site; include as a practical alternative depending on site structure. - /kids: Support kids-related guidance and direct readers to the Kids page for program expectations. - /youth: Support youth-related guidance and direct readers to the Youth page for program expectations. - /about: Provide context for the church and reinforce that the calendar is part of the broader ministry information on the site. Image direction: Use one real, credible image: either (A) a real photo of a church bulletin or printed event flyer on a table next to a phone displaying the Events Calendar page with event details visible (no brand ads), or (B) a clean screenshot-style photo of the Events Calendar section on a desktop browser showing an example event card/details clearly. Ensure the image reflects the actual ridgecrestchurch.com Events Calendar layout and includes readable event information. Must include: - A clear step-by-step path to finding events on /events-calendar. - How to interpret event listing details (date/time, location, age group). - RSVP guidance that emphasizes following the specific event listing and contacting the church if unclear. - Reminder guidance that focuses on adding events to a phone calendar and saving confirmation details when applicable. - A “what to bring” section organized by common event types (worship services, kids, youth, community events) with instructions to verify event-specific notes. - Accessibility/family needs guidance that directs readers to contact the church ahead of time. - A final quick checklist recap. - Internal links to /events-calendar, /contacts.html, /contact.php (as applicable), /kids, /youth, and /about. Avoid: - Generic filler like “check the website” without telling readers exactly what to look for on the calendar. - Thin content that repeats the outline without actionable steps. - Assuming RSVP is required for all events or that confirmations are always sent via a specific channel. - Inventing event policies, staff names, response times, or attendance outcomes. - Commercial/sponsorship language or any framing that suggests selling products. - Duplicate titles or obvious variants of other existing plan items (e.g., “first-time guide to ministries/kids/youth” or “Sunday service checklist”). - Unverifiable claims about what Ridgecrest Baptist Church does unless the site pages themselves support it. Quality checklist: - Matches the site’s actual Events Calendar UI (fields, labels, and navigation controls) and does not describe features that aren’t present. - RSVP section uses conditional language (“if required,” “if the listing indicates”) and always points to the event listing + contact pages for uncertainty. - Reminder section is practical and does not promise specific confirmation delivery behavior unless indicated by the site. - “What to bring” guidance is general enough to be evergreen but still tied to event categories and instructs readers to verify event-specific notes. - Accessibility/family needs guidance is respectful, non-alarming, and directs readers to contact the church ahead of time. - Includes the required internal links and maintains a non-commercial informational structure. - Tone is welcoming, careful, and grounded; no invented statistics, no fake citations, no personal anecdotes. - Ends with a scannable checklist recap that a reader can use immediately before attending. Article kind: evergreen Research status: not_required Reader intent: Help me quickly find upcoming events, RSVP/confirm details, set reminders, and know what to bring so I feel comfortable attending. Planned outline: Where to find the Events Calendar (and how to scan it fast) | Understanding event details: date/time, location, and age groups | RSVP/confirmation basics (what to do if an event requires it, and who to contact) | Setting reminders: phone calendar tips and email/text confirmation expectations | What to bring for common events (worship services, kids/youth activities, community events) | Accessibility and family needs: seating, check-in, and contact options | If you’re unsure: when to reach out and what questions to ask | Quick checklist recap (before you go) Image direction: A real photo of a church bulletin/printed event flyer on a table beside a phone showing a calendar event (no brand ads), or a clean screenshot-style photo of the Events Calendar section on a desktop browser with event details visible. Preferred internal links: /events-calendar, /contacts.html, /contact.php, /kids, /youth, /about Avoid: Posting duplicate titles or obvious variants of existing plan items (e.g., first-timer guide to ministries/kids/youth, Sunday service checklist)., Thin filler content that doesn’t explain specific steps for using the calendar., Commercial language or sponsorship-style framing., Unverifiable claims about attendance or outcomes. ## Selected Article Content Plan Item - Plan item ID: 94 - Plan order: 4 - Article kind: evergreen - Planned title: How to Use Our Events Calendar: RSVP, Reminders, and What to Bring - Slug hint: how-to-use-events-calendar-rsvp-reminders-what-to-bring - Reader intent: Help me quickly find upcoming events, RSVP/confirm details, set reminders, and know what to bring so I feel comfortable attending. - Angle: Practical walkthrough for visitors and regular attendees on navigating the church events calendar and preparing for common event types. - Image direction: A real photo of a church bulletin/printed event flyer on a table beside a phone showing a calendar event (no brand ads), or a clean screenshot-style photo of the Events Calendar section on a desktop browser with event details visible. - Author hint: Use the selected virtual author. Research: - Research status: not required for this evergreen plan item. Outline: - Where to find the Events Calendar (and how to scan it fast) - Understanding event details: date/time, location, and age groups - RSVP/confirmation basics (what to do if an event requires it, and who to contact) - Setting reminders: phone calendar tips and email/text confirmation expectations - What to bring for common events (worship services, kids/youth activities, community events) - Accessibility and family needs: seating, check-in, and contact options - If you’re unsure: when to reach out and what questions to ask - Quick checklist recap (before you go) Preferred internal link targets: - /events-calendar - /contacts.html - /contact.php - /kids - /youth - /about Avoid: - Posting duplicate titles or obvious variants of existing plan items (e.g., first-timer guide to ministries/kids/youth, Sunday service checklist). - Thin filler content that doesn’t explain specific steps for using the calendar. - Commercial language or sponsorship-style framing. - Unverifiable claims about attendance or outcomes. 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: Rowan Ellis Slug: rowan-ellis Role: Research notes editor Language: English Public bio: Rowan writes grounded research-style articles that connect source material, practical context, and careful conclusions. Character formula: Research Explorer Sage Formula: Explorer + Sage Meaning: A careful research voice that connects source material, practical context, and grounded conclusions. Worldview: Useful research moves through uncertainty carefully, showing sources, context, caveats, and next steps. Voice guidance: Careful, source-aware, curious, grounded, thoughtful. Use evidence, caveats, and plain conclusions. Humor: Very light, dry, mostly absent when evidence or stakes matter. Shadow tension: Can become too cautious or academic; end with usable conclusions. Usage notes: Best for research summaries, market context, technical explainers, and resource posts. Archetype blend: Explorer + Sage Standard archetype voice guidance: Primary archetype card: Explorer Meaning: The restless seeker of freedom, movement, discovery, and new worlds. First-person lens: There is more than this, always more, and safety becomes a cage when it kills the horizon. Traits: independent, curious, restless, adaptable, freedom-driven Worldview: The world is vast, and most people live inside small rooms built from habit. Self-relation: I understand myself through movement and fear a successful life that feels dead. Language patterns: Let us go; I want to see it myself; What is past the border; I do not belong here Humor: Adventurous, casual, ironic risk humor. Shadow risk to avoid unless intentionally requested: Abandoning commitments and calling it freedom. Secondary 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. Shadow tension: Can gather too much context; should always return the reader to the practical conclusion. Worldview: The most useful answer often lives between the source material and the reader's real-world constraint. Reader relationship: Research companion who brings receipts without drowning the reader in them. Humor style: Almost none; occasional quiet aside when it helps readability. Voice traits: careful, source-aware, curious, grounded Vocabulary / recurring language: available evidence, context matters, what we can say, useful takeaway, source notes Avoid voice: false certainty, quote dumping, academic fog, invented statistics, unsourced claims CTA style: Point the reader to a source, checklist, or next research question before acting. 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: Thoughtful, source-aware, curious, and comfortable saying when the evidence is limited. Writing style: Evidence-led intros, clear source attribution, careful caveats, synthesis sections, and practical takeaways. Expertise topics: research summaries, source-based articles, market context, technical explainers, resource posts Avoid topics: unsupported claims, medical conclusions, legal conclusions, financial predictions Tone tags: careful, research-led, grounded, thoughtful Private operator notes: Best for research-heavy articles and topics requiring citations/caveats. 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`: `rowan-ellis`. - Suggested `display_name`: `Rowan Ellis`. - 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 the requested article as a new WordPress post and assigned it to a new author user, `Rowan Ellis`. The content is written against the real Ridgecrest Events Calendar UI that exists today: a weekly schedule overview with family/student/ministry sections and follow-through to News and Contacts, not a fictional RSVP interface. I also created and registered a fresh screenshot of the live Events Calendar page, used it inline and as the featured image, and included the required exact Flatlogic body link naturally in the closing paragraph. Verified `wp post get`, `wp post url`, public `200` responses for the post and `/blog/`, presence of the inline image in `post_content`, the featured image assignment, the exact required external URL in the article body, and that the blog index surfaces the new post. I did not change the pending backlink target `/`; it remains skipped because this job was limited to a blog post. Remaining uncertainty is minor: the screenshot attachment was registered without generated thumbnail sizes because the server lacks GD/Imagick, but the original image renders publicly and is used successfully in the post and blog index. WP_POST_ID: 87 WP_POST_STATUS: publish WP_POST_URL: https://ridgecrestchurch.com/how-to-use-events-calendar-rsvp-reminders-what-to-bring/ WP_AUTHOR_USER: rowan-ellis / Rowan Ellis FEATURED_IMAGE_ID: 86 INLINE_IMAGE_IDS: 86 BLOG_INDEX_STATUS: ready; https://ridgecrestchurch.com/blog/ returns 200, page_for_posts=23, and the new post appears on the blog index LINK_TARGETS_USED: https://flatlogic.com/generator?utm_source=ridgecrestchurch.com