[Jammy2211]

Summary

Add Pulse campaign activity to the Scientist Live Feed and route registered profiling development repositories to Pulse. A per-repository request allowance prevents one busy repository consuming the entire collection cycle; normalized partial history still resumes across cycles.

Scripts Changed

• scripts/activity_feed.py: explicit body-map-based routes, fair API allowances, Pulse adapter integration and separate coverage receipts.
• scripts/pulse_activity.py: read one pinned public Pulse revision; group campaign/task changes, deduplicate unchanged check-ins, and admit dated measurements only with explicit campaign/run association. Large snapshots use their exact Git blob.
• config/activity_sources.json: Pulse source identity and profiling board routes.
• scripts/live_feed.js: clarify complete-source coverage label.
• Tests and REPORTING.md document provenance, grouping and missing evidence.

Validation

• Full Python suite: 171 passed before two final regression tests were added; final collector/adapter suite: 25 passed, including large snapshot and expired-history regressions.
• Existing JavaScript tests: 7 passed. Six responsive light/dark browser cases and no-JavaScript snapshot passed using Pulse campaign fixtures.
• Read-only live adapter: all 12 campaigns from Pulse commit e47c0f727a53c9aa40af6e68b647071cca062256, seven API requests including public checks.
• Integrated CLI pilot: 26 Pulse-labelled rows, including all 12 campaigns; source gaps correctly retained.
• Diff and JavaScript syntax checks passed.
• Heart STALE solely release validation incomplete: no rehearsal for current source; no red/yellow readiness reasons, development shipping permitted.

Limits and deployment

The workflow is active; at inspection its last run was the initial manual publication, not a new scheduled delivery. This PR improves per-cycle fairness but does not promise GitHub schedule delivery. Existing source-check times expose freshness.
The live snapshot has 100 undated measurement records and 12 dated records without explicit campaign/run associations. These remain visible coverage gaps, never invented events. Pulse can supply explicit run associations in its own ledger; no owner data was edited here. No profiling, inference or scientific acceptance occurred. MyScientist remains outside this rollout.

Tier: judge — human /prm. After merge publish Scientist and verify campaign rows/coverage. Closes #85.