Files changed

• .milkyflow/agents/developer/prompts/EPIC_2_DEPLOY_BUG_2/

Briefing

You are the Software Solution Architect Agent.

Based on the rules you must follow in the file .milkyflow/agents/solution_architect/rules_solution_architect.md,
generate the coding-agent prompts for work item DEPLOY_BUG_2 of EPIC_2
(section 10 of your rules for a bug, section 10a for a FIX item).

Specification — this is what your prompts must make true:
.milkyflow/agents/devops/reports/EPIC_2_DEPLOY_BUG_2.md

This is a DEFECT report, and it is a work item of the EPIC — not of any user story. Its
"Steps to reproduce" and "Expected result" are the specification: QA will re-execute those
steps literally to validate your fix, so the work must make the Expected result hold from a
clean state. Its "## Detected during" field is informational only — never derive a story id,
a path, or any routing decision from it.

Do NOT create a story file for this work item, do NOT write into the Product Owner's
directory, and never consume a US_$j number. Do not edit the report itself: it belongs to the
agent that produced it, and its occurrence history is that agent's record.

Save the prompts under .milkyflow/agents/developer/prompts/EPIC_2_DEPLOY_BUG_2/,
one file per task, numbered in execution order, as your rules specify. Generate prompts for
DEPLOY_BUG_2 only — every other work item waits for the QA verdict on this one.

Output

» You are the Software Solution Architect Agent.

Based on the rules you must follow in the file .milkyflow/agents/solution_architect/rules_solution_architect.md,
generate the coding-agent prompts for work item DEPLOY_BUG_2 of EPIC_2
(section 10 of your rules for a bug, section 10a for a FIX item).

Specification — this is what your prompts must make true:
.milkyflow/agents/devops/reports/EPIC_2_DEPLOY_BUG_2.md

This is a DEFECT report, and it is a work item of the EPIC — not of any user story. Its
"Steps to reproduce" and "Expected result" are the specification: QA will re-execute those
steps literally to validate your fix, so the work must make the Expected result hold from a
clean state. Its "## Detected during" field is informational only — never derive a story id,
a path, or any routing decision from it.

Do NOT create a story file for this work item, do NOT write into the Product Owner's
directory, and never consume a US_$j number. Do not edit the report itself: it belongs to the
agent that produced it, and its occurrence history is that agent's record.

Save the prompts under .milkyflow/agents/developer/prompts/EPIC_2_DEPLOY_BUG_2/,
one file per task, numbered in execution order, as your rules specify. Generate prompts for
DEPLOY_BUG_2 only — every other work item waits for the QA verdict on this one.
… Let me read the relevant files first.
[tool] bash {'command': 'cat /home/oem/Documents/Sandbox/Kody/Projects/Backupper/.milkyflow/agents/solution_architect/rules_solution
[tool] bash {'command': 'cat /home/oem/Documents/Sandbox/Kody/Projects/Backupper/.milkyflow/agents/devops/reports/EPIC_2_DEPLOY_BUG_
… Let me read the relevant files first.
[tool] bash {'command': "cat /home/oem/Documents/Sandbox/Kody/Projects/Backupper/.milkyflow/agents/solution_architect/rules_solution
[tool] bash {'command': 'cat /home/oem/Documents/Sandbox/Kody/Projects/Backupper/local/fixtures/provision-pc-fixture.sh 2>/dev/null'
[tool] bash {'command': 'cat /home/oem/Documents/Sandbox/Kody/Projects/Backupper/.milkyflow/agents/developer/prompts/EPIC_2_BUG_1/2_
Now I have full context. The bug report says the `2_FIX_PROVISION_PASSWORD_CHANGE.md` task was supposedly implemented but the script was never actually updated. The fix is straightforward: add the `PUT /api/v1/users/{userId}` call to the provision script.

Let me check the current script and the existing answers directory:
[tool] bash {'command': 'ls /home/oem/Documents/Sandbox/Kody/Projects/Backupper/.milkyflow/agents/developer/answers/EPIC_2_BUG_1/ 2>
The BUG_1 task 2 was never answered. Now I'll generate the single coding prompt for DEPLOY_BUG_2:
[tool] bash {'command': 'mkdir -p /home/oem/Documents/Sandbox/Kody/Projects/Backupper/.milkyflow/agents/developer/prompts/EPIC_2_DEP
[tool] create {'path': '/home/oem/Documents/Sandbox/Kody/Projects/Backupper/.milkyflow/agents/developer/prompts/EPIC_2_DEPLOY_BUG_2/1_
Done. One prompt generated:

**`.milkyflow/agents/developer/prompts/EPIC_2_DEPLOY_BUG_2/1_ADD_PASSWORD_CHANGE_CLEAR_STEP.md`**

The fix is a single, focused change: insert the `PUT /api/v1/users/{BACKUP_USER_ID}` call with `{"changePasswordNextLogin":false}` between Step 2 and Step 3 of `local/fixtures/provision-pc-fixture.sh`, followed by the required confirmation echo.

The prompt includes:
- Static grep checks (no Docker needed) and a live end-to-end reprovision validation
- The exact insertion point and code pattern to mirror
- Strict out-of-scope list (no `src/`, no tests, no compose file)
- Answer file path under `EPIC_2_DEPLOY_BUG_2/`
[done] exit=0 premium_requests=1 api=79972ms