docs: WW-PGD telemetry field guide (scheduled vs applied)

[quint-mbbdigital]

Type

• A no-def
• B docs-only
• C embeds a definition choice

Summary

Add docs/WWPGD_TELEMETRY_FIELDS.md explaining how to read projection CSV event/dose/pin-related fields: scheduled ≠ applied, dose vs event index, dual-label pointer, and conflict log pointing at #131/#132 predicates (without re-implementing #129/#130 designs). Link from README.

Why

Telemetry misreads recreate science confounds (clock vs dose, requested vs verified pin).

Definition surface

Docs only. Marks #131/#132 field sets as intended SoT when not yet on main.

Prior / conflict

• feat: dual-label density alpha and rank q on projection CSV rows #128 dual-label logging (merged)
• feat: name first-apply dose fields on WW-PGD projection rows #129 first-event approach — prefer fix: add exact resume-safe WWPGD projection dose telemetry #131 predicates
• feat: optional WWPGD_COMMIT_PIN for floating ww_pgd installs #130 single-runner pin — prefer fix: verify WWPGD commit pins at every shared adapter boundary #132 predicates

Test plan

• docs only
• no scientific efficacy claim

Out of scope

Adapter code changes; efficacy claims; monorepo α_zc.