site: the drift table no longer promises byte-identical generated stacks

Generated code is a reference helper you own (ADR-0034 Amendment 3), so the conformance
corpora cannot guarantee that a TS stack and a Java stack agree byte-for-byte; they hold
every port to one reading of the model. What catches a stale consumer is that port's
verify failing the build that has not regenerated. The row now says that.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01M1mRRB1K2WdYy82kntMQdx

Author: claude

www/index.html

@@ -233,7 +233,7 @@ <h2 class="section-label">Context is advisory. This is not: drift breaks the bui
           <tr>
             <td>TS service renames a column; the Java consumer's POJO mapping silently goes stale</td>
             <td>Boundary drifts. Cross-service schema mismatch in production.</td>
-            <td>Same metadata regenerates both stacks. Conformance corpus guarantees they agree byte-for-byte.</td>
+            <td>Same metadata regenerates both stacks. Each port's <code>verify</code> fails the build that has not regenerated, and the conformance corpora hold every port to one reading of the model.</td>
           </tr>
         </tbody>
       </table>