product-capabilities Agent Guide

Scope: this guide applies to src/crates/assembly/product-capabilities.

bitfun-product-capabilities owns product capability pack assembly facts: which delivery profiles, runtime services, feature groups, tool provider group ids, harness provider descriptors, profile-scoped harness registries, and runtime service availability wrappers a product capability selects. It does not own concrete runtime execution.

Guardrails

• Do not depend on bitfun-core, app crates, Tauri, product-domain implementations, concrete service crates, AI adapters, transport adapters, terminal, tool-runtime, or concrete tool implementations.
• Keep this crate limited to stable delivery profile facts, capability ids, feature group facts, service capability facts, runtime service availability checks, tool provider group id selection, and harness provider descriptor selection.
• ProductToolPlan is the assembly-owned authority for the exact tool feature owners requested by one runtime. Provider groups preserve registration order; they are not feature unions. The Agent Runtime baseline plan selects only Basic and AgentControl, while delivery profiles select their reviewed product plan explicitly.
• ProductAssembler may validate explicit profile input and return immutable runtime parts; it must not create concrete services or product state.
• ProductCoreDependencyMode::ExplicitCoreCapabilityClosure records that an entrypoint selects reviewed Cargo owner capabilities; it is not a feature list, runtime availability result, or permission to introduce a profile-named umbrella feature.
• Do not encode product UI behavior, permission decisions, session lifecycle, filesystem/process IO, Git/AI provider acquisition, or feature defaults here.
• Preserve default product tool provider order and legacy harness provider ids when changing capability packs.

Verification

cargo test -p bitfun-product-capabilities
node scripts/check-core-boundaries.mjs

For documentation-only changes, run git diff --check.