docs: exclude package-private members from API reference

[dgarcia360]

Closes #484

How to test

1. Build the docs.
2. Open http://127.0.0.1:5500/api/Client/
3. Check there are no (package) members.

[coderabbitai]

📝 Walkthrough

Walkthrough

The js-doc-config.js file is updated to add an explicit access configuration array containing "public", "protected", and "undefined". Explanatory comments are also added to describe the intent. This prevents members tagged with @package from appearing in the generated public API documentation, as JSDoc will now only render members matching the listed access levels.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'docs: exclude package-private members from API reference' directly and clearly describes the main change in the PR.
Description check	✅ Passed	The description references issue #484 and provides testing instructions related to excluding package-private members from API documentation.
Linked Issues check	✅ Passed	The PR successfully addresses issue #484 by modifying js-doc-config.js to exclude @package members from the public API documentation.
Out of Scope Changes check	✅ Passed	The changes are limited to js-doc-config.js with configuration updates focused on excluding package-private members, which is directly aligned with the linked issue objective.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[dgarcia360]

cc/ @adespawn @annastuchlik

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@js-doc-config.js`:
- Around line 7-10: The access property in the JSDoc configuration is currently
set to an array value, but JSDoc v4 expects a single string value. Change the
access property from the array format ["public", "protected", "undefined"] to a
single string value representing the desired access level, such as "public" or
"protected". Note that JSDoc v4 only supports filtering by a single access level
at a time, so you will need to choose one primary access level for the access
property.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: a9bab65a-b18b-4d54-9033-97541cb461f9

📥 Commits

Reviewing files that changed from the base of the PR and between 1df6525 and d951d0d.

📒 Files selected for processing (1)

• js-doc-config.js