Skip to content

Forward-merge release/0.2 into main - #249

Merged
AnuradhaKaruppiah merged 1 commit into
mainfrom
release/0.2
Aug 18, 2026
Merged

Forward-merge release/0.2 into main#249
AnuradhaKaruppiah merged 1 commit into
mainfrom
release/0.2

Conversation

@rapids-bot

@rapids-bot rapids-bot Bot commented Aug 18, 2026

Copy link
Copy Markdown

Forward-merge triggered by push to release/0.2 that creates a PR to keep main up-to-date. If this PR is unable to be immediately merged due to conflicts, it will remain open for the team to manually merge. See forward-merger docs for more info.

#### Overview

- Publish the repository adapter-contract documentation as the maintained, incremental guide for harness adapters and custom-agent integrations.
- Normalize the southbound lifecycle around `AgentConfig`, `AgentRunRequest`, `RuntimeContext`, and `AgentRunResult`.
- Migrate all five bundled adapters, the NVIDIA NeMo Agent Toolkit adapter, and the LangGraph custom-agent example to the typed request and result boundary.
- Keep request projection and consumer-facing result enrichment in the NeMo Fabric core, and remove the redundant descriptor input selector.
- Regenerate the JSON Schemas, Python and TypeScript bindings, and Rust API reference; update the public authoring skill, release notes, examples, and repository overview.

Adapters now receive `AgentConfig` at startup, receive `AgentRunRequest` and `RuntimeContext` for each invocation, and return one typed `AgentRunResult`. Adapter authors can follow the staged guide and use Hermes Agent as the complete harness reference, mini-SWE-agent as the minimum-surface example, NVIDIA NeMo Agent Toolkit as the shared-framework example, or the LangGraph email-phishing analyzer as the dedicated custom-agent example.

#### Where Should the Reviewer Start?

Start with `docs/adapter-contract/README.md` for the reader path and minimum surface, then review `docs/adapter-contract/execution.md` and `crates/fabric-core/src/agent_execution.rs` for the typed lifecycle boundary.

#### Validation

- Full Python and Rust workspace suites passed.
- TypeScript generation, generated-file, type, dependency, audit, and package checks passed.
- Documentation copyright, API reference, strict link, and Mermaid render checks passed.
- Final review fixes: 131 focused adapter tests and the artifact-collision Rust regression test passed.

Relates to #228

Closes FABRIC-211
Closes FABRIC-212

- [x] I confirm this contribution is my own work, or I have the right to submit it under this project's license.
- [x] I searched existing issues and open pull requests, and this does not duplicate existing work.



## Summary by CodeRabbit

* **New Features**
  * Added configurable Adapter Targets for harnesses, shared frameworks, and custom agents.
  * Standardized invocation results with statuses, structured errors, artifacts, token usage, and cost details.
  * Added optional native OpenAI streaming and adapter extension validation.
  * Added normalized usage details to SDK run results.
  * Expanded custom-agent, MCP, LangGraph, and mini-SWE-agent integration support.

* **Documentation**
  * Updated Fabric 0.2 and v1alpha2 adapter contract guidance.
  * Added examples, discovery guidance, streaming instructions, and adapter verification checklists.
  * Clarified configuration and lifecycle requirements for adapter integrations.

Authors:
  - Anuradha Karuppiah (https://github.com/AnuradhaKaruppiah)

Approvers:
  - Ajay Thorve (https://github.com/AjayThorve)
  - Zhongxuan (Daniel) Wang (https://github.com/zhongxuanwang-nv)
  - https://github.com/lvojtku

URL: #241
@rapids-bot
rapids-bot Bot requested review from a team as code owners August 18, 2026 18:34
@rapids-bot

rapids-bot Bot commented Aug 18, 2026

Copy link
Copy Markdown
Author

FAILURE - Unable to forward-merge due to an error, manual merge is necessary. Do not use the Resolve conflicts option in this PR, follow these instructions https://docs.rapids.ai/maintainers/forward-merger/

IMPORTANT: When merging this PR, do not use the auto-merger (i.e. the /merge comment). Instead, an admin must manually merge by changing the merging strategy to Create a Merge Commit. Otherwise, history will be lost and the branches become incompatible.

@AnuradhaKaruppiah
AnuradhaKaruppiah merged commit bacb524 into main Aug 18, 2026
2 of 3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant