@geonosis/observability 1.0.0

package/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,333 @@
+# @geonosis/observability
+
+**Ports whose answer can say *failed*, a vocabulary that refuses a person as a tenant, and a probe
+that plants an error and goes and looks for it.**
+
+Extracted from during.day's PostHog sink and health endpoint, dielime's provider seam, and Midday's
+tiered health registry — after an afternoon in which four instruments reported green while measuring
+nothing (`docs/rules-backlog.md` #42). Zero runtime dependencies. Node ≥ 22 and workerd: every flush
+is explicit or returned as a promise the host can `waitUntil`, and no timer is ever left running.
+
+```bash
+pnpm add @geonosis/observability better-result
+pnpm add posthog-node      # only if you use the /posthog adapter
+```
+
+| Import | What is behind it |
+|---|---|
+| `@geonosis/observability` | the ports, the vocabulary, `createMemorySink`, `createSwallowingSink`, `createMemoryTracer`, `withDedupe`, `withLastEvent`, `proveObservability` |
+| `@geonosis/observability/health` | `createHealthRegistry` — tiers, TTL, timeouts, `ready()` vs `dependencies()` |
+| `@geonosis/observability/posthog` | `createPostHogSink` — the vendor is injected, never imported |
+| `geonosis-observability prove` | the CLI. Four verdicts, exit 0 or 2 |
+
+---
+
+## 1. The ports
+
+```ts
+type ErrorSink = {
+  capture: (error: Error, attributes: Attributes) => Promise<Result<CaptureReceipt, SinkFailure>>
+  flush: () => Promise<Result<void, SinkFailure>>
+  kind: string
+}
+
+type CaptureReceipt = { deduplicated: boolean; id: string }
+```
+
+`better-result` is a **required peer**: `Result` is in every return type, so you cannot call this
+package without it, and a second copy in a `dependencies` field would put two `Ok` classes in one
+tree.
+
+**Why not `Promise<number>`.** during.day's seam answers with a count: `events.length` from the real
+sink, `0` from the one with no key, a rejected promise from a dead transport — handed to
+`waitUntil`, where nothing reads it. A count cannot say *failed*. That is the shape `no-void-port`
+refuses, wearing a number instead of `void`.
+
+**Why the receipt carries an id.** React strips an error's message on the way to a browser; a deploy
+renames every stack frame. The id the sink filed the report under survives both, which is why it is
+in the answer rather than in a log line.
+
+```ts
+const receipt = await sink.capture(error, { envelopeId, service: 'api', tenant: orgId })
+if (receipt.isErr()) log.warn('the report did not land', receipt.error.sink, receipt.error.message)
+else response.headers.set('x-error-id', receipt.value.id)
+```
+
+### The tracer
+
+```ts
+tracer.span('queue.handle-batch', { service: 'api', tenant: orgId }, async () => doTheWork())
+```
+
+Returns whatever the body returned and rethrows whatever it threw. It is a recorder, not a gate: a
+tracer that swallowed a throw would make a failed request answer 200. Its own failures are its own
+business and never the caller's.
+
+**Span names** are `<area>.<action>`, lowercase, at least two dot-separated segments, dashes inside a
+segment: `queue.handle-batch`, `db.cell.query`, `http.request`. `isSpanName(name)` decides;
+`SPAN_NAME_CONVENTION` states it. Never enforced by a throw — a bad span name must not become a 500
+— so assert it in your own tests if you want it held.
+
+## 2. The vocabulary
+
+| Field | Meaning |
+|---|---|
+| `service` | **required.** A report nobody can route to a service is a report nobody reads. |
+| `tenant` | Always a **group id**, never a person. Refused if it contains `@`. |
+| `envelopeId` | The id this occurrence already has upstream. The dedupe key, and the id it is filed under. |
+| `runtime` | `node`, `workerd`, `browser`, a container id. An open string. |
+| `release` | Which build. |
+| `actor` | The one field that MAY carry an identity. |
+| `extra` | Anything else. May not shadow a field above. |
+
+`release` and `runtime` are here because **neither consumer attaches either**, and a production error
+that cannot be pinned to a deploy is the first of the four lying instruments.
+
+`tenant` refusing an `@` is the one rule that is not a shape check. A group id is the join key every
+dashboard fans out on, and the one field an erasure request cannot reach once an address is in it —
+and it is the mistake both repos would make first, because `distinctId` legitimately holds a person
+and the two fields sit one line apart.
+
+```ts
+import { parseAttributes, attributesSchema } from '@geonosis/observability'
+import { z } from 'zod'
+
+parseAttributes(value)      // → Result<Attributes, InvalidAttributes>, no zod anywhere
+attributesSchema(z)         // → the same rules, built over YOUR zod
+```
+
+Two doors, one set of rules. Both consumers run different zod versions (4.2.0, 4.4.3 and 4.5.4
+measured across the two trees), so this package imports none.
+
+## 3. The sinks
+
+```ts
+const sink = createMemorySink()      // a real implementation: what tests and the probe read
+const sink = createSwallowingSink()  // answers ok, keeps nothing — shipped so --prove can catch it
+```
+
+`createSwallowingSink` is during.day's `silentAnalyticsSink` with the `console.info` removed. It is
+here on purpose: it is what both consumers actually run whenever no key is set, and a probe that
+could not tell it from a real sink would prove nothing.
+
+### Dedupe
+
+```ts
+withDedupe(sink)                                  // an in-memory Map
+withDedupe(sink, { seen, remember })              // your store: a KV namespace, an audit table
+```
+
+At-least-once in, at-most-once counted. A repeat of a known `envelopeId` answers with the id the
+first capture was filed under and `deduplicated: true`, and the inner sink is not called. An
+envelope whose capture **failed** is not remembered — buying at-most-once by losing at-least-once
+would make one transport error permanent silence for that envelope.
+
+An attributes bag with no `envelopeId` always passes through: during.day mints a fresh uuid for a
+`request`-door failure precisely because it has none, and dropping the second of two would lose a
+real second failure.
+
+### The last-event file
+
+```ts
+withLastEvent(sink, (record) => writeFile('.geonosis/last-event.json', JSON.stringify(record)))
+```
+
+Writes `{ at, id, sink, release? }` after a capture the sink accepted — nothing for a refusal,
+nothing for a deduplicated repeat. This is the file `geonosis-doctor`'s `observability` check reads.
+The writer is injected because a file is a Node fact; on workerd the same record goes to KV.
+
+## 4. The PostHog adapter
+
+```ts
+import { PostHog } from 'posthog-node'
+import { createPostHogSink } from '@geonosis/observability/posthog'
+
+const sink = createPostHogSink({
+  newClient: (batchSize) =>
+    new PostHog(env.POSTHOG_API_KEY, {
+      host: env.POSTHOG_HOST,
+      flushAt: batchSize,
+      flushInterval: 0,   // no long-lived process to run a timer in
+    }),
+  groupName: 'organization',                          // default
+  identityOf: (a) => a.actor ?? `org:${a.tenant}`,    // during.day's
+})
+
+// in a worker
+ctx.waitUntil(sink.flushable().promise)
+```
+
+`posthog-node` is never imported here — you pass the constructor. That keeps this package at zero
+runtime dependencies, keeps your key and host out of it, and makes the whole adapter drivable
+against a stub server with no network.
+
+`flushable()` returns `{ pending, promise }`. Read `pending` before awaiting to skip the call when
+there is nothing to send; the promise **resolves**, never rejects, so a host handing it to
+`waitUntil` is not handed a rejection it never asked for. Read the `Result` if you want to know.
+
+**Two vendor behaviours this is built around**, both measured against `posthog-node@5.50.0`:
+
+1. **A `uuid` that is not a valid UUID is silently replaced.** during.day's ids are
+   `crypto.randomUUID()`, so its dedupe works; ids like `evt_7`, a ULID, a nanoid or a Medusa
+   `order_01H…` would be dedupe keys that never arrive. The adapter passes a UUID through untouched
+   and derives a **stable UUIDv5** from anything else — same envelope, same uuid, every process,
+   verified against CPython's `uuid5` — and puts the original on the wire as `properties.envelopeId`.
+2. **`shutdown()` resolves over a batch the server refused.** A 500 and a dead port both leave the
+   await resolving normally; the failure is reported only through an `on('error')` listener. The
+   adapter subscribes and turns what it hears into the `SinkFailure`.
+
+**The browser half is yours.** `posthog-js` is a bundler and framework fact — a key-gated, memoised
+dynamic `import('posthog-js')`, `identify(userId)` on sign-in, `group('organization', orgId)` so the
+browser session and the server events join on the same key. Use the same group name you passed here
+and the two halves meet; that is all this package can usefully say about it.
+
+## 5. `--prove`
+
+```bash
+geonosis-observability prove --sink memory
+geonosis-observability prove --sink posthog-stub
+geonosis-observability prove --sink posthog --verify-command 'my-posthog-query "$GEONOSIS_TRACE_ID"'
+```
+
+Plants an error under a trace id nothing else in the world has, then goes and LOOKS.
+
+| Verdict | Meaning | Exit |
+|---|---|---|
+| `PROVEN observability: the planted error reached <sink> as <trace id>` | found | 0 |
+| `CANNOT FAIL: the sink swallowed it` | answered ok, kept nothing | 2 |
+| `MISREAD: …` | kept something, but not the plant | 2 |
+| `CANNOT MEASURE: …` | nothing configured, a refused plant, or a failed flush | 2 |
+
+`--sink posthog` **refuses without `--verify-command`**. A key proves you can send; sending is not
+arriving, and "the SDK did not complain" is exactly the evidence that was found to be worthless.
+Nothing here queries anybody's project — your command runs with `GEONOSIS_TRACE_ID` in its
+environment and its exit code is the answer.
+
+Put your own sink behind the same four verdicts with the exported `proveObservability`:
+
+```ts
+const proof = await proveObservability({ probe: { kind, sink, seen: (id) => lookItUp(id) } })
+process.exit(exitCodeOf(proof))
+```
+
+## 6. The health contract
+
+```ts
+import { createHealthRegistry } from '@geonosis/observability/health'
+
+const health = createHealthRegistry({
+  dependencies: [
+    { name: 'cell', tier: 1, check: () => pingCell(db), timeoutMs: 2000, ttlMs: 5000 },
+    { name: 'controlPlane', tier: 1, check: () => pingControl(control), timeoutMs: 2000 },
+    { name: 'search', tier: 4, check: () => pingSearch(), timeoutMs: 1000, ttlMs: 30_000 },
+  ],
+})
+```
+
+`ready()` runs **tier 1 only** and answers `{ ok, status: 200 | 503, degraded, dependencies }`.
+`dependencies()` runs every tier; its `status` still follows tier 1, so a degraded search index does
+not take a pod out. A registry with no tier-1 dependency answers 503 — a 200 from a registry that
+verified nothing is the `/health` over an unreachable database, built out of an empty array.
+
+`timeoutMs` (5s default) makes a hang a failure with `timed out after Nms`, and the timer is cleared
+on the path where the check answered first. `ttlMs` caches a good answer and marks it
+`cached: true`; a failure is **never** cached, because a service reported dead for a minute after it
+recovered is worse than one nobody predicted.
+
+### Fixture — Hono
+
+```ts
+app.get('/health/ready', async (c) => {
+  const report = await health.ready()
+  return c.json(report, report.status)
+})
+
+app.get('/health/dependencies', async (c) => {
+  const report = await health.dependencies()
+  return c.json(report, report.status)
+})
+```
+
+### Fixture — Node `http`
+
+```ts
+createServer(async (request, response) => {
+  const report =
+    request.url === '/health/ready' ? await health.ready() : await health.dependencies()
+
+  response.writeHead(report.status, { 'content-type': 'application/json' })
+  response.end(JSON.stringify(report))
+})
+```
+
+Both are examples, not code this package ships: a health registry that depended on one server could
+not be used by the other.
+
+## 7. The doctor line
+
+`geonosis-doctor` gains an `observability` check when `geonosis.json` has a block:
+
+```json
+{
+  "observability": {
+    "sink": "posthog",
+    "endpoint": "https://eu.i.posthog.com",
+    "lastEventFile": ".geonosis/last-event.json",
+    "maxAgeSeconds": 3600,
+    "probe": "geonosis-observability prove --sink posthog-stub"
+  }
+}
+```
+
+It asks whether a sink is configured (a `memory`/`noop`/`swallowing` one is a WARN), whether the
+endpoint answers a HEAD, and whether an event arrived inside `maxAgeSeconds`. It reads the FILE
+`withLastEvent` wrote and **imports nothing of this package** — a check that needed the library it
+checks cannot run in the tree where the library is missing, which is the first case it exists to
+find. It names your `probe` command; it never runs it.
+
+---
+
+## Migrating during.day
+
+`apps/api/src/lib/posthog-mirror.ts` becomes a `createPostHogSink` instance plus `withDedupe`.
+
+| Today | With this package |
+|---|---|
+| `AnalyticsSink { capture: (events) => Promise<number> }` | `ErrorSink` returning `Result<CaptureReceipt, SinkFailure>` |
+| `distinctId: message.actor ?? \`org:${orgId}\`` | `identityOf: (a) => a.actor ?? \`org:${a.tenant}\`` — the `org:` prefix stays yours |
+| `groups: { organization: orgId }` | `tenant: orgId` + `groupName: 'organization'` (the default) |
+| `uuid: message.id` | `envelopeId: message.id` — already a UUID, so it goes on the wire unchanged |
+| `new PostHog(key, { flushAt: events.length, flushInterval: 0 })` per batch | your `newClient(batchSize)`, verbatim |
+| `context.waitUntil(analytics.capture(mirrored))` | `for (…) await sink.capture(…)`, then `context.waitUntil(sink.flushable().promise)` |
+| `await client.shutdown()` then `return events.length` | the `Result` — `shutdown()` resolving over a refused batch is why |
+| `silentAnalyticsSink` when no key | `createSwallowingSink()`, and `--prove` says `CANNOT FAIL` over it |
+| `handleQueue({ seen: (id) => hasAuditEntryForEvent(db, { eventId: id }) })` | keep it — and add `withDedupe(sink, { seen, remember })` for the counting |
+| `FailureDoor = 'cron' \| 'mail' \| 'queue' \| 'request' \| 'workflow'` | `extra: { door }` — the five values are a worker's, not a vocabulary's |
+| `failureEventFor` minting `crypto.randomUUID()` | leave `envelopeId` off; the sink mints one |
+| `healthStatus(version, probes)` | `createHealthRegistry`, with `cell` and `controlPlane` at tier 1 and a `timeoutMs` each |
+| one `/health` | `/health/ready` from `ready()`, `/health/dependencies` from `dependencies()` |
+| nothing | `release` and `runtime` on every capture, and a `probe` line in `geonosis.json` |
+
+`apps/web/lib/analytics/browser.ts` does not move. It is `posthog-js`, a bundler-visible env read and
+a dynamic import — all three are the app's. Keep `group('organization', orgId)` matching `groupName`.
+
+## Migrating dielime
+
+dielime has **no error sink and no health endpoint at all**. Its migration is adoption, not
+replacement, and its own best-shaped seam is the template:
+`packages/medusa-plugins/customer-service/src/lib/llm-provider.ts` resolves three ways
+(`anthropic` | `claude-cli` | `dev`) and its no-key path is a real deterministic implementation, not
+a null object.
+
+1. Put `createMemorySink()` behind that same shape — a resolver that returns the memory sink with no
+   key and a real adapter with one. dielime's no-key path is then readable, which
+   `silentAnalyticsSink` never was.
+2. `service` is the plugin or the app; `tenant` is nothing until it has one — leave it off rather
+   than putting a customer in it.
+3. Medusa entity ids (`order_01H…`) are **not** UUIDs. Pass them as `envelopeId` anyway: the adapter
+   derives a stable UUIDv5 and keeps the original as `properties.envelopeId`. Passing one straight to
+   `posthog-node` would lose the dedupe silently.
+4. `withDevFallback`'s `[dev-fallback]` marker is the same idea as `deduplicated: true` and the
+   `CANNOT FAIL` verdict — a run that did less than it looks like it did says so.
+5. There is no `/health` to migrate. Add `createHealthRegistry` with Postgres and Redis at tier 1
+   and the search provider at tier 3, and `--prove` in the gate.

package/bin/geonosis-observability.mjs

@@ -0,0 +1,4 @@
+#!/usr/bin/env node
+// Committed, so `pnpm install` can link the bin on a fresh clone — before `pnpm build` has
+// produced dist/. A bin that only exists after a build is a bin that is missing when you need it.
+import '../dist/observability-cli.js'