NetRatel v0.1.1

NetRatel 0.1.1

NetRatel 0.1.1 is a stable release with a focused update to the operator
experience and current documentation.

Operator experience

• Integration credentials: a structured details dialog groups connection
  metadata, lifecycle dates, tenant and server permissions, current admission,
  and policy details. Status chips, expandable sections and responsive scrolling
  make the information easier to inspect. Existing permission and credential
  checks remain in place.
• Flow history: History opens a dialog immediately, with loading and error
  states, published versions, recent runs and selected-run results. Closing it
  preserves the flow list and returns keyboard focus to the invoking control.
• Client management: update attempt details expand below their summary in a
  full-width MudBlazor panel. Version observations, server confirmation and
  automation metadata have space to wrap without stretching the table columns.
• Monitoring: Active alerts initially selects Firing, including tenant
  links. Pending, Unknown, Suppressed and All states remain explicit choices,
  and deliberately supplied state filters are respected.

Documentation

The README links to the current releases without a pinned RC or beta. Obsolete
test-campaign runbooks and their dated requirements have been removed from
maintained guides. Product setup, operations, authentication and release
verification instructions remain available through the
documentation index.

Installation and upgrade

Download the matching Compose or native-client archives, SHA256SUMS and
publication.json from the GitHub release.
Use the image digests included in the completed Compose bundle and retain the
existing configuration and persistent state. Follow
release installation and the
self-hosting guide.

This update introduces no database migrations or MCP/API contract changes.
The existing generic workflows validate the source, build the downloadable
artifacts, and publish the five container images with their checksums and
publication record. Release distribution and deployment acceptance are recorded
separately; publishing does not change an installation's rollout controls.