pub fn render_status_with_failures(
plugins: &[PluginStatus],
failed: &[FailedLoad],
) -> StringExpand description
WT.4: render_status plus a trailing section for plugins that tried to
load and could not.
Trailing, and deliberately so. The interactivity layer maps
cursor.line - HEADER_LINES into the loaded-plugin list, so anything
inserted above or between the rows would put chords on the wrong plugin.
Failed entries have no host id to unload or reload anyway — they are a
report, not a row you can act on — so appending them costs the mapping
nothing.
Why it exists at all: a plugin that failed to load is otherwise indistinguishable from one that was never installed. That is precisely what made the reported failure take a debugging session — org was absent, and absent looks the same either way.