Generated database-e2e harness for opto-sync.
Profile: database-e2e
Source organization: opto-sync
- Supabase auth
- RLS
- realtime
- offline reconcile
| Source | Commit | Branch observed |
|---|---|---|
opto-sync/opto-sync-clients |
fdf4fad9e2e841f66ecee19fca3b408d5fa7fa4c |
main |
opto-sync/opto-sync-e2e |
0326de7d62acf94af933a0a1dae8a004b34017db |
main |
| Mode | Source | Manager | Path/subdir |
|---|---|---|---|
| none | - | - | - |
The pull-request workflow validates the generated contract without cross-organization credentials. Product-specific files outside the generated file set are preserved and must add executable assertions without weakening the base contract. Full integration is intentionally release-gated until required source repositories and organization read credentials are present. The generic protected lane reports source-access status only; source certification requires a product-specific executable overlay. A skipped integration job is not source certification. Run the profile-specific checks recorded in test-plan.json after materializing the submodule, Zed, or native-package lane.