CoreRasurae
cc24d8c8ac
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
59 lines
1.9 KiB
Gherkin
59 lines
1.9 KiB
Gherkin
Feature: CLI Commands Full Coverage
|
|
As a developer
|
|
I want to test all CLI command paths
|
|
So that I achieve comprehensive coverage
|
|
|
|
Scenario: Context add command with file
|
|
Given I have a temporary test directory
|
|
And I have a CLI test file "test.py" with content "print('test')"
|
|
When I run context add with file "test.py"
|
|
Then the context add should execute
|
|
|
|
Scenario: Context add command with directory
|
|
Given I have a temporary test directory
|
|
And I have multiple test files in a directory
|
|
When I run context add with directory path
|
|
Then the context add should execute
|
|
|
|
Scenario: Context remove command
|
|
Given I have a temporary test directory
|
|
And I have added files to context
|
|
When I run context remove with a file
|
|
Then the context remove should execute
|
|
|
|
Scenario: Context clear command
|
|
Given I have a temporary test directory
|
|
And I have added files to context
|
|
When I run context clear
|
|
Then the context clear should execute
|
|
|
|
Scenario: Context list command
|
|
Given I have a temporary test directory
|
|
And I have added files to context
|
|
When I run context list
|
|
Then the context list should execute
|
|
|
|
Scenario: Project init command
|
|
Given I have a temporary test directory
|
|
When I run project init
|
|
Then the project init should execute
|
|
|
|
Scenario: Project init with force
|
|
Given I have a temporary test directory
|
|
And I have an existing project
|
|
When I run project init with force flag
|
|
Then the project init should execute with force
|
|
|
|
Scenario: Project status command
|
|
Given I have a temporary test directory
|
|
And I have an initialized project with basic config
|
|
When I run project status
|
|
Then the project status should execute
|
|
|
|
Scenario: Context command group help
|
|
When I run context command with help
|
|
Then the context help should display
|
|
|
|
Scenario: Project command group help
|
|
When I run project command with help
|
|
Then the project help should display |