Response overflow outlines, SPARQL VALUES fix, entity field narrowing
Three fixes: bounded response overflow on well-connected entities, a SPARQL label-injection bug, and a bandwidth win on entity fetches.
Added:
kind/sections/retrieval_noticeoutput fields onwikidata_get_entityandwikidata_get_statements— an oversized response now returns an outline (available sections with byte sizes, largest first) instead of a payload past the client's token limit;wikidata_get_statementson Q30 drops from 519,077 to 13,893 bytes (#17)
Changed:
wikidata_get_entity'sfieldsnow forwards to the REST API's?_fields=parameter, narrowing the upstream fetch instead of fetching the full entity and filtering client-side —Q76with_fields=labelsis 6,703 bytes versus 344,114 whole (#26)
Fixed:
WikidataSparqlService.prepareQuery()'s labelSERVICEinjection regex now recognizes a trailingVALUESclause, so it no longer injects the SERVICE block inside a trailing VALUES data block and breaks the query (#20)
264 tests pass; bun run devcheck clean.