Several docs pages reference missing static assets and bytecode files

[Gercekkriptocu]

Summary

Several Base Chain spec pages reference /static/... assets and bytecode files that do not appear to exist in the repository.

Missing image references

• docs/base-chain/specs/protocol/fault-proof/index.mdx:20 -> /static/assets/fault-proof.svg
• docs/base-chain/specs/protocol/fault-proof/stage-one/bridge-integration.mdx:29 -> /static/assets/legacy-l2oo-list.png
• docs/base-chain/specs/protocol/fault-proof/stage-one/fault-dispute-game.mdx:116 -> /static/assets/ob-tree.png
• docs/base-chain/specs/protocol/fault-proof/stage-one/fault-dispute-game.mdx:205 -> /static/assets/attack.png
• docs/base-chain/specs/protocol/fault-proof/stage-one/fault-dispute-game.mdx:214 -> /static/assets/defend.png
• docs/base-chain/specs/protocol/fault-proof/stage-one/fault-dispute-game.mdx:221 -> /static/assets/valid-moves.png

Missing bytecode references

• docs/base-chain/specs/upgrades/ecotone/derivation.mdx:129 -> /static/bytecode/ecotone-l1-block-deployment.txt
• docs/base-chain/specs/upgrades/ecotone/derivation.mdx:170 -> /static/bytecode/ecotone-gas-price-oracle-deployment.txt
• docs/base-chain/specs/upgrades/fjord/derivation.mdx:157 -> /static/bytecode/fjord-gas-price-oracle-deployment.txt
• docs/base-chain/specs/upgrades/isthmus/derivation.mdx:36 -> /static/bytecode/isthmus-l1-block-deployment.txt
• docs/base-chain/specs/upgrades/isthmus/derivation.mdx:84 -> /static/bytecode/isthmus-gas-price-oracle-deployment.txt
• docs/base-chain/specs/upgrades/isthmus/derivation.mdx:137 -> /static/bytecode/isthmus-operator-fee-deployment.txt
• docs/base-chain/specs/upgrades/jovian/derivation.mdx:48 -> /static/bytecode/jovian-l1-block-deployment.txt
• docs/base-chain/specs/upgrades/jovian/derivation.mdx:129 -> /static/bytecode/jovian-gas-price-oracle-deployment.txt

Expected behavior

Referenced diagrams and full bytecode files should be present and load correctly.

Suggested fix

Either:

1. Add the missing static files to the expected location, or
2. Update the references to the correct existing asset paths, or
3. Remove or replace the links if these files are no longer intended to be published.

Impact

This affects technical specification pages where diagrams and full bytecode links are important for understanding and verification.