A status block that had grown into a wall, and one claim in it that was false

A status block that had grown into a wall, and one claim in it that was false The README's status blockquote had reached five paragraphs and twenty lines, so a reader met it before anything about the product. Worse, it had gone stale in the way prose about your own code does: it said the signed claim "carries the asset, transform, channel, territory, identity, share link and expiry, but not the tenant" — and G22a put the tenant in the claim days ago. The sentence describing the limitation was describing the version before the fix. What is actually still true is narrower and now says so: the claim carries the tenant and delivery checks it, but the library is resolved from configuration rather than from the claim, so one `damd` answers delivery for one tenant. Same practical limitation, accurately stated. Trimmed to a status sentence and two bullets. The AWS conformance result moved out of it entirely — twenty passed, none skipped, a 77-second restore is a *strength*, and it had been filed under caveats where nobody reads it. It sits in Verification beside the command that reproduces it, along with why "none skipped" is asserted at all. Also: a CI badge and a licence badge, because the Actions tab is the first thing a visitor to a public repository reads and a README that does not link it is asking them to go looking. A link to `docs/blog/`, which existed and had nothing pointing at it. And the one-line Licence section says something now — every crate is `publish = false`, so nothing reaches crates.io by accident and the version numbers mean nothing to a registry. Dependabot, grouped and monthly rather than weekly and per-package. Several hundred transitive dependencies across cargo, pnpm and the actions would otherwise produce more pull requests than anyone reads — and a queue nobody reads is indistinguishable from no queue, which is the same failure this repository already found in a nightly job that reported success while running nothing. Advisories arrive immediately regardless, and `cargo deny check advisories` runs on every push so one is a red build rather than a notification.