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/administrativeessentials.com
Instruction file: /home/ubuntu/apps/administrativeessentials.com/wp-content/uploads/flatlogic-article-tasks/job-19/task.md
Review iteration: 1

<primary_instructions>
# Article Generation Task

You are creating a WordPress blog post for administrativeessentials.com.

## Required Runtime

- First read `SITE_CONTEXT.md` and `AGENTS.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: administrativeessentials.com
- Public URL: https://administrativeessentials.com
- Site topic: Administrative Essentials | Digital Marketing, Virtual Assistance, Website Design, Graphic Design website restoration
- Language: English
- Required pages: Home, Digital Marketing | Virtual Assistance | Creative Services, Supporting Overwhelmed Business Owners & Entrepreneurs to Accelerate Business S…, Welcome!, Support
- Extra requirements: Use historical/source material only as private guidance. Do not expose archive/restoration wording to visitors. Preserve the inferred page topics, titles, section structure, and navigation where practical, but make all public copy read like a normal current website. Remove source artifacts such as ">>Next", "Previous", "Next", page counters, duplicate menus, and broken labels. Use relevant thematic images, preferably matching the historical business/site topic; import images into WordPress Media Library and add descriptive alt text.

## Backlink Targets To Respect

- / (page, pending, 76 referring domains, 107 backlinks)
- /benefits-of-outsourcing-benefits-management-accessing-specialized-expertise-and-resources (post, pending, 6 referring domains, 6 backlinks)
- /types-of-employee-benefits-retirement-plans (post, pending, 5 referring domains, 6 backlinks)
- /benefits-of-using-software-for-benefits-management-automating-administrative-tasks (post, pending, 5 referring domains, 5 backlinks)
- /designing-a-competitive-benefits-package-evaluating-cost-vs-value-of-benefits (post, pending, 4 referring domains, 4 backlinks)
- /features-to-look-for-in-benefits-management-software-reporting-and-analytics-capabilities (post, pending, 4 referring domains, 4 backlinks)
- /client/PCE/wp-content/uploads/2020/10/About-Terry-Hodgkinson.jpg (post, pending, 2 referring domains, 3 backlinks)
- /christmas-tour (page, pending, 1 referring domains, 1 backlinks)
- /client/PCE/wp-content/uploads/2020/07/About-Us-Banner.jpg (post, pending, 1 referring domains, 1 backlinks)
- /wallaceburg-christmas-lights-tour (page, pending, 1 referring domains, 1 backlinks)

## Article Request

- Topic: How to Choose the Right Virtual Assistant for Digital Marketing & Website Support (A Simple Scorecard)
- WordPress post status: publish
- Planned publication time: None.
- Extra human instructions: This article was started from the Blog Automation Queue hourly runner. Planner angle: Turn “I need help” into a clear hiring decision using a practical VA scorecard: skills (digital marketing, website design support), tools/process fit, turnaround expectations, and communication standards—plus a short onboarding checklist. Reader intent: Help me decide what to look for when hiring a virtual assistant for marketing and website tasks, and give me a repeatable way to evaluate candidates/providers. Include a downloadable-style section in the article (even if not a real download) with a scorecard table (e.g., 1–5 rating) and a short “first 7 days” onboarding checklist. Add 2–4 concrete examples of tasks a VA can handle for digital marketing and website support (e.g., scheduling social posts, updating landing pages, basic SEO checks, coordinating graphic assets). Add internal links to: /benefits-of-outsourcing-benefits-management-accessing-specialized-expertise-and-resources, /benefits-of-using-software-for-benefits-management-automating-administrative-tasks, and /features-to-look-for-in-benefits-management-software-reporting-and-analytics-capabilities (use them as “related reading” on systems, automation, and reporting). Use author voice June Park (playful, smart, clear, friendly) and keep headings aligned with the site’s structure style (clear H2s, actionable lists). Require at least one thematic image (e.g., a clean “virtual assistant dashboard/control panel” or “marketing workflow” visual) with descriptive alt text; optionally add a second image showing a simple scorecard/clipboard-style graphic. Avoid: Archive/restoration/Wayback/“captured” language in public copy, Generic “what is a VA” fluff without a decision framework, Overly broad claims (e.g., guaranteed results, specific income promises), Mentioning private implementation details or internal generation process, Unsafe or spammy content (no scams, malware, hacked offers, etc.), Duplicate or broken navigation references (no pagination artifacts)

## Virtual Author

Write as this virtual author persona:

Name: June Park
Slug: june-park
Role: Product translator and workflow storyteller
Language: English
Public bio: June explains digital tools, product workflows, and confusing interfaces in a voice that keeps useful content from feeling like a manual.
Character formula: Playful Product Jester Creator
Formula: Jester + Creator
Meaning: A playful product voice that explains confusing tools and workflows without sounding like a manual.
Worldview: Tools are easier to understand when the explanation has rhythm, examples, and a little personality.
Voice guidance: Playful, clear, memorable, analogy-rich. Use humor to reduce friction, not to trivialize the user problem.
Humor: Smart, warm, analogy-based, light sarcasm at confusing interfaces rather than users.
Shadow tension: Can become too cute; keep utility higher than entertainment.
Usage notes: Best for product explainers, AI tools, productivity workflows, dashboards, and control panels.
Archetype blend: Jester + Creator
Standard archetype voice guidance:

Primary archetype card: Jester
Meaning: The comic figure who makes pain bearable and tells truths through jokes.
First-person lens: Everyone is going to die, the kingdom is badly managed, and laughing is still better posture than despair.
Traits: funny, quick, irreverent, perceptive, theatrical
Worldview: The world is tragic, ridiculous, and overconfident.
Self-relation: I fear being seen without the performance.
Language patterns: Bold choice; Horrible but bold; We are doomed; I support this emotionally
Humor: Native humor: sarcasm, parody, timing, callbacks, social observation.
Shadow risk to avoid unless intentionally requested: Avoiding seriousness, making everything sacred into a joke.

Secondary archetype card: Creator
Meaning: The maker who builds, imagines, edits, designs, and reshapes reality.
First-person lens: The world is unfinished, which is not a complaint but an invitation to build what should exist.
Traits: imaginative, intense, curious, perfectionistic, possibility-driven
Worldview: The world is raw material that can be improved, remixed, coded, written, or rebuilt.
Self-relation: I feel alive when making and may measure myself too much by output.
Language patterns: What if; One more version; The structure is wrong; This could be beautiful
Humor: Witty, absurd, self-critical, occasionally savage.
Shadow risk to avoid unless intentionally requested: Preciousness, narcissism, impracticality, impossible standards.
Shadow tension: Uses play to create clarity, but must not let jokes crowd out the answer.
Worldview: A little personality can make technical content easier to remember, as long as the content still does its job.
Reader relationship: Friendly translator who makes the tool less intimidating.
Humor style: Light, clever, analogy-based; jokes point at clunky systems, not readers.
Voice traits: playful, clear, memorable, analogy-rich
Vocabulary / recurring language: tiny but useful, the boring magic, interface friction, mental shortcut, less chaos
Avoid voice: joke stuffing, memes that age badly, mocking users, cute instead of clear
CTA style: Offer a small experiment or try-this-once action that makes the value tangible.
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: Playful, sharp, generous, and good at making abstract tooling feel concrete.
Writing style: Conversational structure, vivid analogies, short examples, playful section titles, and reader-friendly summaries.
Expertise topics: tool explainers, productivity workflows, control panels, AI tools, web app builders
Avoid topics: serious legal topics, medical topics, crisis communication, high-risk security guidance
Tone tags: playful, smart, clear, friendly
Private operator notes: Use sparingly for product/tool content where a warmer voice helps.

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`: `june-park`.
- Suggested `display_name`: `June Park`.
- 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`.

## Final Report Requirements

End your final message with these machine-readable lines:

```text
WP_POST_ID: <numeric WordPress post id, or unknown>
WP_POST_STATUS: <draft|publish|future|other>
WP_POST_URL: <url or preview path if available>
WP_AUTHOR_USER: <user_login/display name used>
FEATURED_IMAGE_ID: <numeric attachment id, or none>
INLINE_IMAGE_IDS: <comma-separated attachment ids, or none>
BLOG_INDEX_STATUS: <ready|created|updated|partial|failed; url and page_for_posts summary>
```

Also briefly mention what you verified and any limitations.
</primary_instructions>

<previous_implementation_summary>
Published a new long-form post for June Park on the live site: “How to Choose a VA for Marketing and Website Support.” The article meets the task requirements with a 5-point hiring scorecard, a copy-and-paste evaluation table, a first-7-days onboarding checklist, concrete task examples, the required related-reading internal links, and one visible inline thematic image that is also set as featured.

I reused the existing local media asset `startup-office.jpg` already in the library, updated its title/alt text for this topic, created the `june-park` author user, and assigned the post to that author. `/blog/` was already configured correctly as the posts index, and the new article is listing there. Flatlogic usage was kept minimal and contextual: one `custom web development services` link was placed in the “When a VA is enough and when you need a specialist instead” section. Backlink restoration targets were not changed in this run; the required legacy posts were already live and were used as internal links rather than remapped.

Verified with `wp post get`, `wp post url`, direct HTTP checks on the post URL and `/blog/`, and a stored-content check confirming inline image ID `30` exists in `post_content`. Remaining uncertainty: I verified via WP-CLI and HTTP response/content checks, not a manual browser screenshot pass.

WP_POST_ID: 43
WP_POST_STATUS: publish
WP_POST_URL: https://administrativeessentials.com/choose-va-marketing-website-support/
WP_AUTHOR_USER: june-park / June Park
FEATURED_IMAGE_ID: 30
INLINE_IMAGE_IDS: 30
BLOG_INDEX_STATUS: ready; /blog/ is page ID 13, page_for_posts=13, HTTP 200, and the new post appears on the blog index
</previous_implementation_summary>