Commit Graph

10 Commits

Author SHA1 Message Date
pulse-triage[bot] 90f5e9c687 Distinguish Recovery backups before configuration import
Explain the four existing backup scopes in the Recovery guide, link their established procedures, and keep configuration replacement separate from workload recovery and guest thaw. Add rendered guidance and link regression checks.

Contract-Neutral: Documentation and rendered scope checks only; existing export/import, polling, guest safety and recovery contracts are unchanged.
Change-source: pulse-maintainer
2026-10-07 12:01:50 +01:00
pulse-triage[bot] f77070690e Integrate reviewed full guest recovery safety guidance
Preserve the exact reviewed help candidate and the current PBS reconciliation link. Require independent thaw, writes to every covered filesystem, workload liveness and prior-active restoration without changing runtime or guest operations.

Change-source: pulse-maintainer
2026-10-06 23:56:46 +01:00
pulse-triage[bot] e032238241 Consolidate overlapping PBS guidance while preserving help entry points
The exact PI candidate overlaps the already integrated Web PBS guide. Keep that authoritative guide byte-identical, route Recovery and Troubleshooting to it, and focus the added tests on mirrors and rendered navigation rather than maintaining duplicate safety text.

Contract-Neutral: Existing backup help and renderer navigation tests only; no posture, API, permissions or collection contract changes.
Change-source: pulse-maintainer
2026-10-06 23:46:55 +01:00
pulse-triage[bot] 4b08b353b8 Keep recovery help on the full guest safety precaution
The Recovery guide allowed monitoring to restart after thaw alone. Require independent post-backup thaw, writes to every covered filesystem and workload liveness; preserve prior-active restoration and the in-flight request boundary. Keep the planned pause distinct from incident recovery and verify the rendered guide against its exact parent.

Contract-Neutral: Existing help and its regression checks only; recovery APIs, runtime, backup safety policy, frontend behaviour and dependency graph are unchanged.
Change-source: pulse-maintainer
2026-10-06 23:44:25 +01:00
pulse-triage[bot] 4273480242 Explain conflicting PBS backup health without unsafe diagnostics
Distinguish listed artifacts and verification from workload posture, link one-row passive checks from existing help, and preserve native identity, privacy and backup-safety boundaries. Add shipped-renderer and navigation regression checks.

Contract-Neutral: Existing backup help and tests only; no posture, API, permissions or collection contract changes.
Change-source: pulse-maintainer
2026-10-06 23:23:14 +01:00
pulse-triage[bot] 48dc32d1a3 Fix Recovery safe-reporting navigation
Resolve the shipped Recovery link to the actual Troubleshooting heading and bind it to rendered Markdown. Exercise keyboard and reload fragment navigation in desktop Chromium and phone WebKit.

Contract-Neutral: Correct an existing help link and add regression controls; no API or subsystem contract changes.
Change-source: pulse-maintainer
2026-10-03 23:24:02 +01:00
pulse-triage[bot] 2201fd59b4 Make recovery help distinguish backup evidence from safe restore
The existing guide points to a retired page and documents ignored time and subject filters. Explain current platform views, provider verification limits, independent thaw and isolated restore acceptance; mirror the guide and bind examples to the read-only handlers.

Contract-Neutral: Recovery runtime, APIs, trust policy, frontend behaviour and dependency graph are unchanged; this corrects existing help and its regression checks.
Change-source: pulse-maintainer
2026-10-03 21:21:04 +01:00
rcourtman 93dbdd91cf Build canonical protection posture 2026-07-19 15:10:38 +01:00
rcourtman 7d6b447c59 Simplify recovery presentation and type contracts 2026-05-14 21:08:54 +01:00
rcourtman 778a2577b6 feat: Pulse v6 release 2026-03-18 16:06:30 +00:00