docs(readme): the shield row names six tools and the Stack table names ten - #537
Merged
Merged
Conversation
…s ten A checkup of the badges found every one of them rendering and both workflow badges reading passing; what was stale was coverage. The Stack table below the row lists Alloy, Alertmanager, snmp_exporter, Proxmox VE and Docker Compose, and none of them had a shield; the Digest drift workflow — the one scheduled check that runs off-host — had no badge at all. Each of them has one now, and pfSense's badge carries the logo Simple Icons has for it. Alertmanager and snmp_exporter borrow the Prometheus mark, which is the project they belong to; Alloy borrows Grafana's for the same reason. Nothing about the counts changed: the README still says 43 ADRs and 7 dashboards, and the tree still agrees. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
smaug has run TrueNAS since 2026-09-16 and the media stack since 2026-09-19, alexander has run the lab stack since 2026-09-07, and the table that says what the estate runs on named none of them. Three rows: TrueNAS 25.10 with the erebor mirror and the share; Jellyfin as the one stack deployed from TrueNAS's Docker rather than by make deploy; and the lab's own Prometheus, Loki and Grafana on a guest, with ADR-0028's rule that liveness crosses and telemetry does not. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this is
A checkup of the README badges, asked for after the 2026-09-19 issues pass. Every badge rendered, both workflow badges read passing, and the counted claims the README carries (43 ADRs, 7 dashboards) still match the tree. What was stale was coverage: the shield row named six tools and the Stack table beneath it named ten, and the table itself had no row for the NAS, the media stack or the lab stack.
Shields
digests.ymlworkflow, the one scheduled check that runs off-host, had no badge. It reads passing today.Every shield and every link target was fetched and returned 200 before this was committed.
Stack table
Three rows, in the second commit: Storage — TrueNAS 25.10 on
smaug, theerebormirror, the share, and the Docker the media stack runs under; Media — Jellyfin, the one stack deployed from TrueNAS rather than bymake deploy; Lab observability — the lab's own Prometheus, Loki and Grafana onalexander, a guest onSaruman, with ADR-0028's rule that liveness crosses to the estate's stack and telemetry does not.smaughas run TrueNAS since 2026-09-16 and the media stack since 2026-09-19 (#522);alexanderhas run the lab stack since 2026-09-07 (#264). The table named none of them.Not touched
The authored-but-undeployed stacks,
sensitiveandsoc, still have no rows. The table describes what runs, and neither does yet; they get their rows whentrinityandodinexist.🤖 Generated with Claude Code