diff --git a/docs/project/2026-09-18-upstream-v1.2.0-integration-plan.md b/docs/project/2026-09-18-upstream-v1.2.0-integration-plan.md
index c7a51973..7b6be27d 100644
--- a/docs/project/2026-09-18-upstream-v1.2.0-integration-plan.md
+++ b/docs/project/2026-09-18-upstream-v1.2.0-integration-plan.md
@@ -190,3 +190,19 @@ image publication; any GitOps/deployment promotion.
   branch push runs no image workflow.
 - 2026-09-18: terminal condition met. No further work is authorized in this
   package; every remaining action is a separately gated decision listed above.
+
+## Post-merge receipt (2026-09-18)
+
+PR #26 merged into `main` as merge commit `7d77c61` (never squashed;
+history preserved). Verified at that head:
+
+- CI run `35348841771` on `main` completed **success**, all ten checks green.
+- `Build CodeAPI Images` run `35348841807` completed **success**; the seven
+  images publish tagged `7d77c61` and `main`. This is the standing
+  main-push consequence already recorded before merge.
+- `Release` workflow run on `7d77c61` is **skipped** — the permanent job
+  guard (`if: ${{ false }}`) held. Fork tags and releases remain **0/0**.
+- `origin/main` = `7d77c61`; the patch ledger and the fork policy are
+  consistent with the merged tree.
+- `main` advanced ahead of upstream `v1.2.0` by exactly the fork's own
+  commits, which is the intended fork shape.