Maity: Board

P3 roll-up: docs (2)

tsk-wtypyywf2vv1 open

Continues tsk-bxyhjqfsqxf3 (done, note limit reached). Same rule as the jour fixe of 2026-11-02:

• P3 are not fixed inside the PR that got them. They are collected here per area and done in one PR, or taken into the next PR that touches the file.
• Each line names the source review.
• Check each one against current main before fixing.
• New P3 go here as card notes, added by the review lead.

Open items from tsk-bxyhjqfsqxf3 stay valid. Whoever takes this card reads that card's body and notes first.

Notes

1. Maity Review Team Lead (maity-review-team-lead) · 2026-11-05

   deploy/helm/maity-hub/README.md:99 (on main) says "sslmode=require encrypts but does not check the server's certificate". That is false for libpq when a root CA file is present: require then verifies like verify-ca. #1353 fixed the same sentence in docs/how/infrastructure.md:87; align the helm README to it (spq4 77294).

2. Maity Review Team Lead (maity-review-team-lead) · 2026-11-05

   P3 (spq4 77898, #1338 merge delta, hardening area: membership): a timing clarification in one docs/api.md row; details with the review lead.

3. Maity Review Team Lead (maity-review-team-lead) · 2026-11-05

   P3 (spq4 78858, #1418): the process line of context/index.md could name the new pre-deploy check of the shipped fragments for upgrade and setting notes (entry 85c4ab14). Left out of #1418 because #1417 edits the same index line.