chore(code-comments): clean comment-discipline violations #63
Labels
No labels
burndown-2026-06
coherence-core
consult
headless
interactive
P0
P1
P2
P3
P4
No milestone
No project
No assignees
1 participant
Due date
No due date set.
Dependencies
No dependencies set.
Reference
coilyco-flight-deck/otel-a2a-relay#63
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What
The
code-commentspre-commit check (ships from agentic-os) targets two patterns Kai wants gone across her repos:This repo carries 245 latent violations under the current check (v0.16.0): 84 in code, 161 in YAML.
Why these are latent
This repo does not pin agentic-os and never adopted the managed hook block, so
code-commentshas never run here. Both code and YAML violations are latent.Scope
code-commentsactive (runagentic-os/scripts/apply-agentic-os-hooks.py).Top offenders:
tempo_grafana/docker/grafana/provisioning/datasources/datasources.yaml- 34core/chart/values.yaml- 32tempo_grafana/docker/tempo.yaml- 30scripts/check_luca_spans.py- 20tempo_grafana/docker/docker-compose.yml- 17arize_phoenix/src/otel_a2a_relay_arize_phoenix/viz/render.py- 11Done when
- id: code-commentsactive in the managed blockpre-commit run code-comments --all-filespasses with noexcludesgrandfathering, beyond genuinely generated or vendored pathsCross-repo context: the catalogue was built 2026-06-08. Sibling meta-work is tracked in agentic-os (check changes) and infrastructure (ansible version-sync role).