Yeachan-Heo e102af6ef3 Honor project permission defaults when CLI has no override ... Runtime config already parsed merged permissionMode/defaultMode values, but the CLI defaulted straight from RUSTY_CLAUDE_PERMISSION_MODE to danger-full-access. This wires the default permission resolver through the merged runtime config so project/local settings take effect when no env override is present, while keeping env precedence and locking the behavior with regression tests. Constraint: Must preserve explicit env override precedence over project config Rejected: Thread permission source state through every CLI action | unnecessary refactor for a focused parity fix Confidence: high Scope-risk: narrow Directive: Keep config-derived defaults behind explicit CLI/env overrides unless the upstream precedence contract changes Tested: cargo test -p rusty-claude-cli permission_mode -- --nocapture Tested: cargo test -p rusty-claude-cli defaults_to_repl_when_no_args -- --nocapture Not-tested: interactive REPL/manual /permissions flows		2026-04-02 10:02:26 +00:00
..
src	Honor project permission defaults when CLI has no override	2026-04-02 10:02:26 +00:00
tests	test(cli): expand integration tests for CLI args, config, and slash command dispatch	2026-04-02 18:11:25 +09:00
Cargo.toml	Merge remote-tracking branch 'origin/rcc/hook-pipeline' into integration/dori-cleanroom	2026-04-02 11:05:03 +09:00