The run-outcome gate ignored the profile, so chat could be handed a log it is promised it never sees
This commit is contained in:
@@ -160,7 +160,12 @@ if ($profile === 'varaverk' || $profile === 'troubleshoot') {
|
||||
// — nothing had failed, so nothing in the question said failure. It retrieved the documentation
|
||||
// on where logs live and answered with directions to a page the operator already had open. The
|
||||
// question is about a run that happened, so the run itself has to be in context.
|
||||
$runOutcome = (bool)preg_match(
|
||||
//
|
||||
// Restricted to the two profiles that are allowed Varaverk's own material. chat is promised, as
|
||||
// its first and most absolute rule, that it has not been shown this installation — attaching a
|
||||
// log tail to it because the phrasing matched would break exactly the guarantee that stops it
|
||||
// inventing confident answers about the operator's system.
|
||||
$runOutcome = ($profile === 'varaverk' || $profile === 'troubleshoot') && (bool)preg_match(
|
||||
'/\b(how did|how.d|did .{0,24}\b(run|go|finish|complete)|last run|latest run|last night|'
|
||||
. 'go last|went last|how long did|run record|rundown|summar(y|ise|ize)|recap)\b/i',
|
||||
$question
|
||||
|
||||
Reference in New Issue
Block a user