Hostel v0.1.14

This release brings together the Bed runtime and component changes since v0.0.5, including declarative services, process configuration, lifecycle renewal, and capability-aware isolation.

Upgrade Notes

• Update status consumers for /v1/status schema version 5. Host observations are split into host.fact and host.status; managed port allocations are under host.status.ports, and configuration-source observations are under components.configuration. Bed lifecycle and component status are reported separately.
• Review the current Bed creation, service, and component configuration contracts before upgrading older clients. Bed services use caller-provided ServiceSpec declarations; the runtime image supplies their executables and dependencies.
• Named configuration sources and absolute env_files references are intended for a trusted control plane. Source registration is not tenant authorization, and environment injection does not establish filesystem or process isolation.

New Features

• Bed services: optional per-Bed managed processes share the Bed execution environment and lifecycle, with restart policies, readiness checks, HTTP access discovery, optional bearer authentication, and daemon-wide TCP port allocation shared with Amenities.
• Configuration management: ordinary execution and services independently select env, env_files, env_from, and env_value_from. Named host directories can supply projected configuration; resolved file values stay out of persisted declarations and status responses.
• Lifecycle and execution: a shared Bed model separates persistent Bed identity, replaceable Executors, and individual Executions. Asynchronous initialization waits for data restore and environment preparation. Bed renewal extends retention without creating or waking a Bed.
• Capability-aware isolation: filesystem, identity, and network components compose their actual guarantees into Bed room profiles. Optional network namespaces and policies, scoped Unix users, and PRoot/pathshim process views support different host capabilities while reporting limitations explicitly.
• Storage and integrations: configurable BedFS paths, per-Bed store selection, explicit S3 and restic transfers, Bed-scoped remote MCP access, structured execution events, and OpenTelemetry tracing.

Bug Fixes

• Separate service readiness from process supervision and support readiness checks when network inspection privileges are unavailable.
• Verify service listeners in the Bed network scope and use UUIDv7 transfer instance IDs.
• Harden initialization, cleanup, executor failure handling, and filesystem boundaries; preserve command stdin and heredoc behavior across execution paths.

Full Changelog: v0.0.5...v0.1.14