45 Commits

Author	SHA1	Message	Date
HAL9000	91d497ca03	fix(context-policy): resolve AmbiguousStep conflict and fix ruff formatting ... Rename step decorators in context_policy_strategy_config_steps.py from 'the strategy should be "{strategy}"' to 'the policy strategy should be "{strategy}"' (and likewise for the None variant) to avoid collision with the identically-patterned step already registered in plan_merge_strategy_steps.py. Update the feature file to match. Also apply ruff format to the three files flagged by CI lint gate: - features/steps/context_policy_strategy_config_steps.py - scripts/update_context_policy.py - src/cleveragents/domain/models/core/context_policy.py ISSUES CLOSED: #7572	2026-06-19 00:18:05 -04:00
HAL9000	48df4ce508	feat(context): add strategy configuration to context policy YAML schema ... - Add strategy and strategy_config fields to ProjectContextPolicy model - Support basic, semantic, relevance_scoring, adaptive, and fusion strategies - Validate strategy names with VALID_STRATEGIES constant - Add field validator for strategy configuration - Include update script for model changes	2026-06-19 00:18:05 -04:00
Rebase Agent	dea5ea4c18	Put tsx on PATH instead of replacing npx call sites	2026-06-18 03:03:26 -04:00
Rebase Agent	8f631969ff	Bypass npx by installing tsx locally and calling its binary directly	2026-06-18 03:03:26 -04:00
Rebase Agent	6f2c4de113	Guard all prompt_async paths against empty bodies	2026-06-18 03:03:26 -04:00
Rebase Agent	fc7fed644d	Skip worker launch when build_*_prompt returns empty content	2026-06-18 03:03:26 -04:00
Rebase Agent	9791460cca	Add grooming worker type with task-groomer and estimator-grooming	2026-06-18 03:03:26 -04:00
HAL9000	eba947bd0f	chore(ci): centralize tool version management into a single source of truth	2026-06-15 02:03:56 -04:00
HAL9000	f808abff86	chore(ci): fix pre-commit hook failures ... Fix JSON syntax errors in .devcontainer/devcontainer.json (removed invalid JS-style // comments) and .devcontainer/opencode.json (removed 90+ trailing commas). Apply auto-fixes for end-of-file and trailing whitespace issues across 100+ files. Fix SIM105 ruff violations in benchmarks/core_circuit_breaker_bench.py (use contextlib.suppress). Note: The security fix from issue #7478 (validate_path startswith bypass) was already delivered to master in commit e18ac5f2. This PR as currently structured is non-atomic (35 commits across 10+ issues) and needs significant restructure before merge. This commit only addresses the CI/pre-commit failures. ISSUES CLOSED: #7478	2026-06-14 09:51:14 -04:00
HAL9000	bcc4400080	style: apply ruff format to fix CI lint failure	2026-06-10 05:05:40 -04:00
HAL9000	97b5424bd2	fix(scripts): validate subprocess path arguments in check-quality-gates.py to prevent command injection ... Validate quality-gate subprocess path arguments against a safe allowlist, resolve them inside the project root, and require referenced paths to exist before command execution. Harden the command-injection regression feature so it loads the script reliably, avoids generic Behave step collisions, verifies path arguments are resolved before subprocess execution, and carries the mandatory TDD issue tag. ISSUES CLOSED: #7286	2026-06-10 05:05:40 -04:00
Rebase Agent	3c8cf60110	build: got auto-agents to a working state with deterministic starting	2026-05-13 21:14:25 -04:00
hurui200320	d25a060c58	Revert "feat(ci): implement TDD bug tag quality gate for bug fix PRs" ... This reverts commit e8d2f76466.	2026-05-12 08:30:24 +00:00
CoreRasurae	e8d2f76466	feat(ci): implement TDD bug tag quality gate for bug fix PRs ... Add an automated quality gate that enforces TDD bug fix workflow rules on pull requests. The gate parses PR descriptions for bug-closing keywords (Closes/Fixes/Resolves #N, ISSUES CLOSED: #N), searches the codebase for corresponding TDD tests tagged @tdd_bug_N, and verifies that @tdd_expected_fail tags have been removed. Key components: - scripts/tdd_quality_gate.py: Main quality gate script with PR description parsing, TDD test discovery, and tag removal verification. All public functions validate arguments fail-fast and are statically typed. - noxfile.py: New tdd_quality_gate session that reads PR_DESCRIPTION from the environment and runs the quality gate script. - .forgejo/workflows/ci.yml: New tdd_quality_gate CI job that runs only on pull_request events, passing the PR body as PR_DESCRIPTION. - features/tdd_quality_gate.feature: 46 Behave scenarios covering PR parsing, TDD test search, tag removal verification, full gate logic, robot diff handling, edge cases, argument validation, bool guards, co-located bug false-positive guard, and main() CLI entry point. - features/steps/tdd_quality_gate_steps.py: Step definitions for all Behave scenarios using temporary directories for isolation. - robot/tdd_quality_gate.robot: 15 Robot Framework integration tests exercising the gate end-to-end via a helper subprocess. - robot/helper_tdd_quality_gate.py: Helper script for Robot tests with sentinel-based sub-commands. Review-round fixes applied: - check_expected_fail_removed now uses _contains_tag_token for word-boundary matching (avoids false positives on partial tag names) - Diff expected-fail removal detection tracks flags at file level instead of per-hunk (fixes false negatives when tags span hunks) - parse_bug_refs filters out issue number zero - Redundant double error reporting eliminated (file-level check short-circuits the diff-level check) - run_quality_gate returns (errors, bug_refs) tuple to avoid redundant re-parsing in main() - Regex compilation cached via functools.lru_cache - Nox session no longer installs the full project (stdlib only) - CI checkout uses fetch-depth: 0 for reliable merge-base resolution Review-round 2 fixes applied: - _diff_has_expected_fail_removal_for_bug now requires the removed line to contain both the expected-fail tag and the specific bug tag (fixes false positives when two bugs share the same test file) - check_expected_fail_removed error messages use the correct tag prefix per file type (@tdd_bug_N for .feature, tdd_bug_N for .robot) - bool values rejected by bug-number validation guards in find_tdd_tests, check_expected_fail_removed, and _diff_has_expected_fail_removal_for_bug - File-read error handling catches UnicodeDecodeError alongside OSError (root-safe unreadable-file handling via invalid-UTF-8 test fixture) - Temp directory cleanup added to after_scenario hook in environment.py - 8 new Behave scenarios: bool type guards (2), co-located bug false-positive regression (1), run_quality_gate argument validation (3), and main() CLI entry point exit codes (2) Review-round 3 fixes applied: - Synthetic PR diff helper (_default_pr_diff_for_bug_refs) now auto-detects .robot vs .feature file type from the temp search tree and generates the matching diff format (fixes under-tested robot-format diff code path in multi-bug integration scenarios) - check_expected_fail_removed test step now filters files by bug tag via find_tdd_tests before checking (matches production path in run_quality_gate) - after_scenario temp directory cleanup no longer sets context.temp_dir = None (fixes cleanup conflict with cli_init_yes_flag_steps.py cleanup functions that run after hooks) - 2 new Behave scenarios: multi-line PR description parsing, and non-string pr_diff type guard for run_quality_gate ISSUES CLOSED: #629	2026-05-12 00:22:49 +01:00
hurui200320	bef7f3175b	fix(tests): resolve integration test failures in behave parallel log filtering ... Fix the integration test helper so that it can load scripts/run_behave_parallel.py outside of nox sessions. The helper imports the runner module via importlib, which triggers the top-level from behave_pass_suppress_formatter import PassSuppressFormatter. When invoked from integration tests (or any non-nox context), neither behave_pass_suppress_formatter nor the behave_parallel package (created by noxfile.py for unit_tests) is on sys.path, causing a ModuleNotFoundError and all 6 Robot tests to fail with exit code 1. The fix adds scripts/ to sys.path before loading the runner module so that from behave_pass_suppress_formatter import PassSuppressFormatter resolves correctly. This mirrors the approach already used in noxfile.py's unit_tests session for the behave-parallel package. Also addresses review feedback: - Removes one blank line from scripts/run_behave_parallel.py to bring it to 499 lines, satisfying the project's <500-line code style rule. - Moves in-function behave imports (Configuration, StreamOpener) in features/steps/behave_parallel_log_filtering_steps.py to the top-level import block alongside the existing behave imports, complying with the project's rule that all imports must be at the top of the file. Refs: #10987	2026-05-07 18:09:26 +08:00
hurui200320	49f1cfcdb6	chore(tests): suppress passing scenario output by default in behave-parallel unit test runner ... Implemented PassSuppressFormatter, a custom Behave formatter that buffers per-scenario output and only flushes it to stdout when the scenario failed or errored. Passing scenarios produce no output, keeping an all-passing suite at ~5-10 lines (the _print_overall_summary block only). Key design decisions: - PassSuppressFormatter (in scripts/behave_pass_suppress_formatter.py) inherits from behave's Formatter base class so it can be registered via behave.formatter._registry.register_as(), which enforces issubclass(cls, Formatter). - _SUPPRESS_STATUSES = {'passed', 'skipped'} determines which terminal statuses are silently discarded; all others (failed, undefined, etc.) trigger a buffer flush so no failure is hidden. - _make_runner() in run_behave_parallel.py registers the formatter and sets it as the default format whenever config.format is None (no explicit -f/--format flag). Coverage mode (BEHAVE_PARALLEL_COVERAGE=1) bypasses the formatter and falls back to config.default_format so slipcover can instrument a single process. - The formatter lives in a separate file to keep both scripts under the 500-line limit. _install_behave_parallel() in noxfile.py copies both files into the behave_parallel package. A try/except import handles both the direct-script path (tests via importlib) and the installed- package path (nox CI). - Three new BDD scenarios in behave_parallel_log_filtering.feature cover: (1) passing scenario -> no output, (2) failing scenario -> full output, (3) mixed run -> only failing scenario visible. All 20 scenarios pass. ISSUES CLOSED: #10987	2026-05-07 07:08:52 +00:00
CoreRasurae	cecca72b8e	test(behave): Reduce the coverage level to 96.5%	2026-05-05 02:01:49 +00:00
CoreRasurae	d4d43862e3	fix: Create fresh DB template and atomically swap it ... - Unit tests tend to fail due inconsitent DB file. - Create a fresh copy on a temporary location and the atomically swap it. - To always provide a completely initialized and migrated DB.	2026-05-05 02:01:49 +00:00
freemo	97ea5a26d8	script: reinforced auto-agent scripts	2026-05-02 14:02:26 -04:00
HAL9000	514d61c63c	build: fixed script to work with agent changes	2026-04-27 13:02:32 -04:00
HAL9000	fe30961990	build: Updated script to match the new agent code	2026-04-27 12:52:51 -04:00
hurui200320	f829e68911	fix(actor): resolve registry.add() rejection of spec-compliant actor YAML ... The ActorRegistry.add() method rejected spec-compliant YAML that uses the actors: map format with nested config: blocks because it only looked for provider/model at the top level of the blob. Four changes fix this: 1. _extract_v2_actor() now handles both the spec-canonical actors: key and the legacy agents: key, with actors: taking precedence. It also supports the combined actor field format (e.g. "openai/gpt-4") from the spec. 2. _extract_v2_options() mirrors the same actors:/agents: support. 3. registry.add() now unconditionally calls _extract_v2_actor() so that nested unsafe flags and graph descriptors are always captured — even when top-level provider/model are present. This eliminates the behavioural asymmetry with from_blob(). 4. The unsafe confirmation gate now runs before the duplicate-actor check, and the graph_descriptor resolution uses explicit is-not-None checks to distinguish "not set" from "set to empty dict". Review fixes (cycle 4): - Added 9 new Behave scenarios: _extract_v2_options edge cases (empty map, None, list, missing options key), _extract_v2_actor with unsafe=True, add() with missing name field, top-level unsafe: true (rejection + acceptance), and multi-actor unsafe limitation documentation. - Added graph descriptor assertions to all _extract_v2_actor direct scenarios that were missing them. - Fixed unsafe field coercion to use explicit boolean check (is True or == 1) instead of bool() to prevent truthy non-boolean values like "no" from being treated as unsafe. - Added legacy graph key fallback (blob.get("graph")) in add() for consistency with from_blob(). - Fixed _StubActorService.upsert_actor to handle set_default parameter and pass non-None config_blob to Actor.compute_hash(). - Updated stale CLI comment about registry.add() capabilities. - Applied ruff format to step definitions. Review fixes (cycle 5 — external review): - T1/T2/T3: Added unsafe coercion edge-case tests for 1.0 (float→True), 2 (int>1→False), and 0 (int zero→False). - T4/T5/T6: Added _extract_v2_options tests for non-dict first entry, missing config block, and actors: preference over agents:. - T7: Added integration test for top-level graph_descriptor key. - T8: Added integration tests for top-level provider_type/model_id aliases. - T9: Added integration tests for top-level unsafe string coercion ("yes"/"no"). - S1: effective_unsafe now includes unsafe/allow_unsafe params to match from_blob() and spec rule. - S2: CHANGELOG entry expanded with multi-actor rejection, options preservation, and coercion fix. - B1: Changed v2_options guard from truthiness to is-not-None check. - P1: _extract_v2_options() now returns a shallow copy. - P2: Nested options overwrite non-dict top-level options values. - Q3: Fixed comment variable name (unsafe_raw → top_unsafe_raw). - S3: Added spec-extension comment for provider_type/model_id aliases. - S4/B3: Cached actors_raw in multi-actor guard; added cross-ref comment. - Q5: Added TODO(#10832) to _StubActorService duplicate. - Q6: Replaced misleading (M2) label with (unsafe coercion). Review fixes (cycle 6 — agent review): - MAJ-1: Removed allow_unsafe from effective_unsafe computation. allow_unsafe is a permission flag, not an assertion; it should not mark a non-unsafe actor as unsafe. Updated docstring to clarify the semantic difference between unsafe and allow_unsafe. - MIN-1: Changed provider/model alias resolution in _extract_v2_actor() from or-based to is-not-None checks for consistency with _resolve_actors_map() and add(). - MIN-2: Added test scenario for allow_unsafe=True on non-unsafe YAML. - MIN-3: Added test scenarios for top-level unsafe: 1 (integer) rejection without flag and acceptance with flag. - MIN-4: Added test scenario for graph descriptor additional keys loop (routes key propagation). - MIN-5: Added test scenario for non-dict top-level options with nested options. - MIN-9: Applied ruff format to step file (removed unnecessary parens). - NIT-1: Differentiated redundant scenario to test graph descriptor agent key value instead of duplicating assertions. - NIT-2: Added test scenario verifying config_blob source: "yaml" default. - NIT-5: Changed _resolve_actors_map() return type to use Literal["actors", "agents"] for stronger type safety. Includes 78 Behave scenarios covering spec-compliant actors: map, legacy agents: map, top-level fields, rejection of missing provider/model, combined actor field edge cases, update=True path, schema_version and compiled_metadata forwarding, actors-as-list edge case, empty actors dict blocking agents fallback, malformed actor field parts, reverse precedence for the combined actor field, _extract_v2_options edge cases, unsafe=True detection, missing name rejection, top-level unsafe, multi-actor rejection, unsafe coercion edge cases (1.0, 2, 0, "yes", "no"), top-level graph_descriptor, provider_type/model_id aliases, _extract_v2_options structural parity with _extract_v2_actor, allow_unsafe on non-unsafe YAML, top-level unsafe: 1 (integer), graph descriptor additional keys, non-dict top-level options, and config_blob source default. ISSUES CLOSED: #4466	2026-04-23 16:15:49 +00:00
CoreRasurae	0c5b140d29	fix(database): include alembic files in package distribution ... Move alembic configuration and migration files from repository root into the Python package structure to ensure they are included in the wheel distribution. This fix resolves the FileNotFoundError when running `agents init` in Docker containers or any environment using the built wheel distribution. Changes: - Move alembic/ directory from repo root to src/cleveragents/infrastructure/database/migrations/ - Move alembic.ini to the same new location and update script_location setting - Update MigrationRunner._find_alembic_ini() to search from the new canonical location within the package - Update create_template_db.py to point to the new alembic.ini location - Update documentation references to reflect new migration file locations - Create __init__.py for migrations package - The env.py file is imported when running tests that verify all modules can be imported without errors. However, context.config is only available when alembic is actually running migrations, not during normal module imports. This caused an AttributeError when the test tried to import the migrations.env module. - Fix by using getattr() with a default value to safely access context.config, and guard all code that uses config with None checks. This allows the module to be safely imported while still functioning correctly during migrations. Testing: - Verified MigrationRunner can locate alembic.ini in new location - Tested agents init succeeds in creating project with database - Template database creation works correctly - All migration tests should pass without changes Alembic files now follow standard Python packaging conventions, making them automatically included in wheel distributions without special configuration. ISSUES CLOSED: #4180	2026-04-17 17:40:00 +00:00
HAL9000	449c33b752	style(tests): apply ruff format to run_behave_parallel.py ... Fix formatting of conditional expression in _is_btrfs_or_overlayfs() that was flagged by ruff format --check in CI.	2026-04-17 07:16:05 +00:00
Test	4fc4d7863c	fix(tests): prevent behave-parallel multiprocessing deadlock on btrfs/overlayfs ... Detect btrfs and overlayfs filesystems and automatically fall back to sequential mode to prevent deadlocks caused by SQLite WAL file locking and btrfs COW copy-up locks when multiple forked workers try to access the same files simultaneously. The fix adds a _is_btrfs_or_overlayfs() function that: 1. Attempts to detect the filesystem type using stat command 2. Falls back to reading /proc/mounts if stat fails 3. Returns True if the filesystem is btrfs or overlayfs The sequential mode condition is updated to include this check, ensuring that on affected filesystems, all features run in a single process instead of being split across multiple forked workers. ISSUES CLOSED: #9390	2026-04-17 07:16:05 +00:00
HAL9000	b8732dfc6f	fix(tests): resolve nox unit_tests timeout for agent_skills_loader and skill_search features ... Adjusted test running and file-detection logic to stabilize unit tests in overlayfs environments and improve target feature handling. - Modified scripts/run_behave_parallel.py to run sequentially when there are 2 or fewer feature files, avoiding fork deadlocks on overlayfs and reducing nox-based unit test timeouts for agent_skills_loader and skill_search features. - Updated noxfile.py to correctly detect feature files in posargs, fixing the prior logic that appended the "features/" directory when specific feature files were provided. This ensures precise test selection and avoids unnecessary path expansion. Rationale: These changes address the root causes of flaky unit test timeouts by preventing problematic forking behavior with small feature sets and by ensuring nox respects explicitly provided feature file paths. ISSUES CLOSED: #9374	2026-04-15 08:16:38 +00:00
hurui200320	8b2e0c81c5	fix(testing): print behave-parallel worker logs only for failed chunks ... In parallel mode, the behave runner previously replayed captured stdout/stderr for every worker chunk, creating noisy output that obscured failure diagnostics in CI and local runs. Changes to scripts/run_behave_parallel.py: - Added _chunk_has_failures() and _chunk_no_scenarios_ran() helpers to evaluate individual chunk summaries for failure/error/crash conditions. - Updated the aggregation loop in main() to conditionally replay captured stdout/stderr only for chunks whose summary indicates failures, errors, or no scenarios ran (crash detection). Passing chunks now suppress their output entirely. - Added robust exception handling in _worker_run_features() so that worker crashes produce a full traceback in stderr and return a crash summary with features.errors = 1, enabling the parent to detect the crash via _chunk_has_failures (and also _chunk_no_scenarios_ran, since no scenarios reached a terminal state) and replay the diagnostics. - The conditional replay uses summary-based checks rather than the raw runner.run() boolean, consistent with the existing exit-code logic. This avoids spurious log replay for @tdd_expected_fail scenarios whose runner.run() returns True even though the TDD inversion handler has corrected the scenario status to passed. - Existing summary merge, exit semantics, and the no-scenarios safety net are fully preserved. New Behave unit tests (17 scenarios) cover the chunk-level helpers, the conditional aggregation loop, the pure no-scenarios-ran path, stderr replay for non-crash failed chunks, and the worker crash path. New Robot integration tests (6 test cases) verify the same behavior end-to-end via the helper_behave_parallel_log_filtering.py script. Also updated: - CHANGELOG.md: add unreleased entry for this behavioral change. - features/steps/behave_parallel_log_filtering_steps.py: use contextlib.redirect_stdout/redirect_stderr instead of manual sys.stdout assignment; register module in sys.modules; document CWD requirement in _load_runner_module(). - robot/helper_behave_parallel_log_filtering.py: move import io to top-level; remove redundant inline imports; use contextlib for output capture; register module in sys.modules; document CWD requirement. Branch note: the canonical branch for this fix is bugfix/m3-behave-parallel-failed-chunk-logs. The PR head branch (bugfix/mX-behave-parallel-failed-chunk-logs) cannot be renamed via the Forgejo API; both branches are kept in sync at the same SHA. ISSUES CLOSED: #8351	2026-04-15 03:21:05 +00:00
HAL9000	4c0f3e1da9	fix(tests): fix create_template_db.py to create writable SQLite template database ... Added os.chmod(db_path, 0o664) after database creation to ensure the template database has writable permissions. This prevents sqlite3.OperationalError: attempt to write a readonly database when tests copy and modify the template during test setup. The template database is now created with rw-rw-r-- (664) permissions instead of the default rw-r--r-- (644), allowing the test runner process to write to it. ISSUES CLOSED: #9372	2026-04-14 22:10:07 +00:00
HAL9000	6559a0e9df	docs: integrate docs-writer automation tracking workflows ... - document docs-writer responsibilities and automation tracking requirements\n- enforce automation tracking label validation and clean coverage regression tags\n\nISSUES CLOSED: #7616 # Conflicts: # CHANGELOG.md # docs/development/automation-tracking.md # docs/development/docs-writer.md # mkdocs.yml	2026-04-14 14:11:47 +00:00
hurui200320	0bd8fbb296	fix(ci): resolve lint errors and remove stale tdd_expected_fail tag (#5264) ... ## Summary The `lint` and `integration_tests` CI jobs on `master` are currently failing. This PR fixes both: 1. **Lint (`nox -e lint`)** — 51 ruff violations in `scripts/validate_automation_tracking.py`: - Sorted imports per isort convention - Replaced deprecated `typing.List`/`Dict`/`Tuple`/`Optional` with builtin equivalents (`list`, `dict`, `tuple`) - Removed unused `Optional` import and unused local variable `issues` - Fixed trailing whitespace, blank-line whitespace, and 6 lines exceeding 88-char limit - Replaced `dict.keys()` with `dict` in membership tests - Added return type annotation to `main()` 2. **Integration tests (`nox -e integration_tests`)** — 1 failure in `robot/coverage_threshold.robot`: - Removed `tdd_expected_fail`, `tdd_issue`, and `tdd_issue_4305` tags from the `Noxfile Contains Coverage Threshold Constant` test - The bug this TDD tag tracked (issue #4305) is now fixed — `COVERAGE_THRESHOLD = 97` exists in `noxfile.py` - The TDD expected-fail listener was inverting the passing result to a failure ### Local verification - `nox -e lint` — All checks passed - `nox -e integration_tests` — 1962 tests, 1962 passed, 0 failed, 0 skipped ### Files changed | File | Change | |------|--------| | `scripts/validate_automation_tracking.py` | Fixed all 51 lint violations | | `robot/coverage_threshold.robot` | Removed stale `tdd_expected_fail` tag | Closes #5266 Reviewed-on: #5264 Co-authored-by: Rui Hu <rui.hu@cleverthis.com> Co-committed-by: Rui Hu <rui.hu@cleverthis.com>	2026-04-09 04:41:01 +00:00
freemo	f2fc8f771e	feat: add port checking to opencode-builder script ... - Add check_opencode_running() function to detect existing OpenCode server - Skip server startup if OpenCode already running on target port - Display prominent warning when connecting to existing server - Only manage server lifecycle when script starts its own server - Add OWN_SERVER flag to track server ownership - Update cleanup logic to leave existing servers running This enables multiple developers and automation scripts to safely run in parallel without conflicting server management.	2026-04-08 19:57:54 -04:00
freemo	a323f07783	feat: implement new automation tracking system for agent supervision ... Replace shared session state issue tracking with individual tracking issues per agent to reduce noise and improve searchability. **Agent Updates:** - session-persister: [AUTO-SESSION] prefix with cycle management - implementation-orchestrator: [AUTO-IMP-POOL] prefix for health reports - system-watchdog: [AUTO-WATCHDOG] prefix for system health - backlog-groomer: [AUTO-GROOMER] prefix + backup cleanup functionality - human-liaison: [AUTO-LIAISON] prefix for status updates **New Features:** - Standardized issue title format: [AUTO-<PREFIX>] <TYPE> (Cycle <N>) - Announcement format: [AUTO-<PREFIX>] Announce: <message> - Automatic cleanup to prevent issue accumulation - Required 'Automation Tracking' label for filtering - Validation script for format compliance **Documentation:** - Complete system documentation at docs/development/automation-tracking.md - Added to mkdocs.yml navigation - Validation script at scripts/validate_automation_tracking.py **Benefits:** - Reduced noise from shared tracking issue - Better searchability with agent-specific prefixes - Cleaner history per agent type - Easier debugging with focused issue threads - Automatic cleanup prevents accumulation Closes automation tracking system implementation requirements.	2026-04-08 21:28:46 +00:00
freemo	73afe58cfe	build: runner for opencode project-builder	2026-04-05 01:09:18 -04:00
freemo	02250473ad	fix(ci): restore all CI quality gates to passing on master ... Fix all failing CI quality gates (lint, unit_tests, format) without suppressing any quality enforcement. Root causes and fixes: 1. Format: features/steps/plan_namespaced_name_tdd_steps.py had trailing whitespace; fixed by running ruff format. 2. Unit tests - A2A JSON-RPC 2.0 migration (commit 9c6d6915) renamed A2aRequest fields (operation→method, request_id→id, a2a_version→jsonrpc) and A2aResponse fields (status+data→result, request_id→id) but did not update all step files and feature files: - a2a_jsonrpc_wire_format_steps.py: added use_step_matcher('re') and reset to 'parse' at end to prevent parallel test interference - a2a_facade_wiring_steps.py: updated operation= to method=, .status/.data to .result - a2a_facade_steps.py: updated request_id→id, a2a_version→jsonrpc, A2aResponse(request_id=..., status=...) to new API - m6_facade_steps.py: updated all old API usage - devcontainer_cleanup_steps.py: updated A2aRequest(operation=...) - plan_prompt_command_steps.py: updated A2aRequest(operation=...) - wf03_plan_prompt_confidence_steps.py: updated A2aRequest(operation=...) - consolidated_misc.feature: updated old A2aRequest/A2aResponse scenarios 3. Unit tests - Session CLI output changed (commit 0d5d9cf0 and others): - 'Session Created' → 'Session created' (lowercase) - 'Session Details' → 'Session Summary' - 'Sessions (N total)' → 'Sessions' - session list JSON: top-level 'total' → nested 'summary.total' - Fixed in: session_cli.feature, session_cli_coverage_boost.feature, session_cli_uncovered_branches.feature, session_list_error.feature, tdd_session_create_persist_steps.py 4. Unit tests - Plan list output changed (commit 1a07a891): - 'V3 Lifecycle Plans' → 'Plans' - 'Lifecycle Plans' → 'Plans' - Name column removed (restored in source) - Invariants column removed (restored in source) - Project truncation removed (restored in source) - Fixed in: plan_cli_cancel_revert_coverage.feature, plan_lifecycle_cli_coverage.feature, plan_cli_coverage_boost_steps.py, plan.py (source code restored) 5. Unit tests - Plan apply command now requires ULID (commit 300a5d6d): - plan_cli_coverage_r3.feature: updated 'PLAN-001' to valid ULID - plan_cli_coverage_r3_steps.py: added --yes flag, added new step for no-eligible-plans path 6. Unit tests - Various source code bugs: - ThoughtBlock: converted from @dataclass to Pydantic BaseModel (architecture test requires all dataclasses to use Pydantic) - session.py: added DatabaseError handling to export, import, tell commands - database.py: fixed rollback_to() to reuse checkpoint connection for writes - database.py: added _get_checkpoint_conn() helper - check-tls-cert.py: fixed SSLCertVerificationError.reason AttributeError 7. Unit tests - Test step bugs: - error_recovery_coverage_boost_steps.py: fixed invalid ULID _PLAN_ID - session_service_coverage_steps.py: fixed 'sha256:' prefix bug in checksum - database_models_new_coverage_steps.py: added 'name' field to session mock - async_audit_recording_steps.py: fixed Settings(audit_async=False) via env var - coverage_threshold_config_steps.py: added --coverage-min pattern support - m5_acms_smoke_steps.py: updated usage hint text - actor_cli_yaml_steps.py: updated 'Removed actor' → 'Actor removed' - aimodelscredentials_steps.py: set context.imported_class in import step - domain_base_model.feature: added missing 'When I examine model_config' step - tui_first_run_steps.py: fixed module reload to restore cleveragents.tui.* modules after test (prevented patch interference in subsequent tests) - tui_first_run_steps.py: added set_search('') step for empty string - resource_handler_base_coverage_r3_steps.py: use _MinimalHandler instead of DatabaseResourceHandler for NotImplementedError tests - resource_handler_crud.feature: updated to test new DatabaseHandler behavior - resource_handler_sandbox.feature: updated to test new DatabaseHandler behavior - tdd_json_decode_crash_persistence.feature: fixed @tdd_bug → @tdd_issue tags 8. Parallel test interference: - All step files using use_step_matcher('re') now reset to 'parse' at end to prevent global matcher state leaking to subsequent step files	2026-04-04 20:38:16 +00:00
freemo	70e2ce4386	Merge pull request 'fix(infra): resolve TLS handshake failure on git.dev.cleveragents.com' (#1865) from fix/infra-tls-handshake-failure-git-dev into master	2026-04-03 01:13:31 +00:00
freemo	8c81f13758	fix(infra): resolve TLS handshake failure on git.dev.cleveragents.com ... The TLS handshake failure on git.dev.cleveragents.com was caused by the hostname being absent from the certificate's Subject Alternative Names (SANs), or by SNI virtual-host misconfiguration on the server side. This commit delivers the repository-side remediation: - scripts/check-tls-cert.py: New TLS certificate health-check script. Connects to a hostname, verifies the certificate's SANs include the target hostname, checks expiry, and reports errors/warnings. Accepts an injectable SSLContext for unit testing without real network access. Supports wildcard SAN matching and configurable expiry warning threshold. - docs/development/ops-runbook.md: New ops runbook documenting the full certificate renewal procedure (Let's Encrypt/certbot and manual CA), SNI misconfiguration diagnosis steps, expiry monitoring with cron, and recommended alert thresholds (30/14/7/0 days). - features/tls_certificate_check.feature: 14 Behave scenarios tagged @tdd_issue @tdd_issue_1543 covering: missing SAN detection, valid SAN acceptance, expired certificate detection, expiry warning threshold, TLS handshake errors, connection timeouts, connection refused, wildcard SAN matching, and _hostname_matches_san unit tests. - features/steps/tls_certificate_check_steps.py: Step definitions for the above feature, using unittest.mock to inject SSL contexts and socket connections so no real network calls are made. - mkdocs.yml: Added Ops Runbook to the Development section navigation. The actual server-side certificate renewal (adding git.dev.cleveragents.com as a SAN and reloading the web server) must be performed by the server administrator following the procedure in docs/development/ops-runbook.md. Closes #1543 ISSUES CLOSED: #1543	2026-04-02 23:59:37 +00:00
freemo	37586882b3	chore(ci): extract behave-parallel runner script from noxfile.py into scripts/ ... Move the large embedded `_BEHAVE_PARALLEL_CLI_SOURCE` string constant out of noxfile.py and into a standalone `scripts/run_behave_parallel.py` module. The `_install_behave_parallel()` helper now reads the script from disk via `Path(__file__).parent / 'scripts' / 'run_behave_parallel.py'` instead of embedding the source as a raw string literal. This allows ruff to lint and type-check the runner independently, and makes noxfile.py significantly shorter and easier to read. No functional changes: the installed `behave-parallel` entry point is identical to the previous embedded version. Parallel and sequential modes, coverage integration, and the multiprocessing fork model are all preserved. Fixed two SIM105 lint violations in the extracted script (replaced try/except/pass with contextlib.suppress). ISSUES CLOSED: #1538	2026-04-02 23:44:30 +00:00
freemo	a8f7ed57cb	perf(tests): reduce per-feature startup cost with shared fixtures and lazy imports ... Created scripts/create_template_db.py that builds a pre-migrated SQLite template database using Base.metadata.create_all() + alembic stamp (~5ms for 34 tables, vs ~0.5-3s x 25 Alembic migrations per scenario). Nox unit_tests and coverage_report sessions generate the template before test execution and propagate CLEVERAGENTS_TEMPLATE_DB env var to all workers. features/environment.py before_all() installs a monkey-patch on MigrationRunner.init_or_upgrade that copies the template for fresh scenario temp DBs, falling through to real migrations for :memory:, existing files, and migration-runner unit tests. Quick wins: sleep(0.5) -> sleep(0.05) in cli_streaming wait step; removed redundant Background re-declaration in cli_streaming.feature scenario 7. ISSUES CLOSED: #483	2026-03-02 02:01:27 +00:00
brent.edwards	761db2518c	test: harden code sandbox, add path traversal protection, and fix test mocks	2026-02-12 01:07:44 +00:00
brent.edwards	7caac2714e	refactor: changes requested by Rui ... Removed `run-semgrep.sh` and automatically run setup-dev.sh	2026-02-11 00:59:58 +00:00
brent.edwards	7ef5ebb695	feat: Add Q0: Pre-commit hooks setup. ... This should automatically check for problems on build.	2026-02-10 16:04:17 +00:00
freemo	1486aa9de7	Removed sync and install scripts	2025-11-05 18:16:54 -05:00
freemo	9008f1a99d	Tentatively finishing phase 1	2025-11-05 17:07:35 -05:00
freemo	b941ef9a1a	Significantly revamped the base project to use more robust static checking including benchmarks and integration test support	2025-10-31 16:18:53 -04:00
freemo	f7a5d26c41	Modernized build tooling	2025-08-01 18:38:09 -04:00