Overview - Ai

aiWorkspace

CI Pipeline Executions
- Filtered
Runs
Demo

Insights

Compare tasks
Analytics

Overview

ai

Loading workspace stats

Loading workspace insights...

Statistics interval

7 days30 days

Latest CI Pipeline Executions

Filter

Fuzzy

Sort by

© 2026 - Nx Cloud

Terms of Service Privacy Policy Changelog Status Docs Contact Nx Cloud Pricing Company @NxDevTools

aiWorkspace

Average execution time

8m 40s

610 CI pipeline executions

Computation time saved

7d 19h

Cache hit rate

55%

Time to Green

19m 58s

Was 23m 52s, improved by 16%

Succeeded
main
592c72c2 feat(ai): add AG-UI activity messages and optional ActivityStore (#1323) * feat(ai): introduce AG-UI activity messages with snapshot and delta handling - Added frontend-only activity messages: ACTIVITY_SNAPSHOT and ACTIVITY_DELTA. - Updated StreamProcessor to handle these new message types without affecting model input. - Integrated fast-json-patch for applying updates to activity content. - Enhanced type definitions and tests to ensure proper functionality and type safety for activity messages. - Updated pnpm-lock.yaml to include fast-json-patch dependency. * feat(ai-client): expose AG-UI activity messages in chat client - Introduced support for 'activity' role in UIMessage, allowing frontend-only activity messages to be appended without affecting model input. - Updated type definitions to include ActivityPart and modified relevant interfaces. - Enhanced chat client logic to handle activity messages appropriately, ensuring they are retained in the transcript but not sent to the model. - Added tests to verify the correct handling and integration of activity messages in various scenarios. * feat(ai): implement AG-UI ActivityMessage handling in snapshots - Introduced emission of AG-UI ActivityMessage on MESSAGES_SNAPSHOT events. - Updated StreamProcessor to retain omitted activity rows when a snapshot replaces the transcript. - Enhanced uiMessagesToWire function to include activity messages based on the new includeActivity option. - Added tests to ensure correct handling of activity messages during persistence and snapshot processes. * feat(ai): add optional ActivityStore for AG-UI activity persistence - Introduced an ActivityStore to enable saving and reconstructing AG-UI activity without affecting the MessageStore. - Updated client persistence documentation to reflect the new activity storage capabilities. - Enhanced tests to validate the integration and functionality of the ActivityStore within the existing persistence framework. * refactor(ai): streamline message rendering and improve activity handling - Updated the Messages component to skip rendering for 'activity' role messages, enhancing performance and clarity. - Refactored message part rendering logic for better readability and maintainability. - Adjusted type definitions and imports for consistency across the codebase. - Improved handling of JSON patching in activity records to ensure accurate updates. * test(e2e): add AG-UI activity harness and Playwright coverage Add a provider-free /activity-test route that exercises live ACTIVITY_SNAPSHOT/DELTA, MESSAGES_SNAPSHOT hydrate, and the client send filter so activity never goes back as model input. * fix(ai): harden activity handling and add reconstruct E2E + Angular UI Guard ACTIVITY_SNAPSHOT from replacing non-activity messages, reject mismatched ACTIVITY_DELTA types and invalid root patch results, and merge activity metadata on live snapshot/delta. Add reconstructChat E2E via ActivityStore and render activity rows in the Angular chat example (PLAN checklist + JSON fallback). * refactor(ai): replace EventType constants with string literals in stream processor tests Updated the stream processor tests to use string literals for ACTIVITY_SNAPSHOT and ACTIVITY_DELTA instead of EventType constants for improved clarity and consistency. This change also applies to the test-utils file and the e2e activity test route, ensuring uniformity across the codebase. * fix(StreamProcessor): improve handling of omitted activity messages in snapshots * fix(ai-persistence): page activity rows and keep activity saves best-effort - reconstructChat: a thread with activity loads in full, interleaves, then pages, so each activity shows on one page at the right place. - withPersistence: save activity after the message, run, and interrupt writes, and ignore activity store errors. - ActivityRecord keeps metadata in both directions. - ChatMiddlewareContext.activities is optional. - Add a changeset for ai-byteplus and a migration note for role 'activity'. * docs(persistence): document the activities store and activity rows * fix(ai, ai-persistence): keep stored activity rows and use the AG-UI activity types - Do not save an empty activity list from the pending-turn snapshot. - Merge inbound activity rows into the stored rows by id. - Drop the activity rows of a turn that a reload replaces. - Page through the store when a cursor is not a UI message id. - Log a failed activity save. Skip the save when the context has no activities. - Derive the activity event, part, and record types from @ag-ui/core. - Send activity metadata in MESSAGES_SNAPSHOT. - Warn on a delta for an unknown id and on a text and activity id collision. - Accept the activity role in the event-client and devtools message types. - Document the activities skip for the conformance suite. * fix(ai): accept an inbound AG-UI ActivityMessage and keep its subagentRunId - Collect an inbound message in the AG-UI ActivityMessage shape, not only a UIMessage with an activity part. - Keep subagentRunId from an inbound message and from an activity event on the stored record. - Send subagentRunId on the ActivityMessage in MESSAGES_SNAPSHOT. --------- Co-authored-by: Alem Tuzlak <t.zlak@hotmail.com> Co-authored-by: Tom Beckenham <34339192+tombeckenham@users.noreply.github.com>
by Harshdeep ...
Succeeded
main
592c72c2 feat(ai): add AG-UI activity messages and optional ActivityStore (#1323) * feat(ai): introduce AG-UI activity messages with snapshot and delta handling - Added frontend-only activity messages: ACTIVITY_SNAPSHOT and ACTIVITY_DELTA. - Updated StreamProcessor to handle these new message types without affecting model input. - Integrated fast-json-patch for applying updates to activity content. - Enhanced type definitions and tests to ensure proper functionality and type safety for activity messages. - Updated pnpm-lock.yaml to include fast-json-patch dependency. * feat(ai-client): expose AG-UI activity messages in chat client - Introduced support for 'activity' role in UIMessage, allowing frontend-only activity messages to be appended without affecting model input. - Updated type definitions to include ActivityPart and modified relevant interfaces. - Enhanced chat client logic to handle activity messages appropriately, ensuring they are retained in the transcript but not sent to the model. - Added tests to verify the correct handling and integration of activity messages in various scenarios. * feat(ai): implement AG-UI ActivityMessage handling in snapshots - Introduced emission of AG-UI ActivityMessage on MESSAGES_SNAPSHOT events. - Updated StreamProcessor to retain omitted activity rows when a snapshot replaces the transcript. - Enhanced uiMessagesToWire function to include activity messages based on the new includeActivity option. - Added tests to ensure correct handling of activity messages during persistence and snapshot processes. * feat(ai): add optional ActivityStore for AG-UI activity persistence - Introduced an ActivityStore to enable saving and reconstructing AG-UI activity without affecting the MessageStore. - Updated client persistence documentation to reflect the new activity storage capabilities. - Enhanced tests to validate the integration and functionality of the ActivityStore within the existing persistence framework. * refactor(ai): streamline message rendering and improve activity handling - Updated the Messages component to skip rendering for 'activity' role messages, enhancing performance and clarity. - Refactored message part rendering logic for better readability and maintainability. - Adjusted type definitions and imports for consistency across the codebase. - Improved handling of JSON patching in activity records to ensure accurate updates. * test(e2e): add AG-UI activity harness and Playwright coverage Add a provider-free /activity-test route that exercises live ACTIVITY_SNAPSHOT/DELTA, MESSAGES_SNAPSHOT hydrate, and the client send filter so activity never goes back as model input. * fix(ai): harden activity handling and add reconstruct E2E + Angular UI Guard ACTIVITY_SNAPSHOT from replacing non-activity messages, reject mismatched ACTIVITY_DELTA types and invalid root patch results, and merge activity metadata on live snapshot/delta. Add reconstructChat E2E via ActivityStore and render activity rows in the Angular chat example (PLAN checklist + JSON fallback). * refactor(ai): replace EventType constants with string literals in stream processor tests Updated the stream processor tests to use string literals for ACTIVITY_SNAPSHOT and ACTIVITY_DELTA instead of EventType constants for improved clarity and consistency. This change also applies to the test-utils file and the e2e activity test route, ensuring uniformity across the codebase. * fix(StreamProcessor): improve handling of omitted activity messages in snapshots * fix(ai-persistence): page activity rows and keep activity saves best-effort - reconstructChat: a thread with activity loads in full, interleaves, then pages, so each activity shows on one page at the right place. - withPersistence: save activity after the message, run, and interrupt writes, and ignore activity store errors. - ActivityRecord keeps metadata in both directions. - ChatMiddlewareContext.activities is optional. - Add a changeset for ai-byteplus and a migration note for role 'activity'. * docs(persistence): document the activities store and activity rows * fix(ai, ai-persistence): keep stored activity rows and use the AG-UI activity types - Do not save an empty activity list from the pending-turn snapshot. - Merge inbound activity rows into the stored rows by id. - Drop the activity rows of a turn that a reload replaces. - Page through the store when a cursor is not a UI message id. - Log a failed activity save. Skip the save when the context has no activities. - Derive the activity event, part, and record types from @ag-ui/core. - Send activity metadata in MESSAGES_SNAPSHOT. - Warn on a delta for an unknown id and on a text and activity id collision. - Accept the activity role in the event-client and devtools message types. - Document the activities skip for the conformance suite. * fix(ai): accept an inbound AG-UI ActivityMessage and keep its subagentRunId - Collect an inbound message in the AG-UI ActivityMessage shape, not only a UIMessage with an activity part. - Keep subagentRunId from an inbound message and from an activity event on the stored record. - Send subagentRunId on the ActivityMessage in MESSAGES_SNAPSHOT. --------- Co-authored-by: Alem Tuzlak <t.zlak@hotmail.com> Co-authored-by: Tom Beckenham <34339192+tombeckenham@users.noreply.github.com>
by Harshdeep ...
Succeeded
main
592c72c2 feat(ai): add AG-UI activity messages and optional ActivityStore (#1323) * feat(ai): introduce AG-UI activity messages with snapshot and delta handling - Added frontend-only activity messages: ACTIVITY_SNAPSHOT and ACTIVITY_DELTA. - Updated StreamProcessor to handle these new message types without affecting model input. - Integrated fast-json-patch for applying updates to activity content. - Enhanced type definitions and tests to ensure proper functionality and type safety for activity messages. - Updated pnpm-lock.yaml to include fast-json-patch dependency. * feat(ai-client): expose AG-UI activity messages in chat client - Introduced support for 'activity' role in UIMessage, allowing frontend-only activity messages to be appended without affecting model input. - Updated type definitions to include ActivityPart and modified relevant interfaces. - Enhanced chat client logic to handle activity messages appropriately, ensuring they are retained in the transcript but not sent to the model. - Added tests to verify the correct handling and integration of activity messages in various scenarios. * feat(ai): implement AG-UI ActivityMessage handling in snapshots - Introduced emission of AG-UI ActivityMessage on MESSAGES_SNAPSHOT events. - Updated StreamProcessor to retain omitted activity rows when a snapshot replaces the transcript. - Enhanced uiMessagesToWire function to include activity messages based on the new includeActivity option. - Added tests to ensure correct handling of activity messages during persistence and snapshot processes. * feat(ai): add optional ActivityStore for AG-UI activity persistence - Introduced an ActivityStore to enable saving and reconstructing AG-UI activity without affecting the MessageStore. - Updated client persistence documentation to reflect the new activity storage capabilities. - Enhanced tests to validate the integration and functionality of the ActivityStore within the existing persistence framework. * refactor(ai): streamline message rendering and improve activity handling - Updated the Messages component to skip rendering for 'activity' role messages, enhancing performance and clarity. - Refactored message part rendering logic for better readability and maintainability. - Adjusted type definitions and imports for consistency across the codebase. - Improved handling of JSON patching in activity records to ensure accurate updates. * test(e2e): add AG-UI activity harness and Playwright coverage Add a provider-free /activity-test route that exercises live ACTIVITY_SNAPSHOT/DELTA, MESSAGES_SNAPSHOT hydrate, and the client send filter so activity never goes back as model input. * fix(ai): harden activity handling and add reconstruct E2E + Angular UI Guard ACTIVITY_SNAPSHOT from replacing non-activity messages, reject mismatched ACTIVITY_DELTA types and invalid root patch results, and merge activity metadata on live snapshot/delta. Add reconstructChat E2E via ActivityStore and render activity rows in the Angular chat example (PLAN checklist + JSON fallback). * refactor(ai): replace EventType constants with string literals in stream processor tests Updated the stream processor tests to use string literals for ACTIVITY_SNAPSHOT and ACTIVITY_DELTA instead of EventType constants for improved clarity and consistency. This change also applies to the test-utils file and the e2e activity test route, ensuring uniformity across the codebase. * fix(StreamProcessor): improve handling of omitted activity messages in snapshots * fix(ai-persistence): page activity rows and keep activity saves best-effort - reconstructChat: a thread with activity loads in full, interleaves, then pages, so each activity shows on one page at the right place. - withPersistence: save activity after the message, run, and interrupt writes, and ignore activity store errors. - ActivityRecord keeps metadata in both directions. - ChatMiddlewareContext.activities is optional. - Add a changeset for ai-byteplus and a migration note for role 'activity'. * docs(persistence): document the activities store and activity rows * fix(ai, ai-persistence): keep stored activity rows and use the AG-UI activity types - Do not save an empty activity list from the pending-turn snapshot. - Merge inbound activity rows into the stored rows by id. - Drop the activity rows of a turn that a reload replaces. - Page through the store when a cursor is not a UI message id. - Log a failed activity save. Skip the save when the context has no activities. - Derive the activity event, part, and record types from @ag-ui/core. - Send activity metadata in MESSAGES_SNAPSHOT. - Warn on a delta for an unknown id and on a text and activity id collision. - Accept the activity role in the event-client and devtools message types. - Document the activities skip for the conformance suite. * fix(ai): accept an inbound AG-UI ActivityMessage and keep its subagentRunId - Collect an inbound message in the AG-UI ActivityMessage shape, not only a UIMessage with an activity part. - Keep subagentRunId from an inbound message and from an activity event on the stored record. - Send subagentRunId on the ActivityMessage in MESSAGES_SNAPSHOT. --------- Co-authored-by: Alem Tuzlak <t.zlak@hotmail.com> Co-authored-by: Tom Beckenham <34339192+tombeckenham@users.noreply.github.com>
by Harshdeep ...
Failed
feat/ag-ui-activity
304f2c8a Merge 101e044650b6f6b97ee2554b507e9150e0910920 into 8ce7ad97cbcf5e01de1b8fc07124aece87ca6102
by Harshdeep ...
Succeeded
main
81c28517 fix(ai-bedrock): use catalog Mantle path for Gemma 4 (#1270) * feat(ai-bedrock): update Bedrock Mantle endpoint for Gemma models - Introduced a new changeset to specify that `google.gemma-*` models now use the `/openai/v1` path on the Bedrock Mantle endpoint, ensuring correct routing for chat and response requests. - Updated documentation to reflect the new endpoint behavior for Gemma models. - Modified the `buildBaseURL` function to dynamically set the base URL based on the model type. - Enhanced tests to verify the correct base URL is used for both Gemma and other models on the mantle endpoint. * fix(ai-bedrock): refine Bedrock Mantle endpoint usage for Gemma models - Updated the Bedrock Mantle endpoint to specify that only `google.gemma-4-*` models use the `/openai/v1` path, while `google.gemma-3-*` models continue to use `/v1`. - Adjusted documentation to clarify the endpoint behavior for different Gemma model versions. - Enhanced tests to ensure correct base URL handling for both Gemma 3 and Gemma 4 models. * ci: apply automated fixes * fix(ai-bedrock): take Mantle path from the catalog row Look up mantlePath on GENERATED_BEDROCK_MODELS instead of a google.gemma-4- prefix. Seed the path in bedrock-api-compatibility.json and emit it from fetch-bedrock-models. Add Gemma 4 catalog rows so bedrockText(..., { api: 'chat' }) can construct. * fix(ai-bedrock): read Mantle path from the compatibility config Look up mantlePath from the Bedrock API compatibility rules instead of denormalizing it onto every catalog row, so Gemma 4 keeps /openai/v1 even before the catalog lists that id. Co-authored-by: Cursor <cursoragent@cursor.com> * fix(ai-bedrock): accept chat-only models on the branching factory Gemma 4 is not a Converse model. Widen the implementation signatures and reject the default Converse path when the catalog says converse is false. Co-authored-by: Cursor <cursoragent@cursor.com> --------- Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com> Co-authored-by: Tom Beckenham <34339192+tombeckenham@users.noreply.github.com> Co-authored-by: Cursor <cursoragent@cursor.com>
by Harshdeep ...
Succeeded
main
81c28517 fix(ai-bedrock): use catalog Mantle path for Gemma 4 (#1270) * feat(ai-bedrock): update Bedrock Mantle endpoint for Gemma models - Introduced a new changeset to specify that `google.gemma-*` models now use the `/openai/v1` path on the Bedrock Mantle endpoint, ensuring correct routing for chat and response requests. - Updated documentation to reflect the new endpoint behavior for Gemma models. - Modified the `buildBaseURL` function to dynamically set the base URL based on the model type. - Enhanced tests to verify the correct base URL is used for both Gemma and other models on the mantle endpoint. * fix(ai-bedrock): refine Bedrock Mantle endpoint usage for Gemma models - Updated the Bedrock Mantle endpoint to specify that only `google.gemma-4-*` models use the `/openai/v1` path, while `google.gemma-3-*` models continue to use `/v1`. - Adjusted documentation to clarify the endpoint behavior for different Gemma model versions. - Enhanced tests to ensure correct base URL handling for both Gemma 3 and Gemma 4 models. * ci: apply automated fixes * fix(ai-bedrock): take Mantle path from the catalog row Look up mantlePath on GENERATED_BEDROCK_MODELS instead of a google.gemma-4- prefix. Seed the path in bedrock-api-compatibility.json and emit it from fetch-bedrock-models. Add Gemma 4 catalog rows so bedrockText(..., { api: 'chat' }) can construct. * fix(ai-bedrock): read Mantle path from the compatibility config Look up mantlePath from the Bedrock API compatibility rules instead of denormalizing it onto every catalog row, so Gemma 4 keeps /openai/v1 even before the catalog lists that id. Co-authored-by: Cursor <cursoragent@cursor.com> * fix(ai-bedrock): accept chat-only models on the branching factory Gemma 4 is not a Converse model. Widen the implementation signatures and reject the default Converse path when the catalog says converse is false. Co-authored-by: Cursor <cursoragent@cursor.com> --------- Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com> Co-authored-by: Tom Beckenham <34339192+tombeckenham@users.noreply.github.com> Co-authored-by: Cursor <cursoragent@cursor.com>
by Harshdeep ...
Succeeded
docs/remove-duplicate-page-headings
5d682de5 feat(ai-openai): accept token-provider apiKey on openaiCompatible (#1322) * feat(ai-openai): enhance compatibility with OpenAI SDK token-provider Added support for `openaiCompatible` and `openaiCompatibleText` to accept a token-provider function for the `apiKey`, allowing for better type-checking with Azure Entra and rotating keys. Updated type definitions to use `NonNullable` for `apiKey` in configuration interfaces. Added tests to verify the new functionality. * ci: apply automated fixes --------- Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
by Harshdeep ...
Succeeded
docs/remove-duplicate-page-headings
2d427248 feat(ai-openai): accept token-provider apiKey on openaiCompatible (#1322) * feat(ai-openai): enhance compatibility with OpenAI SDK token-provider Added support for `openaiCompatible` and `openaiCompatibleText` to accept a token-provider function for the `apiKey`, allowing for better type-checking with Azure Entra and rotating keys. Updated type definitions to use `NonNullable` for `apiKey` in configuration interfaces. Added tests to verify the new functionality. * ci: apply automated fixes --------- Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
by Harshdeep ...
Succeeded
main
2f6a45c4 feat(ai-openai): accept token-provider apiKey on openaiCompatible (#1322) * feat(ai-openai): enhance compatibility with OpenAI SDK token-provider Added support for `openaiCompatible` and `openaiCompatibleText` to accept a token-provider function for the `apiKey`, allowing for better type-checking with Azure Entra and rotating keys. Updated type definitions to use `NonNullable` for `apiKey` in configuration interfaces. Added tests to verify the new functionality. * ci: apply automated fixes --------- Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
by Harshdeep ...
Succeeded
main
2f6a45c4 feat(ai-openai): accept token-provider apiKey on openaiCompatible (#1322) * feat(ai-openai): enhance compatibility with OpenAI SDK token-provider Added support for `openaiCompatible` and `openaiCompatibleText` to accept a token-provider function for the `apiKey`, allowing for better type-checking with Azure Entra and rotating keys. Updated type definitions to use `NonNullable` for `apiKey` in configuration interfaces. Added tests to verify the new functionality. * ci: apply automated fixes --------- Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
by Harshdeep ...
Succeeded
main
2f6a45c4 feat(ai-openai): accept token-provider apiKey on openaiCompatible (#1322) * feat(ai-openai): enhance compatibility with OpenAI SDK token-provider Added support for `openaiCompatible` and `openaiCompatibleText` to accept a token-provider function for the `apiKey`, allowing for better type-checking with Azure Entra and rotating keys. Updated type definitions to use `NonNullable` for `apiKey` in configuration interfaces. Added tests to verify the new functionality. * ci: apply automated fixes --------- Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
by Harshdeep ...
Succeeded
feat/compatible-token-provider
65d7ec48 Merge e61a2508b59d46d78236a4a995b6e47add457f18 into bad612a3ae64702a3194c986a70f1905cad42751
by Harshdeep ...
Succeeded
feat/compatible-token-provider
5a9a20f0 Merge 020c7352338af56c3d50f7b7d191fdb74ef8dd17 into 62e4e4699bbe270826a915b1bf3fbc21f85e6217
by Harshdeep ...
Failed
feat/ag-ui-activity-client
83a28ecd Merge 9f7a9ad5b0a1338104f9f6f6d3931b8fb907f817 into 1d15d526312a209b5d7f843d80f34bd3c1434c0a
by Harshdeep ...
Succeeded
feat/ag-ui-activity-client
83a28ecd feat(ai-client): expose AG-UI activity messages in chat client - Introduced support for 'activity' role in UIMessage, allowing frontend-only activity messages to be appended without affecting model input. - Updated type definitions to include ActivityPart and modified relevant interfaces. - Enhanced chat client logic to handle activity messages appropriately, ensuring they are retained in the transcript but not sent to the model. - Added tests to verify the correct handling and integration of activity messages in various scenarios.
by Harshdeep ...
Failed
feat/ag-ui-activity-client
83a28ecd feat(ai-client): expose AG-UI activity messages in chat client - Introduced support for 'activity' role in UIMessage, allowing frontend-only activity messages to be appended without affecting model input. - Updated type definitions to include ActivityPart and modified relevant interfaces. - Enhanced chat client logic to handle activity messages appropriately, ensuring they are retained in the transcript but not sent to the model. - Added tests to verify the correct handling and integration of activity messages in various scenarios.
by Harshdeep ...
Succeeded
feat/compatible-token-provider
faeed116 feat(ai-openai): enhance compatibility with OpenAI SDK token-provider Added support for `openaiCompatible` and `openaiCompatibleText` to accept a token-provider function for the `apiKey`, allowing for better type-checking with Azure Entra and rotating keys. Updated type definitions to use `NonNullable` for `apiKey` in configuration interfaces. Added tests to verify the new functionality.
by Harshdeep ...
Succeeded
feat/compatible-token-provider
faeed116 feat(ai-openai): enhance compatibility with OpenAI SDK token-provider Added support for `openaiCompatible` and `openaiCompatibleText` to accept a token-provider function for the `apiKey`, allowing for better type-checking with Azure Entra and rotating keys. Updated type definitions to use `NonNullable` for `apiKey` in configuration interfaces. Added tests to verify the new functionality.
by Harshdeep ...
Succeeded
fix-925-bedrock-mantle-path
df7f9118 Merge 7566becbc4cb9c0cec6f7162a80531c14ae3127c into b899fe5328f2907e5abbaa9c11b8f486caec229f
by Harshdeep ...
Succeeded
fix-1212-openai-responses-reasoning-roundtrip
b798a419 Merge 856d1f3557d2b6e3a5ee7f081dd40cbe9acdfd5f into b899fe5328f2907e5abbaa9c11b8f486caec229f
by Harshdeep ...