docs(changelog): add v1.1.0 release section

[gomessguii]

Passo 2 do corte da v1.1.0. Adiciona a seção ## [v1.1.0] - 2026-09-02 ao CHANGELOG do umbrella. Doc-only: nenhum código, nenhum ponteiro.

Este commit é onde a tag v1.1.0 do umbrella vai ser cortada, e os sete bullets de ### Submodules updated são o corpo das sete GitHub Releases dos submódulos — por isso cada bullet é auto-contido.

O que a janela contém

2026-07-15 → 2026-09-02 (49 dias), 965 commits, medidos por serviço do ponteiro que este repo carregava na v1.0.0 até o head congelado. Os sete ranges de..até estão em Repository housekeeping para qualquer um reproduzir com git rev-list --count.

	commits	migrations
evo-ai-frontend-community	347	0
evo-ai-crm-community	335	5
evo-auth-service-community	105	9
evo-ai-core-service-community	78	8
evo-ai-processor-community	48	0
evo-flow-community	40	0
evo-bot-runtime	12	0

A v1.0.0 não tinha migration nenhuma; esta tem 22, e várias são porta de mão única:

• quatro revogações forward-only no auth (down no-op de propósito — re-conceder seria escalação de privilégio frente a uma instalação nova);
• uma que ALARGA (20260818120001): papel que só criava passa a gerenciar, porque .manage não tem divisão mais fina;
• backfill irreversível de SKU no CRM e backfill irreversível de modelo no core, esse último exigindo que o role do migrate seja DONO de evo_core_agents;
• dois índices CONCURRENTLY, um deles capaz de falhar em duplicatas pré-existentes.

### Notes for upgrading an existing PROD enumera as 22 uma a uma, com risco e ordem (auth primeiro — ele é dono de users).

Como foi produzido

Levantamento por agente sobre o range congelado de cada serviço, seguido de um crítico de completude que rodou contra os commits reais. Ele apontou 25 defeitos no primeiro rascunho; os dois críticos:

• contagens de commit — o crítico mediu os ponteiros pré-bump e acusou fabricação. Reconferi na mão: os números do texto são do range que a tag vai conter. Para não deixar isso ambíguo, cada bullet e o housekeeping agora citam o de..até em SHA curto.
• evolution-api — o rascunho dizia que os três submódulos não-família estavam parados. O evolution-api moveu 12 commits com mudança de comportamento. Corrigido; só evolution-go e evo-nexus estão parados.

Os outros 23 (migrations não citadas, breaking changes ausentes, acoplamentos em um sentido só) foram aplicados.

Fora do relatório dos agentes, corrigi à mão o bullet de Swarm reproducibility: ele descrevia o evo-flow no :develop porque o range analisado termina antes da #184, que é justamente onde esse pin foi corrigido.

Depois desta PR

3. tags v1.1.0 annotated nos sete submódulos → publicam evoapicloud/<svc>:1.1.0 e movem o :latest
4. GitHub Release em cada submódulo, com o corpo extraído desta seção
5. tag v1.1.0 lightweight neste commit → release.yml
6. develop → main

Summary by Sourcery

Document the v1.1.0 release and its production upgrade guidance across the CRM Community family.

Documentation:

• Add a comprehensive v1.1.0 release section documenting family-wide RBAC, credential vault, AI, pipeline, messaging, journey, WhatsApp, webhook, and model-catalogue changes.
• Document migration requirements, upgrade risks, service compatibility constraints, environment configuration, and repository housekeeping for existing production deployments.

[sourcery-ai]

Sorry @gomessguii, you've used your own review budget of 250,000 diff characters for the last 7 days.

You can request another review in 1 day and 5 hours by commenting @sourcery-ai review. Upgrade to get a review now.

[sourcery-ai]

Reviewer's Guide

This documentation-only PR adds the umbrella's v1.1.0 changelog section, consolidating the frozen seven-service release contents into implementation-focused themes and self-contained submodule notes, with detailed migration, deployment, compatibility, configuration, and production-upgrade guidance.

Sequence diagram for v1.1.0 production upgrade

sequenceDiagram
    participant Operator
    participant Auth
    participant CRM
    participant Core
    participant Processor

    Operator->>Auth: db:migrate
    Auth-->>Operator: RBAC migrations applied
    Operator->>CRM: db:migrate
    CRM-->>Operator: CRM migrations applied
    Operator->>Core: db:migrate
    Core-->>Operator: Vault and model migrations applied
    Operator->>CRM: ai_credentials:migrate_dry_run
    CRM-->>Operator: Migration report
    Operator->>CRM: ai_credentials:migrate
    CRM->>Core: Resolve vault credentials
    Core-->>CRM: Encrypted credential data
    Operator->>CRM: integration_credentials:migrate
    Operator->>Processor: Deploy vault-compatible processor
    Processor->>Core: Read credential_refs and vault credentials
    Core-->>Processor: Credential data

Loading

Flow diagram for v1.1.0 media forwarding and bounded retry

flowchart LR
    CRM[CRM build_message_event]
    Buffer[Bot Runtime attachment buffer]
    Allowlist[MEDIA_HOST_ALLOWLIST]
    Processor[AI Processor]
    Notice[AI failure postback]

    CRM -->|attachments with TTL URLs| Buffer
    Buffer --> Allowlist
    Allowlist -->|validated media| Processor
    Processor -->|transient failure| Buffer
    Buffer -->|bounded retry| Processor
    Processor -->|final failure| Notice

Loading

File-Level Changes

Change	Details	Files
Adds a comprehensive v1.1.0 release section documenting the frozen family release window, implementation themes, service deltas, API/configuration changes, and upgrade risks.	Summarizes 965 commits across seven tagged submodules and records reproducible commit ranges. Documents 22 migrations, including irreversible backfills, forward-only RBAC revocations, privilege widening, and concurrent indexes. Details credential-vault rollout, fail-closed authorization, pipeline/RBAC changes, AI/media behavior, segmentation, WhatsApp, webhooks, and model updates. Adds self-contained release bullets for all seven submodules plus behavior-changing non-family pointer updates. Adds production upgrade notes covering migration ordering, prerequisites, environment variables, version couplings, breaking contracts, probes, jobs, and rollback hazards.	CHANGELOG.md
Extends release housekeeping and existing documentation to explain repository-level cleanup, CI coverage, deployment reproducibility, and role-model corrections.	Records CI and documentation additions across submodules and umbrella documentation corrections. Documents deletion of internal review tooling and removal of dangling references. Describes swarm image-tag alignment and the remaining :latest reproducibility limitation. Lists exact family pointer ranges and commit counts, including unchanged or behavior-changing non-family submodules.	CHANGELOG.md

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.