port(upstream#2007): 23 more names in the channel rainbow list

[adminopenclaw8-sketch]

Update 2026-09-19: synced with master after #67

• New base/master: 31c2aa8e3869822f79a8414d89277d5552669056 (includes fix(packets): keep the Details summary on one line so rows stay bounded #67).
• New head: adafd563051a6f8fb34f5e1c115b82b7ee2a167e, an ordinary merge of origin/master into the previous head a0d3fdd9 (no rebase, no force-push). Feature scope unchanged: channel-rainbow.json (320 entries) and internal/channel/channel_rainbow_test.go; the merge only adds master's advance (fix(packets): keep the Details summary on one line so rows stay bounded #67's three files).
• Local: internal/channel go test PASS incl. TestChannelRainbowMatchesDeriveKey; JSON valid.
• Row-height tests on the port(upstream#1860): Phosphor icon instead of emoji in the RX coverage header #28+port(upstream#2007): 23 more names in the channel rainbow list #50 integration tree (CI integration only: #28 + #50 — do not merge #66) (local fixture server, Chromium 1208): test-issue-1122-packets-filter-ux-e2e.js 6/6 (incl. "Path column row height stays bounded < 60px"), test-issue-1122-details-row-clamp-e2e.js 18/18.
• CI: run 35424424934 on adafd563: success. Go Build & Test, Playwright E2E (incl. #1122 row height and the clamp test 18/18): success. Docker job success with GHCR steps skipped. Release, Deploy Staging, Badges skipped (fork guards).
• The older verification and CI notes below describe earlier heads and are kept for history.

---

Split out of #25 (commit abef6d3a there). This branch holds exactly one upstream change so it can be reviewed, tested and reverted on its own.

Upstream

• PR: Kpa-clawbot/CoreScope#2007 by @nullrouten0, merged 2026-09-12
• Upstream commit: c283f42c1fd1e43fc3dbd78ae6ed4ef4178bd067
• Applied with git cherry-pick -x onto master fda24ca5; upstream authorship kept, and the commit message carries the (cherry picked from commit …) line.
• Patch-id identical to the port(upstream): 26 clean upstream fixes — prune batching, /ws limits, observer liveness, watchdog race #25 commit and to the upstream commit.
• Scope: channel-rainbow.json (data only).

Problem

The ingestor's hashtag-channel guess list (channel-rainbow.json, name → derived key) lacked 23 generic channel names seen in operators' client-side lists.

Change

Adds those 23 names (297 → 320 entries). Upstream checked every added name against stored ciphertext on two archives before landing it.

Adaptation to this fork

None. The cherry-pick applied without conflicts and the changed lines are identical to upstream.

Notes for review

Effect: traffic on those hashtag channels is decrypted and named automatically. The file is read by the ingestor at startup (cmd/ingestor/main.go) and copied by Dockerfile.go.

Dependencies and merge order

• Independent. Branched directly from master fda24ca5 and needs no other PR from this split.
• A merge simulation of all 24 split PRs gives the same tree in upstream order and in reverse order.
• The same simulation also merges cleanly with each of the open API: expose on-wire channelHashHex on channel messages #11, feat(map): support CARTO basemap API keys #13 and chore(deps): bump to golang:1.27.1-alpine3.24 and alpine:3.24 #22, and with test(ingestor): make neighbor metrics pruning deterministic #33 (opened during this split; it makes TestPruneOldNeighborMetrics deterministic). If test(ingestor): make neighbor metrics pruning deterministic #33 lands first, the expected CI failure named below disappears; nothing in this PR depends on it.
• Recommended position: 24 of 24, following upstream's merge order (the order port(upstream): 26 clean upstream fixes — prune batching, /ws limits, observer liveness, watchdog race #25 was assembled in).

Verification

Local run of the same commands as CI's “Go Build & Test” job (server tests with -race), on this branch and on master fda24ca5 under the same conditions (same machine, run one after another):

Check	master fda24ca5	this branch	verdict
go-ingestor-build-vet	PASS	PASS
go-ingestor-test	FAIL	FAIL TestPruneOldNeighborMetrics	baseline failure, unchanged
channel-lib-test	PASS	PASS
decrypt-cli-build-test	PASS	PASS
dockerfile-copy-invariants	FAIL	FAIL	not runnable locally: script needs bash ≥4 (declare -A), macOS has 3.2; identical on master
staging-disk-monitor	PASS	PASS
css-vars-lint	PASS	PASS

Baseline failures (fail identically on master; not introduced or changed here): see rows marked baseline failure, unchanged.

Browser validation (local, fixture DB, no staging/production): Not applicable (no frontend change).

Not run:

• Playwright E2E suites (no local Playwright install); CI's E2E job will also be skipped, see below.
• eslint (not installed locally; CI installs it on the fly).
• Go -race/tests for modules this PR does not touch (unchanged code, identical to master).
• Browser tests against staging/production (deliberately none).

Expected GitHub CI: “Go Build & Test” is expected to fail on TestPruneOldNeighborMetrics, which already fails on master (see #25's run). Downstream jobs (Playwright, image build) are therefore skipped. “Deploy Staging” and all GHCR publish steps only run on push to master and cannot run for this PR.
Two further ingestor tests have failed intermittently in this split's CI on branches whose cmd/ingestor tree is byte-identical to master (#27, #28), so they can also appear here without being caused by this change:

• TestBackfillTxLastSeen_ResolvesFromMaxObservationTimestamp: also reproduced locally on unmodified master.
• TestMQTTStallWatchdog_DisconnectedEscalationThrottled_1749: the suite flake that upstream test(ingestor): join the watchdog loop goroutine instead of only asking it to stop Kpa-clawbot/CoreScope#2003 (also split out of port(upstream): 26 clean upstream fixes — prune batching, /ws limits, observer liveness, watchdog race #25) addresses.

GitHub CI result: run 34753115957 on 7cc34f0f. Go Build & Test: failure; all downstream jobs incl. Deploy Staging skipped. Failed tests:

• TestPruneOldNeighborMetrics: fails on master, documented baseline
• TestBackfillTxLastSeen_ResolvesFromMaxObservationTimestamp: intermittent, reproduced on unmodified master locally

🤖 Generated with Claude Code

Update — current master 693eb04 (2026-09-17)

The existing PR branch was updated without force-push from 7cc34f0f to bdde3e3f. The merge graph preserves the original upstream-attributed commit, incorporates green master 693eb045dbb10ecdd4657444134a696f007297e1, and includes the verified local prep commit 18f6d3db.

The PR diff against current master is limited to channel-rainbow.json and internal/channel/channel_rainbow_test.go.

Fresh verification on bdde3e3

• JSON parse and schema check: PASS — object with 320 entries, all values valid 16-byte hex keys
• cd internal/channel && go test ./...: PASS; validates entry count, duplicate names/keys, firmware-default Public key, and every derived key
• git diff --check: PASS

No staging, production, deployment, workflow, or auto-merge action was performed. GitHub PR CI: run 35220101234 completed with failure. Go/build gates passed; Playwright failed the existing Kpa-clawbot#1122/Kpa-clawbot#1124 path-row-height assertion (69–84 px, limit <60 px). That assertion passed on green master run 35212554871, while this PR changes only rainbow channel JSON and its Go validation test, so this is recorded as a new unrelated CI deviation rather than hidden as a baseline failure. Release, image publication, staging deploy, and badge publication were skipped. No retry or unrelated fix was made.

Update — current master 37d82e8 (2026-09-18)

The existing PR branch was updated without force-push from bdde3e3f to a0d3fdd9, an ordinary merge commit. The merge graph incorporates green master 37d82e8a1844234e498c0c909d0fb1155ea858d7, which now includes PR #64 and PR #48 (see PR #28's update for detail — this branch inherits the same base).

The PR diff against current master remains exactly channel-rainbow.json + internal/channel/channel_rainbow_test.go (121 lines). git diff --check clean. .github/workflows/ unchanged by this branch.

Fresh verification on a0d3fdd

• channel-rainbow.json: valid JSON, 320 entries, diff is purely additive (23 new keys after Public, no existing key/value touched)
• cd internal/channel && go test ./...: PASS — TestChannelRainbowMatchesDeriveKey validates entry count, no duplicate names/keys, the firmware-default Public key, and every other entry's key against DeriveKey(name)

Kpa-clawbot#1122/Kpa-clawbot#1124 row-height investigation

The prior CI run (35220101234 on bdde3e3f) failed test-issue-1122-packets-filter-ux-e2e.js's row-height assertion. This PR touches no packets-page code, so the failure was investigated rather than written off as baseline, per developer instruction. Findings, most important first:

1. Under CI-faithful local conditions (fixture freshened via tools/freshen-fixture.sh, matching the exact CI pipeline step, then migrated), the test passes cleanly and repeatably: 6/6 assertions, 3/3 runs, on current master, on this PR's new head a0d3fdd9, and on the old 693eb045 baseline the prior CI run for this same assertion was green against. This is established by direct local reproduction, not hypothesis, and rules out a code-level regression in this PR or in master's recent history — the same result holds across all three commits under identical faithful conditions.
2. A first pass without fixture-freshening (an incomplete reproduction of CI's process, using the committed fixture's own stale dates as-is) does show a real, separate row-height issue, reproducible identically on the PR#50 candidate, current master, and 693eb045 alike: table row height is set by its tallest cell, and .data-table td.col-details's base (desktop) CSS rule (white-space: normal; word-break: break-word) has no line/height clamp — only a mobile media query clamps it. A row with long details/tag text can wrap to multiple lines and stretch the whole row, including the already-correctly-bounded .col-details td.col-path cell (height: 28px from the bug(packets): filter UX disaster — help panel overlaps table, toolbar chaotic, path chips spill rows Kpa-clawbot/CoreScope#1122/bug(packets): layout chaos — path chips spill rows, +N popover overlaps, filter chips collide with toolbar, Saved dropdown bleeds through Kpa-clawbot/CoreScope#1128 fix, which itself works — the sibling cell is what drags the row taller). This is a genuine, verifiable CSS behavior, confirmed via live DOM/computed-style inspection, but it only manifests with this PR's ad-hoc stale-fixture setup, not under CI's actual (freshened) conditions — so it does not explain the CI failure either, and is noted here only for completeness, not as an action item.
3. What is not established: why the specific CI run on bdde3e3f failed. It cannot be reproduced locally even with fixture-freshening applied; the "Seed grouped-packet row for Packets page collapse button in the left column of the table opens the dialog. Kpa-clawbot/CoreScope#1486 collapse test" CI step (an additional SQL insert before the server starts) was not replicated locally, and may account for the difference, as could headless-Chromium/font-rendering differences between this Mac and the CI runner. This can only be settled by observing the fresh CI run on the new head — it is not something this local investigation could resolve further without expanding scope into CI-environment replication.

No staging, production, deployment, workflow, or auto-merge action was performed. All local servers, temp DBs, and scratch checkouts used for this investigation were cleaned up afterward.

🤖 Generated with Claude Code