Replace direct ryu usage with zmij for float formatting

.cargo/config.toml

@@ -3,10 +3,10 @@
 router = "run --package hive-router"
 dev = "run --package qp-dev-cli"
 subgraphs = "run --package subgraphs"
-test_qp = "test --package hive-router-query-planner"
-test_all = "test --workspace --exclude e2e --exclude *-plugin-example"
-test_e2e = "test --package e2e -- --test-threads=5"
-test_qpe = "test --package hive-router-plan-executor"
-test_plugin_examples = "test --package *-plugin-example -- --test-threads=5"
+test_qp = "nextest run --package hive-router-query-planner"
+test_all = "nextest run --workspace --exclude e2e --exclude *-plugin-example"
+test_e2e = "nextest run --package e2e --test-threads 5"
+test_qpe = "nextest run --package hive-router-plan-executor"
+test_plugin_examples = "nextest run --package *-plugin-example --test-threads 5"
 "clippy:fix" = "clippy --all --fix --allow-dirty --allow-staged"
 "router-config" = "run --release -p hive-router-config router-config.schema.json"

.changeset/added_missing_isrepeatable_on_type_directive.md

@@ -0,0 +1,12 @@
+---
+hive-router-query-planner: patch
+hive-router-plan-executor: patch
+hive-router: patch
+node-addon: patch
+---
+
+# Added missing `isRepeatable` on `type __Directive`
+
+The router's introspection schema was resolving `isRepeatable`, but it did not appear in the public (consumer) schema, leading to validation errors when introspection schema was executed through Laboratory. 
+
+This change adds the missing `isRepeatable: Boolean!` to `type __Directive`, according to the [GraphQL introspection spec](https://github.com/graphql/graphql-spec/blob/main/spec/Section%204%20--%20Introspection.md).

.changeset/avoid-include-skip-condition-propagation.md

@@ -0,0 +1,13 @@
+---
+hive-router-query-planner: patch
+hive-router-plan-executor: patch
+hive-router: patch
+node-addon: patch
+---
+
+# Avoid propagating `@include`/`@skip` conditions to unconditional fetches
+
+Fixed query planner condition propagation logic to avoid wrapping unconditional fetches
+in conditional blocks when merging steps. This ensures that fields without directives are
+not incorrectly gated by conditions from other steps, allowing for correct execution of
+queries with mixed conditional and unconditional selections.

.changeset/clever-pandas-tickle.md

@@ -0,0 +1,31 @@
+---
+hive-router-internal: minor
+hive-router-plan-executor: minor
+hive-router: minor
+---
+
+## Improve HTTP server request OTel tracing with client and peer network attributes.
+
+The `http.server` span now includes:
+- `client.address` and `client.port` from a configurable request header
+- `network.peer.address` and `network.peer.port` from the address of the incoming connection
+
+```yaml
+telemetry:
+  client_identification:
+    # Default - use socket peer only
+    ip_header: null
+
+    # Header name - use the left-most valid IP from the header
+    ip_header: x-forwarded-for
+
+    # Trusted proxies - only trust the header when the socket peer is trusted
+    ip_header:
+      name: x-forwarded-for
+      trusted_proxies:
+        - 10.0.0.0/8
+        - 192.168.0.0/16
+```
+
+In trusted proxies scenario, the Router scans the configured header from right to left, skips trusted proxy IP ranges, and records the first non-trusted IP as `client.address`.
+If no valid client IP can be resolved, the Router falls back to the socket peer address.

.changeset/coprocessors.md

@@ -0,0 +1,37 @@
+---
+hive-router: minor
+hive-router-internal: minor
+hive-router-plan-executor: minor
+hive-router-config: minor
+---
+
+## Coprocessors
+
+Introduces Coprocessors as language agnostic way to extend Hive Router.
+
+**Supports coprocessor stages:**
+- `router.request`
+- `router.response`
+- `graphql.request`
+- `graphql.analysis`
+- `graphql.response`
+
+**Stage capabilities:**
+- include selected request/response fields in stage payloads (headers, body, context, and optional SDL depending on stage config)
+- mutate request body/headers/context for downstream pipeline execution
+- short-circuit and return an immediate HTTP response from a stage
+
+**Transport and endpoint support:**
+- `http://` and `unix://` (unix socket domain) endpoints
+- http/1, http/2 and h2c protocols
+
+**Error handling:**
+- coprocessor failures map to server-side failures (500)
+- client-facing GraphQL errors are masked as Internal server error
+- structured error codes are preserved in GraphQL extensions.code
+- detailed coprocessor failure reasons remain in server logs/telemetry only
+
+**Adds coprocessor metrics:**
+- hive.router.coprocessor.requests_total
+- hive.router.coprocessor.duration
+- hive.router.coprocessor.errors_total

.changeset/dynamic-exclusions.md

@@ -0,0 +1,45 @@
+---
+hive-router: minor
+hive-console-sdk: minor
+hive-apollo-router-plugin: minor
+hive-router-internal: patch
+hive-router-plan-executor: patch
+---
+
+# Dynamic Exclusions
+
+## Dynamic Exclusions in Hive Router
+
+Hive Router now supports dynamic exclusions, allowing you to exclude specific requests from usage reporting based on custom logic. This feature is useful for scenarios where you want to skip telemetry for certain requests, such as health checks or specific endpoints.
+
+The previous operation-name list format is still supported for backward compatibility.
+
+### Usage
+```diff
+- exclude: ['ExcludedOp']
++ exclude:
++   expression: '.request.operation.name == "ExcludedOp"'
+```
+
+Both of the following are valid and supported:
+
+```yaml
+# legacy format
+exclude:
+  - ExcludedOp
+
+# dynamic expression format
+exclude:
+  expression: '.request.operation.name == "ExcludedOp"'
+```
+
+The details about expression context is documented in the [Hive Router documentation](https://the-guild.dev/graphql/hive/docs/router/configuration/expressions).
+
+## Dynamic Exclusions in Apollo Router
+
+As in Hive Router, Apollo Router used to support only operation name based exclusions. With the new dynamic exclusions feature, you can now specify custom logic to exclude requests from usage reporting.
+
+
+# New `add_report_with_request` method in Hive Console SDK
+
+In order to support exclusions based on request properties, a new method `add_report_with_request` has been added to the Hive Console SDK. This method allows you to include the request information in the report, which can then be used in the dynamic exclusion logic.

.changeset/enhancement_update_lab_to_016.md

@@ -0,0 +1,9 @@
+---
+hive-router: patch
+---
+
+# enhancement: update lab to 0.1.6
+
+#934 by @mskorokhodov
+
+Update hive lab to 0.1.6 to support new query plan visualization + fetch settings

.changeset/fix_fragments_dropped_in_interface.md

@@ -0,0 +1,25 @@
+---
+hive-router-query-planner: patch
+hive-router-plan-executor: patch
+node-addon: patch
+hive-router: patch
+---
+
+Fix fragments being dropped when multiple inline fragments target the same concrete type within an abstract type fragment.
+
+Previously, when a query contained two or more inline fragments on the same concrete type nested inside an interface or union fragment, only the first fragment's fields were included in the query plan — all subsequent ones were silently dropped.
+
+**Example query that previously returned only `title`:**
+
+```graphql
+query {
+  films {
+    ... on Node {
+      ... on Film { title }
+      ... on Film { director }
+    }
+  }
+}
+```
+
+Both fields are now correctly returned.

.changeset/lab_upgrade.md

@@ -0,0 +1,5 @@
+---
+hive-router: patch
+---
+
+# Upgrade Laboratory to v0.1.7

.changeset/norm_fix.md

@@ -0,0 +1,10 @@
+---
+hive-router-query-planner: patch
+hive-router-plan-executor: patch
+hive-router: patch
+node-addon: patch
+---
+
+# Fix fragment handling
+
+Fix fragment handling for some queries that use reusable fragments with conditional directives

.changeset/operation_kind_enum.md

@@ -0,0 +1,9 @@
+---
+hive-router-plan-executor: patch
+hive-router-internal: patch
+hive-router-query-planner: patch
+hive-router: patch
+node-addon: patch
+---
+
+## Adjustments in operation's kind being Enum and not &'static str

.changeset/release-sync.sh

@@ -3,6 +3,10 @@ set -e
 
 CHANGESET_DIR=".changeset"
 
+# Define your list of target directories here (space-separated)
+# You can also override this by passing arguments to the script: TARGET_DIRS="${@:-.}"
+TARGET_DIRS=". ./apollo-router-workspace"
+
 # Function to extract package names and their corresponding filenames
 get_pkg_file_pairs() {
     grep -rE "^[^:]+: (patch|minor|major)" "$CHANGESET_DIR"/*.md 2>/dev/null | \
@@ -11,40 +15,52 @@ get_pkg_file_pairs() {
 
 echo "🔍 Cascading changes (scoped per file)..."
 
-METADATA=$(cargo metadata --format-version 1 --no-deps)
+for DIR in $TARGET_DIRS; do
+    echo "📂 Processing workspace: $DIR"
+
+    MANIFEST_PATH="$DIR/Cargo.toml"
+
+    if [ ! -f "$MANIFEST_PATH" ]; then
+        echo "⚠️  No Cargo.toml found at $MANIFEST_PATH. Skipping..."
+        continue
+    fi
+
+    # Fetch metadata for the specific directory
+    METADATA=$(cargo metadata --manifest-path "$MANIFEST_PATH" --format-version 1 --no-deps)
 
-while true; do
-    PAIRS=$(get_pkg_file_pairs)
-    NEW_CHANGE_FOUND=false
+    while true; do
+        PAIRS=$(get_pkg_file_pairs)
+        NEW_CHANGE_FOUND=false
 
-    for PAIR in $PAIRS; do
-        PKG=$(echo "$PAIR" | cut -d: -f1)
-        FILE=$(echo "$PAIR" | cut -d: -f2)
+        for PAIR in $PAIRS; do
+            PKG=$(echo "$PAIR" | cut -d: -f1)
+            FILE=$(echo "$PAIR" | cut -d: -f2)
 
-        # Find publishable packages that depend on $PKG
-        DEPENDENTS=$(echo "$METADATA" | jq -r ".packages[] |
-            select(.dependencies[].name == \"$PKG\") |
-            select(.publish == null or (.publish | length > 0)) |
-            .name")
+            # Find publishable packages that depend on $PKG
+            DEPENDENTS=$(echo "$METADATA" | jq -r ".packages[] |
+                select(.dependencies[].name == \"$PKG\") |
+                select(.publish == null or (.publish | length > 0)) |
+                .name")
 
-        for DEP in $DEPENDENTS; do
-            # SCOPED CHECK: Only check if the dependency is missing FROM THIS SPECIFIC FILE
-            if ! grep -qE "^$DEP:" "$FILE" 2>/dev/null; then
-                echo "🔗 In $FILE: $DEP depends on $PKG. Adding..."
+            for DEP in $DEPENDENTS; do
+                # SCOPED CHECK: Only check if the dependency is missing FROM THIS SPECIFIC FILE
+                if ! grep -qE "^$DEP:" "$FILE" 2>/dev/null; then
+                    echo "🔗 In $FILE: $DEP depends on $PKG. Adding..."
 
-                # macOS/BSD compatible sed insertion
-                sed -i '' "2,\$s/^---$/$DEP: patch\\
+                    # macOS/BSD compatible sed insertion
+                    sed -i '' "2,\$s/^---$/$DEP: patch\\
 ---/" "$FILE"
 
-                NEW_CHANGE_FOUND=true
-            fi
+                    NEW_CHANGE_FOUND=true
+                fi
+            done
         done
-    done
 
-    # If no files were modified in this pass, we are done
-    if [ "$NEW_CHANGE_FOUND" = false ]; then
-        break
-    fi
+        # If no files were modified in this pass for this directory, break the while loop
+        if [ "$NEW_CHANGE_FOUND" = false ]; then
+            break
+        fi
+    done
 done
 
-echo "✅ All changesets internally consistent."
+echo "✅ All changesets internally consistent across all directories."

.changeset/replace-ryu-with-zmij.md

@@ -0,0 +1,7 @@
+---
+graphql-tools: patch
+hive-router-plan-executor: patch
+---
+
+Replace direct `ryu` usage with `zmij` for float formatting in `graphql-tools` and `hive-router-plan-executor`.
+

.config/nextest.toml

@@ -0,0 +1,12 @@
+# Minimum recommended version
+nextest-version = "0.9.133"
+
+[profile.default]
+# Show output (stdout/stderr) of failed tests
+failure-output = "immediate"
+# Show output of successful tests only when --no-capture is passed
+success-output = "never"
+# Don't stop on the first failure
+fail-fast = false
+# Mark as slow test after 10s and terminate after 3 retries
+slow-timeout = { period = "10s", terminate-after = 3 }

.gemini/styleguide.md

@@ -116,3 +116,48 @@ We are using `knope` with changesets for declaring changes.
 If you detect a new file in a PR under `.changeset/` directory, please confirm the following rules:
 
 - If a PR touches `config` crate and adds/changes to the `HiveRouterConfig` struct, it must have a `router` changeset that contains a YAML example on how the configuration needs to be used.
+
+---
+
+## Pull Request Reviewing
+
+
+### What to Look For
+
+Code that looks wrong in isolation may be correct given surrounding logic—and vice versa.
+Read the full file to understand existing patterns, control flow, and error handling.
+
+**Bugs** - Your primary focus.
+- Logic errors, off-by-one mistakes, incorrect conditionals
+- If-else guards: missing guards, incorrect branching, unreachable code paths
+- Edge cases: null/empty/undefined inputs, error conditions, race conditions
+- Security issues: injection, auth bypass, data exposure
+- Broken error handling that swallows failures, throws unexpectedly or returns error types that are not caught.
+
+**Structure** - Does the code fit the codebase?
+- Does it follow existing patterns and conventions?
+- Are there established abstractions it should use but doesn't?
+- Excessive nesting that could be flattened with early returns or extraction
+
+**Performance** - Only flag if obviously problematic.
+- O(n²) on unbounded data, N+1 queries, blocking I/O on hot paths
+
+**Behavior Changes** - If a behavioral change is introduced, raise it (especially if it's possibly unintentional).
+
+---
+
+### Before You Flag Something
+
+**Be certain.** If you're going to call something a bug, you need to be confident it actually is one.
+
+- Only review the changes - do not review pre-existing code that wasn't modified
+- Don't flag something as a bug if you're unsure - investigate first
+- Don't invent hypothetical problems - if an edge case matters, explain the realistic scenario where it breaks
+- If you need more context to be sure, use the tools below to get it
+
+**Don't be a zealot about style.** When checking code against conventions:
+
+- Verify the code is *actually* in violation. Don't complain about else statements if early returns are already being used correctly.
+- Some "violations" are acceptable when they're the simplest option.
+- Excessive nesting is a legitimate concern regardless of other style choices.
+- Don't flag style preferences as issues unless they clearly violate established project conventions.