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_1 of EPIC_2 — section 3b of your rules, which this
briefing follows exactly.

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

Where to reach the app and test accounts: the "Endpoints" and "Access" sections of
.milkyflow/agents/devops/prompts/EPIC_2_BUG_1/DEPLOY_CONFIG_1.md
Precondition: .milkyflow/agents/devops/answers/EPIC_2_BUG_1/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_1_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_1_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_1 of EPIC_2 — section 3b of your rules, which this
briefing follows exactly.

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

Where to reach the app and test accounts: the "Endpoints" and "Access" sections of
.milkyflow/agents/devops/prompts/EPIC_2_BUG_1/DEPLOY_CONFIG_1.md
Precondition: .milkyflow/agents/devops/answers/EPIC_2_BUG_1/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_1_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_1_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.
… Let me start by reading the necessary files to understand the task.
[tool] view {'path': '/home/oem/Documents/Sandbox/Kody/Projects/Backupper/.milkyflow/agents/devops/answers/EPIC_2_BUG_1/DEPLOY_CONFI
[tool] view {'path': '/home/oem/Documents/Sandbox/Kody/Projects/Backupper/.milkyflow/agents/qa/reports/EPIC_2_BUG_1.md'}
The deployment answer shows "Status: FAILED" (not READY). Let me check the precondition carefully — the instructions say the answer must report READY.
… Let me start by reading the necessary files to understand the task.
[tool] bash {'command': 'ls /home/oem/Documents/Sandbox/Kody/Projects/Backupper/.milkyflow/agents/devops/answers/EPIC_2_BUG_1/', 'de
[tool] bash {'command': 'ls /home/oem/Documents/Sandbox/Kody/Projects/Backupper/.milkyflow/agents/devops/prompts/EPIC_2_BUG_1/ 2>/de
The deployment answer at `.milkyflow/agents/devops/answers/EPIC_2_BUG_1/DEPLOY_CONFIG_1.md` reports **Status: FAILED** (not READY).

Per the precondition in my briefing:

> Precondition: `.milkyflow/agents/devops/answers/EPIC_2_BUG_1/DEPLOY_CONFIG_1.md` exists and reports **READY**. If it does not, stop and report: **there is no deployed environment.**

---

## QA Report — EPIC_2 BUG_1 — Pre-flight Check

**Precondition NOT MET.**

The file `.milkyflow/agents/devops/answers/EPIC_2_BUG_1/DEPLOY_CONFIG_1.md` exists but its lifecycle status is **`FAILED`**, not `READY`. The DevOps Agent recorded two configuration defects that prevented verified readiness:

1. The `backup-cockpit live-import destination list` subcommand does not exist in the deployed branch.
2. The provisioning script leaves the backup account in a "password change required" state, causing `write_permission` to fail with HTTP 401.

**There is no deployed environment ready for QA validation.**

### Required next steps (before QA can proceed)

The Solution Architect must correct `DEPLOY_CONFIG_1.md` (and/or `local/fixtures/provision-pc-fixture.sh`) to address both defects, then route back to DevOps for a clean redeployment that produces a `READY` answer. Only then can QA execute Part 1 (defect gone) and Part 2 (interrupted story validation).
[done] exit=0 premium_requests=1 api=27886ms