Allow an explicit no-framework-docs entry in the alignment evidence

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Author: MariusStorhaug

src/docs/Ways-of-Working/PR-Format.md

@@ -127,7 +127,7 @@ The **Technical details** block is for reviewers and maintainers. Include intern
     | `src/**` (PowerShell) | Naming, Functions | Module source layout | Aligned |
     | `.github/workflows/**` | GitHub Actions | Reusable workflow contract | Exception — Owner/Repo#123 |
 
-    A result is `Aligned`, `Fixed in this PR`, or `Exception` with a link to the follow-up issue that carries it.
+    A result is `Aligned`, `Fixed in this PR`, or `Exception` with a link to the follow-up issue that carries it. A surface with no framework or domain documentation of its own is recorded as `None (no framework-specific docs)`.
 
 The **Relevant issues (or links)** block is required and uses fully qualified references (`Owner/Repo#N`) so links work across repositories.
 

src/docs/Ways-of-Working/Workflow-Stages/Implement.md

@@ -64,7 +64,7 @@ Record the outcome as one row per changed surface:
 | `src/functions/**` (PowerShell) | Naming, Functions, Error Handling | Module source layout | Aligned |
 | `.github/workflows/**` | GitHub Actions | Reusable workflow contract | Exception — Owner/Repo#123 |
 
-A result is `Aligned`, `Fixed in this PR`, or `Exception` with a link that justifies it. Carry the table into the pull request's Technical details block per [PR Format](../PR-Format.md), so [Review](Review.md) can verify the pass instead of guessing whether it happened.
+A result is `Aligned`, `Fixed in this PR`, or `Exception` with a link that justifies it. Where a changed surface has no framework or domain documentation of its own, write `None (no framework-specific docs)` rather than inventing a pseudo-link. Carry the table into the pull request's Technical details block per [PR Format](../PR-Format.md), so [Review](Review.md) can verify the pass instead of guessing whether it happened.
 
 **Stop rule.** Fix what is in scope for the closing Task or Bug and small enough to keep the pull request reviewable. When a finding is out of scope, systemic across the repository, or would change the shape of the pull request, file a follow-up issue through [Define](Define.md), link it in the table as an exception, and leave the change as it is. The pass improves alignment; it does not turn into a second delivery.