aditya
ef8f9640fa
CI / lint (pull_request) Successful in 30s
CI / typecheck (pull_request) Successful in 1m7s
CI / quality (pull_request) Successful in 46s
CI / security (pull_request) Successful in 1m0s
CI / build (pull_request) Successful in 23s
CI / helm (pull_request) Successful in 41s
CI / integration_tests (pull_request) Successful in 4m11s
CI / unit_tests (pull_request) Successful in 4m38s
CI / docker (pull_request) Successful in 1m22s
CI / coverage (pull_request) Successful in 11m26s
CI / e2e_tests (pull_request) Successful in 18m21s
CI / status-check (pull_request) Successful in 1s
CI / benchmark-publish (pull_request) Has been skipped
CI / benchmark-regression (pull_request) Successful in 58m2s
Add phase-wise context analysis summaries for strategize, execute, and apply, and integrate them into `agents project context inspect` and `agents project context simulate` with per-phase resource counts, size and token utilization, and narrowing diagnostics.\n\nAdd Behave and Robot coverage for empty, single-resource, multi-resource, and budget-constrained context analysis, and tighten the M5 smoke coverage after review feedback with exact summary assertions and a missing-path regression scenario for `agents context add`.\n\nISSUES CLOSED: #849
32 lines
1.6 KiB
Gherkin
32 lines
1.6 KiB
Gherkin
Feature: Project context phase analysis summaries
|
|
As a developer
|
|
I want per-phase ACMS context analysis summaries
|
|
So that strategize/execute/apply scope narrowing is visible and actionable
|
|
|
|
Scenario: Empty context still produces per-phase summaries
|
|
Given a phase analysis policy with narrowing limits
|
|
And no tiered fragments for phase analysis
|
|
When I compute project context phase analysis with budget 2000
|
|
Then each phase summary should include resource and size metrics
|
|
And phase analysis should report monotonic narrowing
|
|
|
|
Scenario: Single resource context produces human-readable summaries
|
|
Given a phase analysis policy with narrowing limits
|
|
And a single resource fragment for phase analysis
|
|
When I compute project context phase analysis with budget 2000
|
|
Then each phase summary should include human-readable text
|
|
And strategize phase should include at least one fragment
|
|
|
|
Scenario: Multiple resources are counted in summaries
|
|
Given a phase analysis policy with narrowing limits
|
|
And multiple resource fragments for phase analysis
|
|
When I compute project context phase analysis with budget 2000
|
|
Then strategize phase resource count should be 2
|
|
|
|
Scenario: Budget constraints reduce execute and apply scope
|
|
Given a phase analysis policy with narrowing limits
|
|
And budget constrained fragments for phase analysis
|
|
When I compute project context phase analysis with budget 1000
|
|
Then execute phase should have fewer tokens than strategize phase
|
|
And apply phase should have fewer or equal tokens than execute phase
|