Update site-design-json-schema

[ntennant4]

Created via Content Mentor Quick Workspace

[learn-build-service-prod]

Learn Build status updates of commit 5d164e5:

❌ Validation status: errors

Please follow instructions here which may help to resolve issue.

File	Status	Preview URL	Details
	❌Error		Details

• [Error: CannotMergeCommit] Cannot merge commit 5d164e5abfb89c98b01564d8a80a032dd345f182 in branch ntennant4-1783015325730 of repository https://github.com/ntennant4/sp-dev-docs into branch main (commit 29c6c9717bba640926dfd932eefde93913ecc453). Please follow this documentation: https://help.github.com/articles/resolving-a-merge-conflict-using-the-command-line/ to use git.exe to resolve you content conflicts locally and then push to remote.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

[learn-build-service-prod]

Learn Build status updates of commit 8b1fdd0:

❌ Validation status: errors

Please follow instructions here which may help to resolve issue.

File	Status	Preview URL	Details
	❌Error		Details

• [Error: CannotMergeCommit] Cannot merge commit 8b1fdd07cb556da70dbc71194499591ace8a221d in branch ntennant4-1783015325730 of repository https://github.com/ntennant4/sp-dev-docs into branch main (commit 29c6c9717bba640926dfd932eefde93913ecc453). Please follow this documentation: https://help.github.com/articles/resolving-a-merge-conflict-using-the-command-line/ to use git.exe to resolve you content conflicts locally and then push to remote.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

[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 and severity-2 issues. 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.

✅ No issues found

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 6e88c26:

💡 Validation status: suggestions

File	Status	Preview URL	Details
docs/declarative-customization/site-design-json-schema.md	💡Suggestion	View	Details

docs/declarative-customization/site-design-json-schema.md

• Line 6, Column 12: [Suggestion: ms-author-invalid - See documentation] Invalid value for 'ms.author', 'ntennant4' is not a valid Microsoft alias.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.