[anurag4DSB]

Spec: https://claude.ai/artifact/QhKsCqtGNzaVice35nvip9#bcc30d01-27db.m1yth80jczv.20396

Intent: why does this change exist?

• An account needs to find all its destinations, page by page.

System impact: what's affected, including downstream?

• List reads the record store with the requester's account as the key prefix.

Preserved behavior: what explicitly stays the same?

• A List never shows the destinations of another account.

Intended change: what's different after this PR?

• List answers pages of 100 by default, with max-items up to the listing limit and NextMarker.
• Each entry is the element that Get answers.

Verification: how do we know this worked, or how would we know if it didn't?

• Unit tests run the handler and its paging on mem.
• Functional route tests in s3c-ft-tests and file-ft-tests compare List entries with Get.

https://claude.ai/code/session_01LSEjuApZSsJxDp6dw1FhVa

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 88.28%. Comparing base (b78b066) to head (19b6121).
✅ All tests successful. No failed tests found.

Additional details and impacted files

Files with missing lines	Coverage Δ
lib/api/api.js	93.85% <100.00%> (+0.01%)	⬆️
lib/api/notificationDestinationList.js	100.00% <100.00%> (ø)

... and 1 file with indirect coverage changes

@@                             Coverage Diff                             @@
##           improvement/CLDSRV-1065-destination-get    #6367      +/-   ##
===========================================================================
+ Coverage                                    88.19%   88.28%   +0.08%     
===========================================================================
  Files                                          214      215       +1     
  Lines                                        14638    14689      +51     
===========================================================================
+ Hits                                         12910    12968      +58     
+ Misses                                        1728     1721       -7     

Flag	Coverage Δ
checksums-disabled-tests	35.18% <21.56%> (-0.05%)	⬇️
file-ft-tests	71.65% <80.39%> (+0.15%)	⬆️
file-ft-tests-null-compat	72.11% <80.39%> (+0.14%)	⬆️
kmip-ft-tests	28.00% <21.56%> (-0.03%)	⬇️
mongo-v0-ft-tests	70.80% <21.56%> (-0.18%)	⬇️
mongo-v1-ft-tests	70.78% <21.56%> (-0.20%)	⬇️
multiple-backend	35.91% <21.56%> (-0.05%)	⬇️
s3c-ft-tests-v0	66.90% <80.39%> (+0.12%)	⬆️
s3c-ft-tests-v0-null-compat	66.97% <80.39%> (+0.13%)	⬆️
s3c-ft-tests-v1	66.88% <80.39%> (+0.12%)	⬆️
sur-tests	36.45% <21.56%> (-0.06%)	⬇️
sur-tests-inflights	39.24% <21.56%> (-0.09%)	⬇️
unit	76.27% <100.00%> (+0.08%)	⬆️
utapi-v2-tests	35.14% <21.56%> (-0.05%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.