Skip to content

docs(claude): weekly CLAUDE.md refresh 2026-07-27 - #21

Merged
kkroo merged 1 commit into
mainfrom
staff-engineer/docs-claude-weekly-refresh-20260727
Aug 11, 2026
Merged

kkroo merged 1 commit into
mainfrom
staff-engineer/docs-claude-weekly-refresh-20260727

Conversation

@allyblockcast

@allyblockcast allyblockcast Bot commented Jul 27, 2026

Copy link
Copy Markdown

Added

Pruned

  • None. The seven-day merge set did not contradict an existing root CLAUDE.md instruction.

Fixed

  • None. No stale path or line citation was established by the reviewed merge.

Uncertain — needs human review

  • gbrain recall/query tools were unavailable in this execution, consistent with the active Paperclip Hindsight plugin outage tracked in BLO-18382/BLO-18384. No memory-derived guidance was added or removed.
  • The requested docs/claude-weekly-refresh-20260727 branch cannot exist because this repository has a top-level docs Git ref. This PR uses the established staff-engineer/docs-... fallback, matching prior weekly refresh PR docs(claude): weekly CLAUDE.md refresh 2026-07-06 #16.

Verification

Paperclip: BLO-18402

Co-Authored-By: Paperclip <noreply@paperclip.ing>
@allyblockcast

allyblockcast Bot commented Jul 27, 2026

Copy link
Copy Markdown
Author

🔗 Paperclip issue: BLO-18382
🔗 Paperclip issue: BLO-18384
🔗 Paperclip issue: BLO-18402

1 similar comment
@allyblockcast

allyblockcast Bot commented Jul 27, 2026

Copy link
Copy Markdown
Author

🔗 Paperclip issue: BLO-18382
🔗 Paperclip issue: BLO-18384
🔗 Paperclip issue: BLO-18402

@allyblockcast allyblockcast left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ally — Consolidated PR Review

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

Reviewed head: 70423b5

Looks good. The readiness guidance accurately reflects the merged Helm configuration from PR #20: API readiness uses /version, worker readiness uses /metrics, and /health remains the database-aware endpoint.

Strengths

  • Keeps the repository guidance concise and scoped to the operational invariant.
  • Explains the failure mode the probe choice prevents, rather than only recording endpoint names.

Recommended Action

Approve and merge.

@kkroo
kkroo merged commit ead5161 into main Aug 11, 2026
80 checks passed
kkroo pushed a commit that referenced this pull request Sep 10, 2026
The "Helm Operations" paragraph claimed "readiness remains DB-backed on
`/health`". That is false against the chart and contradicts the
"Helm Health Probes" section immediately below it.

Ground truth in helm/hindsight/values.yaml at this head:
  - API readiness      -> /version   (values.yaml:53)
  - worker readiness   -> /metrics   (values.yaml:156)
  - the only /health probes are the optional TEI reranker/embeddings
    sidecars on ports 8090/8091 (values.yaml:396-447) -- unrelated to
    API/worker readiness.

values.yaml:49-50 states the intent directly: "Keep readiness on the
cheap process/version endpoint so DB pressure cannot cascade into kube
probe failures".

The claim was introduced by #16 (8df7368, 2026-08-25) and regressed the
fact established by #21 (ead5161, 2026-08-11). Left uncorrected it
would lead a reader to repoint readiness at /health, reintroducing the
DB-pressure -> probe-failure restart cascade that #15, #18, #20 and #21
were filed to remove.

Drops the false clause and cross-references the section below rather
than restating it. Liveness endpoints and the DB-pool/concurrency
sentence were verified correct and are unchanged.

Co-authored-by: Staff Engineer <staff-engineer@paperclip.blockcast.net>
Co-authored-by: Paperclip <noreply@paperclip.ing>
Co-authored-by: Claude <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants