[scripts] Update the reference coverage tester to look at package-level items

[AlexJerabek]

No description provided.

[learn-build-service-prod]

PoliCheck Scan Report

The following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 issues. Other issues are also a high priority. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans.

#	File	Term	Line	Sev	AI Recommendation	Class	AI Review Details
1	generate-docs\API Coverage Report.csv	slope	11827	1	No action needed	Diversity	Details The term `slope` is used as an enum value for a bevel type in a software API, referring to a geometric or graphical property (an incline), not a person or in any offensive context. This matches rule 1, so it does not need to be replaced or removed.
2	generate-docs\API Coverage Report.csv	country	1344	2	No action needed	Geopolitical	Details The term `country` is used as an enum value in the context of `Excel.ChartMapAreaLevel`, which is a field or filter name in an API or code reference. According to the rules, when the word is used as a field, filter, property, or enum name, it does not need to be replaced or removed.
3	generate-docs\API Coverage Report.csv	Bengali	15021	2	Replacement required	Geopolitical	Details The term `Bengali` is used as an enum value for a language identifier, and the context is not specifically for India. According to the rules, when referring to the language or script name in content for Bangladesh, it should be replaced with 'Bangla'. Since this is a language identifier and could be used in the context of Bangladesh, it is best to update it to 'Bangla' to align with current naming conventions and avoid sensitivity.
4	generate-docs\API Coverage Report.csv	Oriya	15118	2	Replacement required	Geopolitical	Details The term `Oriya` is used as an enum value for a language identifier in a modern software context. The modern and preferred term is `Odia`, so it should be updated for accuracy and sensitivity.

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

[learn-build-service-prod]

Learn Build status updates of commit 655dbdb:

✅ Validation status: passed

File	Status	Preview URL	Details
generate-docs/API Coverage Report.csv	✅Succeeded
generate-docs/api-extractor-inputs-custom-functions-runtime/tsdoc-metadata.json	✅Succeeded
generate-docs/api-extractor-inputs-office-release/tsdoc-metadata.json	✅Succeeded
generate-docs/api-extractor-inputs-office-runtime/tsdoc-metadata.json	✅Succeeded
generate-docs/api-extractor-inputs-powerpoint-release/PowerPoint_1_1/tsdoc-metadata.json	✅Succeeded
generate-docs/api-extractor-inputs-powerpoint-release/PowerPoint_1_2/tsdoc-metadata.json	✅Succeeded
generate-docs/api-extractor-inputs-powerpoint-release/PowerPoint_1_3/tsdoc-metadata.json	✅Succeeded
generate-docs/api-extractor-inputs-powerpoint-release/PowerPoint_1_4/tsdoc-metadata.json	✅Succeeded
generate-docs/api-extractor-inputs-powerpoint-release/PowerPoint_1_5/tsdoc-metadata.json	✅Succeeded
generate-docs/api-extractor-inputs-powerpoint-release/PowerPoint_1_6/tsdoc-metadata.json	✅Succeeded
generate-docs/api-extractor-inputs-powerpoint-release/PowerPoint_1_7/tsdoc-metadata.json	✅Succeeded
generate-docs/api-extractor-inputs-powerpoint-release/PowerPoint_1_8/tsdoc-metadata.json	✅Succeeded
generate-docs/api-extractor-inputs-powerpoint-release/PowerPoint_1_9/tsdoc-metadata.json	✅Succeeded
generate-docs/api-extractor-inputs-powerpoint/tsdoc-metadata.json	✅Succeeded
generate-docs/api-extractor-inputs-word-release/word_1_1/tsdoc-metadata.json	✅Succeeded
generate-docs/api-extractor-inputs-word-release/word_1_2/tsdoc-metadata.json	✅Succeeded
generate-docs/api-extractor-inputs-word-release/word_1_3_hidden_document/tsdoc-metadata.json	✅Succeeded
generate-docs/api-extractor-inputs-word-release/word_1_3/tsdoc-metadata.json	✅Succeeded
generate-docs/api-extractor-inputs-word-release/word_1_4_hidden_document/tsdoc-metadata.json	✅Succeeded
generate-docs/api-extractor-inputs-word-release/word_1_4/tsdoc-metadata.json	✅Succeeded
generate-docs/api-extractor-inputs-word-release/word_1_5_hidden_document/tsdoc-metadata.json	✅Succeeded
generate-docs/api-extractor-inputs-word-release/word_1_5/tsdoc-metadata.json	✅Succeeded
generate-docs/api-extractor-inputs-word-release/word_1_6/tsdoc-metadata.json	✅Succeeded
generate-docs/api-extractor-inputs-word-release/word_1_7/tsdoc-metadata.json	✅Succeeded
generate-docs/api-extractor-inputs-word-release/word_1_8/tsdoc-metadata.json	✅Succeeded

This comment lists only the first 25 files in the pull request.
For more details, please refer to the build report.