docs(claude): sync the org-standards block

[tracebloc-release-train]

Managed sync of the org-standards block into this repo's CLAUDE.md — canonical
source: tracebloc/.github/org-standards.md. Do not hand-edit the block; to change
a rule, open a PR against tracebloc/.github and the sync propagates it.

Part of tracebloc/backend#1602 (org-wide engineering standards).

🤖 Generated with Claude Code

[LukasWodka]

Content is fine — byte-identical managed sync of the org-standards block.

Red on the same required check as the whole batch: set-status / closing-ref, step "The title names a ticket, so the PR must link it". The gate reads backend#1602 from the title's trailing parens and wants it in the PR's link graph; Part of tracebloc/backend#1602 is a mention, not a link.

Don't follow the gate's printed advice here. Adding Closes tracebloc/backend#1602 would close the epic when the first of these twenty PRs merges, with nineteen still open — cross-repo closing keywords do fire in the owner/repo#n form.

The fix is in the sync generator: drop (backend#1602) from the title so the gate returns NOTHING_NAMED, and keep Part of … in the body for the cross-reference. Full write-up on tracebloc/.github#344.

Holding my review until the titles are regenerated — the content is right, the blocker isn't in this diff.

[LukasWodka]

Title fix worked — set-status / closing-ref is green here and across the batch. I approved the identical content on rfcs#54.

Holding my approval on the remaining red, which is structural rather than a finding:

Bugbot review gate: FAIL
No Bugbot check run on head …
Waited 900s over 46 attempt(s) and Bugbot never reported a terminal verdict.
Measured Bugbot latency is p50 164s / max 635s over 40 runs, so this is not slowness.

The author is app/tracebloc-release-train and Bugbot doesn't review bot PRs, so the verdict the gate waits for cannot arrive. Every managed sync into a Bugbot-gated repo burns 900s and reports red, permanently. rfcs has no Bugbot caller, which is the only reason it went green.

bugbot / review isn't a required context, so it doesn't block the merge — but I don't approve over a red check. Full write-up and the two options on tracebloc/.github#344; the better one is exempting bot-authored PRs in the caller rather than timing out on a verdict that structurally cannot come.