docs(readme): point the dogfooding link at the full capability deck

Link engine-deck.pdf (the multi-page deck with live charts and the real
comparative-benchmark pages) instead of the single-page banner, so the
reader lands on the richer self-rendered document. Refresh the committed
deck to the current render and drop the now-unused engine-banner.pdf.

Author: DemchaAV

README.md

@@ -39,7 +39,7 @@
 </p>
 
 <p align="center">
-  <sub>☝ This banner is itself a GraphCompose document — <a href="./assets/readme/examples/engine-banner.pdf"><b>view the source PDF</b></a>, rendered by <a href="./examples/src/main/java/com/demcha/examples/flagships/EngineDeckExample.java"><code>EngineDeckExample</code></a>. The engine renders its own marketing.</sub>
+  <sub>☝ This banner is itself a GraphCompose document — <a href="./assets/readme/examples/engine-deck.pdf"><b>view the full capability deck (PDF)</b></a>, rendered by <a href="./examples/src/main/java/com/demcha/examples/flagships/EngineDeckExample.java"><code>EngineDeckExample</code></a>: live charts and real comparative benchmarks, all drawn by the engine. It renders its own marketing.</sub>
 </p>
 
 ## Why GraphCompose