Testing and Debugging

Run the same checks before every handoff:

npm run typecheck
npm run build
cargo fmt --check
cargo check
npx --yes @haloforge/plugin-pack@0.2.13 check .
npx --yes @haloforge/plugin-pack@0.2.13 pack . --out dist/package

Local Install

hf operates on the local HaloForge workspace. In source checkout examples use npm run hf -- ...; installed Windows builds can use hf ... directly after opening a new terminal. On macOS, run command -v hf first because automatic PATH linking is not implemented yet.

cd /path/to/HaloForge
npm run hf -- plugin install local /path/to/plugin/dist/package/<plugin-id>-<version>.hfpkg --json
npm run hf -- plugin list --json

The installed plugin should show:

• enabled: true
• state: "active"
• error_message: null

See Command Line for launch profile and catalog admin commands.

Runtime Logs

HaloForge writes application, frontend bridge, and plugin logs to a daily file:

tail -f ~/.haloforge/logs/haloforge.log.$(date +%F)

In development, raise Rust tracing with:

RUST_LOG=debug npm run tauri dev

Frontend plugins should use createPluginLogger() from @haloforge/plugin-sdk; Rust backends should use ctx.log(...). For image generation and other gateway flows, log request start, success, and failure with request ID, model, size, status, elapsed time, output count, and a short error summary. Do not log API keys, bearer tokens, full prompts, or raw image/base64 payloads.

Package Inspection

Inspect a package before installing:

unzip -l dist/package/dev.example.my-plugin-0.1.0.hfpkg

For a UI plugin, confirm the package contains:

• manifest.json
• frontend bundle
• frontend stylesheet if declared
• native library when entry.native is declared
• icon/assets referenced by the manifest

Plugin panel not loaded

Check these first:

1. registerPlugin() uses the exact same ID as manifest.json.
2. entry.frontend points to the built JavaScript file inside the package.
3. integration.*.panel_entry points to the panel bundle.
4. The package contains the frontend bundle and CSS.
5. The bundle executed without a JavaScript error.
6. The Rust backend loaded and registered commands.
7. Required host capabilities and permissions were declared.

If the bundle executed but did not register a panel, HaloForge should report that clearly in the plugin slot error area.