fix(cli): don't block persistence-restore resume on schema validation

Cursor (High): `crewai run --inputs '{"id":"…"}'` is a persistence resume —
kickoff hydrates full state from storage, so schema-required fields may come
from the restored state rather than --inputs. The new required-field
prompt/validation was erroring/prompting before kickoff, breaking resume. When
`id` is present in --inputs, forward the inputs unchanged and skip the
prompt/validation. Test: test_id_only_input_skips_required_validation.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01RBYGqJHC2TMC6fonFziuuh

lib/cli/tests/test_run_declarative_flow.py

@@ -351,3 +351,14 @@ def test_reserved_id_input_is_forwarded_not_dropped(
     captured = capsys.readouterr()
     assert captured.out == "a@b.com\n"
     assert "Ignoring unknown input 'id'" not in captured.err
+
+
+def test_id_only_input_skips_required_validation(tmp_path: Path) -> None:
+    # Resume via `crewai run --inputs '{"id":"..."}'` must not be blocked by the
+    # required-field check: kickoff hydrates required state from persistence.
+    path = _write(tmp_path, REQUIRED_FLOW_YAML)
+    flow = run_declarative_flow_module.load_declarative_flow(str(path))
+
+    resolved = run_declarative_flow_module._resolve_flow_inputs(flow, {"id": "run-123"})
+
+    assert resolved == {"id": "run-123"}