✅ Release Asset Validation: PASSED

All release assets have been validated successfully!

Status: Ready for publication ✅
Validated: 2026-08-18 13:09:21 UTC
Workflow: Pulse Release Pipeline #352

Validation Summary

• All required assets present ✓
• Checksums verified ✓
• Version strings correct ✓
• Binary architectures validated ✓

Pulse v6.3.0-rc.2 Release Notes

v6.3.0-rc.2 is a release candidate for the next Pulse v6 minor release and
the first published candidate in the 6.3 line. An earlier rc.1 publication
did not complete, so this cut uses a fresh immutable version for the advanced
main branch. It follows stable
v6.2.1 and introduces the Patrol v2 operating model, a first-class Actions
workspace, guarded agent action preflight, large-estate response improvements,
and monitoring correctness fixes.

Highlights

• Patrol guides operators through one ranked decision at a time; Actions now
  has its own primary review workspace.
• Read-only observers extend Patrol coverage between full model investigations
  without granting mutation authority.
• Approved actions gain agent preflight and stable refusal telemetry; large
  installations gain compressed APIs and indexed lookups.

Added

• Durable Patrol objectives with pause, archive, resource-scope, coverage, and
  observer-health state.
• Model-authored observer proposals that are validated, installed as bounded
  read-only checks, and kept separate from action authority.
• Verified Patrol work receipts and clearer navigation between findings,
  objectives, attention items, and governed actions.
• A persistent decision workspace with explicit decision origin, review
  progress, next-item navigation, and automatic advancement after a decision.
• A canonical platform-admission facet projected on unified resources so
  supported onboarding and runtime modes stay consistent across the product.
• Unified Agent preflight contracts for package updates, package-cache cleanup,
  and Docker lifecycle or update operations.
• Production security deployment guidance and a focused security-review packet.

Improved

• Patrol now works from durable outcomes, scoped investigations, and verified
  work receipts instead of treating the chat stream as operational state.
• Patrol investigations preserve objective and resource intent across retries,
  provider interruptions, chat restarts, truncated responses, and retained
  objective runs.
• Finding identity, evidence, causal conclusions, and remediation proposals are
  canonicalized and validated before Patrol writes or acts on them.
• Autonomous execution remains bounded by advertised capabilities, explicit
  policy, agent preflight, current target state, and post-action verification.
• Patrol separates its Inbox, Protection, and Activity modes, removes duplicate
  counters and generic state, and keeps Assistant focused on explaining the
  selected item rather than acting as the operations front door.
• Authenticated startup no longer pulls the full legacy state payload. Unified
  resource pages load concurrently after the first page and no longer wait for
  WebSocket hydration before beginning the canonical fetch.
• Actions and Patrol identify whether a decision originated from a finding,
  alert, objective, or explicit operator request, making review context clearer.
• Action refusal telemetry now classifies target changes, prerequisites,
  contract failures, capability limits, policy decisions, and stale plans
  instead of collapsing the new agent reason codes into the catch-all bucket.
• API gzip handling preserves informational and bodyless responses, while
  polling, metric lookup, registry resolution, and source-target mapping avoid
  repeated large-estate scans.
• OpenRouter, Ollama, and subscription-backed Patrol routes handle reasoning
  limits, readiness checks, deadlines, and continuation latency more reliably.
• Subscription-backed turns now complete their idle timeout promptly even when
  a canceled CLI descendant still holds an inherited output pipe open.

Fixed

• Patrol no longer accepts empty, blocked, contradicted, incoherent, unscoped,
  or unsupported findings and proposals as successful investigation output.
• Enabling full AI mode or restarting the chat provider now preserves and
  rewires Patrol controls and investigation dependencies.
• Platform-admission state stays current across tenant changes, reconnects,
  shell navigation, and canonical resource aggregation.
• Agent Doctor names the judged credential in verdict evidence, and agents
  warn when the server overrides a presented agent identity.
• Alert threshold overrides resolve through canonical registry identity, and
  the monitoring-policy menu no longer clips inside alert cards.
• Docker health-check dependencies and app-container scope now remain attached
  to the correct canonical findings.
• Stale ZFS alerts clear when storage loses its pool attachment, and node-local
  ZFS pools are no longer attached to shared storage records.
• vSphere backup status, agent thermal history, explicit cluster-member address
  overrides, and discovery-analysis request timeouts now reflect their actual
  runtime state.

Security

• Patrol observers are read-only and proposal-only. Mutating operations still
  require the normal action-policy, approval, capability, preflight, and
  verification path.
• Agent preflight responses expose bounded machine reason codes rather than
  command output, paths, package names, or provider-specific error text.
• Investigation tooling is projected from the selected resource scope and
  rejects tools that were not advertised for that run.

Upgrade Notes

Use the normal v6 install or update flow for v6.3.0-rc.2 only when you are
comfortable testing a release candidate. The rollback target is v6.2.1.

The exact rollback reinstall command is:

./scripts/install.sh --version v6.2.1

The changes since v6.3.0-rc.1 do not require a Pulse Mobile client change
and preserve the existing mobile, Relay, onboarding, and mobile-facing API
contracts. No companion mobile build upload or public mobile-store rollout is
part of this candidate.

Windows Unified Agent binaries in this prerelease retain exact-SHA, checksum,
and detached-signature verification but are not Authenticode-signed, so Windows
may display an Unknown Publisher warning. Stable v6.3.0 still requires the
normal SignPath Authenticode lane unless a separate version-bound owner decision
is recorded.

Paid Pulse Pro, Relay, and eligible legacy customers should continue to use the
private download page and private runtime image for paid runtime features.

Installation

Docker (recommended):

docker pull rcourtman/pulse:6.3.0-rc.2

Docker Compose:
Update your docker-compose.yml to use rcourtman/pulse:6.3.0-rc.2

See the Installation Guide for complete setup instructions.

Review the Code signing policy for release provenance, approval roles, and signing scope.

Paid Pulse Pro, Relay, and eligible legacy customers: public GitHub release assets and the public rcourtman/pulse Docker image are community builds. They do not include the private Pulse Pro runtime hooks. Use https://pulserelay.pro/download.html with your activation key to get the private Pulse Pro Docker image or Linux/LXC archive.

Promotion Metadata

• Promotion channel: rc
• Candidate stable tag: v6.3.0-rc.2
• Promoted prerelease tag: n/a
• Rollback target: v6.2.1
• Rollback command: ./scripts/install.sh --version v6.2.1
• Hotfix exception: false
• Windows Authenticode required: false
• Unsigned Windows exception: false