Cloud telemetry: emit normalized productivity baseline windows

[jeffhuber]

Problem

The cloud contract accepts productivity_summary events, including active, wait, review, green, and merge time, but normal dogfood/repo-sync workflows do not yet produce a consistent baseline suitable for before/after Code Mower comparisons. PR counts alone cannot establish productivity improvement.

Outcome

Add a deterministic metadata-only producer for normalized repository/release productivity windows.

Scope

• Emit repository or release productivity_summary windows from GitHub lifecycle metadata plus local controller/audit timing when available.
• Separate elapsed time, observed active agent time, queue/wait time, review time, time to green, and owner wait.
• Include PR counts, fix rounds, interventions, reverts, and post-merge defect linkage only when explicitly observed.
• Record measurement coverage and provenance so incomplete active-time data cannot be presented as complete.
• Support a pre-Code-Mower or operator-selected comparison window without claiming causality.
• Update docs, validation, fixtures, and tests.

Acceptance criteria

• Repeated syncs emit stable, idempotent windows.
• Missing active-time and defect linkage remain unavailable, not zero.
• Output contains no source, diffs, transcripts, issue bodies, raw output, file paths, auth output, or secrets.
• CodeMower.com's paired issue is linked before merge.

Process

One focused PR, tests and docs, independent final-head audits, required green gate, and metadata-only dogfood upload.

[jeffhuber]

Paired CodeMower.com consumer issue: https://github.com/jeffhuber/codemower.com/issues/243

The OSS producer must land first. Comparisons must carry explicit measurement coverage and must not claim causality from a before/after correlation.