Update all docs

docs/knowledge/rpc/jip2-gav.md

@@ -6,7 +6,7 @@ sidebar_position: 1
 slug: /advanced/rpc/jip2-node-rpc
 ---
 
-(source https://hackmd.io/@polkadot/jip2 from 2025-09-19)
+(source https://hackmd.io/@polkadot/jip2 from 2025-12-04)
 
 <!-- The raw MD from above will be downloaded and appended -->
 # JIP-2: Node RPC

docs/knowledge/simple-networking/spec.md

@@ -5,7 +5,7 @@ sidebar_position: 1
 slug: /knowledge/advanced/simple-networking/spec
 ---
 
-(source https://github.com/zdave-parity/jam-np/blob/main/simple.md from 2025-09-19)
+(source https://github.com/zdave-parity/jam-np/blob/main/simple.md from 2025-12-04)
 
 <!-- The raw MD from above will be downloaded and appended -->
  # JAM Simple Networking Protocol (JAMNP-S)
@@ -180,9 +180,12 @@ Core Index = u16
 
 Ed25519 Signature = [u8; 64]
 
+Segments-Root = [u8; 32]
 Erasure-Root = [u8; 32]
 Shard Index = u16
+Work-Package Bundle = [u8] (Encoded as in GP)
 Bundle Shard = [u8]
+Segment = [u8; 4104]
 Segment Shard = [u8; 4104 / R] (R is the recovery threshold; 342 with 1023 validators, 2 with 6)
 ```
 
@@ -362,8 +365,9 @@ Submission of a work-package from a builder to a guarantor.
 The second message should contain all the extrinsic data referenced by the work-package, formatted
 as in work-package bundles, which are defined in the Computation of Work Results section of the GP.
 
-Note that the content of imported segments _should not_ be sent; it is the responsibility of the
-receiving guarantor to fetch this data from the availability system.
+Note that if the builder can provide the content of imported segments, CE 146 should be used to submit 
+the full work-package bundle. Otherwise it is the responsibility of the receiving guarantor to fetch 
+this data from the availability system.
 
 ```
 Work-Package = As in GP
@@ -377,6 +381,31 @@ Builder -> Guarantor
 <-- FIN
 ```
 
+### CE 146: Work-package bundle submission
+
+Submission of a complete work-package bundle from a builder to a guarantor.
+
+Note that the bundle parts are sent in separate messages to allow for authorizing the work-package before reading the rest of the bundle.
+
+The import proof corresponds to $\mathit{J}$ as defined in the gray paper.
+
+```
+Work-Package = As in GP
+Extrinsic = [u8]
+Import-Proof = len++[Hash]
+Segments-Root Mappings = len++[Work-Package Hash ++ Segments-Root]
+
+Builder -> Guarantor
+
+--> Core Index ++ Segments-Root Mappings
+--> Work-Package
+--> [Extrinsic] (Message size should equal sum of extrinsic data lengths)
+--> [Segment] (All imported segments)
+--> [Import-Proof] (Import proofs for all imported segments)
+--> FIN
+<-- FIN
+```
+
 ### CE 134: Work-package sharing
 
 Sharing of a work-package between guarantors on the same core assignment.
@@ -406,9 +435,7 @@ mappings cannot be verified, the guarantor may, at their discretion, either refu
 work-package or blindly trust the mappings.
 
 ```
-Segments-Root = [u8; 32]
 Segments-Root Mappings = len++[Work-Package Hash ++ Segments-Root]
-Work-Package Bundle = As in GP
 
 Guarantor -> Guarantor
 
@@ -541,6 +568,21 @@ Auditor -> Assurer
 <-- FIN
 ```
 
+### CE 147: Bundle request
+
+Request for a work-package bundle.
+
+This protocol should be used by auditors to request work-package bundle from guarantors
+for auditing. In case the guarantor fails to provide the valid bundle, the auditor should fall back to recovering the bundle with CE 138
+```
+Auditor -> Guarantor
+
+--> Erasure-Root
+--> FIN
+<-- Work-Package Bundle
+<-- FIN
+```
+
 ### CE 139/140: Segment shard request
 
 Request for one or more segment shards.
@@ -594,6 +636,31 @@ Guarantor -> Assurer
 <-- FIN
 ```
 
+### CE 148: Segment request
+
+Request for one or more segments.
+
+This protocol should be used by guarantors or builders to request import segments from other guarantors in order
+to complete work-package bundles.
+
+The number of segments requested in a single stream should not exceed $W_M$ ($W_M = 3072$,
+this constant is defined in the GP).
+
+If the guarantor fails to return the valid data, the requestor should fall back to using CE 139/140
+
+```
+Segment Index = u16
+Import-Proof = len++[Hash]
+
+Guarantor -> Guarantor
+
+--> [Segments-Root ++ len++[Segment Index]]
+--> FIN
+<-- [Segment]
+<-- [Import-Proof]
+<-- FIN
+```
+
 ### CE 141: Assurance distribution
 
 Distribution of an availability assurance ready for inclusion in a block.
@@ -654,7 +721,7 @@ is expected to be checked against a different database.
 ```
 Preimage = [u8]
 
-Node -> Node
+Validator -> Node
 
 --> Hash
 --> FIN

docs/knowledge/testing/pvm/host-call-log.md

@@ -4,7 +4,7 @@ sidebar_label: Log Host Call
 sidebar_position: 1
 ---
 
-(source https://hackmd.io/@polkadot/jip1 from 2025-09-19)
+(source https://hackmd.io/@polkadot/jip1 from 2025-12-04)
 
 <!-- The raw MD from above will be downloaded and appended -->
  # JIP-1: Debug message host call

package.json

@@ -17,21 +17,21 @@
     "convert-yaml": "node scripts/yml-to-md.js"
   },
   "dependencies": {
-    "@docusaurus/core": "3.8.1",
-    "@docusaurus/preset-classic": "3.8.1",
+    "@docusaurus/core": "3.9.2",
+    "@docusaurus/preset-classic": "3.9.2",
     "@mdx-js/react": "^3.1.1",
     "clsx": "^2.0.0",
     "prism-react-renderer": "^2.3.0",
-    "react": "^19.1.1",
-    "react-dom": "^19.1.1",
+    "react": "^19.2.1",
+    "react-dom": "^19.2.1",
     "rehype-katex": "^7.0.1",
     "remark-math": "^6.0.0"
   },
   "devDependencies": {
-    "@docusaurus/module-type-aliases": "3.8.1",
-    "@docusaurus/tsconfig": "3.8.1",
-    "@docusaurus/types": "3.8.1",
-    "typescript": "~5.9.2"
+    "@docusaurus/module-type-aliases": "3.9.2",
+    "@docusaurus/tsconfig": "3.9.2",
+    "@docusaurus/types": "3.9.2",
+    "typescript": "~5.9.3"
   },
   "browserslist": {
     "production": [