@astrale-domains/services 0.3.3 → 0.4.0

package/CHANGELOG.md

@@ -1,5 +1,30 @@
 # Changelog
 
+## [0.4.0](https://github.com/astrale-os/domains/compare/services-v0.3.4...services-v0.4.0) (2026-09-07)
+
+
+### ⚠ BREAKING CHANGES
+
+* **services:** implement management methods on exact worker classes ([#176](https://github.com/astrale-os/domains/issues/176))
+
+### Features
+
+* **domains:** adopt deploy-only project environments ([#183](https://github.com/astrale-os/domains/issues/183)) ([cedee91](https://github.com/astrale-os/domains/commit/cedee910d89e3e23420aad8291f54715fc6c87f5))
+* **services:** implement management methods on exact worker classes ([#176](https://github.com/astrale-os/domains/issues/176)) ([f08ecd5](https://github.com/astrale-os/domains/commit/f08ecd5ffed9305e3ebae194202a1d252a84d1af))
+
+
+### Bug Fixes
+
+* **domains:** align bootstrap domains with Register kernel ([#185](https://github.com/astrale-os/domains/issues/185)) ([ead0ed0](https://github.com/astrale-os/domains/commit/ead0ed0fc7483d862e825934dd5e7ec01fbeaced))
+
+## [0.3.4](https://github.com/astrale-os/domains/compare/services-v0.3.3...services-v0.3.4) (2026-09-05)
+
+
+### Bug Fixes
+
+* **services:** bind Workers to their canonical public URL ([#182](https://github.com/astrale-os/domains/issues/182)) ([fc8be8e](https://github.com/astrale-os/domains/commit/fc8be8eb10fc81491665d076daa8d12c6d2fe63f))
+* **services:** explain interrupted deployment recovery ([#180](https://github.com/astrale-os/domains/issues/180)) ([d65f814](https://github.com/astrale-os/domains/commit/d65f814603202ff5769c2c2bcc5f86bc703f9b44))
+
 ## [0.3.3](https://github.com/astrale-os/domains/compare/services-v0.3.2...services-v0.3.3) (2026-09-05)
 
 

package/README.md

@@ -16,6 +16,9 @@ protocols behind neutral SDK Integrations and stores only admitted lifecycle evi
 - logs are remote evidence admitted by the Cloudflare Provider before a Workflow returns them.
 - the only admitted Worker service binding is the logical platform router; the provider resolves
   it to the selected environment and callers cannot name arbitrary same-account Workers.
+- the provider supplies `WORKER_URL` as the Service's canonical HTTPS URL to both candidate and
+  public Workers. It is reserved provider metadata, not a caller variable or secret. Applications
+  therefore keep one issuer even when requests arrive over HTTP or through a dispatcher alias.
 
 The View, CLI, and agent consumers read the named Service Queries directly; there is intentionally
 no list Function wrapping `listServicesQuery`. Deployment, secrets, schedules, logs, and deletion
@@ -23,6 +26,12 @@ are Workflows because they coordinate admitted caller intent with external effec
 are authorized by the ownership Policy before their Workflows begin. `service-hosting`
 is the provider-neutral compute Integration contract. Cloudflare is its first Provider.
 
+`Service` declares seven abstract management contracts. `CloudflareWorker` owns their executable
+Methods (`setSecret`, `deleteSecret`, `secrets`, `setSchedule`, `schedules`, `logs`, `delete`) and
+applies `OwnService` to each one. Workflow addresses are `CloudflareWorker.*`; abstract `Service.*`
+keys are not executable. A future provider Class must supply its own concrete declarations and
+implementations. Properties and ownership relationships retain their inherited meaning.
+
 ## Development
 
 Copy `.env.example` to `.env.dev` and fill the Cloudflare values.
@@ -82,3 +91,9 @@ receipt alongside the artifact tag. Matching code alone is insufficient: Cloudfl
 can remain unchanged when only secrets change. Services-owned operation leases serialize callers;
 operators making direct provider changes must coordinate with those operations. The code ETag is
 not a lock for concurrent configuration changes.
+
+If a Kernel interruption prevents recording a deployment outcome, the Service can remain busy
+until its retained operation lease expires (currently 30 minutes from acquisition or renewal).
+Retry the same deployment after the expiry reported in the rejection; it reuses the Service and
+provider identity. Do not clear the lease or create another Service to bypass an uncertain outcome.
+An operation without a recorded expiry needs operator inspection, not a guessed retry deadline.