Address second round of Jesper Schulz-Wedde's review on PR #156

- dimension-management-wiring.md/.good.al: split into the two distinct
  models the article was conflating - master data (Default Dimension
  records via ValidateDimValueCode/SaveDefaultDim) vs. transactional/
  document data (a single Dimension Set ID assembled via AddDimSource +
  GetDefaultDimID, verified against BCApps' ExchRateAdjmtProcess.Codeunit.al).
  Added a compiling document-table example alongside the existing master
  table one.
- Deleted api-page-flowfields-must-be-calcfields (.md/.good.al/.bad.al):
  Microsoft's own FlowFields documentation states a FlowField used as a
  control's direct source expression is automatically calculated on any
  page - no API-page exception is documented, and none could be
  reproduced.
- prefer-email-module.bad.al/.md: Codeunit Mail has no Send/GetErrorDesc
  members; fixed to the real current 7-argument CreateMessage signature,
  and corrected the claim that the legacy path "still runs" - its base
  implementation no longer sends anything, only raises integration events.
- check-post-line-batch-pattern.md/.good.al: reframed from a universal
  invariant to the standard shape, naming the real Gen./Item/CA/Res./Job/
  Insurance/Mfg. Item/FA Jnl.-Check Line/-Post Line/-Post Batch codeunits
  it's based on. Added the missing Check Line companion codeunit so the
  good fixture is internally complete.
- test-data-must-be-random-and-complete.good.al: removed leftover
  "collision-free" wording contradicting the already-corrected article text.
- fixed-choice-set-must-use-enum-not-integer.md: removed the reintroduced
  state-count heuristic ("the line is the state count"), aligned with
  binary-choice-must-be-boolean.md's semantics-based distinction.
- namespace-must-be-verified-from-source.md: removed the false claim that
  the compiler and AL Language Server use different namespace-resolution
  rules.
- intrinsic-al-functions-must-use-modern-casing.md: removed the unverified
  claim that PascalCase is the VS Code formatter's default output.

Worklist completeness: added cues for the 8 rules in data-modeling,
testing, performance, and web-services that had none (Jesper's explicit
ask), plus the same gap in all 7 style rules from this PR (not explicitly
named this round, but the identical systemic issue) - 15 cues total across
al-data-modeling-review.md, al-testing-review.md, al-performance-review.md,
al-web-services-review.md, and al-style-review.md.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

microsoft/knowledge/web-services/api-page-flowfields-must-be-calcfields.bad.al

@@ -1,24 +0,0 @@
-page 50100 "Item Availability API"
-{
-    PageType = API;
-    APIPublisher = 'contoso';
-    APIGroup = 'inventory';
-    APIVersion = 'v1.0';
-    EntityName = 'itemAvailability';
-    EntitySetName = 'itemAvailabilities';
-    SourceTable = Item;
-
-    layout
-    {
-        area(content)
-        {
-            repeater(General)
-            {
-                field(itemNo; Rec."No.") { }
-                field(quantityOnHand; Rec.Inventory) { }
-                // No OnAfterGetRecord CalcFields — Inventory is a FlowField
-                // and returns 0 to every consumer.
-            }
-        }
-    }
-}

microsoft/knowledge/web-services/api-page-flowfields-must-be-calcfields.good.al

@@ -1,27 +0,0 @@
-page 50100 "Item Availability API"
-{
-    PageType = API;
-    APIPublisher = 'contoso';
-    APIGroup = 'inventory';
-    APIVersion = 'v1.0';
-    EntityName = 'itemAvailability';
-    EntitySetName = 'itemAvailabilities';
-    SourceTable = Item;
-
-    layout
-    {
-        area(content)
-        {
-            repeater(General)
-            {
-                field(itemNo; Rec."No.") { }
-                field(quantityOnHand; Rec.Inventory) { }
-            }
-        }
-    }
-
-    trigger OnAfterGetRecord()
-    begin
-        Rec.CalcFields(Inventory);
-    end;
-}

microsoft/knowledge/web-services/api-page-flowfields-must-be-calcfields.md

@@ -1,28 +0,0 @@
----
-bc-version: [all]
-domain: web-services
-keywords: [api-page, flowfield, calcfields, odata]
-technologies: [al]
-countries: [w1]
-application-area: [all]
----
-
-# Explicitly Calculate FlowFields on API Pages
-
-> Contributions welcome — open a PR to refine or extend this article.
-
-## Description
-
-FlowFields are not stored in the database — Business Central computes them on demand. Regular pages trigger that calculation automatically while rendering, but API pages do not. A FlowField referenced in an API page's layout returns an empty value to external consumers unless it is calculated explicitly, producing a silent data gap in OData responses that is easy to miss in review.
-
-## Best Practice
-
-Call `CalcFields` for every FlowField referenced in the page layout from the `OnAfterGetRecord` trigger, combining multiple fields into a single call.
-
-See sample: `api-page-flowfields-must-be-calcfields.good.al`.
-
-## Anti Pattern
-
-Relying on the implicit calculation that regular pages perform. Any FlowField left out of the `CalcFields` call returns a blank value to every API consumer with no visible error.
-
-See sample: `api-page-flowfields-must-be-calcfields.bad.al`.