# Production observability evidence

Date: 2026-07-28 UTC
Worker: `multideal`
URL: `https://app.multideal.co.il`

## Deploy identity

```text
$ git log --oneline -3
310e3ee18 Fix deploy secrets probe to match name-only endpoint contract
5bab4e45e Retire flowmap capture specs
a02155145 Sync developer checkout after daily scoreboard land

$ git tag --points-at HEAD
v0.1.5
```

GitHub Actions run `30326899145` completed successfully for tag `v0.1.5` and
commit `310e3ee1810e8f972b0154e8d7a4a6c06573bdfc`.

The deploy job log showed:

```text
Run if [ -n "$SENTRY_AUTH_TOKEN" ] && [ -n "$SENTRY_ORG" ] && [ -n "$SENTRY_PROJECT" ]; then
Sentry env vars not set - skipping source map upload
```

Therefore this deploy did not create a Sentry release. The exact release
command, which was not executed, would have used `v0.1.5`.

## Sentry

Live probe attempted with Playwright against the existing production route:

```text
$ pnpm exec playwright screenshot --wait-for-timeout 3000 \
  --save-har /tmp/t11-live.har \
  https://app.multideal.co.il/buy/t11-observability-nonexistent-20260728 \
  /tmp/t11-live.png
Navigating to https://app.multideal.co.il/buy/t11-observability-nonexistent-20260728
Waiting for timeout 3000...
Capturing screenshot into /tmp/t11-live.png
```

Sentry API query for production events:

```text
$ sentry api '/api/0/projects/alexcodeplace/multideal-web/events/?limit=20&query=environment%3Aproduction'
[]
```

Sentry API query for the deploy release:

```text
$ sentry api '/api/0/organizations/alexcodeplace/releases/v0.1.5/'
{
  "detail": "The requested resource does not exist"
}
```

Event ID: none. No event was returned, so environment and release attribution
cannot be claimed and no event ID is fabricated.

Root cause found in source: runtime `initSentry` omitted `environment`; the
build-time Sentry init defaulted missing environment to `development`. Both
now default to `production` and use the runtime `ENVIRONMENT` value when set.
This source fix rides the next orchestrator-created deploy tag.

## Cloudflare Workers analytics

Command used:

```text
$ wrangler tail multideal --format=json --sampling-rate=0.99
```

While the tail was active, Playwright requested `/api/health`. The real tail
output included:

```json
{
  "executionModel": "stateless",
  "outcome": "ok",
  "event": {
    "request": {
      "url": "https://app.multideal.co.il/api/health",
      "method": "GET"
    },
    "response": { "status": 200 }
  }
}
```

This proves a production request was served by Worker `multideal`.

## Validation

```text
pnpm --filter web run typecheck
Result (3212 files):
- 0 errors
- 0 warnings
- 0 hints
```