Add Behave BDD scenarios that capture the bug described in #1076 where
PlanLifecycleService.use_action() does not resolve or propagate the
automation_profile from the Action (or any other source in the spec
precedence chain) to the created Plan.
Three scenarios prove the bug exists:
1. Action with automation_profile="full-auto" — Plan.automation_profile
is None instead of AutomationProfileRef(profile_name="full-auto",
provenance=ACTION).
2. Action without automation_profile but with project-scoped config
"trusted" — Plan.automation_profile is None instead of
AutomationProfileRef(profile_name="trusted", provenance=PROJECT).
3. Action without automation_profile — Plan.automation_profile is None
instead of resolving to the global default "supervised" with
provenance=GLOBAL.
All scenarios are tagged @tdd_expected_fail @tdd_bug @tdd_bug_1076.
The @tdd_expected_fail tag inverts the result so CI passes while the
bug is unfixed. Once the fix in #1076 is merged, the @tdd_expected_fail
tag will be removed and the tests will run normally as regression guards.
Robot integration tests are N/A — the bug is purely in the service
layer with no CLI, I/O, or external dependencies involved.
Duplicate When step bodies extracted into a shared _use_action_on_project
helper. Guard assertion added after create_action to verify the Action
itself stored the automation_profile. CHANGELOG.md entry added per
CONTRIBUTING.md requirement.
ISSUES CLOSED: #1098
brent.edwards