fix(review): runbook owner + next-review pointer (P0 doc drift)

P0 from v1.1 multi-persona code review (Pass 1, doc-drift sweep).
The runbook referenced the old cto-inboxos owner at two locations
that the v1.1 work introduced (the §5.1 runner recovery example
and the §10 RTO breakdown) and had a stale 'Next review' footer
that still pointed at the v1.0 Phase 5 close.

  - docs/operations-runbook.md:319 §5.1 (Gitea runners API URL)
  - docs/operations-runbook.md:792 §10 (Gitea restore push URL)
  - docs/operations-runbook.md:823 footer (Next review pointer)

---ci---
project: inboxos
phase: 1
milestone: v1.1
status: review
---/ci---

docs/operations-runbook.md

@@ -316,7 +316,7 @@ A single stuck job can block the live cron (live jobs have `cancel-in-progress:
 5. **Verify recovery.**
    ```bash
    curl -u "$GITEA_USER:$GITEA_PASS" \
-     https://git.cloudinit.dev/api/v1/repos/cto-inboxos/inboxos/actions/runners
+     https://git.cloudinit.dev/api/v1/repos/jc-capital/inboxos/actions/runners
    ```
    Expect 2 entries with `status: "online"`. Then dispatch `live-pipeline.yml` manually with a small `max_emails` (e.g. `5`) to confirm the end-to-end loop.
 6. **If recurring:** the runner is under-provisioned. Increase its memory limit in `docker/docker-compose.yml` (`mem_limit: 4g` or similar) or move to a host with more RAM.
@@ -789,7 +789,7 @@ section is the **commitment**.
     so the workflows and secrets are back, then NocoDB so
     the module-table IDs are available, then SeaweedFS).
   - 60 min — restore the Gitea bundle and force-push the
-    `cto-inboxos/inboxos` repo. Verify the workflows are
+    `jc-capital/inboxos` repo. Verify the workflows are
     visible at the Gitea UI.
   - 60 min — restore the NocoDB export. The export is a
     JSON dump; the operator opens the NocoDB UI and uses
@@ -820,4 +820,4 @@ in isolation).
 
 ---
 
-*End of runbook. Next review: when Phase 5 (Full Deployment) closes, or when the next failure mode is added to §5. Last verified against the source files cited inline; any divergence is a bug in this document — fix the doc, do not just edit around it.*
+*End of runbook. Next review: after the v1.1 ship (2026-06-08, milestone `milestone/v1.1-initial`), or when the next failure mode is added to §5. Last verified against the source files cited inline; any divergence is a bug in this document — fix the doc, do not just edit around it.*