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

Merged

coilysiren merged 1 commit from aos/claude/finish-dowel-rename into main

2026-08-19 01:32:21 +00:00

coilyco-ops commented

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

Member

Closes #948. Answers ask 4 of coilyco-bridge/deploy#657.

Two corrections to #948 before the diff

There are six references across four files, not three. #948 named docs/sirens-echo-http.md and internal/community/silentturn_test.go. It missed AGENTS.md and the two in .agents/skills/sirens-dowel/references/moxn-knowledge-base.md.

None of them is a test name. #948's case for urgency rested on one being a test name, invoking the TestTheCadenceIsEightSixteenForty precedent where a name stops describing the thing and passes anyway. The two test functions in that file are TestATurnThatAlreadyAnsweredThroughAToolPostsNothing and TestATurnThatDidNothingAtAllIsStillAFailure. Neither carries the lane, and neither does the fixture type. The reference is in a comment above the fixture. Real, worth fixing, not the failure mode described.

What changed, and why each one

#948 said to read deploy#657 first, because some references there are deliberate survivors. I did, and the split in this repo is cleaner than in deploy.

docs/sirens-echo-http.md, two references — factually wrong, fixed. The cluster has cut over: the namespace is sirens-dowel, and sirens-deep-owl-glass no longer exists in the manifests or on kai-server. The doc named that namespace twice. I checked the surrounding facts against sirens-dowel-values.yaml rather than assuming they travelled with the name, and both still hold: NodePort 30122 and tailnet.enabled: false.

AGENTS.md — retired name, fixed. It called the lane "the owl.glass lane" while naming its skill root sirens-dowel.

internal/community/silentturn_test.go — retired name, rewritten rather than substituted. The comment called the fixture "the owl.glass shape". What it describes is not specific to that lane at all: it is the shape any write tool aimed at the reply channel produces. It now says that.

I first wrote a version citing an issue number for the record behind it, then checked and the commit that added the file (c0973a5) names no issue, so the citation came out rather than going in unverified.

.agents/skills/sirens-dowel/references/moxn-knowledge-base.md, two references — deliberate survivors, kept and annotated. owl-glass there is the Moxn workspace, and owl-glass.moxn.dev is its address. Moxn's names, not this deployment's, and they did not rename with the lane. Renaming them would have broken a working reference.

deploy#657's actual complaint is that "nothing distinguishes a deliberate survivor from a missed one," so these now carry one line saying why they stay. That is the discipline its ask 1 requests, applied to this repo's two.

Not in scope, still open on deploy#657

The telemetry discontinuity is the part that bites tomorrow and is not mine to fix here. service.name moved with the namespace, so every SigNoz query keyed to sirens-deep-owl-glass now returns empty rather than erroring, and the #939/#940 incident measurements are all against the old name. Anyone asking "did the fix work" on August 19 has to union two service names or read an empty result as a pass. deploy#657 ask 3 carries it.

Also untouched, correctly: the incident issues themselves still say owl.glass, per Darren's reasoning on #657 that a record silently adopting a name the incident did not happen under is harder to trust.

Verification

just gate passes: build, policy-check, vet, test, test-skips, pre-commit. Naming only, no behaviour, and the one Go file touched is a comment.

Closes #948. Answers ask 4 of coilyco-bridge/deploy#657. ## Two corrections to #948 before the diff **There are six references across four files, not three.** #948 named `docs/sirens-echo-http.md` and `internal/community/silentturn_test.go`. It missed `AGENTS.md` and the two in `.agents/skills/sirens-dowel/references/moxn-knowledge-base.md`. **None of them is a test name.** #948's case for urgency rested on one being a test name, invoking the `TestTheCadenceIsEightSixteenForty` precedent where a name stops describing the thing and passes anyway. The two test functions in that file are `TestATurnThatAlreadyAnsweredThroughAToolPostsNothing` and `TestATurnThatDidNothingAtAllIsStillAFailure`. Neither carries the lane, and neither does the fixture type. The reference is in a comment above the fixture. Real, worth fixing, not the failure mode described. ## What changed, and why each one #948 said to read deploy#657 first, because some references there are deliberate survivors. I did, and the split in this repo is cleaner than in deploy. **`docs/sirens-echo-http.md`, two references — factually wrong, fixed.** The cluster has cut over: the namespace is `sirens-dowel`, and `sirens-deep-owl-glass` no longer exists in the manifests or on kai-server. The doc named that namespace twice. I checked the surrounding facts against `sirens-dowel-values.yaml` rather than assuming they travelled with the name, and both still hold: NodePort **30122** and **`tailnet.enabled: false`**. **`AGENTS.md` — retired name, fixed.** It called the lane "the owl.glass lane" while naming its skill root `sirens-dowel`. **`internal/community/silentturn_test.go` — retired name, rewritten rather than substituted.** The comment called the fixture "the owl.glass shape". What it describes is not specific to that lane at all: it is the shape any write tool aimed at the reply channel produces. It now says that. I first wrote a version citing an issue number for the record behind it, then checked and **the commit that added the file (`c0973a5`) names no issue**, so the citation came out rather than going in unverified. **`.agents/skills/sirens-dowel/references/moxn-knowledge-base.md`, two references — deliberate survivors, kept and annotated.** `owl-glass` there is the **Moxn workspace**, and `owl-glass.moxn.dev` is its address. Moxn's names, not this deployment's, and they did not rename with the lane. Renaming them would have broken a working reference. deploy#657's actual complaint is that "nothing distinguishes a deliberate survivor from a missed one," so these now carry one line saying why they stay. That is the discipline its ask 1 requests, applied to this repo's two. ## Not in scope, still open on deploy#657 The **telemetry discontinuity** is the part that bites tomorrow and is not mine to fix here. `service.name` moved with the namespace, so every SigNoz query keyed to `sirens-deep-owl-glass` now returns empty rather than erroring, and the #939/#940 incident measurements are all against the old name. Anyone asking "did the fix work" on August 19 has to union two service names or read an empty result as a pass. deploy#657 ask 3 carries it. Also untouched, correctly: the incident issues themselves still say `owl.glass`, per Darren's reasoning on #657 that a record silently adopting a name the incident did not happen under is harder to trust. ## Verification `just gate` passes: build, policy-check, vet, test, test-skips, pre-commit. Naming only, no behaviour, and the one Go file touched is a comment.

coilyco-ops added 1 commit

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

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

ci / image-build (pull_request) Successful in 35s

Details

ci / test (pull_request) Successful in 1m8s

Details

ci / publish-echo-image (pull_request) Has been skipped

Details

ci / publish-observed (pull_request) Has been skipped

Details

467588d3ab

The lane renamed in coilyco-bridge/deploy a5d87c5 and this repo kept the
old name in three places. The cluster has since cut over: the namespace
is sirens-dowel and sirens-deep-owl-glass no longer exists, so the HTTP
doc named a namespace that is gone while its NodePort and its
tailnet.enabled: false were still correct, both checked against the
deployed values rather than assumed.

AGENTS called the lane by its retired name. The silent-turn fixture
comment named the lane where what it describes is a shape any write tool
aimed at the reply channel produces, so it now says that instead.

The Moxn workspace stays owl-glass and its filesystem stays glass. Those
are Moxn's names, not this deployment's, and they did not rename with the
lane. Annotated in place, because deploy#657 records that the real
problem is nothing distinguishing a deliberate survivor from a miss.

Closes #948. Answers ask 4 of coilyco-bridge/deploy#657.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-authored-by: Kai Siren <coilysiren@gmail.com>
Co-authored-by: Claude <noreply@anthropic.com>

coilyco-ops requested review from coilysiren

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