deps: Update dependency anolishq/anolis to v0.1.35

[renovate]

This PR contains the following updates:

Package	Update	Change
anolishq/anolis	patch	0.1.31 → 0.1.35

---

Release Notes

anolishq/anolis (anolishq/anolis)

v0.1.35

Compare Source

Added

• Mode-transition hook executions are now logged on success (#​188), one INFO
  line per call (Before/After-transition hook (AUTO -> MANUAL): bread0/dcmt0 set_open_loop OK). The safe-state hooks that zero actuators
  on AUTO exit were running silently — failures logged, successes left no
  evidence, which is both an operator-confidence problem during supervised
  actuation sessions and how the hooks were mistaken for missing in the
  first place.

Fixed

• install.sh no longer overwrites .prev on a same-version re-run (#​184).
  The backup phase previously snapshotted the running binaries on every
  install, so an idempotent re-run after an upgrade silently replaced the
  real rollback point with a copy of the current binaries — --rollback
  then "succeeded" as a no-op. The backup is now skipped when the incoming
  bin/ payload is byte-identical to what is installed.

v0.1.34

Compare Source

Added

• /v0/providers/health now carries the provider's own health report (#​185).
  The runtime fetches ADPP GetHealth from each available provider on demand
  and merges it into the response: a per-provider reported block (state,
  message, metrics) plus degraded and failed_device_count; per-device
  reported blocks (state, message, metrics, last_seen_epoch_ms) alongside
  the runtime's own freshness view; and devices the provider reports but the
  registry does not carry — e.g. expected devices that failed their startup
  probe — appended with registered: false. Previously a provider could sit
  at AVAILABLE with a silently missing configured device, and
  provider-reported metrics (such as bread 0.3.3's io_* counters and real
  last_seen) were invisible over HTTP.

v0.1.33

Compare Source

Fixed

• install.sh no longer fails with Text file busy when installing over a
  running service (#​181). Re-install, upgrade, and --rollback all wrote the
  new binaries onto the executing ELFs in place; binaries are now staged to a
  temp name and renamed over the destination, so the running process keeps its
  old inode until the restart both flows already perform. Found on the #​138
  bench — every prior hardware install had followed an --uninstall, so the
  in-place path had never run against a live service.
• install.sh repairs /etc/hosts even when the device already carries its
  anolis-<serial> hostname (#​180). The early-return in phase_hostname
  skipped the hosts fix from #​173 on exactly the devices that needed it,
  leaving sudo: unable to resolve host warnings on re-installs.

v0.1.32

Compare Source

Security

• install.sh now provisions the runtime with authentication enabled whenever it
  exposes the HTTP API on a non-loopback address. The bundle renderer emits
  http.auth_enabled: true alongside the 0.0.0.0 bind, and a new install phase
  generates a per-device 256-bit API token into /etc/anolis/runtime.env
  (0600 root:root), injected into the service via systemd EnvironmentFile=.
  The secret never enters runtime.yaml and is never baked into a bundle, which
  is a redistributable artifact. The token is reused across upgrades, so an
  upgrade does not invalidate tokens already issued to clients. Requests from the
  device itself remain exempt (auth_exempt_loopback), so on-device access and
  the health probe are unaffected. (#​172)

Fixed

• install.sh rewrote the runtime's bind to 0.0.0.0 without enabling
  authentication, producing a config the runtime is guaranteed to reject at
  startup ("non-loopback but authentication is disabled"). The online --project
  path therefore installed a runtime that could never start; it crash-looped while
  the installer reported success. Found on real hardware during the #​138
  acceptance run. (#​172)
• install.sh now preflights the runtime config against the constraint the
  runtime enforces at startup and refuses to install one that cannot start,
  instead of shipping a boot loop. This also covers operator-edited configs
  preserved across upgrades. (#​172)
• install.sh no longer prints "installation complete" and exits 0 when the
  runtime failed to come up. A failed health check is now a failed install, so
  curl … | sudo bash and workbench's deploy.py see a non-zero exit. The
  I2C-just-enabled/reboot-pending case is still reported as advisory, not a
  failure. (#​172)
• install.sh set the device hostname without updating /etc/hosts, leaving the
  machine unable to resolve its own name (sudo: unable to resolve host anolis-<serial>) and undermining the http://anolis-<serial>.local:8080 access
  URL it prints. (#​172)

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.