[Jammy2211]

Why

Profiling updates and pending work are spread between project ledgers and Mind. Pulse needs to be the single place to start or resume a profiling conversation.

Changes

• An editable, copyable all-campaign check-in prompt at the top; accept campaign direction before or after copying.
• Eleven campaign rows, followed by open tasks and the existing measurement evidence.
• Twenty-six migrated task records, with original text, pinned Mind source and checksums. Twenty-five remain open; one superseded umbrella is retained in history.
• A validated campaign ledger, one-chat operating guide, and stale-ledger detection on dashboard checks. Board refreshes do not stamp a check-in or modify task status.

Scripts Changed

pulse/campaigns.py, board/CLI integration and campaign regression tests. Detailed timing producers and scientific qualification are unchanged.

Validation

86 tests pass; Ruff and format checks pass; offline registry/snapshot/feed checks pass. All 26 original task bodies match their pinned source hashes. Native clipboard, fallback and denied-copy handlers exercised in Node with edited text. A full browser screenshot was unavailable because Chromium is not installed.

Heart published at 2026-10-03T10:12:06Z: scoped GREEN for PyAutoPulse/PyAutoMind (no in-scope blockers); organism-wide RED.

Merge order

Merge this before the companion Mind migration, so originals are not removed before their destination exists. No compute jobs or releases were started. Human /prm merge mode.

Closes #6