# Core Upstream

`services/core/` is derived from the Mattermost server repository.

- Source: `https://github.com/mattermost/mattermost.git`
- Branch: `master`
- Baseline tag: `v11.4.2`
- Baseline commit: `bcf511968217cd0f65cbead926e03260bfcd1011`
- Snapshot date: `2026-05-30`
- Snapshot source: `.upstream/mattermost/mattermost/`
- Snapshot target: `services/core/`
- Tracked components: Mattermost server and bundled webapp from the same
  upstream repository snapshot.

## Patch Boundary

Keep product-specific changes small and easy to compare against this baseline.
Prefer compose files, docs, wrapper scripts, config, and isolated compatibility
patches over changes inside upstream-owned server or webapp code.

Do not use `services/core` for broad nexo product UI work, package-wide rename,
or deep fork behavior. If an exception is needed, record the upstream feature
classification, changed paths, rollback path, and smoke evidence with the
snapshot update.

## Update Gate

A core snapshot update must stay separate from Mattermost mobile app and
push-proxy updates. Before a merge request, record the selected upstream commit,
review the snapshot diff, run the relevant core compose smoke, and classify any
failure as `server`, `webapp`, `push-proxy`, `SDK contract`, or `infra`.

When runtime images change, keep image tag and digest evidence in
`docs/runtime-image-validation.md`; the source baseline remains this file.