feat(docs): api-reference-parameter-descriptions-audit

[Caneryy]

Closes #26

Summary

• API reference parameter descriptions audit

Test plan

• Relevant tests pass locally
• Manual verification on affected UI or API paths

[drips-wave]

@Caneryy Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

[truthixify]

The api-reference parameter audit work looks substantial (213 + 374 lines across endpoints + types). Two things:

1. Conflict on api-reference/endpoints.mdx against develop:

git fetch origin
git rebase origin/develop
# Keep develop's recent endpoint additions, then re-apply your audit descriptions
git push --force-with-lease

2. Heads up: API reference parameter descriptions audit #26 had been assigned to @emarkees in our morning batch. @emarkees — please coordinate with @Caneryy on the issue thread if you'd already started.

[Caneryy]

Rebased onto develop and resolved the conflict in api-reference/endpoints.mdx.

Conflict resolution:

• Kept develop's recent endpoint additions (typescript no-check blocks, path parameter tables)
• Preserved audit cross-references (e.g. Chat endpoint now links to ChatResponse instead of duplicating inline types)
• types.mdx auto-merged cleanly — Federation types from develop + parameter descriptions from this PR

Also retargeted the PR base from main → develop to match repo convention.

Ready for re-review.

[Caneryy]

@truthixify check please