You are the implementation agent in a non-interactive Codex loop.
Work only inside the provided context directory.
Make reasonable assumptions, implement directly, and do not ask follow-up questions.
When finished, summarize what changed and mention any remaining risks or uncertainty.

Context directory: /home/ubuntu/apps/administrativeessentials.com
Instruction file: /home/ubuntu/apps/administrativeessentials.com/wp-content/uploads/flatlogic-site-polish-tasks/job-45/task.md
Iteration: 0

<primary_instructions>
# Initial WordPress Site Polish / Visual QA Task

You are working directly inside the live WordPress root directory for domain "administrativeessentials.com".

Task type: final visual QA and polish after initial WordPress page/post generation.

## Required Runtime

- First read `SITE_CONTEXT.md` and `AGENTS.md` in this WordPress root.
- Then read `wp-content/plugins/flatlogic-site-polish/INSTRUCTIONS.MD`.
- Follow the site-polish instructions as the primary workflow.

## Site Details

- Domain: administrativeessentials.com
- Public URL: https://administrativeessentials.com/
- Site label: administrativeessentials.com
- Topic / niche: Administrative Essentials | Digital Marketing, Virtual Assistance, Website Design, Graphic Design website restoration

## Critical Visual QA Requirements

- Inspect the public homepage and key pages after page/post generation.
- Fix obvious visual defects before finishing: overlapping buttons, giant images, horizontal overflow, broken nav, raw/default-looking layout, weak header identity, missing footer utility links, or footer Flatlogic/AppWizzy links.
- Replace or fix complex text-heavy generated SVGs/infographics, awkwardly cropped images, nearly invisible images, or images that are clearly off-topic for their page.
- Replace or remove images, filenames, alt text, captions, mockups, screenshots, or decorative graphics that make the site look visually affiliated with Flatlogic/AppWizzy. Flatlogic/AppWizzy links may appear only as contextual body text links, not as visual branding or image subject matter.
- If published WordPress posts exist, verify `/blog/` returns a successful public response and `page_for_posts` points to a Blog page. Fix a missing/broken Blog index when practical.
- Check desktop width and mobile width when practical. Browser/screenshot tooling is optional, but when you attempt it, use Playwright Chromium exactly like `npx -y playwright@latest screenshot --browser=chromium https://administrativeessentials.com/ /tmp/site-polish-home.png`. Make at most one browser/screenshot attempt. If that command fails because Playwright/browser binaries, shared libraries, or browser dependencies are missing, do not install packages and do not keep retrying; immediately use HTML/CSS/WordPress checks and targeted fixes.
- Do not use hardcoded WordPress database table names such as `wp_options`, `wp_posts`, or `wp_postmeta`. Provisioned sites may use a custom table prefix. Prefer WP-CLI APIs; if direct SQL is unavoidable, first get the actual prefix with `wp db prefix`.
- 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()` or Custom CSS helper functions exist.
- Do not depend on Python PIL/Pillow being installed. If image processing libraries are unavailable, fix image sizing/layout through HTML, CSS, theme settings, or WordPress media metadata. Do not use `wp media list`; inspect media with `wp post list --post_type=attachment` or WordPress APIs.
- Do not rebuild all content unless the visual issue requires it.
- Keep Flatlogic/AppWizzy links contextual in page/post body content only, never in the footer.
- Keep restored backlink targets live; do not undo page/post creator restoration work.

## Final Report

When you finish, return the final report required by `flatlogic-site-polish/INSTRUCTIONS.MD`.
</primary_instructions>