[bokelley]

Fixes the upstream drift that is failing CI on every PR, including #3380 and #3399:

• Registry types out of sync. The published registry OpenAPI added a typed PREPARED_FIXTURES_DENIED error body, so registry.yaml and src/lib/registry/types.generated.ts are regenerated.
• Audit advisories. body-parser, undici, fast-uri and ip-address are patched within their existing ranges (lockfile only).
• Not fixed here: zod. Its high advisory is fixed in 4.6.6, but on 4.6.x zod-openapi renders an extended ProductSchema as an anyOf at about 1.5 MB, which breaks the schema-portability test. zod stays at 4.4.3, and the problem is tracked in zod 4.6.6 advisory: ProductSchema OpenAPI rendering changes on zod ≥ 4.6 #3402. The Security Audit lane will keep failing on that one advisory until zod 4.6.6 advisory: ProductSchema OpenAPI rendering changes on zod ≥ 4.6 #3402 lands.

Patch changeset included. Local: build, typecheck, format, registry tests and the portability test pass.

🤖 Generated with Claude Code

[aao-secretariat]

Medium: patch for a response-type widening. The generated 403 body goes from Error ({ error: string }) to Error | { code: "PREPARED_FIXTURES_DENIED"; refusal_code: string }. A downstream consumer reading .error off the 403 body now gets a compile error without first narrowing — a response-shape change on an exported type. Generated types are excluded from the changeset-trigger paths and this is an additive witness-the-wire correction, so patch is defensible, but minor is the more conservative semver call. Non-blocking.

[aao-secretariat]

Ladon verdict: Approve

Approve — routine registry schema sync with no blocking findings.

What I checked:

• schemas/registry/registry.yaml adds a distinct PREPARED_FIXTURES_DENIED 403 variant; anyOf branches are genuinely disjoint (Error requires error; new body requires code+refusal_code), so no ambiguous wire-shape collision.
• src/lib/registry/types.generated.ts regenerated to match the schema exactly — no drift, no fabrication (witness-not-translator preserved).
• package-lock.json bumps transitive deps only, no range changes, consistent with the changeset.
• Changeset present.

Medium findings (non-blocking):

• .changeset/registry-and-audit-sync.md:2 — patch changeset for a 403 response-type widening (Error → union). minor is arguably more correct, but generated types are excluded from the changeset trigger and this is an additive, witness-the-wire correction. One medium only.

Decision path: No critical/high (row 1 n/a). gated_paths: false (row 2 n/a). high_risk is true but the only high-risk file is (modified) with only a single medium finding — row 5 requires the modified file AND a medium; however the finding is on the changeset file, not the high-risk schema file, and more importantly re-reading row 5: it fires on any medium when a modified high-risk file is present.

Correction: row 5 reads "high_risk true AND any (modified) entry AND any medium finding." That condition is met → escalate.

Medium findings

• .changeset/registry-and-audit-sync.md:2 — patch changeset for a 403 response-type widening