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: 1

<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>

A previous review found issues. Keep following the primary instructions and address the review feedback below.

<review_summary>
Material follow-up is still required before this can be marked complete. Based on the provided implementation summary, the highest-risk gap is incomplete final visual QA on key public pages, especially mobile/key-page inspection after the homepage/header CSS fixes.
</review_summary>

<review_findings>
- The implementation summary only demonstrates a visual/browser inspection of the homepage, not the required 'homepage and key pages' visual QA. The remaining page checks described are mostly HTTP 200/status checks, which do not verify layout, image quality, navigation, or footer presentation on those pages.
- Mobile validation is explicitly marked partial. The primary instructions require checking desktop and mobile widths when practical; the summary does not show a completed mobile review of the key pages after the polish changes.
- The post-fix verification evidence is thin for image-related requirements on interior pages. The summary confirms the duplicate homepage image was hidden, but it does not show that key pages/posts were checked for awkward crops, off-topic images, weak SVG/infographic output, or Flatlogic/AppWizzy-looking visual assets.
- Independent filesystem/runtime inspection was not possible in this review run because shell commands failed with `bwrap: loopback: Failed RTM_NEWADDR: Operation not permitted`, so the current site state could not be directly verified from the context directory.
</review_findings>

<fix_instructions>
Perform one more implementation pass focused only on final QA evidence and any issues found. Re-read `SITE_CONTEXT.md`, `AGENTS.md`, and `wp-content/plugins/flatlogic-site-polish/INSTRUCTIONS.MD`, then inspect the live homepage plus a small set of key public pages/posts with the highest restoration/traffic value, including `/blog/` and at least the main restored backlink targets. Check both desktop and mobile behavior using the single allowed Playwright Chromium screenshot attempt only if you have not already consumed it in the implementation run; otherwise use public HTML/CSS/theme/WordPress inspection to verify layout. Specifically confirm no broken nav, no horizontal overflow, no giant/awkward/off-topic images, no Flatlogic/AppWizzy visual branding, and healthy footer/legal links on those interior pages. If any issues are found, fix them with targeted WordPress/theme/CSS changes only. In the final report, add concrete page-level QA evidence for the key pages reviewed, not just status-code checks.
</fix_instructions>