Package com.ultikits.ultitools.utils

Enum Class PluginInitiationUtils.VerdictRecorder

java.lang.Object
java.lang.Enum<PluginInitiationUtils.VerdictRecorder>
com.ultikits.ultitools.utils.PluginInitiationUtils.VerdictRecorder
All Implemented Interfaces:
Serializable, Comparable<PluginInitiationUtils.VerdictRecorder>, java.lang.constant.Constable
Enclosing class:
PluginInitiationUtils
static enum PluginInitiationUtils.VerdictRecorder extends Enum<PluginInitiationUtils.VerdictRecorder>
Which side of a capability-gated dispatch records the RemoteActionLog verdict for the enabled branch (CR-01, 06-REVIEW.md).

Exactly two entries — execute_command and file_operation — invoke a handler that performs its own, independent, finer-grained AccessDecision check (CommandExecutionManager#isCommandAllowed/FileOperationManager#isPathAllowed) and records its own verdict from that check; every other capability-gated entry has no second policy layer to conflict with. Before this enum existed, dispatchWithCapabilityGate recorded a blanket ALLOWED entry on every enabled branch regardless of which case it was, producing a contradictory second log line — a real DENIED from the handler's own check immediately followed by a false ALLOWED from the gate — for every blocklisted command and every credential/out-of-root file request. A required field (verified by inspecting every entry's handler for its own RemoteActionLog write) is what stops a newly added entry from silently repeating that mistake, rather than a defaulted or inferred value. Precisely: omitting the argument is a genuine compile error; a null value compiles but is rejected immediately at class-initialization time — see PluginInitiationUtils.InboundHandlerEntry's own javadoc for the exact boundary between the two (IN-01, 06-REVIEW.md).