Audit Log Typings

[lillithrosepup]

Closes # No issue submitted, discussed in discord

Evidence

• Every property, type and example comes from a captured response
• • Pulled latest entry from each audit type my bot has captured. Can provide on request
• pnpm lint passes
• pnpm test -w session -w <workflow> passes

[pkg-pr-new]

pnpm add https://pkg.pr.new/vrchatapi/specification/vrchat@6c32f5e

commit: 6c32f5e

[lillithrosepup]

TODO:

• different union fallback
• check GroupAuditLogEntryDataGroupMemberUserUpdate
• finish GroupAuditLogEntryDataGroupRoleUpdate
• finish GroupAuditLogEntryDataGroupUpdate
• arrazzo tests

[Copilot]

Copilot review overview

🔵 Needs a closer look

It is a DRAFT adding 56 reverse-engineered schemas with new discriminator/allOf patterns and no accompanying test workflow or completed test run, so it needs human verification against captured traffic.

Review effort: Balanced
Findings: 1

Open (1)

• Inconsistent targetId schema types across related group events · New

What changed in this PR

This PR replaces the previously free-form GroupAuditLogEntry.data (type: object with an inline example) with a fully-typed, discriminated model of VRChat's group audit log. GroupAuditLogEntry is now allOf: [GroupAuditLogEntryBase, GroupAuditLogEntryEvent], where GroupAuditLogEntryEvent is a oneOf keyed by a discriminator on eventType (with a 3.2.1 defaultMapping catch-all to GroupAuditLogEntryUnknown). Each of the 32 known eventTypes gets its own entry schema plus a dedicated data payload schema, with shared primitives (StringChange, BooleanChange, StringListChange, UserIdChange, DataEmpty, DataUnknown) and allOf reuse between create/delete payload pairs. This is a documentation-only change that strengthens generated client typings for the group audit log endpoints. The PR is explicitly marked DRAFT, with the pnpm test -w session -w <workflow> evidence checkbox left unchecked.

Changes:

• Split GroupAuditLogEntry into a shared base + a discriminated oneOf of 32 event types plus an Unknown fallback.
• Added per-event data payload schemas, reusing shared change-wrapper and base payload schemas via $ref/allOf.
• Removed the old inline data/targetId definitions and example from GroupAuditLogEntry.yaml.

File	Description
GroupAuditLogEntry.yaml	Reworked to allOf of base + event discriminator; drops inline data/targetId/example.
GroupAuditLogEntryBase.yaml	New shared fields (actorId, created_at, eventType, groupId, id, etc.).
GroupAuditLogEntryEvent.yaml	discriminator + defaultMapping + oneOf over all 32 event schemas and Unknown.
GroupAuditLogEntryUnknown.yaml	Catch-all event using eventType with not: enum of the known types.
GroupAuditLogEntryGroup*.yaml (32 files)	One wrapper per eventType binding a const eventType, targetId, and a data $ref.
GroupAuditLogEntryDataGroup*.yaml (data payloads)	Per-event payload shapes; create/delete pairs share a base via allOf.
GroupAuditLogEntryDataEmpty.yaml /​ DataUnknown.yaml	Closed empty payload / open (additionalProperties: true) payload.
GroupAuditLogEntry{String,Boolean,StringList,UserId}Change.yaml	Reusable before/after change wrappers for update payloads.

Observations from review: All $ref targets resolve, the discriminator mapping/oneOf/Unknown-not-enum sets are internally consistent, defaultMapping is valid in the 3.2.1 source and stripped by the downlevel plugin for 3.1/3.0 bundles, and the newly introduced allOf composition is handled correctly by close-schemas (unevaluatedProperties). The main substantive issue is inconsistent targetId typing (see inline comment). Per the repo's evidence conventions, the new schemas are not yet backed by any test/arazzo.yaml workflow, and the test checkbox is unchecked.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[lillithrosepup]

@ariesclark re-requesting review, ive double checked everything & implemented the group.(role|member)?.update? log types
Only thing left is arazzo but it would be a whole other task to automate this