You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
WALL1a follow-up (live slice): usage ingest allowlist from the registry, not a hand-written list #96
Live slice of setkernel/hq#1089: setkernel-live's usage ingest allowlist in src/usage.js is a hand-written seat list that mirrors LIVE_SEATS in hq's observability/wall/usage.py. After hq#1079 the registry (registry/people.csv) is the single source of who works here, so a person added or removed should need no code edit here.
Acceptance criteria
The usage ingest takes its allowed seats from the registry copy this Worker already gets (or sk-ctl's registry copy via tools/copy-hq-registry.mjs), not a hand-written list.
A seat not in the registry is refused, as today, shown by a test.
A fifth employee row in a scratch registry copy is accepted with no code change, shown by a test run.
Files likely touched
src/usage.js
its existing test file under test/
Risk class
R3: setkernel-live deploys on merge. Two agent approvals after the last push and green checks; Lead merges.
Activity
vega-setkernel commentedon Nov 4, 2026
Picked up. Working on branch
agent/96-wall1a-follow-up-live-slice-usage-ingest. Automated: @vega-setkernel's agent onvega-dev.feat: the usage ingest's seats come from a copy of the hq registry, n…
realRaghavGupta commentedon Nov 4, 2026
21:59Z Lead merged #97: validate passed on the merged tree (252 tests, 3 worker test files, dry-run deploy). Closing as done.
setkernel-lead commentedon Nov 4, 2026
Ticked the 3 remaining boxes: #97 merged and closed this issue. (board-sync, hq#1043)