docs(T07): correct the premise -- key-cape is not waiting

T07's note and the registration doc said publishing would close
KEY-WP-0013-T02, blocked since 2026-09-08. Checked against key-cape: T02 is
done, T05 (which actually held the human registration) is done, and key-cape
closed KEY-WP-0030, a follow-up this repo prompted. The issuer side of the gap
that created this repository is already discharged.

Submitting the registration closes INFD-WP-0001-T07, not a key-cape task.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EJbh7o7UWF4tQ5jxygnNGu

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 2072522@bnt-lap001
Assistant-Session: 46173adf-7302-4ede-99d6-963b61359928

workplans/INFD-WP-0001-founding-specs-and-approver-ui-ownership.md

@@ -398,6 +398,17 @@ not affect the registration — `key-cape` matches the redirect URI as a string
 `/authorize` and never fetches it. Evidence:
 `railiance-apps/docs/informed-decision-origin.md`.
 
+2026-09-11 — **correction to this task's premise.** This note and the
+registration doc previously said publishing would "close `KEY-WP-0013-T02`,
+blocked since 2026-09-08". Checked against `key-cape` rather than against this
+file's own prose: `KEY-WP-0013-T02` is `done`, and so is `KEY-WP-0013-T05`, the
+task that actually held the human registration. `key-cape` did not wait — it
+published the contract shape from its side (accepting the `approval:read` scope
+gap as ours-was-right, documenting the `assurance` object, and fixing `at` from
+mint time to authentication time), and closed `KEY-WP-0030`, a follow-up this
+repo prompted. The gap that created this repository is discharged on the issuer
+side already. What is left is this repo submitting its half.
+
 Every input this task owns is now fixed and real.
 `docs/keycape-client-registration.md` is ready to submit. **The task stays
 `progress` until the remaining acceptance criteria are met, which are not