We've noticed the external docs https://www.elastic.co/guide/en/kibana/current/external-plugin-localization.html have broken links.

kui detects links and makes them clickable
it would be neat if it could also detect if the output on the console is a kui command, make it clickable so that when clicked the corresponding/linked command is executed.

example:

> echo auth add a:b
auth add a:b # this is detected as a kui command and made clickable so that it results in

> auth add a:b <return> # being executed

It'd be great to be able to load an external history upon initializing the undo/redo feature.

It's already supported by the Undoo lib, through the import(history) API, so it should be trivial to implement.
https://github.com/fabioricali/undoo#undooimporthistory--undoo

I suppose changing the UndoProps by adding a initialHistory prop would do the trick:

export interface UndoPr

Is your feature request related to a problem? Please describe.
In a few places we're forcing a disabled element by adding the class

.navi-report__action-link--force-disabled {
  color: @disabled-gray !important;
  cursor: not-allowed !important;
}

Probably because some child's cursor and color styles ignore its parent's disabled attribute/class.

**Describe the solution y

Splash screen right now is inconsistent with the theme, it would be better to have a theme based splash screen for both iOS and Android implemented in flutter itself.

User often do lots of parameter tuning. What some would like is create a new batch from filtered results (e.g. my_param: best_value), so that they can save them as a milestone with a descriptive name.

TODO

• Add a "Move filtered outputs" menu item, next to the "Rename batch" item, and [much like it](https://github.com/Samsung/qaboard/blob/master/webapp/src/components/CommitNavbar.js#