/api/v1/search answers kind=pulls (and kind=issues meaning issues only), so a narrowed search returns N of the kind asked for #7633

forge search --kind pulls (#7463) asks /api/v1/search for kind=issues at its 100-hit ceiling and keeps the pulls on the client, because the API's issues kind answers both issues and pulls. When more than 100 conversations match and fewer than N of them are pulls, the CLI prints fewer than N though more exist (it says so with truncated.issues).

Let src/actions/search.ts take kind=pulls, and filter issues from pulls in the query, so the limit applies to the kind asked for; then the CLI passes --kind and --limit straight through and narrowConversations goes. A test: 150 issues and 5 pulls matching, kind=pulls&limit=5 returns the 5 pulls.

Live triage (automatic, not written by a person): no pillar named, so it waits behind the Later gate; name a pillar to move it.