Allow the issues event in the observed-events policy before it is switched on #629

🤖 Generated by the Agentic Engineer (interactive Claude Code session)

Problem

The policy that limits which events may start a workflow, workflow-execution-policies/allow-observed-events.json, allows eight events and not issues. It is not switched on yet. devantler-tech/monorepo#4293 adds a monorepo workflow that starts on issues: labeled: it emails the maintainer at once when an ask is marked urgent. Once the policy is switched on, that workflow would stop starting, and urgent asks would wait for the weekly digest instead.

Proposed direction

Add issues to allowed_events before the policy moves to active, and update the README's count and table.

Acceptance criteria

• allow-observed-events.json allows issues, and the README describes nine events.
• The policy is applied, and its read-back matches.

Size

S. Part of #202.

Public maintainer-channel rollout integration — 24 October 2026

Monorepo#4489 completes the accepted daily GitHub ask channel. The managed monorepo label set also needs maintainer-ask-cap-delayed and maintainer-ask-delivered; an independent live read confirmed those undeclared labels are removed by reconciliation. Declare both in the authoritative source, alongside this issue's existing issues event prerequisite. Preserve every current label and keep the event policy disabled; activation remains the separate owner-controlled rollout under #202.

• The rendered monorepo labels retain both urgent-delivery state labels and every existing live label.
• The reviewed release is published/reconciled, and independent GitHub reads confirm both labels and the policy's unchanged disabled state.