commit ca9cf65a8b17673833029125c60d8a36748a6328
Author: Ramin Torabi <16882282+RaminTorabi@users.noreply.github.com>
Date: Fri Jun 5 20:40:29 2026 +0200

sanitize(victoria-metrics): drop private ansible playbook references

The public overlay must not name the private ansible-playbooks-gentoo
repo. The victoria-metrics pkg_postinst elog (which lands in the
operator email via the portage-elog forwarder) told users to "Tune
retention/listen/memory via the ansible victoriametrics role
(roles/victoriametrics in ansible-playbooks-gentoo)" - leaking the
private repo name and its internal layout into a public ebuild.

Replace with playbook-agnostic guidance: tune via a systemd drop-in
at /etc/systemd/system/victoria-metrics.service.d/ (standard,
public systemd knowledge; no private references).

Cleaned all five touch points across both the single-node and the
(hard-masked) cluster variants:
- victoria-metrics{,-bin} pkg_postinst elog
- victoria-metrics-bin src_install layout comment
- victoria-metrics-cluster{,-bin} src_install layout comment
- both files/victoria-metrics.service ExecStart comments

Overlay-wide grep for ansible/playbook now returns nothing. elog/
comment/service-comment changes do not touch ebuild metadata
variables, so md5-cache is unaffected. bash -n clean on all four
ebuilds.

commit 5c31dfdcd7a716509dc06c7e142936c2543e1cfc
Author: Ramin Torabi <16882282+RaminTorabi@users.noreply.github.com>
Date: Sat May 23 16:01:10 2026 +0200

unmask: app-metrics/victoria-metrics{,-bin} after host validation

Validated app-metrics/victoria-metrics-1.143.0 (source build) on a Gentoo host: full Go compile from vendor/, install, systemd start, /metrics + /-/healthy endpoints respond, dynamic UID/GID, storage path layout, version stamp embedded correctly. Unmask both source and -bin variants - they have a !! blocker between them so the consumer still picks one or the other, but neither needs to be hand-unmasked at the host level any more.

Stamp the source ebuild as `verified at 2026-05-23` so the next weekly classifies it as skip:stamped instead of re-emerging from scratch.

commit a48d79adb3d332187d234488d7080a163d071fac
Author: Ramin Torabi <16882282+RaminTorabi@users.noreply.github.com>
Date: Thu May 21 12:02:20 2026 +0200

sanitize: drop private-context references; add missing metadata.xml for victoria-metrics acct ebuilds

Cleanup pass before going public:
* package.mask: drop "Cirrus is the first deployment target" + "rolling out to the rest of the fleet" - those leak private home-fleet topology
* acct-user/victoria-metrics: drop "no fleet-wide convention" wording in favor of generic phrasing
* app-metrics/victoria-metrics{,-bin}/files/victoria-metrics.service: drop "Time-series database for the home fleet" header and the ansible-role specifics that do not belong in a public overlay
* app-metrics/victoria-metrics{,-bin}/metadata.xml: rewrite longdescription to drop the home-fleet / sensor specifics
* licenses/Kiro-EULA, licenses/Kiro-CLI-EULA: drop references to internal "Task 6.1 / Task 6.2 of the rato-verlay spec"

Add the two missing metadata.xml files (acct-group/victoria-metrics, acct-user/victoria-metrics) so every package satisfies the Gentoo overlay QA requirement.

commit 970c19ca3c23af798cdedd48acf91f4036fb5665
Author: Ramin Torabi <16882282+RaminTorabi@users.noreply.github.com>
Date: Thu May 21 11:15:07 2026 +0200

rato-verlay: squashed history

Single-commit root for the public Gentoo overlay containing AWS-specific ebuilds (amazon-ssm-agent, amazon-cloudwatch-agent, amazon-efs-utils, victoria-metrics, kiro, dcv) and the daily/weekly automation hooks. Older commit history was wiped to keep the public-facing repo small and free of operational noise; meaningful changes from this point forward are tracked normally.