@defrex/autobuild 0.13.0 → 0.14.0

package/skills/guide/references/operator-api.md

@@ -1,7 +1,7 @@
 # Operator API v1
 
 The hosted service exposes the polling-oriented operator surface at
-`/operator/v1/repos/{repo}`. It is versioned with remote store protocol **3**.
+`/operator/v1/repos/{repo}`. It is versioned with remote store protocol **4**.
 Every request must send `X-Autobuild-Version`,
 `X-Autobuild-Protocol-Version: 3`, and `Authorization: Bearer …`. Identity is
 checked before authentication or resource lookup.

package/skills/guide/references/remote-store-protocol.md

@@ -37,7 +37,7 @@ headers, or available backend.
   `[store] url` (in that precedence order, before the local default); the shipped client appends the routes below.
 - Every `/builds`, `/repos`, and `/sessions` request sends
   `X-Autobuild-Version` with the exact client package version and
-  `X-Autobuild-Protocol-Version` with the remote protocol version (`3` in this
+  `X-Autobuild-Protocol-Version` with the remote protocol version (`4` in this
   distribution). Before authentication,
   body parsing, or resource lookup, the server validates the release-line window and known protocol identity.
   Unsupported or missing values receive `409 {"kind":"conflict","error":"…"}`;
@@ -355,6 +355,74 @@ part of this protocol. Retention is enforced server-side inside the store at
 deposit time (bounded pruning of dispatcher run/config artifact revisions),
 not through any endpoint.
 
+### Named reducer values
+
+`POST /builds/{slug}/reducer-values` and
+`POST /repos/{repo}/reducer-values` accept at most 4 KiB of JSON:
+
+```json
+{"reducer":"dispatchStatus","args":{"run":"run-a"}}
+```
+
+The response is `200 {"version":2,"cursor":123,"value":{...}}`. Only the
+finished JSON answer is returned, with no accumulator or raw-log bundle. `cursor`
+is the authoritative prefix included in the answer, not a guarantee to include
+appends concurrent with the request. Every call checks durable progress and
+persisted state; parallel instances may safely advance the same checkpoint.
+Snapshots are disposable caches: deletion, corruption, wrong versions and
+unreadable cache storage cause replay. Log read failures remain errors.
+
+The executable catalog is `kernel/reducer-registry.ts`. All requests reject
+unknown names, excluded reducers, wrong scopes and invalid/extra arguments with
+`400 validation`. A missing resource is `404`, project and delegated authority
+checks are the same as other reads, and unsupported methods remain unavailable.
+The operation is read-only authority even though its HTTP verb is POST and its
+internal cache may advance. It does not accept caller-supplied state. This is an
+additive protocol route: historical snapshot and event handlers and the supported
+client version window are unchanged.
+
+| Scope | Reducers with no arguments |
+| --- | --- |
+| Build | `executionNoProgress`, `summaryRequests`, `build`, `buildDigest`, `currentPrAttachments`, `pendingPrAttachmentReclaims`, `openExecution`, `lastExecutionOutcome`, `infrastructureFailureReset`, `openWorkspace`, `setupStreak`, `openBuildWorkspace`, `currentDeferralObservation`, `dashboardFacts`, `pinnedAssets`, `buildDelegation` |
+| Repository | `harvest`, `dispatchSettings`, `sandboxStates`, `openHarvestExecutions`, `autoMergeDefault`, `effectiveConfig`, `harvestDelegation` |
+
+| Reducer | Scope | Required arguments |
+| --- | --- | --- |
+| `dispatchStatus`, `openTick` | Repository | `run`: nonempty string |
+| `dispatchFailureBudget` | Build | `infrastructureOwnsWorkspace`: boolean |
+| `phaseFailures` | Build | `phase`: valid phase name; `round`: nonnegative integer |
+
+Arguments are canonicalized into the cache identity; variants never reuse one
+another's accumulator. `effectiveConfig` returns an object with optional `run`
+and `reference: {kind, rev}`. Absence is distinct from an unreadable referenced
+artifact. Delegation values contain semantic lifecycle facts indexed by prefixed
+identifiers, not authorization decisions; request time and grace expiry are
+always evaluated against those facts on the service.
+
+Each remaining registered reducer is explicitly excluded:
+
+| Reducers | Reason |
+| --- | --- |
+| `journalView`, `repositoryStateEvents`, `dispatchFrontend` | Raw repository event lists |
+| `session` | Operator-session log scope |
+| `publicationState` | Selector functions in finished value |
+| `logIndex` | Maps and Sets in finished value |
+| `hostedPrAttachments` | Map as finished value |
+| `summaryBoundary`, `ticketSourceHealth`, `frozenPrImageHost`, `publishedBranchHead`, `verifyDiffBase`, `recordedBaseSha`, `baseBranch`, `provisionMarker`, `recoveryCheckpoint` | Existing finished contract can return top-level `undefined`, which is not JSON |
+
+`GET /repos/{repo}/state-events` is **deprecated**. Its response remains unchanged
+for supported clients, including the current dispatcher run's event tail. It is
+the compatibility exception to flat event-row reads; new callers should request
+named values. The current product no longer loads or writes raw-tail snapshots.
+
+The `value.*` snapshot namespace is reserved for the adapter's private value
+checkpoint hooks. Public snapshot GET and PUT requests for this prefix return
+`400 validation`, including requests made with delegated or administrator
+credentials. Adapter snapshot APIs reject the same names. Ordinary snapshot
+names retain their existing behavior. The value cache key format is versioned;
+checkpoints from the former publicly writable format are ignored and rebuilt
+from the log after upgrading.
+
 ### Reducer snapshots
 
 A reducer snapshot is one registered reducer's serialized state as of a log
@@ -1136,7 +1204,7 @@ Four shipped behaviors do not add `BuildStore` routes:
   store lifecycle; there is no close endpoint.
 - `GET /health` is outside the `BuildStore` interface. It is always open and
   returns exactly `200 {"ok":true,"autobuildVersion":"<package>",
-  "protocolVersion":"3", "supportedClientRange":{"minVersion":"0.9.0",
+  "protocolVersion":"4", "supportedClientRange":{"minVersion":"0.9.0",
   "maxVersionExclusive":"0.12.0"}}`. It reports HTTP-process availability and identity,
   not a deeper backing-store transaction or migration check.
 
@@ -1213,3 +1281,17 @@ require a project credential and operate only on its own identity; admin and
 internal operator credentials cannot impersonate self-service. All protocol
 responses are no-store/no-referrer. Connection commands are unavailable in
 build/harvest sessions.
+
+### Repository tick telemetry (protocol 4)
+
+`POST /repos/:repo/tick/begin` accepts `{holder}` and returns the actual start
+ timestamp, or null when the unexpired repository lease does not match.
+`POST /repos/:repo/tick/finish` accepts `{holder, completion, events}`. Completion
+is `{outcome:"completed", counters}` or `{outcome:"failed", error}`; events is
+empty for a quiet success or a matching dispatcher start/terminal pair for that
+holder. The validated batch and finished telemetry commit atomically. The reply
+is `{observation, events}` with assigned envelopes, or null on fencing failure.
+These operations never renew the lease. Repository records optionally expose
+`tick: {run, open?: {startedAt}, finished?: {run, startedAt, completedAt, ...completion}}`.
+They retain the previous completion while a new tick is open and after lease
+release. Build and session credentials cannot mutate repository ticks.

package/templates/hosted-service/package.json

@@ -4,8 +4,8 @@
     "build": "ab-hosted-service-build"
   },
   "dependencies": {
-    "@defrex/autobuild-hosted-store-service": "0.13.0",
-    "@defrex/autobuild": "0.13.0",
+    "@defrex/autobuild-hosted-store-service": "0.14.0",
+    "@defrex/autobuild": "0.14.0",
     "next": "16.1.6",
     "react": "19.2.4",
     "react-dom": "19.2.4"