Fix remaining READ-convention sample links across this PR's 18 articles

The same plain-backtick "See sample: \`x.good.al\`." form fixed on
al-methods-limited-during-write-transactions (PR #161) turned up
repo-wide on 15 more of this PR's articles - Knowledge-Retrieval.ps1
requires the markdown-link form to associate a sample with its
article. All 16 fixed; the four local validators (frontmatter,
knowledge-index, knowledge-retrieval, review-fixtures, skill-index)
pass.

microsoft/knowledge/data-modeling/check-post-line-batch-pattern.md

@@ -19,10 +19,10 @@ Business Central's own journal-based posting routines consistently follow a thre
 
 `Check Line` reads setup/dimension data only on its first call and shows no UI beyond errors. `Post Line` only operates on the record passed to it — never the Journal table — so it can be called directly by other posting code, including a document posting routine. `Post Batch` is the only one of the three that reads and updates the Journal table, and it is the only one invoked from the Post action on a journal page. A `-Post` document codeunit is never called directly from a page; a page calls a `-Post (Yes/No)` confirmation wrapper instead, so the same `-Post` codeunit can also run unattended from a batch-posting report.
 
-See sample: `check-post-line-batch-pattern.good.al`.
+See sample: [`check-post-line-batch-pattern.good.al`](check-post-line-batch-pattern.good.al).
 
 ## Anti Pattern
 
 A single monolithic posting codeunit that reads the Journal table, validates lines, writes ledger entries, and shows confirmation dialogs all in one procedure. It cannot be reused by another posting routine without fabricating journal records, and it cannot run unattended because it insists on user interaction.
 
-See sample: `check-post-line-batch-pattern.bad.al`.
+See sample: [`check-post-line-batch-pattern.bad.al`](check-post-line-batch-pattern.bad.al).

microsoft/knowledge/data-modeling/dimension-management-wiring.md

@@ -26,10 +26,10 @@ For a master table, validate each shortcut dimension field through `ValidateDimV
 
 For a document table, when the field that attaches the document to a master record changes (e.g. `Customer No.`), call `AddDimSource` naming that master table and key, then `GetDefaultDimID` to compute the document's new `Dimension Set ID`, inheriting the master's Default Dimension records. Pass `0` for `GetDefaultDimID`'s `InheritFromDimSetID` argument in this case — passing the document's *existing* `Dimension Set ID` instead inherits whatever dimensions were already in it, so a value the previous linked record supplied can survive into the new one even where the new record has no default for that dimension. Validate the document's own Shortcut Dimension fields through `ValidateShortcutDimValues`, which updates that same `Dimension Set ID` in place rather than persisting a separate Default Dimension record.
 
-See sample: `dimension-management-wiring.good.al`.
+See sample: [`dimension-management-wiring.good.al`](dimension-management-wiring.good.al).
 
 ## Anti Pattern
 
 Adding a dimension-looking field with only a `TableRelation` to Dimension Value, and no call into `DimensionManagement` at all. The field accepts input but never becomes a real Default Dimension record, so it does not validate against blocked values and does not flow into postings.
 
-See sample: `dimension-management-wiring.bad.al`.
+See sample: [`dimension-management-wiring.bad.al`](dimension-management-wiring.bad.al).

microsoft/knowledge/data-modeling/do-not-change-primary-key.md

@@ -19,10 +19,10 @@ Once a table has shipped — to AppSource, or to any customer environment that h
 
 Leave a published table's key exactly as shipped. Model a new discriminating dimension as a separate table with its own key instead of adding a field to the existing key, and branch orchestration code by the new dimension rather than filtering one shared table on an extra key field.
 
-See sample: `do-not-change-primary-key.good.al`.
+See sample: [`do-not-change-primary-key.good.al`](do-not-change-primary-key.good.al).
 
 ## Anti Pattern
 
 Adding a field to a published table's primary or clustered key to distinguish a new case. This fails AppSource validation or any customer upgrade with `AS0009` as soon as rows already exist under the old key shape, whether the field is being added, removed, or reordered.
 
-See sample: `do-not-change-primary-key.bad.al`.
+See sample: [`do-not-change-primary-key.bad.al`](do-not-change-primary-key.bad.al).

microsoft/knowledge/data-modeling/testfield-required-setup-field.md

@@ -19,10 +19,10 @@ A procedure that reads a field from a setup or configuration table inside a bran
 
 Once a business rule has decided that a setup-table field's value is required for a branch to behave correctly, call `TestField` on it before use, even though a plain read would "work" by returning a blank or zero without erroring. Write a test that blanks the setup field and asserts the resulting error, so the guard itself is verified rather than merely present.
 
-See sample: `testfield-required-setup-field.good.al`.
+See sample: [`testfield-required-setup-field.good.al`](testfield-required-setup-field.good.al).
 
 ## Anti Pattern
 
 Reading a required setup-table field behind a presence check that falls through to a default value instead of erroring. This looks defensive because it never crashes, but it converts "administrator forgot to configure this" into "system silently did something else" — worse than a hard failure, because nobody is told anything went wrong.
 
-See sample: `testfield-required-setup-field.bad.al`.
+See sample: [`testfield-required-setup-field.bad.al`](testfield-required-setup-field.bad.al).