end-to-end-workflow

To determine which files to modify for a Rust feature, follow a decision-tree workflow that maps feature types to specific module targets across Config, CLI, Bridge, LSP, and Core library workflows, ensuring all required file changes are identified.

End-to-end feature development requires executing specific build commands to validate changes: run cargo test export_bindings for bindings, xtask build-js for the JS bridge, and cargo build to compile the Rust core.

You need a decision-tree workflow when implementing multi-module changes that span Config, CLI, Bridge, LSP, or Core library components, guiding you through exact file targets and required build steps to avoid missing dependencies.

Yes, the end-to-end workflow supports feature changes involving both the LSP and Core library by providing clear decision points that map the required cross-module file modifications and the necessary build orders.

The best way to handle multi-module feature changes is applying a comprehensive decision-tree workflow that maps the specific feature type to touched files and build orders across Rust and JS bridges, ensuring complete end-to-end implementation.