Lib.GAB 1.0.0

Release Notes

1.0.0

This release is aimed at engineers building host-side bridge products, not end users.

Typical adopters include:

• game mods exposing a GABP endpoint from inside a running game
• embedded automation bridges supervising a game or application process
• product-specific bridge hosts in the style of RimBridgeServer

Highlights

• Stable release line aligned with Gabp.Runtime 1.0.0
• Ships both netstandard2.0 and net10.0 assets
• Adds optional attention APIs: attention/current, attention/ack, attention/opened, attention/updated, and attention/cleared
• Improves tools/list metadata with canonical title, inputSchema, outputSchema, ResultDescription, and structured [ToolResponse] fields
• Fixes parameter metadata and binding so optional/defaulted parameters are advertised and applied correctly

Compatibility

• Intended to work in modern .NET hosts and in Unity/Mono-style hosts that can consume .NET Standard 2.0
• Validated locally against a RimBridgeServer-style consumer build targeting net472 and deploying into RimWorldMac.app
• Depends on Gabp.Runtime 1.0.0

Audience Guidance

Lib.GAB is the host/runtime layer. It helps you expose a stable GABP surface from inside your product, but it does not replace product-specific logic.

You still own:

• capability naming and semantics
• access to game or application state
• event production policy
• attention policy
• packaging and deployment inside your host product

Upgrade Notes

• Existing hosts that run inside Unity, Mono, or .NET Framework do not need a .NET 10 runtime. They consume the netstandard2.0 asset.
• Existing hosts should revisit any custom workarounds around optional parameters or default values in tool metadata. tools/list and tool invocation now agree on defaulted parameters.
• Product teams that want richer downstream discovery should start filling in ResultDescription and [ToolResponse] where their tools return stable, meaningful result shapes.

Recommended Adoption Pattern

1. Reference Lib.GAB from the host-side component that actually runs inside the game or application.
2. Register product-specific tools explicitly or by attribute scanning.
3. Surface ResultDescription and [ToolResponse] metadata where downstream bridges benefit from richer discovery.
4. Enable attention support only when your product has a clear policy for opening, updating, and acknowledging blocking async state.

Lib.GAB v0.1.0-alpha.1

What's Changed

• Implement complete GABP 1.0 server with tool registry, events, and TCP transport by @Copilot in #1
• Refactor Lib.GAB to target .NET Standard 2.0 for RimWorld mod compatibility by @Copilot in #2
• Remove automatic bridge config file creation and add external configuration API by @Copilot in #3
• Remove all legacy WriteConfigFile functionality and obsolete code by @Copilot in #5
• Refactor README: Remove modding references and obsolete features for improved clarity by @Copilot in #6
• Add seamless GABS integration with automatic environment detection by @Copilot in #7
• Add comprehensive GABS integration tests and discover CLI interface behavior by @Copilot in #8
• Add outputSchema support for tool response type documentation by @Aragas in #10
• Propagate nullable to GABS by @Aragas in #11

New Contributors

• @Copilot made their first contribution in #1
• @Aragas made their first contribution in #10

Full Changelog: https://github.com/pardeike/Lib.GAB/commits/v0.1.0-alpha.1

v0.1.0

What's Changed

• Input QoL FiIxes by @Aragas in #13

Full Changelog: v0.1.0-alpha.1...v0.1.0