Pass 2 of the routine-narrative job (per
en/scripts/narrate_routines.md). Every page under
en/docs/auto-catalog/{procedures,functions}/ now has a business-context
narrative replacing the auto-generated placeholder. 1,684 procedures +
177 functions + 3 setup samples = 1,864 narratives.
Each narrative follows the three-section shape:
- **Business context:** Chinese module path from gdsmodule.sChinese,
preserved verbatim, plus the user action that triggers the routine.
- **What it does:** terse mechanism naming actual tables/columns/procs.
- **Invocation:** concrete dispatch channel — gdsmodule hook,
gdsconfigformmaster sSqlStr, GenericProcedureCallController dispatch,
workflow proc via gdsmoduleflow.sApplyProName, Sp_Invalid_backwriting
or Sp_delete_backwriting indirect dispatch, JMS PRO_ERPMERGEBASE
family, Quartz scheduler via Sp_Task_*, external HTTP dashboard, or
"appears orphaned, no caller found in any channel".
Pass 3 QA: 70 random samples + 25 targeted re-verifications (orphan
claims, bug flags). Zero slop; one broken cross-link fixed.
Narratives surface real maintainer audit signal: shadowed-name DELETE
tautologies in three PRO_ERPMERGE family procs, broken Chinese-char
regex in Fun_GetCh / GetChineseChar, sealed-but-still-bound report
procs, ~501 confirmed orphans, multiple copy-paste COMMENT drift,
tenant-baked GUIDs in workflow data-builders, and several
under-deployed feature families (e.g. the Sp_Receivables_* HZ
variants, the entire Sp_beforeSaveReturn_* shadow family).
