[witbrock]

DGX inbox context previously selected tasks only by message thread IDs, so a native task named in message text could disappear from its projected task list. Coding context also skipped attachment enumeration when the cached count was zero and supplied no file-copy bytes.

Resolve explicit native task references through canonical point reads within the existing worker assignment scope, preserve assignee/evidence and distinguish omitted, failed, excluded and actor-scoped not-found results. Enumerate attachment metadata independently of cached counts. Stage explicitly referenced file copies through the actor-scoped canonical service, retaining identity, SHA-256 and local paths while refusing checksum mismatches. Both prompts explain the distinction between projection, canonical lookup and native attachments.

Validation: 92 targeted Python tests passed; final worker/inbox rerun 80 passed. Two existing unread/rendering frontend suites passed (14 tests). Python 3.11 syntax, PDM lock and diff checks passed. Regressions cover a task present but omitted from the initial projection, cached-zero attachments, denied file reads and checksum mismatch.

Merge decision changes — the bounded context repair is ready. The full native task remains blocked on controller activation and live evidence: this coding run cannot canonically inspect the actual parent task/screenshot or reconcile Michael's 17/54 badges. The dated investigation note records concrete counting differences, acceptance cases and the bounded controller handoff. No unread implementation task was created. No public deployment was requested or performed.

Native task: #V#task_agent_67fc1049d5f662f4bf9035ce34ac6819