Fix harness_list output validation for PR activity

[cursor]

Description

Fixes harness_list(resource_type="pr_activity") output validation when the Harness Code activities API returns a bare array. The list tool now normalizes bare arrays and common list-array wrapper keys into { items, total } before compacting and formatting, ensuring MCP structuredContent is present for the declared output schema.

Type of Change

• Bug fix
• New feature
• Refactor
• Documentation
• Other

Checklist

• Tests pass
• Typecheck passes

Verification:

• pnpm test tests/tools/tool-handlers.test.ts
• pnpm typecheck
• pnpm build
• pnpm test

  

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[cursor]

1 finding.

• Medium — harness_list is fixing list-shape drift in the wrong layer. The new normalization in src/tools/harness-list.ts makes this tool return { items, total } for bare-array / raw-envelope responses, but the affected resource definitions still advertise responseExtractor: passthrough instead of using the registry extractor layer that already owns list normalization. That splits the contract across layers, duplicates backend-shape knowledge, and leaves other Registry.dispatch(..., "list") consumers inconsistent. The cleaner fix is to normalize pr_activity (and any sibling raw-array PR list endpoints) in the resource extractor layer, reusing the existing extractor helpers there.

  

_{Sent by Cursor Automation: Sunil On Demand Architecture Review}

[cursor]

Medium: this is patching the symptom in the generic tool instead of fixing the list contract where the repo already normalizes response shapes.

If pr_activity is a bare-array list, the canonical fix is to switch that resource off responseExtractor: passthrough and use a registry extractor (v1ListExtract() or a dedicated extractor) in src/registry/toolsets/pull-requests.ts. Doing it here duplicates list-envelope knowledge the registry already owns, and Registry.dispatch(..., "list") still returns raw arrays to other shared consumers that assume { items, total } (for example harness_search). That’s exactly the kind of boundary drift CLAUDE.md/AGENTS.md ask us to avoid.