spec-driven-docs 0.4.11

Spec-driven documentation: current specs, immutable decision records, and executable gates kept coherent for people and coding agents.
Documentation 
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
38
39
40
41
42
43

//! `gate` subcommand: runtime-shape.
//!
//! Runs one delivered gate against the invoking repository, printing every
//! violation to stdout, or lists the registry. Gate semantics live in
//! `gates`; this handler only dispatches and reports.

use crate::cli::gate::GateArgs;
use crate::context::AppContext;
use crate::error::AppError;
use crate::gates::{GateCtx, spec};
use crate::output;

/// Run or list gates.
///
/// # Errors
///
/// [`AppError::Violations`] when the gate found any; I/O errors when it
/// could not run.
pub fn run(_ctx: &AppContext, args: GateArgs) -> Result<(), AppError> {
    let GateArgs { id, files, list } = args;
    if list {
        for gate in crate::gates::GATES {
            output::line(format!("{}: {}", gate.id, gate.name));
        }
        return Ok(());
    }
    let Some(id) = id else {
        return Err(AppError::Usage(
            "a gate id or --list is required".to_string(),
        ));
    };
    let gate_ctx = GateCtx::new(".");
    let violations = (spec(id).run)(&gate_ctx, &files)?;
    if violations.is_empty() {
        return Ok(());
    }
    for violation in &violations {
        output::line(violation);
    }
    Err(AppError::Violations {
        count: violations.len(),
    })
}