Briefing

You are the QA Agent.

Based on the rules you must follow in the file .milkyflow/agents/qa/rules_qa_agent.md,
validate work item BUG_4 of EPIC_2 — section 3b of your rules, which this
briefing follows exactly.

Specification (your test script):
.milkyflow/agents/qa/reports/EPIC_2_BUG_4.md

Where to reach the app and test accounts: the "Endpoints" and "Access" sections of
.milkyflow/agents/devops/prompts/EPIC_2_BUG_4/DEPLOY_CONFIG_1.md
Precondition: .milkyflow/agents/devops/answers/EPIC_2_BUG_4/DEPLOY_CONFIG_1.md
exists and reports READY. If it does not, stop and report: there is no deployed environment.

Do NOT read the developer answer files or any completion report before testing — they
describe what was claimed, and reading them first biases the test.

**Part 1 — the defect is gone.**
Follow the report's "Steps to reproduce" literally, from a clean state. Its "Expected result"
must now hold. Record the verdict per step: PASS / FAIL / BLOCKED.

**Part 2 — the interrupted work is actually complete.**
On the SAME deployment, in this same session, identify the interrupted work item yourself —
nothing on disk records it:

- the epic's first US_$j, in the order stated in
  .milkyflow/agents/product_owner/EPIC_2/epic.md, that has NO pass document at
  .milkyflow/agents/qa/reports/EPIC_2_US_$j_PASS.md;
- if every planned story has one, the epic is in its e2e phase: re-execute the e2e plan's
  failed test plus every test the interrupted run never reached.

Execute that item's specification IN FULL — every acceptance criterion, not only the ones
that failed before. You are establishing that it is complete, not that one symptom moved.

**Verdicts (section 6).** This session can close TWO work items:

- defect gone AND every criterion of the interrupted story passed →
  create .milkyflow/agents/qa/reports/EPIC_2_BUG_4_PASS.md AND
  .milkyflow/agents/qa/reports/EPIC_2_US_$j_PASS.md for that story.
  In the same write, flip the bug report's `Status:` marker to `CLOSED`.
- defect gone, but the interrupted story reveals a DIFFERENT failure → the work item's pass
  document only, plus a NEW bug report (section 5: "## Bug Occurrence" 1, no
  "## Previous occurrence"). Never write a pass document for a story whose criteria did not
  all pass in THIS session.
- the SAME defect is still present → no pass document. Follow the repeat-defect rule of
  section 5: read the previous report's "## Bug Occurrence", and either raise a new report
  with the count incremented and a "## Previous occurrence" link, or — once the threshold in
  `qa.max_bug_occurrences` (default 3) is reached — stop creating reports, write
  .milkyflow/agents/qa/reports/EPIC_2_BUG_4_BLOCKED.md listing the whole
  chain, and escalate to the Project Manager as a category D blocker.

Cite DEPLOY_CONFIG_1 and the deployment answer in every report's Environment
section. The DevOps Agent tears the environment down after your verdict, whatever it is.

Output

» You are the QA Agent.

Based on the rules you must follow in the file .milkyflow/agents/qa/rules_qa_agent.md,
validate work item BUG_4 of EPIC_2 — section 3b of your rules, which this
briefing follows exactly.

Specification (your test script):
.milkyflow/agents/qa/reports/EPIC_2_BUG_4.md

Where to reach the app and test accounts: the "Endpoints" and "Access" sections of
.milkyflow/agents/devops/prompts/EPIC_2_BUG_4/DEPLOY_CONFIG_1.md
Precondition: .milkyflow/agents/devops/answers/EPIC_2_BUG_4/DEPLOY_CONFIG_1.md
exists and reports READY. If it does not, stop and report: there is no deployed environment.

Do NOT read the developer answer files or any completion report before testing — they
describe what was claimed, and reading them first biases the test.

**Part 1 — the defect is gone.**
Follow the report's "Steps to reproduce" literally, from a clean state. Its "Expected result"
must now hold. Record the verdict per step: PASS / FAIL / BLOCKED.

**Part 2 — the interrupted work is actually complete.**
On the SAME deployment, in this same session, identify the interrupted work item yourself —
nothing on disk records it:

- the epic's first US_$j, in the order stated in
  .milkyflow/agents/product_owner/EPIC_2/epic.md, that has NO pass document at
  .milkyflow/agents/qa/reports/EPIC_2_US_$j_PASS.md;
- if every planned story has one, the epic is in its e2e phase: re-execute the e2e plan's
  failed test plus every test the interrupted run never reached.

Execute that item's specification IN FULL — every acceptance criterion, not only the ones
that failed before. You are establishing that it is complete, not that one symptom moved.

**Verdicts (section 6).** This session can close TWO work items:

- defect gone AND every criterion of the interrupted story passed →
  create .milkyflow/agents/qa/reports/EPIC_2_BUG_4_PASS.md AND
  .milkyflow/agents/qa/reports/EPIC_2_US_$j_PASS.md for that story.
  In the same write, flip the bug report's `Status:` marker to `CLOSED`.
- defect gone, but the interrupted story reveals a DIFFERENT failure → the work item's pass
  document only, plus a NEW bug report (section 5: "## Bug Occurrence" 1, no
  "## Previous occurrence"). Never write a pass document for a story whose criteria did not
  all pass in THIS session.
- the SAME defect is still present → no pass document. Follow the repeat-defect rule of
  section 5: read the previous report's "## Bug Occurrence", and either raise a new report
  with the count incremented and a "## Previous occurrence" link, or — once the threshold in
  `qa.max_bug_occurrences` (default 3) is reached — stop creating reports, write
  .milkyflow/agents/qa/reports/EPIC_2_BUG_4_BLOCKED.md listing the whole
  chain, and escalate to the Project Manager as a category D blocker.

Cite DEPLOY_CONFIG_1 and the deployment answer in every report's Environment
section. The DevOps Agent tears the environment down after your verdict, whatever it is.
I'll start by reading the rules, checking the precondition, and reading the bug report specification — in that order, without reading any developer answer files first.
… Let me start by reading the required files in the correct order - first the rules, then check the precondition, then the bug report specification.
[tool] view {'path': '/home/oem/Documents/Sandbox/Kody/Projects/Backupper/.milkyflow/agents/qa/rules_qa_agent.md'}
[tool] view {'path': '/home/oem/Documents/Sandbox/Kody/Projects/Backupper/.milkyflow/agents/devops/answers/EPIC_2_BUG_4/DEPLOY_CONFI
The deployment answer reports **Status: FAILED**, not READY. Per the precondition in section 3b and section 2 of my rules:

> *"must exist and report READY — if it does not, stop: there is no deployed environment"*

**There is no deployed environment.**

The deployment answer (`DEPLOY_CONFIG_1.md`) for EPIC_2_BUG_4 reports `Status: FAILED` — the DevOps Agent halted because a configuration defect caused authentication failures (HTTP 401) against the Password Cockpit fixture. QA cannot start.

I must not proceed with testing. I'll now append the mandatory history row.
… Let me start by reading the required files in the correct order - first the rules, then check the precondition, then the bug report specification.
[tool] bash {'command': 'date -u +%Y-%m-%dT%H:%M:%SZ', 'description': 'Get UTC timestamp'}
[tool] bash {'command': 'cat /home/oem/Documents/Sandbox/Kody/Projects/Backupper/.milkyflow/agents/history.md 2>/dev/null || echo "F
[tool] bash {'command': 'echo "| 2026-08-09T04:03:14Z | QA — QA Agent | bug_validation | {\\"epic_id\\": \\"EPIC_2\\", \\"work_item\
---

**QA Agent — EPIC_2 BUG_4 validation — STOPPED**

**Precondition not met.** The deployment answer at  
`.milkyflow/agents/devops/answers/EPIC_2_BUG_4/DEPLOY_CONFIG_1.md`  
reports **`Status: FAILED`**, not READY.

Per rules section 2 and 3b: *"if it does not [report READY], stop: there is no deployed environment."*

**Root cause recorded in the deployment answer:** Every step in DEPLOY_CONFIG_1 hard-codes the literal username `backup` for the Password Cockpit fixture, but the actual provisioned account username comes from `local/.secrets/PC_FIXTURE_USERNAME`. This caused HTTP 401 on every authentication attempt; the readiness check failed at `auth_ok`; the DevOps Agent halted before declaring READY.

**No testing was performed.** No pass, fail, or bug documents were created. The history row has been appended. The Solution Architect must correct DEPLOY_CONFIG_1 (corrections detailed in the deployment answer) and request a new deployment before this validation can proceed.
[done] exit=0 premium_requests=1 api=30976ms