knowledgepixels / nanodash / 32342034803

41%

push

github

Point view-display queries at repo/full-based versions (5 SERVICE -> 2)

GET_VIEW_DISPLAYS -> RAWlJqJ5afOTN0AIDP3rnSCysQer9B4pmSC6QbzssTAyc
(supersedes RArKslem), GET_VIEW_DISPLAYS_UNRESOLVED ->
RAkIkmSiwDT-bgYZhGtknPhpkHsJcx0Q3nP0u8OyO_fZ4 (supersedes RAXdRFNL).

Same semantics, endpoint rebased from the ViewDisplay type repo onto
repo/full: the preset branch and all ResourceView lookups become local
patterns; only the two repo/spaces state lookups stay federated. The
per-hop loopback federation was the main amplifier of the rdf4j
connection-pool deadlock behind the fleet-wide /api wedges (thread dump
2026-08-20: 22 of 28 pool-blocked threads were get-view-displays; the
unresolved variant's pin lookups fired one federated round-trip per
referenced view under a nested-loop join).

Validated byte-for-byte identical against the previous versions on clean
data across standalone displays, preset assignments, governed views, an
agent's own page, a non-space maintained resource, and rival space refs
(anti-bleed intact). Constants are pinned full IDs (QueryApiAccess.get
does not follow supersedes), hence this bump.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

3273 of 9221 branches covered (35.5%)

Branch coverage included in aggregate %.

6207 of 15243 relevant lines covered (40.72%)

6.47 hits per line