testing-tasklisted

# Testing Task Skill Produces the final hand-off to the (Arabic-speaking) testing team and closes the workflow. ## When to Use - The `testing` action — only from stage `deployed` or `deployment_skipped`. ## Inputs - The **approved implemented behavior**: `docs/ai-context/TASK_PLAN.md` (Required Behavior + Acceptance Criteria as approved), the feature-changelog entry updated at finalization, the implementation summary. - Deployment status from state. ## Outputs - Arabic `Title` + `Description` **copied to the host clipboard** in their original logical Unicode order, ready to paste into the testing team's task-management system, plus a **terminal-only visual preview** of the same text so it is readable in this terminal — content rules in [references/arabic-testing-task-rules.md](references/arabic-testing-task-rules.md). - **No file.** Never create `docs/ai-context/testing-task-ar.md`, `.claude/testing-task-ar.md`, or any replacement testing-task file anywhere. - State: `testing_task = {status: "generated", generated_at}`; `state transition completed`. The generated Arabic text itself is never stored in state. ## Preconditions - Stage is `deployed` or `deployment_skipped`; commit verified. ## Order of Operations The clipboard copy comes **first**, and everything else depends on it: 1. `CLI clipboard copy --preview` with the finished Arabic text on stdin. 2. Exit code `0` → the command has copied the logical text and printed a visual preview