Skip to content

feat: add TreadFi CLI status skeleton#39

Open
JaeLeex wants to merge 3 commits into
mainfrom
jl/treadfi-cli-skeleton
Open

feat: add TreadFi CLI status skeleton#39
JaeLeex wants to merge 3 commits into
mainfrom
jl/treadfi-cli-skeleton

Conversation

@JaeLeex

@JaeLeex JaeLeex commented Jun 16, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Adds a read-only hl treadfi command group for contract status, capability placeholders, and BTCSWP local identifiers.
  • Shares behavior through a JSON-friendly contract module so MCP tools can reuse it later.

Test plan

  • python3 -m pytest tests/test_treadfi_contract.py

Made with Cursor

JaeLeex and others added 2 commits June 16, 2026 12:46
Expose read-only TreadFi contract status through `hl treadfi` so agents can see what is blocked without calling invented endpoints.

Co-authored-by: Cursor <cursoragent@cursor.com>
Add explicit read-only FastMCP tools for TreadFi contract status so agents can discover the blocked integration state.

Co-authored-by: Cursor <cursoragent@cursor.com>

@sdb001 sdb001 left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed. The CLI status skeleton stays read-only and accurately reports TreadFi as blocked until endpoint/tool fixtures exist. Verified on the stacked TreadFi branch: tests/test_treadfi_contract.py + tests/test_treadfi_mcp.py passed (5 passed), plus hl treadfi spec-status and market-params smoke checks returned the expected blocked/local BTCSWP payloads.

feat: expose TreadFi status over MCP
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants