# REAL evidence — PR #17 self-block (no zombie pattern)

This is the **first real GitHub-side evidence** that the auto-merge controller refuses to merge its own PR while the chairman is the gatekeeper.

## Timeline (UTC)
- `00:57:55` — PR #17 opened against main; auto-merge workflow triggered.
- `00:57:55.628` — Controller fetched `main` HEAD via `gh api /repos/.../branches/main`.
- `00:57:56.301` — Controller listed open PRs (`?state=open&base=main`).
- `00:57:56.546` — Controller pulled check-runs for head SHA `4db7dfed...`.
- `00:57:56.875` — Controller decision:
  ```
  [skip] PR #17 — missing=['ci/guard', 'gemini-review-gate', 'guard',
                            'merge-safety-check']
                  non_success=['hidden-path-audit', 'lock-in-check', 'qc-check']
  ```
  (NB: hidden-path-audit/lock-in-check were still in-progress, qc-check actually
   FAIL — pre-existing CI bug uses absolute /home/jay/workspace path that
   doesn't exist on the GitHub runner.)
- `00:57:56.876` — Controller attempted to add `auto-merge-blocked` label.
- `00:57:57.636` — Cycle done: `merged=0 skipped=1 cancelled=0 errors=0`.

## Why this matters
- task-2440 chairman explicitly named the zombie pattern (PR #14/#15 self-merged by bot).
- The auto-merge workflow runs on `pull_request: opened` — meaning the controller has the opportunity to self-merge **the very PR that introduces it**.
- Result: `merged=0` — the controller honoured every gate against itself. ★
- `mergeStateStatus=BLOCKED` (per `pr-status.json`) confirms GitHub-side ruleset would also have rejected any attempt.

## Files
- `controller-run-25295918976.txt` — verbatim log lines from the GitHub Actions run.
- `pr-status.json` — `gh pr view 17` snapshot at first cycle completion.
- `main-head-after-controller-cycle.txt` — main HEAD after the controller cycle (unchanged from before).

## What happens next
PR #17 stays open until the chairman manually merges it (`manual_after_full_enforcement`). After that first merge, the next cron `*/5` cycle will produce true A1 evidence on the next PR that satisfies all 8 gates.