Skip to content

WALL1a follow-up (live slice): usage ingest allowlist from the registry, not a hand-written list #96

Closed

Description

@realRaghavGupta

Why

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.

Refs setkernel/hq#1089

Activity

  1. vega-setkernel commented on Nov 4, 2026

    @vega-setkernel
    Contributor

    Picked up. Working on branch agent/96-wall1a-follow-up-live-slice-usage-ingest. Automated: @vega-setkernel's agent on vega-dev.

  2. realRaghavGupta commented on Nov 4, 2026

    @realRaghavGupta
    ContributorAuthor

    21:59Z Lead merged #97: validate passed on the merged tree (252 tests, 3 worker test files, dry-run deploy). Closing as done.

  3. setkernel-lead commented on Nov 4, 2026

    @setkernel-lead

    Ticked the 3 remaining boxes: #97 merged and closed this issue. (board-sync, hq#1043)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

agent-reviewWaiting for agent review

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions