Inlined plugins

tauri version:2
I have a custom plugin(not a lib package,just a rs file with some commands), in the rs file,there is an init function like below:

// custom.rs
pub fn init() -> TauriPlugin<Wry> {
    Builder::new("custom")
        .invoke_handler(generate_handler![test_command])
        .build()
}

and inner the main.rs

// main.rs
fn main() {
    tauri::Builder::default()
        .plugin(tauri_plugin_process::init())
        .plugin(tauri_plugin_dialog::init())
        .plugin(tauri_plugin_clipboard_manager::init())
        .plugin(tauri_plugin_os::init())
        .plugin(tauri_plugin_shell::init())
        .plugin(tauri_plugin_notification::init())
        .plugin(tauri_plugin_fs::init())
        .plugin(tauri_plugin_global_shortcut::Builder::new().build())
        .plugin(tauri_plugin_http::init())
        // custom plugin
        .plugin(custom::init())
        .run(tauri::generate_context!())
        .expect("error while running tauri application");
}

but i can't invoke this command from frontend.

  await invoke(plugin::custom|test_command);

Error from frontend:Unhandled Promise Rejection: custom:test_command not allowed. Plugin not found.

and i can't add this custom command to capability too.

In the previous version tauri V1, I could invoke custom command using this way.
so,what i should do for this in v2?

Start with the custom.rs init function and main.rs registration shown in the report, then compare the Tauri v2 command-invocation and capability documentation. Clarify the supported way to expose an inlined custom plugin command from the frontend and the relevant capability configuration; done when the v1-to-v2 migration path and the reported custom:test_command failure are documented.