fix: properly update enabled flag when disabling content

Problem:
When disabling content via PATCH /api/shops/:id/content/:contentId,
the enabled flag was not being set to false, causing the content to
still appear as enabled in subsequent API requests.

Solution:
Added call to setContentEnabled(contentId, false) before deleting
content data to ensure the enabled flag is properly updated in the
database.

Changes:
- Call db.setContentEnabled(contentId, false) when disabling content
- This ensures the enabled flag is persisted correctly
- Content data is still cleared and Qdrant embeddings are still deleted

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

src/api/components/ContentEndpoint.ts

@@ -242,7 +242,10 @@ export class ContentEndpoint extends BaseEndpointComponent {
           }
         }
 
-        // Then delete from database (clears content but keeps URL record)
+        // Set enabled flag to false
+        this.db.setContentEnabled(contentId, false);
+
+        // Then delete content data (clears content but keeps URL record)
         this.db.deleteContentData(contentId);
         actionTaken = 'content_and_embeddings_deleted';
         logger.info(`Disabled content ${contentId} and cleared data for shop ${shop.id}`);