Make fallback coverage something that can actually happen, and say so on the page
fallback.sh starts covered containers with docker start and never creates them, so a coverage list the partner has never been sent is a promise nothing can keep — all twelve were missing. Adds the push and remove paths, a readiness card that checks rather than infers, and the fallback state the assistant needs to answer for it.
This commit is contained in:
@@ -116,7 +116,7 @@ const VV_AI_PROFILES_DEF = [
|
||||
// system_state is read-only and shared with repair. Both need to know a container is down
|
||||
// or a pool is full to explain anything about this machine rather than about Unraid in
|
||||
// general; neither gets a way to act on it, and only repair can change a setting.
|
||||
'caps' => ['retrieve', 'health', 'system_state', 'run_evidence', 'scoped_log',
|
||||
'caps' => ['retrieve', 'health', 'system_state', 'fallback_state', 'run_evidence', 'scoped_log',
|
||||
'incidents', 'conf_lookup', 'file_bugs'],
|
||||
],
|
||||
// The only profile that may change a setting, and the only one not offered as a button.
|
||||
@@ -136,7 +136,7 @@ const VV_AI_PROFILES_DEF = [
|
||||
'hint' => 'Works through a finding with you, and can apply a fix you approve.',
|
||||
'turns' => 3,
|
||||
'ui' => false,
|
||||
'caps' => ['retrieve', 'health', 'system_state', 'run_evidence', 'scoped_log', 'incidents',
|
||||
'caps' => ['retrieve', 'health', 'system_state', 'fallback_state', 'run_evidence', 'scoped_log', 'incidents',
|
||||
'conf_lookup', 'conf_write', 'probe', 'file_findings', 'phrasebook', 'past_fixes'],
|
||||
],
|
||||
];
|
||||
@@ -148,6 +148,7 @@ const VV_AI_CAP_MEANING = [
|
||||
'kind_filter' => 'the retrieval kind filter the page exposes',
|
||||
'health' => 'live health sweep measured at question time — the AI subsystem only',
|
||||
'system_state' => 'read-only view of the machine: hardware, containers, pools, array, UPS',
|
||||
'fallback_state' => 'whether a failover would actually work: state, tiers, and whether the partner really has the covered containers',
|
||||
'run_evidence' => 'run record and log tail for a script named in the question',
|
||||
'scoped_log' => 'log tail for whatever the operator currently has open',
|
||||
'incidents' => 'operator-written history of what previously went wrong with this thing',
|
||||
|
||||
Reference in New Issue
Block a user