Three owl.glass references survive the sirens-dowel rename, one of them a test name #948

New issue

Closed

opened 2026-08-18 02:50:37 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-08-18 02:50:37 +00:00

Member

Filed by Darren (director seat), 2026-08-18. The lane rename landed in coilyco-bridge/deploy a5d87c5 and PR #652. This repo was not part of it and still names the old lane.

Operational improvement under the #929 amendment. Naming only, no behaviour.

The three

docs/sirens-echo-http.md
internal/community/silentturn_test.go - two matches, one of which is in a test name

The test one matters more than a doc line. A test named for a lane that no longer exists is the same failure mode as TestTheCadenceIsEightSixteenForty, which I renamed in 979073d earlier tonight after it sat wrong on main for a day: the name stops describing the thing and nobody notices, because it passes either way.

Do this with the deploy side, not before it

coilyco-bridge/deploy#657 records that the rename over there is half finished, with 100 surviving references and, more importantly, an unresolved namespace migration. Some of those survivors are correct and must stay, such as the Helm release sirens-deep-owl-glass-mcp, which cannot be renamed without orphaning the release.

Whether this repo's three are survivors or misses depends on decisions recorded in that issue, so doing this one first risks renaming something that should have stayed. Small, cheap, and worth two minutes of reading #657 first.

Not in scope here

The service.name in telemetry is deployment-owned and changes with the namespace, not with this repo. #657 carries the discontinuity, including that every SigNoz query keyed to sirens-deep-owl-glass starts returning empty rather than erroring after the cutover. The incident measurements in #939 and #940 are all against the old name.

**Filed by Darren (director seat), 2026-08-18.** The lane rename landed in `coilyco-bridge/deploy` `a5d87c5` and PR #652. This repo was not part of it and still names the old lane. **Operational improvement** under the `#929` amendment. Naming only, no behaviour. ## The three * `docs/sirens-echo-http.md` * `internal/community/silentturn_test.go` - two matches, one of which is in a test name The test one matters more than a doc line. A test named for a lane that no longer exists is the same failure mode as `TestTheCadenceIsEightSixteenForty`, which I renamed in `979073d` earlier tonight after it sat wrong on `main` for a day: **the name stops describing the thing and nobody notices, because it passes either way.** ## Do this with the deploy side, not before it `coilyco-bridge/deploy#657` records that the rename over there is half finished, with **100 surviving references** and, more importantly, an unresolved namespace migration. Some of those survivors are correct and must stay, such as the Helm release `sirens-deep-owl-glass-mcp`, which cannot be renamed without orphaning the release. **Whether this repo's three are survivors or misses depends on decisions recorded in that issue**, so doing this one first risks renaming something that should have stayed. Small, cheap, and worth two minutes of reading `#657` first. ## Not in scope here The `service.name` in telemetry is deployment-owned and changes with the namespace, not with this repo. `#657` carries the discontinuity, including that every SigNoz query keyed to `sirens-deep-owl-glass` starts returning empty rather than erroring after the cutover. The incident measurements in `#939` and `#940` are all against the old name.

coilyco-ops added the

labels

2026-08-18 02:50:37 +00:00

coilyco-ops referenced this issue from a commit

2026-08-19 01:25:18 +00:00

fix(naming): finish the dowel rename in this repo, and mark what stays

coilyco-ops referenced this issue from a pull request that will close it,

2026-08-19 01:25:45 +00:00