📖 [Docs]: Scope issue and PR references by repository (local, remote, external) (#50)

The Ways of Working now explain where issue and pull request references
belong, and how to format them. References live in issues and pull
requests — not in commit messages — and are scoped to where they
resolve.

## Changed: How issues, PRs, and commits reference each other

- **Same repository** — use the `#123` shorthand.
- **Another repository** — use the fully qualified `Owner/Repo#123` form
so the link resolves to the right repository.
- **Outside GitHub** (Jira, Confluence, Slack, external docs, release
announcements) — use the full URL, since no GitHub autolinking applies.
- **Commit messages** — carry no issue or PR references at all. The pull
request links the work to its issue (via a closing keyword such as
`Fixes #123`); commits describe the change itself.

Updated documents:

- **Issue Format** gains a "Properties of every issue" rule covering the
same-repo, cross-repo, and external cases.
- **PR Format** scopes the Related issues rule the same way, and its
examples now model both forms — a same-repo `Fixes #123` alongside a
cross-repo `PSModule/Process-PSModule#124`.
- **Commit Conventions** rule 5 now keeps issue and PR references out of
commit history entirely.

## Technical Details

- `src/docs/Ways-of-Working/Issue-Format.md`: new bullet under
"Properties of every issue".
- `src/docs/Ways-of-Working/PR-Format.md`: §4 Related issues rule
reworded; same-repo examples use `#123`/`#218`/`#219`, the cross-repo
example keeps `Owner/Repo#N`.
- `src/docs/Ways-of-Working/Commit-Conventions.md`: rule 5 changed from
"reference issues" to "keep issue and PR references out of commit
messages".
- Implementation plan progress: all three tasks in #49 completed.

<details>
<summary>Related issues</summary>

- Fixes #49

</details>

Author: MariusStorhaug

src/docs/Ways-of-Working/Commit-Conventions.md

@@ -8,7 +8,7 @@ Commit messages serve two audiences: the engineer reading `git log` six months f
 2. **No conventional-commit prefixes.** No `fix:`, `feat:`, `docs:`, `chore:`, `refactor:`, etc. The change type is captured at the PR level — repeating it on every commit adds noise without information.
 3. **No generic messages.** `Update for PR`, `WIP`, `fixes`, `more changes` — all forbidden. They erase traceability.
 4. **One logical change per commit.** Micro-iterative discipline. If a change touches three unrelated concerns, that's three commits.
-5. **Reference issues by number when natural** — but don't force it. `Fixes #N` belongs in the PR description, not every commit message.
+5. **Keep issue and pull request references out of commit messages.** Cross-references to issues and pull requests belong in the PR description and in issues — not in commit history. The pull request links the work to its issue (via a closing keyword such as `Fixes #123`); commits describe the change itself.
 
 ## Examples
 

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

@@ -13,6 +13,7 @@ Every issue in the PSModule organization follows the same structure. The format
 - **Comments record change history only.** Each description update is accompanied by a comment summarizing what changed and why.
 - **Tone is impersonal.** No first-person ("I", "my") or second-person ("you", "your") language. Neutral references like "the user", "the developer", or passive constructions.
 - **External references are hyperlinks.** Every mention of an API, RFC, library, doc, or tool is a clickable `[text](url)` link. No bare URLs.
+- **Issue and PR references are scoped to their target.** Use the `#123` shorthand for an issue or pull request in the same repository, and the fully qualified `Owner/Repo#123` form for one in another repository so the link resolves to the right place. Outside GitHub — Jira, Confluence, Slack, or any surface without GitHub autolinking — use the full URL (`https://github.com/Owner/Repo/issues/123`).
 - **No duplicates.** Existing issues are searched before creating or restructuring. Duplicates are consolidated or cross-linked.
 
 ## Title

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

@@ -103,13 +103,13 @@ Omit the section entirely if there's nothing noteworthy.
 
 ### 4. Related issues
 
-A collapsible `<details>` block at the very end of the description containing issue links. Always use fully qualified references (`Owner/Repo#N`) so links work across repositories.
+A collapsible `<details>` block at the very end of the description containing issue links. Use the `#123` shorthand for issues in the same repository and the fully qualified `Owner/Repo#123` form for issues in another repository so links resolve to the right place. When a reference appears outside GitHub (release announcements, Jira, Slack, external docs), use the full URL (`https://github.com/Owner/Repo/issues/123`).
 
 ```markdown
 <details>
 <summary>Related issues</summary>
 
-- Fixes PSModule/GitHub#123
+- Fixes #123
 - PSModule/Process-PSModule#124
 
 </details>
@@ -155,8 +155,8 @@ Commands that query a specific repository, enterprise, or release by name now re
 <details>
 <summary>Related issues</summary>
 
-- Fixes PSModule/GitHub#218
-- PSModule/GitHub#219
+- Fixes #218
+- #219
 
 </details>
 ````