Summary

Adds detection and tracking of unnamed exports in Kibana plugins. When a JSDoc-style comment appears above a line that isn't a proper declaration (e.g., a stray export or a comment above a non-declaration), the tooling now identifies these as unnamed exports and reports them as validation issues.

Before / After Example

Given an index file with a stray export like:

/** Some docs for a random export */
export { something } from './internal';

Before this PR:

The tooling silently skipped these nodes with no indication of an issue:

info pluginFoo: Processing public scope...

After this PR:

The tooling identifies the unnamed export and reports it:

warn pluginFoo: 1 unnamed export(s) found
  - public/index.ts:5 — `export { something } from './internal';`

And a new --stats unnamed flag allows listing all unnamed exports:

node scripts/check_package_docs.js --plugin pluginFoo --stats unnamed

Changes

• Add UnnamedExport, UnnamedExportsByPlugin types and unnamedExports field to ApiStats and IssuesByPlugin
• Refactor getDeclarationNodesForPluginScope to return a DeclarationNodesResult containing both nodes and unnamed exports
• Detect unnamed exports in getExportedFileDeclarations when a node has no identifiable name
• Propagate unnamed exports through getPluginApi and getPluginApiMap into stats collection
• Add --stats unnamed CLI flag for listing unnamed exports
• Update integration tests and snapshots

Impact

• Plugins with stray or malformed exports are now surfaced in validation reports
• No change to existing validation pass/fail criteria -- unnamed exports are tracked but do not block

Made with Cursor