docs: add target precedence explanation and improve clarity

- Add explicit target resolution precedence in BREAKING CHANGE section
- Clarify Configuration File options list is commonly used subset
- Point users to schema.json for complete list including deprecated options

Addresses external audit feedback on documentation completeness.

Author: JohannesHoppe

README.md

@@ -79,6 +79,15 @@ You can also and modify your `angular.json` to archive the same:
 ```
 
 You can also use `prerenderTarget` instead of `buildTarget` for prerendered/SSG applications.
+
+**Target Resolution Precedence:**
+
+When multiple build target options are specified, they are resolved in this order:
+1. `prerenderTarget` (if specified) — highest priority, overrides all others
+2. `browserTarget` (deprecated, kept for compatibility)
+3. `buildTarget` (recommended)
+4. Default: `${project}:build:production` if none specified
+
 There is no support for `universalBuildTarget` or `serverTarget` because GitHub Pages only supports static assets and no Server-Side Rendering!
 
 We will then try to deploy the `dist/test/browser` folder to GitHub Pages.
@@ -415,7 +424,7 @@ This can be very useful because it outputs what would happen without doing anyth
 
 ## 📁 Configuration File <a name="configuration-file"></a>
 
-To avoid all these command-line cmd options, you can write down your configuration in the `angular.json` file in the `options` attribute of your deploy project's architect. Just change the kebab-case to lower camel case. Common options in lower camel case:
+To avoid all these command-line cmd options, you can write down your configuration in the `angular.json` file in the `options` attribute of your deploy project's architect. Just change the kebab-case to lower camel case. Commonly used options in lower camel case (see schema.json for complete list including deprecated options):
 
 - baseHref
 - buildTarget