chore: sync Registry Stack identifiers

[github-actions]

Summary

Synchronize the active identifier allowlist from Registry Stack commit f3c54332e0a8eb8c20f1a034dbb4b6bdceef673e.

This branch is automation-owned. Do not push human edits to it; change Registry Stack source or open a separate publisher PR instead.

registrystack-id@0.1.0 report:catalog
node scripts/report-catalog-change.mjs origin/main

Identifier catalog change

Published identifiers: 296 -> 338

Added (42)

• https://id.registrystack.org/problems/registry-breg/ingestion/chunk_mismatch
• https://id.registrystack.org/problems/registry-breg/ingestion/profile_mismatch
• https://id.registrystack.org/problems/registry-breg/ingestion/receipt_erased
• https://id.registrystack.org/problems/registry-breg/ingestion/run_blocked
• https://id.registrystack.org/problems/registry-breg/ingestion/run_not_open
• https://id.registrystack.org/problems/registry-breg/runtime/field_encryption/unavailable
• https://id.registrystack.org/problems/registry-casework/review/result-expired
• https://id.registrystack.org/problems/registry-casework/review/submission-conflict
• https://id.registrystack.org/problems/registry-casework/review/task-not-held
• https://id.registrystack.org/problems/registry-scheduling/authentication/refused
• https://id.registrystack.org/problems/registry-scheduling/booking/duplicate-active
• https://id.registrystack.org/problems/registry-scheduling/cancellation/cutoff-passed
• https://id.registrystack.org/problems/registry-scheduling/capability/unmatched
• https://id.registrystack.org/problems/registry-scheduling/capacity/exhausted
• https://id.registrystack.org/problems/registry-scheduling/cursor/expired
• https://id.registrystack.org/problems/registry-scheduling/cursor/invalid
• https://id.registrystack.org/problems/registry-scheduling/eligibility/unavailable
• https://id.registrystack.org/problems/registry-scheduling/hold/expired
• https://id.registrystack.org/problems/registry-scheduling/hold/released
• https://id.registrystack.org/problems/registry-scheduling/hook/unavailable
• https://id.registrystack.org/problems/registry-scheduling/horizon/outside
• https://id.registrystack.org/problems/registry-scheduling/idempotency/expired
• https://id.registrystack.org/problems/registry-scheduling/idempotency/key-reused
• https://id.registrystack.org/problems/registry-scheduling/location/closed
• https://id.registrystack.org/problems/registry-scheduling/operation/not-authorized
• https://id.registrystack.org/problems/registry-scheduling/party/capacity-inadequate
• https://id.registrystack.org/problems/registry-scheduling/policy/changed
• https://id.registrystack.org/problems/registry-scheduling/precondition/failed
• https://id.registrystack.org/problems/registry-scheduling/precondition/required
• https://id.registrystack.org/problems/registry-scheduling/prerequisite/missing
• https://id.registrystack.org/problems/registry-scheduling/profile/not-authorized
• https://id.registrystack.org/problems/registry-scheduling/request/body-too-large
• https://id.registrystack.org/problems/registry-scheduling/request/invalid
• https://id.registrystack.org/problems/registry-scheduling/request/method-not-allowed
• https://id.registrystack.org/problems/registry-scheduling/request/not-found
• https://id.registrystack.org/problems/registry-scheduling/request/unprocessable
• https://id.registrystack.org/problems/registry-scheduling/request/unsupported-media-type
• https://id.registrystack.org/problems/registry-scheduling/resource/unavailable
• https://id.registrystack.org/problems/registry-scheduling/revision/mismatch
• https://id.registrystack.org/problems/registry-scheduling/schedule/unpublished
• https://id.registrystack.org/problems/registry-scheduling/service/unavailable
• https://id.registrystack.org/schemas/scheduling/runtime/runtime.v1alpha1.schema.json

Removed (0)

None.

Metadata updated (63)

• https://id.registrystack.org/problems/registry-breg/action/evidence_failed
• https://id.registrystack.org/problems/registry-breg/action/handler_failed
• https://id.registrystack.org/problems/registry-breg/action/refused
• https://id.registrystack.org/problems/registry-breg/authentication/refused
• https://id.registrystack.org/problems/registry-breg/idempotency/conflict
• https://id.registrystack.org/problems/registry-breg/lookup/unresolved
• https://id.registrystack.org/problems/registry-breg/mutation/conflict
• https://id.registrystack.org/problems/registry-breg/precondition/failed
• https://id.registrystack.org/problems/registry-breg/precondition/required
• https://id.registrystack.org/problems/registry-breg/query/cursor_invalid
• https://id.registrystack.org/problems/registry-breg/query/invalid
• https://id.registrystack.org/problems/registry-breg/request/invalid
• https://id.registrystack.org/problems/registry-breg/request/plan_refused
• https://id.registrystack.org/problems/registry-breg/request/timeout
• https://id.registrystack.org/problems/registry-breg/resource/not_found
• https://id.registrystack.org/problems/registry-breg/runtime/not_ready
• https://id.registrystack.org/problems/registry-breg/service/unavailable
• https://id.registrystack.org/problems/registry-breg/source/unavailable
• https://id.registrystack.org/problems/registry-breg/unsupported/media_type
• https://id.registrystack.org/problems/registry-casework/absence/cover-cycle
• https://id.registrystack.org/problems/registry-casework/absence/invalid-period
• https://id.registrystack.org/problems/registry-casework/absence/overlap
• https://id.registrystack.org/problems/registry-casework/absence/self-cover
• https://id.registrystack.org/problems/registry-casework/authentication/refused
• https://id.registrystack.org/problems/registry-casework/clock/recompute-preview-expired
• https://id.registrystack.org/problems/registry-casework/cursor/expired
• https://id.registrystack.org/problems/registry-casework/cursor/invalid
• https://id.registrystack.org/problems/registry-casework/idempotency/expired
• https://id.registrystack.org/problems/registry-casework/idempotency/key-reused
• https://id.registrystack.org/problems/registry-casework/operation/not-authorized
• https://id.registrystack.org/problems/registry-casework/precondition/failed
• https://id.registrystack.org/problems/registry-casework/precondition/required
• https://id.registrystack.org/problems/registry-casework/profile/not-authorized
• https://id.registrystack.org/problems/registry-casework/profile/not-human
• https://id.registrystack.org/problems/registry-casework/request/body-too-large
• https://id.registrystack.org/problems/registry-casework/request/invalid
• https://id.registrystack.org/problems/registry-casework/request/method-not-allowed
• https://id.registrystack.org/problems/registry-casework/request/not-found
• https://id.registrystack.org/problems/registry-casework/request/reason-unsupported
• https://id.registrystack.org/problems/registry-casework/request/source-rejected
• https://id.registrystack.org/problems/registry-casework/request/unprocessable
• https://id.registrystack.org/problems/registry-casework/request/unsupported-media-type
• https://id.registrystack.org/problems/registry-casework/runtime/failure
• https://id.registrystack.org/problems/registry-casework/service/unavailable
• https://id.registrystack.org/problems/registry-casework/source-profile/not-applicable
• https://id.registrystack.org/problems/registry-casework/source-profile/required
• https://id.registrystack.org/problems/registry-casework/source/bad-gateway
• https://id.registrystack.org/problems/registry-casework/source/not-found
• https://id.registrystack.org/problems/registry-casework/source/record-missing
• https://id.registrystack.org/problems/registry-casework/source/reviewer-not-authorized
• https://id.registrystack.org/problems/registry-casework/source/signature-invalid
• https://id.registrystack.org/problems/registry-casework/work-item/already-claimed
• https://id.registrystack.org/problems/registry-casework/work-item/not-holder
• https://id.registrystack.org/problems/registry-casework/work-item/not-offered
• https://id.registrystack.org/problems/registry-casework/work-item/not-visible
• https://id.registrystack.org/problems/registry-casework/work-item/proposal-changed
• https://id.registrystack.org/problems/registry-casework/work-item/recovery-pending
• https://id.registrystack.org/problems/registry-casework/work-item/source-unavailable
• https://id.registrystack.org/problems/registry-casework/work-item/superseded
• https://id.registrystack.org/schemas/breg/authoring/registry-module.v1alpha1.schema.json
• https://id.registrystack.org/schemas/breg/authoring/registry-project.v1alpha1.schema.json
• https://id.registrystack.org/schemas/breg/runtime/runtime.v1alpha1.schema.json
• https://id.registrystack.org/schemas/casework/runtime/runtime.v1alpha1.schema.json

Artifact digest updated (4)

• https://id.registrystack.org/schemas/breg/authoring/registry-module.v1alpha1.schema.json
• https://id.registrystack.org/schemas/breg/authoring/registry-project.v1alpha1.schema.json
• https://id.registrystack.org/schemas/breg/runtime/runtime.v1alpha1.schema.json
• https://id.registrystack.org/schemas/casework/runtime/runtime.v1alpha1.schema.json

Checks

• npm run check:upstream -- _upstream/registry-stack
• npm test

All checks ran before this branch was pushed.