fix(docs-gen): stop cleanup/writer filter mismatch from eating manual content

Comprehensive-review findings, all generator-consistency bugs:
- cleanup used staging's isIntegrationBlock while the writer kept the legacy
  filter, so integrations/{knowledge,memory,table}.mdx were deleted then
  regenerated without their manual intros every run. Both now honor a shared
  NATIVE_RESOURCE_BLOCK_TYPES set; intros reseeded.
- Trigger-only services (imap, circleback; category 'triggers') were likewise
  deleted each run; the canonical set now includes visible trigger-category
  blocks, the standalone writer preserves manual content, and their intros are
  reseeded.
- Mapped jsm -> jira_service_management, so JSM triggers merge into the JSM
  integration page instead of an orphan jsm.mdx (removed).
- Repointed lingering bare /tools links to /integrations; added missing
  pageType to integrations/index and building-agents/custom-tools.
Double-regen is now churn-free (idempotent) with all manual content intact.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: ouiliame

apps/docs/content/docs/en/blocks/agent.mdx

@@ -37,7 +37,7 @@ Files for the model to read: images for a vision-capable model, or documents for
 
 ### Tools
 
-Capabilities the agent can call while it runs: search a knowledge base, send a Slack message, run a [Function](/blocks/function), or call any of the [integrations](/tools). The model decides which to call and when. Each tool has a usage control:
+Capabilities the agent can call while it runs: search a knowledge base, send a Slack message, run a [Function](/blocks/function), or call any of the [integrations](/integrations). The model decides which to call and when. Each tool has a usage control:
 
 - **Auto.** The model calls it when the context warrants.
 - **Force.** The model must call it on every run.

apps/docs/content/docs/en/building-agents/choosing.mdx

@@ -17,13 +17,13 @@ The running example is a workflow that scores inbound sales leads. It reads a ne
 
 A **block** is a single step that runs at a fixed point on the path, with no model deciding whether to. It always runs when the workflow reaches it. Use one when the action must happen every time: an API call, a data transform, a branch.
 
-In the lead scorer, a [Google Sheets](/tools) block always appends the scored lead to a tracking sheet, and a [Function](/blocks/function) block always reshapes the enrichment response into the fields the next step expects. There is no judgment call. The work is guaranteed.
+In the lead scorer, a [Google Sheets](/integrations) block always appends the scored lead to a tracking sheet, and a [Function](/blocks/function) block always reshapes the enrichment response into the fields the next step expects. There is no judgment call. The work is guaranteed.
 
 Most steps in a workflow are blocks. Reach for the kinds below only when you want a model to decide, or you want to reuse something.
 
 ## Agent tool
 
-An **agent tool** is an action you hand to an [Agent](/blocks/agent) block. The agent reads the task and decides whether and when to call it. The same catalog of [integrations](/tools) that exist as standalone blocks can also be attached to an agent as tools.
+An **agent tool** is an action you hand to an [Agent](/blocks/agent) block. The agent reads the task and decides whether and when to call it. The same catalog of [integrations](/integrations) that exist as standalone blocks can also be attached to an agent as tools.
 
 In the lead scorer, the Agent has a Search tool and a Send Email tool. For a lead with a thin profile it runs Search to gather context; for a strong lead it calls Send Email. A thin, obvious lead might trigger neither. The agent chooses per run.
 

apps/docs/content/docs/en/building-agents/custom-tools.mdx

@@ -1,6 +1,7 @@
 ---
 title: Custom Tools
 description: Create your own tools with JavaScript code and use them in Agent blocks
+pageType: guide
 ---
 
 import { Callout } from 'fumadocs-ui/components/callout'

apps/docs/content/docs/en/building-agents/index.mdx

@@ -31,7 +31,7 @@ To let an agent do something in the world, give it **tools**. A tool is an actio
 
 Tools come from a few places:
 
-- **[Integrations](/tools)** are the catalog of external services: Gmail, Slack, Airtable, Linear, and hundreds more.
+- **[Integrations](/integrations)** are the catalog of external services: Gmail, Slack, Airtable, Linear, and hundreds more.
 - **[Custom tools](/building-agents/custom-tools)** are tools you define once with a schema and a snippet of code, then reuse.
 - **[MCP tools](/mcp)** come from an external provider you connect through the Model Context Protocol.
 - **[Workflow-as-tool](/workflows)** makes another workflow callable, so the agent runs a whole procedure as one step.

apps/docs/content/docs/en/getting-started/index.mdx

@@ -173,7 +173,7 @@ Build, test, and refine workflows quickly with immediate feedback
   <Card title="Explore Blocks" href="/workflows#blocks">
     Discover API, Function, Condition, and other blocks
   </Card>
-  <Card title="Browse Integrations" href="/tools">
+  <Card title="Browse Integrations" href="/integrations">
     Connect 1,000+ services including Gmail, Slack, Notion, and more
   </Card>
   <Card title="Add Custom Logic" href="/blocks/function">
@@ -188,7 +188,7 @@ Build, test, and refine workflows quickly with immediate feedback
 
 **Need detailed explanations?** Visit the [Blocks documentation](/workflows#blocks) for comprehensive guides on each component.
 
-**Looking for integrations?** Explore the [Tools documentation](/tools) to see all 1,000+ available integrations.
+**Looking for integrations?** Explore the [Tools documentation](/integrations) to see all 1,000+ available integrations.
 
 **Ready to go live?** Learn about [Execution and Deployment](/workflows) to make your workflows production-ready.
 

apps/docs/content/docs/en/index.mdx

@@ -20,7 +20,7 @@ Welcome to Sim, the open-source AI workspace where teams build, deploy, and mana
   <Card title="Blocks" href="/workflows#blocks">
     Learn about the building blocks
   </Card>
-  <Card title="Tools & Integrations" href="/tools">
+  <Card title="Tools & Integrations" href="/integrations">
     Explore 1,000+ integrations
   </Card>
 </Cards>

apps/docs/content/docs/en/integrations/circleback.mdx

@@ -1,21 +1,53 @@
 ---
 title: Circleback
-description: AI-powered meeting notes and action items
+description: Circleback triggers for automating workflows
 ---
 
 import { BlockInfoCard } from "@/components/ui/block-info-card"
 
-<BlockInfoCard 
+<BlockInfoCard
   type="circleback"
   color="linear-gradient(180deg, #E0F7FA 0%, #FFFFFF 100%)"
 />
 
-## Usage Instructions
-
-Receive meeting notes, action items, transcripts, and recordings when meetings are processed. Circleback uses webhooks to push data to your workflows.
-
-
-
+{/* MANUAL-CONTENT-START:intro */}
+[Circleback](https://circleback.ai/) is an AI-powered platform that automates meeting notes, action items, transcripts, and recordings for your team. When a meeting is completed, Circleback processes the conversation and provides detailed notes and action items, along with a transcript and a recording (when available). This helps teams efficiently capture insights, distribute action items, and ensure nothing is missed—all seamlessly integrated into your workflows.
+
+With the Sim Circleback integration, you can:
+
+- **Receive detailed meeting notes and action items**: Automatically collect well-formatted meeting summaries and track actionable tasks discussed during your calls.
+- **Access complete meeting recordings and transcripts**: Get the full conversation and the associated recording, making it easy to review key moments or share with colleagues.
+- **Capture attendee information and meeting context**: Attendee lists, meeting metadata, and tags help keep your data organized and actionable.
+- **Deliver insights directly into your workflows**: Trigger automations or send Circleback data to other systems the moment a meeting is done, using Sim’s powerful webhook triggers.
+
+**How it works in Sim:**  
+Circleback uses webhook triggers: whenever a meeting is processed, data is pushed automatically to your agent or automation. You can build further automations based on:
+
+- Meeting completed (all processed data available)
+- New notes (notes ready even before full meeting is processed)
+- Raw webhook integration for advanced use cases
+
+**The following information is available in the Circleback meeting webhook payload:**
+
+| Field          | Type    | Description                                        |
+|----------------|---------|----------------------------------------------------|
+| `id`           | number  | Circleback meeting ID                              |
+| `name`         | string  | Meeting title                                      |
+| `url`          | string  | Virtual meeting URL (Zoom, Meet, Teams, etc.)      |
+| `createdAt`    | string  | Meeting creation timestamp                         |
+| `duration`     | number  | Duration in seconds                                |
+| `recordingUrl` | string  | Recording URL (valid 24 hours)                     |
+| `tags`         | json    | Array of tags                                      |
+| `icalUid`      | string  | Calendar event ID                                  |
+| `attendees`    | json    | Array of attendee objects                          |
+| `notes`        | string  | Meeting notes in Markdown                          |
+| `actionItems`  | json    | Array of action items                              |
+| `transcript`   | json    | Array of transcript segments                       |
+| `insights`     | json    | User-created insights                              |
+| `meeting`      | json    | Full meeting payload                               |
+
+Whether you want to distribute instant summaries, log action items, or build custom workflows triggered by new meeting data, Circleback and Sim make it seamless to handle everything related to your meetings—automatically.
+{/* MANUAL-CONTENT-END */}
 
 
 ## Triggers

apps/docs/content/docs/en/integrations/imap.mdx

@@ -1,21 +1,29 @@
 ---
-title: IMAP Email
-description: Trigger workflows when new emails arrive via IMAP (works with any email provider)
+title: IMAP
+description: IMAP triggers for automating workflows
 ---
 
 import { BlockInfoCard } from "@/components/ui/block-info-card"
 
-<BlockInfoCard 
+<BlockInfoCard
   type="imap"
   color="#6366F1"
 />
 
-## Usage Instructions
-
-Connect to any email server via IMAP protocol to trigger workflows when new emails are received. Supports Gmail, Outlook, Yahoo, and any other IMAP-compatible email provider.
+{/* MANUAL-CONTENT-START:intro */}
+The IMAP Email trigger allows your Sim workflows to start automatically whenever a new email is received in any mailbox that supports the IMAP protocol. This works with Gmail, Outlook, Yahoo, and most other email providers.
 
+With the IMAP trigger, you can:
 
+- **Automate email processing**: Start workflows in real time when new messages arrive in your inbox.
+- **Filter by sender, subject, or folder**: Configure your trigger to react only to emails that match certain conditions.
+- **Extract and process attachments**: Automatically download and use file attachments in your automated flows.
+- **Parse and use email content**: Access the subject, sender, recipients, full body, and other metadata in downstream workflow steps.
+- **Integrate with any email provider**: Works with any service that provides standard IMAP access, without vendor lock-in.
+- **Trigger on unread, flagged, or custom criteria**: Set up advanced filters for the kinds of emails that start your workflows.
 
+With Sim, the IMAP integration gives you the power to turn email into an actionable source of automation. Respond to customer inquiries, process notifications, kick off data pipelines, and more—directly from your email inbox, with no manual intervention.
+{/* MANUAL-CONTENT-END */}
 
 
 ## Triggers

apps/docs/content/docs/en/integrations/index.mdx

@@ -1,6 +1,7 @@
 ---
 title: Integrations
 description: Connect third-party services and OAuth accounts for your workflows
+pageType: guide
 ---
 
 import { Callout } from 'fumadocs-ui/components/callout'