//! Shared `resolve_flag` 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 crateAppError;
pub use crateRoutineStore;
/// Resolve (delete) flag `filename` on routine `id`, refreshing `prompt.compiled.local.md` so it
/// stops appearing in the next run's prompt.