moadim 3.2.7

Loop engine for AI agents — routines over REST, MCP, and a built-in web UI
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37

//! Shared `trigger_routine` logic: response shape and how to build it. Both the HTTP handler
//! (`http.rs`) and the MCP tool (`mcp.rs`) build on top of this.

use crate::error::AppError;
pub(crate) use crate::routines::{Routine, RoutineStore};
use serde::Deserialize;
use utoipa::ToSchema;

/// An explicit operator confirmation to run despite host-level power saving.
#[derive(Debug, Deserialize, ToSchema)]
pub struct TriggerRoutineRequest {
    /// Bypass only host-level power saving for this manual run. It does not bypass a routine's
    /// explicit power-saving state, disabled state, or the global lock.
    #[serde(default)]
    pub override_system_power_saving: bool,
}

/// Manually trigger the routine with the given UUID, recording `last_manual_trigger_at` and
/// returning the updated record.
pub fn build(
    store: &RoutineStore,
    id: &str,
    override_system_power_saving: bool,
) -> Result<Routine, AppError> {
    if !override_system_power_saving {
        return crate::routines::svc_trigger(store, id);
    }
    crate::routines::svc_trigger_with_system_power_saving_override(
        store,
        id,
        override_system_power_saving,
    )
}

#[cfg(test)]
#[path = "logic_tests.rs"]
mod logic_tests;