# Release notes 0.1.162

> 27 October 2026: Fixes from the live read-back of 0.1.161, where real rows were longer than the sample data: the findings list, the runbook catalog and the change actors table fit their card again…

_Release notes · Updated 2026-10-28 · Describes release 0.1.164_

## 0.1.162 — 27 October 2026 {#0-1-162-27-october-2026}

Fixes from the live read-back of 0.1.161, where real rows were longer than the sample data: the findings list, the runbook catalog and the change actors table fit their card again, a blocked route's operations break only after a dot again, a change request stored before 0.1.161 reads its blast radius in the current words, an RCA's blast radius section uses the change page's words, and the dark theme draws native controls dark. No schema change, no new setting, route, permission, audit action or chart value. Nothing to do for the upgrade (see the [upgrade row](/help/ops-upgrade-and-verify.md)).

- **The findings list fits its card from 1280 px.** On a live workspace the findings list under **Security posture** ran to about 1,500 px in a 1,006 px card from 1280 to 1920 px: an image finding names its resource by its sha256 digest, the resource sample under a finding's title held the **Finding** column 448 px wide, and *AWS Backup (platform read)* and a six-digit CVE id never wrapped. The resource sample now takes the width the title sets and is cut there, with the whole name on hover; a source wraps at its spaces, a rule id such as a CVE id after its hyphens, and a **Fixed — awaiting CSPM** chip at its spaces. From 1280 px the **Finding** column keeps at least 8rem for its title (about 170 px at 1280 px, 214 px from 1440 px).
- **The runbook catalog fits its card at 1024 and 1280 px.** A resource-type key (`aws.s3.account_public_access_block`) stayed on one line in its badge and an AWS document name (`ASR-DisableUnrestrictedAccessToHighRiskPorts`) on one line under the runbook's name: the catalog ran to 984 px in a 716 px card at 1024 px. A resource type now breaks after a dot or an underscore and a platform step after a dot or a hyphen; the *Published by AWS · … · Automated Security Response on AWS v4.1.0* line breaks between the words of the document's name (`ASR-`, `Disable`, `Unrestricted` …). None of them breaks inside a word.
- **The change actors table fits its card at 1024 px.** A captured actor is often a node role's session name (`eks-auto-mode-compute-…`), one long token: **Who changed what** on **Changes** ran 825 px in a 718 px card at 1024 px and cut its last column, and a cut name had no tooltip. A long actor is now cut to the column's width with the whole name on hover, and the column grows with the window.
- **A blocked route's operations break only after a dot.** 0.1.161 let a long identifier in a list table break anywhere, and that reached the **Automation** column on **Problems**: from 1280 px its operations split mid-name (`aws.lambda.publis|h_version`), undoing the 0.1.160 fix. The **Automation** list and the runbook catalog's *Platform steps* break each operation only after a dot again.
- **A change request stored before 0.1.161 reads in the current words.** On a live workspace 7 of 43 planned changes held a blast radius stored before 0.1.161. Their card read *Estimate: computed from the target's direct neighbours …; target not found in the harvested estate* (the generic note and the specific reason together), a folded *1967 entities and 0 relations flagged inconsistent or stale left out of reasoning*, and the change management agent's bare *No impact* beside *Estimated impact*. The card under **Affected resources & blast radius** and the change request document's **2.4 Impact** and **2.5 Risk** now print the specific reason alone (*Estimate: target not found in the harvested estate*). The folded gap's relations read in the per-kind line and its entities as *Coverage gap recorded before 0.1.161, not split by kind: N resources in the estate map stale or inconsistent between sources, left out of reasoning* (the old report counted stale and inconsistent together, so they cannot be split). A bare *No impact* from a draft that did not read the report shown reads as the agent's note, never as a second verdict: *The change management agent's note: No impact (drafted over an earlier report)*, or *(drafted before this estimate's basis was shown)* for a draft that read no report — one made before 0.1.161, or while no impact had been computed yet.
- **An RCA's blast radius in the change page's words.** The RCA of an incident whose fix ran headed its blast radius section *Blast radius (certified)* whatever the basis and printed the stored reason as written, so a report stored before 0.1.161 read *Estimated from the target's neighbourhood; no exact delta for this operation.; target not found in the harvested estate*. The section is now headed by the change page's basis label (*Blast radius — Estimated impact*, *— Runtime impact*, *— Computed (certificate not checked)*, *— Certified blast radius*) and carries the same one basis sentence. An RCA written before the upgrade keeps its text.
- **Native controls draw dark in the dark theme.** In the dark theme the **Estate map**'s three checkboxes (**Show every object**, **Business layer only**, **Changes since the last scan**) were bright white squares: the page never told the browser it was dark. A checkbox, radio button, select list or scrollbar now draws dark on every page of both consoles; a ticked box keeps the accent colour.
- **The release check reads how a table fits.** The check that opens every page at 1024 to 1920 px failed a table wider than its card but not a dotted identifier split inside one of its parts, so the Problems regression above passed it. It now fails an operation, resource type or rule id laid out with one of its parts on two lines, and its sample data carries the live shapes that broke 0.1.161.


## Next steps

- Next: [Release notes 0.1.161](/help/release-notes-0-1-161.md)
- [All What's new pages](/help/what-s-new/llms.txt)
- [Documentation home](/help/)