# Capture changes into my fork

You're integrating one or more commits from a sibling GitHub fork into
the CURRENT WORKING DIRECTORY. The CWD should already be a clean git
working tree on a branch you're willing to commit to.

## Source thread: brauliogusmao takes Mike to Brazil

A top-to-bottom Portuguese localization, with practice areas rewritten for the Brazilian bar.

| # | SHA | Subject | Fork | Authored |
|---|-----|---------|------|----------|
| 1 | [`a096a76d`](https://github.com/brauliogusmao/mike/commit/a096a76d5f4ef1427d4f4389c69d0a36c04e012d) | chore: instala dependencias do backend e frontend | `brauliogusmao/mike` | 2026-05-11 |
| 2 | [`f12456ca`](https://github.com/brauliogusmao/mike/commit/f12456cab218908969a5137feddd9535cf7ab7ae) | feat(i18n): configura next-intl e cria traducoes pt-BR | `brauliogusmao/mike` | 2026-05-11 |
| 3 | [`1f6b1527`](https://github.com/brauliogusmao/mike/commit/1f6b152719c755e537b4230d915ec559b959b724) | feat(i18n): traduz login, signup, modais shared e componentes de diretório | `brauliogusmao/mike` | 2026-05-12 |
| 4 | [`826e25fd`](https://github.com/brauliogusmao/mike/commit/826e25fd68cf72d8b706650fa6999fb3253c935b) | feat(i18n): translate assistant and tabular components to pt-BR | `brauliogusmao/mike` | 2026-05-12 |
| 5 | [`693e2fe5`](https://github.com/brauliogusmao/mike/commit/693e2fe56400f0ab0345a692a3f547fa4b1015d6) | feat(i18n): traduz workflows, modais, páginas e hook de chat para pt-BR | `brauliogusmao/mike` | 2026-05-12 |
| 6 | [`170e7bca`](https://github.com/brauliogusmao/mike/commit/170e7bcaf7d2b6336dcf3d833468f4e75a157422) | feat(i18n): traduz menu lateral (AppSidebar) para pt-BR | `brauliogusmao/mike` | 2026-05-12 |
| 7 | [`b6ed3d1c`](https://github.com/brauliogusmao/mike/commit/b6ed3d1cd330ae0b99f3b4e22728867c1d5e9fc1) | feat(i18n): traduz botão de documentos (AddDocButton) para pt-BR | `brauliogusmao/mike` | 2026-05-12 |
| 8 | [`ab9b0d7c`](https://github.com/brauliogusmao/mike/commit/ab9b0d7ccc24b1a4e78041e4de33650500c83aa4) | feat(i18n): renomeia Revisões Tabulares para terminologia jurídica brasileira | `brauliogusmao/mike` | 2026-05-12 |
| 9 | [`50553c3c`](https://github.com/brauliogusmao/mike/commit/50553c3c1b8a1e2947023ff2c9f8761289d2fc02) | feat(i18n): traduz painel de alterações rastreadas para pt-BR | `brauliogusmao/mike` | 2026-05-12 |
| 10 | [`937d816a`](https://github.com/brauliogusmao/mike/commit/937d816a65428f4de97bb75d816f75935798324f) | feat: traduz áreas de prática para português e documenta como config de instânci | `brauliogusmao/mike` | 2026-05-12 |
| 11 | [`1dcd8a86`](https://github.com/brauliogusmao/mike/commit/1dcd8a86d40944df65b3f357e7819648eb98d7b2) | feat: renomeia Workflows para Fluxos de trabalho e adiciona label no botão Criar | `brauliogusmao/mike` | 2026-05-12 |
| 12 | [`846ce3f2`](https://github.com/brauliogusmao/mike/commit/846ce3f2e5f9cea2fbde1eac8ea282cca07783eb) | feat: atualiza modal de novo fluxo com nomenclatura em português | `brauliogusmao/mike` | 2026-05-12 |
| 13 | [`a9e0d671`](https://github.com/brauliogusmao/mike/commit/a9e0d6714143bf52701f41bcffdd3311fc8d48b4) | fix: corrige label "Workflows" → "Fluxos de trabalho" no chat input | `brauliogusmao/mike` | 2026-05-12 |
| 14 | [`61e35e23`](https://github.com/brauliogusmao/mike/commit/61e35e235eb680df26751c0da8b960ac92030101) | feat: traduz página de Configurações para português | `brauliogusmao/mike` | 2026-05-12 |
| 15 | [`fde100d5`](https://github.com/brauliogusmao/mike/commit/fde100d5c5ceb4f583e6dc11b6181a8d36a4621f) | merge: adaptação para português (pt-BR) | `brauliogusmao/mike` | 2026-05-12 |

### Commit URLs (for your tooling)

1. https://github.com/brauliogusmao/mike/commit/a096a76d5f4ef1427d4f4389c69d0a36c04e012d
2. https://github.com/brauliogusmao/mike/commit/f12456cab218908969a5137feddd9535cf7ab7ae
3. https://github.com/brauliogusmao/mike/commit/1f6b152719c755e537b4230d915ec559b959b724
4. https://github.com/brauliogusmao/mike/commit/826e25fd68cf72d8b706650fa6999fb3253c935b
5. https://github.com/brauliogusmao/mike/commit/693e2fe56400f0ab0345a692a3f547fa4b1015d6
6. https://github.com/brauliogusmao/mike/commit/170e7bcaf7d2b6336dcf3d833468f4e75a157422
7. https://github.com/brauliogusmao/mike/commit/b6ed3d1cd330ae0b99f3b4e22728867c1d5e9fc1
8. https://github.com/brauliogusmao/mike/commit/ab9b0d7ccc24b1a4e78041e4de33650500c83aa4
9. https://github.com/brauliogusmao/mike/commit/50553c3c1b8a1e2947023ff2c9f8761289d2fc02
10. https://github.com/brauliogusmao/mike/commit/937d816a65428f4de97bb75d816f75935798324f
11. https://github.com/brauliogusmao/mike/commit/1dcd8a86d40944df65b3f357e7819648eb98d7b2
12. https://github.com/brauliogusmao/mike/commit/846ce3f2e5f9cea2fbde1eac8ea282cca07783eb
13. https://github.com/brauliogusmao/mike/commit/a9e0d6714143bf52701f41bcffdd3311fc8d48b4
14. https://github.com/brauliogusmao/mike/commit/61e35e235eb680df26751c0da8b960ac92030101
15. https://github.com/brauliogusmao/mike/commit/fde100d5c5ceb4f583e6dc11b6181a8d36a4621f

## What I want you to do

1.  **Sanity check first.**

    - Run `git status`. If the working tree is dirty (uncommitted
      changes you don't recognise, untracked stuff you don't expect),
      STOP and tell me — don't try to be helpful by stashing. I'll
      resolve it.
    - Run `git branch --show-current`. If the branch is `main` or
      `master`, confirm with me before proceeding.

2.  **For each commit URL above, in the order listed:**

    a.  Fetch the diff. Pick whichever works:
        - `gh api repos/<owner>/<repo>/commits/<sha>` returns the full
          patch in JSON.
        - WebFetch the URL with `.patch` appended, e.g.
          `https://github.com/<owner>/<repo>/commit/<sha>.patch`.

    b.  Read the original commit message. That's the AUTHOR's intent —
        respect it.

    c.  Read the diff and understand the change. **Don't blindly
        cherry-pick.** This is a sibling fork — paths, naming, and
        structure can differ. You're porting, not pasting.

    d.  Compare against THIS repo's layout:
        - File at the same path → apply the change.
        - File exists under a different name (renamed / restructured) →
          apply the equivalent change at the right location.
        - File doesn't exist here at all → decide: new file we want, or
          is the source adding something this repo already has by
          another name? Use judgement. Lean towards creating the file
          when in doubt — easier for me to delete than to recreate.

    e.  Apply the change. Run `git diff` after, eyeball it, fix
        obvious issues (lint errors, broken imports, typos in the diff
        itself).

    f.  Commit with a message that:
        - Preserves the source commit's subject line.
        - Adds a short body explaining what you adapted, if anything.
        - Includes trailers:

              Source: <commit-url>
              Source-author: <original author name>

        so the attribution stays clear.

3.  **After all commits are applied:**

    - Run `git log --oneline -<count>` showing what you produced.
    - Show `git status` final state.
    - List any files you skipped, conflicts you resolved, and any
      assumptions you made.

## Rules

- **Do not push.** Local commits only. I'll review and push.
- **Do not rebase or force.** Only fresh commits. If you'd otherwise
  need a force push, stop and explain why.
- **Don't touch `.git/config` or run `git remote add`.** Leave my
  repo's remote setup alone.
- **No package installs, build steps, or migrations** unless the
  change manifestly requires it AND you explicitly tell me what
  you're about to run first.
- **One commit per source commit.** Don't squash. Don't split. If
  porting genuinely requires either, explain.
- **Read existing code before changing it.** This isn't the source
  fork. Match the local style.

## If you get stuck

Stop and tell me. Show what you've already done (commits made, files
changed), what blocked you (conflict, missing file, ambiguous intent),
and your recommended next move. I'd rather ship 3 of 5 commits cleanly
than have you guess on the 4th and break things.