@volter/twin-sentry 0.1.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/LICENSE +202 -0
- package/README.md +142 -0
- package/client/sentry-mirror.css +99 -0
- package/client/sentry-mirror.tsx +352 -0
- package/dist/client/sentry-mirror.bundle.js +321 -0
- package/dist/client/sentry-mirror.css +99 -0
- package/dist/client/sentry-mirror.d.ts +17 -0
- package/dist/client/sentry-mirror.js +156 -0
- package/dist/client/sentry-mirror.tsx +352 -0
- package/dist/src/cli.d.ts +2 -0
- package/dist/src/cli.js +36 -0
- package/dist/src/index.d.ts +15 -0
- package/dist/src/index.js +75 -0
- package/dist/src/sentry-budget.d.ts +50 -0
- package/dist/src/sentry-budget.js +145 -0
- package/dist/src/sentry-capabilities.d.ts +3 -0
- package/dist/src/sentry-capabilities.js +1180 -0
- package/dist/src/sentry-conformance.d.ts +22 -0
- package/dist/src/sentry-conformance.js +97 -0
- package/dist/src/sentry-connector.d.ts +77 -0
- package/dist/src/sentry-connector.js +226 -0
- package/dist/src/sentry-events.d.ts +54 -0
- package/dist/src/sentry-events.js +131 -0
- package/dist/src/sentry-ingest.d.ts +137 -0
- package/dist/src/sentry-ingest.js +387 -0
- package/dist/src/sentry-mirror-ui.d.ts +38 -0
- package/dist/src/sentry-mirror-ui.js +162 -0
- package/dist/src/sentry-perform-harness.d.ts +9 -0
- package/dist/src/sentry-perform-harness.js +20 -0
- package/dist/src/sentry-server.d.ts +14 -0
- package/dist/src/sentry-server.js +27 -0
- package/dist/src/sentry-twin.d.ts +17 -0
- package/dist/src/sentry-twin.js +1739 -0
- package/dist/test-fixtures/sentry-openapi-operations.SOURCE.md +24 -0
- package/dist/test-fixtures/sentry-openapi-operations.json +1837 -0
- package/package.json +75 -0
- package/src/cli.ts +34 -0
- package/src/index.ts +145 -0
- package/src/sentry-budget.ts +171 -0
- package/src/sentry-capabilities.ts +1222 -0
- package/src/sentry-conformance.ts +110 -0
- package/src/sentry-connector.ts +260 -0
- package/src/sentry-events.ts +171 -0
- package/src/sentry-ingest.ts +471 -0
- package/src/sentry-mirror-ui.ts +162 -0
- package/src/sentry-perform-harness.ts +19 -0
- package/src/sentry-server.ts +35 -0
- package/src/sentry-twin.ts +1615 -0
- package/test-fixtures/sentry-openapi-operations.SOURCE.md +24 -0
- package/test-fixtures/sentry-openapi-operations.json +1837 -0
|
@@ -0,0 +1,24 @@
|
|
|
1
|
+
# sentry-openapi-operations.json — provenance
|
|
2
|
+
|
|
3
|
+
The operation-inventory denominator for `../sentry-spec-census.json`: a scope-filtered subset of
|
|
4
|
+
the vendor's published spec, enumerated by `deriveFromOpenAPI` (`packages/world-tooling/src/derive.ts`).
|
|
5
|
+
|
|
6
|
+
- **Upstream:** https://github.com/getsentry/sentry-api-schema — `openapi-derefed.json`
|
|
7
|
+
(raw: `https://raw.githubusercontent.com/getsentry/sentry-api-schema/main/openapi-derefed.json`, fetched 2026-09-02;
|
|
8
|
+
`info.version` `v0`, 140 paths / 227 operations).
|
|
9
|
+
- **How it was built:** `bun scripts/spec-census-bootstrap.ts --vendor sentry --from-file <openapi-derefed.json> --scope-paths /api/0/organizations/,/api/0/projects/,/api/0/teams/,/api/0/issues/ --apply`
|
|
10
|
+
over a copy of the upstream file fetched 2026-09-02; operation metadata only (operationId, summary, tags), schemas and response codes dropped. The gate never fetches — refreshing the fixture is
|
|
11
|
+
`bun scripts/spec-refresh.ts --vendor sentry --from-file <newer spec> --apply` over a newly fetched copy.
|
|
12
|
+
- **Scope (221 of 227 upstream operations):** every operation whose path starts with one of
|
|
13
|
+
`/api/0/organizations/`, `/api/0/projects/`, `/api/0/teams/`, `/api/0/issues/`.
|
|
14
|
+
- **Mapping (after the hand review):** 66 operations mapped to capability ids, 36 ruled `$ruled` in the census
|
|
15
|
+
against the deeper-engine todos the manifest files (`sentry.replay.segment_ingest`, `sentry.performance.profiling`,
|
|
16
|
+
`sentry.crons.monitors`, `sentry.events.symbolication`, `sentry.performance.span_aggregation` in
|
|
17
|
+
`src/sentry-capabilities.ts`), and 119 left `unmapped` (the ratchet baseline): surfaces the twin does
|
|
18
|
+
not route, chiefly the ORG-SCOPED issues resource this spec moved under `/organizations/{org}/issues/`
|
|
19
|
+
(the twin still serves the legacy top-level `/api/0/issues/{id}/` family, which this spec no longer
|
|
20
|
+
documents) and Sentry's new workflows/detectors automation model (the twin serves the legacy
|
|
21
|
+
`/rules/` + `/alert-rules/` surface instead). The birth mapping was 120 capability / 101 unmapped; the
|
|
22
|
+
hand review corrected 112 entries (the bootstrap is blind to the `orgs` ↔ `organizations`
|
|
23
|
+
abbreviation, and mapped many unrouted sub-paths onto their parent resource's id). Every later ruling
|
|
24
|
+
(a `$ruled` marker, a remap) is an edit to the census, never to this fixture.
|