fix(asana): complete and verify requested task workflows

[masoudgolchin]

Summary

The Asana helper now reads direct subtask descriptions and exact comments, downloads attachments, completes a named task, and posts real mentions with verified saved content. A project can choose its cache folder.

Dry runs make no local or remote writes. Failed reads return a nonzero exit status. Completion checks saved state after an uncertain response; comments are not blindly retried. Cache updates preserve human-written files, and 1Password unlock has a bounded timeout.

Release the shared base pack as 1.11.0 and the marketplace as 2.15.0 for Claude Code and Codex.

Why

• Refs asana#1217577281347968
• Asana task
• Repeated manual API work was leaving missing context, incomplete task updates, and misleading success reports.

Test plan

• All 64 repository tests passed, including 30 independent Asana CLI workflow tests with a local server and synthetic credentials.
• Package validation passed for 9 packs and 43 skills; generated manifests are current.
• Six live API checks passed on a separate bot-owned test task: configured cache and child instructions, attachment bytes, completion preview, multiline mention and exact story readback, parent-only completion, and repeat completion. Test parent and child were completed after verification.
• Detailed scope and limits: tests/skill-evals/asana/2026-09-09.md.
• After merge: base 1.11.0 installed in Codex, the whole installed pack matched the release, all six live checks passed again, and a fresh Codex session discovered 1.11.0 and ran its bundled --help with exit code 0.
• The named Asana task was completed using the installed helper; saved completion was verified.

Notes

Direct subtask notes are explicit; deeper task history still needs a separate pull. Mentions use Asana rich text and follower membership; the API does not prove delivery to a recipient's inbox. Downloads stop at 100 MiB and report provider-only attachments.

CRE Daily main and stage contain no tracked Asana fork; its current project contract uses the marketplace base pack. No client site code changes.