Keep only EVM parity matrix in docs

Author: monty-sei

.gitignore

@@ -4,6 +4,7 @@
 packages/*/coverage
 
 examples/
+.internal/
 
 # compiled output
 dist

docs/docs.json

@@ -83,14 +83,9 @@
 			},
 			{
 				"dropdown": "EVM Parity",
-				"description": "Compatibility matrix and execution plan",
-				"icon": "check-double",
-				"pages": [
-					{
-						"group": "Program",
-						"pages": ["evm-parity/plan", "evm-parity/matrix", "evm-parity/rpc-conformance", "evm-parity/issue-sla"]
-					}
-				]
+				"description": "Compatibility matrix",
+				"icon": "table",
+				"pages": ["evm-parity/matrix"]
 			},
 			{
 				"dropdown": "@sei-js/sei-global-wallet",

docs/evm-parity/issue-sla.mdx

@@ -51,7 +51,3 @@ This matrix tracks EVM developer workflows rather than package export counts. A
 ## Scoring Rule
 
 The public coverage score will start once conformance tests land. Only core rows count toward the >=95% target. `Not core` and `Network-limited` rows remain visible so developers understand the boundary, but they do not lower the SDK score when the behavior is intentional and documented.
-
-## Source Data
-
-The editable matrix source is stored at `/docs/evm-parity/matrix.json`.