fix(processor): preserve existing comment as fallback for accessor signatures

[udayreddy-s]

Summary

When resolving accessor types in processor.mjs, the existing
comment on the accessor was being unconditionally overwritten
by the signature comment — even when the signature comment
was undefined or empty.

This PR uses nullish coalescing (??) to fall back to the
existing accessor.comment when the signature comment is
missing, preserving any previously set comment.

This is a minimal, targeted improvement that avoids adding
unnecessary optional chaining on getSignature or
setSignature themselves — since as noted in #71, these
will always be defined when the reflection kind is Accessor.

Relates to: #71

What kind of change does this PR introduce?
Bug fix — prevents accidental comment loss during
accessor type resolution

Did you add tests for your changes?
No

Does this PR introduce a breaking change?
No

Use of AI
No AI was used for this change

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
webpack-doc-kit	Ready	Preview, Comment	Apr 23, 2026 3:56am

[udayreddy-s]

Closing this — after reviewing PR #71 more carefully, I realized this overlaps with the nullish coalescing improvement already proposed there. Apologies for the duplicate.