Skip to content

docs(claude): sync org-standards block (backend#1602) - #651

Merged
LukasWodka merged 2 commits into
developfrom
docs/1602-org-standards-sync
Aug 11, 2026
Merged

docs(claude): sync org-standards block (backend#1602)#651
LukasWodka merged 2 commits into
developfrom
docs/1602-org-standards-sync

Conversation

@LukasWodka

@LukasWodkaLukasWodka commented Aug 10, 2026

Copy link
Copy Markdown
Contributor

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


Note

Low Risk
Documentation-only sync of engineering process guidance; no runtime or security impact.

Overview
Syncs the org-standards block in CLAUDE.md from tracebloc/.github/org-standards.md (managed copy — not hand-edited here).

Under Engineer kanban, it adds a rule that every board ticket must have a Status (nothing stays at "No Status"), with new work starting in Backlog, and bugs as the exception: use work-type:bug and move them directly to Ready instead of waiting for refinement.

Reviewed by Cursor Bugbot for commit 2911d5e. Bugbot is set up for automated code reviews on this repo. Configure here.

Managed sync from tracebloc/.github/org-standards.md.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@LukasWodkaLukasWodka self-assigned this Aug 10, 2026
@aptracebloc
aptracebloc self-requested a review August 11, 2026 07:19

@aptraceblocaptracebloc left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@LukasWodkaApproved. Managed org-standards sync — verified the block is faithful.

Extracted the content between the org-standards markers in this branch's CLAUDE.md (51 lines) and diffed it against canonical tracebloc/.github/org-standards.md: identical. The single added line is the new ### Engineer kanban bullet ("every ticket carries a Status… bugs go straight to Ready") — inside the managed block and verbatim to canonical, not a hand-edit. Bugbot green, CI green. Only CLAUDE.md changed, so no code-owner gate applies.

🤖 Generated with Claude Code

@LukasWodka
LukasWodka merged commit e7a47f6 into developAug 11, 2026
12 checks passed
@LukasWodka
LukasWodka deleted the docs/1602-org-standards-sync branch August 11, 2026 11:06
LukasWodka added a commit that referenced this pull request Aug 14, 2026
… (backend#1729) (#715)
The guard added in #706 parses all four CLIENT_ENV declarations and compares
them. It ran in helm-ci.yaml's `Helm lint` job. `Helm lint` is not a required
status check on this repo -- the required contexts on develop are `Unit tests`,
`Lint`, `quality/*`, `version-bump-gate/version-check` and `Source-of-truth
drift` -- so a PR that made the four declarations disagree was mergeable with
the guard red. It could advise; it could not block.
That is the shape backend#1729 is about, in the epic's own flagship deliverable:
a mechanism that appears to verify something without being connected to the
outcome it claims to control.
`Source-of-truth drift` is the correct home and needed no new configuration:
- it is REQUIRED on develop and on main, so a disagreement blocks the merge;
- it deliberately carries NO `paths:` on pull_request (its header records why
-- a path-filtered required check bricks PRs outside those paths, which is
what happened to #651/#657/#660 on 2026-08-11), so the guard now also runs
on the installer-only PRs helm-ci's filter would have skipped;
- it is already the home of the other duplicated-declaration guard
(check-drift.sh), and the guard needs only bash + python3, ~2s.
helm-ci loses the step and the two `paths:` entries that arrived with it in
#706. `scripts/install-k8s.ps1` genuinely leaves -- helm-ci is the repo's
heaviest workflow (a real k3d cluster plus two 4-platform matrices) and a
PowerShell installer edit has no other reason to start it. The explicit
`scripts/lib/common.sh` entry also goes, but that one was always redundant:
the pre-existing `scripts/lib/**` glob still matches it, so helm-ci's
triggering on a common.sh change is unchanged.
Mutation-proved rather than assumed: with `staging)` renamed in
scripts/lib/common.sh the guard exits 1; restored, it exits 0. The mutation
anchor was asserted to have applied first -- an inert mutation and good
coverage look identical in a log.
Verified green on this branch before arming: all four declarations agree and
all six spellings are exercised (dev 12, development 2, prod 11, production 4,
staging 9, stg 6).
Refs backend#1729
Sign up for freeto 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

@LukasWodka@aptracebloc