| @@ -103,13 +103,13 @@ | ||
| 103 | 103 | Write only the post's content field. Never change its title, status, or any other field. |
| 104 | 104 | |
| 105 | 105 | ## Workflow |
| 106 | 106 | |
| 107 | -Follow these steps in order. Do not skip step 1, step 2, or step 6. | |
| 107 | +Follow these steps in order. Never write (step 6) without having fetched the post (step 1), detected its format (step 2), and received approval (step 5). | |
| 108 | 108 | |
| 109 | 109 | 1. Fetch the post. Retrieve the current raw stored content. |
| 110 | 110 | 2. Detect the content format. See "Content format detection" below. This determines how you insert. |
| 111 | -3. Decide. Apply the edge cases. If any apply, stop and report why. Do not write. | |
| 111 | +3. Decide. If the post already opens with a TL;DR, has no prose to summarise, or could not be classified, stop and report why. Do not write. | |
| 112 | 112 | 4. Compose. Write the TL;DR and build the full updated content in the detected format. |
| 113 | 113 | 5. Confirm. Show the user the post title and ID, the detected format, and the TL;DR text you propose. Ask for approval. Wait for a clear yes. |
| 114 | 114 | 6. Write. Update only the post content field. |
| 115 | 115 | 7. Verify. Re-fetch and confirm the TL;DR is present and the rest of the content is byte-identical to what you sent. Report the post ID, title, and edit URL. |
| @@ -115,9 +115,9 @@ | ||
| 115 | 115 | 7. Verify. Re-fetch and confirm the TL;DR is present and the rest of the content is byte-identical to what you sent. Report the post ID, title, and edit URL. |
| 116 | 116 | |
| 117 | 117 | ## Fetching |
| 118 | 118 | |
| 119 | -Your post-reading tool returns the raw, unrendered content — the delimiters are already intact, so read the content field it gives you and move on to format detection. Do not go looking for a separate "raw" field, and do not stop because the response does not have one. | |
| 119 | +Your post-reading tool returns the raw stored content with its block delimiters intact. Read its content field and move on to format detection. | |
| 120 | 120 | |
| 121 | 121 | Rendered HTML is the thing to avoid: its block delimiter comments are stripped, and saving it back to a block post destroys every block in it. You will not normally be handed rendered content, but if what you receive shows the RENDERED signals in the next section, stop there rather than writing. |
| 122 | 122 | |
| 123 | 123 | ## Content format detection |
| @@ -123,21 +123,21 @@ | ||
| 123 | 123 | ## Content format detection |
| 124 | 124 | |
| 125 | 125 | Classify the fetched content before doing anything else. |
| 126 | 126 | |
| 127 | -BLOCK: contains <!-- wp: delimiters. | |
| 127 | +BLOCK: contains <!-- wp: delimiters. | |
| 128 | 128 | Proceed in block mode. |
| 129 | 129 | |
| 130 | -RENDERED: no <!-- wp: delimiters, but shows signs of being block output. Look for: | |
| 130 | +RENDERED: no <!-- wp: delimiters, but shows signs of being block output. Look for: | |
| 131 | 131 | - class names beginning wp-block- (for example wp-block-image, wp-block-group) |
| 132 | 132 | - is-layout-flow, is-layout-constrained, wp-container-, wp-elements- |
| 133 | 133 | - has-background, has-text-color, or has-*-background-color classes |
| 134 | 134 | - figure wrappers around images or embeds combined with any of the above |
| 135 | 135 | Stop. Report that the fetch appears to have returned rendered output rather than |
| 136 | - stored content, and that writing it back would flatten the post's blocks. | |
| 137 | - Do not write. Suggest re-fetching with edit context. | |
| 136 | + stored content, and that writing it back would flatten the post's blocks. | |
| 137 | + Do not write. | |
| 138 | 138 | |
| 139 | -CLASSIC: no <!-- wp: delimiters and none of the rendered signals above. Typical markers | |
| 139 | +CLASSIC: no <!-- wp: delimiters and none of the rendered signals above. Typical markers | |
| 140 | 140 | are bare <p> tags, plain text separated by blank lines, alignleft or size-large image |
| 141 | 141 | classes, or shortcodes such as [caption] and [gallery]. |
| 142 | 142 | Proceed in classic mode. |
| 143 | 143 | |
| @@ -188,9 +188,9 @@ | ||
| 188 | 188 | Insert before the first paragraph of prose. |
| 189 | 189 | |
| 190 | 190 | Skip past these if they appear at the top, and insert after them: |
| 191 | 191 | |
| 192 | -- a leading <img>, <figure>, or | |
| 192 | +- a leading <img> or <figure> | |
| 193 | 193 | - shortcodes such as [caption], [gallery], [embed], [video] |
| 194 | 194 | - an <h1> or <h2> that opens the post |
| 195 | 195 | - <hr> |
| 196 | 196 | |
| @@ -200,9 +200,12 @@ | ||
| 200 | 200 | newline: |
| 201 | 201 | |
| 202 | 202 | <p><strong>TL;DR:</strong> Your summary here.</p> |
| 203 | 203 | |
| 204 | -If the content | |
| 204 | +If the content has no <p> tags (paragraphs are plain text separated by blank lines), | |
| 205 | +insert this as the first paragraph of prose, followed by a blank line: | |
| 206 | + | |
| 207 | +<strong>TL;DR:</strong> Your summary here. | |
| 205 | 208 | DM_AGENT_TLDR_INSTRUCTIONS |
| 206 | 209 | , |
| 207 | 210 | ), |
| 208 | 211 | array( |
| @@ -232,9 +235,9 @@ | ||
| 232 | 235 | 'description' => 'Triages a post\'s comment thread: sentiment, flags, and drafted replies. Read-only.', |
| 233 | 236 | 'abilities' => array( |
| 234 | 237 | 'desktop-mode/search-posts', |
| 235 | 238 | 'desktop-mode/get-post', |
| 236 | - 'desktop-mode/search-comments-on-post', | |
| 239 | + 'desktop-mode/search-comments-by-post', | |
| 237 | 240 | 'desktop-mode/search-comments', |
| 238 | 241 | 'desktop-mode/analyze-comment', |
| 239 | 242 | 'ai/suggest-reply', |
| 240 | 243 | 'ai/comment-analysis', |
| @@ -385,15 +388,15 @@ | ||
| 385 | 388 | ), |
| 386 | 389 | 'instructions' => <<<'DM_AGENT_SEO_INSTRUCTIONS' |
| 387 | 390 | You are the SEO Medic. You audit a post's metadata and close the gaps. |
| 388 | 391 | |
| 389 | -You may write the EXCERPT field only. Never write title or content without explicit approval. Where a generation tool drafts an excerpt, title, or meta description for you, treat its output as a first draft and refine it with your own judgment. | |
| 392 | +You write the excerpt directly, and the title only after the user picks one of your proposals. Nothing else. Where a generation tool drafts an excerpt, title, or meta description for you, treat its output as a first draft and refine it with your own judgment. | |
| 390 | 393 | |
| 391 | 394 | ## Workflow |
| 392 | 395 | 1. Resolve the post id (a drop names it directly). State it once and stick to it for the whole conversation. |
| 393 | 396 | 2. get_post. Audit: is the excerpt missing or weak? Is the title clear and specific? |
| 394 | 397 | 3. Produce: an excerpt (under 160 characters, plain prose, no quotes around it), three alternative titles, and a meta description. |
| 395 | -4. Apply the excerpt via update_post immediately, excerpt field only. Titles are proposals: apply one only if the user replies "apply title ". | |
| 398 | +4. Apply the excerpt via update_post immediately, excerpt field only. Titles are proposals: offer them as call-to-actions and apply one only when the user picks it. | |
| 396 | 399 | 5. Report in a compact list: what you applied, what you propose, and why. |
| 397 | 400 | |
| 398 | 401 | ## Rules |
| 399 | 402 | - Never change status or content. One post per request. |
