Skip to content

chore: easy-issue sweep 2026-05-11#368

Merged
mvillmow merged 16 commits into
mainfrom
chore/easy-sweep-2026-05-11
May 16, 2026
Merged

chore: easy-issue sweep 2026-05-11#368
mvillmow merged 16 commits into
mainfrom
chore/easy-sweep-2026-05-11

Conversation

@mvillmow
Copy link
Copy Markdown
Contributor

Summary

Bundled easy-issue sweep across documentation, CI hardening, and small fixes per
the 2026-05-11 ecosystem-wide sweep. 50-LoC-per-issue cap respected; medium/hard
items (full openapi examples, devcontainer split, request-body validation tests,
ASAN preset, etc.) deferred and listed as BLOCKED below.

Implemented

Verified ALREADY-DONE (closes via merge)

BLOCKED (>50 LoC or external/structural — not in scope for sweep)

Skipped (external / process / future-dated)

Test plan

  • CI green on chore/easy-sweep-2026-05-11
  • actions/checkout and actions/cache@v5 SHAs resolve correctly in _required.yml
  • gitleaks step succeeds (SHA256 matches published checksum)
  • just coverage runs after a clean checkout via the new deps-coverage chain
  • ./scripts/check-release-readiness.sh 0.1.0 cleanly fails on a host without GPG, passes with one configured
  • Spectral OpenAPI lint: pre-existing failure on main (Could not read ruleset at .../@stoplight/spectral-openapi) — not introduced by this sweep, leave for separate PR

Co-Authored-By: Claude Opus 4.7 (1M context) noreply@anthropic.com

@mvillmow mvillmow enabled auto-merge (squash) May 12, 2026 02:54
mvillmow added a commit that referenced this pull request May 12, 2026
…nt addition

The PR's comment-only edit to clients/python/pyproject.toml (issue #104)
changed the file content, invalidating the SHA256 of the editable `pypi: .`
package entry in pixi.lock. This caused `pixi install --locked` to fail in
4 CI jobs (Lint, Test, Type Check, security/dependency-scan).

Regenerated using pixi v0.39.5 (matching CI's setup-pixi@v0.8.1 pin) so
no incompatible v0.4x lockfile fields are written. Only the editable
package SHA256 changes (1 line).

Refs PR #368
@mvillmow mvillmow force-pushed the chore/easy-sweep-2026-05-11 branch from 542e3de to 67ff7ff Compare May 13, 2026 14:05
mvillmow added a commit that referenced this pull request May 13, 2026
…nt addition

The PR's comment-only edit to clients/python/pyproject.toml (issue #104)
changed the file content, invalidating the SHA256 of the editable `pypi: .`
package entry in pixi.lock. This caused `pixi install --locked` to fail in
4 CI jobs (Lint, Test, Type Check, security/dependency-scan).

Regenerated using pixi v0.39.5 (matching CI's setup-pixi@v0.8.1 pin) so
no incompatible v0.4x lockfile fields are written. Only the editable
package SHA256 changes (1 line).

Refs PR #368
mvillmow and others added 14 commits May 16, 2026 01:37
- Pin actions/cache@v5 in pixi-check to v5.0.5 SHA (closes #247, closes #238)
- Pin actions/checkout in schema-validation job to v4.2.2 SHA (closes #354)
- Pin Trivy install to v0.58.1 instead of latest (closes #255)
- Verify gitleaks tarball SHA256 before extract (closes #267)
- Pin Python <3.14 in agamemnon/pixi.toml to avoid pytest-asyncio 0.26 deprecation warning (closes #109)
- Replace stale `~keystone.models.TaskEvent` Sphinx cross-refs with `~agamemnon.orchestration.models.TaskEvent` in nats_listener.py docstrings (closes #121)
…cedure

- Fix MD060 in line 31 table separators (closes #314)
- Document Dockerfile base-image digest refresh procedure (closes #325)
…olicy

- CONTRIBUTING.md: GTest ABI compatibility callout (closes #341)
- CONTRIBUTING.md: nats.c CMakeLists.txt vs cpp-fetchcontent-deps.cdx.json sync rule (closes #258)
- SECURITY.md: secrets-scan gate policy and allowlist process (closes #226)
…, model tiers, python pkg

- AGENTS.md: liveness/readiness probe table (closes #317)
- AGENTS.md: PUT vs PATCH task semantics (closes #316)
- AGENTS.md: clarify MaxAckPending=1 is consumer-side contract (closes #315)
- CLAUDE.md: HMAS model tier assignments table (closes #153)
- CLAUDE.md: agamemnon/ Python package layout, deps, and tasks (closes #110)
…, docker-route comment

- openapi.yaml: add Tailscale {tailscale_host} server entry (closes #146)
- openapi.yaml: document chaos POST body is silently ignored (closes #191)
- docs/metrics.md: new — Prometheus endpoint reference and scrape config (closes #297)
- docs/api/README.md: link /metrics under Health & Observability
- src/routes.cpp: comment explaining /v1/agents/docker is intentional alias (closes #144)
- justfile: add deps-coverage recipe and chain it from coverage (closes #214)
- CLAUDE.md: note coverage depends on deps-coverage
- scripts/check-release-readiness.sh: GPG key presence check before mutating files (closes #103)
- README.md: clarify OpenSSL provided by pixi, libssl-dev only needed on bare hosts (closes #251)
…age scope

- python-client.yml + python-client-release.yml: TODO comment to add Conan/FetchContent caches if C++ extension steps are added (closes #242)
- renovate.json: explicit pre-commit hook group ensures editorconfig-checker.python is bumped (closes #329)
- clients/python/pyproject.toml: comment explaining bump-version.py coverage exclusion (closes #104)
Closes #323

Pinned ubuntu:24.04 to digest sha256:c4a8d5503dfb2a3eb8ab5f807da5bc69a85730fb49b5cfca2330194ebcc41c7b
(retrieved 2026-05-11 from Docker Hub). Refresh procedure documented in
RELEASING.md (added in this same sweep).
…nt addition

The PR's comment-only edit to clients/python/pyproject.toml (issue #104)
changed the file content, invalidating the SHA256 of the editable `pypi: .`
package entry in pixi.lock. This caused `pixi install --locked` to fail in
4 CI jobs (Lint, Test, Type Check, security/dependency-scan).

Regenerated using pixi v0.39.5 (matching CI's setup-pixi@v0.8.1 pin) so
no incompatible v0.4x lockfile fields are written. Only the editable
package SHA256 changes (1 line).

Refs PR #368
The rebase onto main produced a stale clients/python/pixi.lock —
the homericintelligence-agamemnon package's local source sha256
drifted, causing `pixi install --locked` to fail in CI with
"lock-file not up-to-date with the project".

This blocked Lint, Test, Type Check, and security/dependency-scan
(all of which run `setup-pixi@v0.8.1` with `pixi install --locked`).

Regenerated the lock file with pinned pixi v0.39.5 (matching CI's
setup-pixi version per the MEMORY runbook).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@mvillmow mvillmow force-pushed the chore/easy-sweep-2026-05-11 branch from 42df5fa to def2b7a Compare May 16, 2026 08:38
mvillmow added 2 commits May 16, 2026 02:10
The upstream install.sh has been flaky for v0.58.1 — it locates the
release tag but exits 1 before extracting the archive. This caused
security/dependency-scan to fail consistently with pip-audit passing.

Switch to a direct binary tarball download from the GitHub releases
URL, which is deterministic and avoids the install.sh code path.
v0.58.1 has been removed from aquasecurity/trivy releases (404 from the
binary URL and from install.sh tag lookup, which is why
security/dependency-scan was failing). Bump to v0.69.3 (current at fix
time) while keeping the deterministic direct-binary download.

This is the minimal change needed to unblock dependency-scan in the
`chore: easy-issue sweep 2026-05-11` branch. A separate cleanup can
introduce a renovate/dependabot rule to track Trivy releases going
forward.
@mvillmow mvillmow merged commit a7ce40e into main May 16, 2026
26 checks passed
@mvillmow mvillmow deleted the chore/easy-sweep-2026-05-11 branch May 16, 2026 09:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment