feat(cli): unify runtime-input prompting across declarative flows and crews

Declarative (JSON) crews now resolve inputs the same way declarative flows
do, via a shared crewai_cli.input_prompt module (prompt_for_inputs,
parse_inputs_json, closest_name, is_interactive):

- accept --inputs (previously rejected for crews), forwarded to the crew
  subprocess via CREWAI_JSON_CREW_INPUTS and validated before spinning up uv
- layer --inputs over the crew's declared `inputs` defaults
- prompt for missing {placeholder}s with the same UX as flows, and error
  cleanly with a pointed per-name message when non-interactive
- warn on unknown keys with a "did you mean" suggestion

Unlike flows — whose state schema is authoritative, so unknown keys are
dropped — the crew placeholder scan is heuristic (agent/task text fields
only), so unrecognized keys are warned about but kept, to avoid discarding a
value a field the scan doesn't cover may rely on.

--inputs remains rejected for classic (Python/YAML) crews, which take their
inputs from main.py. run_declarative_flow's private input helpers move to the
shared module with no behavior change.

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

lib/cli/tests/test_input_prompt.py

@@ -0,0 +1,83 @@
+"""Tests for the shared runtime-input prompting used by flows and crews."""
+
+from __future__ import annotations
+
+import pytest
+
+import crewai_cli.input_prompt as input_prompt_module
+from crewai_cli.input_prompt import (
+    closest_name,
+    parse_inputs_json,
+    prompt_for_inputs,
+)
+
+
+def test_parse_inputs_json_returns_none_for_none():
+    assert parse_inputs_json(None) is None
+
+
+def test_parse_inputs_json_parses_object():
+    assert parse_inputs_json('{"topic": "AI"}') == {"topic": "AI"}
+
+
+def test_parse_inputs_json_rejects_invalid_json(capsys):
+    with pytest.raises(SystemExit) as exc_info:
+        parse_inputs_json("not json")
+
+    assert exc_info.value.code == 1
+    assert "Invalid --inputs JSON" in capsys.readouterr().err
+
+
+def test_parse_inputs_json_rejects_non_object(capsys):
+    with pytest.raises(SystemExit) as exc_info:
+        parse_inputs_json("[1, 2, 3]")
+
+    assert exc_info.value.code == 1
+    assert "expected an object" in capsys.readouterr().err
+
+
+def test_closest_name_suggests_near_miss():
+    assert closest_name("prospect_emai", ["prospect_email", "topic"]) == "prospect_email"
+
+
+def test_closest_name_returns_none_when_nothing_close():
+    assert closest_name("zzzzz", ["prospect_email", "topic"]) is None
+
+
+def test_prompt_for_inputs_uses_describe_and_coerce(monkeypatch, capsys):
+    seen: list[str] = []
+
+    def fake_prompt(text: str, **kwargs: object) -> str:
+        seen.append(text)
+        return "42"
+
+    monkeypatch.setattr(input_prompt_module.click, "prompt", fake_prompt)
+
+    result = prompt_for_inputs(
+        ["count"],
+        title="Flow inputs",
+        subtitle="This flow needs the following to run.",
+        describe=lambda name: f"How many {name}?",
+        coerce=lambda name, raw: int(raw),
+    )
+
+    captured = capsys.readouterr()
+    assert result == {"count": 42}
+    assert any("count" in text for text in seen)
+    # Header, subtitle, and description hint all render on stderr.
+    assert "Flow inputs" in captured.err
+    assert "How many count?" in captured.err
+
+
+def test_prompt_for_inputs_keeps_raw_string_without_coerce(monkeypatch):
+    monkeypatch.setattr(
+        input_prompt_module.click, "prompt", lambda text, **kwargs: "AI"
+    )
+
+    result = prompt_for_inputs(
+        ["topic"],
+        title="Crew inputs",
+        subtitle="This crew needs the following to run.",
+    )
+
+    assert result == {"topic": "AI"}