Read-only discovery completed for recurring or reusable website content QA automation across /Users/samaguiar/Documents/New project, /Users/samaguiar/Documents/Projects, and ~/.codex/automations.
Best broad candidate: /Users/samaguiar/Documents/New project/scripts/audit_recent_wp_content.py. It audits pages and posts via WordPress REST, covers published items since a cutoff plus all non-published statuses, writes JSON/CSV/Markdown, and already checks forbidden visible phrases, bad filler patterns, question-heading issues, media URLs, headings, bold copy, repeated sentences, and orange-background patterns.
Pre-publish/file gate: /Users/samaguiar/Documents/New project/scripts/wp_content_quality_gate.py. It accepts HTML files or public URLs, already checks FAQ schema vs visible FAQ mismatch and other copy defects, and is named in the Amazon prevention plan as the gate that should run before publishing generated or repaired WordPress legal content.
Delivery-cluster specialized audit: /Users/samaguiar/Documents/New project/scripts/audit_delivery_cluster_content.py. It checks mapped delivery live URLs plus local proposed artifacts, already catches FAQ schema mismatch, Related Content weaknesses, non-link bold, trust-strip issues, and internal workflow labels. It is useful for delivery pages but less general than the recent WP content scanner.
Rendered layout helper: /Users/samaguiar/Documents/New project/outputs/delivery-cluster-skills-audit-2026-05-17/live_render_qa.js. It checks desktop/mobile rendered delivery pages for overflow, heading alignment, trust-strip structure, and Related Content link count. It is output-local and path-specific, but useful for Playwright-side assertions.
Recurring automation surface: ~/.codex/automations/hourly-trucking-pillar-live-page-monitor/automation.toml.disabled invoked python3 scripts/monitor_trucking_pillar_live.py --json-out outputs/live-page-monitor/trucking-pillar-latest.json from /Users/samaguiar/Documents/New project, hourly. It is disabled because Sam requested the hourly cron stop. Its memory says crontab and launchd had no matching active local job at disable time.
Active related automation: ~/.codex/automations/daily-schema-check/automation.toml, active daily at 9:00. It is schema-focused, not a content QA script. Use only if the goal is extending an existing active heartbeat prompt, not if the goal is code-level content QA.
audit_recent_wp_content.py, add helper functions near heading_findings and bold_findings, then append them in audit_item after existing content checks. This is the best place for broad live/draft page and post coverage.toc_findings(content): fail target templates when .sa-toc-wrap or visible On This Page is absent, flag redundant What this page covers, and optionally check TOC appears before .sa-snippet.snippet_findings(content, text): flag internal phrases, generic snippets, duplicate snippets, missing .sa-snippet on pages that use the SA page wrapper, and snippet text drift from client-facing language.sidebar_cta_findings(content): require .sa-sidebar, .sa-sidebar-cta, at least one tel: link, visible phone CTA text, and trust/CTA card structure without hidden or unreadable button text.section_12b_faq_findings(content): flag comparative-fault FAQ or city-narrow FAQ language on broad Kentucky practice-area pages unless a page-specific allowlist applies. Also keep exact visible/schema FAQ parity.wp_content_quality_gate.py for pre-publish file/URL checks, or import shared helpers if a small shared module is created later.audit_delivery_cluster_content.py and live_render_qa.js with the same TOC/snippet/sidebar assertions. Keep this secondary to the broad scanner.The requested search and read-only analysis are complete. No files were edited.