Trim stale status comments in tz5 pubkey tests

Drop the now-false "RED until the fix lands" / "currently stop at BLpk"
status notes from the tz5/mdpk forging tests (the fix has landed; they
are green). Keep the evergreen "why" (reveals embed an mdpk pubkey
forged via forge_public_key, tag \x04).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: Wizard1209

tests/unit_tests/test_michelson/test_forge_address.py

@@ -29,10 +29,8 @@ def test_forge_unforge_tz5_key_hash_only(self):
 
 
 class TestForgePublicKey:
-    # GAP-1: tz5 / ML-DSA-44 reveals embed an `mdpk` public key, which is forged
-    # by forge_public_key (NOT forge_address). These currently stop at BLpk (tag
-    # \x03) and raise — RED until the forge_public_key/unforge_public_key fix
-    # (add `mdpk` -> tag \x04) lands.
+    # tz5 / ML-DSA-44 reveals embed an `mdpk` public key, forged by
+    # forge_public_key (tag \x04) — a path distinct from forge_address.
     def test_forge_unforge_tz5_mdpk_round_trip(self):
         # synthetic ML-DSA-44 public key: exactly 1312 bytes of mdpk payload
         payload = bytes(range(256)) * 5 + bytes(32)

tests/unit_tests/test_operation/test_forging.py

@@ -35,9 +35,8 @@ def test_operation_hash_is_correct(self, opg_hash):
         self.assertEqual(opg_hash, res)
 
     def test_forge_reveal_with_tz5_account(self):
-        # GAP-1: a tz5 reveal embeds an ML-DSA-44 (mdpk) public key, so
-        # forge_reveal -> forge_public_key must handle it. RED until the
-        # forge_public_key fix (mdpk -> tag \x04) lands.
+        # a tz5 reveal embeds an ML-DSA-44 (mdpk) public key, so
+        # forge_reveal -> forge_public_key must tag it \x04.
         payload = bytes(range(256)) * 5 + bytes(32)
         content = {
             'kind': 'reveal',