Fork rebranded to "Michelle"; CORS extended for multi-origin Amplify deploys

easterbrooka renamed the product from "Mike" to "Michelle" across user-facing strings and extended the backend CORS handler to accept a comma-separated list of origins. The rebrand is fork-specific; the CORS pattern is reusable.

brandinginfrastructure

Commit 5bc4211 touches nine files: browser title, logo text in the sidebar, workflow system badge, two column-prompt placeholders, the error page title, and the account page help text. Code identifiers, type names, file names, and comments are intentionally left as "mike" - this is a copy pass only.

The CORS change in backend/src/index.ts replaces the single-origin string with a callback that checks against an array built from FRONTEND_URL split on commas. The motivation is parallel URLs during AWS Amplify testing: the Amplify-managed amplifyapp.com subdomain and a custom domain are both live at the same time, and a single-value FRONTEND_URL would block one of them. The implementation is straightforward - split, trim, filter empties, then allow if origin is in the set or absent (server-to-server).

This commit is a clear signal about deployment trajectory: easterbrooka is rolling mike onto AWS Amplify under a new product name, and the multi-origin CORS was a practical blocker they hit during that rollout.

So what Skip the rebrand strings entirely - that's easterbrooka's product name, not yours. The CORS multi-origin pattern is worth copying if you're running both an Amplify-managed URL and a custom domain simultaneously; it's a few lines in `index.ts`. The commit is more useful as a signal: this fork is in active production deployment on AWS, which means the AWS-specific changes elsewhere (ECS, Secrets Manager, Amplify) have been exercised for real.

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?

Commits in this thread

1 commit from easterbrooka/mike, oldest first. Source extracted verbatim from the harvested git log.

SHA	Subject	Author	Date
`5bc4211a`	Rebrand UI from Mike to Michelle + multi-origin CORS	andrew	2026-05-05	↗ GitHub
commit body Renames the 8 user-facing brand strings (browser title, logo text, sidebar nav, workflow badges, modal placeholders, error page, account page help text). Logo icon is unchanged. Code identifiers (types, file names, comments) intentionally untouched in this pass. Backend CORS now accepts a comma-separated FRONTEND_URL so the amplifyapp.com fallback URL keeps working alongside new custom subdomains during testing. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

SHA

Subject

Author

Date

5bc4211a

Rebrand UI from Mike to Michelle + multi-origin CORS

andrew

2026-05-05

↗ GitHub

commit body

Renames the 8 user-facing brand strings (browser title, logo text,
sidebar nav, workflow badges, modal placeholders, error page,
account page help text). Logo icon is unchanged. Code identifiers
(types, file names, comments) intentionally untouched in this pass.

Backend CORS now accepts a comma-separated FRONTEND_URL so the
amplifyapp.com fallback URL keeps working alongside new custom
subdomains during testing.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-59.md from inside the repo you want the changes in.