2 Commits

Include renames

Author	SHA1	Message	Date
Illia PolosukhinandClaude Opus 4.5	598dd43b1c	Rebrand to IronClaw with security-first mission ... Renamed project from "near-agent" to "ironclaw" throughout the codebase. Updated documentation to emphasize the core philosophy: - Your data stays yours (local, encrypted, no telemetry) - Self-expanding capabilities (build tools on the fly) - Defense in depth (WASM sandbox, prompt injection defense) - Always on user's side Key changes: - Package name: near-agent -> ironclaw - Config paths: ~/.near-agent/ -> ~/.ironclaw/ - Database name in docs: near_agent -> ironclaw - CLI binary: near-agent -> ironclaw - Log filters: RUST_LOG=near_agent -> RUST_LOG=ironclaw - All user-facing strings (welcome messages, help text, etc.) Preserved for compatibility: - HKDF salt "near-agent-secrets-v1" (changing would break existing secrets) - WIT interface names (near::agent::*) - NEAR AI provider config (NEARAI_* env vars) Co-Authored-By: Claude Opus 4.5 <[email protected]>	2026-02-05 01:10:40 -08:00
Illia PolosukhinandClaude Opus 4.5	e6946172f7	Apply Telegram channel learnings to WhatsApp implementation ... - Fix metadata flow: store sender_phone for response routing - Add credential injection in headers (Bearer {WHATSAPP_ACCESS_TOKEN}) - Add secret_validated check for webhook defense in depth - Add status message filtering to prevent loops - Add proper WhatsApp API error response parsing - Create whatsapp.capabilities.json with setup/secrets/rate limits - Add docs/BUILDING_CHANNELS.md with patterns and examples Also fix UTF-8 truncation bugs across codebase: - wrapper.rs: content preview, response body, webhook body logging - agent_loop.rs: params truncation for approval display - shell.rs: truncate_for_error() helper Co-Authored-By: Claude Opus 4.5 <[email protected]>	2026-02-04 22:32:23 -08:00