Link the last two pinned divergences to their tracking entries

The unrecognized-resultType and scope-aggregation divergences gained
tracking entries after their pins landed; wire the issue fields so the
fixer trail is complete for every pinned divergence in the manifest.

Author: maxisbey

tests/interaction/_requirements.py

@@ -3853,6 +3853,7 @@ def __post_init__(self) -> None:
                 "surfaced on the returned result unchanged -- on both eras (the in-code TODO "
                 "in src/mcp/server/runner.py records the missing rejection)."
             ),
+            issue="L117",
         ),
     ),
     "mrtr:input-responses:invalid-rejected": Requirement(
@@ -5404,6 +5405,7 @@ def __post_init__(self) -> None:
                 "hosting:auth:scope-403 divergence) -- a client missing several scopes is "
                 "challenged one scope per round trip."
             ),
+            issue="L118",
         ),
     ),
     "hosting:auth:scope:no-offline-access": Requirement(