v0.8.0

Added

• actions/apply-proposal composite action: copies a proposal's mapped
  Issue Fields onto its parent (type/parent/labels handled as
  reserved names via native Issue Type, sub-issue, and Label mutations),
  then closes the proposal and any open sibling proposals of the same
  parent. Idempotent — a no-op against an already-closed proposal.
• actions/reject-proposal composite action: closes a proposal, nothing
  else.

Changed

• proposal-shared.yml's apply and reject jobs now run the actions
  above instead of a placeholder notice.

v0.7.0

Changed

• Breaking: proposal-lifecycle-shared.yml is renamed to
  proposal-shared.yml, matching the <name>-shared.yml pattern used by the
  other reusable workflows. The workflow's name: and its Telegram-report
  workflow: value change from "Proposal Lifecycle" to "Proposal", and its
  concurrency group prefixes shorten from proposal-lifecycle-* to
  proposal-*.

v0.6.0

Added

• proposal-lifecycle-shared.yml reusable workflow: the contract for the
  five-job proposal lifecycle (apply, reject, distill, rework,
  propose) described in #11, with self-gating, an input-invariant check,
  and per-comment/per-repository concurrency groups. Domain logic for each
  action is not implemented yet — this release ships the contract and
  reporting scaffold only.
• actions/telegram-notify composite action: optionally report a job's
  triggered action and outcome to a Telegram chat (#46). Opt-in per
  consumer; a missing chat id/bot token is a no-op and a delivery failure
  never fails the calling job.

v0.5.0

Added

• collect-pull-requests-shared.yml reusable workflow and
  actions/collect-pull-requests composite action: collect open pull requests,
  including drafts, from configured
  organizations/repositories into a GitHub Project V2. Existing active and
  archived Project items are left untouched, and Status is owned by Project
  automation.

Changed

• Breaking: pull-issue-shared.yml and actions/pull-issue are renamed to
  collect-issues-shared.yml and actions/collect-issues for consistent naming
  across issue and pull-request collection.

v0.4.0

Changed

• Breaking: pull-issue-shared.yml and actions/pull-issue replace the
  comma-separated organizations and repos inputs with JSON-array
  organizations and repositories inputs.

v0.3.1

Removed

• intake-issue-shared.yml reusable workflow and actions/intake-issue
  composite action. Use pull-issue-shared.yml for centralized repository or
  organization intake.

v0.3.0

Added

• pull-issue-shared.yml reusable workflow: pulls open issues from a
  configured set of organizations and/or repositories into a GitHub
  Project V2, idempotently — the hub-side (pull) counterpart to
  intake-issue-shared.yml's push model. Donor repos need no
  configuration; organizations are expanded to repositories, and each
  repository's open issues are paginated independently.

v0.2.0

Added

• route-issue-shared.yml reusable workflow: transfers an issue to
  another repository when a configured label is applied, idempotently
  (verified: a retry after a completed transfer is a clean no-op, not a
  duplicate or an error). Exact label-to-repo routing only; unmatched
  labels and source-equals-destination are clean no-ops.

v0.1.2

• perf: scope project.items() query to the calling repo (#29)
• chore: pin actions/intake-issue to @v0.1, fix README's @v1 example (#26)

v0.1.1

• fix: check membership via project-side scan, not issue.projectItems (#24)