# Filter-bar fix release deployed, 2026-09-10

Release `20260910-022948-5a52b33` was activated by the governed module after the owner ran the
launcher. Application commit `5a52b332686398e377d67647e2a928a8b3694bb8` (deployment tooling the same
commit; candidate fingerprint `58978f83…` unchanged, 237 files). It carries, after `4086e43`: the
three decision papers, the credential alerting sweep (`7f77835`, inert until an `Alerts` section
exists in the web host's secrets file), the previous deployment record, and the filter-bar fix on
all ten Argus pages that cached their view (`5a52b33`, reported by the owner that day for
`/argus/items` and "most screens").

Preparation: `local\deploy\Prepare-Deploy.ps1`; WhatIf 02:31 UTC, Planned, 161 entries, production
untouched. Execute ran from 03:30:22 to 03:31:09 UTC: `Ok: true`, `Outcome: Executed`, nothing
thrown, 12/12 checks, transaction `ebfffadb-aaac-4b66-8a83-927fe2a673f0`, IIS backup
`SibylaE2-20260910-033021`. Evidence: `local\artifacts\filter-fix-release-260910\`.

Independent verification at 03:31 UTC, outside the runner:

- all three `CURRENT.txt` pointers name the release; `PREVIOUS.txt` names `20260910-012403-4086e43`;
- the worker service is Running from the release tree, process started 03:30:44 UTC; its first
  report after restart (03:30:46) reads signed in, source `token`;
- web `/`, API `/health`, API `/health/ready` and docs `/naming-glossary.md` answer 200; the three
  IIS sites and pools are Started on the release paths;
- the deployed `Sibyla.Web.dll`, `Sibyla.Platform.Infrastructure.dll`, `Sibyla.Platform.Domain.dll`
  and `Sibyla.Api.dll` are byte-identical to the staged publish (SHA-256) and differ from the
  previous release; the staged manifest names commit `5a52b33`, not dirty; the binaries carry the
  alerting strings introduced by `7f77835`;
- no `AiCredentialAlert` audit row exists on Main: the sweep has nothing to send while the worker
  reports healthy, and no channel is configured.

A note on method: a first string probe of the web binary reported the alerting label absent. The
probe decoded the file as UTF-16 from offset zero only, and a .NET user-string can sit at an odd
byte offset; decoding at both alignments finds every probed string. The hash comparison is the
evidence that matters; the probe is recorded so the next reader does not repeat the false alarm.

Rollback target on every host: `20260910-012403-4086e43`. C6 is unchanged.