# 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: nwhitehouse opens Mike to a hand-picked roster

Launch-week plumbing brings the fork up as a hosted product, with signups locked to three named firms at the database.

| # | SHA | Subject | Fork | Authored |
|---|-----|---------|------|----------|
| 1 | [`076add79`](https://github.com/nwhitehouse/mike/commit/076add799b024ca30e21a2232636bd5c81e785ef) | Hosting prep: multi-origin CORS, signup redirect, region env | `nwhitehouse/mike` | 2026-05-01 |
| 2 | [`f061f757`](https://github.com/nwhitehouse/mike/commit/f061f75773302114c3be77c81f681f66386332bd) | Fix Railway build: use aptPkgs for libreoffice so Node.js auto-detection survive | `nwhitehouse/mike` | 2026-05-01 |
| 3 | [`f3ca06e6`](https://github.com/nwhitehouse/mike/commit/f3ca06e65bb8364fb29dd5c60124223faa76d0df) | Pin backend Node engine to >=20 (Nixpacks dropped Node 18) | `nwhitehouse/mike` | 2026-05-01 |
| 4 | [`f4a157ba`](https://github.com/nwhitehouse/mike/commit/f4a157bac954d29df1d843645f29780b1f8d322d) | Frontend: legacy-peer-deps so npm install survives next@16.0.3 / @opennextjs/clo | `nwhitehouse/mike` | 2026-05-01 |
| 5 | [`a19d145a`](https://github.com/nwhitehouse/mike/commit/a19d145ac0ec8cad73f0f50770219470ffec6ab6) | Trigger Vercel rebuild on latest main | `nwhitehouse/mike` | 2026-05-01 |
| 6 | [`faaa8458`](https://github.com/nwhitehouse/mike/commit/faaa845854854bc117faa2406e003051979942a1) | Re-trigger Vercel after verified-commits override | `nwhitehouse/mike` | 2026-05-01 |
| 7 | [`58fdae57`](https://github.com/nwhitehouse/mike/commit/58fdae5759d56e17b640e0928aec4d9d0ab033ac) | Bump Next.js to 16.2.4 (Vercel blocks deploys of vulnerable 16.0.3) | `nwhitehouse/mike` | 2026-05-01 |
| 8 | [`4d13761c`](https://github.com/nwhitehouse/mike/commit/4d13761c9c14518af8a0368c2eecf76f4cae610c) | CORS: allow tryolava.ai apex + subdomains | `nwhitehouse/mike` | 2026-05-01 |
| 9 | [`79b39c9e`](https://github.com/nwhitehouse/mike/commit/79b39c9e940d7aaf0250b6bbfe51c081e1fe20d8) | Email domain whitelist for signups (Onit, McCarthy Finch, K1) | `nwhitehouse/mike` | 2026-05-01 |
| 10 | [`0d9be7cb`](https://github.com/nwhitehouse/mike/commit/0d9be7cb45c45116bf821bfa2813cf86192903e4) | [ops] Regenerate package-lock.json - fixes Railway npm ci failure | `nwhitehouse/mike` | 2026-05-07 |
| 11 | [`c8bbffb8`](https://github.com/nwhitehouse/mike/commit/c8bbffb8b1cb73d4d00ff9b085e6e5252b39d1d5) | [chore] Add @vercel/analytics to root layout | `nwhitehouse/mike` | 2026-05-07 |

### Commit URLs (for your tooling)

1. https://github.com/nwhitehouse/mike/commit/076add799b024ca30e21a2232636bd5c81e785ef
2. https://github.com/nwhitehouse/mike/commit/f061f75773302114c3be77c81f681f66386332bd
3. https://github.com/nwhitehouse/mike/commit/f3ca06e65bb8364fb29dd5c60124223faa76d0df
4. https://github.com/nwhitehouse/mike/commit/f4a157bac954d29df1d843645f29780b1f8d322d
5. https://github.com/nwhitehouse/mike/commit/a19d145ac0ec8cad73f0f50770219470ffec6ab6
6. https://github.com/nwhitehouse/mike/commit/faaa845854854bc117faa2406e003051979942a1
7. https://github.com/nwhitehouse/mike/commit/58fdae5759d56e17b640e0928aec4d9d0ab033ac
8. https://github.com/nwhitehouse/mike/commit/4d13761c9c14518af8a0368c2eecf76f4cae610c
9. https://github.com/nwhitehouse/mike/commit/79b39c9e940d7aaf0250b6bbfe51c081e1fe20d8
10. https://github.com/nwhitehouse/mike/commit/0d9be7cb45c45116bf821bfa2813cf86192903e4
11. https://github.com/nwhitehouse/mike/commit/c8bbffb8b1cb73d4d00ff9b085e6e5252b39d1d5

## 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.