[/H]

— EDITORIAL / AI WORKFLOW LEAKAGE CLEANUP

FINAL CONTROLLED VERSION

Published + Future Posts

Minimal Sentence-Only Repair

Site:
This is a tightly scoped cleanup operation.
The purpose is ONLY to remove or minimally repair reader-visible editorial, Codex, AI-production, batch-production, and internal-linking workflow language that was accidentally left inside article content.
This is NOT:

• a content rewrite
• an SEO rewrite
• an optimization task
• an internal-link-building task
• a technical-content revision
• a title rewrite
• a metadata rewrite
• a restructuring task

The smallest possible modification must always be used.

1. AUTHORIZED SCOPE

Inspect WordPress records where:
post_type = post
and status is:

• publish
• future

Do NOT modify:

• drafts
• pages
• attachments
• categories
• tags
• media
• plugins
• themes
• WordPress core
• redirects
• site settings

Runtime WordPress state is authoritative.
Before writing anything, record the current site inventory.

2. PROBLEM 1 — EDITORIAL / INTERNAL-LINK WORKFLOW LANGUAGE

Search the complete body of every published and future post for reader-visible language that exposes the internal content-production or linking workflow.
Known examples include:
"Use these internal references to extend the checks in"
"without changing the measurement boundary or substituting a nearby topic for the original question"
"Since [X] is the immediately previous post in your internal linking sequence"
"Since [X] is the immediately previous article in this internal sequence"
"is the immediately previous post in this internal sequence"
"is the immediately previous article in this internal sequence"
"this post should also link"
"should also link back there"
"should also link there directly"
"internal linking sequence"
"internal sequence"
"previous post in your internal linking sequence"
"previous article in this internal sequence"
Statements explaining that another article is linked because it came before or after it in a publishing/content sequence are editorial instructions and must not remain visible to readers.

3. PROBLEM 2 — "BATCH ARTICLE" WORKFLOW LANGUAGE

Search all published and future posts for reader-visible expressions including:
"batch article"
"batch articles"
"the batch article"
"the batch articles"
"this batch"
"the batch"
when the expression refers to the internal content-production process.
Examples:
"The batch article on Manual J heating design temperature explains..."
"The batch article comparing Category I and Category IV furnace venting explains..."
"The batch articles on auxiliary-heat lockout and heat-strip staging explain..."
These expressions expose the production workflow and should not appear in final reader-facing content.

4. MOST IMPORTANT RULE — ONLY THE PROBLEM SENTENCE MAY CHANGE

For every confirmed occurrence:
ONLY modify the exact sentence containing the editorial / AI workflow leakage.
Everything else is frozen.
Do NOT:

• rewrite the surrounding paragraph
• change the previous sentence
• change the next sentence
• add a new paragraph
• add a new sentence
• expand the article
• shorten unrelated content
• reorganize the article
• change headings
• change tables
• change lists
• change technical explanations
• optimize keyword usage
• rewrite for style
• improve unrelated grammar
• touch sentences that do not contain workflow leakage

Even if surrounding prose could be improved, leave it untouched.

5. DECISION RULE FOR EACH PROBLEM SENTENCE

For every confirmed problem sentence, use this order:

CASE A — Sentence is completely unnecessary

If the sentence exists only to describe:

• internal linking order
• publishing order
• article sequence
• batch production
• Codex instructions
• editorial instructions

delete ONLY that sentence.
Do not replace it.
Example:
BAD:
"Since that post is the immediately previous article in this internal sequence, this post should also link there directly."
If the previous sentence already contains the useful link:
DELETE the bad sentence completely.
Do not add replacement prose.

CASE B — Sentence contains a useful existing internal link

If the problematic sentence contains an internal link that would otherwise be lost:
Minimally rewrite ONLY that sentence.
Preserve:

• the same URL
• the same factual intent
• the same topic relationship

Do not add another link.
Example:
BAD:
"Since Ohio is the immediately previous post in your internal linking sequence, Pennsylvania should also link to what size AC do I need in Ohio."
Allowed minimal repair:
"For a nearby comparison, see what size AC do I need in Ohio."
Only that sentence changes.
Nothing before or after it changes.

CASE C — "Batch article" sentence contains useful technical meaning

If:
"The batch article on Manual J heating design temperature explains why..."
contains useful reader-facing technical meaning, remove ONLY the workflow expression.
Allowed:
"Our guide to Manual J heating design temperature explains why..."
or an equally minimal grammatical repair.
Do not rewrite the technical remainder of the sentence.
Example:
BAD:
"The batch article comparing Category I and Category IV furnace venting explains the category boundary."
Allowed:
"The guide comparing Category I and Category IV furnace venting explains the category boundary."
Only the minimum words necessary may change.

6. NO FREE REWRITING

Codex is NOT authorized to make a sentence "better" beyond removing workflow leakage.
Do not:

• improve tone
• improve readability generally
• add context
• add examples
• add explanations
• add claims
• add keywords
• change sentence structure unnecessarily

The repaired sentence should remain as close as possible to the original.
Use the minimum edit distance necessary.

7. INTERNAL LINKS ARE PROTECTED

Before modifying a candidate sentence, record all internal links contained in it.
Rules:

• Do not change the target URL.
• Do not create a new target URL.
• Do not replace an existing valid internal link with another article.
• Do not add new internal links.
• Do not perform link optimization.
• Do not change anchor text unless the anchor text itself contains workflow/editorial language.

If a workflow-only sentence contains a link that is already linked naturally in the immediately surrounding section, the redundant workflow sentence may be deleted.
If deleting the sentence would remove the article's only link to that target:
do not blindly delete it.
Minimally repair that exact sentence instead.

8. "RELATED TECHNICAL GUIDES" SECTIONS

Some posts include introductions similar to:
"Use these internal references to extend the checks in [ARTICLE] without changing the measurement boundary or substituting a nearby topic for the original question."
This is editorial workflow language.
If the entire sentence is only an editorial instruction:
DELETE THAT SENTENCE ONLY.
Do NOT automatically replace it with:
"Related guides..."
or any other new sentence.
Keep:

• the heading
• the existing link list
• every valid list item
• surrounding text

unchanged.
If removal creates an empty paragraph block, remove that now-empty paragraph block only.
Do not change the heading.

9. SEMANTIC DETECTION

Do not rely exclusively on exact-string matches.
Also detect semantically equivalent content-production language such as:

• "this article should link to..."
• "we need to link..."
• "previous post in the sequence"
• "next post in the sequence"
• "because this article was published before..."
• "this batch..."
• "another article in this batch..."
• editorial instructions addressed to the writer rather than the reader

However, be conservative.
Do NOT remove legitimate HVAC uses of:

• sequence
• previous
• next
• stage
• order

Example that must NOT be changed:
"The furnace ignition sequence begins with the inducer."
That is legitimate HVAC technical language.
Example that must be changed:
"This is the previous article in our internal linking sequence."
That is production workflow language.

10. FALSE POSITIVE PROTECTION

Every candidate occurrence must be classified before modification as one of:

• INTERNAL_LINK_WORKFLOW
• INTERNAL_SEQUENCE_WORKFLOW
• BATCH_ARTICLE_WORKFLOW
• FALSE_POSITIVE

FALSE_POSITIVE items must remain untouched.
When uncertain whether language is genuinely reader-facing or production leakage:
DO NOT MODIFY IT.
Report it for review.

11. PRE-WRITE AUDIT

Before changing any post, build a candidate ledger containing:

• Post ID
• Title
• Slug
• Status
• Publication date
• Exact problem sentence
• Surrounding paragraph for context
• Classification
• Internal links contained in the sentence
• Proposed action:
  • DELETE_SENTENCE
  • MINIMAL_SENTENCE_REPAIR
  • FALSE_POSITIVE
  • MANUAL_REVIEW
• Exact proposed new sentence if repair is required

Do not write until all candidates have been classified.

12. PUBLISHED POST PROTECTION

Published posts must remain published.
For every modified published post, freeze:

• ID
• title
• slug
• status
• original publication date
• author
• category
• tags
• featured image
• excerpt
• comment status
• ping status
• Rank Math focus keyword
• Rank Math SEO title
• Rank Math meta description
• all other SEO metadata

Only the confirmed problem sentence may change in post_content.

13. FUTURE POST PROTECTION

Future posts must remain future.
Before touching any future post, record:

• ID
• title
• slug
• status
• local scheduled timestamp
• GMT scheduled timestamp
• author
• category
• Rank Math fields
• featured image
• body SHA-256

After modification verify that ALL of these remain identical except body SHA-256.
Absolutely no future publication timestamp may change.
Do not:

• publish immediately
• reschedule
• move between slots
• change timezone interpretation
• change future → draft
• change future → publish

14. DO NOT TOUCH THE GENERAL SOURCES BOILERPLATE

The recurring statement similar to:
"Final sizing, airflow, electrical, combustion, and refrigerant decisions must also follow the exact equipment instructions and applicable local code."
is NOT part of this task.
Do not modify it.
Do not modify "Sources and verification" sections except when a sentence inside them specifically contains confirmed workflow leakage such as "batch article."
This broader boilerplate issue will be handled separately.

15. NO OTHER CONTENT CLEANUP

Do not address during this operation:

• state-page similarity
• duplicate topics
• cannibalization
• thin content
• excessive technical detail
• outdated articles
• calculators
• metadata quality
• keyword targeting
• new internal links
• orphan pages
• source quality
• headings
• title improvements
• URLs
• redirects

Even if problems are noticed, only REPORT them.
Do not fix them.

16. WRITE IN CONTROLLED GATES

Make changes in gates of no more than 10 posts.
After every gate verify:

• status unchanged
• title unchanged
• slug unchanged
• publication timestamp unchanged
• future timestamp unchanged
• category unchanged
• featured image unchanged
• Rank Math unchanged
• valid internal links preserved
• no malformed HTML
• no malformed Gutenberg markup
• no empty unintended paragraph fragments
• no empty lists
• no broken anchors
• no PHP errors

Stop immediately if a regression is detected.

17. POST-EDIT BODY DIFFERENCE CHECK

For every modified post, compare body before and after.
The diff must show ONLY:

• deletion of a confirmed problem sentence

OR

• minimal modification of the exact confirmed problem sentence

No unrelated line or sentence may differ.
If unrelated content differs:
STOP.
Restore that post to the pre-edit body.
Report the failure.

18. FINAL GLOBAL SEARCH

After all authorized modifications, search every published and future post again for:
"internal linking sequence"
"internal sequence"
"immediately previous post"
"immediately previous article"
"this post should also link"
"should also link back"
"should also link there"
"Use these internal references to extend the checks"
"without changing the measurement boundary"
"substituting a nearby topic"
"batch article"
"batch articles"
"this batch"
Expected reader-visible workflow leakage:
0
Any remaining matches must be explicitly documented as:

• legitimate technical context
• false positive
• manual review item

Do not hide remaining matches.

19. REGRESSION REQUIREMENTS

Required final state:
Published status changes = 0
Future status changes = 0
Future timestamp changes = 0
Published date changes = 0
Title changes = 0
Slug changes = 0
Category changes = 0
Tag changes = 0
Rank Math focus keyword changes = 0
Rank Math title changes = 0
Rank Math meta description changes = 0
Featured-image changes = 0
New internal links = 0
Internal-link target changes = 0
New external links = 0
Media uploads = 0
Media deletions = 0
Images generated = 0
Redirect changes = 0
Page changes = 0
Draft changes = 0
Plugin changes = 0
Theme changes = 0
WordPress core changes = 0
Unexpected publication events caused by this task = 0

20. FRONTEND VALIDATION

After editing, smoke-test:

• at least 10 modified published posts
• every modified future post through authenticated preview
• at least 3 unrelated published control posts

Verify:

• normal rendering
• no visible workflow language
• internal links work
• no broken layout
• no PHP errors
• no unexpected frontend console errors caused by the edit

Do not change anything merely because a smoke test reveals an unrelated issue.
Report unrelated issues separately.

21. FINAL REPORT

Return the following.

A. BEFORE INVENTORY

Published posts:
Future posts:
Draft posts:
Pages:
Categories:
Tags:
Media:

B. PROBLEM 1 AUDIT

Unique posts containing editorial/internal-link workflow leakage:
Published:
Future:
Total confirmed occurrences:
False positives:
Manual-review items:

C. PROBLEM 2 AUDIT

Unique posts containing "batch article" / batch workflow leakage:
Published:
Future:
Total confirmed occurrences:
False positives:
Manual-review items:

D. MODIFICATION COUNTS

Sentences deleted:
Sentences minimally repaired:
Paragraphs rewritten:
Must equal 0.
New sentences added:
Must equal 0.
New internal links:
Must equal 0.

E. MODIFIED POST LEDGER

For every modified post show:
Post ID
Title
Status
Slug
Leak classification
Exact old sentence
Action:

• DELETE_SENTENCE
  or
• MINIMAL_SENTENCE_REPAIR

Exact new sentence if applicable
Internal URLs before
Internal URLs after
Body SHA-256 before
Body SHA-256 after

F. FUTURE QUEUE INTEGRITY

Future count before:
Future count after:
Schedule hash before:
Schedule hash after:
Timestamp changes:
Status changes:
Unexpected publications caused by this task:
All unauthorized values must equal zero.

G. SEO / METADATA INTEGRITY

Titles changed:
Slugs changed:
Rank Math focus keywords changed:
Rank Math SEO titles changed:
Rank Math descriptions changed:
Categories changed:
Tags changed:
Featured images changed:
All must equal 0.

H. FINAL PROHIBITED-PHRASE AUDIT

Report the final count individually for:
internal linking sequence:
internal sequence:
immediately previous post:
immediately previous article:
this post should also link:
should also link back:
should also link there:
Use these internal references to extend the checks:
without changing the measurement boundary:
substituting a nearby topic:
batch article:
batch articles:
this batch:
Explain every non-zero result.

I. REGRESSION SUMMARY

Unrelated body changes:
New sentences:
New links:
Deleted valid unique links:
Schedule changes:
SEO metadata changes:
Media changes:
Plugin/theme changes:
Technical regressions:
All must equal 0.

FINAL OPERATING RULE

Only the exact sentence containing confirmed editorial / AI workflow leakage may be changed.
If the sentence is unnecessary:
DELETE THAT SENTENCE ONLY.
If the sentence contains useful information or a necessary existing internal link:
MINIMALLY REPAIR THAT SENTENCE ONLY.
Do not touch surrounding content.
Do not add new information.
Do not add new sentences.
Do not add new links.
Do not perform SEO rewriting.
Do not perform general content improvement.
Do not generate or upload images.
When uncertain:
DO NOT MODIFY.
REPORT FOR MANUAL REVIEW.
Final line: