Offer Troubleshoot as a profile, and say plainly when it has no log
This commit is contained in:
@@ -93,12 +93,19 @@ const VV_AI_PROFILES_DEF = [
|
||||
'ui' => true,
|
||||
'caps' => ['code_scan'],
|
||||
],
|
||||
// Offered as a button as well as entered by context. It was context-only on the reasoning
|
||||
// that choosing it from a dashboard produces a troubleshooting contract with nothing to
|
||||
// troubleshoot — true of the inputs, but not of the profile: name a script in the question
|
||||
// and run_evidence resolves the run record and log for it without any scope at all. The
|
||||
// prompt now states which of those it actually received rather than asserting a log, so
|
||||
// picking it with nothing open degrades to an honest "I cannot see one" instead of an
|
||||
// invented reading of a log that was never attached.
|
||||
'troubleshoot' => [
|
||||
'label' => 'Troubleshoot',
|
||||
'short' => 'Troubleshoot',
|
||||
'hint' => 'Reasons from the log you have open, then the docs. Files a bug only when the evidence shows one.',
|
||||
'hint' => 'Reasons from evidence — the log you have open, or one you name. Says so when there is none.',
|
||||
'turns' => 2,
|
||||
'ui' => false,
|
||||
'ui' => true,
|
||||
'caps' => ['retrieve', 'health', 'run_evidence', 'scoped_log', 'incidents', 'conf_lookup', 'file_bugs'],
|
||||
],
|
||||
];
|
||||
|
||||
Reference in New Issue
Block a user