fix: support /plugins slash command in resume mode

[code-yeongyu]

Bug

claw --resume session.jsonl /plugins --output-format json returns:

{"command":"/plugins","error":"unsupported resumed slash command","type":"error"}

But /mcp and /skills both work in resume mode. The /plugins handler exists in the REPL and non-resume CLI paths — it was just never wired into run_resume_command.

Fix

• Move SlashCommand::Plugins out of the unsupported catch-all in run_resume_command
• Add a handler arm that calls handle_plugins_slash_command for list/help
• Mutation actions (install/uninstall/enable/disable) are rejected with a clear error since there is no runtime to reload in resume mode
• Add /plugins coverage to resumed_inventory_commands_emit_structured_json_when_requested test

Verification

cargo test -p rusty-claude-cli -- resumed_inventory_commands
# 1 passed, 0 failed

Before: exit 1, error envelope
After: exit 0, {kind: "plugin", action: "list", reload_runtime: false, target: null, message: "..."}

[Yeachan-Heo]

Review verdict: REQUEST_CHANGES

Reviewed current head 39bae88 against current base 8e45f185. CI is green: cargo fmt, clippy, test, and docs source-of-truth all pass.

Changed files:

• rust/crates/rusty-claude-cli/src/main.rs
• rust/crates/rusty-claude-cli/tests/output_format_contract.rs

Local targeted tests passed:

• cargo test -p rusty-claude-cli --test output_format_contract resumed_inventory_commands_emit_structured_json_when_requested -- --nocapture
• cargo test -p rusty-claude-cli direct_slash_commands_surface_shared_validation_errors -- --nocapture
• cargo test -p commands validate_slash_command_input_rejects_extra_single_value_arguments -- --nocapture

I also manually exercised resume-mode /plugins commands against the built binary.

This PR changes user-facing resume-mode slash/JSON behavior, so owner confirmation is required before merge even after blockers are fixed.

Blockers:

1. /plugins update <id> is still allowed through resume mode.

The new resume handler rejects install, uninstall, enable, and disable, but not update. The parser supports ["update", target] as SlashCommand::Plugins { action: Some("update"), ... }, and handle_plugins_slash_command can perform manager.update(...) with reload_runtime: true.

Manual evidence: /plugins update demo reaches the plugin update path and errors only because demo is not installed. If the plugin exists, this can mutate plugin state in resume mode without runtime reload.

2. Claimed list/help support is incomplete: /plugins help and /plugins --help fail before the resume handler.

The resume handler comment says only list/help are supported, but parse_plugin_command does not parse help or --help as a valid plugin action. Manual results for /plugins help, /plugins --help, /plugin help, and /plugin --help are errors/exit 2.

Requested changes:

• Reject update in resume mode alongside the other mutation commands.
• Either implement /plugins help / /plugins --help parsing and resume output, or remove the help-support claim from PR description/comment/tests.
• Add regression tests for /plugins update <id> being rejected in resume mode before mutation. Ideally cover all mutation verbs: install/uninstall/enable/disable/update.
• If help is intended, add tests for /plugins help and/or /plugins --help; if not, make the contract list-only.

Merge risk: medium until mutation handling is fixed; likely low after fixes, subject to owner confirmation of the new resume-mode /plugins JSON contract.

—
[repo owner's gaebal-gajae (clawdbot) 🦞]

[Yeachan-Heo]

Re-review verdict: APPROVE

Reviewed current head ae65619cd9eb342974a0c182d4fa4d56a70160b3 after the REQUEST_CHANGES fix.

Previous blockers are resolved:

1. /plugins update <id> is now rejected in resume mode before plugin manager construction / handler dispatch.

   • main.rs now rejects install, uninstall, enable, disable, and update.
   • Plugin manager setup happens after this guard, so update cannot reach the mutation path in resume mode.

2. The false list/help claim is removed.

   • The contract/comment now says list-only: Only list is supported in resume mode (no runtime to reload).

CI for ae65619 is green 4/4:

• cargo clippy --workspace: success
• cargo fmt: success
• cargo test --workspace: success
• docs source-of-truth: success

Targeted verification:

• cargo test -p rusty-claude-cli --test output_format_contract resumed_inventory_commands_emit_structured_json_when_requested -- --nocapture passed.
• Manual smoke: --resume <session> /plugins returns JSON with kind=plugin, action=list, target=null, reload_runtime=false.
• Manual smoke: --resume <session> /plugins update bogus exits nonzero with the interactive-only resume mutation error.
• Update-first smoke confirmed no plugin registry file was created before rejection.

Merge risk: LOW.

Blockers: none from code review.

Process gate: owner confirmation is still required before merge because this changes user-facing resume-mode /plugins slash/JSON behavior.

—
[repo owner's gaebal-gajae (clawdbot) 🦞]

[TheArchitectit]

Review Checklist

User-facing behavior added

• /plugins slash command now works in resume mode (claw --resume session.jsonl /plugins --output-format json)
• List/help actions work; mutation actions (install/uninstall/enable/disable) rejected with clear error (no runtime to reload)

Config keys / CLI flags changed

• No new config — fixes existing /plugins command in resume mode

Migration or compatibility notes

• No breaking changes — bug fix for previously unsupported path
• Mutation actions intentionally rejected in resume mode (no runtime to reload plugins)

Tests run locally

• resumed_inventory_commands_emit_structured_json_when_requested now covers /plugins
• cargo test -p rusty-claude-cli -- resumed_inventory_commands passes

Known risks / non-goals

• Non-goal: Mutation actions remain unsupported in resume mode — intentional limitation

[code-yeongyu]

QA FAIL: resumed_status_command_emits_structured_json_when_requested test fails on this branch — left: Some(1) vs right: Some(0) (exit code 1 instead of 0 for --resume SESSION /status --output-format json). Likely a regression introduced by the plugins fix. Needs investigation before merge.

[code-yeongyu]

QA note: resumed_status_command_emits_structured_json_when_requested fails on this branch but this is a pre-existing failure on main — not introduced by this PR. The test expects exit 0 but gets exit 1 for --resume SESSION /status --output-format json. This is a main regression that needs fixing separately before these PRs can show clean CI on that specific test.