v1.2.1 — reporting_get_data forwards unit/page

Patch. Completes the 2026-08-21 field report. Additive parameters only — no action surface change, no change to existing call behaviour.

Fixed — unit and page are forwarded

Both were discarded before the call, so a caller paging backwards received correctly-shaped data for the last hour with nothing to indicate the parameters had been ignored. The query schema accepts both, and its additionalProperties is false, so middleware would have rejected them loudly — silently dropping them was the only reason it went unnoticed.

⚠️ page is not an index. unit: "HOUR", page: 3 returns the last three hours, not the third hour back. unit and start/end are mutually exclusive (the API rejects the combination) and page requires unit; both are now rejected client-side with a clear message.

Documented — two gaps closed without new actions

Enumerating middleware (781 methods on 26.0.0-BETA.1) settled both:

• Kernel log is unreachable — no method exposes the ring buffer, and containers can't substitute without CAP_SYSLOG. TROUBLESHOOTING.md now records the substitute that works: cgroup memory.events plus State.OOMKilled, which is what separates a host-wide OOM from a cgroup-limit kill.
• No memory/swap/ARC action will be added — memory and ARC compose from a single reporting_get_data call, cheap now that detail defaults to "summary". Swap has no middleware source at all.

272 tests pass. Action count (270) and safety tiers unchanged.