wrap-uplisted

<!-- Generated by scripts/build-adapters.sh. Do not edit directly. --> # Wrap Up Run this skill manually from time to time or as the final step after a task reaches its goal. It is a delivery audit and cleanup pass, not permission to expand scope or hide unfinished work. ## 1. Reconstruct the task - Read the original request, acceptance criteria, task plan, and final diff. - Write a short objective statement and an acceptance matrix: each requested outcome, its evidence, and its status. - Compare the result with the original idea, not merely with the implementation plan. Mark anything ambiguous or unverified as `UNKNOWN` rather than assuming it is complete. - Identify the exact repositories, worktrees, branches, files, services, and temporary paths owned by this task. Preserve pre-existing user work. ## 2. Verify the implementation - Inspect the final diff and confirm every requested behavior is implemented. - Check related tests, types, docs, configuration, migrations, and feature flags where the change requires them. - Run the repository-defined checks appropriate to the change. Follow local instructions and use the project’s package scripts rather than bypassing its tooling. - Prefer the smallest meaningful verification first, then the full applicable suite. Record exact commands and results. - If a check fails, determine whether it is caused by this task. Do not call the task green because an unrelated check happened to pass. - For user-facing behavior, require real