# LineUp France - Ready For Prod Validation - 2026-03-12

## Decision

Current status: `READY FOR PROD VALIDATION`

This is not the final production go-live decision.
This means the codebase has cleared the local validation bar on the full critical path and is ready for controlled production validation.

## Validation basis

### 1. BO real local E2E

Command:

```bash
cd /Users/gsent/Documents/app
./scripts/e2e_local_lineup.sh
```

Result:
- `38 passed, 0 failed`

Covers:
1. mission creation
2. multi-candidature
3. single liner selection
4. payment confirmation
5. mission chat
6. mission timeline
7. wallet settlement after queue

### 2. client_app real local API E2E

Command:

```bash
cd /Users/gsent/Documents/untitled2/apps/client_app
./scripts/e2e_real_client_api.sh
```

Result:
- `All tests passed!`

Covers:
1. real client login
2. mission creation
3. double liner application
4. liner selection
5. payment
6. mission track
7. mission message
8. payment history

### 3. liner_app real local API E2E

Command:

```bash
cd /Users/gsent/Documents/untitled2/apps/liner_app
./scripts/e2e_real_liner_api.sh
```

Result:
- `All tests passed!`

Covers:
1. real liner login
2. published mission visibility
3. liner application
4. client selection + confirmation
5. mission chat
6. mission proof
7. mission completion flow
8. wallet + history after queue

### 4. Unified local validation suite

Command:

```bash
cd /Users/gsent/Documents/app
./scripts/local_validation_suite.sh
```

Result:
- `Suite complete: OK`

This is now the reference local validation command before any controlled production validation.

## What is now considered validated locally

1. BO + client + liner are synchronized on the core mission lifecycle
2. multi-candidature ends with exactly one selected liner
3. payment confirmation is coherent with selected liner
4. liner can progress the mission until completion
5. client and liner both see mission chat and track data
6. mission proof submission is functional in the local integrated flow
7. wallet credit appears after queue processing

## What is still not proven until production validation

1. production queue behavior under the real infra
2. real device geolocation behavior
3. real device push notification routing
4. provider-backed payment and payout behavior in prod
5. production storage behavior for uploads and moderation artifacts

## Production validation gate

Move from `READY FOR PROD VALIDATION` to final `GO / NO-GO` only after:

1. `preflight_cpanel.sh` passes
2. `smoke_web.sh` passes
3. `prod-e2e-run-sheet.md` is executed completely
4. one full client -> liner -> BO mission run succeeds in production
5. no critical issue remains on wallet, payment, mission start/finish, or geolocation

## Recommended execution order

1. run `./scripts/local_validation_suite.sh`
2. run prod preflight and smoke
3. execute `docs/qa/prod-e2e-run-sheet.md`
4. issue final `GO / NO-GO`

## Source references

- `scripts/e2e_local_lineup.sh`
- `scripts/local_validation_suite.sh`
- `docs/qa/prod-smoke-checklist.md`
- `docs/qa/prod-e2e-client-liner-bo-checklist.md`
- `docs/qa/prod-e2e-runbook-copy-paste.md`
- `docs/qa/prod-e2e-run-sheet.md`
- `docs/qa/validation-status-2026-03-12.md`
- `docs/qa/go-no-go-summary-2026-03-12.md`
- `docs/qa/executive-go-no-go-2026-03-12.md`
