614 Commits

Author	SHA1	Message	Date
HAL9000	35bf1d6962	[AUTO-TIME-1] Update timeline: schedule adherence 2026-04-17	2026-06-03 22:29:32 -04:00
HAL9000	8170dabb4f	docs(timeline): [AUTO-TIME-2] update schedule adherence 2026-04-18 with changelog and contributor entries ... - Add Schedule Adherence tables for 2026-04-18 (M3-M10) - Add Daily Snapshot section with milestone risk assessments - Fix missing newline at end of timeline table content - Update CHANGELOG.md under [Unreleased] with entry for timeline snapshot - Update CONTRIBUTORS.md with HAL 9000 contribution entry - Proper newline termination before new markdown table sections ISSUES CLOSED: #10288 Epic reference: Tracking issue #8519 (AUTO-TIME supervisor) Automated by CleverAgents Bot Supervisor: Timeline Update | Agent: timeline-update-pool-supervisor	2026-06-03 22:07:47 -04:00
CleverAgents Bot	5ca87cd5af	docs(v3.6.0-v3.7.0): add comprehensive feature documentation and guides ... - Add v3.6.0 features guide covering advanced context management, enhanced security profiles, improved observability, performance optimizations, and API enhancements - Add v3.7.0 features guide covering TUI redesign, Agent-to-Agent Communication (A2A), enhanced automation execution, advanced skill management, and improved developer experience - Add comprehensive v3.7.0 TUI guide with detailed navigation, management interfaces, keyboard shortcuts, and advanced features - Add v3.7.0 A2A protocol specification covering message format, transport layers, authentication, error handling, and multi-agent orchestration - Add v3.6.0-v3.7.0 release notes with upgrade paths, deprecation timeline, and migration guides - Include practical examples and best practices for all major features - Ensure all documentation is properly formatted with table of contents and cross-references This documentation audit and update provides comprehensive coverage of v3.6.0 and v3.7.0 features with examples, ensuring users can effectively utilize new capabilities.	2026-06-03 21:06:30 -04:00
HAL9000	0aacec7845	fix(cli): address PR #6626 review blockers for context set output ... - Fix ruff import ordering in project_context_cli_steps.py (yaml moved to third-party section) - Remove unused noqa: F401 suppression in rendering/__init__.py - Add *args, **kwargs to _test_format_output stub in coverage boost steps (fixes TypeError) - Extract context-set step definitions into dedicated module (project_context_set_steps.py) to bring project_context_cli_steps.py under 500-line limit (469 -> 316 lines) - Revert spec changes for context show/inspect/simulate message format (bare strings) to keep PR focused on issue #6319 (context set only),	2026-06-03 17:30:22 -04:00
HAL9000	388fc458c5	fix(cli): fix project context set JSON/YAML output structure (#6319) ... Implemented spec-compliant JSON, YAML, plain, and rich outputs for `agents project context set`. Added BDD coverage verifying the new output structure across formats.\n\nISSUES CLOSED: #6319	2026-06-03 17:30:22 -04:00
HAL9000	46fff75c1a	docs: add v3.2.0 and v3.3.0 feature documentation [AUTO-DOCS-2]	2026-06-03 15:56:46 -04:00
CleverAgents Bot	70517398a6	[AUTO-TIME-1] Day 105 timeline update — 2026-04-15 ... Update schedule adherence and milestone progress: - v3.2.0: 26% complete (933 open) - v3.3.0: 36% complete (212 open) - v3.4.0: 37% complete (158 closed / 427 total) - v3.5.0: 18% complete (1,107 open) - v3.6.0: 33% complete (329 open) - v3.7.0: 42% complete (603 open) - v3.8.0: 29% complete (364 open) - v3.9.0: 41% complete (35 open) Automated by CleverAgents Bot	2026-06-03 11:55:34 -04:00
HAL9000	b31d52fe0e	docs(spec): clarify Anonymous Tool enforcement rules in glossary ... Expands the Anonymous Tool glossary entry to explicitly document: - Anonymous tools are never passed to ToolRegistry.register() - Name field is required but context-local (no namespace prefix) - Attempting global registration raises ToolError - Namespacing requirement applies only to registered tools Closes #8799. [AUTO-ARCH-14]	2026-06-03 00:24:21 -04:00
HAL9000	7ba1e5737f	docs(spec): document context_tier_hydrator module in ACMS architecture section ... Adds Context Tier Hydration subsection to the ACMS Architecture section of the specification, documenting the context_tier_hydrator module's public interface (hydrate_tiers_for_plan, hydrate_tiers_from_project), file listing strategy (git ls-files for git-checkout resources, os.walk fallback), budget limits (256 KB per file, 10 MB total per project), and fragment structure (TieredFragment with ContextTier.HOT placement, metadata keys path/detail_depth/relevance_score). Also updates CHANGELOG.md under [Unreleased] > Documentation and adds contribution entry to CONTRIBUTORS.md. ISSUES CLOSED: #6175	2026-06-02 23:07:34 -04:00
HAL9000	5e89f1016c	refactor(subplans): Centralize subplan errors per v3.3.0 spec (#8725) ... Move SubplanSpawnError from local subplan_service definition to centralized cleveragents.core.exceptions alongside four new spec-defined error types: SubplanExecutionError, MaxParallelExceededError, and SubplanDepthLimitError. Per the v3.3.0 specification (AUTO-ARCH-6), all subplan-related errors are defined in exceptions.py with proper inheritance hierarchy under DomainError/ PlanError/BusinessRuleViolation. The old local SpawnValidationError class has been replaced with SubplanSpawnError(PlanError) with a simplified constructor API (message string instead of validation_errors list). Updates: - exceptions.py: Added 4 subplan error classes + __all__ entries - subplan_service.py: Remove local SpawnValidationError, import SubplanSpawnError from exceptions - services/__init__.py: Update TYPE_CHECKING stub and _LAZY_IMPORTS for new location - vulture_whitelist.py: Replace old entry with new error class names - docs/reference/subplan_service.md: Update to reference SubplanSpawnError (v3.3.0) - features/*.feature + steps: Update test references from SpawnValidationError to SubplanSpawnError	2026-06-02 19:50:41 -04:00
HAL9000	bc6677b3cd	feat(subplans): Subplan System Specification and Invariant Enforcement v3.3.0 (#8725) ... Add comprehensive Subplan System specification defining module boundaries, data models (Subplan, SubplanResult, SubplanTree), PostgreSQL schema with indexes, the 8-step spawning algorithm, concurrency control via per-plan semaphores, and error handling. Implement invariant loading and enforcement in Strategize phase: - Add InvariantViolationError exception class - Add load_active_invariants() and check_invariants() methods to InvariantService - Add _is_violation heuristic for action/invariant matching - Add BDD tests with @load_invariants, @check_invariants, etc. tags ISSUES CLOSED: #8725	2026-06-02 19:50:41 -04:00
HAL9000	8ebd922e77	docs(specification): add deleted_at field to agents project delete JSON/YAML output ... Updated docs/specification.md to document the correct JSON/YAML output structure for the project delete command, replacing the legacy deletion_summary object with the deleted, success, and deleted_at fields that match the actual implementation introduced in PR #6639. Added BDD feature file and step definitions to validate the output format. ISSUES CLOSED: #7872	2026-06-02 04:09:01 -04:00
HAL9000	f7ce8f0093	fix: update pr-review-pool-supervisor tracking prefix from AUTO-REV-POOL to AUTO-REV-SUP ... - Updated pr-review-pool-supervisor.md tracking prefix from AUTO-REV-POOL to AUTO-REV-SUP - Updated automation-tracking.md table and search query to use AUTO-REV-SUP - Updated agent-system-specification.md all references from AUTO-REV-POOL to AUTO-REV-SUP - Aligns documentation with actual production tracking prefix ISSUES CLOSED: #7891	2026-06-02 00:58:16 -04:00
HAL9000	518c40be21	docs: document 2026-04-06 to 2026-04-08 improvements ... - add changelog entries summarizing watchdog supervision and documentation updates\n- add ci-log-fetcher module guide detailing interface contract and usage\n- refresh system-watchdog doc with CI-blocker escalation and struggling PR detection\n- normalize coverage threshold robot test by dropping temporary tdd_expected_fail tags\n\nISSUES CLOSED: #7987	2026-05-31 09:38:17 -04:00
freemo	1fd4918be8	docs(spec): clarify TUI session export formats and persona schema fields ... Accept implementation extensions as spec updates based on UAT findings: 1. `/session:export` now officially supports three formats: - `json` (default, canonical, importable) - `md` (Markdown transcript, lossy) - `txt` (plain-text transcript, lossy) Updated ADR-046 command table and spec Conversation Export section. 2. Persona data model now includes two optional display fields: - `icon`: emoji or single character for tab labels and lists - `greeting`: message shown when persona is activated Updated ADR-045 data model YAML example and Decision section. These changes accept positive implementation extensions discovered by UAT testing (issues #4871, #4858) rather than reverting them. Refs: #4940	2026-05-31 08:35:06 -04:00
HAL9000	bc64074036	docs: add tool and validation management showcase ... - document the CLI workflow for registering tools, wrapping validations, and querying registry metadata - index the new example in docs/showcase/examples.json - re-enable coverage threshold regression checks by removing obsolete tdd_expected_fail tags ISSUES CLOSED: #4565 Refs: #4305 Refs: #4227	2026-05-30 17:21:55 -04:00
HAL9000	fc0366d05a	fix(docs): correct SDK link from a2aprojects to a2aproject ... The SDK URL was incorrectly changed to a2aprojects/a2a-python (404 broken link). Revert to the correct a2aproject/a2a-python which is the official A2A Python SDK org. Fixes blocker from PR review.	2026-05-30 09:33:19 -04:00
freemo	9b64297eff	docs(a2a): fix SSE streaming event example method name ... Corrects the Example Streaming Event in docs/reference/a2a.md to use the correct JSON-RPC 2.0 notification method name `task/statusUpdate` instead of the incorrect `message/stream`. `message/stream` is the client→server REQUEST method that initiates streaming. The actual SSE data payloads are JSON-RPC 2.0 notifications (no `id` field) with method names `task/statusUpdate` or `task/artifactUpdate`, as implemented in SseEventFormatter. Closes #2519	2026-05-30 09:33:19 -04:00
CoreRasurae	3e13411fcf	fix(actors): distinguish namespace/name from provider/model in actor name parsing ... When action YAML references actors using namespace/name format (e.g. `strategy_actor: local/my-strategist`), `_parse_actor_name()` incorrectly treated the namespace prefix as a provider name, causing `ValueError: Unknown provider type: local`. Changes: - `_is_known_provider()`: New utility function (strategy_resolution.py) that checks whether a slash-separated first segment matches a known `ProviderType` value (openai, anthropic, etc.). Consolidated into a single implementation; llm_actors.py now imports from strategy_resolution.py. - `_parse_actor_name()`: When the first segment IS a known provider, preserves existing behaviour (provider/model). When it is NOT a known provider, treats the input as namespace/name and returns the full name as the model identifier with the default provider. Callers SHOULD pre-resolve namespace/name references via the actor registry before calling this function. Both implementations (strategy_resolution.py and llm_actors.py) updated; ProviderType import moved to top level. - `PlanLifecycleService.resolve_actor_provider_model()`: New method that resolves a namespaced actor name (e.g. local/my-strategist) to provider/model format by looking up the actor record and extracting its provider and model fields. - `LifecycleService` Protocol (strategy_resolution.py): Added `resolve_actor_provider_model` to the protocol, eliminating the need for `# type: ignore[union-attr]` at call sites. - `PlanLifecycleProtocol` (llm_actors.py): Added `resolve_actor_provider_model` to the protocol. - Caller pre-resolution: StrategyActor, LLMStrategizeActor, LLMExecuteActor, SessionWorkflow._resolve_llm(), and CLI session commands now pre-resolve actor names through the lifecycle service or via injected actor_resolver callables before calling `_parse_actor_name()`, ensuring namespace/name references are correctly mapped to their underlying LLM providers. - `_build_actor_resolver()` (cli/commands/session.py) and `_build_actor_resolver_for_session_workflow()` (a2a/facade.py): Moved `_is_known_provider` imports to top level; removed redundant `except (NotFoundError, Exception)`; added warning logging for outer exception handlers. - `make_mock_lifecycle()` (mock_strategy_llm.py) and `_make_mock_lifecycle()` (llm_actors_coverage_steps.py): Added `resolve_actor_provider_model` to mock lifecycle services for test compatibility. - Added `@tdd_issue @tdd_issue_11254` tags to all new BDD scenarios related to namespace/name disambiguation in llm_actors_coverage, strategy_actor_llm, and plan_lifecycle_service_coverage_boost_r4 feature files. - Updated docs/CHANGELOG.md with the fix entry. ISSUES CLOSED: #11254	2026-05-22 20:42:25 +01:00
CoreRasurae	8548644819	fix(cli): wire SubplanExecutionService in _get_plan_executor() to enable child plan execution ... Wire subplan_service from the DI container into _get_plan_executor() so PlanExecutor can spawn child plans during the Execute phase. When SubplanService is available but SubplanExecutionService is not explicitly injected, _execute_subplans() now lazily creates a SubplanExecutionService on-the-fly using the parent plan's subplan_config and the new _execute_child_plan callback. - _get_plan_executor(): retrieve subplan_service from container, pass to PlanExecutor constructor - _execute_subplans(): lazily build SubplanExecutionService when only SubplanService is wired (Forgejo #10268) - _execute_child_plan(): new PlanExecutor method that runs a child plan's strategize + execute phases, registered as executor_fn callback ISSUES CLOSED: #10268	2026-05-19 19:28:35 +01:00
HAL9000	2cba7d41bc	chore(agents): fix bug-hunt-pool-supervisor tracking prefix AUTO-BUG-POOL to AUTO-BUG-SUP (complete fix) ... Replace all remaining AUTO-BUG-POOL references with correct AUTO-BUG-SUP in agent-system-specification.md, automation-tracking.md documentation and agent-system-specification.md spec document, replaced with correct `AUTO-BUG-SUP` prefix used by the bug-hunt-pool-supervisor agent (#7875). ISSUES CLOSED: #7875	2026-05-09 00:05:17 +00:00
HAL9000	57881a075b	docs(spec): update specification — validation gate blocks on empty validation summary	2026-05-08 19:14:24 +00:00
HAL9000	a130d63357	docs(timeline): update schedule adherence Day 101 (2026-04-12) (#7858)	2026-05-08 10:21:23 +00:00
HAL9000	3d7afb4378	fix(resource): wire discover_devcontainers() into git-checkout and fs-directory handlers ... GitCheckoutHandler.discover_children() and FsDirectoryHandler.discover_children() now call discover_devcontainers() after scanning for fs-directory children. Any .devcontainer/devcontainer.json or root-level .devcontainer.json found at the resource location is registered as a devcontainer-instance child resource with provisioning_state: discovered. Named configurations are also discovered and carry the configuration name in the config_name property. This wires the previously-isolated discover_devcontainers() function into the production code path, enabling the spec's zero-configuration devcontainer experience. ISSUES CLOSED: #4740	2026-05-07 23:49:20 +00:00
HAL9000	2778bde95a	fix(repositories): derive PlanResult.success from result_success column instead of error_message ... ISSUES CLOSED: #7501	2026-05-07 14:22:57 +00:00
HAL9000	f2d1f4efe7	docs: fix quickstart plan/apply command signatures ... Update docs/quickstart.md to use correct CLI command signatures: - Replace 'cleveragents plan --project' with 'cleveragents plan use <action> --project' - Replace 'cleveragents apply --project' with 'cleveragents plan list' + 'cleveragents plan apply <plan-id>' Addresses reviewer non-blocking suggestion to verify CLI commands match actual signatures before merging.	2026-05-06 04:29:40 +00:00
HAL9000	54fef4768c	docs: add quick start guide (PR #9245) ... Add docs/quickstart.md with end-to-end quick start guide covering prerequisites, installation, project creation, resource registration, plan/apply workflow, and troubleshooting. Update mkdocs.yml navigation to include Quick Start page and rename ADR-028 title to Skill/Tool Abstraction Definition. Update CHANGELOG.md with quick start guide entry. Closes #9245	2026-05-06 04:29:40 +00:00
HAL9000	8384f53e28	test(cli): cover actor remove format regression (#6491) ... Add Robot regression coverage for `actor remove --format json`, document the flag in the CLI synopsis, and record the fix in the changelog.\n\nISSUES CLOSED: #6491	2026-05-06 01:07:15 +00:00
hurui200320	85c579b51f	fix(cli): display full session IDs in session list output ... Remove the [:8] truncation from session IDs in the Rich table row, Most Recent summary, and Oldest summary fields of list_sessions() and _session_list_dict(). Session IDs are 26-character ULIDs and must be usable directly for copy-paste into session tell, session show, and other session commands. The structured output (JSON/YAML) already used full IDs in the sessions[*].id field, but the summary panel leaked the truncation into those formats as well. Added Behave scenarios: - Rich table displays full 26-character ULIDs (scoped to table region) - Summary panel shows full ULIDs for unnamed sessions (scoped to panel) - Summary panel shows session names for named sessions - Full ULID from list output works with session tell (round-trip, uses parsed ULID, not hardcoded constant) Review Cycle 2 fixes: - docs/specification.md: Updated YAML output example to full ULIDs - docs/showcase/*.md: Updated all example output blocks to full ULIDs - docs/reference/session_cli.md: Replaced placeholder with full ULID - features/session_cli.feature: Consecutive When steps -> And - features/steps/session_cli_steps.py: Summary panel asserts both IDs, 8-char negative guard in table output, ULID capture scoped to table region with fixture verification, named-session absence check for second session - CHANGELOG.md: Added [Unreleased] entry for the behavioral change ISSUES CLOSED: #10970	2026-05-05 10:56:18 +00:00
hurui200320	7164b04019	refactor(providers): unify provider factory behind single source of truth ... Extract _get_api_key() and _create_provider_instance() as a single internal factory that handles all provider types, including MOCK. Both create_llm() and create_ai_provider() now delegate to _create_provider_instance(), eliminating the duplicated if/elif provider-switching chains and the divergence between the two code paths. Adding a new provider now requires touching exactly one place. Key changes: - New _get_api_key(provider_type) consolidates API key lookup and validation that was previously duplicated across create_llm(), _create_provider_llm(), and every branch of create_ai_provider(). - New _create_provider_instance() is the unified raw-LLM factory, replacing _create_provider_llm() and the specialised adapter constructors in create_ai_provider(). MOCK is now handled here via FakeListLLM. - create_ai_provider() wraps all providers uniformly in LangChainChatProvider instead of using specialised adapters (OpenAIChatProvider, AnthropicChatProvider, GoogleChatProvider, OpenRouterChatProvider) for the four primary providers. - create_llm() drops its own API key validation block; validation now happens inside _create_provider_instance() via _get_api_key(). - All BDD scenarios updated: _create_provider_llm references become _create_provider_instance, and provider-type assertions on create_ai_provider results are updated to LangChainChatProvider. Review fixes (Cycle 2): - Add _coerce_env_bool() for consistent boolean env-var coercion in CLEVERAGENTS_ALLOW_MOCK_PROVIDER checks. - Introduce _ApiKeyMissing sentinel to distinguish 'not provided' from None in provider configuration. - Set MOCK supports_streaming=False in DEFAULT_CAPABILITIES to align with FakeListLLM semantics. - Make MOCK is_configured conditional on CLEVERAGENTS_ALLOW_MOCK_PROVIDER. - Use FakeListLLM(responses=['mock response'] * 10) to prevent IndexError in multi-step workflows. - Strip max_retries from kwargs before passing to LangChain constructors. - Extract _resolve_provider_type() helper shared by create_llm() and create_ai_provider() to reduce duplication and improve readability. - Ensure __api_key_sentinel flows through factory_kwargs even when api_key is None, avoiding double _get_api_key() calls. - Add CHANGELOG env-var documentation and providers.md env-var table. - Resolve template DB lock issues by persisting in-memory SQLite via VACUUM INTO instead of direct file creation on tmpfs. ISSUES CLOSED: #10949	2026-05-05 06:16:46 +00:00
HAL9000	988a169831	docs: add InvariantReconciliationActor API docs, devcontainer discovery module guide, and mkdocs nav ... - docs/api/actor.md: Add InvariantReconciliationActor section documenting the built-in reconciliation actor introduced in v3.8.0, including the reconciliation algorithm, ReconciliationResult/ConflictRecord/ScopeInvariants data classes, standalone reconcile_invariants() function, DI registration, and failure behaviour. - docs/modules/devcontainer-discovery.md: New module guide for the devcontainer auto-discovery system (v3.8.0 fix #2615), covering DevcontainerDiscoveryResult, discover_devcontainers(), is_trigger_type(), monorepo named-config support, and gotchas. - mkdocs.yml: Add 'Devcontainer Auto-Discovery' to the Modules nav section, alongside shell-safety, uko-provenance, invariant-reconciliation, context-hydration, and git-worktree-sandbox module docs. - robot/coverage_threshold.robot: Add tdd_issue and tdd_issue_4305 tags to the Noxfile Contains Coverage Threshold Constant test case. ISSUES CLOSED: #4485	2026-05-05 06:15:57 +00:00
CoreRasurae	cc24d8c8ac	fix(cli): remove legacy plan commands from help output ... Completely removed all legacy plan commands from the CLI: - Removed tell, build, new, current, cd, continue CLI commands - Removed programmatic wrapper functions (tell_command, build_command, etc.) - Removed legacy deprecation message - Updated help text to indicate V3 Plan Lifecycle exclusively - Removed stale references to tell/build in help output and command validation Removes the legacy 'tell' and 'build' CLI shortcuts from main.py: - Removed echo lines advertising tell/build commands - Removed tell/build from valid_cmds list - Removed tell/build from _LIGHTWEIGHT_COMMANDS frozenset - These dead entries were preventing helpful error messages Test infrastructure improvements: - Event bus exception test: Patch the module-level logger during emit() so that structlog.testing.capture_logs() can capture the logs. Without patching, the module-level logger created at import time is not captured by the context manager. - Session create/list commands: Suppress cleveragents.mcp logger to CRITICAL level during JSON/YAML output formatting to prevent health check warnings with ANSI codes from being written to stdout before JSON output, which breaks JSON parsing. - Extended plan_cli_coverage_boost with scenarios for estimation_result, invariants, execution_environment, validation_summary, and checkpoint coverage in _plan_spec_dict Documentation: - Created docs/Legacy_to_V3_Guide.md with comprehensive migration instructions - Updated CONTRIBUTING.md to document removal of legacy workflow - Updated CHANGELOG.md to reference issue #4181 instead of PR #10800 ISSUES CLOSED: #4181	2026-05-05 02:01:49 +00:00
HAL9000	dde71cf8e2	docs(milestone): split advanced-concepts and tui docs into sub-documents ... Split docs/advanced-concepts.md (554 lines) into four sub-documents under docs/advanced-concepts/ and docs/tui.md (634 lines) into four sub-documents under docs/tui/, each under the 500-line limit per CONTRIBUTING.md. Advanced Concepts sub-documents: - docs/advanced-concepts/index.md: Overview, context strategies, LLM backends - docs/advanced-concepts/resource-types.md: Resource types, A2A rename - docs/advanced-concepts/container-tools.md: Container tools, scope chain, budgets, safety - docs/advanced-concepts/e2e-tests-and-plugins.md: E2E tests, code review, plugins TUI sub-documents: - docs/tui/index.md: Overview, getting started, main screen layout - docs/tui/sidebar-and-personas.md: Sidebar states, persona system - docs/tui/input-and-sessions.md: Reference/command input, session management - docs/tui/configuration-and-integration.md: Config, key bindings, theme, integration Updated mkdocs.yml navigation to reflect new sub-document structure. Updated CONTRIBUTORS.md with contribution entry for PR #9903. ISSUES CLOSED: #10533	2026-05-03 01:11:03 +00:00
HAL9000	7ece6f1530	docs(spec): rename checkpoint triggers on_tool_write → before/after_tool_execute ... Update the Automatic Checkpoint Triggers table and configuration reference in docs/specification.md to use the trigger names that match the actual implementation in ToolRunner and config_service.py: - on_tool_write → before_tool_execute - on_tool_write_complete → after_tool_execute The implementation (PR #3474) chose before_/after_ prefix pattern for consistency with event naming conventions and because _execute is more precise than _write. The spec was not updated at that time. ISSUES CLOSED: #4745	2026-04-30 17:48:19 +00:00
HAL9000	d7f03ee0a6	docs: add CHANGELOG.md and CONTRIBUTING.md to docs tree ... Add mirrored versions of root CHANGELOG.md and CONTRIBUTING.md to the docs tree. Add migration headers noting these are mirrors of the authoritative root files. Update mkdocs.yml navigation to include both new pages between FAQ and Reference.	2026-04-30 14:26:39 +00:00
HAL9000	0ade2526eb	docs(cli): update agents validation attach synopsis to use --key value named option format ... Update docs/specification.md to clarify that agents validation attach extra arguments use --key value named option format (not positional [<ARGS>...] format). Updates synopsis, argument description, and all inline references across the specification. ISSUES CLOSED: #4747	2026-04-29 17:08:17 +00:00
HAL9000	ab15eec673	docs(showcase): add audit log and security commands example to registry ... Register the existing audit-log-and-security.md example in the showcase registry (examples.json) so it appears alongside other CLI tool examples. Includes 17 audit commands covering list, show, count, and prune operations with all filter options. Closes #10824	2026-04-28 20:47:15 +00:00
HAL9000	ba53d2723b	docs(timeline): update schedule adherence Day 99 (2026-04-09)	2026-04-28 11:02:38 +00:00
HAL9000	98bc7c6b5d	docs(spec): align checkpoint trigger names and config key path with implementation ... - Update trigger names from 'on_tool_write' and 'on_tool_write_complete' to 'before_tool_execute' and 'after_tool_execute' to match the actual implementation in config_service.py - Correct config key path from 'core.checkpoints.auto_create_on' to 'checkpoints.auto_create_on' to match the actual configuration structure - Update TOML configuration examples to use comma-separated string format instead of array format, matching the actual ConfigService implementation - Update references to trigger names in the CLI Usage section to use the correct names	2026-04-28 08:20:42 +00:00
HAL9000	581dff6b43	spec(acms): add comprehensive ACMS v1 specification section (v3.4.0) ... Adds a comprehensive ACMS v1 (Advanced Context Management System) specification section covering all aspects of the context management architecture for milestone v3.4.0 — ACMS v1 + Context Scaling. Sections included: - Overview and design goals - Architecture: UKO (Unified Knowledge Ontology), CRP (Context Request Protocol), Context Pipeline, Storage Tiers (hot/warm/cold) - Module Definitions across all 4 architecture layers (Domain, Application, Infrastructure, Presentation) - Data Models: ContextFragment, ContextBudget, ProjectContextPolicy, ContextView, AssembledContext/ContextPayload, IndexMetadata - Key Interfaces: ACMSPipeline, ContextBudgetEnforcer, UKOStore, ContextTierService, RepoIndexingService - 10-Component Pipeline Architecture (3 phases: Strategy Orchestration, Fragment Fusion, Context Finalization) - Context Strategies: 6 built-in strategies with fallback degradation path - CLI Commands: agents context list/add/show/clear and agents project context set/show/inspect/simulate - Integration Points: Plan Lifecycle, Resource System, Actor/Agent, Configuration, DI Container - Database Schema: repo_indexes and indexed_files tables - v1 Known Limitations with planned conformance path - Acceptance Criteria for milestone v3.4.0 Replaces stuck [AUTO-ARCH-19] worker from Cycle 26. [AUTO-ARCH-20] Cycle 27 # Conflicts: # docs/specification.md	2026-04-26 18:45:44 +00:00
HAL9000	3975ad244c	docs(spec): fix invariant reconciliation, add ACMS thread safety, v3.6.0 section, ADR-049 ... - Fix invariant glossary entry: reconciliation now documented as occurring at each phase boundary (before Strategize, Execute, Apply, and after Apply) rather than only at start of Strategize (closes #9899) - Add Multi-Phase Invariant Enforcement note to Plan Lifecycle section - Add ACMS Thread Safety subsection documenting threading.RLock concurrency contract for ContextAssemblyPipeline and all context stores (closes #9859) - Append M7: Advanced Concepts and Deferred Features (v3.6.0) milestone spec section covering advanced invariant lifecycle, ACMS observability, plan hierarchy enhancements, and CLI communication pattern migration - Add ADR-049: CLI Communication Pattern documenting local CLI exemption from A2A boundary requirement and M9 migration path	2026-04-26 17:09:22 +00:00
HAL9000	0f0efe02e3	docs: update examples.json index with actor management workflow entry ... ISSUES CLOSED: #7539	2026-04-26 16:52:36 +00:00
HAL9000	4f2122cd9e	docs: add action module API reference, update CHANGELOG and nav ... - Add docs/api/action.md: full API reference for ActionConfigSchema and ActionArgumentSchema — field tables, factory methods, camelCase compat mapping, env-var interpolation, database integrity note, and complete YAML example - Update docs/api/index.md: add cleveragents.action entry to module index - Update mkdocs.yml: add 'Action Schema: api/action.md' to the API Reference nav - Update CHANGELOG.md [Unreleased] Fixed: document plan use UNIQUE constraint violation fix (#4174, #4197) - Clarify from_yaml_file ValueError semantics, document inputs_schema type as dict[str, Any] | None, and update A2A ASV benchmarks to pass method= requests after JSON-RPC migration ISSUES CLOSED: #7472	2026-04-26 09:39:17 +00:00
HAL9000	663a6d2397	docs(decomposition): enhance docstrings and add spec section for selective subtree recomputation	2026-04-24 08:26:59 +00:00
HAL9000	dddfa48eb4	docs(spec): extend diagnostics example to cover all providers ... - update agents diagnostics examples to show all provider checks across rich, plain, JSON, and YAML formats - refresh error scenario samples to reflect the expanded provider coverage and recommendation counts - align CLI diagnostics output with the spec by adding explicit provider display names and consistent ordering Closes #5320	2026-04-24 03:51:32 +00:00
HAL9000	afc17b22c5	feat(architecture-pool-supervisor): add milestone assignment to spec PRs ... Restore original permission structure and model configuration while adding only the changes needed for issue #7521: forgejo_update_pull_request permission and PR Workflow for Major Changes documentation section. Fixes addressed: - Restore flat permission format (was incorrectly restructured to nested) - Restore model to claude-haiku-4-5 with reasoningEffort max - Restore removed critical rules (6: label delegation, 7: pagination) - Restore removed permission denials (*, doom_loop, question, etc.) - Add CHANGELOG.md entry for this feature - Restore CONTRIBUTORS.md to master (remove unrelated changes) ISSUES CLOSED: #7521 # Conflicts: # CONTRIBUTORS.md	2026-04-24 02:04:54 +00:00
HAL9000	44fc7411f9	ci: move benchmark regression job out of default PR workflow ... Extract the benchmark-regression job from the default PR CI workflow into a dedicated scheduled workflow (.forgejo/workflows/benchmark-scheduled.yml). The benchmark job was blocking PR feedback for 99-132 minutes even when lint/typecheck/tests passed in under 20 minutes. The new workflow runs: - Nightly regression tests (2 AM UTC) comparing HEAD against master - Weekly full benchmark suite (3 AM UTC Sundays) for trend analysis - Manual dispatch trigger for ad-hoc benchmark validation AWS S3 integration stores benchmark results for historical trend analysis. Documentation updated in docs/development/ci-cd.md. CONTRIBUTORS.md updated with benchmark workflow separation contribution. ISSUES CLOSED: #9040 # Conflicts: # CONTRIBUTORS.md # Conflicts: # CONTRIBUTORS.md	2026-04-23 14:24:09 +00:00
HAL9000	00d12c844d	[AUTO-TIME-2] Day 103 Timeline Update — Cycle 3 (2026-04-13 ~22:02 UTC) ... Update docs/timeline.md with Cycle 3 milestone status: - ALERT: Scope expanding faster than closing (+110 open in 60 min, only +2 closed) - M2 v3.1.0: 5 open (was 3) — scope expanding in closed milestone - M3 v3.2.0: 802 open (was 776), 269 closed — 25.1% completion - M4 v3.3.0: 157 open (was 148), 109 closed — 41.0% completion - M5 v3.4.0: 242 open (was 233), 139 closed — 36.5% completion - M6 v3.5.0: 1052 open (was 1032), 212 closed — 16.8% completion - M7 v3.6.0: 314 open (was 296), 152 closed — 32.6% completion - M8 v3.7.0: 574 open (was 548), 427 closed — 42.6% completion Added scope expansion alert section and Cycle 3 schedule adherence entries.	2026-04-21 20:32:34 +00:00
CoreRasurae	e19af527e6	revert 4e86ffe596 ... revert docs: document LLM provider fallback behavior (Anthropic Sonnet fallback) [AUTO-DOCS-7]	2026-04-21 19:44:48 +00:00
HAL9000	4e86ffe596	docs: document LLM provider fallback behavior (Anthropic Sonnet fallback) [AUTO-DOCS-7]	2026-04-21 17:26:19 +00:00