@openvtc/trust-tasks 0.27.3 → 0.27.5

package/src/git-ns/projection/show/0.3/payload.ts

@@ -0,0 +1,473 @@
+/**
+ * Generated by scripts/build-ts-bindings.mjs — DO NOT EDIT BY HAND.
+ * Source: specs/git-ns/projection/show/0.3/payload.schema.json
+ */
+
+import type { Did_GitNsV0_3 as Did, Ext, Resource_GitNsV0_6 as Resource, Right } from "../../../../_shared/components.js";
+
+
+/**
+ * A community administrator reads what the VTC has published (and what it still owes) to the Trust Registry for its git namespaces. The outer document members (id, type, issuer, recipient, issuedAt, expiresAt, proof) are owned by the framework — SPEC §6.3.
+ */
+export interface GitNamespacesShowTrustRegistryProjectionPayload {
+  /**
+   * Only published records on this resource or inside it. Absent: every resource.
+   */
+  resource?: Resource;
+  /**
+   * Opaque continuation token from a previous response's `nextCursor`. A consumer supplying a `cursor` MUST NOT also change `resource` from the request that produced it — start a fresh query instead.
+   */
+  cursor?: string;
+  /**
+   * Maximum published records to return in this page. A VTC clamps to 1..=500 (default 100).
+   */
+  limit?: number;
+  ext?: Ext;
+}
+/**
+ * What is published, and how far it is from what the VTC's records currently call for.
+ */
+export interface GitNamespacesShowTrustRegistryProjectionResponsePayload {
+  /**
+   * Whether this VTC can publish at all — a Trust Registry and its own publishing DID are configured. `false`: `published` is only what was last published before publishing was unconfigured, and `pendingChanges` still counts against the VTC's current records.
+   */
+  registryConfigured: boolean;
+  /**
+   * Records matching `resource`, as the VTC's own mirror of what it last published, ordered by `resource` then `action` then `entity`.
+   */
+  published: PublishedRow[];
+  /**
+   * Continuation token for the next page of `published`; pass it back as the request's `cursor`. Absent on the last page — never `null`.
+   */
+  nextCursor?: string;
+  /**
+   * How many records the next reconciliation pass will add, remove or replace to bring the registry into line with the VTC's current rights — across the whole VTC, regardless of `resource` or paging. Zero means the registry already matches.
+   */
+  pendingChanges: number;
+  ext?: Ext;
+}
+/**
+ * One record the VTC has published to the Trust Registry.
+ */
+export interface PublishedRow {
+  /**
+   * The DID the record is about — the right's subject.
+   */
+  entity: Did;
+  /**
+   * The TRQP action the record is published under.
+   */
+  action: Right;
+  resource: Resource;
+  context: Context;
+  /**
+   * When the VTC last wrote this record to the registry.
+   */
+  publishedAt: string;
+}
+/**
+ * The record's context as published: what the TRQP record has no member of its own for. Not itself governed by this specification — it is the projector's internal shape, carried through unchanged, and a consumer MUST treat unrecognised members as opaque rather than failing on them.
+ */
+export interface Context {
+  /**
+   * The Trust Task type URI the record was published under — this specification's framework constant for a recorded or implied right, or the fixed `git-trust/grant/0.1` URI for a role-derived one.
+   */
+  framework: string;
+  /**
+   * Present, and always `roleDerived`, exactly for a v0.1 `[hooks.git-trust] grant_on_role` tuple. Absent for a tuple sourced from a recorded or implied right.
+   */
+  origin?: "roleDerived";
+  /**
+   * When the underlying right took effect. Absent for a role-derived tuple, which has no grant time of its own.
+   */
+  activeFrom?: string;
+  /**
+   * When the underlying right expires. Absent: no expiry, or the longest of two merged sources' expiries once neither is absent.
+   */
+  activeTo?: string;
+  /**
+   * Present when this tuple publishes a right implied by another recorded right (a repository's `git.commit.sign` implied by its `git.repo.own`, or a namespace's implied rights). Names the right that implies it.
+   */
+  impliedBy?: Right;
+}
+
+/** Shared definitions this specification references, re-exported under the names it used to declare them with. */
+export type { Did, Ext, Resource, Right };
+
+/** Trust Task type URI. */
+export const TYPE_URI = "https://trusttasks.org/spec/git-ns/projection/show/0.3" as const;
+
+/** Stable alias for this specification's request payload shape. */
+export type Payload = GitNamespacesShowTrustRegistryProjectionPayload;
+
+/** Trust Task response type URI (request type URI + "#response"). */
+export const RESPONSE_TYPE_URI = "https://trusttasks.org/spec/git-ns/projection/show/0.3#response" as const;
+
+/** Stable alias for this specification's success-response payload shape. */
+export type Response = GitNamespacesShowTrustRegistryProjectionResponsePayload;
+
+/**
+ * This specification's payload schema, as a value.
+ *
+ * SPEC.md §7.2 item 2 is performed against this. It is shipped as data
+ * rather than only as a `.json` file because TypeScript types are erased
+ * at runtime: without a schema a consumer has nothing to validate, and
+ * every REQUIRED payload member is optional in practice. Cross-file
+ * `$ref`s are already inlined, so it needs no resolver.
+ */
+export const PAYLOAD_SCHEMA = {
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$id": "https://trusttasks.org/spec/git-ns/projection/show/0.3",
+  "title": "Git Namespaces — Show Trust Registry Projection — payload",
+  "description": "A community administrator reads what the VTC has published (and what it still owes) to the Trust Registry for its git namespaces. The outer document members (id, type, issuer, recipient, issuedAt, expiresAt, proof) are owned by the framework — SPEC §6.3.",
+  "type": "object",
+  "additionalProperties": false,
+  "properties": {
+    "resource": {
+      "$ref": "#/$defs/Resource",
+      "description": "Only published records on this resource or inside it. Absent: every resource."
+    },
+    "cursor": {
+      "type": "string",
+      "description": "Opaque continuation token from a previous response's `nextCursor`. A consumer supplying a `cursor` MUST NOT also change `resource` from the request that produced it — start a fresh query instead."
+    },
+    "limit": {
+      "type": "integer",
+      "minimum": 1,
+      "maximum": 500,
+      "description": "Maximum published records to return in this page. A VTC clamps to 1..=500 (default 100)."
+    },
+    "ext": {
+      "$ref": "#/$defs/Ext"
+    }
+  },
+  "$defs": {
+    "Context": {
+      "title": "Context",
+      "description": "The record's context as published: what the TRQP record has no member of its own for. Not itself governed by this specification — it is the projector's internal shape, carried through unchanged, and a consumer MUST treat unrecognised members as opaque rather than failing on them.",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "framework"
+      ],
+      "properties": {
+        "framework": {
+          "type": "string",
+          "minLength": 1,
+          "maxLength": 2048,
+          "description": "The Trust Task type URI the record was published under — this specification's framework constant for a recorded or implied right, or the fixed `git-trust/grant/0.1` URI for a role-derived one."
+        },
+        "origin": {
+          "type": "string",
+          "enum": [
+            "roleDerived"
+          ],
+          "description": "Present, and always `roleDerived`, exactly for a v0.1 `[hooks.git-trust] grant_on_role` tuple. Absent for a tuple sourced from a recorded or implied right."
+        },
+        "activeFrom": {
+          "type": "string",
+          "format": "date-time",
+          "description": "When the underlying right took effect. Absent for a role-derived tuple, which has no grant time of its own."
+        },
+        "activeTo": {
+          "type": "string",
+          "format": "date-time",
+          "description": "When the underlying right expires. Absent: no expiry, or the longest of two merged sources' expiries once neither is absent."
+        },
+        "impliedBy": {
+          "$ref": "#/$defs/Right",
+          "description": "Present when this tuple publishes a right implied by another recorded right (a repository's `git.commit.sign` implied by its `git.repo.own`, or a namespace's implied rights). Names the right that implies it."
+        }
+      }
+    },
+    "PublishedRow": {
+      "title": "PublishedRow",
+      "description": "One record the VTC has published to the Trust Registry.",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "entity",
+        "action",
+        "resource",
+        "context",
+        "publishedAt"
+      ],
+      "properties": {
+        "entity": {
+          "$ref": "#/$defs/Did",
+          "description": "The DID the record is about — the right's subject."
+        },
+        "action": {
+          "$ref": "#/$defs/Right",
+          "description": "The TRQP action the record is published under."
+        },
+        "resource": {
+          "$ref": "#/$defs/Resource"
+        },
+        "context": {
+          "$ref": "#/$defs/Context"
+        },
+        "publishedAt": {
+          "type": "string",
+          "format": "date-time",
+          "description": "When the VTC last wrote this record to the registry."
+        }
+      }
+    },
+    "Response": {
+      "$anchor": "response",
+      "title": "Git Namespaces — Show Trust Registry Projection — response payload",
+      "description": "What is published, and how far it is from what the VTC's records currently call for.",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "registryConfigured",
+        "published",
+        "pendingChanges"
+      ],
+      "properties": {
+        "registryConfigured": {
+          "type": "boolean",
+          "description": "Whether this VTC can publish at all — a Trust Registry and its own publishing DID are configured. `false`: `published` is only what was last published before publishing was unconfigured, and `pendingChanges` still counts against the VTC's current records."
+        },
+        "published": {
+          "type": "array",
+          "items": {
+            "$ref": "#/$defs/PublishedRow"
+          },
+          "description": "Records matching `resource`, as the VTC's own mirror of what it last published, ordered by `resource` then `action` then `entity`."
+        },
+        "nextCursor": {
+          "type": "string",
+          "description": "Continuation token for the next page of `published`; pass it back as the request's `cursor`. Absent on the last page — never `null`."
+        },
+        "pendingChanges": {
+          "type": "integer",
+          "minimum": 0,
+          "description": "How many records the next reconciliation pass will add, remove or replace to bring the registry into line with the VTC's current rights — across the whole VTC, regardless of `resource` or paging. Zero means the registry already matches."
+        },
+        "ext": {
+          "$ref": "#/$defs/Ext"
+        }
+      }
+    },
+    "Ext": {
+      "title": "Ext",
+      "description": "Vendor-namespaced extension object per SPEC.md §4.5.1. Each immediate key MUST be a reverse-DNS namespace; structure under each namespace is opaque to the framework.",
+      "type": "object",
+      "minProperties": 1,
+      "additionalProperties": true,
+      "propertyNames": {
+        "pattern": "^[a-z][a-z0-9-]*(\\.[a-z0-9-]+)+$"
+      }
+    },
+    "Resource": {
+      "title": "Resource",
+      "description": "A forge-qualified resource, all lowercase: `<forge-host>/<owner>` for a namespace, or `<forge-host>/<owner>/<repo-path>` for one repository — `github.com/acme`, `github.com/acme/widgets`, `codeberg.org/acme`. On a forge with nested groups (GitLab) the repository path holds the subgroups between the top-level owner and the project: `gitlab.com/acme/platform/tools/cli` is one repository of the namespace `gitlab.com/acme`, and a subgroup such as `gitlab.com/acme/platform` is not a resource. A repository path has 1 to 21 segments (GitLab: 20 levels of subgroup and the project); GitHub and Forgejo repository paths are always one. The forge is never implied: `acme/widgets` alone is not a resource. Containment is by whole segment: `github.com/acme` contains `github.com/acme/widgets` and does not contain `github.com/acme-labs/x` or `codeberg.org/acme/widgets`.",
+      "type": "string",
+      "maxLength": 5885,
+      "pattern": "^[a-z0-9](?:[a-z0-9-]*[a-z0-9])?(?:\\.[a-z0-9](?:[a-z0-9-]*[a-z0-9])?)+/[a-z0-9_-][a-z0-9._-]{0,254}(?:/[a-z0-9_-][a-z0-9._-]{0,254}){0,21}$"
+    },
+    "Right": {
+      "title": "Right",
+      "description": "One of the five git rights. Each string is also the TRQP `action` the VTC publishes the right under in its Trust Registry, so it is carried verbatim. `git.ns.admin` and `git.repo.create` apply to a namespace resource; `git.repo.own` and `git.repo.maintain` to a repository resource; `git.commit.sign` to either.",
+      "type": "string",
+      "enum": [
+        "git.ns.admin",
+        "git.repo.create",
+        "git.repo.own",
+        "git.repo.maintain",
+        "git.commit.sign"
+      ]
+    },
+    "Did": {
+      "title": "Did",
+      "description": "A bare DID in the W3C DID Core syntax (§3.1): `did:`, a method name of lowercase letters and digits, `:`, and a method-specific id of colon-separated segments drawn from `A-Z a-z 0-9 . - _` and percent-encoded octets, the last segment non-empty. A DID URL is not a DID: no path, query or fragment (`/`, `?`, `#`), so a verification-method id such as `did:key:z6Mk…#z6Mk…` is refused. Compared by exact string equality — no case folding or percent-decoding. A consumer MUST still treat the value as data: the pattern keeps shell metacharacters, whitespace and quotes out of the wire form, but it does not make a DID safe to splice into a command or markup.",
+      "type": "string",
+      "maxLength": 2048,
+      "pattern": "^did:[a-z0-9]+:(?:(?:[A-Za-z0-9._-]|%[0-9A-Fa-f]{2})*:)*(?:[A-Za-z0-9._-]|%[0-9A-Fa-f]{2})+$"
+    }
+  }
+} as const;
+
+/** As {@link PAYLOAD_SCHEMA}, for the success-response variant. */
+export const RESPONSE_PAYLOAD_SCHEMA = {
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$ref": "#/$defs/Response",
+  "$defs": {
+    "Context": {
+      "title": "Context",
+      "description": "The record's context as published: what the TRQP record has no member of its own for. Not itself governed by this specification — it is the projector's internal shape, carried through unchanged, and a consumer MUST treat unrecognised members as opaque rather than failing on them.",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "framework"
+      ],
+      "properties": {
+        "framework": {
+          "type": "string",
+          "minLength": 1,
+          "maxLength": 2048,
+          "description": "The Trust Task type URI the record was published under — this specification's framework constant for a recorded or implied right, or the fixed `git-trust/grant/0.1` URI for a role-derived one."
+        },
+        "origin": {
+          "type": "string",
+          "enum": [
+            "roleDerived"
+          ],
+          "description": "Present, and always `roleDerived`, exactly for a v0.1 `[hooks.git-trust] grant_on_role` tuple. Absent for a tuple sourced from a recorded or implied right."
+        },
+        "activeFrom": {
+          "type": "string",
+          "format": "date-time",
+          "description": "When the underlying right took effect. Absent for a role-derived tuple, which has no grant time of its own."
+        },
+        "activeTo": {
+          "type": "string",
+          "format": "date-time",
+          "description": "When the underlying right expires. Absent: no expiry, or the longest of two merged sources' expiries once neither is absent."
+        },
+        "impliedBy": {
+          "$ref": "#/$defs/Right",
+          "description": "Present when this tuple publishes a right implied by another recorded right (a repository's `git.commit.sign` implied by its `git.repo.own`, or a namespace's implied rights). Names the right that implies it."
+        }
+      }
+    },
+    "PublishedRow": {
+      "title": "PublishedRow",
+      "description": "One record the VTC has published to the Trust Registry.",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "entity",
+        "action",
+        "resource",
+        "context",
+        "publishedAt"
+      ],
+      "properties": {
+        "entity": {
+          "$ref": "#/$defs/Did",
+          "description": "The DID the record is about — the right's subject."
+        },
+        "action": {
+          "$ref": "#/$defs/Right",
+          "description": "The TRQP action the record is published under."
+        },
+        "resource": {
+          "$ref": "#/$defs/Resource"
+        },
+        "context": {
+          "$ref": "#/$defs/Context"
+        },
+        "publishedAt": {
+          "type": "string",
+          "format": "date-time",
+          "description": "When the VTC last wrote this record to the registry."
+        }
+      }
+    },
+    "Response": {
+      "$anchor": "response",
+      "title": "Git Namespaces — Show Trust Registry Projection — response payload",
+      "description": "What is published, and how far it is from what the VTC's records currently call for.",
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "registryConfigured",
+        "published",
+        "pendingChanges"
+      ],
+      "properties": {
+        "registryConfigured": {
+          "type": "boolean",
+          "description": "Whether this VTC can publish at all — a Trust Registry and its own publishing DID are configured. `false`: `published` is only what was last published before publishing was unconfigured, and `pendingChanges` still counts against the VTC's current records."
+        },
+        "published": {
+          "type": "array",
+          "items": {
+            "$ref": "#/$defs/PublishedRow"
+          },
+          "description": "Records matching `resource`, as the VTC's own mirror of what it last published, ordered by `resource` then `action` then `entity`."
+        },
+        "nextCursor": {
+          "type": "string",
+          "description": "Continuation token for the next page of `published`; pass it back as the request's `cursor`. Absent on the last page — never `null`."
+        },
+        "pendingChanges": {
+          "type": "integer",
+          "minimum": 0,
+          "description": "How many records the next reconciliation pass will add, remove or replace to bring the registry into line with the VTC's current rights — across the whole VTC, regardless of `resource` or paging. Zero means the registry already matches."
+        },
+        "ext": {
+          "$ref": "#/$defs/Ext"
+        }
+      }
+    },
+    "Ext": {
+      "title": "Ext",
+      "description": "Vendor-namespaced extension object per SPEC.md §4.5.1. Each immediate key MUST be a reverse-DNS namespace; structure under each namespace is opaque to the framework.",
+      "type": "object",
+      "minProperties": 1,
+      "additionalProperties": true,
+      "propertyNames": {
+        "pattern": "^[a-z][a-z0-9-]*(\\.[a-z0-9-]+)+$"
+      }
+    },
+    "Resource": {
+      "title": "Resource",
+      "description": "A forge-qualified resource, all lowercase: `<forge-host>/<owner>` for a namespace, or `<forge-host>/<owner>/<repo-path>` for one repository — `github.com/acme`, `github.com/acme/widgets`, `codeberg.org/acme`. On a forge with nested groups (GitLab) the repository path holds the subgroups between the top-level owner and the project: `gitlab.com/acme/platform/tools/cli` is one repository of the namespace `gitlab.com/acme`, and a subgroup such as `gitlab.com/acme/platform` is not a resource. A repository path has 1 to 21 segments (GitLab: 20 levels of subgroup and the project); GitHub and Forgejo repository paths are always one. The forge is never implied: `acme/widgets` alone is not a resource. Containment is by whole segment: `github.com/acme` contains `github.com/acme/widgets` and does not contain `github.com/acme-labs/x` or `codeberg.org/acme/widgets`.",
+      "type": "string",
+      "maxLength": 5885,
+      "pattern": "^[a-z0-9](?:[a-z0-9-]*[a-z0-9])?(?:\\.[a-z0-9](?:[a-z0-9-]*[a-z0-9])?)+/[a-z0-9_-][a-z0-9._-]{0,254}(?:/[a-z0-9_-][a-z0-9._-]{0,254}){0,21}$"
+    },
+    "Right": {
+      "title": "Right",
+      "description": "One of the five git rights. Each string is also the TRQP `action` the VTC publishes the right under in its Trust Registry, so it is carried verbatim. `git.ns.admin` and `git.repo.create` apply to a namespace resource; `git.repo.own` and `git.repo.maintain` to a repository resource; `git.commit.sign` to either.",
+      "type": "string",
+      "enum": [
+        "git.ns.admin",
+        "git.repo.create",
+        "git.repo.own",
+        "git.repo.maintain",
+        "git.commit.sign"
+      ]
+    },
+    "Did": {
+      "title": "Did",
+      "description": "A bare DID in the W3C DID Core syntax (§3.1): `did:`, a method name of lowercase letters and digits, `:`, and a method-specific id of colon-separated segments drawn from `A-Z a-z 0-9 . - _` and percent-encoded octets, the last segment non-empty. A DID URL is not a DID: no path, query or fragment (`/`, `?`, `#`), so a verification-method id such as `did:key:z6Mk…#z6Mk…` is refused. Compared by exact string equality — no case folding or percent-decoding. A consumer MUST still treat the value as data: the pattern keeps shell metacharacters, whitespace and quotes out of the wire form, but it does not make a DID safe to splice into a command or markup.",
+      "type": "string",
+      "maxLength": 2048,
+      "pattern": "^did:[a-z0-9]+:(?:(?:[A-Za-z0-9._-]|%[0-9A-Fa-f]{2})*:)*(?:[A-Za-z0-9._-]|%[0-9A-Fa-f]{2})+$"
+    }
+  }
+} as const;
+
+/**
+ * SPEC.md §7.2 policy for the request variant, from this specification's
+ * front matter. Pass to `consumeInbound` — items 5b, 7 and 8 are
+ * per-specification and cannot be derived from the document alone, and
+ * item 2 needs the schema this carries.
+ */
+export const SPEC = {
+  typeUri: TYPE_URI,
+  isBearer: false,
+  isProofRequired: true,
+  isRecipientRequired: true,
+  isIssuedAtRequired: false,
+  payloadSchema: PAYLOAD_SCHEMA,
+} as const;
+
+/**
+ * SPEC.md §7.2 policy for the success-response variant. `isRecipientRequired`
+ * tracks the *issuer* party's requirement because a response swaps the
+ * parties (§7.3 item 5).
+ */
+export const RESPONSE_SPEC = {
+  typeUri: RESPONSE_TYPE_URI,
+  isBearer: false,
+  isProofRequired: true,
+  isRecipientRequired: true,
+  isIssuedAtRequired: false,
+  payloadSchema: RESPONSE_PAYLOAD_SCHEMA,
+} as const;

package/src/git-ns/repo/adopt/0.1/payload.ts

@@ -3,7 +3,7 @@
  * Source: specs/git-ns/repo/adopt/0.1/payload.schema.json
  */
 
-import type { Bootstrap, Did_GitNsV0_1 as Did, DriftItem, Ext, ForgeAccount, ForgeHost, ForgeId, RepoResource, RepoSummary_GitNsV0_1 as RepoSummary, RepoVisibility, Sync } from "../../../../_shared/components.js";
+import type { Bootstrap, Did_GitNsV0_1 as Did, DriftItem_GitNsV0_1 as DriftItem, Ext, ForgeAccount_GitNsV0_1 as ForgeAccount, ForgeHost_GitNsV0_1 as ForgeHost, ForgeId_GitNsV0_1 as ForgeId, RepoResource_GitNsV0_1 as RepoResource, RepoSummary_GitNsV0_1 as RepoSummary, RepoVisibility, Sync_GitNsV0_1 as Sync } from "../../../../_shared/components.js";
 
 
 /**

package/src/git-ns/repo/adopt/0.2/payload.ts

@@ -3,7 +3,7 @@
  * Source: specs/git-ns/repo/adopt/0.2/payload.schema.json
  */
 
-import type { Bootstrap, Did_GitNsV0_3 as Did, DriftItem, Ext, ForgeAccount, ForgeHost, ForgeId, RepoResource, RepoSummary_GitNsV0_3 as RepoSummary, RepoVisibility, Sync } from "../../../../_shared/components.js";
+import type { Bootstrap, Did_GitNsV0_3 as Did, DriftItem_GitNsV0_1 as DriftItem, Ext, ForgeAccount_GitNsV0_1 as ForgeAccount, ForgeHost_GitNsV0_1 as ForgeHost, ForgeId_GitNsV0_1 as ForgeId, RepoResource_GitNsV0_1 as RepoResource, RepoSummary_GitNsV0_3 as RepoSummary, RepoVisibility, Sync_GitNsV0_1 as Sync } from "../../../../_shared/components.js";
 
 
 /**