Cursor plugin specification and official plugins
TypeScript
Point at the Origin docs instead of restating them
Cursor Agent3992065c0c8a
diff --git a/origin-apps/README.md b/origin-apps/README.mdindex c9955bf5..52a45a3f 100644--- a/origin-apps/README.md+++ b/origin-apps/README.md@@ -8,14 +8,12 @@ reads [Agent Skills](https://agentskills.io).## What it includes-`origin-api` is the general skill. It lists the sources to fetch first (the-live OpenAPI spec and docs are the only source for endpoints, scopes, and-event slugs) and then the Origin rules that GitHub habits get wrong. Native-versus mirrored repositories. Opt-in webhook events. `v1ed` signatures.-`deliveryId` idempotency. Lean payloads. Credential kinds and token minting.-Scopes from `x-origin-scopes`. Opaque page tokens. TypeIDs. `404` semantics.-Rate limits. The differences from GitHub that are decisions, not gaps. Use it-for any Origin work.+`origin-api` is the general skill. It sends the agent to the live OpenAPI+spec and docs for every fact, gives a table of which docs section answers+which question, and names the four rules to check first (native versus+mirrored repositories, event subscriptions, webhook verification, scopes+from the spec) plus the GitHub features Origin does not have. Use it for any+Origin work.`port-github-app-to-origin` builds on `origin-api`. Run it inside your GitHubApp's repository. It reads what the app uses from GitHub out of the code, maps@@ -88,8 +86,8 @@ mkdir -p .cursor/skills && cp -r plugins/origin-apps/skills/* .cursor/skills/## Where the brief goesThe porting skill writes `ORIGIN-PORTING-BRIEF.md` at the repository root and-prints its path. The gap cards in the brief are yours to send, through your-shared Slack channel with Cursor if you have one, or to `[email protected]`.+prints its path. The gap cards in the brief are yours to send through+whatever contact route you have with Cursor.## Licensediff --git a/origin-apps/skills/origin-api/SKILL.md b/origin-apps/skills/origin-api/SKILL.mdindex e139d265..bfa17d3a 100644--- a/origin-apps/skills/origin-api/SKILL.md+++ b/origin-apps/skills/origin-api/SKILL.md@@ -2,10 +2,11 @@name: origin-apidescription: >-Guides building on the Cursor Origin API: creating an Origin App,- authenticating as it, calling the REST API, receiving webhooks. Use whenever code or a plan touches- Origin endpoints, installation tokens, scopes, webhook subscriptions or- signatures, page tokens, or an Origin App manifest. Lists the sources to- fetch first and the Origin rules that GitHub habits get wrong.+ authenticating as it, calling the REST API, receiving webhooks. Use whenever+ code or a plan touches Origin endpoints, installation tokens, scopes, webhook+ subscriptions or signatures, page tokens, or an Origin App manifest. Points+ at the docs section that answers each question and names the few rules that+ GitHub habits get wrong.license: MITcompatibility: >-Needs network access to https://cursor.com/docs/api/origin/* at run time.@@ -13,73 +14,72 @@ compatibility: >-# Build on the Origin API-## Fetch first. Never name an endpoint, scope, slug, or header from memory.+The docs are the only source of truth. This skill tells you where to look and+which rules to check first. It restates nothing you can read there.-- `https://cursor.com/docs/api/origin/openapi.yaml` is the contract. Every- operation carries `x-origin-scopes` (`scopes`, `tokenTypes`, `ambient`).- Every webhook payload schema carries `x-origin-webhook-events`, the only- authoritative list of subscribable slugs.-- `https://cursor.com/docs/api/origin/llms-full.txt` covers the installation- flow, authentication, the scopes table, mirrored repositories, webhook- headers and verification, the delivery envelope, retries, pagination,- errors, and current limitations.-- `https://cursor.com/docs/api/origin/llms.txt` is the index.- `https://cursor.com/docs/api/origin/changelog` says what moved.+## Fetch first. Never name an endpoint, scope, slug, header, or limit from memory.++- `https://cursor.com/docs/api/origin/openapi.yaml`: the contract. Every+ operation carries `x-origin-scopes`; every webhook payload schema carries+ `x-origin-webhook-events`, the list of slugs that deliver it.+- `https://cursor.com/docs/api/origin/llms-full.txt`: the prose reference.+ Anchors below are sections of this file.+- `https://cursor.com/docs/api/origin/llms.txt` (index) and+ `https://cursor.com/docs/api/origin/changelog` (what moved).Cite `operationId`s and `llms-full.txt` anchors. If this file and the fetcheddocs disagree, the docs win.-## Rules GitHub habits get wrong+## Where to look++| Question | Section of `llms-full.txt` |+| --- | --- |+| Which credential for which call; how to mint and how long it lives | `#authentication` through `#git-https-authentication` |+| Install flow and the callback receipt | `#installation`, `#installation-receipt` |+| Which scope an operation needs | `x-origin-scopes` on the operation; `#scopes` for the table and the rules |+| What an installation can do on a mirrored repository | `#mirrored-repositories` |+| Webhook headers, signature, envelope, retries, pausing, recovery | `#webhooks` and its subsections |+| Which events exist and which are delivered without subscribing | `#events` |+| Payload shapes | `#event-payloads` and the schema's `x-origin-webhook-events` |+| Pagination, errors, request IDs, repository paths, ID form | `#common-conventions` |+| Rate limits and headers | `#rate-limits` |+| Check-run keys, attempts, stale writes | `#check-runs` |+| What is not there yet | `#current-limitations` |+| A checklist to build against | `#implementation-checklist` |++## Rules to check first++In priority order. Each is one line in the docs; getting it wrong costs a+week.++1. **Native or mirror.** Confirm the target repositories are Origin-native+ or stable outbound mirrors before anything else. On any other mirror+ state an installation can only read, and pushes are not delivered+ (`#mirrored-repositories`, `#events`).+2. **Subscribe.** Only the `installation.*` events arrive without a+ subscription. Select every other event the app needs; a missing+ subscription is silence, not an error (`#events`).+3. **Verify, dedupe, acknowledge.** Verify the signature over the raw body+ before parsing, dedupe on the delivery ID, return `2xx`, then process+ (`#signature-verification`, `#retries`, `#automatic-disable`). The digest+ step differs from the Standard Webhooks spec, so do not assume a generic+ verifier passes.+4. **Scopes from the spec.** Request the union of `x-origin-scopes.scopes`+ over the operations the app calls, and nothing else (`#scopes`).++## Coming from GitHub++Origin does not have these. Build the Origin idiom instead of emulating the+GitHub one. Until the docs carry this list, it lives here:-- **Check native or mirror before anything else.** Apps get full scopes only- on Origin-native repositories. A repository mirrored from GitHub returns- `403` on every write and never delivers `repository.pushed`. The ping- succeeds and then nothing else arrives.-- **Only installation lifecycle events are delivered by default.** Select- every other event in app settings. An unselected event is silence, not an- error.-- **Signature `v1ed` is Ed25519 over a SHA-256 digest of the raw body**, with- keys from Origin's JWKS. It matches Standard Webhooks except for the digest,- so off-the-shelf verifiers fail unmodified. Verify the raw body before- parsing. Reject `webhook-timestamp` more than five minutes off. Headers are- `webhook-*`, not `x-github-*`. After verification the body is authoritative.-- **`deliveryId` is the idempotency key.** It is stable across retries.- `event.id` identifies the domain event. Return `2xx` after verification and- process asynchronously, because persistent failure pauses delivery for the- app.-- **Payloads are lean snapshots** of the one object that changed, plus- references to its containers. No changed-file lists, before-SHAs, web URLs,- or inlined profiles. Follow up with the `Get…` for the object and count the- fan-out. The action is in the slug (`pull_request.review.submitted`). There- is no `action` field.-- **The installation receipt JWT proves consent. It is never a Bearer token.**- Its `sub` is the installation ID.-- **The app JWT is EdDSA over Ed25519, not RS256.** Register only the public- key.-- **Installation tokens are short-lived. Mint them just in time** from the- app JWT and attenuate to the scopes and `repositoryIds` the job needs (IDs,- not slugs). Git over HTTPS uses Basic auth with user `x-access-token` and- the token as password. Bearer is REST only.-- **Scopes come from the operations you call.** Request the union of their- `x-origin-scopes.scopes`. `write` implies `read`. `repository:metadata:read`- is automatic. `ambient: true` needs no request. Operations whose- `tokenTypes` is user-only (create app, add repositories to an installation,- mirror transitions) have no app-side path, and there is no `/user` analog.-- **Page tokens are opaque and bound to the resource and filters.** Never- construct, parse, or reuse one across filter changes. Send `pageSize` on- every request, including continuations. There is no `Link` header and no- total.-- **IDs are TypeIDs** (`repo_…`, `i_…`, `cmt_…`), never integers. Cache IDs,- not slugs. `/repos/_/{repoId}` survives renames. 64-bit integers (pull- request numbers, versions) are JSON strings. Defaults are present (`false`, `0`,- `[]`), so a present `false` is a value.-- **`404` means not found or no access.** Branch on status and `code`, never- on message text. Quote `X-Request-ID` when escalating.-- **The rate limit is a per-principal point budget.** Honor `Retry-After` on- `429`. Git HTTPS is metered separately. Cursor raises per-app budgets on- request.-- **These are decisions, not gaps.** No commit statuses (check runs upsert on- a caller-stable `key`). No Issues (conversation is pull request comments, threads,- reviews, and labels). No GraphQL. No per-repository webhook CRUD. No user or- email directory. Reviews anchor to a pull request version, not a SHA. A- thread materializes from its first diff-anchored comment.+- Issues. Conversation is pull request comments, threads, reviews, labels.+- Commit statuses. Check runs with a stable `key` (`#check-runs`).+- GraphQL. REST only.+- Per-repository webhook CRUD. Subscriptions are app settings.+- User, email, team, or member directory. Actors are IDs, plus a handle+ where the payload exposes one.+- `/user`-style flows. Discover repositories through the installation.+- Reviews keyed by commit SHA. Reviews reference a pull request version.+- Numeric IDs and page numbers. IDs and page tokens are opaque strings; do+ not parse or construct them, and cache repository IDs rather than slugs+ (`#repository-paths`, `#pagination`).diff --git a/origin-apps/skills/port-github-app-to-origin/references/brief-template.md b/origin-apps/skills/port-github-app-to-origin/references/brief-template.mdindex 5f893c11..876fb506 100644--- a/origin-apps/skills/port-github-app-to-origin/references/brief-template.md+++ b/origin-apps/skills/port-github-app-to-origin/references/brief-template.md@@ -109,24 +109,22 @@ fields read only for logging.## 5. Hello-world path-The shortest route to one real event from one native repository. Each step-is a verification, linked to `llms-full.txt`. Append one step for each-spec-silent behavior the brief depends on, stated as the observation to make.--1. Create the app, register the Ed25519 public key, and set the webhook URL- and callback.-2. Select every repository event from § 3 in app settings.-3. Install on an Origin-native repository. Verify the receipt JWT and read- the installation ID from `sub`.-4. Mint an app JWT, exchange it for an installation token, and confirm the- repository is listed with the mirror state § 2 expects.-5. Verify the ping (`v1ed` over the raw body, timestamp skew, `deliveryId`- dedupe).-6. Perform the smallest action in § 3 and confirm the slug and the § 4- fields arrive. If the ping arrived and this did not, re-check steps 2 and- 3 first.-7. Smallest write from § 3 (check run with a stable `key`, pull request comment),- confirming its scope is in the grant.+The shortest route to one real event from one native repository. The+mechanics are in `llms-full.txt#implementation-checklist` and the sections it+links; this list is the observations to make, in order. Append one step for+each spec-silent behavior the brief depends on.++1. App created, signing key registered, webhook URL and callback set.+2. Every repository event from § 3 selected in app settings.+3. Installed on an Origin-native repository; receipt verified; installation+ ID recorded.+4. Installation token minted; the repository appears in the installation's+ repositories with the mirror state § 2 expects.+5. Ping received and verified; a retried delivery is deduplicated.+6. Smallest action in § 3 performed; the expected slug and the § 4 fields+ arrive. If the ping arrived and this did not, re-check steps 2 and 3+ first.+7. Smallest write from § 3 succeeds with the scopes from the § 3 line.## 6. Gaps worth raisingdiff --git a/origin-apps/skills/port-github-app-to-origin/references/gap-bar.md b/origin-apps/skills/port-github-app-to-origin/references/gap-bar.mdindex 578d20eb..64eb3f17 100644--- a/origin-apps/skills/port-github-app-to-origin/references/gap-bar.md+++ b/origin-apps/skills/port-github-app-to-origin/references/gap-bar.md@@ -33,8 +33,9 @@ At least one must hold. Quote it on the card.live spec before writing any card.- A concept the Origin docs never mention (Marketplace billing, merge queues,Actions, Projects). That is `unknown` plus a question.-- A GitHub Search query. The idiom is a list operation with its filters plus a- client-side predicate. A sorted list read that stops at a cutoff costs+- A GitHub Search query, when the spec has no search operation for that+ resource. The idiom is a list operation with its filters plus a client-side+ predicate. A sorted list read that stops at a cutoff costsproportional to the matches, not the collection. If that count fails thebar, the card is about a filter, never about search.@@ -67,9 +68,8 @@ can act without a call.```Do not propose scope, field, or route names. Do not batch unrelated-capabilities. Do not send cards yourself. The team decides-what goes out, through their shared Slack channel with Cursor or to-`[email protected]` with "Origin API" and the app name in the subject, quoting the-spec version and any `X-Request-ID` from failed calls. "This is by design,-here is the idiom" is a fine answer. It goes back into the brief as-`by-design-absent`.+capabilities. Do not send cards yourself. The team decides what goes out,+through whatever contact route they have with Cursor, quoting the spec+version and any request ID from failed calls (`llms-full.txt#errors`). "This+is by design, here is the idiom" is a fine answer. It goes back into the+brief as `by-design-absent`.diff --git a/origin-apps/skills/port-github-app-to-origin/references/origin-isms.md b/origin-apps/skills/port-github-app-to-origin/references/origin-isms.mdindex 3bbda21a..3342bdfd 100644--- a/origin-apps/skills/port-github-app-to-origin/references/origin-isms.md+++ b/origin-apps/skills/port-github-app-to-origin/references/origin-isms.md@@ -2,35 +2,37 @@Check here before labeling anything `gap`. A row below is `by-design-absent`or `reshaped`. The brief points at the idiom and never files a card. The-`origin-api` skill carries the reasoning. This table carries only the label-and the idiom. Confirm current wording in `llms-full.txt`.+third column says where the Origin answer lives: an anchor in+`llms-full.txt`, or "Coming from GitHub" in the `origin-api` skill for items+the docs do not yet carry. Read the source; do not copy this table into the+brief.-| GitHub call, event, or permission | Label | Origin idiom |+| GitHub call, event, or permission | Label | Where the Origin answer lives || --- | --- | --- |-| Acting on a repository mirrored *from* GitHub (writes, `push` events) | `by-design-absent` | Install on Origin-native repositories or stable outbound mirrors. Mirrors are read-only to apps and deliver no `repository.pushed`. First question of every brief. |-| Install callback with `installation_id` + `setup_action` query params | `reshaped` | Signed installation receipt JWT; `sub` is the installation ID. Not a Bearer. |-| RS256 app JWT | `reshaped` | EdDSA over Ed25519; register the public key. |-| `ghs_` installation tokens, long cache | `reshaped` | `oit_…`, short-lived, minted just in time, attenuable to scopes and `repositoryIds`. |-| User OAuth: `/user`, `/user/installations`, `/user/repos`, install-by-user picker | `by-design-absent` | Repository discovery is `/installation/repos`. App creation and installation-repository changes are admin actions with a user credential, not app calls. Ask what the flow should do. |-| Permissions `<noun>: read\|write` | `reshaped` | Scopes `repository:<noun>[:<sub>]:<read\|write>` taken from `x-origin-scopes` of the called operations. |-| Numeric IDs, `/repositories/{id}` | `reshaped` | TypeIDs; `/repos/_/{repoId}`. |-| `Link` / `page` / `per_page` pagination, total counts | `reshaped` | `pageSize` / `pageToken` / `nextPageToken`; opaque; no total. |-| GraphQL | `by-design-absent` | REST; decompose and count the fan-out. |-| Commit statuses (`statuses` permission, `POST /statuses/{sha}`) | `reshaped` | Check runs upserting on a caller-stable `key`; rulesets bind on the key. |-| Issues (`issues` permission, `issues.*` events, `/issues/{n}` not on a pull request) | `by-design-absent` | Pull request comments, threads, reviews, and labels. Ask what the pull-request-scoped behavior should be. |-| `/issues/{n}/comments`, `/issues/{n}/labels` used on a pull request | `reshaped` | Same calls under `/pulls/{n}/…`. |-| Repository webhook CRUD (`/repos/…/hooks`) | `by-design-absent` | Subscriptions are app settings. |-| App-manifest conversion, OAuth-app token mints | `by-design-absent` | App creation form (accepts prefill params) or user-credential `CreateApp`. |-| Git Data API tree/blob writes | `by-design-absent` | Push over Git HTTPS with an installation token, or the documented commit-from-files and ref operations. |-| Standalone review-thread objects | `reshaped` | A thread materializes from its first diff-anchored comment and is addressable for resolve/reopen. |-| User, email, team, and member lookups | `by-design-absent` | Actors are TypeIDs (plus a handle where exposed). No directory. |-| Single `pull_request` event with `action` field, `previous_attributes` | `reshaped` | One slug per action (`pull_request.head_ref.pushed`); no `action` field, no delta. Confirm each slug in `x-origin-webhook-events`. |-| `x-github-*` headers, HMAC `x-hub-signature-256` | `reshaped` | `webhook-*` headers; `v1ed` Ed25519 over a SHA-256 digest, JWKS keys. |-| Fields GitHub inlines in payloads (changed files on push, before-SHA, `html_url`, `sender` profile) | `reshaped` | Follow-up `Get…`, `CompareCommits`, or `ListComparisonFiles` with identifiers the payload carries. Name the call for each field and count the fan-out. |-| Default delivery of all events after app creation | `reshaped` | Only installation lifecycle is default; select the rest. |-| Reviews keyed by `commit_id` | `reshaped` | Reviews anchor to a pull request version. |-| Finding own check runs / comments by actor | `reshaped` | Check runs by `key`; comments and reviews by a marker the app controls. |-| Requested-reviewer team pages, `created_via` | `by-design-absent` | Reviewers addressed by identifier only. |+| Writes or `push` events on a repository mirrored from GitHub | `by-design-absent` | `#mirrored-repositories`, `#events`. First question of every brief. |+| Install callback query parameters (`installation_id`, `setup_action`) | `reshaped` | `#installation-receipt` |+| RS256 app JWT | `reshaped` | `#app-jwt` |+| Long-lived installation tokens | `reshaped` | `#installation-access-token` |+| User OAuth, `/user`, `/user/installations`, install-by-user picker | `by-design-absent` | `#scopes` (user-credential operations); Coming from GitHub. Ask what the flow should do. |+| Permissions `<noun>: read\|write` | `reshaped` | `#scopes`; `x-origin-scopes` per operation |+| Numeric IDs, `/repositories/{id}` | `reshaped` | `#repository-paths` |+| `Link` / `page` / `per_page` pagination, total counts | `reshaped` | `#pagination` |+| GraphQL | `by-design-absent` | Coming from GitHub. Decompose and count the fan-out. |+| Commit statuses (`statuses` permission, `POST /statuses/{sha}`) | `reshaped` | `#check-runs`; Coming from GitHub |+| Issues (`issues` permission, `issues.*` events, `/issues/{n}` not on a pull request) | `by-design-absent` | Coming from GitHub. Ask what the pull-request-scoped behavior should be. |+| `/issues/{n}/comments`, `/issues/{n}/labels` used on a pull request | `reshaped` | Pull requests endpoint reference; same calls under `/pulls/{n}/…` |+| Repository webhook CRUD (`/repos/…/hooks`) | `by-design-absent` | Coming from GitHub; subscriptions are app settings (`#events`) |+| App-manifest conversion, OAuth-app token mints | `by-design-absent` | `#installation`, Create App in the endpoint reference |+| Git Data API tree/blob writes | `by-design-absent` | `#git-https-authentication`; Git data endpoint reference |+| Standalone review-thread objects | `reshaped` | `#current-limitations`; Pull requests endpoint reference |+| User, email, team, and member lookups | `by-design-absent` | `#resource-references`; Coming from GitHub |+| Single `pull_request` event with an `action` field, `previous_attributes` | `reshaped` | `#events`, `#event-payloads` |+| `x-github-*` headers, HMAC `x-hub-signature-256` | `reshaped` | `#headers`, `#signature-verification` |+| Payload inlines (changed files on push, before-SHA, `html_url`, `sender` profile) | `reshaped` | `#current-limitations`, `#resource-references`. Name the follow-up call per field and count the fan-out. |+| All events delivered after app creation | `reshaped` | `#events` |+| Reviews keyed by `commit_id` | `reshaped` | Coming from GitHub; `pullRequestVersion` in the review schema |+| Finding own check runs or comments by actor | `reshaped` | `#check-runs` (`key`); comments and reviews by a marker the app controls |+| Requested-reviewer team pages, `created_via` | `by-design-absent` | Pull requests endpoint reference (reviewers by identifier) |A feature that is not on this list and that the Origin docs never mention(Marketplace billing, merge queues, Actions, Pages, Projects) is `unknown`diff --git a/origin-apps/skills/port-github-app-to-origin/references/spec-mapping.md b/origin-apps/skills/port-github-app-to-origin/references/spec-mapping.mdindex 5c27442c..87851051 100644--- a/origin-apps/skills/port-github-app-to-origin/references/spec-mapping.md+++ b/origin-apps/skills/port-github-app-to-origin/references/spec-mapping.md@@ -5,28 +5,27 @@ table here. Build the index once. Every later step looks things up in it.## Extensions the spec carries-| Extension | Where | Meaning |+| Extension | Where | Use || --- | --- | --- |-| `x-origin-scopes` | every operation | `scopes` the operation requires. `tokenTypes` it accepts (`app`, `installation`, `user`). `ambient: true` means there is nothing to request. |-| `x-origin-webhook-events` | payload schemas | The slugs that deliver this payload shape. A schema carrying it is a webhook family. These slugs are the only authoritative event list. |-| `x-origin-webhook-resource` | some payload schemas | The REST component the payload embeds. When absent, infer it from `$ref`s. Pushes, deletions, and reviewer requests are event-native with no REST twin. |-| `x-cursor-visibility: PREVIEW` | some operations | Usable. The shape may move. Carry the badge into the brief as a `preview` suffix. |+| `x-origin-scopes` | every operation | The scope, credential, and ambient rules for that operation. Rules in `llms-full.txt#scopes`. |+| `x-origin-webhook-events` | payload schemas | The slugs that deliver this payload shape. A schema carrying it is a webhook family. Infer the embedded resource from its `$ref`s; some families (pushes, deletions, reviewer changes) have no REST twin. |+| `x-cursor-visibility` | some schema fields | A stability badge on a field. Carry it into the brief as a `preview` suffix on rows that read the field. |## Build the index1. **Operations and scopes**: `rg -B1 -A4 'x-origin-scopes:' openapi.yaml`- prints every `operationId` with its `scopes`, `tokenTypes`, and `ambient`- flag. From it, note the union of scopes with the operations that need- each, and separate installation-requestable scopes from ambient and- user-only ones. The user-only set tells you which GitHub flows have no- app-side equivalent. Read parameters and response components from the- spec when a rule below asks for them.+ prints every `operationId` with its scope block. From it, note the union+ of scopes with the operations that need each, and separate+ installation-requestable scopes from ambient and user-only ones+ (`llms-full.txt#scopes` explains the difference). The user-only set tells+ you which GitHub flows have no app-side equivalent. Read parameters and+ response components from the spec when a rule below asks for them.2. **Webhook events**: `rg -A3 'x-origin-webhook-events:' openapi.yaml` listsevery slug with its payload schema. `scripts/index-origin-spec.pyopenapi.yaml` prints each payload family with its fields and `$ref`sresolved two levels deep; `schema <Name>` does the same for one component.- From `llms-full.txt` § Webhooks, note which slugs are app-lifecycle- (always delivered) versus repository events (must be selected).+ From `llms-full.txt#events`, note which slugs are delivered without a+ subscription and which must be selected.3. **Resources**: component schemas returned by `Get…`/`List…`, with fieldnames, for "does the Origin object carry this field".@@ -39,17 +38,17 @@ match is a candidate, never a result.**REST calls**-1. Normalize the GitHub path to the same shape under `/v1/origin`- (`{owner}/{repo}` → `{ownerSlug}/{repoName}`, `{pull_number}` →- `{pullNumber}`; custom verbs are `:verb` suffixes such as- `…/contents:batchGet`).-2. Re-home GitHub's issue-flavored pull request calls: `/issues/{n}/comments` and- `/issues/{n}/labels` used *on a pull request* live under `/pulls/{n}/…`.- That is a path change, not a gap. When the code uses them on real issues,- see `origin-isms.md`.-3. Re-home `/app`, `/app/installations`, access-token minting, and- `/installation/repositories` under `/v1/origin/app…` and- `/v1/origin/installation/repos`; confirm `tokenTypes`. `/user`,+1. Look for the same resource path under the Origin base path+ (`llms-full.txt#repository-paths` gives the path shape). Most GitHub+ repository, pull request, check, label, branch, and commit paths have a+ direct or near-direct counterpart.+2. Re-home GitHub's issue-flavored pull request calls (`/issues/{n}/comments`,+ `/issues/{n}/labels` used *on a pull request*) to the pull request+ endpoints. That is a path change, not a gap. When the code uses them on+ real issues, see `origin-isms.md`.+3. Re-home app and installation calls (`/app`, `/app/installations`,+ access-token minting, `/installation/repositories`) to the Apps and+ installations endpoints and confirm the credential each accepts. `/user`,`/user/installations`, `/orgs/…`, `/search/…`, and `/repositories/{id}`have no path counterpart. Consult `origin-isms.md` before labeling them.4. Compare parameters as well as paths. A matching path that lacks a filter@@ -68,11 +67,10 @@ the operations the code calls and take the union of *their*(`statuses`, `issues`, `members`, `organization_*`, `pages`, `actions`,`workflows`, `deployments`) go through `origin-isms.md` first.-**Events → slugs.** Each GitHub `event` + `action` pair becomes a candidate-slug (`pull_request` plus `synchronize` becomes `pull_request.head_ref.pushed`).-Confirm it exists in the webhook index. A candidate that does not exist is-not an event on Origin. Check whether the state change is observable another-way before classifying it.+**Events → slugs.** Each GitHub `event` + `action` pair maps to at most one+slug in `llms-full.txt#events`; the action is part of the slug. A pair with+no slug is not an event on Origin. Check whether the state change is+observable another way before classifying it.**Payload fields → schema properties.** For each field path a handler reads,walk the mapped slug's payload schema and record one of four outcomes.