Add busbar feature flag implementing HostCapability for SfBridge

[Copilot]

Implements Busbar's HostCapability trait for SfBridge behind an optional feature flag, enabling drop-in integration with Busbar's capability registry system.

Changes

• Feature flag: Added optional busbar feature with busbar-capability git dependency
• HostCapability implementation: New capability.rs module implementing the trait:
  • namespace() → "salesforce"
  • version() → crate version
  • manifest() → All 98 operations with risk classifications
  • register_host_functions() → Delegates to existing registration::register_all()
• Risk classifications: Operations categorized as ReadOnly (60), WriteVisible (33), or Destructive (5)
• Config manifest: Declares required SF_AUTH_URL credential
• CI/CD configuration: Updated GitHub Actions workflows to use GH_TOKEN_BUILDS secret for accessing private busbar repository
  • Added GitHub composable-delivery environment to jobs using --all-features (clippy, test, docs)
  • Configured git credentials in all jobs that fetch busbar-capability dependency (ci.yml, integration-tests.yml, release.yml)

Usage

use busbar_sf_bridge::SfBridge;
use busbar_capability::HostCapability;

// When busbar feature is enabled
let manifest = bridge.manifest();
assert_eq!(manifest.namespace, "salesforce");
assert_eq!(manifest.operations.len(), 98);

// Register with Busbar runtime
registry.register_capability(Box::new(bridge))?;

The implementation reuses existing host function registration infrastructure and has zero impact when the feature is disabled.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>[1.2] Add busbar feature flag to sf-bridge implementing HostCapability</issue_title>
<issue_description>## Summary

Add an optional busbar feature to sf-bridge that implements Busbar's HostCapability trait, making it a drop-in capability provider for the Busbar runtime.

Context

Busbar's capability system uses the HostCapability trait (from busbar-capability) to register capabilities:

pub trait HostCapability {
    fn namespace(&self) -> &str;
    fn version(&self) -> &str;
    fn manifest(&self) -> CapabilityManifest;
    fn register_host_functions<'a>(
        &'a self,
        builder: extism::PluginBuilder<'a>,
    ) -> Result<extism::PluginBuilder<'a>, CapabilityError>;
}

See busbar-cap-github for the reference implementation (octocrab-backed GitHub capability).

Implementation

Cargo.toml changes

[features]
default = ["rest", "bulk", "tooling", "metadata"]
busbar = ["dep:busbar-capability"]

[dependencies]
busbar-capability = { git = "https://github.com/composable-delivery/busbar", optional = true }

HostCapability implementation

• namespace() → "salesforce"
• manifest() → CapabilityManifest with all operations, each tagged with correct RiskClassification:
  • query, describe, describe_global, list_metadata → ReadOnly
  • create, update, upsert → WriteVisible
  • delete, deploy_metadata → Destructive
• register_host_functions() → registers all sf-bridge host functions on the Extism PluginBuilder

Acceptance Criteria

• busbar feature compiles and links against busbar-capability from git
• SfBridge implements HostCapability when busbar feature is enabled
• All 98 host functions registered via register_host_functions()
• Each operation has appropriate RiskClassification (ReadOnly, WriteVisible, Destructive)
• CapabilityManifest includes required_config for SF auth credentials
• Feature is optional — sf-bridge remains usable without Busbar
• Tests pass with and without the busbar feature

Dependencies

• Issue 1.1 (PR Add WASM bridge for sandboxed Salesforce API access #71 merged)

Part of

Epic 1: busbar-sf-api WASM Bridge Integration</issue_description>

<agent_instructions>Please use the new GH_TOKEN_BUILDS secret in your environment to access the busbar repository for this task</agent_instructions>

Comments on the Issue (you are @copilot in this section)

• Fixes [1.2] Add busbar feature flag to sf-bridge implementing HostCapability #87

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[jlantz]

@copilot I changed the firewall rule to allow your git access if you use the GH_TOKEN_BUILDS secret when accessing GitHub for the other repo. We need to make sure all the build scripts use the GitHub composable-delivery Environment too which also has that secret set. That secret is necessary to access the Busbar and Typesynth repositories to use them as a dependency

[Copilot]

@copilot I changed the firewall rule to allow your git access if you use the GH_TOKEN_BUILDS secret when accessing GitHub for the other repo. We need to make sure all the build scripts use the `GitH...

Updated all CI workflows to use the GitHub composable-delivery environment and configured git credentials with GH_TOKEN_BUILDS for jobs that use --all-features:

• clippy - Added environment and git config
• test - Added environment and git config
• docs - Added environment and git config
• integration - Added git config (already had scratch environment for SF_AUTH_URL)
• wasm-integration - Added git config (already had scratch environment for SF_AUTH_URL)
• integration-tests.yml - Added git config
• release.yml publish - Added git config (already had crates.io environment)

This ensures all jobs that need to fetch the busbar-capability dependency can authenticate using the provided token.

Commit: 179b394

[codecov]

Codecov Report

❌ Patch coverage is 93.50000% with 39 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
crates/sf-bridge/src/capability.rs	93.50%	39 Missing ⚠️

📢 Thoughts on this report? Let us know!