fix(acms): use project-level hot_max_tokens in execute phase context assembly #11216

Merged

hamza.khyari merged 1 commits from bugfix/m5-acms-project-budget-override into master

2026-05-15 10:50:06 +00:00

Author	SHA1	Message	Date
hamza.khyari	1baa888659	fix(acms): use project-level hot_max_tokens in execute phase context assembly CI / lint (pull_request) Successful in 57s Details CI / typecheck (pull_request) Successful in 1m24s Details CI / quality (pull_request) Successful in 1m16s Details CI / build (pull_request) Successful in 40s Details CI / security (pull_request) Successful in 1m28s Details CI / integration_tests (pull_request) Successful in 6m2s Details CI / helm (pull_request) Successful in 24s Details CI / push-validation (pull_request) Successful in 28s Details CI / unit_tests (pull_request) Successful in 7m13s Details CI / docker (pull_request) Successful in 1m29s Details CI / coverage (pull_request) Successful in 11m50s Details CI / status-check (pull_request) Successful in 7s Details Added _resolve_effective_budget() method to ACMSExecutePhaseContextAssembler that reads each linked project's settings.hot_max_tokens and uses the maximum override value as the pipeline budget instead of the hardcoded global default. Updated assemble() to use the resolved effective budget for both CoreContextBudget and ContextRequest. Added Behave regression scenario with @tdd_issue @tdd_issue_11035 tags verifying the pipeline receives the project-level budget. Removed test artifact ANALYSIS.md left over from scenario 20. Fixes: #11035 Fixes: #11215	2026-05-15 10:27:57 +00:00