test(client): declare the nested-relation rest pin as a client test input

The census ledger row added for the rest pin names
packages/rest/src/analytics-nested-relation-filter.test.ts: it pins that
file's five producer reads of analytics.query. That makes it a real input
of @objectstack/client's tests, so it is declared per-file in the client's
cross-package input globs and mirrored into client#test's turbo inputs. A
changed call count in the rest pin now re-runs the client suite.

Claude-Session: https://claude.ai/code/session_01XY5uCwTjZj7884yYtyur4H
Co-authored-by: Claude <noreply@anthropic.com>

Author: claude

scripts/cross-package-test-inputs.mjs

@@ -748,6 +748,10 @@ export const CROSS_PACKAGE_TEST_INPUTS = {
       // `@objectstack/spec` already declares it verbatim, so Layer C reaches it
       // today. What stays uncovered stays recorded in that test's header.
       'scripts/**',
+      // The census's hand LEDGER names this file: a NOT_SDK row pins its five
+      // producer reads of `analytics.query`. A real input, so a changed call
+      // count re-runs this suite.
+      'packages/rest/src/analytics-nested-relation-filter.test.ts',
     ],
     heldBy: {
       // `scripts/**` is rostered TODAY through the census's own

turbo.json

@@ -174,7 +174,8 @@
         "$TURBO_ROOT$/scripts/check-route-envelope.mjs",
         "$TURBO_ROOT$/scripts/js-comment-mask.mjs",
         "$TURBO_ROOT$/scripts/js-comment-mask.d.mts",
-        "$TURBO_ROOT$/scripts/**"
+        "$TURBO_ROOT$/scripts/**",
+        "$TURBO_ROOT$/packages/rest/src/analytics-nested-relation-filter.test.ts"
       ]
     },
     "@objectstack/lint#test": {