@shiftleftpt/sbd-toe-mcp 0.1.0

package/.env.example

@@ -0,0 +1,35 @@
+# Runtime normal: o bundle local já vem incluído no repositório e nos GitHub Releases.
+# Não é necessário Algolia nem checkout adicional do builder semântico para usar o MCP.
+DOCS_SNAPSHOT_FILE=./data/publish/algolia_docs_records.json
+ENTITIES_SNAPSHOT_FILE=./data/publish/algolia_entities_records.json
+DOCS_ENRICHED_SNAPSHOT_FILE=./data/publish/algolia_docs_records_enriched.json
+ENTITIES_ENRICHED_SNAPSHOT_FILE=./data/publish/algolia_entities_records_enriched.json
+INDEX_SETTINGS_FILE=./data/publish/algolia_index_settings.json
+RUN_MANIFEST_FILE=./data/reports/run_manifest.json
+
+# Os dois índices publicados pelo upstream continuam a ser a referência semântica.
+SEMANTIC_BACKEND_DOCS_INDEX=SbD-ToE-ASKAI-Docs
+SEMANTIC_BACKEND_ENTITIES_INDEX=SbD-ToE-ASKAI-Entities
+
+# Prompting e links de referência.
+SYSTEM_PROMPT_FILE=./prompts/sbd-toe-chat-system.md
+SITE_BASE_URL=https://www.securitybydesign.dev/
+MANUAL_BASE_URL=https://www.securitybydesign.dev/sbd-toe/sbd-manual/
+CROSS_CHECK_BASE_URL=https://www.securitybydesign.dev/sbd-toe/cross-check-normativo/
+
+DEFAULT_LANGUAGE=pt-PT
+DEBUG_MODE=false
+DOCS_HITS=8
+ENTITIES_HITS=5
+MAX_CONTEXT_RECORDS=8
+SAMPLING_MAX_TOKENS=1200
+
+# Configuração opcional para mantenedores que queiram atualizar o bundle embutido
+# a partir de um checkout local do repositório sbd-toe-knowledge-graph.
+UPSTREAM_KNOWLEDGE_GRAPH_DIR=../sbd-toe-knowledge-graph
+BACKEND_CHECKOUT_FILE=./data/upstream/backend-checkout.json
+
+# Fonte dos snapshots: 'local' (default, cópia da repo local) ou 'release' (GitHub Releases)
+UPSTREAM_SOURCE=local
+# Tag da release a usar (só relevante quando UPSTREAM_SOURCE=release). Use 'latest' para a mais recente.
+UPSTREAM_RELEASE_TAG=latest

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,323 @@
+# sbd-toe-mcp-poc
+
+Servidor MCP (Model Context Protocol) para VS Code, em Node.js/TypeScript, que faz retrieval local sobre snapshots semânticos publicados do manual SbD-ToE e os expõe ao chat via `stdio`.
+
+> Estado atual: **PoC / primeira iteração publicável**. O foco desta versão é distribuição simples via GitHub Releases, uso local no VS Code, grounding forte e zero dependência de builder semântico em runtime.
+
+## O que é este projeto
+
+Este repositório empacota um servidor MCP que:
+
+- corre localmente via `stdio`
+- expõe tools e prompts MCP para consulta do manual
+- usa o modelo configurado pelo utilizador no VS Code
+- faz retrieval local sobre um bundle embutido em `data/publish/`
+- devolve contexto grounded, citações e metadados úteis para debug
+
+O objetivo é responder melhor, dentro do VS Code, a perguntas práticas sobre o ecossistema SbD-ToE, por exemplo:
+
+```text
+quais os requisitos de autenticacao que preciso implementar para esta aplicacao L1
+```
+
+ou:
+
+```text
+Que policies governam pipelines CI/CD?
+```
+
+## Porque existe
+
+O manual SbD-ToE é a fonte editorial canónica, mas o consumo prático dentro do editor exige uma camada técnica própria:
+
+- descoberta contextual no momento da pergunta
+- recuperação determinística de records relevantes
+- composição de prompt grounded
+- integração direta com o chat do VS Code
+
+Este repositório existe para fazer essa ponte, sem duplicar o papel dos outros repositórios do ecossistema.
+
+## Relação com o ecossistema SbD-ToE
+
+| Repositório | Papel |
+| --- | --- |
+| `Shiftleftpt/SbD-ToE-Manual` | fonte editorial canónica do manual |
+| `sbd-toe-knowledge-graph` | builder/publicador dos snapshots semânticos |
+| `sbd-toe-mcp-poc` | consumer MCP para uso local no VS Code |
+
+Este projeto **consome** artefactos já produzidos pelo `sbd-toe-knowledge-graph`. Não reindexa o manual, não reconstrói semântica e não substitui o builder.
+
+## O que faz
+
+- consulta os snapshots `SbD-ToE-ASKAI-Docs` e `SbD-ToE-ASKAI-Entities`
+- faz ranking local observável para seleção de contexto
+- expõe as tools `search_sbd_toe_manual`, `answer_sbd_toe_manual` e `inspect_sbd_toe_retrieval`
+- expõe a prompt MCP `ask_sbd_toe_manual`
+- permite debug forte quando `debug=true` ou `DEBUG_MODE=true`
+- usa sampling MCP opcionalmente, mantendo o modelo do lado do utilizador
+
+## O que não faz
+
+- não faz parsing do corpus Markdown
+- não reconstrói bundles semânticos
+- não reindexa o manual
+- não depende de Algolia em runtime
+- não executa retrieval remoto
+- não mantém memória conversacional
+- não substitui o VS Code Chat nem o `sbd-toe-knowledge-graph`
+
+## Arquitetura resumida
+
+1. O utilizador faz uma pergunta no chat do VS Code.
+2. O chat chama `search_sbd_toe_manual` ou `answer_sbd_toe_manual`.
+3. O servidor MCP lê os snapshots locais embutidos em `data/publish/`.
+4. O retrieval combina records documentais e estruturados.
+5. O servidor devolve contexto grounded com citações `[D1]`, `[E1]`, links e debug.
+6. O modelo do utilizador responde com base nesse contexto.
+
+O papel detalhado deste repositório está documentado em [`docs/role.md`](docs/role.md).
+
+## Ferramentas MCP expostas
+
+- `search_sbd_toe_manual`
+  - tool principal para o fluxo normal de chat
+  - devolve contexto grounded sem obrigar a sampling
+- `answer_sbd_toe_manual`
+  - usa retrieval local e pede a resposta final ao modelo do utilizador via MCP sampling
+- `inspect_sbd_toe_retrieval`
+  - mostra retrieval, seleção final e prompt montado
+  - útil para tuning, grounding e troubleshooting
+- `ask_sbd_toe_manual`
+  - prompt MCP/slash command para orientar o chat a usar retrieval antes de responder
+
+## Distribuição e release bundle
+
+O canal principal de distribuição é **npm** (`sbd-toe-mcp`). O **GitHub Releases** mantém-se como canal secundário — publica um bundle self-contained para instalação em ambientes sem acesso à internet ou sem `npx`.
+
+Cada release publica um bundle via GitHub Releases com convenção de nome explícita:
+
+- `sbd-toe-mcp-vX.Y.Z-bundle.tar.gz`
+- `sbd-toe-mcp-vX.Y.Z-bundle.zip`
+- `sbd-toe-mcp-vX.Y.Z-bundle.sha256`
+
+O bundle inclui:
+
+- `dist/`
+- `data/publish/`
+- `data/reports/run_manifest.json`
+- `prompts/`
+- `examples/`
+- `docs/`
+- `.vscode/mcp.json`
+- `.env.example`
+- `README.md`
+- `CONTRIBUTING.md`
+- `CODE_OF_CONDUCT.md`
+- `SECURITY.md`
+- `SUPPORT.md`
+- ficheiros de licença
+
+O bundle **não** inclui:
+
+- `node_modules`
+- checkout completo do upstream
+- tooling de desenvolvimento desnecessário para runtime
+
+## Como os snapshots são distribuídos
+
+`data/publish/` é tratado como parte intencional do produto:
+
+- fica **versionado no repositório**
+- fica **incluído no artefacto de release**
+- é a base do retrieval local em runtime
+
+Isto significa que:
+
+- o utilizador **não precisa** de Algolia
+- o utilizador **não precisa** de correr o builder semântico
+- o utilizador **não precisa** de fazer checkout do `sbd-toe-knowledge-graph` para usar o servidor
+
+O ficheiro `data/reports/run_manifest.json` mantém a proveniência do snapshot embutido.
+Esse ficheiro deve conter apenas proveniência pública e redistribuível, sem paths absolutos de máquinas locais.
+
+## Instalação via GitHub Release (alternativa sem internet)
+
+Fluxo para ambientes sem acesso ao npm ou sem `npx`:
+
+1. Descarregar o asset `sbd-toe-mcp-vX.Y.Z-bundle.zip` ou `sbd-toe-mcp-vX.Y.Z-bundle.tar.gz` em **GitHub Releases**.
+2. Extrair o archive para um diretório local.
+3. Confirmar que a extração já inclui `dist/` e `data/publish/`.
+4. Copiar `.env.example` para `.env`.
+5. Abrir a pasta extraída no VS Code.
+6. Reutilizar o `.vscode/mcp.json` já incluído no bundle.
+7. Abrir o chat e usar perguntas reais sobre o manual.
+
+Exemplo:
+
+```bash
+cp .env.example .env
+```
+
+Depois de extrair a release, não é necessário correr `npm ci` nem `npm run build`.
+Também não é necessário editar manualmente a configuração MCP se usares a pasta extraída como workspace do VS Code.
+
+## Quick Start — instalar via npm
+
+[![npm](https://img.shields.io/npm/v/@shiftleftpt%2fsbd-toe-mcp)](https://www.npmjs.com/package/@shiftleftpt/sbd-toe-mcp)
+
+**Zero configuração obrigatória.** O servidor funciona directamente com `npx`:
+
+1. Instalar Node.js ≥ 20.9.0: [nodejs.org/download](https://nodejs.org/download/)
+2. Registar o servidor no teu cliente MCP (exemplo para Claude Code):
+   ```bash
+   claude mcp add sbd-toe -- npx -y @shiftleftpt/sbd-toe-mcp
+   ```
+3. Usar as tools MCP no Claude Code (ou Claude Desktop, VS Code, Cursor, etc.)
+
+Para instruções completas por cliente MCP (Claude Desktop, VS Code, Cursor, Windsurf, Zed),
+consultar [`docs/installation.md`](docs/installation.md).
+
+---
+
+## Instalação a partir do source
+
+Se preferires trabalhar a partir do source deste repositório:
+
+```bash
+npm ci
+npm run check
+npm run build
+```
+
+O checkout de source já traz `data/publish/` versionado. Portanto, mesmo a partir do source, o uso normal do MCP **não** depende do builder semântico.
+
+O script abaixo é apenas para mantenedores que queiram atualizar o bundle embutido a partir de um checkout local do `sbd-toe-knowledge-graph`:
+
+```bash
+npm run checkout:backend
+```
+
+Esse fluxo regenera um manifesto local em `data/upstream/backend-checkout.json`, usado apenas para manutenção/debug local e não versionado neste repositório.
+
+## Configuração `.env`
+
+Copiar `.env.example` para `.env` e ajustar apenas o que fizer sentido para o teu ambiente local.
+
+Variáveis mais relevantes para runtime:
+
+| Variável | Uso |
+| --- | --- |
+| `DOCS_SNAPSHOT_FILE` | snapshot documental local |
+| `ENTITIES_SNAPSHOT_FILE` | snapshot de entidades local |
+| `INDEX_SETTINGS_FILE` | metadados dos índices publicados |
+| `RUN_MANIFEST_FILE` | proveniência do bundle embutido |
+| `SYSTEM_PROMPT_FILE` | system prompt usada pela tool de answer |
+| `DEBUG_MODE` | ativa debug adicional nas respostas |
+
+Variáveis de manutenção opcional:
+
+| Variável | Uso |
+| --- | --- |
+| `UPSTREAM_KNOWLEDGE_GRAPH_DIR` | checkout local do `sbd-toe-knowledge-graph` |
+| `BACKEND_CHECKOUT_FILE` | manifesto local do último refresh do bundle; ficheiro de manutenção local, não versionado |
+
+Não há API keys obrigatórias neste projeto: o modelo continua a ser o do utilizador no VS Code.
+
+## Integração com VS Code
+
+O exemplo de configuração está em [`examples/vscode.mcp.json`](examples/vscode.mcp.json).
+
+Para o fluxo mais simples via GitHub Release, o bundle já inclui [`.vscode/mcp.json`](.vscode/mcp.json) com este formato:
+
+```json
+{
+  "servers": {
+    "sbdToe": {
+      "type": "stdio",
+      "command": "node",
+      "args": ["${workspaceFolder}/dist/index.js"],
+      "envFile": "${workspaceFolder}/.env"
+    }
+  }
+}
+```
+
+Se abrires a pasta extraída no VS Code, `${workspaceFolder}` passa a apontar para esse bundle e o editor pode usar a configuração diretamente.
+
+Exemplo realista para um bundle extraído fora do workspace atual:
+
+```json
+{
+  "servers": {
+    "sbdToe": {
+      "type": "stdio",
+      "command": "node",
+      "args": ["/absolute/path/to/sbd-toe-mcp-poc/dist/index.js"],
+      "envFile": "/absolute/path/to/sbd-toe-mcp-poc/.env"
+    }
+  }
+}
+```
+
+Se estiveres a trabalhar diretamente neste repositório, podes adaptar para `${workspaceFolder}`.
+
+## Exemplo de uso no chat
+
+Perguntas úteis para validar a integração:
+
+```text
+quais os requisitos de autenticacao que preciso implementar para esta aplicacao L1
+```
+
+```text
+Que policies governam pipelines CI/CD?
+```
+
+Comportamento esperado:
+
+- o chat usa `search_sbd_toe_manual` ou `answer_sbd_toe_manual`
+- o MCP recupera records relevantes do bundle local
+- a resposta final usa apenas o contexto recuperado
+- a resposta cita records e aponta páginas determinísticas quando existirem
+
+## Troubleshooting e debug
+
+- Se `dist/` não existir, estás provavelmente num checkout de source sem build concluído.
+- Se `data/publish/` não existir, a instalação está incompleta ou o archive foi extraído incorretamente.
+- Se o cliente MCP não suportar `sampling`, usa `search_sbd_toe_manual` como fluxo principal.
+- Usa `inspect_sbd_toe_retrieval` para ver retrieval, seleção final e prompt montado.
+- Ativa `DEBUG_MODE=true` para anexar metadados de debug à resposta.
+- Se precisares de atualizar o snapshot embutido, usa `npm run checkout:backend` a partir de um checkout local do `sbd-toe-knowledge-graph`.
+
+## Contribuição
+
+O fluxo de contribuição está em [`CONTRIBUTING.md`](CONTRIBUTING.md).
+
+Em resumo:
+
+- trunk-based development com `master`
+- branches `feat/`, `fix/`, `docs/`, `chore/` e `hotfix/`
+- validação local com `npm ci`, `npm run check` e `npm run build`
+- teste manual no VS Code antes de abrir PR
+- squash merge para `master`
+- releases por tag `vX.Y.Z`
+
+## Próximas iterações
+
+Os pontos abertos e candidatos a evolução futura estão em [`NEXT-STEPS.md`](NEXT-STEPS.md), incluindo a hipótese de uma extensão wrapper para publicação no VS Code Marketplace.
+
+## Suporte
+
+Ver [`SUPPORT.md`](SUPPORT.md).
+
+## Segurança
+
+Ver [`SECURITY.md`](SECURITY.md). Vulnerabilidades devem ser reportadas em privado por email, nunca por issue público.
+
+## Licença
+
+Este repositório usa **split licensing**:
+
+- código e runtime: [`LICENSE`](LICENSE) (`Apache-2.0`)
+- documentação e snapshots embutidos: [`LICENSE-DATA`](LICENSE-DATA) (`CC BY-SA 4.0`)
+- nota de mapeamento e atribuição: [`LICENSE-NOTE.md`](LICENSE-NOTE.md)