docs(tip-1096): retarget activation from T12 to T13

[max-digi]

Retargets TIP-1096 activation from T12 to T13, per the current upgrade plan.

Two shifts, applied together so the surrounding text stays consistent. First, T12 becomes T13 for the activation itself: frontmatter protocolVersion, the coordinated T12/Z1 activation section, the tokenEnablementCursorInitialized gate, and the TempoAdvanced / BatchSubmitted event changes. Second, T11 becomes T12 where the spec refers to the fork immediately preceding activation, i.e. the portal runtime being replaced and the requirement that an oversized backlog be settled before the upgrade.

Please sanity-check that second shift. It assumes the spec meant "the fork before activation" rather than "T11 specifically". The Z1 zone hardfork pairing is unchanged.

Related: the three open Cyclops findings on this TIP (CYCLOPS-1578, CYCLOPS-1673, CYCLOPS-1633) were written against the old gate and will need re-checking.

[tempo-voight-kampff]

Hi @dankrad — your review approval was detected by Voight-Kampff but no live Voight-Kampff agent connection received it, so Voight-Kampff sent a push fallback. The push was not approved before the approval window closed. Your review did not count toward this PR.

You can also try approving the PR directly via CLI with

vk approve pr https://github.com/tempoxyz/tempo/pull/7348

Voight-Kampff: dismissing this approval review — it was never confirmed through a Voight-Kampff prompt, so it must not count toward merging this pull request. Re-submit the review and complete the Voight-Kampff prompt if you want this verdict to count.

[tempo-voight-kampff]

Hi @dankrad — your review approval was detected by Voight-Kampff but no live Voight-Kampff agent connection received it, so Voight-Kampff sent a push fallback. The push was not approved before the approval window closed. Your review did not count toward this PR.

You can also try approving the PR directly via CLI with

vk approve pr https://github.com/tempoxyz/tempo/pull/7348

Voight-Kampff: dismissing this approval review — it was never confirmed through a Voight-Kampff prompt, so it must not count toward merging this pull request. Re-submit the review and complete the Voight-Kampff prompt if you want this verdict to count.