# Platform Invite Router Core Baseline

## Why this note exists

The platform invite router train publishes a new `@elevasis/core` auth schema export for the narrow organization auth-config endpoint used by the backend invite router.

## Applies to

- Template-derived projects that consume `@elevasis/core`.
- Project `core/package.json` and `operations/package.json` package baselines after the core release.

## Required actions

- Accept the `@elevasis/core` dependency baseline update after the core publish stage.
- Do not add tenant app-origin routing code to template projects from this train; invitation routing remains platform API behavior.
- Keep tenant app WorkOS login routes accepting `invitation_token` when project-specific launch work has already added that route support.

## Verification

- Run `pnpm sync:verify` after manifest-scoped external sync.
- For projects receiving the baseline, run project-local checks required by the sync plan.

## Not handled by /git-sync

- Publishing `@elevasis/core`.
- Updating package baselines after publish.
- WorkOS production application configuration.
- Per-tenant invitation smoke tests.
