feat: add bounded Patient Zero pressure context

[christopherjnelson]

Summary

• add a six-tick engine-authored pressure rollup to each displayed current Patient Zero cleaner event
• report subject totals, disinfections, blocked cleans, consecutive affected ticks, and current-member alliance totals
• derive prior counts from dedicated committed cleaner history plus only the current uncommitted candidate interval
• keep the event feed current-interval-only and exclude movement, live position, route, target, identity, and historical membership inference
• guide Patient Zero to distinguish isolated from sustained pressure and suppress only equivalent recent Zero advice
• expose bounded counts in Behavior Trace and retain them in full-safe SQLite observation JSON
• document the contract in ADR 0024

Validation

Repository owner confirmed the following local validation is green:

• pnpm format
• pnpm validate
• pnpm test:e2e

Scope

No cleaner mechanic, coordinator type, model-call count, decision contract, or normalized SQLite schema changes. Legacy D1.1 observations may omit the additive context; live D1.2 observations populate it for every nonempty feed event.