docs(claude): weekly CLAUDE.md refresh 2026-07-06

[allyblockcast]

Added

• Documented that GitHub Actions perf artifacts intentionally retain for 1 day while durable history is published to the performance dashboard (from PR [codex] Cap Actions artifact retention at one day #14).
• Documented Helm liveness/readiness guidance and default embedded-PostgreSQL pool/worker-concurrency caps to avoid DB-pressure restarts (from PR fix(helm): reduce Hindsight DB pressure during liveness #15).

Pruned

• None.

Fixed

• None.

Uncertain

• Branch name uses staff-engineer/docs-claude-weekly-refresh-20260706 because pushing the requested docs/claude-weekly-refresh-20260706 name was rejected by GitHub due to a remote directory/file namespace conflict.

Verification

• Reviewed merged PRs since 2026-06-29: [codex] Cap Actions artifact retention at one day #14, fix(helm): reduce Hindsight DB pressure during liveness #15.
• Queried gbrain for recent hindsight facts; no matching recent facts returned.
• Ran git diff --check.

[allyblockcast]

Ally — Consolidated PR Review

Lenses: pr-review-toolkit (code, tests, comments, errors, types) + gstack/review + native-codex.
reviewed head: f2f929f

Looks good

Docs-only change (CLAUDE.md, +7/-0), a weekly refresh summarizing PRs #14 and #15. Verified both additions against the source PRs rather than trusting the summary at face value:

• Perf-artifact retention claim — .github/workflows/perf-test.yml confirms retention-days: 1 on all three upload-artifact steps, and a "Publish to dashboard" step ships enriched results to the hindsight-continuous-performance-monitor GitHub Pages site. Matches the new CLAUDE.md text exactly.
• Helm liveness/readiness + pool-cap claim — helm/hindsight/values.yaml confirms API liveness is /version:8888, worker liveness is /metrics:8889, both readiness probes stay on /health, and HINDSIGHT_API_DB_POOL_MAX_SIZE=10 / worker slot caps (HINDSIGHT_API_WORKER_MAX_SLOTS=2, RETAIN_MAX_CONCURRENT=1) are set as described.
• No pre-existing "Helm Operations" section or liveness/readiness text on main — this is new content, not an accidental duplicate.
• The diff is purely additive (no deletions), so this refresh doesn't risk silently dropping still-current facts, which has bitten prior weekly-refresh PRs in this pattern.

Suggestions

• None.

Self-review comment mode: this PR was authored by the same bot identity; formal review/approval must come from a human or a distinct reviewer identity.