trusty-mpm 1.3.5

trusty-mpm: unified multi-agent orchestration platform (core, daemon, CLI, TUI, Telegram)
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
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63

//! `tm repair` deploy-state recovery command group.
//!
//! Why: extracted from `cli.rs` (issue #2603) to keep the top-level file
//! under the 500-SLOC production cap.
//! What: [`RepairAction`] — `deploy` and `push-guard`.
//! Test: `cli_parses_repair_deploy`, `cli_parses_repair_push_guard` in `tests.rs`.

use clap::Subcommand;

/// Actions for the `repair` subcommand.
///
/// Why: scoped sub-actions keep `tm repair` extensible — future variants can
/// cover other deploy artefacts without changing the top-level command surface.
/// What: `Deploy` covers agent and skill manifests; `PushGuard` retrofits the
/// #2867 cross-branch push guard onto an already-provisioned clone.
/// Test: `cli_parses_repair_deploy`, `cli_parses_repair_push_guard`.
#[derive(Debug, Subcommand)]
pub(crate) enum RepairAction {
    /// Repair the agent/skill deploy state in `~/.claude/`.
    ///
    /// Why: a crash during `tm install` or `tm sessions start` may leave stale
    /// `.tmp` staging files in `~/.claude/agents/` or `~/.claude/skills/`, or
    /// leave either manifest corrupt. This command removes the orphans and
    /// validates both manifests.
    /// What: for each target directory (`~/.claude/agents/`, skill subdirs under
    /// `~/.claude/skills/`), removes `*.tmp` orphans and validates the manifest.
    /// With `--force`, resets a corrupt agent manifest to empty so the next
    /// `tm install` performs a fresh full deploy.
    /// Test: `cli_parses_repair_deploy`.
    Deploy {
        /// Reset a corrupt manifest to empty (triggers full re-deploy on next
        /// `tm install`). Without this flag, a corrupt manifest is reported
        /// but not modified.
        #[arg(long)]
        force: bool,
    },

    /// Retrofit the #2867 cross-branch `pre-push` guard onto an existing clone.
    ///
    /// Why: the guard is installed automatically only when trusty-mpm CLONES a
    /// repository, so every base clone that already existed when the guard
    /// shipped is unprotected — including long-lived ones shared by dozens of
    /// worktrees, which is exactly the population #2867 happened in. Without
    /// this verb there is no supported way to close that gap.
    /// What: installs the guard into the clone's SHARED hooks directory
    /// (`$GIT_COMMON_DIR/hooks`), which every linked and ad-hoc worktree of
    /// that clone consults — so one invocation from any worktree covers them
    /// all, with no git config write. Idempotent: re-running an up-to-date
    /// guard writes nothing. It never overwrites a `pre-push` it does not own
    /// (a foreign hook, a symlink, an unreadable file, or a `core.hooksPath`
    /// redirect all produce a refusal that names the reason). `--dry-run`
    /// reports what would happen and writes nothing at all.
    /// Test: `cli_parses_repair_push_guard`, `cli_parses_repair_push_guard_flags`.
    PushGuard {
        /// Repository (or any worktree of it) to protect. Defaults to the
        /// current directory.
        #[arg(long)]
        path: Option<String>,
        /// Report what would happen without writing anything.
        #[arg(long)]
        dry_run: bool,
    },
}