> For the complete documentation index, see [llms.txt](https://developer.eagle.cool/plugin-api/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.eagle.cool/plugin-api/plugin-review/results.md).

# Review Results and Resubmission

Required changes may be identified during either the initial scan or human review. A submission that does not pass is not permanently banned; it means the current version is not yet ready for publication.

## Approved Submissions

Passing the initial scan moves the plugin to human review. The plugin is approved for publication only after human review also passes.

Feedback may include non-blocking recommendations. Developers can choose whether to address them in a later release, and they do not change the current approval result.

## Submissions That Require Changes

Feedback lists confirmed issues that must be fixed in the current submission. Each issue will aim to identify:

* an objective problem the developer can verify;
* the affected file, setting, listing field, observable behavior, or visual asset;
* why the issue affects users, safety, or publication quality;
* an actionable correction.

Feedback includes only issues that actually block the submission. Areas that passed, were not completed, or contain only recommendations are not added merely to fill out a checklist.

## Resubmitting

1. Address every required change in the review feedback.
2. Repackage the plugin instead of reusing the previous `.eagleplugin` file.
3. Confirm that the new package contains no stale build output, sensitive data, or test files.
4. Make sure listing copy, visual assets, and the changelog match the new version.
5. Submit the new version for review.

The resubmitted version goes through the initial scan and human review again. Results that applied only to the previous package are not automatically applied to a new build.

## Review Could Not Be Completed

If review cannot be completed because of a temporary system or data-access issue, this is not treated as a plugin violation. We will handle the submission according to the situation. Developer action is requested only when the plugin itself lacks required files, cannot be tested, or requires additional information.

Before resubmitting, use [Prepare Plugin](/plugin-api/publishing/prepare.md) and review the complete [Review Criteria](/plugin-api/plugin-review/criteria.md).