@agentsfleet/orly 0.14.2 → 0.14.3

package/README.md

@@ -78,7 +78,7 @@ TypeSafe's Jev model supplies runtime advice through explicit `orly judge` reque
 
 See [releases](https://github.com/agentsfleet/orly/releases) for published versions.
 The install commands below fetch the published package.
-The release workflow publishes 0.14.2 after its version change merges to `main`.
+The release workflow publishes 0.14.3 after its version change merges to `main`.
 
 ---
 

package/dispatch/write_ts_adhere_bun.md

@@ -313,6 +313,8 @@ The TypeScript-relevant gate cards (`ui-substitution`, `design-token`) dissolve
 
 The design-system package (`ui/packages/design-system/src/index.ts` exports — `Section`, `Card`, `Badge`, `Button`, `Input`, `Dialog`, `Pagination`, `EmptyState`, `Tooltip`, `List`/`ListItem`, `WakePulse`, `Terminal`, `InstallBlock`, etc.) is the source of truth for visual primitives. Raw HTML in either dashboard or marketing files drifts from those tokens silently.
 
+**Record dates.** Label creation timestamps **Created** across tables and detail views. Other timestamps name their event: **Updated**, **Last used**, **Occurred**, **Expires**, or **Joined / invited**. Reuse shared app labels; avoid generic **Time** or **Date** headings. Render dates with the shared `Time` component.
+
 **Marketing-display typography — primitives now exist.** `<DisplayXL>` (marketing hero `<h1>`, `text-fluid-hero`) and `<DisplayLG>` (section heads `<h2>`, `text-fluid-display-lg`) ship from `@agentsfleet/design-system` and compose `font-mono` + the fluid text/leading/tracking tokens internally. Use them on marketing-display surfaces. Raw `<h1>+utilities` is no longer the carve-out — UI GATE blocks it. The dashboard's `<PageTitle>` (`text-heading ≈ 18px`) remains the correct primitive for app surfaces.
 
 This gate enforces "use the primitive when one exists" without enumerating the primitives in this rule (so the rule scales as the design-system grows).

package/docs/CHANGELOG.md

@@ -1,5 +1,13 @@
 # Changelog
 
+## 0.14.3 — 2026-10-15
+
+The REST API guide carries agentsfleet's conversation and reviewed-setup exceptions, and the TypeScript rules name how timestamps are labelled.
+
+- **Conversation sends** — fleet and draft `/messages` sends take one UUIDv7 `operation_id` in the body and refuse an `Idempotency-Key` header; replay, conflict and `202` answers are defined.
+- **Stale reviews** — a reviewed setup mutation refused with `409` also returns the current `review_digest` and `current_state`.
+- **Record dates** — creation timestamps are labelled **Created**; other timestamps name their event.
+
 ## 0.14.2 — 2026-10-15
 
 The release inventory reads npm 12's pack output, and the API and logging guides cite agentsfleet's current module paths.

package/docs/REST_API_DESIGN_GUIDELINES.md

@@ -142,7 +142,19 @@ If the parent ID is in the path, never repeat it in the body.
 
 **PATCH idempotency guarantee** — PATCH MUST be idempotent unless the spec's "Failure Modes" section explicitly declares otherwise with a reason. Idempotent PATCH means: issuing the same body twice in succession produces identical row state and identical 200 responses. A negative test that issues the same PATCH twice and asserts equality is required (§10).
 
-**Idempotency keys for non-idempotent POSTs.** Any POST that creates a billable, externally-visible, or side-effecting resource MUST accept an `Idempotency-Key` request header (UUIDv7 from the client). The server stores `(workspace_id, key) → response` for at least 24 hours and replays the prior response on duplicate. Endpoints exempt: pure RPC reads, internal-only POSTs. List which endpoints honor the key in the OpenAPI description.
+**Idempotency keys for non-idempotent POSTs.** Any POST that creates a billable, externally-visible, or side-effecting resource MUST accept an `Idempotency-Key` request header (UUIDv7 from the client), except the conversation rules below. The server stores `(workspace_id, key) → response` for at least 24 hours and replays the prior response on duplicate. Endpoints exempt: pure RPC reads, internal-only POSTs. List which endpoints honor the key in the OpenAPI description.
+
+**Owner-approved conversation exception.** Fleet and creator-private draft
+`/messages` sends require one UUIDv7 `operation_id` in the JSON body. They MUST
+reject an `Idempotency-Key` header. Draft creation uses the same body key and
+atomically records its optional first message. Authorization and lifecycle
+checks apply before replay. The same key, normalized message and actor recover
+the accepted message; changed content or actor conflicts. Sends return
+`202 {status, sequence, replayed}` for drafts, or the fleet's accepted event
+receipt, with `Location` pointing to that conversation's messages collection.
+Pending state, answers and usage are read through messages and its authorized
+live stream. These resources create neither a public turn-status resource nor
+a generic operation. Creator-private text never appears in workspace streams.
 
 **Owner-approved workspace exception.** `POST /v1/workspaces` accepts no replay
 key. It requires a tenant-unique name and performs one tenant-scoped insert with
@@ -156,7 +168,7 @@ generalize this exception to other POST endpoints.
 
 ### Long-running operations
 
-Endpoints that can't complete inside the request window MUST follow this convention — no per-endpoint reinvention:
+Endpoints that can't complete inside the request window MUST follow this convention, except conversation acceptance described above:
 
 1. The kicking POST returns `202 Accepted` with `Location: /v1/operations/{operation_id}` and a body containing `operation_id` and `status: "pending"`.
 2. `GET /v1/operations/{operation_id}` returns:
@@ -434,6 +446,14 @@ the caller gets the registry's 500 and no internal detail.
 - `409` MUST include `current_state: <string>` naming the state that forbade the transition (e.g. `"current_state": "approved"` when the caller tried to approve an already-approved gate).
 - `412` MUST include `etag: <string>` carrying the resource's current ETag so the client can refetch and retry.
 
+<!-- oracle-packs:start product.agentsfleet -->
+Reviewed setup mutations in `agentsfleet` additionally return `review_digest`
+on a stale-review `409`. The daemon computes this opaque digest from the current
+effective setup and access/model resolution versions. The response also carries
+`current_state`; clients fetch the current review before submitting again.
+This extension grants no setup or runtime authority.
+<!-- oracle-packs:end -->
+
 Don't invent other extensions without amending this doc.
 
 ---

package/docs/RULE_ENFORCEMENT.md

@@ -7,14 +7,14 @@ regenerates this file and fails on any difference. To update it, run
 | Rule document | enforced by | judged | acknowledged | classified | trigger |
 |---|---|--:|--:|--:|---|
 | `docs/LOGGING_STANDARD.md` | `LOG` → `logging.sh` | 10 | 13 | 30/30 | mechanical |
-| `docs/REST_API_DESIGN_GUIDELINES.md` | — | 0 | 0 | 0/67 | mechanical |
+| `docs/REST_API_DESIGN_GUIDELINES.md` | — | 0 | 0 | 0/69 | mechanical |
 | `docs/SCHEMA_CONVENTIONS.md` | — | 0 | 0 | 0/17 | mechanical |
 | `docs/DOCUMENTATION_RULES.md` | — | 0 | 0 | 0/22 | latent |
 | `docs/LIFECYCLE_PATTERNS.md` | — | 0 | 0 | 0/22 | mechanical |
 | `docs/CHANGELOG_VOICE.md` | — | 0 | 0 | 0/3 | latent |
 | `docs/VERIFY_TIERS.md` | — | 0 | 0 | 0/4 | uncited |
 | `docs/greptile-learnings/RULES.md` | — | 0 | 0 | 0/115 | mechanical |
-| **corpus** | | | | **30/280** | |
+| **corpus** | | | | **30/282** | |
 
 ## How to read this
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@agentsfleet/orly",
-  "version": "0.14.2",
+  "version": "0.14.3",
   "description": "Repository-scoped engineering harness: renders agent rules, materialises the gates that enforce them, and proves the PR boundary \u2014 for any coding agent.",
   "license": "MIT",
   "type": "module",