docs(cutover): QUICK_REFERENCE spells build, type-check and lint the way the merged tree runs them (objectstack#25803)

The verify tree's adaptation dropped the ui root's turbo-recursive build / type-check / lint
scripts (a nested turbo run inside the root run). The three Install & Build rows still named
them, so quick-reference-commands-4149 'names only scripts the root package.json declares' was
red on the merged tree. The rows now spell the turbo run with a ./*/* filter, measured with
--dry=json from ui/: 46 packages for type-check, 45 for build with @object-ui/site excluded as
the dropped build script excluded it. 4a's QUICK_REFERENCE hunk (Current Release) is
untouched and still applies.

Co-Authored-By: Claude <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CUXv64KLMfYv3ia2sWi6te

Author: claude

ui/QUICK_REFERENCE.md

@@ -9,11 +9,17 @@ A one-page cheat-sheet for working in the `objectui` monorepo.
 ```bash
 pnpm run setup            # Build @objectstack/* at .objectstack-sha, then install (clean checkout)
 pnpm install              # Install all workspace dependencies (once the pinned build exists)
-pnpm build                # Build every package (turbo, parallel & cached)
-pnpm type-check           # Run tsc --noEmit across the workspace (turbo)
-pnpm lint                 # Run eslint across the workspace
+pnpm exec turbo run build --filter='./*/*' --filter='!@object-ui/site'  # Build every ui package (turbo, parallel & cached)
+pnpm exec turbo run type-check --filter='./*/*'                          # Run tsc --noEmit across the ui packages (turbo)
+pnpm exec turbo run lint --filter='./*/*'                                # Run eslint across the ui packages (turbo)
 ```
 
+Run those three from this directory: turbo reads a `./` filter against the directory it is
+launched from, so the filter above selects every package under `packages/`, `apps/` and
+`examples/`. This tree has no `build`, `type-check` or `lint` script of its own, because it
+is a member of the objectstack workspace and a `turbo run` in a member's script would nest
+inside the root's.
+
 ### Run Docs
 
 ```bash