publishing-test-caseslisted

# Publishing Test Cases Create approved Test Cases on the board and link each to the story. Every command comes from `../references/tracker-adapters.md`. ## 1. Verify approval Read the approval record in `.claude/qa/<story-id>.md`. No record, or an empty list → stop and say so. Do not attempt a write. Publish **only** the IDs in the record. A case QA edited but did not approve is not published. ## 2. Resolve what already exists For each approved case: 1. Check the `TC → work-item-id` map in the artifact. 2. If the map is missing or incomplete, query the board by the story-level tag `exloom-qa:<story-id>` to recover the published set in one call. 3. Found → update. Not found → create. Never create a case whose TC-level tag is already on the board. Report the create/update split before starting. ## 3. Build the Steps payload Everything the tester needs to execute goes in the **Steps grid**, in this order: | Row | Action | Expected result | |---|---|---| | 1 | `Precondition: <preconditions>` | *(empty)* | | 2 | `Test data: <test data>` | *(empty)* | | 3+ | One test step each | Its expected result | The precondition and test-data rows are omitted when the case has none. Never write `—` or `None` into a step. Build the XML per `../references/tracker-adapters.md` — entities escaped, ids starting at 2. **Build the XML in a single-quoted shell variable and pass `"$STEPS"`.** Inlining it into a double-quoted `--fields` argument strips the attribute quotes, which silently