# Mission Control rollout rollback

## Purpose

Rollback the LiteSpeed carve-out if the public `/mc` worker/API exposure behaves unexpectedly after the live rollout.

## Scope

This rollback restores the previous LiteSpeed vhost config from the backup created by `apply-mission-control-fix.sh` and reloads LiteSpeed.

It does **not** revert the frontend files in the repo. That is intentional:

- the frontend proxy fix was already validated on the alternate runtime
- the higher-risk live change is the public LiteSpeed carve-out
- restoring the vhost backup is the fastest way to re-protect `/mc` at the public edge

## Command

```bash
cd rollout
I_UNDERSTAND_THIS_RELOADS_SERVICES=YES ./rollback-mission-control-fix.sh /usr/local/lsws/conf/vhosts/altaira.panomity.com/vhost.conf.bak.TIMESTAMP
```

Use the exact backup path printed by `apply-mission-control-fix.sh` during rollout.

## Expected result

After reload, the public `/mc` worker/API carve-outs should be gone again and the protected UI boundary should behave as before.