fix: regenerate client from updated forge-dashboard spec

openapi/SPEC_COMMIT

@@ -1 +1 @@
-b9605dace2ec3df8fd3f2613046e8810e69c8c47
+27aaabb38b9d89b9ce83fa9904e988d7e96db114

openapi/openapi.yaml

@@ -4228,10 +4228,10 @@ components:
         were skipped. It never exceeds `passed`: it is inside `passed`, not
         beside it, so `passed` still counts every check that needs nothing more
         and the four states still add up to the checks the pipeline lists. The
-        server always sends it; a client that may talk to an older server
-        reads a missing one as none. A neutral or bare completed check is passed without
-        being skipped. A client that draws the two side by side must subtract
-        `skipped` from `passed` for the passed figure, or a skipped check is
+        server always sends it, which is why it is required; a client that may
+        talk to an older server may read a missing one as zero. A neutral or bare
+        completed check is passed without being skipped. A client that draws the
+        two side by side must subtract `skipped` from `passed` for the passed figure, or a skipped check is
         counted twice, and a pipeline where every passed check was skipped can
         read as skipped.
 

src/forge_dashboard/_generated/models/check_counts.py

@@ -47,10 +47,10 @@ class CheckCounts:
     were skipped. It never exceeds `passed`: it is inside `passed`, not
     beside it, so `passed` still counts every check that needs nothing more
     and the four states still add up to the checks the pipeline lists. The
-    server always sends it; a client that may talk to an older server
-    reads a missing one as none. A neutral or bare completed check is passed without
-    being skipped. A client that draws the two side by side must subtract
-    `skipped` from `passed` for the passed figure, or a skipped check is
+    server always sends it, which is why it is required; a client that may
+    talk to an older server may read a missing one as zero. A neutral or bare
+    completed check is passed without being skipped. A client that draws the
+    two side by side must subtract `skipped` from `passed` for the passed figure, or a skipped check is
     counted twice, and a pipeline where every passed check was skipped can
     read as skipped.
 

src/forge_dashboard/_generated/models/linked_pull_request.py

@@ -66,10 +66,10 @@ class LinkedPullRequest:
                 were skipped. It never exceeds `passed`: it is inside `passed`, not
                 beside it, so `passed` still counts every check that needs nothing more
                 and the four states still add up to the checks the pipeline lists. The
-                server always sends it; a client that may talk to an older server
-                reads a missing one as none. A neutral or bare completed check is passed without
-                being skipped. A client that draws the two side by side must subtract
-                `skipped` from `passed` for the passed figure, or a skipped check is
+                server always sends it, which is why it is required; a client that may
+                talk to an older server may read a missing one as zero. A neutral or bare
+                completed check is passed without being skipped. A client that draws the
+                two side by side must subtract `skipped` from `passed` for the passed figure, or a skipped check is
                 counted twice, and a pipeline where every passed check was skipped can
                 read as skipped.
 

src/forge_dashboard/_generated/models/main_branch.py

@@ -85,10 +85,10 @@ class MainBranch:
                 were skipped. It never exceeds `passed`: it is inside `passed`, not
                 beside it, so `passed` still counts every check that needs nothing more
                 and the four states still add up to the checks the pipeline lists. The
-                server always sends it; a client that may talk to an older server
-                reads a missing one as none. A neutral or bare completed check is passed without
-                being skipped. A client that draws the two side by side must subtract
-                `skipped` from `passed` for the passed figure, or a skipped check is
+                server always sends it, which is why it is required; a client that may
+                talk to an older server may read a missing one as zero. A neutral or bare
+                completed check is passed without being skipped. A client that draws the
+                two side by side must subtract `skipped` from `passed` for the passed figure, or a skipped check is
                 counted twice, and a pipeline where every passed check was skipped can
                 read as skipped.
 

src/forge_dashboard/_generated/models/pull_request.py

@@ -88,10 +88,10 @@ class PullRequest:
                 were skipped. It never exceeds `passed`: it is inside `passed`, not
                 beside it, so `passed` still counts every check that needs nothing more
                 and the four states still add up to the checks the pipeline lists. The
-                server always sends it; a client that may talk to an older server
-                reads a missing one as none. A neutral or bare completed check is passed without
-                being skipped. A client that draws the two side by side must subtract
-                `skipped` from `passed` for the passed figure, or a skipped check is
+                server always sends it, which is why it is required; a client that may
+                talk to an older server may read a missing one as zero. A neutral or bare
+                completed check is passed without being skipped. A client that draws the
+                two side by side must subtract `skipped` from `passed` for the passed figure, or a skipped check is
                 counted twice, and a pipeline where every passed check was skipped can
                 read as skipped.