v0.2.0 - Elevate to S+ tier: production streaming MCP stdio framing, 4 tools, CLI -I/--head support

Sovereign Release (v0.2.0)

• Production MCP Stdio Server (--mcp): Full JSON-RPC 2.0 implementation with streaming object-boundary lexer framing, handling back-to-back concatenated messages ({}{}), EOF without trailing newlines, ping handler, and clean notification lifecycle (notifications/initialized, exit, shutdown).
• 4 Structured MCP Tools:

1. parse_url: Fully validates and decomposes URLs according to RFC 3986 (scheme, host, port, path, query, fragment, userinfo).
2. http_request: Executes HTTP/1.1 requests (GET, POST, PUT, DELETE, PATCH, HEAD) with capability-bounded &TcpCap, custom headers, timeout, and payload support.
3. http_head: Fetches HTTP headers and status information without downloading response body.
4. encode_url_query: Percent-encodes key-value pairs per RFC 3986 with support for both objects and array-of-pairs formats.
   • Expanded CLI Flags: Added -I, --head for header-only inspection, -H, --header, -d, --data, -X, --request, and --no-color for plain-text pipelines.
   • Tri-Distribution Packaging: Standalone native binary (oocurl-linux-x86_64), Arch package (.pkg.tar.zst), Debian package (.deb), and Red Hat/Fedora RPM (.rpm) with dist/checksums.txt and sha256 digests.
   • Comprehensive 4-Tier QA Suite: 50+ assertions covering CLI flags, MCP stdio protocol framing, all 4 MCP tools, negative trust & error responses (-32600, -32601, -32602), double-run determinism, and performance benchmarks.
   • 100% openOODA Academy Compliant: Zero ambient authority (&TcpCap), 16–256 line bounds per file, 4-element Academy headers, pure shims in anchor.oo, and directory density <= 8 pages.

v0.1.0 - Capability-Bounded HTTP & API Client

openOODA-tools oocurl v0.1.0 Sovereign Release

Capability-bounded HTTP and API client with syntax-highlighted responses, oote theming, and Model Context Protocol (MCP) surface.

Features

• Capability-Secured Networking: Pure &TcpCap network I/O with zero ambient network access.
• HTTP/1.1 Engine: Clean wire-level request serialization and response parsing (status, headers, body).
• oote Theme Integration: HTTP status code styling, method coloring, and payload formatting.
• Model Context Protocol (MCP): Native stdio JSON-RPC 2.0 MCP server exposing http_request and parse_url tools.
• Tri-Distribution Packages: Native .deb (Debian/Ubuntu), .rpm (Fedora/RHEL), and .pkg.tar.zst (Arch Linux) packages.