feat: kernel 0.2.1 — per-company entity vocabulary #5

Merged

haskos-bot merged 1 commit from feat/kernel-0-2-1 into dev

2026-07-27 04:30:17 +00:00

john commented

2026-07-27 04:29:19 +00:00

Owner

Bumps the pinned package 0.2.0 → 0.2.1 and covers the regression it fixes.

SuperCleanOS is live on 0.2.0 right now, and a site→crew link would be rejected today. 0.2.0 hardcoded fourteen HaskyOS entity types in the shared package; 0.2.1 reads HASKOS_VALID_ENTITY_TYPES per call and replaces the default set rather than adding to it.

The gap survived my earlier end-to-end pass because validation applies only to entity_link — registered_entity.entity_type is free text, so POST /entities with type site succeeded and looked like proof the vocabulary worked.

alembic check clean against 0.2.1 — config and EntityLinkService only, no model changes, baseline unchanged
Two new tests: the configured vocabulary is accepted, a HaskyOS type outside it is rejected. 14 passing
.env.example and CLAUDE.md document the setting and the per-company values

Follow-up on merge: set HASKOS_VALID_ENTITY_TYPES=site,crew,job,staff,shift on the superclean-kernel app and redeploy.

Bumps the pinned package 0.2.0 → 0.2.1 and covers the regression it fixes. **SuperCleanOS is live on 0.2.0 right now, and a `site`→`crew` link would be rejected today.** 0.2.0 hardcoded fourteen HaskyOS entity types in the shared package; 0.2.1 reads `HASKOS_VALID_ENTITY_TYPES` per call and **replaces** the default set rather than adding to it. The gap survived my earlier end-to-end pass because validation applies only to `entity_link` — `registered_entity.entity_type` is free text, so `POST /entities` with type `site` succeeded and looked like proof the vocabulary worked. - `alembic check` clean against 0.2.1 — config and `EntityLinkService` only, no model changes, baseline unchanged - Two new tests: the configured vocabulary is accepted, a HaskyOS type outside it is rejected. 14 passing - `.env.example` and `CLAUDE.md` document the setting and the per-company values Follow-up on merge: set `HASKOS_VALID_ENTITY_TYPES=site,crew,job,staff,shift` on the `superclean-kernel` app and redeploy.

john added 1 commit

2026-07-27 04:29:19 +00:00

feat: kernel 0.2.1 — per-company entity vocabulary

CI / Deploy (pull_request) Has been skipped

Details

CI / Detect Changes (pull_request) Has been cancelled

Details

CI / Docker Build (pull_request) Has been cancelled

Details

CI / Backend (pull_request) Has been cancelled

Details

da0ceebf68

Bumps the pinned package from 0.2.0 to 0.2.1 and covers the regression it fixes.

0.2.0 hardcoded fourteen HaskyOS entity types in the shared package, so any other
company got a 400 when linking its own kinds of thing. SuperCleanOS is live on 0.2.0
right now: a site-to-crew link would be rejected today. 0.2.1 reads
HASKOS_VALID_ENTITY_TYPES per call and replaces the default set rather than adding to
it.

The gap survived the earlier end-to-end pass because validation applies only to
entity_link — registered_entity.entity_type is free text, so POST /entities with type
"site" succeeded and looked like proof the vocabulary worked.

- alembic check clean against 0.2.1: config and EntityLinkService only, no model
  changes, baseline unchanged.
- Two new tests: the configured vocabulary is accepted, and a HaskyOS type outside it
  is rejected. 14 passing.
- .env.example and CLAUDE.md document the setting and the per-company values.