chore(deps-dev): bump vitest from 0.34.6 to 3.2.6

.github/CODEOWNERS

@@ -1,5 +1,3 @@
-# These owners will be the default owners for everything in
-# the repo. Unless a later match takes precedence,
-# @global-owner1 and @global-owner2 will be requested for
-# review when someone opens a pull request.
-*       @leonardorpr
+# Owner padrao do repositorio (fork Blu do SDK de tokenizacao).
+# Ajuste para o time dedicado (ex.: Squad Acquiring) se houver um slug proprio.
+*       @Pagnet/azure_plataformas

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,132 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+- Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+- The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+ops@useblu.com.br.
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
+[https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

.github/CONTRIBUTING.md

@@ -0,0 +1,107 @@
+# How to Contribute
+
+:+1::tada: First off, thanks for taking the time to contribute! :tada::+1:
+
+The following is a set of guidelines for contributing to
+`@useblu/checkout-tokenization`. Please take a moment to review this document in
+order to make the contribution process straightforward and effective for
+everyone involved.
+
+### Table Of Contents
+
+- [Code of Conduct](#code-of-conduct)
+- [Issues](#issues)
+- [Making Changes](#making-changes)
+- [Pull Requests](#pull-requests)
+- [Setup](#setup)
+- [Syncing with upstream](#syncing-with-upstream)
+- [Styleguides](#styleguides)
+
+## Code of Conduct
+
+We adopted a Code of Conduct that we expect project participants to adhere to.
+Please read [the full text](CODE_OF_CONDUCT.md) so that you can understand what
+actions will and will not be tolerated.
+
+## Issues
+
+A great way to contribute to the project is to send a detailed report when you
+encounter an issue. We always appreciate a well-written, thorough bug report,
+and will thank you for it!
+
+Check that our issue database doesn't already include that problem or suggestion
+before submitting an issue.
+
+### Security Issues
+
+Blu's staff takes security and privacy issues seriously — even more so for a
+payments SDK. If you discover a potential point of failure, please bring it to
+our attention immediately!
+
+Please **DO NOT** file a public issue, but rather send your report privately to
+seguranca@useblu.com.br.
+
+Read more: [SECURITY.md](SECURITY.md)
+
+## Making Changes
+
+- We adopted [GitHub Flow](https://guides.github.com/introduction/flow/).
+- Assign the issue to yourself so everyone knows you took it.
+- Create your branch from `main` following the pattern
+  `feat/<TICKET>/<short-description>` (e.g. `feat/AC-161/prod-environment-docs`).
+- Make commits of logical and atomic units, following
+  [Conventional Commits](https://www.conventionalcommits.org/).
+- Submit a pull request.
+
+## Pull Requests
+
+Please follow these steps to have your contribution considered by the
+maintainers:
+
+1. Follow all instructions in [the template](PULL_REQUEST_TEMPLATE.md).
+2. Follow the [styleguides](#styleguides).
+3. After you submit your pull request, verify that all CI status checks
+   (lint, tests and build) are passing.
+
+While the prerequisites above must be satisfied prior to having your pull
+request reviewed, the reviewer(s) may ask you to complete additional work,
+tests, or other changes before your pull request can be accepted.
+
+## Setup
+
+This project uses [pnpm](https://pnpm.io/) and Node.js 18 (see `.nvmrc`).
+
+```sh
+# install dependencies
+pnpm install
+
+# run the test suite
+pnpm test:ci
+
+# lint
+pnpm lint
+
+# build (ESM + CJS + type declarations)
+pnpm build
+```
+
+## Syncing with upstream
+
+This package is a **fork** of
+[`@malga/tokenization`](https://github.com/plughacker/malga-tokenization). The
+tokenization logic is inherited from upstream — we do not rewrite it. When
+bringing in upstream changes:
+
+- **Never auto-merge:** every upstream update goes through manual review.
+- **Cherry-pick, don't merge:** to avoid dragging in unwanted changes.
+- **Test locally** before opening a sync PR.
+- **Changelog:** document what changed from upstream in `CHANGELOG.md`.
+- Avoid changing inherited public signatures — each divergence increases the
+  cost of future syncs.
+
+## Styleguides
+
+- **Code:** ESLint + Prettier (`pnpm lint`).
+- **Commits:** [Conventional Commits](https://www.conventionalcommits.org/).
+- **Tests:** keep the inherited suite green and add tests for fork-specific
+  behavior.

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -1,5 +1,5 @@
 name: 🐛 Bug Report
-description: Something is wrong with Malga Tokenization.
+description: Something is wrong with Blu Checkout Tokenization.
 title: '[Bug]: '
 labels:
   - bug
@@ -15,12 +15,11 @@ body:
         support or usage questions. Questions here don't have as much visibility as they do elsewhere. Before
         you ask a question, here are some resources to get help first:
 
-        - Read the docs: https://docs.malga.io/
-        - Explore examples: https://github.com/plughacker
-        - Ask in chat: https://discord.com/h5J5ZkhTXV
+        - Read the docs: https://github.com/Pagnet/blu-checkout-tokenization#readme
+        - Explore examples: https://github.com/Pagnet/blu-checkout-tokenization/tree/main/examples/blu
   - type: input
     attributes:
-      label: What version of Malga Tokenization are you using?
+      label: What version of Blu Checkout Tokenization are you using?
     validations:
       required: true
   - type: textarea

.github/ISSUE_TEMPLATE/config.yml

@@ -1,5 +1,5 @@
 blank_issues_enabled: false
 contact_links:
-  - name: 🤔 Support/Usage Question
-    url: https://discord.com/h5J5ZkhTXV
-    about: This is a bug tracker, not a support system. For usage questions, please use Dicord where there are a lot more people ready to help you out. Thanks!
+  - name: 🔒 Security issue
+    url: https://github.com/Pagnet/blu-checkout-tokenization/blob/main/.github/SECURITY.md
+    about: Please do not open a public issue for security problems. Report them privately to seguranca@useblu.com.br.

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -1,5 +1,5 @@
 name: 💡 Feature Request
-description: I want to add something to Malga Tokenization.
+description: I want to add something to Blu Checkout Tokenization.
 title: '[Feature]: '
 labels:
   - feature
@@ -15,9 +15,8 @@ body:
         support or usage questions. Questions here don't have as much visibility as they do elsewhere. Before
         you ask a question, here are some resources to get help first:
 
-        - Read the docs: https://docs.malga.io/
-        - Explore examples: https://github.com/plughacker
-        - Ask in chat: https://discord.com/h5J5ZkhTXV
+        - Read the docs: https://github.com/Pagnet/blu-checkout-tokenization#readme
+        - Explore examples: https://github.com/Pagnet/blu-checkout-tokenization/tree/main/examples/blu
   - type: textarea
     attributes:
       label: What is the new or updated feature that you are suggesting?