feat: add CLI tool execution with dynamic schema prompting

[MatthewGrigsby]

Description

Add CLI support for executing tools with dynamic JSON Schema prompting, so users can run tool calls from cforge without switching to the desktop app or admin UI.

Closes #5

Changes

• Add cforge tools execute <tool-id> command and wire it into cforge main command registration.
• Support optional --data <file.json> for prefilled arguments from a JSON object file.
• Add prompt_for_json_schema(...) in cforge/common.py to drive interactive prompts from dynamic JSON Schemas.
• Resolve local $ref / $defs references (including array/object references), detect cycles, and reject unsupported external references.
• Prompt only missing required fields when --data is provided.
• Improve plugin CLI UX:
  • Move case-insensitive enum helper to shared CaseInsensitiveEnum in cforge/common.py.
  • Parse plugins list --mode case-insensitively (e.g. --mode EnFoRcE).
  • Improve plugin 404 hinting to distinguish missing plugin (plugins get) from admin API unavailability.
• Add README examples for tools execute.

Testing

• uv run pytest --no-cov tests/commands/resources/test_tools.py tests/commands/resources/test_plugins.py tests/test_common.py
• uv run pytest -o addopts='' --cov=cforge.commands.resources.tools --cov=cforge.commands.resources.plugins --cov=cforge.common --cov-report=term-missing:skip-covered tests/commands/resources/test_tools.py tests/commands/resources/test_plugins.py tests/test_common.py
• Manual validation scenarios documented and exercised in test-cfg-cli/MANUAL_TEST_CASES.md for:
  • tools execute (interactive + --data)
  • $ref object/array schema handling
  • external $ref rejection
  • plugin mode case-insensitive parsing
  • plugin 404 hint behavior

Discussion

• prompt_for_json_schema currently supports local JSON Pointer references (#/...) and intentionally rejects external refs.
• Full-repo coverage remains governed by the repository’s global pytest coverage gate; this PR adds targeted coverage for the new command paths and helper logic.

Definition Of Done

• This PR contains documentation
  • Yes
  • NO (explain)
  • N/A
• This PR contains unit tests
  • Yes
  • NO (explain)
  • N/A
• This PR has been tested for backwards compatibility
  • Yes
  • NO (explain)
  • N/A

Follow-up update for a5aacb4

• Added targeted tests/test_common.py cases to fully cover prompt_for_json_schema edge paths ($ref, enum parsing, optional/required branches, scalar/array/object prompts,
  and additionalProperties behavior).
• Added minimal pragma annotations in cforge/common.py for defensive/unreachable branches only.
• Re-ran full suite: uv run pytest passes, and total coverage remains 100%.

[gabe-l-hart]

This is a great new feature! I've tested it directly and it works nicely for simple tool calls.

start mcp server

python3 -m mcpgateway.translate      --stdio "docker run --rm -i ghcr.io/ibm/fast-time-server:latest -transport=stdio"      --expose-sse      --port 9005

boot CF

rm tmp/*; CONTEXTFORGE_HOME=$PWD/tmp cforge serve --port 5555 --no-auth
# Register in the UI

test with prompting

PORT=5555 CONTEXTFORGE_HOME=$PWD/tmp cforge tools execute 7a43e085175545f58d214c329889d2a9

test with data

PORT=5555 CONTEXTFORGE_HOME=$PWD/tmp cforge tools execute 7a43e085175545f58d214c329889d2a9 --data <(echo '{"timezone": "EST"}')

---

I've got a few NITs and a large-ish request to refactor the new prompt_for_json_schema to avoid code duplication with prompt_for_schema.

[MatthewGrigsby]

@gabe-l-hart

I incorporated the refactor + NITs in the latest commits on this branch:

• Split the former monolithic cforge/common.py into cforge/common/ modules (console, errors, http, prompting, render, schema_validation) and mirrored the same split for tests by moving tests/test_common.py into tests/common/.
• prompt_for_schema and prompt_for_json_schema now share a single core implementation (_prompt_from_json_schema) in cforge/common/prompting.py; only schema construction differs.
• tools execute flow cleanup:
  • Validate --data (exists + JSON object) before fetching the tool (fail-fast).
  • Derive prefilled_data + prompt_optional once, and call prompt_for_json_schema(...) exactly once.
  • Removed defensive parsing for stringified inputSchema; it must be a JSON object (or we fall back to an empty object schema when missing).
• Plugins --mode case-insensitivity: switched mode to str + _parse_plugin_mode() so mixed-case values (e.g. EnFoRcE) don’t fail early in Click/Typer enum validation; added coverage.
• Prompt schema validation regression: skip final jsonschema validation for prompt_for_schema (Pydantic-derived prompt schema is intentionally lossy for some types), while keeping validation for real JSON Schemas; added regression coverage.
• Deps: added jsonschema to pyproject.toml because prompt_for_json_schema now validates prompted payloads against JSON Schema (tool inputSchema) before execution; also bumped the Typer minimum version.

Tests: python -m pytest -q is green. Manual test cases also pass.

[gabe-l-hart]

I love the blowup of common.py. Much more understandable now. I do have some questions about whether we can use some more standardized jsonschema and pydantic functions to reduce the type/schema munging a bit.

[gabe-l-hart]

Almost there! A few small change requests left:

• Remove the dead function in prompting.py
• Comment for why we retain the local-only $ref resolution vs using third party
• Revert changes to .gitignore (unless you want to discuss this one further)
• Open question on dependency lower-bound bump

[gabe-l-hart]

Ship it! Thanks for this great progress