3 Commits

Author	SHA1	Message	Date
rob	8eff55ed1e	Add tool settings files for configurable tool defaults ... Tools can now ship with defaults.yaml containing configurable settings that users can customize via settings.yaml (auto-created from defaults). Features: - ensure_settings() helper copies defaults to settings on first use - Settings available as {settings.key} in templates (scalars only) - Full dict access via settings['key'] in code steps - CLI: cmdforge settings <tool> show/edit/reset/diff - GUI: Defaults editor in Tool Builder, Configure button on Tools page - Registry: defaults.yaml published with tools, included in downloads - Secret detection warning on publish (api_key, password, token, etc.) Fully backward compatible - tools without defaults work unchanged. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>	2026-01-27 11:56:07 -04:00
rob	0d91eb7fa0	Update olddocs to reflect current implementation state ... - REGISTRY.md: Mark phases 1-4, 6-8 complete; phase 5 partial - WEB_UI.md: Update Phase 7 checklist with completion status - DESIGN.md: Note TUI replaced by PySide6 GUI, update structure - PROJECT.md: Update source structure and database schema - PROVIDERS.md, META_TOOLS.md, COLLECTIONS.md: Add status notes - Add "Features Implemented Beyond Original Design" sections Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>	2026-01-17 03:35:42 -04:00
rob	9fbe45244d	Move docs to project-docs symlink structure ... - Docs now point to project-docs/docs/projects/cmdforge - Old docs preserved in olddocs/ - Updated .gitignore to ignore docs symlink 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>	2026-01-06 22:26:39 -04:00