ListStatuses was called with default options, so Forgejo's server
default PageSize (30 == EmbeddedListCap) silently capped responses
at the cap. The >cap truncation check in resource.Bounded never
fired and the truncated/list_tool sentinel never surfaced for SHAs
with more than 30 status contexts.
Request EmbeddedListCap+1 explicitly so Bounded can correctly
distinguish "at-cap" from "over-cap".
Closes forgejo-mcp-827.
Ref PR #172 review https://codeberg.org/goern/forgejo-mcp/pulls/172#issuecomment-16022165
ee1217d830