v1.3.35.1 -- Screenshots README sync¶
A doc-only patch on top of v1.3.35. Rewrites docs/screenshots/README.md so it matches the post-v1.3.34 + v1.3.35 reality: the demo environment is the canonical capture environment, the inventory reflects what's actually on disk + what's pending, and the v1.3.34 deferred-screenshot list (10 new + 3 retakes) is now in the file with concrete capture instructions.
Zero panel binary change; argosVersion and frontend/package.json deliberately stay at 1.3.35. Reuses the v1.3.27.1 / v1.3.34 precedent: tag-without-rebuild for doc-only changes.
Why¶
The previous README was multiple releases stale. Three specific drifts:
- Preamble lied about placeholders. The file claimed "every filename below is a copy of
placeholder.png" but 23 of the 23 listed PNGs were already real captures (23 KiB-588 KiB each), accumulated across v1.0 through v1.3.0- beta. Onlyplaceholder.pngitself was the 68-byte 1×1. - No entries for the v1.3.34 deferred captures. The v1.3.34 release notes deferred 10 new captures + 3 retakes to a post-tag operator session. None of the 13 had README entries, so the operator had no per-capture guidance.
- Stale UI references.
threats-decisions.pngwas captured against/threats, retired in v1.3.24.host-form.pngpredated the v1.3.29 modal layout.appsec-status.pngpredated the v1.3.25 tuning UI. None of these were flagged.
Plus a structural gap: there was no link to the v1.3.35 demo environment as the capture surface, even though that was the release the demo scaffold shipped under.
What ships¶
docs/screenshots/README.md rewrite¶
New structure:
- Capture environment — points at
scripts/demo/init.sh localhost:9181+ logindemo / demo1234. Documents the browser settings (1440 px, dark, 100%, PNG) + navbar caveats (status pills + drawer-closed unless the drawer is the message).- Naming convention —
<area>-<surface>.png, lowercase, hyphenated, single-tier; concrete examples. - Status legend —
[x]up-to-date,[~]UI shifted (RETAKE),[ ]pending. Replaces the previous "everything is a placeholder" framing. - Inventory tables organised by panel area: Landing, Hosts, Security, AppSec + drift, Country bans, Self-block, Threats (legacy), Notifications, System + settings. Every entry carries a Path + Embedded-in + Status + Notes column.
- Capture session workflow — exact 7-step sequence:
init.sh→ log in → capture →mkdocs build --strict→check-no-personal-data.sh→ commit →teardown.sh --purge. - Maintenance rules for when a new feature ships, when a surface gets redesigned, and the periodic-refresh cadence.
Inventory deltas (vs the old README)¶
Marked RETAKE ([~]):
dashboard-overview.png— pre-v1.3.20; retake to surface the v1.3.35 header pill.host-form.png— modal layout shifted post-v1.3.29.appsec-status.png— pre-v1.3.25 tuning UI shape.threats-decisions.png— captured against the/threatsURL retired in v1.3.24.
Added ([ ], files don't exist yet):
| Path | Surface | Release |
|---|---|---|
security-banned.png | Banned IPs tab | v1.3.20 |
security-whitelist.png | Whitelist tab | v1.3.20 |
security-activity.png | Activity audit log | v1.3.20 |
security-scenarios.png | Scenarios w/ description tooltip | v1.3.30 |
host-form-true-detect.png | Edit modal AppSec section | v1.3.29 |
hosts-detect-badge.png | Hosts list DETECT badge | v1.3.29 |
drift-indicators.png | Drift banner + per-tab dot | v1.3.27 |
country-bans-progress.png | Async expansion progress bar | v1.3.31 |
selfblock-banner.png | Self-block detection banner | v1.3.20 |
That's 9 new entries. The 10th deferred capture from the v1.3.34 list (the original "10 new" target) was an already-pending entry; the count overlap is documented in the v1.3.34 release notes.
For each new [ ] entry, the README points at the doc page that needs the embed when the capture lands. Embedding is a separate doc-only commit per the workflow section so the captures and the docs that reference them ship together.
mkdocs.yml nav¶
Adds the v1.3.35.1 release notes entry.
Sanitization¶
scripts/check-no-personal-data.sh clean on the new README (every example IP is RFC 5737 / every domain is example.*).
mkdocs build --strict¶
Clean. The "exists but not in nav" INFO lines for the three planning/ files are intentional and unchanged from prior releases.
Files changed¶
docs/screenshots/README.md(rewritten)docs/release-notes/v1.3.35.1.md(this file)CHANGELOG.md,mkdocs.yml
NOT changed: backend/cmd/argos/main.go argosVersion stays at 1.3.35; frontend/package.json version stays at 1.3.35; no Go code; no frontend code; no migrations; no smokes; no panel rebuild required.
Upgrade¶
Doc-only release. Operator action:
cd ~/argos-edge
git pull
# No make sync-prod required; no panel rebuild required.
# Optional: rebuild the docs portal locally to preview:
mkdocs serve
Operators are then ready to start the v1.3.35 demo capture session against the new README:
The docs portal at cmos486.github.io/argos-edge rebuilds automatically via the existing docs.yml workflow on the push to main; the release.yml workflow auto-publishes the v1.3.35.1 GitHub release object using this file as the body.
What this enables¶
After v1.3.35.1 + the operator's capture session, the v1.3.34 deferred-screenshot gap closes. The 9 new captures land in docs/screenshots/ along with their ![...] embeds in the relevant feature pages (features/crowdsec.md, features/drift-detection.md, features/country-bans.md, features/security-overview.md). The 4 [~] retakes refresh in place; the legacy threats-decisions.png stays for now and may be deleted in a follow-up commit once security-banned.png is the canonical replacement.