Release v0.5.92 · teylabs/kit

kit:status and kit:add flag an undefined connection ability. kit.mcp.connection_ability defaults to settings.read, which the settings feature declares; a host without it (or with its own value) had every MCP connection refused as permission_denied. With the mcp feature, the host requirements now carry a kit.mcp.connection_ability config step: met when a feature declares the ability through the Registry or the Gate defines it, else attention naming the key, the effect and the three fixes. test:status covers the default without settings, an undefined value, a Gate-defined one and a Registry-declared one.

A workspace created in the same request is admitted. IsKitWorkspace read admitted as null until the model was read back, so a workspace made and used in one request was refused admission_required. The trait now mirrors the column's default (true in the kit's migration) on an unsaved or just-created model whose table has the column, so it answers the way its row will; an explicit admitted => false stays false, and admission stays distinct from creation (a host whose adopted column defaults to false sets admitted to false in its model's $attributes). test:workspace-guard covers create-then-check.
Leaving a tenant no longer wipes Pennant's array store. TenantBoundary and the FlushFeatureCacheTask switch task flushed Pennant's cache on every switch; under the array store (the kit's default, and tests) that cache is the store itself, so a flag deactivated earlier in the request came back on, and a test that deactivated a capability then called /mcp saw it on. Both now flush only for a store with a backend (TenantBoundary::flushes(): the default store's driver is not array), where the cache can go stale across tenants. test:capability-guard and test:tenant-tasks cover both stores.

What's Changed

[0.5.x] MCP switch-over fixes: just-created workspace admission, Pennant array store kept across tenant switches, kit:status flags an undefined connection ability (backport of #433) by @jaspertey in #434

Full Changelog: v0.5.91...v0.5.92