chore: kernel 0.2.5 — link vocabulary comes from the app registry #9

Merged

john merged 1 commit from feat/registry-description-content into dev

2026-07-27 10:15:06 +00:00

john commented

2026-07-27 10:12:04 +00:00

Owner

0.2.5 makes EntityLinkService read registered_app.entity_types, falling back to HASKOS_VALID_ENTITY_TYPES and then HaskyOS's defaults. Until this lands, an instance still validates links from an env var — which is per-container: superclean-kernel had it set and superclean-api, importing the same library against the same database, did not.

No schema change. 0002_registry_columns already covers the description and content columns that 0.2.3 restored, and it is written idempotently so it is correct for both the fresh-create and stamped-adopt entry states. alembic check is clean against 0.2.5 with 0002 applied; single head; 20 tests pass.

Deploying this to superclean-kernel also brings SuperCleanOS's database to 0002. That database is still at 0001_baseline and has neither column. Nothing is broken there today — the running container is on kernel 0.2.1, whose model predates them — but the two are only self-consistent by accident, and the entrypoint's alembic upgrade head closes it on deploy.

0.2.5 makes `EntityLinkService` read `registered_app.entity_types`, falling back to `HASKOS_VALID_ENTITY_TYPES` and then HaskyOS's defaults. Until this lands, an instance still validates links from an env var — which is per-container: `superclean-kernel` had it set and `superclean-api`, importing the same library against the same database, did not. **No schema change.** `0002_registry_columns` already covers the `description` and `content` columns that 0.2.3 restored, and it is written idempotently so it is correct for both the fresh-create and stamped-adopt entry states. `alembic check` is clean against 0.2.5 with 0002 applied; single head; 20 tests pass. **Deploying this to `superclean-kernel` also brings SuperCleanOS's database to 0002.** That database is still at `0001_baseline` and has neither column. Nothing is broken there today — the running container is on kernel 0.2.1, whose model predates them — but the two are only self-consistent by accident, and the entrypoint's `alembic upgrade head` closes it on deploy.

john added 1 commit

2026-07-27 10:12:04 +00:00

chore: kernel 0.2.5 — link vocabulary comes from the app registry

CI / Deploy (pull_request) Has been skipped

Details

CI / Docker Build (pull_request) Has been cancelled

Details

CI / Detect Changes (pull_request) Has been cancelled

Details

CI / Backend (pull_request) Has been cancelled

Details

8431f74e3e

0.2.5 makes EntityLinkService read registered_app.entity_types, falling back to
HASKOS_VALID_ENTITY_TYPES and then HaskyOS's defaults. Until this lands, an instance
still validates links from an env var, which is per-container: superclean-kernel had it
set and superclean-api, importing the same library against the same database, did not.

No schema change. 0002_registry_columns already covers the description and content
columns 0.2.3 restored, and alembic check is clean against 0.2.5 with 0002 applied.
20 tests pass.

Deploying this to superclean-kernel also brings SuperCleanOS's database to 0002 — it is
still at 0001_baseline and has neither column. Nothing is broken there today because the
running container is on 0.2.1, whose model predates them, but the two are only
self-consistent by accident.